On 9/12/05, Bob Wyman <[EMAIL PROTECTED]> wrote: > I believe it doesn't make sense for us to add data-carrying elements > to Atom other than atom:content or atom:summary. Atom provides a definition > of a collection of entries and it provides the entry format. Frankly, it > should stop there. The data payload should be carried in the content > element.
I believe the ability to include data outside the content is likely to be useful, and may even be essential in some republishing scenarios where additional metadata about the payload is required. But that's not to say the transport-only view of Atom doesn't offer big advantages in the Structured Blogging kind of scenario where the data can be neatly packaged, relatively opaquely to the rest of the entry data. (Atom as SOAP lite?) One aspect I am curious about - are you intending to use the Atom entry ID as an identifier within the content at all? Any issues there? Cheers, Danny. -- http://dannyayers.com
