I think we could probably provide a more straightforward REST (rather than -ish) interface which does its work using SPARQL but hides the complexity from the app/widget developer. Maybe a handful of parametrized SPARQL queries behind the scenes would be enough.
On Sun, Jun 1, 2014 at 12:51 AM, Simon Spero <[email protected]> wrote: > On Sat, May 31, 2014 at 12:29 PM, Gerald de Jong <[email protected]> > wrote: > >> I'm wondering if the SIG has some kind of CRM API available so that >> software can easily retrieve the model and its component parts >> individually. What I'm thinking of is a REST interface which makes it easy >> to build CRM browser software in Javascript, exposing scope notes and any >> other materials (video fragments of Stephen Stead?). >> > > The output of X3ML is generally RDF, right? > > If the data are exposed via a SPARQL endpoint, then that will provide a > REST-*ish* API. > > GET /sparql/?query=*<sparql query>* HTTP/1.1 > Host: *<hostname>* > Accept: application/sparql-results+json > > > You can also use POST for longer queries (hence the "-ish") > > see: > > SPARQL 1.1 Protocol Recommendation: > http://www.w3.org/TR/sparql11-protocol/ > > SPARQL 1.1 JSON Results Format: > http://www.w3.org/TR/sparql11-results-json/ > > SPARQL 1.1 Query Language: > http://www.w3.org/TR/sparql11-query/ > > Simon > -- Delving BV, Vasteland 8, Rotterdam http://www.delving.eu http://twitter.com/fluxe skype: beautifulcode +31629339805
