- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Thu, 16 Apr 2015 17:54:56 -0400
- To: public-hydra@w3.org
- Message-ID: <55302FB0.8060808@openlinksw.com>
On 4/16/15 4:02 PM, Markus Lanthaler wrote: >> and more importantly, in >> >order to*link* to API documentation, wouldn't there be something in the >> >IANA registry that already would work well enough? maybe "describedby", >> >if that's specific enough for where you want to embed the link? the >> >original question wasn't about the link relation but about the media >> >type, which is a different thing. > No, IMO there isn't anything specific enough in the IANA registry. Correct! And that's because on a good day only an English Speaker can read the prose exposed in those documents. The Web is all about leveraging Relations (what @rel is about) as a means of encoding and decoding information, systematically. The aforementioned endeavor is about relations that are comprehensible to both humans (not just English Speaking variant) and machines (where data representation isn't confined to a specific notation). We really need to get past this problem of REST, media types, and relations semantics. If REST really stops at media types, its utterly flawed. The good news is that REST isn't about media types, that isn't where it stops. It's actually about relations intermingled with hypermedia [webby relations, webby structured data representation, and blogic or webby locic]. The very thing that RDF based Linked Open Data is fundamentally about. RDF isn't a format. It is a Language. -- 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
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Thursday, 16 April 2015 21:55:18 UTC