For review: application/atom+xml

Mark Nottingham mnot at mnot.net
Fri Apr 8 02:20:39 CEST 2005


Will get this in -08 and re-circulate when it's ready.

Thanks,


On Apr 7, 2005, at 4:45 AM, Scott Hollenbeck wrote:

> Mark,
>
> One thing I didn't catch earlier (sorry): the change controller for 
> types in
> the standards tree MUST be the IESG.  It would be more appropriate to 
> say
> it's the IETF community as described in RFC 2048 and the documents 
> that will
> soon obsolete 2048, but the IESG is the standards process gatekeeper so
> that's what we've been using.  We've also accepted text where people 
> have
> said something like "The <foo> working group as designated by the 
> IESG".
>
> -Scott-
>
>> -----Original Message-----
>> From: Mark Nottingham [mailto:mnot at mnot.net]
>> Sent: Wednesday, April 06, 2005 11:41 PM
>> To: ietf-types at alvestrand.no
>> Subject: For review: application/atom+xml
>>
>>
>> One of the deliverables of the ATOMPUB WG is an xml-based format for
>> Web syndication. Please review the proposed "application/atom+xml"
>> media type therein; the registration template can be found below, and
>> the complete draft is:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-07.txt
>>
>> Regards,
>>
>> ---8<----
>>     An Atom Document, when serialized as XML 1.0, can be
>> identified with
>>     the following media type:
>>
>>     MIME media type name: application
>>     MIME subtype name: atom+xml
>>     Mandatory parameters: None.
>>     Optional parameters:
>>        "charset": This parameter has identical semantics to
>> the charset
>>           parameter of the "application/xml" media type as
>> specified in
>>           [RFC3023].
>>     Encoding considerations: Identical to those of
>> "application/xml" as
>>        described in [RFC3023], section 3.2.
>>     Security considerations: As defined in this specification.
>>        [[anchor59: update upon publication]]
>>        In addition, as this media type uses the "+xml" convention, it
>>        shares the same security considerations as described
>> in [RFC3023],
>>        section 10.
>>     Interoperability considerations: There are no known
>> interoperability
>>        issues.
>>     Published specification: This specification.  [[anchor60:
>> update upon
>>        publication]]
>>     Applications that use this media type: No known applications
>>        currently use this media type.
>>
>>     Additional information:
>>
>>     Magic number(s): As specified for "application/xml" in [RFC3023],
>>        section 3.2.
>>     File extension: .atom
>>     Fragment identifiers: As specified for "application/xml" in
>>        [RFC3023], section 5.
>>     Base URI: As specified in [RFC3023], section 6.
>>     Macintosh File Type code: TEXT
>>     Person and email address to contact for further information: Mark
>>        Nottingham <mnot at pobox.com>
>>     Intended usage: COMMON
>>     Author/Change controller: This specification's author(s).
>>        [[anchor61: update upon publication]]
>> --->8---
>>
>>
>> --
>> Mark Nottingham     http://www.mnot.net/
>>
>>
>
>
>

--
Mark Nottingham     http://www.mnot.net/




More information about the Ietf-types mailing list