With respect to editing, OWL editors typically implement all features of the spec. With respect to OWL reasoning, different vendors implement different subsets of the spec.
This is problematic from the interoperability perspective, so profiles were created in an attempt to standardize the subsets. With this, users know what to expect if a vendor supports let’s say OWL-RL or OWL-QL. Thus, you can target your modeling to let’s say OWL-RL profile and be assured that all vendors supporting OWL-RL will give you the same results. I have no information on the specifics of motivations or issues which led to putting certain things in any particular profile. Data range expressions (and it doesn’t matter what restrictions you are using them with) did not make it into any of the profiles. They are still part of OWL specification. As per above, a vendor that implemented one of the profiles will not support these expressions. With rules-based implementations you can add your own rules to support some additional features. A vendor that has an OWL DL reasoner may support the data range expressions which is why I suggested for you to try a DL reasoner. You will need to investigate the level of support. > On Aug 25, 2017, at 11:32 AM, Bohms, H.M. (Michel) <[email protected]> > wrote: > > > Dear Irene, > > Thx for the extra info. > > I am quite confused about a valid OWL2 construct that isn’t in any profile > (ie not even in the strongest profile) for it. > > I got the example from the OWL2 Primer: > > “ > New classes can be defined by restrictions on datatype properties. The > following example defines the class teenager as all individuals whose age is > between 13 and 19 years. > Turtle Syntax > :Teenager rdfs:subClassOf > [ rdf:type owl:Restriction ; > owl:onProperty :hasAge ; > owl:someValuesFrom > [ rdf:type rdfs:Datatype ; > owl:onDatatype xsd:integer ; > owl:withRestrictions ( [ xsd:minExclusive "12"^^xsd:integer ] > [ xsd:maxInclusive "19"^^xsd:integer ] > ) > ] > ] . > “ > Or is this only possible in case of someValuesFrom, not allValuesFrom? > > Thx again Michel > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > T +31888663107 > M +31630381220 > E [email protected] <mailto:[email protected]> > 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. > > > > > From: [email protected] > <mailto:[email protected]> > [mailto:[email protected] > <mailto:[email protected]>] On Behalf Of Irene Polikoff > Sent: vrijdag 25 augustus 2017 17:12 > To: [email protected] <mailto:[email protected]> > Subject: Re: [topbraid-users] constraint violation > > See below > > On Aug 25, 2017, at 7:41 AM, Michel Böhms <[email protected] > <mailto:[email protected]>> wrote: > > Hi Irene > > There was mistake in disjointness modelling. Now I get the errors "shared > instance of disjoint classes"as expected. > > area: so having a minValue (here float) makes me owl full? > > No. > > Dividing OWL into Lite, DL and Full was done as part of OWL 1.0 in attempt to > predict what subsets of OWL may be practically useful. For example, the > working group that produced the standard thought that perhaps vendors would > find OWL Light easier to implement than OWL DL. With OWL 2, more thinking was > done about what what may be practically useful. This thinking resulted in > defining OWL RL, OWL EL and OWL QL - targeted to specific use > cases/implementation technologies such as rules engines, relational > databases, etc. > > You can read about OWL 2 profiles here https://www.w3.org/TR/owl2-profiles/ > <https://www.w3.org/TR/owl2-profiles/> > > The expression you have used was not included into any of the profiles. This > doesn’t mean that some support for it can’t be done with rules. It only means > that it is not part of the profile and, thus, we do not include it in our > OWL-RL implementations. > > You can try your example with a DL reasoner, to see what level of support is > there. > > > wrt rule language: I also have a variant with a sparql ask query (spin) that > works fine (*). > > So what would you advice for future: spin or shacl. Is the power between them > compatible? > > Ie can you do all constraint checking in shacl that you can do in sparql ask? > > SHACL is a standart. If you are interested in using standards, then use > SHACL. It also has a number of additional features. So, you should think of > SHACL as SPIN 2.0. > > > thx a lot, > Michel > > * > <image.png> > > > 2017-08-25 13:22 GMT+02:00 Bohms, H.M. (Michel) <[email protected] > <mailto:[email protected]>>: > > > Verzonden van mijn Android-telefoon via TouchDown (www.symantec.com > <http://www.symantec.com/>) > > -----Original Message----- > From: Irene Polikoff [[email protected] <mailto:[email protected]>] > Received: donderdag, 24 aug. 2017, 19:28 > To: [email protected] <mailto:[email protected]> > [[email protected] <mailto:[email protected]>] > Subject: Re: [topbraid-users] constraint violation > > Michel, > > Is BigPump class disjoint with SmallPump class? > > As for your restriction on the area property, a data range expression is > restricted in OWL 2 RL to the predefined datatypes admitted in OWL 2 RL and > the intersection of data ranges. As an aside, the same is true for OWL 2 QL. > OWL 2 EL is the same plus it also supports enumerations of literals > consisting of a single literal. So, with none of the OWL 2 profiles will > there be reasoning based on xsd:minInclusive. > > I’d recommend SHACL solution over SPIN because it would be more standard. > > > On Aug 24, 2017, at 9:41 AM, Bohms, H.M. (Michel) <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > Dear, > > > > Was hoping to get two warnings/errors on attached file (OWL-RL restrictions > > has been ticked and after inferencing with topspin): > > • Value for area of BigPump_1 does violate owl restriction on area > > • Selected pump violates allvaluesfrom restriction > > > > Is there a way to have tbc showing such issues? > > > > Thx a lot, Michel > > > > Situation: > > <image002.png> > > And the actual nonvalid individual (in red where I hoped for warning/error): > > <image003.png> > > > > Ps I have also spin variant but want to compare with owl-only solution….. > > > > > > Dr. ir. H.M. (Michel) Böhms > > Senior Data Scientist > > > > T +31888663107 <tel:+31%2088%20866%203107> > > M +31630381220 <tel:+31%206%2030381220> > > E [email protected] <mailto:[email protected]> > > Location > > > > > > <image001.gif> > > 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 [email protected] > > <mailto:topbraid-users%[email protected]>. > > For more options, visit https://groups.google.com/d/optout > > <https://groups.google.com/d/optout>. > > <priva-owl.ttl><priva-owl.ttl.tbc> > > -- > 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 [email protected] > <mailto:topbraid-users%[email protected]>. > 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 [email protected] > <mailto:[email protected]>. > 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 [email protected] > <mailto:[email protected]>. > 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 [email protected] > <mailto:[email protected]>. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
