Closed azaroth42 closed 7 years ago
On 29 Sep 2016, at 17:51, Rob Sanderson notifications@github.com wrote:
Going to https://www.w3.org/ns/oa/ https://www.w3.org/ns/oa/ presents an HTML list of the available serializations of the vocabulary, as discussed previously.
However currently clicking on the links does not resolve to the serializations, instead it goes back to the same HTML page.
Seems like a configuration issue of the server?
The right URI-s for the namespace files (at this moment) are
https:/www.w3.org/ns/oa http://www.w3.org/ns/oa.{html,ttl,jsonld,owl,rdf}
and there is an oa.var file:
URI: oa
URI: oa.html
Content-Type: text/html
URI: oa.rdf
Content-Type: application/rdf+xml; qs=0.4
URI: oa.ttl
Content-Type: text/turtle; qs=0.6
URI: oa.jsonld
Content-Type: application/ld+json; qs=0.5
URI: oa.json
Content-Type: application/json; qs=0.4
to ensure conneg.
In other words, the HTML file seems to be the problem child:-(
Indeed, content negotiation works
OWLOntologyManager manager = OWLManager.createOWLOntologyManager();
URL OAURL = new URL("https://www.w3.org/ns/owl.ttl");
InputStream oais = OAURL.openStream();
OWLOntology ontologyOA = manager.loadOntologyFromOntologyDocument(oais);
Before, I used the following code receiving the following error.
OWLOntologyManager manager = OWLManager.createOWLOntologyManager();
URL OAURL = new URL("https://www.w3.org/ns/oa/index.owl");
InputStream oais = OAURL.openStream();
OWLOntology ontologyOA = manager.loadOntologyFromOntologyDocument(oais);
org.semanticweb.owlapi.io.UnparsableOntologyException: Problem parsing inputstream:ontology2
Could not parse ontology. Either a suitable parser could not be found, or parsing failed. See parser logs below for explanation.
The following parsers were tried:
1) org.semanticweb.owlapi.rdf.rdfxml.parser.RDFXMLParser@61edc883
2) org.semanticweb.owlapi.owlxml.parser.OWLXMLParser@6928f576
3) org.semanticweb.owlapi.functional.parser.OWLFunctionalSyntaxOWLParser@660e9100
4) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.RioTurtleDocumentFormatFactory@95fd655c
5) org.semanticweb.owlapi.manchestersyntax.parser.ManchesterOWLSyntaxOntologyParser@3574e198
6) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.NQuadsDocumentFormatFactory@6f9c39ad
7) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.TrigDocumentFormatFactory@27e81c
8) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.RDFJsonDocumentFormatFactory@cd748dc3
9) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.NTriplesDocumentFormatFactory@937ecd36
10) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.BinaryRDFDocumentFormatFactory@3bf24493
11) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.RDFJsonLDDocumentFormatFactory@dcacc47d
12) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.RioRDFXMLDocumentFormatFactory@69b9a3bc
13) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.N3DocumentFormatFactory@9a5
14) org.semanticweb.owlapi.rdf.turtle.parser.TurtleOntologyParser@4c5204af
15) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.TrixDocumentFormatFactory@27e82d
16) org.semanticweb.owlapi.oboformat.OBOFormatOWLAPIParser@79c3f01f
17) org.semanticweb.owlapi.krss2.parser.KRSS2OWLParser@678040b3
18) org.semanticweb.owlapi.rio.RioParserImpl : org.semanticweb.owlapi.formats.RDFaDocumentFormatFactory@264e8d
Thanks for pointing out the url http://www.w3.org/ns/oa.{html,ttl,jsonld,owl,rdf}
That must be changed, to be updated
Going to https://www.w3.org/ns/oa/ presents an HTML list of the available serializations of the vocabulary, as discussed previously.
However currently clicking on the links does not resolve to the serializations, instead it goes back to the same HTML page.
Seems like a configuration issue of the server?