- From: Erik Wilde <dret@berkeley.edu>
- Date: Thu, 22 Apr 2010 11:53:51 -0700
- To: Cory Casanave <cory-c@modeldriven.com>, public-egov-ig@w3.org
- CC: Richard Cyganiak <richard@cyganiak.de>
hello. > [cbc] All I can tell you is we and many others use REST interfaces to > RDF graphs and it works very well (including SPARQL at the same > endpoint) - REST & RDF are orthogonal just like XML and REST are > orthogonal. yes, REST and RDF are orthogonal. using RDF/semweb does not solve the problems that REST solves, such as telling me where to go if i want to do things, and what i can do there. (this is where quite a bit of "discovery" research work has been done in the semweb community.) it also is the reason why i was pointing out that we should look at services, too, because regardless of whether egov data is exposed as XML or JSON or RDF or CSV, it will be important to know what services you can use, i.e. where to go, and how to interact with those services, such as how you can for example update or annotate data. and in the same way as you don't give the world SQL access to your relational data, my guess is that you won't give the world SPARQL access to your RDF data; the main reasons being that you want to be able to enforce constraints, exercise access control, control optimized access paths, and you want the services to be independent of implementation details. cheers, dret.
Received on Thursday, 22 April 2010 18:54:51 UTC