Another approach is to use an ontology architecture and partition the
ontologies according to use cases when you created them in the first
place ... at least for anything you create yourself. Of course, if
you're reusing existing ontologies and have this requirement, then
having a SPIN-based tool could assist in that partitioning.
Cheers,
David
On 6/27/2011 7:00 PM, Leonard Jacuzzo wrote:
Irene,
The use case i had in mind was general.
Imagine if you want to build a model with the greatest potential for
future use at an extensive enterprise.
Using a profile would not be the way to go because then you only have
that profile and not another. So my thought was using DL would be
maximally adaptable.
If using rules based, then one could take out the disjoints etc.
Thanks for another reason to go large.
LFJ
On Mon, Jun 27, 2011 at 1:29 PM, Irene Polikoff <[email protected]
<mailto:[email protected]>> wrote:
While it is possible, my understanding is that one does not really
need to change an ontology. Each inference engine will simply make
the inference that it can i.e., if it supports OWL-RL profile, it
will only make inferences specified in that profile.
What is the use case you have in mind, Leonard?
I suppose one could think of the different style of modeling
depending on the intended inference engine. For example, given how
DL algorithms work, having a lot of disjoint class statements will
have a positive impact on performance of a DL engine; on the other
hand, it may slow down rules-based engine.
Irene Polikoff
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] *On Behalf Of *Leonard
Jacuzzo
*Sent:* Monday, June 27, 2011 1:06 PM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [topbraid-users] Re: an interesting question
Thanks Scott,
I had the feeling that this was the case since all profiles are
subprofiles of DL.
Best wises,
Leonard
On Mon, Jun 27, 2011 at 11:13 AM, Scott Henninger
<[email protected] <mailto:[email protected]>>
wrote:
Hello Leonard; Yes, since all OWL profiles (one can see DL as a
special profile) are specified in RDF, it is possible to create SPARQL
queries that take an OWL model and define models that are compatible
with the different OWL 2 profiles. SPIN could be used to define and
organize the queries. To save the different models, I'd suggest a
small SPARQLMotion script that calls TopSPIN with replace=true and
saves the resulting triples into a file.
For example you can define a set of rules for OWL 2 RL and OWL 2 QL.
Define subproeprties of spin:rule for each (e.g. :owlRL, :owlQL).
Define all OWL 2 RL rules using :owlRL properties defined in owl:Thing
and all OWL 2 QL rules using :owlQL. Then writ a script that imports
the original file and defines two separate pipelines. One calls
TopSPIN with predicate = :owlRL and replace=true, then a
ExportToRDFFile. The second pipe would calls TopSPIN with predicate
= :owlQL and replace=true, then a ExportToRDFFile.
The end result is two files with a the subset of the original OWL file
that meet the different profiles.
SPINMap may be quite useful to such an exercise. See
http://composing-the-semantic-web.blogspot.com/2011/04/spinmap-sparql-based-ontology-mapping.html
-- Scott
On Jun 27, 9:12 am, Leonard Jacuzzo <[email protected]
<mailto:[email protected]>> wrote:
> Hello group,
>
> I just thought of an interesting question. Since, you guys are
the SPIN
> masters, I thought I would pose it to you.
>
> Do you think that it is possible to build a model in OWL 2 DL
and then use
> SPIN to divide it into the various profiles depending upon an
application?
>
> This would be great if it were the case.
>
> Any thoughts would be helpful.
>
> Best wishes,
> Leonard
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid
Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:topbraid-users%[email protected]>
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid
Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:topbraid-users%[email protected]>
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid
Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:topbraid-users%[email protected]>
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid
Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
--
Managing Director and Consultant
TopQuadrant Limited. Registered in England No. 05614307
UK +44 7788 561308
US +1 336-283-0606
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
