Re: What is the correct media-type for a Hydra specification?

On 4/16/15 8:22 PM, Erik Wilde wrote:
> hello kingsley.
>
> On 2015-04-16 17:17 , Kingsley Idehen wrote:
>> I think "lookup the meaning or
>> descriptoin" of its referent is what HTTP URI based hyperlinks
>> facilitate. For instance, <#That> could *identify* an entity of Type
>> document, but that doesn't imply <#This> also *identifies* an entity of
>> type document, even though we perceive their respective meanings
>> (descriptions or connotations) via hypermedia.
>

Erik,

> you're thinking about the RDF data model here. 

I am not.

I am actually talking about the fundamental architecture of the Web 
[1][2][3]. RDF the standard is simply retrospective formalization of 
what was already an intrinsic aspect of the Web's design.

@rel identifies a Relation.

<a/> provides relation object (or attribute value) lookup mechanism.

RDF fully exposes the names of subject, predicate [relation], and object 
parts of an entity relationship.

Using HTTP URIs in RDF statements (which represent relations) simply 
leverages HTTP in regards name interpretation i.e., 
name->document_location indirection. Basically combining denotation and 
connotation to produce identification.

> a very different thing from the web and web services. 

I disagree.

> you're right in what you say when it comes to describing the RDF data 
> model. hypermedia as a way to design loosely coupled information 
> systems is a different thing.

Hypermedia is simply webby content.

Ultimately Hydra, Schema.org, and related initiatives (for describing 
HTTP driven Services) will soon put all of this confusion to REST :)

Links:

[1] http://bit.ly/1aNuWca -- Web Design sketch prior to Web manisfestation
[2] 
http://bit.ly/evidence-that-the-world-wide-web-was-based-on-linked-data-from-inception 
-- Web Design sketch following Web manifestation.
[3] http://www.w3.org/2005/Talks/1110-iswc-tbl/#(7) -- HTTP URI based 
Names in a single slide
>
> cheers,
>
> dret.
>


-- 
Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this