[AVT] Updated 3GPP2 MIME ID: draft-garudadri-avt-3gpp2-mime-01.txt

[hgarudad at qualcomm.com (Harinath Garudadri)]

At 10:49 AM 1/16/2005, Colin Perkins wrote:
>On 17 Dec 2004, at 22:19, Harinath Garudadri wrote:
>>  An updated version of the ID registering 3gpp2 MIME types is now
>>available at
>>http://www.ietf.org/internet-drafts/draft-garudadri-avt-3gpp2-mime 
>>-01.txt. This version uses the correct template and incorporates some
>>editorial changes.
>
>I have a few details that should be resolved:
>
>  - Please move the paragraph defining "Conventions used in this
>document" to
>    be part of the introduction, rather than being a separate section.
>Also,
>    please remove section 6 and add the text as an unnumbered note in the
>    boilerplate at the start of the draft.

Done. The latest draft can obtained from 
http://people.qualcomm.com/randy/draft-garudadri-avt-3gpp2-mime-02.txt if 
you need it before the ID appears at 
http://www.ietf.org/internet-drafts/draft-garudadri-avt-3gpp2-mime -02.txt


>  - Is there a need to register media types other than audio or video
>(the
>    most obvious being "text/3gpp2", to allow a future timed text
>format)?

3GPP2 timed text is same as 3GPP timed text. So, there is no need for other 
media types and we plan to use text/3gpp-tt

>Otherwise this draft looks reasonable to me, although I'm not a MIME
>expert. Once you've made these changes, you might consider asking for
>review on the <[e-mail]> mailing list.

I have copied <[e-mail]> in this thread. Is this adequate or do 
I need to do anything else?

Thanks,
hari.

>Colin

Dr. Hari Garudadri
Qualcomm Inc.
work    : [phone]
mobile : [phone]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://eikenes.alvestrand.no/pipermail/ietf-types/attachments/20050120/96e19386/attachment.htm
>From [e-mail]  Thu Jan 27 14:12:21 2005
From: sah at 428cobrajet.net (Scott Hollenbeck)
Date: Thu Jan 27 14:10:26 2005
Subject: Media Types review for application/simple-filter+xml
In-Reply-To: <[e-mail]>
Message-ID: <20050127131018.QAYU1713.lakermmtao09.cox.net@A31P>

Two comments.  The first is on the namespace registration template found in
section 8.2.  It says:

"This section registers a new XML namespace, as per guidelines in URN
document [4]."  [4] is:

[4]   Mealling, M., "The IETF XML Registry", RFC 3688, January 2004.

There are two problems with the above.

1. 3688 isn't really a URN document.  It describes procedures to register
URNs, but it is better described as the "IETF XML Registry".

2. Section 3.2 of 3688 describes what gets registered when registering an
XML namespace.  It says "XML Namespaces ... are named by a URI.  They have
no real, machine-parsable representation".  Yet the template includes a
chunk of XML to be registered.  It's not needed, so why is it included?  All
that needs to be registered is the urn:ietf:params:xml:ns:simple-filter URN.

Second comment: the schema in section 6 includes several elements and
attributes that allow extensibility, including "<xs:anyAttribute
namespace="##other" processContents="lax"/>" and "<xs:any
namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>".  I don't see any text in the document describing
just how these extension elements and attributes are supposed to be used,
though.  You really should add some text to describe the extensibility
framework.  What's allowed?  What isn't?  What needs to be done to avoid
namespace collisions and version conflicts?

-Scott-

> -----Original Message-----
> From: Hisham Khartabil [mailto:[e-mail]] 
> Sent: Wednesday, January 26, 2005 9:21 AM
> To: [e-mail]
> Cc: Ted Hardie; Robert Sparks
> Subject: Media Types review for application/simple-filter+xml
> 
> The SIMPLE Working Group requests a Media Type review for the 
> following new type:
> 
> - application/simple-filter+xml
> 
> This is intended for the IETF tree, and specified in section 
> 8.1 of 
> http://www.ietf.org/internet-drafts/draft-ietf-simple-filter-format
> -04.txt
> 
> Thanks,
> Hisham Khartabil
> SIMPLE WG Co-chair