John's "cat blog entry" use case has been right all along. The first/core APP spec really should address it on its own.
Peace deeje on 2005-11-04 20:57, John Panzer at [EMAIL PROTECTED] wrote: > James M Snell wrote: > >> John Panzer wrote: >> >>> Quote from this document: >>> "First the client creates a new image resource by POSTing the image >>> to the IRI of the media collection." >>> >>> So, given just the IRI of a Collection resource that presumably >>> represents my "main" feed/blog/whatever, how do I get the IRI of the >>> "media collection" to use for my first POST? >>> >> >> How the multiple Collection IRI's are discovered is an Introspection >> task that would be defined in a separate I-D as has been discussed in >> other recent threads. > > Hmm. I assume that would at best be a document produced after thid I-D > (otherwise, they could be consolidated now). I think this is > operationally equivalent to moving the ability to post such compound > documents out of the core APP. I'm not that concerned about more > complex discovery, etc. but it appears to me that this proposal is > throwing the baby out with the bathwater. If I'm misreading the > situation, please let me know. > > Back when we were starting this whole IETF WG thing, there was general > consensus that the publishing protocol needed to support > XHTML-plus-picture-resources as part of the core. I don't think that's > changed, though please feel free to let me know if you think this is no > longer the case. -- Deeje Cooley Product Marketing and Technology Macromedia Contribute http://www.macromedia.com/contribute http://deeje.com/
