Hi Michel,
just a meta-response: for general modeling advice that is unrelated to
TopBraid, you may want to post your question to
http://answers.semanticweb.com/
where you should also get a wider range of viewpoints.
HTH
Holger
On 5/27/2014 0:34, Bohms, H.M. (Michel) wrote:
Dear all,
I'd like your advice on a specific modelling pattern.
In our taxonomies we use as much as possible "discriminators" that are
datatype properties that get a class-level value (hasValue) relevant
for all individuals.
Sometimes however, we want to discriminate according to something like
"application area" that refers to a (another) class in the ontology.
We cannot do a similar thing as with datatype property discriminators
(like a discriminating object property) because we don't want to
discriminate wrt values/refs of classes but more on the classes itself
(its more a meta object property in fact).
So for now we define an datatype property "applicationArea" and put
the relevant class names as enumeration items. Clearly this feels a
bit double and asking for inconsistencies (keeping relevant classes
and related enumeration items in sync).
We would welcome ideas on THE way to do this in OWL (would it involve
for instance reification?).
I want to conclude with a simple example.
A.Class Engine (next to Class Car, Plane, Ship,...)
B.DatatypeProperty aplicationArea, datatype [Car, Plane, Ship,....]
C.Class CarEngine
SubClassOf Engine
aplicationArea hasValue Car
but maybe better done something like:
A.Class Engine, Car, Plane, Ship
B.ObjectProperty applicationArea (with range: owl:Class) (we don't
like this because we want to model properties as datatypeproperties...)
C.Class CarEngine
SubClasOf Engine
applicationArea "hasValue" Car
or better....???
Thx a lot, Michel and Lieke
Dr. ir. H.M. (Michel) Bohms
Sr. Research Scientist
Structural Reliability
T +31 (0)88 866 31 07
M +31 (0)63 038 12 20
E michel.bo...@tno.nl <mailto:michel.bo...@tno.nl>
Location <http://www.tno.nl/locaties/DTM>
<http://www.tno.nl/>
This message may contain information that is not intended for you. If
you are not the addressee or if this message was sent to you by
mistake, you are requested to inform the sender and delete the
message. TNO accepts no liability for the content of this e-mail, for
the manner in which you use it and for damage of any kind resulting
from the risks inherent to the electronic transmission of messages.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise
Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid
Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
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
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to topbraid-users+unsubscr...@googlegroups.com
<mailto:topbraid-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL
Web Pages and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
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 Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
