Re: LOD

Thank you, Cory!  I will read in full this weekend.   Paragraph two last sentence subject matter nuclear reactors and OMB procedure has a spelling error:  "it's self" should be "itself".

Cheers,
 
Michael A. Norton
 




________________________________
From: Cory Casanave <cory-c@modeldriven.com>
To: Mike Norton <xsideofparadise@yahoo.com>; Bobbin Teegarden <teegs@earthlink.net>; public-egov-ig@w3.org
Sent: Fri, June 4, 2010 6:17:20 PM
Subject: RE: Potential project: Supporting the Linked Data Consumer

 
Linked Open Data.
http://www.w3.org/egov/wiki/Linked_Data
 
 

________________________________
 
From:Mike Norton [mailto:xsideofparadise@yahoo.com] 
Sent: Friday, June 04, 2010 6:53
PM
To: Bobbin Teegarden; Cory
Casanave; public-egov-ig@w3.org
Subject: Re: Potential project:
Supporting the Linked Data Consumer
 
I feel so out of the loop.  What does LOD stand for? 
Linked Ontological Data?
 
Michael A. Norton
 
 
 

________________________________
 
From:Bobbin
Teegarden <teegs@earthlink.net>
To: Cory Casanave
<cory-c@modeldriven.com>; public-egov-ig@w3.org
Sent: Fri, June 4, 2010 12:28:59
PM
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