On Wed, 29 Nov 2006 20:03:22 +0100, Thomas Broyer <[EMAIL PROTECTED]>
wrote:
I'd largely prefer augmenting the existing media type with a 'type'
parameter:
- application/atom+xml => either feed or entry (as defined in RFC4287)
- application/atom+xml;type=feed => feed
- application/atom+xml;type=entry => entry
+1.
How about defining a "tree" similar to the */vnd.* one?
- application/atom+xml => feed or entry document
- application/atom.categories+xml => category document
- application/atom.service+xml => service document
...and of course, if this proposal is finally accepted:
- application/atom.entry+xml => entry document
I think 'type=*' is a cleaner solution, but both serves the same purpose
so I'm not religious about which solution we choose. But I agree that
distinguishing between entries, feeds and every other atom resource is
indeed useful. +1.
As for Tim's concerns, I'd also prefer having it done outside the APP.
Yep.
Also, the APP draft would need to be updated to remove the "entry"
special value for app:accept, as it would be equivalent to the new or
revised media type (app:accept=application/atom+xml;type=entry or
app:accept=applicationAtom.entry+xml)
Of course.
--
Asbjørn Ulsberg -=|=- http://virtuelvis.com/quark/
«He's a loathsome offensive brute, yet I can't look away»
