So this needs a decision tree:
+1 to having some way to modify type= (either new media type, or
appending ";type=entry", +0 to either)
+1 to application/atom.entry+xml if new media type is used
+1 to doing this outside of APP (but concerned about deprecating...)
My use case: A web page that contains both a blog entry, and the
comments for that entry. I want to be able to autodiscover alternates
for both, using separate documents, for example:
<link rel="alternate" type="application/atom.entry+xml" href="entry.xml"
title="This entry"/>
<link rel="alternate feed" type="application/atom+xml"
href="comments.xml" title="This entry's comments"/>
-John
James M Snell wrote:
http://www.intertwingly.net/wiki/pie/PaceEntryMediatype
#pragma section-numbers off
== Abstract ==
For the current Atom Publishing Protocol draft...
Create a new media type for Atom Entry Documents: application/atomentry+xml
Deprecate the use of application/atom+xml for Entry Documents.
== Status ==
Proposed
== Rationale ==
The fact that one media type is used for both Feed and Entry documents
has repeatedly come up as a problem on more than one occasion. We have
an opportunity to fix this problem now.
== Proposal ==
Add to Section 6.1
{{{
Atom Entry Documents are identified with the "application/atomentry+xml"
media type (See section 15).
}}}
Renumber existing section 15.3 to 15.4
Insert..
{{{
15.3 Content-type registration for 'application/atomentry+xml'
MIME media type name: application
MIME subtype name: atomentry+xml
Mandatory parameters: None.
Optional parameters:
"charset": This parameter has semantics identical 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.
In addition, as this media type uses the "+xml" convention, it
shares the same security considerations as described in [RFC3023],
Section 10.
Interoperability considerations: RFC 4287 registers the
application/atom+xml Content-Type for both Atom Feed and Entry
Documents. For Atom Entry Documents, the use of the
application/atom+xml type should be avoided.
Published specification: This specification.
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: .atomentry
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:
This specification's author(s)
Intended usage: COMMON
Author/Change controller: IESG
}}}
== Impacts ==
== Notes ==
----
CategoryProposals
