On 5/3/06, James M Snell <[EMAIL PROTECTED]> wrote:
No, the listing in accept is *only* a listing of media ranges and/or the "entry" label and determines only what kinds of representations may be POSTed to the collection. It does not differentiate between different types of entries.
Looks like a design error to me. Essentially, PaceMediaEntriesN conflates the /purpose/ of a collection with the media types it accepts. Contrast this with the approach in http://franklinmint.fm/2006/01/24/draft-sayre-atompub-protocol-basic-06.html#rfc.section.9 where you get a space separated list in a @class attribute. That allows partial understanding by allowing attributes such as class="feed", class="feed media", and class="feed gcal". That would tell a client that it could reasonably edit the Atom-standard fields in that feed, as long as it built a DOM and changed only the nodes it knows about. class="MySpecial" would indicate that the client could of course read the feed, but might not be able to edit it without knowledge of the extension. The attributes @accept and, probably, @readonly are a definitely right up against the boundary of what would be wise to standardize. -- Robert Sayre
