Re: Read-only (Ont)Model

But with this version I've started getting ConcurrentModificationExceptions again :( Since a complete copy with add() is too slow, I guess if I need to start locking the Model anyway? I was trying to avoid it. On Mon, Oct 17, 2016 at 11:01 PM, Dave Reynolds wrote: >

Re: Statistic of Data in owl file

David, what if we write something like this team1.setPropertyValue(Goals, literalvalue) If we enter Goals next time, the previous value will be vanish, right? On Tue, Oct 18, 2016 at 12:00 PM, David Jordan wrote: > No reason to overwrite anything, each event will

Re: Statistic of Data in owl file

No reason to overwrite anything, each event will have attributes, including a date. On Tue, Oct 18, 2016 at 2:27 PM, Andy Seaborne wrote: > neha, > > Your question is too open ended. Sounds like the whole exercise you have > been asked to do. > > What have you tried? > > Try

Re: Statistic of Data in owl file

I want just to know is there any approach in which we can keep track of data previously entered. I am very sorry but I have not tried any thing related to it as I am completely blind it? I searched the web from last three-four days but could not found hints. That is why I asked here in the experts

Statistic of Data in owl file

Good evening, I have some team information in my ontology i-e team1 wins, goals, Euro goals, Worldcup goals. team1 information will be stored like this in owl file. After one month, again team1 information will be entered, which of course, will over write the previous one. Can I maintain the

Re: Concurrent read with unmatched optional clause causes exception in Jena 3.1.

On 18/10/16 10:59, Dick Murray wrote: Found the cause and I hate log4j... Log4j was unable to find it's configuration file so was quietly defaulting the RootLogger to debug. So when static public final Logger log = LoggerFactory.getLogger(ReorderTransformationSubstitution.class) was called

Re: Concurrent read with unmatched optional clause causes exception in Jena 3.1.

On 17/10/16 21:54, Dick Murray wrote: On 17 Oct 2016 21:33, "Andy Seaborne" wrote: On 17/10/16 21:13, Dick Murray wrote: Hi. On 17 Oct 2016 18:16, "Andy Seaborne" wrote: Are you running with debug tracing on? No, should I and what should I look

Re: Concurrent read with unmatched optional clause causes exception in Jena 3.1.

Found the cause and I hate log4j... Log4j was unable to find it's configuration file so was quietly defaulting the RootLogger to debug. So when static public final Logger log = LoggerFactory.getLogger(ReorderTransformationSubstitution.class) was called it's parent is RootLogger and it's level is