Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Lewis, I tried: OntModel m = ModelFactory.createOntologyModel(); m.read("http://sweetontology.net/sweetAll;, null, "TTL"); System.out.println("DONE"); System.exit(0); and it worked for me (3.6.0, 3.7.0-dev; apache-jena-libs) Have you got any local copies

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Hi Lewis, On 14/03/18 06:13, Lewis John McGibbney wrote: Hi Dave, Coming back to this to address some thing I missed before On 2018/03/07 08:57:47, Dave Reynolds wrote: OntModels use a somewhat older stack of tools (FileManager) which guesses the language based on

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Hi Dave, Coming back to this to address some thing I missed before On 2018/03/07 08:57:47, Dave Reynolds wrote: > OntModels use a somewhat older stack of tools (FileManager) which > guesses the language based on the suffix, with a default of RDF/XML, and > then

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Thanks Andy, OK I've added this dependency to the project and te result is just the same. I am going to try Dave's suggestion. Thanks Lewis On 2018/03/13 18:51:06, Andy Seaborne wrote: > > > On 13/03/18 18:44, Lewis John McGibbney wrote: > > Hi Andy, > > This is correct. > >

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

On 13/03/18 18:44, Lewis John McGibbney wrote: Hi Andy, This is correct. Do you suggest I augment the classpath? Thank you Lewis Yes: org.apache.jena apache-jena-libs pom X.Y.Z On 2018/03/07 17:01:43, Andy Seaborne wrote: On 07/03/18 10:59, Andy

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Hi Andy, This is correct. Do you suggest I augment the classpath? Thank you Lewis On 2018/03/07 17:01:43, Andy Seaborne wrote: > > > On 07/03/18 10:59, Andy Seaborne wrote: > > Lewis - which version? Do yo have all the apache-jena-libs jars on the > > classpath?  RIOT

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Hi Andy, This is Jena 3.6.0. Lewis On 2018/03/07 10:59:42, Andy Seaborne wrote: > Lewis - which version? Do yo have all the apache-jena-libs jars on the > classpath? RIOT rewirers Jena model reading. > > Also, there was an issue around redirect and remapping but it's fixed.

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Hi Dave, Thank you for the response, On 2018/03/07 08:57:47, Dave Reynolds wrote: > I can't tell from the trace whether you are mapping the import URLs to > local files or are loading directly from the URL. If loading from local > files then you really need suffixes

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

On 07/03/18 10:59, Andy Seaborne wrote: Lewis - which version? Do yo have all the apache-jena-libs jars on the classpath?  RIOT rewirers Jena model reading. It looks like you only have jena-core of some version on the classpath. Also, there was an issue around redirect and remapping but

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

Lewis - which version? Do yo have all the apache-jena-libs jars on the classpath? RIOT rewirers Jena model reading. Also, there was an issue around redirect and remapping but it's fixed. Andy On 07/03/18 08:57, Dave Reynolds wrote: I can't tell from the trace whether you are mapping

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

I can't tell from the trace whether you are mapping the import URLs to local files or are loading directly from the URL. If loading from local files then you really need suffixes on those. I'll assume you are loading from the URL ... OntModels use a somewhat older stack of tools (FileManager)

Re: OntModel.read parsing non-suffixed TTL as RDF/XML

read parsing non-suffixed TTL as RDF/XML Hi Folks, Over on the SWEET ontology suite [0] we recently changed out canonical serialization to TTL. Additionally however, we removed all file suffixes from the resources themselves, therefore although the following resource [1] is serialized as TTL, you would n

OntModel.read parsing non-suffixed TTL as RDF/XML

Hi Folks, Over on the SWEET ontology suite [0] we recently changed out canonical serialization to TTL. Additionally however, we removed all file suffixes from the resources themselves, therefore although the following resource [1] is serialized as TTL, you would never know unless you looked at it