JIRA::
https://issues.apache.org/jira/browse/JENA-413 fixes the 0 duration
issue (fixed, closed)
https://issues.apache.org/jira/browse/JENA-414 records the formating of
non-zero second durations (fixed, closed)
https://issues.apache.org/jira/browse/JENA-415 is a feature request for
Thanks for catching this. The restriction was actually correct, but the
definition of associatedWith was left over from when I was only dealing with
Person objects. I changed the definition of associatedWith to:
owl:SymmetricProperty rdf:ID=associatedWith
rdfs:domain
On 19/03/13 00:35, Brian McBride wrote:
On 18/03/2013 21:36, Dave Reynolds wrote:
On 18/03/13 21:16, Joshua TAYLOR wrote:
On Mon, Mar 18, 2013 at 4:55 PM, Brian McBride
br...@epimorphics.com wrote:
On 18/03/2013 20:18, Joshua TAYLOR wrote:
This spurred me to look at some of the relevant
Unfortunately, it looks like there's still a problem with the super/subclass
relationship even after I fixed the inconsistent property. Specifically, here's
the test code:
OntModel model =
ModelFactory.createOntologyModel(OntModelSpec.OWL_DL_MEM_RULE_INF);
On Tue, Mar 19, 2013 at 10:07 AM, Ed Swing ed.sw...@sas.com wrote:
Unfortunately, it looks like there's still a problem with the super/subclass
relationship even after I fixed the inconsistent property. Specifically,
here's the test code:
OntModel model =
Whoops - thanks.
-Original Message-
From: Joshua TAYLOR [mailto:joshuaaa...@gmail.com]
Sent: Tuesday, March 19, 2013 10:51 AM
To: users@jena.apache.org
Subject: Re: Super/Subclass relationships in OntModel?
On Tue, Mar 19, 2013 at 10:07 AM, Ed Swing ed.sw...@sas.com wrote:
On 19/03/13 14:07, Ed Swing wrote:
Unfortunately, it looks like there's still a problem with the super/subclass
relationship even after I fixed the inconsistent property.
This is not a completely fixed ontology.
It still has the illegal section:
owl:Class rdf:ID=Killing
What would be the proper construct then for A killing is a subclass of event
that cannot have a NewsOrganization as the actor?
-Original Message-
From: Dave Reynolds [mailto:dave.e.reyno...@gmail.com]
Sent: Tuesday, March 19, 2013 11:01 AM
To: users@jena.apache.org
Subject: Re:
Hello, everyone,
when I call the following method:
ontmodel_.write(new FileOutputStream(new File(path+filename)));
I have got an error as following several times, if anyone can tell me
what is the possible reason for this? thank you very much.
Caused by:
On 19/03/13 15:25, Jie wrote:
Hello, everyone,
Which version are you running?
when I call the following method:
ontmodel_.write(new FileOutputStream(new File(path+filename)));
I have got an error as following several times, if anyone can tell me
what is the possible reason for this? thank
The notion of apply to a class in OWL is not like it is in object
oriented languages.
For discussion on this see:
http://jena.apache.org/documentation/notes/rdf-frames.html
In particular see the listDeclaredProperties helper function which is
mentioned therein.
Dave
On 19/03/13 15:07, Ed
I am using the version tdb 0.9.4 and jena 2.7.4 and also I use
transactions in my code.
On 19 March 2013 16:29, Andy Seaborne a...@apache.org wrote:
On 19/03/13 15:25, Jie wrote:
Hello, everyone,
Which version are you running?
when I call the following method:
ontmodel_.write(new
On 19/03/13 15:09, Ed Swing wrote:
What would be the proper construct then for A killing is a subclass of event that
cannot have a NewsOrganization as the actor?
The simplest change from what you have might be:
owl:Class rdf:ID=Killing
rdfs:subClassOf rdf:resource=#Event /
On Tuesday, March 19, 2013 03:07:29 PM Ed Swing wrote:
On to my next unexplainable thing in Jena - Property domains.
The code below is trying to identify what properties apply to a class
based on the property domain. Here's the code:
package ontology;
(fx:snip)
Several of these are
On Tue, Mar 19, 2013 at 11:07 AM, Ed Swing ed.sw...@sas.com wrote:
On to my next unexplainable thing in Jena – Property domains. The code below
is trying to identify what properties apply to a class based on the property
domain. Here’s the code:
package ontology;
import
On 19/03/13 15:40, Jie wrote:
I am using the version tdb 0.9.4 and jena 2.7.4 and also I use
transactions in my code.
Could you show more of your code?
Is the ontmodel_ obtained inside a transaction?
The corruption to the node table most likely happened in the past - it's
the read operation
edge:
Jena: VERSION: 2.10.1-SNAPSHOT
Jena: BUILD_DATE: 20130319-1018
ARQ:VERSION: 2.10.1-SNAPSHOT
ARQ:BUILD_DATE: 20130319-1018
RIOT: VERSION: 2.10.1-SNAPSHOT
RIOT: BUILD_DATE: 20130319-1018
TDB:VERSION: 0.10.1-SNAPSHOT
TDB:BUILD_DATE
: VERSION: 2.10.1-SNAPSHOT
Jena: BUILD_DATE: 20130319-1018
ARQ:VERSION: 2.10.1-SNAPSHOT
ARQ:BUILD_DATE: 20130319-1018
RIOT: VERSION: 2.10.1-SNAPSHOT
RIOT: BUILD_DATE: 20130319-1018
TDB:VERSION: 0.10.1-SNAPSHOT
TDB:BUILD_DATE: 20130319-1018
which includes
into a named graph and used a
vanilla TDB assembler file.
I've checked permissions of the store files too.
As far as I can tell, the query makes it to the service fine.
And because I like to live on the bleeding edge:
Jena: VERSION: 2.10.1-SNAPSHOT
Jena: BUILD_DATE: 20130319-1018
ARQ
Hi,
I have been working on a client project on which we have used the Jena SDB
implementation (1.3.5 snapshot backed by Oracle) as our triple store.
The basic issue we have is as follows:
During implementation we encountered some fairly severe performance
restrictions during querying -- not
graph and used a
vanilla TDB assembler file.
I've checked permissions of the store files too.
As far as I can tell, the query makes it to the service fine.
And because I like to live on the bleeding edge:
Jena: VERSION: 2.10.1-SNAPSHOT
Jena: BUILD_DATE: 20130319-1018
ARQ
Hi Andy,
I understand from your email below that the issues I mentioned in my email
have been fixed. Can you please tell me the procedure to access and
integrate these fixes smootly to my code? Do I have to upgrade to a more
recent version of Jena? For instance in Eclipse, I'm getting the error
If you are using Maven the current dev build version you will want for
your Jena dependency will be 2.10.1-SNAPSHOT
If you are using multiple Jena components you should use the latest
SNAPSHOT across all your Jena dependencies as otherwise you will run into
issues with conflicting versions of
Thank you Rob. So, the results of subsequent calls to next() are dependent
on previous calls? Is there any way to execute in bulk or as a batch to
reduce the number of db calls?
I'm trying to find a balance between loading the entire triple store into
memory and leaving everything in the
24 matches
Mail list logo
