W3C home > Mailing lists > Public > public-lod@w3.org > November 2011

Re: Combining Linked Data HTTP URIs and HTML5 WebSocket URIs

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sat, 19 Nov 2011 13:11:06 -0500
Message-ID: <4EC7F13A.7010302@openlinksw.com>
To: public-lod@w3.org
On 11/18/11 9:22 PM, richard.hancock@3kbo.com wrote:
> Hi All,
> I have a couple of questions re combining Linked Data HTTP URIs and HTML5
> WebSocket URIs.
> There are a couple of applications that I would like to build which have a
> mix of static and dynamic data. For the dynamic data I am planning to use
> HTML5 WebSockets [1][2] which uses the ws:// and wss:// prefixes.
> As an example I want to report the runtime status of the servers in a
> Weblogic cluster.  Using JMX monitoring to get the actual status I could
> use
> ws://www.3kbo.com:9090/servers/1/status
> ws://www.3kbo.com:9090/servers/2/status
> to display the current status of each server in my monitoring app.
> I am also planning to display LinkedData[3] about each server using the URIs
> <http://www.3kbo.com:8080/servers/1>  and
> <http://www.3kbo.com:8080/servers/2>.
> It would seem logical to use owl:sameAs to combine the HTTP URIs and the
> Websocket URIs to assert that they are referring to the same individuals,
> but is that valid?


You have to clearly distinguish resource (object / entity) Name from its 
data access Address. Then you have to remember that the name choose has 
to resolve to an actual resource (actual data in EAV/SPO based graph 
pictorial form).

Bearing in mind the above, I can't tell which of the URIs are Names or 
> I.e. can the following two statements be made in OWL?
> <http://www.3kbo.com:8080/servers/1>  owl:sameAs
> <ws://www.3kbo.com:9090/servers/1>  .
> <http://www.3kbo.com:8080/servers/2>  owl:sameAs
> <ws://www.3kbo.com:9090/servers/2>  .

Fine if the URIs above are Names i.e., not Addresses.
> Does the forth LinkedData[3] principal
> "4. Include links to other URIs. so that they can discover more things."
> implicitly include links to Websocket URIs ?

That's a function of using de-referencable URIs as Names. Put 
differently, Names that provide indirect access to data via indirection. 
HTTP URIs are a cost effective route to the aforementioned indirection.

> Cheers,
> Richard Hancock
> 1. http://en.wikipedia.org/wiki/WebSockets
> 2. http://dev.w3.org/html5/websockets/
> 3. http://www.w3.org/wiki/LinkedData



Kingsley Idehen	
President&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Saturday, 19 November 2011 18:11:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:17 UTC