Hi Elli! 27.06.2013 21:38, Elli Schwarz kirjoitti:
While I understand that RDF/XML-ABBREV is more human readable, there's a big price to pay in efficiency, at least for my data. In my case, I'm accessing my Fuseki endpoint via datasetAccessor.getModel(), and as far as I know, there's no way for me to tell Fuseki through this API that I want the data to be serialized as N-TRIPLES (since it's just going to be loaded in a Jena model anyway and not read by a human). Is there a way I can control how Fuseki serializes by default? And why was the default serialization format changed to RDF/XML-ABBREV - is anyone really using RDF/XML anymore as a human-readable format anyway? ;-)
Fuseki respects the Accept header in the SPARQL HTTP Graph Store protocol. So if you're able to inject an Accept header into the request, you can tell Fuseki to output e.g. N-Triples.
I have Fuseki behind a Varnish HTTP proxy and I've set it up so that e.g. /mydataset/data.ttl will be rerouted by Varnish into /mydataset/data with the Accept header set to request Turtle. If you can put some HTTP proxy in front of Fuseki, you could do the same.
I think I've seen some SPARQL HTTP Graph Store implementation support a custom URL parameter that can be used to set the MIME type instead of using an Accept header, but I can't recall which one. If Fuseki supported something like that, it would be easy to request a particular serialization format just by using a special URL.
Hope this helps -Osma -- Osma Suominen | [email protected] | +358 40 5255 882 Aalto University, Department of Media Technology, Semantic Computing Research Group Room 2541, Otaniementie 17, Espoo, Finland; P.O. Box 15500, FI-00076 Aalto, Finland
