Thankyou Jim for your email.I will look at this tool. It might be useful for 
me.RegardsAbdul


      From: Jim Balhoff <[email protected]>
 To: [email protected] 
 Sent: Thursday, 25 May 2017, 15:09
 Subject: Re: OWL2 Support in Jena
   
Abdul,

You might be interested in this tool I wrote that converts OWL 2 ontologies to 
Jena rules:

https://github.com/balhoff/owl-to-rules 
<https://github.com/balhoff/owl-to-rules>

It’s limited to axioms in the OWL 2 RL profile 
(https://www.w3.org/TR/2012/REC-owl2-profiles-20121211/#OWL_2_RL 
<https://www.w3.org/TR/2012/REC-owl2-profiles-20121211/#OWL_2_RL>). Also, it is 
meant to produce Abox inferences only. For example, if your ontology has <A> 
rdfs:subClassOf <B>, and <B> rdfs:subClassOf <C>, the rules will not output <A> 
rdfs:subClassOf <C>. However, any instances of <A> in your dataset will be 
inferred to be instances of <C>.

It supports some useful things from OWL 2 such as property chains, and also 
SWRL rules. But there are some unfinished parts; it doesn’t do anything with 
data properties (I haven’t needed it so far). It also doesn’t yet support any 
SWRL built-ins or OWL 2 keys.

It’s written in Scala but you can use it in Java programs.

Best regards,
Jim Balhoff




> On May 25, 2017, at 4:34 AM, Rob Vesse <[email protected]> wrote:
> 
> Like all open source projects, we rely upon the volunteers to do the work. 
> Unlike higher profile projects e.g. Spark nobody who volunteers on this 
> project does so as their paid job i.e. Everyone is working in their spare 
> time. Therefore, people naturally work on the pieces of the code that have 
> the most value to them.
> 
> As a project, we do not have any volunteers who are experts in OWL 2 nor 
> anyone who is willing/has the time to do the work.  So, it is unlikely that 
> this will ever happen unless such a volunteer steps up
> 
> Rob
> 
> On 25/05/2017 09:23, "Abduladem Eljamel" <[email protected]> 
> wrote:
> 
>    What does it mean that "OWL2 support in Jena will be added in due course"?
> 
> 
> 
> 


   

Reply via email to