Re: Setting (strict) error handler before before reading Model (Jena 2.11.0)

Is it possible to let the Model parse silently and afterwards somehow retrieve org.apache.jena.iri.Violation instances from the ErrorHandler? Currently I'm implementing a custom ErrorHandler that would collect violations instead of logging them. But ErrorHandler only provides String message, long

Re: Concurrent access to a shared (Ont)Model

Is clonedModel.add(ontModel) the best way to clone a model though? Because after that ontModel.size() and clonedModel.size() seem to differ sometimes, e.g. 4723 vs 4729. On Fri, Jul 22, 2016 at 9:24 AM, Dave Reynolds wrote: > On 21/07/16 22:26, Martynas Jusevičius

Re: OntModel imports not loaded (2.11.0 behavior broken in 3.0.1)

OK sorry, I meant that the first one imports the second one: gps: imports gp:. The imports are not cyclic. Location mapping is not part of the problem, I don't know why I attached it :) I guess you can just remove all the external imports (sp:, spin:, foaf:, sioc:) from the ontologies so they're

Re: Can not write to the file

On 22/07/16 13:17, kumar rohit wrote: I dont know if attaching screen shot is allowed or not, but kindly if you can check it. You can see what we all see of your emails by looking in the archives:

Re: Adding multiple individuals

On 21/07/16 17:55, neha gupta wrote: Thank you Admin for adding me. I am Neha and in the final semester of my Bachelor degree. My project is in Semantic web and Jena, unfortunately. err I have read a lot about Jena and knows how to create classes and individuals. I know how to create single

Re: OntModel imports not loaded (2.11.0 behavior broken in 3.0.1)

So "import each other" is not a cycle? and does the location-mapping.n3 make a difference because I though the issue was the overridden model.read was not being called which is not related to location mapping. Andy On 22/07/16 21:10, Martynas Jusevičius wrote: No this is about

Re: OntModel imports not loaded (2.11.0 behavior broken in 3.0.1)

No this is about getOntology() not calling loadImports() in 3.0.1, which I now need to call myself. And OntModel is retrieved multiple times. I see there is Set m_imported in OntModelImpl -- could be exposed as OntModel.getImportedURIs() for example. The concurrency thing is another thread. I

Re: Web UI of Fuseki doesn't start

Dear Stian, Thank you for your reaction. I have started Fuseki from the command line with: java -jar /var/www/fuseki/fuseki-server.jar --update --mem /ds as usual. Any other time it worked. I haven't tried Fuseki 2.4.0 so far. Best Regards, Sandor Am 21.07.2016 um 14:27 schrieb Stian

Re: OntModel imports not loaded (2.11.0 behavior broken in 3.0.1)

Martynas, This is the concurrency problem? Not JENA-1210 (imports) which happens with non-cyclic imports? Could you put a complete, minimal example for this please? It really does help to have them so that someone can know they are working on the problem reported. Otherwise, they spend a

Re: OntModel imports not loaded (2.11.0 behavior broken in 3.0.1)

Is there a way to check whether imports already have been load for an OntModel? As to call loadImports() only once and avoid calling it with each OntModel access. On Thu, Jul 14, 2016 at 2:48 PM, Andy Seaborne wrote: > On 13/07/16 22:33, Martynas Jusevičius wrote: >> >> Hey, >>

Re: Default RDF/XML writer changed between 2.11.0 and 3.0.1?

Why was the default changed though? Because we used to get questions as to why the output wasn't pretty. The change wasn't at 3.0.0. It came when RIOT wired itself into model.write which was before that. Andy On 22/07/16 15:42, Martynas Jusevičius wrote: Our code depends on Jena

Re: OntModel imports not loaded (2.11.0 behavior broken in 3.0.1)

These are 2 ontologies that import each other (gps: imports gp:): https://github.com/AtomGraph/Processor/blob/master/src/main/resources/org/graphity/processor/gps.ttl https://github.com/AtomGraph/Processor/blob/master/src/main/resources/org/graphity/processor/gp.ttl Here is the location mapping

Re: Default RDF/XML writer changed between 2.11.0 and 3.0.1?

Our code depends on Jena indirectly through SPIN API, the latest release of which (2.0.0) uses Jena 3.0.1: http://topbraid.org/spin/api/ On Fri, 22 Jul 2016 at 15:04, Rob Vesse wrote: > I don’t know why the default was changed but please bear in mind that > you’re not just

Re: Default RDF/XML writer changed between 2.11.0 and 3.0.1?

I don’t know why the default was changed but please bear in mind that you’re not just going from 2.x to 3.x but are jumping from 2.11.0 which was released September 2013 to 3.0.1 which was released December 2015 and there were six other releases between those two. Lots of things changed in that

Re: Can not write to the file

I dont know if attaching screen shot is allowed or not, but kindly if you can check it. After running the code , it has added the garbage classes to the file. User class is also there as I have created it, but again it has disappeared my classes in ontology. *Note:* I have added new class in

Base uri vs Ontology uri

What is base URI and how it differs with the actual ontology URI? Both are mandatory inside Jena while dealing with ontologies?

Re: Can not write to the file

On 22/07/16 10:44, kumar rohit wrote: Yes because the model.write() works but the FileWriter does not. I also tried something like this to append data but failed: FileOutputStream f1=new FileOutputStream(file, *true*); Any solution please you suggest to write it to the same file I have read

Re: Can not write to the file

Yes because the model.write() works but the FileWriter does not. I also tried something like this to append data but failed: FileOutputStream f1=new FileOutputStream(file, *true*); Any solution please you suggest to write it to the same file I have read from? On Fri, Jul 22, 2016 at 2:22 AM,

Re: Can not write to the file

On 22/07/16 10:22, Lorenz B. wrote: Hello Dave, I think the problem is that he writes to another file - and I guess this one already contains some data. Of course the write method cannot append data, but just overwrites the file. Am I right? Anything else would sound like some magic. Sure.

Re: Default RDF/XML writer changed between 2.11.0 and 3.0.1?

RDFWriterRegistry.register(Lang.RDFXML, RDFFormat.RDFXML_PLAIN) did the trick. Why was the default changed though? I think it should be mentioned in the 3.x migration guide: https://jena.apache.org/documentation/migrate_jena2_jena3.html On Fri, Jul 22, 2016 at 10:22 AM, Andy Seaborne

Re: Can not write to the file

Hello Dave, I think the problem is that he writes to another file - and I guess this one already contains some data. Of course the write method cannot append data, but just overwrites the file. Am I right? Anything else would sound like some magic. Otherwise, to append data, one would have to

Re: Can not write to the file

On 22/07/16 09:58, kumar rohit wrote: The main() pass the required file and then just the GUI loads because we have to deal with a text field where user enter his name and we will create individual of that name. The main purpose of this code is to create individual (after user enter the name)

Re: Can not write to the file

The main() pass the required file and then just the GUI loads because we have to deal with a text field where user enter his name and we will create individual of that name. The main purpose of this code is to create individual (after user enter the name) and store it locally in a file *(either a

Re: Can not write to the file

1.) This is not a minimal running example! that means, nobody can test it without some (in your case too much) effort to get it running. 2.) w.r.t. 1), look at your main() method, it reads a file and then? 2.) Please tell us exactly WHAT does not work and WHAT you expect. 3.) The OntModel object

Re: Concurrent access to a shared (Ont)Model

On 21/07/16 22:26, Martynas Jusevičius wrote: Thanks Dave. Does the following code look reasonable? OntModel ontModel = OntDocumentManager.getInstance().getOntology(ontologyURI, ontModelSpec); ontModel.enterCriticalSection(Lock.READ); try {

Re: Default RDF/XML writer changed between 2.11.0 and 3.0.1?

On 21/07/16 23:44, Martynas Jusevičius wrote: Hey, I noticed that after upgrade from 2.11.0 to 3.0.1 the RDF/XML output changed: element name is used instead of rdf:Description + rdf:type, rdf:nodeID attribute is gone etc (output below). The model is written the same way, like this: