1. Any reason you are not using QUDT?
2. Any reason you are not using SHACL?
3. I found it strange that you are embedding a unit of measure into a string
e.g., “2.40m”.
4. Option one is simpler than option two for defining Height. It requires an
extra triple when using Height. This does not seem “too much” to me fo use in
systems since querying restrictions is more complex than just using a simple
triple.
Given OWL reasoner, option 2 entails some inferences. Option 1 does not entail
any inferences, but “given OWL reasoner” is an assumption that is typically not
practical since there are very few OWL reasoners available and next to none in
use. You could implement a rule that defines your own inference for option 1.
5. Not sure what problems you have with using cdt:length in the restriction. I
can’t reproduce the issue, it works for me - see below.
In my example, I did not give example:hasQuantity any range, it does not matter
whether you specify range or not.
And in RDF
example:Height
rdf:type owl:Class ;
rdfs:subClassOf example:Property ;
rdfs:subClassOf [
rdf:type owl:Restriction ;
owl:hasValue example:length ;
owl:onProperty example:hasQuantity ;
] ;
.
6. As for semantics of this definition, it means that if there is :R1 a
example:Height, then it will be inferred that :R1 example:hasQuantity
example:length. Thus, I do not think it makes sense using length as you are
doing in:
> ex:Height_1 rdf:type ex:Height ;
> bs:hasValueUnit “2.40 m”^^cdt:length .
I do not think it would make sense with the first option either since you are
putting this info on the class itself (option 2 and 3) or into an instance
resource representing Height (option 1). Whether you are using inferences or
not, you can always get this information
May be you meant to do something like:
> ex:Height_1 rdf:type ex:Height ;
> bs:hasValueUnit “2.40”^^cdt:meter .
7. Yes, if you don’t have to be in OWL-DL, you can also use option 3. As option
1, it does not entail any inferences.
> On Jul 7, 2019, at 7:15 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
> <topbraid-users@googlegroups.com> wrote:
>
> In the W3C LBD we are comparing different ways of modelling (complex)
> properties.
>
> One option:
>
> ex:Height rdf:type bs:PropertyType ;
> bs:hasQuantity cdt:length .
> ex:Door_1 rdf:type ex :Door ;
> bs:hasProperty ex:Height_1 .
> ex:Height_1 rdf:type bs:Property ;
> bs:hasPropertyType ex:Height ;
> bs:hasValueUnit “2.40 m”^^cdt:length .
>
>
> but some people think the XType modelling is too much. So they like to just
> specialise bs:Property into ex:Height resulting in:
>
> ex:Height rdfs:subClassOf bs:Property ;
> rdfs:subClassOf [ rdf:type owl:Restriction ;
> owl:hasValue “cdt:length” ;
> owl:onProperty bs:hasQuantity ; ] .
> ex:Door_1 rdf:type ex :Door ;
> bs:hasProperty ex:Height_1 .
> ex:Height_1 rdf:type ex:Height ;
> bs:hasValueUnit “2.40 m”^^cdt:length .
>
>
> so the original:
> bs:hasQuantity cdt:length .
>
> becomes a restriction in the second option.
>
> BUT...as can be seen instead of just
> cdt:length
>
> I have to specify
> “cdt:length” with quotes (just cdt:length does not work in
> tbc)
>
> (the range of hasQuantity is rdfs:Datatype)
>
> In the constraint.
>
> Is this actually doing what I intended?
>
> Thx Michel
>
> Ps related to my earlier OWL Full question, guess an OWL Full option could
> also be:
>
> ex:Height rdfs:subClassOf bs:Property ;
> owl:hasQuantity cdt:length .
>
>
>
>
>
>
>
> Dr. ir. H.M. (Michel) Böhms
> Senior Data Scientist
>
> T +31888663107
> M +31630381220
> E michel.bo...@tno.nl <mailto:michel.bo...@tno.nl>
> Location
> <https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707>
>
>
> <image001.gif> <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 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>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/2f1adc9bf0894158857783a8220a7165%40tno.nl
>
> <https://groups.google.com/d/msgid/topbraid-users/2f1adc9bf0894158857783a8220a7165%40tno.nl?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/8BF7DEBD-276A-4D57-BCD5-A84237F77E27%40topquadrant.com.
For more options, visit https://groups.google.com/d/optout.
