On 07/12/06, Jan Algermissen <[EMAIL PROTECTED]> wrote: > > > > > > > On Thursday, December 07, 2006, at 05:18PM, "Steve Jones" <[EMAIL PROTECTED]> > wrote: > >On 06/12/06, Jan Algermissen <[EMAIL PROTECTED]> wrote: > >> The Atom publishing protocol for example solves a heap of machine to > >> machine interaction problems wih only a handful of link semantics. > >> (Remember: Enterprise software need not be enterprisey) > > > >Where is atom used in a pure server to server (i.e. not as a content > >publishing mechanism)? > > I mean the Atom Publiching Protocol, not Atom. I suggest to check out the > current draft > http://www.ietf.org/internet-drafts/draft-ietf-atompub-protocol-11.txt > and see for yourself what linking semantics are in there and how they can be > used in > non human contexts. > > Question: How does your browser find the stylesheet assciated with a Web > page? > By following the link with the desired semantic, right? That is about all > the machine2machine magic > you ask for (modulo forms languages).
So what you are saying therefore is that for REST you need to publish a document (like the one you referenced) for every resource that you are trying to expose? The document you reference details how some content can be formed but what happens when I need to actually process the content within the atom wrapping? Surely myself and the originator must have some shared understanding or perhaps you expect some intermediary to do the conversion - in which case it must have shared understanding of what I want and what the sender provides? So how is that communicated? > > > > >> > >> Nobody said you should use a media type with just one link semantic > >> (<a href..>) for machine to machine interaction! > > > >What other standard semantics are there? I'm still not understanding > >how consumers have the meaning communicated to them in advance. > > See browser-finds-stylesheet use case above. > Read the atom pub protocol specs with a good eye on app:collections and how > client software picks them. The read the atompub-features extension > (http://tools.ietf.org/wg/atompub/draft-snell-atompub-feature-01.txt) to see > how > collections (processors) can be picked by capability (aka by type). And how do you communicate the meaning of that type to the consumer? The spec describes an envelope, but not the meaning of the content (sort of like the SOAP spec). > > Cheers, > Jan > > > > >> > >> Jan > >> > >> > > >
