Eric Scheid wrote:
then you're not going to like what I was thinking of doing ... posting
<atom:category /> chunks to an APP/media collection, such that the media
collection entry might look like this (no typos this time, I hope)...

<entry>
   ...
   <content type="application/atom+xml">
       <category .../>
   </content>
</entry>

Now that we're talking about APP things are slightly different. I wouldn't necessarily expect an Atom aggregator to be able to handle APP media feeds in a useful way, so if APP decided to do something wierd with atom:content elements I wouldn't be particularly concerned as long as it were documented well enough that APP clients would know how to handle it.

However, as it stands this wouldn't be a valid media collection according to the APP spec since the media resource is supposed to be stored external to the collection feed and referenced via a content src link. Even then, I'd think you'd need a different type to signfy that the content was in fact a collection element and not an Atom document.

Regards
James

Reply via email to