> On Sep 1, 2014, at 00:03, John Walker <[email protected]> wrote: > > Snapper seems to fit the bill so will see if I can get it talking to the > graph store.
Given a SPARQL 1.1 graph store protocol endpoint that supports Turtle and sets appropriate CORS headers (or by using a CORS proxy) you should get pretty far, and the editor does support Basic authentication. That said, different functionalities in Snapper do require different types of endpoints to be available, due to their different inherent limitations. Basically, the spread is as follows: SPARQL graph store protocol endpoint: * loading/replacing by graph, adding triples SPARQL update endpoint: * deleting/replacing individual resources SPARQL query endpoint: * label autocompletion & label display * listing graphs in the graph store * single resource loading (but Snapper can also load resources with simple GETs) I’ll try to update https://github.com/jiemakel/snapper with this info as well as some additional usage information when I get the chance. (and do file issues if you encounter any problems or think of improvements) - Eetu -- Eetu Mäkelä, Researcher, D.Sc. - http://www.seco.tkk.fi/u/jiemakel/ Semantic Computing Research Group - http://www.seco.tkk.fi/ Department of Media Technology - http://www.media.tkk.fi/ Aalto University School of Science - http://sci.aalto.fi/
