Re: Interaction model vs data model

On 1/24/13 12:25 PM, Wilde, Erik wrote:
> hello kingsley.
> On 2013-01-24 17:59 , "Kingsley Idehen" <> wrote:
>> On 1/24/13 11:40 AM, Wilde, Erik wrote:
>>> i am certainly using "link" in the REST sense: references that clients
>>> are expected to follow in their application flow, and where the behavior
>>> is defined by the protocol (the media type). if that may cause
>>> confusion, what about hyperlink, following the recent trend that one of
>>> the essences of REST is that it's hypermedia?
>> Is a Content-type (or media type) a protocol? Isn't that metadata for
>> the resource denoted by the link? Basically, the description of the data
>> de-referenced by the link.
> any content type that uses links (i.e., goes beyond simple image/gif kind
> of standalone data formats) essentially is a protocol: it defines rules
> how interactions between clients and servers are possible, and what they
> mean.
> cheers,
> dret.

Bearing in mind your characterization of Content-Type as a protocol. 
What are the Content-Types supported by LDP? Hopefully, we can 
triangulate a route to clarity along this axis. Note, Linked Data 
doesn't need its own Content-Type since it covers RDF model based data 
representation and RESTful data access.

Linked Data is all about denoting entities and their relations using 


1. .
2. -- HTML .
3. -- RDF/XML (just one of many 
Content-Types associated with RDF) .



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web:
Personal Weblog:
Twitter/ handle: @kidehen
Google+ Profile:
LinkedIn Profile:

Received on Thursday, 24 January 2013 18:19:13 UTC