Re: Fuseki 2: Serving RDF/XML over HTTP

2019-01-15 Thread Kevin Dreßler
Thanks Andy, that helped a lot indeed! Best, Kevin > On 14. Jan 2019, at 17:13, Andy Seaborne wrote: > > The problem is that you are asking the dataset for RDF/XML. > > Datasets include the named graphs. It needs TriG or N-Quads. > > So you ask for RDF/XML, and content negotiation says

Re: Fuseki 2: Serving RDF/XML over HTTP

2019-01-14 Thread Andy Seaborne
The problem is that you are asking the dataset for RDF/XML. Datasets include the named graphs. It needs TriG or N-Quads. So you ask for RDF/XML, and content negotiation says "can't - here's nmy default (which is N-Quads) and then the code ignores the Content-type and forces RDF/XML. It then

Re: Fuseki 2: Serving RDF/XML over HTTP

2019-01-14 Thread Kevin Dreßler
Sorry for double posting but I might add that with this code I get the following Exception: java.lang.RuntimeException: org.apache.jena.riot.RiotException: [line: 1, col: 7 ] Element or attribute do not match QName production: QName::=(NCName':')?NCName. at

Re: Fuseki 2: Serving RDF/XML over HTTP

2019-01-14 Thread ajs6f
Please show the code you are actually using to make requests. ajs6f > On Jan 14, 2019, at 9:06 AM, Kevin Dreßler wrote: > > Hello, > > for unit testing I need to mock up a HTTP server delivering RDF/XML per > content negotiation (Accept: application/rdf+xml). For a HTTP request on >

Fuseki 2: Serving RDF/XML over HTTP

2019-01-14 Thread Kevin Dreßler
Hello, for unit testing I need to mock up a HTTP server delivering RDF/XML per content negotiation (Accept: application/rdf+xml). For a HTTP request on http://myEndpoint:myPort/test with the "Accept" header set as above it should output DESCRIBE(http://myEndpoint:myPort/test) as RDF/XML, so