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). > >> >> 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). Cheers, Jan > >> >> Jan >> >> >
