While reviewing the changes we'd need to make to our impl. to support PaceMediaEntries4, the question has come up about how to handle posted text and xml media. Specifically, whether or not it would be appropriate to inline the text/xml in the atom:content rather than use content/@src.
For example, if I POST an ical to an APP collection, POST /mycollection HTTP/1.1 Host: example.org Content-Type: text/calendar Content-Length: nnnn BEGIN:VEVENT ... END:VEVENT Would it be appropriate for the server to inline the iCal in the Atom entry rather than link to it via content/@src. <entry> ... <link rel="edit" type="application/atom+xml" href="/entry/foo" /> <link rel="edit-resource" type="text/calendar" href="/entry/foo" /> <content type="text/calendar"> BEGIN:VEVENT ... END:VEVENT </content> </entry> Note that the edit and edit-resource href's are the same meaning that the user can PUT either an atom:entry or a text/calendar to the URI. This is clearly legal according to RFC4287 and I think it should be legal in APP. There is currently nothing in APP draft -08 or PaceMediaEntries4 that would forbid this behavior. - James p.s. looking at the above example, I'm thinking "edit-resource" in PaceMediaEntries4 should be renamed to "edit-content".
