W3C home > Mailing lists > Public > public-egov-ig@w3.org > June 2010

RE: Potential project: Supporting the Linked Data Consumer

From: Cory Casanave <cory-c@modeldriven.com>
Date: Mon, 7 Jun 2010 15:16:52 -0400
Message-ID: <4F65F8D37DEBFC459F5A7228E5052044AA7C52@DATCENTRALSRV.datcentral.local>
To: "Bobbin Teegarden" <teegs@earthlink.net>, <public-egov-ig@w3.org>
Bobbim,

Hi - I didn't'[t realize you were hanging out on this list!  Thanks for
the support.

 

As for read/write - I had thought that may be too much to suggest at
first, but as a vision it is absolutely something we should consider.  I
added it to the write-up.

 

As for the browser add-in.  As we consider the implementation options we
should think about browser/server tradeoffs.  I also thought of this
more as a browser capability but as I have understood the LOD
environment and challenges more I am thinking we may want it to be a
server based capability with less requirement for special stuff in the
browser.  This is for a few reasons:

*	The pain of browser incompatibilities, particularly with
plugins.  Tabulator suffers from its firefox-only foundation.
*	The need to retain "context" across sources and display
information in a way that is sensitive to the users role and of having
associated libraries of display widgets bound to the users role
*	How to access the data in a consistent way?

	*	The need to access large data sources by query
	*	The fact that many data sources don't support query 
	*	The difficulty in federating queries
	*	The various ways of binding data and query sources

*	Where business rules and even executable resources would reside,
and where the resulting data would go.

 

So, I think a "LOD Node" will have to be able to buffer some data and
federate others to provide a kind of virtual query point.  This then
needs to be bound to display forms based on user context.  This all
seems like more than could (or should) ever be done in the browser.  Of
course, some aspects will want to be browser based but my thinking has
moved much more to the server side.  

 

Of course - there is more than one way to skin this cat.

-Cory

 

Thanks,

-Cory

________________________________

From: Bobbin Teegarden [mailto:teegs@earthlink.net] 
Sent: Friday, June 04, 2010 3:29 PM
To: Cory Casanave; public-egov-ig@w3.org
Subject: RE: Potential project: Supporting the Linked Data Consumer 

 

As an industry consultant and prospective consumer of LOD, I applaud the
idea of an LOD 'Front Page' and this first pass addressing consumer
needs.  

Here is some thoughts of how it might be easy to implement (sooner is
good), integrate into what consumers already do, and take advantage of
the wonderful visual side of linked data:

First pass, could you make it a browser add-in, that says 'oh, this is
RDF/OWL data' and offer a display option as the visual graph, in context
(full graph, or centered segment - almost like a network management map
that scopes around the 'big' map -- sort of an OpenView for LOD);

With either pass-over or right click, tell the internal format, and
entry points - URI to 'front page' or domain/entity, SPARQL endpoints
and API interfaces, other notes;

Drill-down ability by double click (as now) on any map entity, and have
another graph display of the 'sub-domain' (and down as many levels as
the domain design);

Ability to 'log in' to a domain with use privs for CRUD on
entities/objects (this may be too hard, without more standardization
around authorization, but a desire in the long run.

 The more familiar you make it, in KISS mode, the faster the uptake on
real usage.  It might not be 'optimal', but almost immediately useable.
Then we can get to some of the harder problems, like using multiple
inconsistent overlapping domain data, transforms to and from legacy
systems, etc.

Just a wishlist  from the realside, hope this contributes.  And thanks
for thinking of how we take advantage of the emergent LOD cloud, how
rich our world is becoming.

 

Bobbin Teegarden

CTO/Chief Architect, OntoAge

Chief Scientist/Consultant, LVI

WA:  425.378.0131

cell: 206.979.0196

CA: 650.851.8273

teegs@earthlink.net

 

From: public-egov-ig-request@w3.org
[mailto:public-egov-ig-request@w3.org] On Behalf Of Cory Casanave
Sent: Friday, June 04, 2010 11:34 AM
To: public-egov-ig@w3.org
Subject: Potential project: Supporting the Linked Data Consumer 

 

eGov IG,

On the LD-Demo call today I suggested we should focus some effort on the
consumer side of linked data.  As requested I have put together a rough
draft project outline to expand the idea, please take a look here:

 

http://www.w3.org/egov/wiki/Supporting_the_Linked_Data_Consumer

 

Your comments are very welcome as well as suggestions as to existing
resources that can help satisfy the needs expressed.

 

Regards,

Cory Casanave

 

 

 
Received on Monday, 7 June 2010 19:17:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 June 2010 19:17:20 GMT