Re: "Basic profile" terminology ?

Looking at the UCR example of application integration, I think I see a 
style that a bit like a shared, schemaless database than as a designed 
set of services.

Applications put data in (publish); other applications retrieve the data 
- but the publishing application does not put data in the shared data 
repository for a purpose other than to publish it.  There is no design 
intent, let alone a contract between sender and receiver.  RDF is useful 
for this because it decouples the data layer from application data 
modelling by enabling the schemaless.

The "RESTful interactions" and book order examples have a different 
character where the order is placed by POSTing with a media type for the 
expectations - there is a shared intent identified by the media type. 
There is a book ordering service, a book order is made by a certain 
action; the return body is presumably something to track the order with 
and the body has the links to follow.

	Andy

Received on Monday, 9 July 2012 14:42:16 UTC