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

SPARQL best practice for egov?

From: Cory Casanave <cory-c@modeldriven.com>
Date: Fri, 23 Apr 2010 09:16:53 -0400
Message-ID: <4F65F8D37DEBFC459F5A7228E5052044A03DFC@DATCENTRALSRV.datcentral.local>
To: "public-egov-ig IG" <public-egov-ig@w3.org>
We had some discussion about the relationship between a RDF URL and a
SPARQL endpoint as well as other resources such as graph metadata.  The
conclusion seemed to be that there are various vocabularies where a
triple in the graph could point to the endpoint that points to metadata.
The issue with this is that you would then have to get the entire graph
to get this one triple - which kind of missed the point if you have a
large dataset that you want to query instead of download.


I can imagine two conventions that could help solve this: 

1) That every resource should respond to a SPARQL endpoint.  This would
then allow you to query that one resource directly to subset the data
and/or to get the triple that points to metadata.

2) That a standard manipulation is done on a URI to get metadata about
resources, which would include the query point.  For example:
http://www.example.com/rdf/people.rfd#cory could have metadata at
http://www.example.com/rdf/metadata.rdf.  There are some existing
solutions that use this approach.


Can we set a "best practice" for open government data?  My preference
would be the first.  Thoughts?


Received on Friday, 23 April 2010 13:17:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:43 UTC