Comments for linked, not bound

Comment on Self-Descriptive Hypermedia by zazi

zazi — Thu, 10 Feb 2011 16:41:00 +0000

I think that cries for the application of a standardized description format whose instantiations can be serialized into appropriated representation formats that are consumable by the interacting clients (instead of creating all the time domain-specific media types that describe domain models).
So, I would suggest to use RDF Model as a basis and utilize existing Semantic Web knowledge representation languages and specific ontologies, that are built on top of that knowledge representation structure, for creating such domain-specific description. If you won’t find an appropriated Semantic Web ontology to describe (parts of) your domain model, you can create a new one. However, it is generally better to utilize existing Semantic Web ontologies to establish easier a shared understanding.

What do you think about that way?

Comment on Self-Descriptive Hypermedia by Client-driven APIs | Loosely Connected

Client-driven APIs | Loosely Connected — Thu, 10 Feb 2011 01:38:11 +0000

[...] http://linkednotbound.net/2010/07/19/self-descriptive-hypermedia/ [...]

Comment on Hypermedia is an Event Filter by This Week in #REST – Volume 33 (Jan 29 2011 – Feb 8 2011) « This week in REST

Wed, 09 Feb 2011 13:46:51 +0000

[...] Hypermedia is an Event Filter – “In this post, I will re-examine these alternatives, extending the analysis to the information flowing from client to server and the protocols used to exchange information. By doing so, I hope to clarify the advantages provided by REST for input event processing.” (by Andrew Wahbe) [...]

Comment on Hypermedia is an Event Filter by Scott Banwart's Blog » Blog Archive » Distributed Weekly 88

Scott Banwart's Blog » Blog Archive » Distributed Weekly 88 — Fri, 04 Feb 2011 14:02:26 +0000

[...] Hypermedia is an Event Filter [...]

Comment on Hypermedia is an Event Filter by Stu

Stu — Fri, 04 Feb 2011 05:39:56 +0000

(I wish I could say more, but it probably would be jibberishy)

Comment on Hypermedia is an Event Filter by Tweets that mention Hypermedia is an Event Filter « linked, not bound -- Topsy.com

Mon, 31 Jan 2011 03:40:57 +0000

[...] This post was mentioned on Twitter by Glenn Block and Darrel Miller, Andrew Wahbe. Andrew Wahbe said: Blogged: Hypermedia is an Event Filter http://wp.me/pOny4-1u [...]

Comment on Web Linking by This Week in #REST – Volume 30 (Nov 21 2010 – Dec 12 2010) « This week in REST

Mon, 13 Dec 2010 10:13:18 +0000

[...] Web Linking – “A couple months ago, Mark Nottingham’s Web Linking internet draft made its way to RFC status. This is a pretty significant specification for the web. It does three key things: It provides a generic definition of a “link”; It establishes a registry for link relations; and It defines the HTTP link header.” (by Andrew Wahbe) [...]

Comment on Web Linking by Scott Banwart's Blog » Blog Archive » Distributed Weekly 79

Scott Banwart's Blog » Blog Archive » Distributed Weekly 79 — Fri, 03 Dec 2010 14:29:04 +0000

[...] Web Linking [...]

Comment on Web Linking by Andrew Wahbe

Andrew Wahbe — Wed, 01 Dec 2010 18:16:24 +0000

Oops yes — I agree on the second example. I forgot to change the content type in the second example from “application/json” to my fictitious “application/node” media type. Will update.

Your comment about “presenting the link to a human” is touching on the “data-guided controls” issue I talked about at the end. More on that to follow.

Comment on Web Linking by Nathan

Nathan — Wed, 01 Dec 2010 17:48:32 +0000

The first examples contains 3 URIs, if they were presented to a human in such a way that they were actionable, then those would be called hyperlinks, untyped ones.

The second example is exactly the same, because application/json doesn’t have any hypermedia semantics, the terms href and rel in that JSON have no meaning at all. It’s no good using two terms from another mediatype and saying that they have the same meaning else where, they don’t.

The third example has one fully typed link, the one in the Link header. And that’s the only example with any kind of link in it.

Best,

Nathan