On Dec 17, 2006, at 10:13 AM, James M Snell wrote:
Quite frankly it doesn't matter what we call anything right now. The
server gets to determine what pieces of data it's willing to handle.
Period. If you want anything more than that, use webdav.
(Sorry if this has already been said or not on the point, but I
cannot read through the thread right now).
- The server is free to 'mess' with the PUTed data at will before
doing the update; so it can strip out whatever it wants.
- Clients should do a GET before doing a PUT so they get some chance
to see what the sever actually handles
Jan
- James
Eric Scheid wrote:
On 17/12/06 1:13 PM, "A. Pagaltzis" <[EMAIL PROTECTED]> wrote:
* Lisa Dusseault <[EMAIL PROTECTED]> [2006-12-16 02:15]:
Since clients post Atom entries and other clients retrieve
them, it seemed reasonable to want to extend Atom
client-to-client. If I used "AtomFu" client that was able to
annotate my entries automatically with what music I was
listening to (track name, album and artist in XML elements)
while I wrote a blog posting, I thought AtomFu should just
store that as XML markup in the entry.
That is, IMO, a misconception about Atom one that is frequently
seen. We just had a similar discussion tonight in #atom on the
Freenode IRC network. The track name, album and artist are data;
they should be part of the payload of an entry, not part of its
envelope. In practice, that means you use either microformats or
a more structured format than HTML. Extending the Atom envelope
is a strategy of last resort.
wha?
What music Lisa is listening to when she wrote a blog posting is
meta data,
not content, unless of course she's writing a blog posting *about*
that
particular bit of music. The music is contextual meta data, along
the same
vein as geo location of circumstance, the atom:generator involved,
and even
the atom:published date/time.
Since when are we calling atom entries "envelopes"?
e.
