On Wed, Jun 20, 2007 at 04:54:10PM -0700, Yaron Goland wrote: > > Below I walk through a number of mandatory ATOM elements and explain > that in many cases we either have no useful value for these elements or > the values we have are potentially deceptive. Rather than wasting > enormous amounts of bandwidth sending around empty elements in GET > responses and even more bandwidth on having clients have to send these > elements up to us on PUTs/POSTs (where we will ignore the submitted > values) can we just make these values optional in ATOM? Atom is a very general format, suited to representing many different kinds of things, but it's not for everything. If it were, it would just be a reinvention of XML/RDF/<whatever> and there wouldn't be much point. If you're having to twist the model that much to make your data fit, you should probably be using some other format. (The above is my opinion, if anyone here things that Atom should be used as a completely generic envelope please shake your head vehemently.)
Attachment:
pgpmIh8Bxnl92.pgp
Description: PGP signature