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
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
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
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
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,
>>
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
Do you have some test files we can use?
On 15/07/16 20:30, Martynas Jusevičius wrote:
Created an issue: https://issues.apache.org/jira/browse/JENA-1210
On Fri, Jul 15, 2016 at 5:48 PM, Andy Seaborne wrote:
On 15/07/16 15:15, Martynas Jusevičius wrote:
I am afraid this code
On 15/07/16 15:15, Martynas Jusevičius wrote:
I am afraid this code requires too much knowledge of OntModel inner
workings, which I don't have. Calling loadImports() explicitly works as a
workaround for me.
Wouldn't the fix basically revert to the 2.11.0 code? It did not seem
broken, so why was
I am afraid this code requires too much knowledge of OntModel inner
workings, which I don't have. Calling loadImports() explicitly works as a
workaround for me.
Wouldn't the fix basically revert to the 2.11.0 code? It did not seem
broken, so why was it "fixed" with RDFDataMgr in the first place?
On 14/07/16 15:17, Martynas Jusevičius wrote:
Should I open a Jira for this as well? Seems like a bug to me.
Yes.
And a fix?
Andy
Should I open a Jira for this as well? Seems like a bug to me.
On Thu, 14 Jul 2016 at 15:48, Andy Seaborne wrote:
> On 13/07/16 22:33, Martynas Jusevičius wrote:
> > Hey,
> >
> > I upgraded Jena from 2.11.0 to 3.0.1 and OntModel imports stopped
> > working when getOntology() is
On 13/07/16 22:33, Martynas Jusevičius wrote:
Hey,
I upgraded Jena from 2.11.0 to 3.0.1 and OntModel imports stopped
working when getOntology() is called.
I traced the problem to AdapterFileManager.readModelWorker(Model
model, String filenameOrURI, String baseURI, String syntax), where
Hey,
I upgraded Jena from 2.11.0 to 3.0.1 and OntModel imports stopped
working when getOntology() is called.
I traced the problem to AdapterFileManager.readModelWorker(Model
model, String filenameOrURI, String baseURI, String syntax), where
model.read(in, baseURI, syntax)
was at some point
13 matches
Mail list logo