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

[public-egov-ig] <none>

From: Gannon Dick <gannon_dick@yahoo.com>
Date: Fri, 23 Apr 2010 14:50:04 -0700 (PDT)
Message-ID: <868558.28985.qm@web112605.mail.gq1.yahoo.com>
To: public-egov-ig IG <public-egov-ig@w3.org>
Cc: Cory Casanave <cory-c@modeldriven.com>
+1, Cory (for all the good it might do you).

http://www.rustprivacy.org/meta/citation/parseCitation.rdf (with XSD Validation) is a thinly disguised solution #2.  I simply do not believe it possible for Government work to address granularity and existence (discovery) as two separate issues although the separation may be just dandy for web surfing - on a serious, sophisticated level, of course ;)

--Gannon 


====================
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 21:50:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 April 2010 21:50:39 GMT