As far as the tire example, I assume that you have a way to identify that a tire is either front or back, such as a property ‘position’ with ‘back’ or ‘front’ values.
If so, then you would attach two different rules to the Tire class – one
about instances with {?this example:position example:back} and another one
about instances with {?this example:position example:front}. There is no
need to create FrontTireClass and BackTireClass.
DL style of modeling, on the other hand, is typically about having extensive
class trees.
Irene Polikoff
From: [email protected]
[mailto:[email protected]] On Behalf Of Bohms, H.M. (Michel)
Sent: Thursday, September 29, 2011 8:29 AM
To: [email protected]
Subject: [topbraid-users] two rule-issues: CWA & instance rules
In figuring out the best way to model etc. rules I run into 2 specific
issues.
1. CWA <> OWA
I know and understand the typical example involving card=1. CWA: 1 allowed;
OWA: if more, they are inferred the same. But how does it work in owl2 (no
spin) with 'value examples'. Like age > 0 and age fact of individual = -3.
What is the OWA interpretation now? (something like "anything"=true beacuse
inconsistent or what?)
2. using some own meta-models up to know for rule modelling we could even
model rules on instance level. ie there is an instance wall_1 for which we
know height>10m or which should have height>10m. How would that work in
spin: do we always have to introduce extra classes to deal with such
constraints? typical example "in-the-middle": front tires of a car: min
2.3bar pressure, back tires min 2.5 bar.
In our meta-models: we attach 2x2 constraints to four tire instances
(having/needing one Tire class only). Using owl directly it seems we can
only introduce the class FrontTire RearTire or even FronLeftTire etc. and
then instaniate all classes one time.Would be interested in your view.
Thanks for any views on these two modelling/rule issues. Michel
Dr. ir. H.M. (Michel) Böhms
Sr. Research Scientist
Technical Sciences
T +31 888663107
M +31 630381220
E <mailto:[email protected]> [email protected]
<http://www.tno.nl/locaties/dtm> Location
<http://www.tno.nl/emaildisclaimer> Disclaimer
<http://www.tno.nl/>
--
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
--
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
<<image001.gif>>
