On 05/04/12 19:09, Paolo Castagna wrote:
Hi Philip,
yep, documentation can always be improved.

In the meantime, you can look at DEF.java [1] in Fuseki and WebContent.java [2]
in ARQ source code. You can try those and build a list of supported content
types yourself.

I know, I know... but this will get you going. :-)

Share your findings, others will benefit.

Thanks,
Paolo

  [1]
http://svn.apache.org/repos/asf/incubator/jena/Jena2/Fuseki/tags/jena-fuseki-0.2.1-incubating/src/main/java/org/apache/jena/fuseki/DEF.java
  [2]
http://svn.apache.org/repos/asf/incubator/jena/Jena2/ARQ/tags/jena-arq-2.9.0-incubating/src/main/java/org/openjena/riot/WebContent.java

Philip Fennell wrote:
Hello,

I've been working recently with Fuseki (0.2.1) and I'm testing some code that 
talks to Fuseki using the SPARQL 1.1 Graph Store HTTP Protocol. Through trial 
and error I've found that Fuseki will return graph the following graph 
representations when requested, appropriately, via the Accept header:

RDF/XML application/rdf+xml
N-Triples       text/plain

and depending on what it makes of your Accept header it may return either of 
these.

Are these the only two representations that Fuseki supports?

Turtle, text/turtle.

I've looked through the documentation but haven't yet found a definitive list 
of the supported media-types.

I know I can load graphs in the above formats and Turtle too but I've not been 
able to coerce Fuseki into returning a graph as Turtle.

text/turtle should work.

And RDF/JSON (i.e. the Talis format) in development system.

You can send a variety of choices and give preferences with q=

The SOH tools send:

Accept: application/rdf+xml;q=0.9, text/turtle, */*;q=0.1

        Andy



Regards

Philip




Reply via email to