> On 13 Jan 2022, at 16:52, Ben Kass <bk...@enterprise-knowledge.com> wrote: > > You can pun in OWL 2 Full and DL as both a class and object property - it's > briefly mentioned in the documentation here at the bottom of the examples: > https://www.w3.org/TR/owl2-new-features/#F12:_Punning > I know of one organization that will pun classes and datatype properties (no > possible in OWL DL) for convenience of modeling, but when I asked around at > my workplace no-one else had heard of people punning in that way, so I've > always assumed it's pretty uncommon and I don't think that tooling tends to > particularly like when you do it. That's about all I know about it. There is > a working draft for OWL 2 online that goes into it more > (http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.448.2097&rep=rep1&type=pdf) > but those parts seem to have been cut from the final documentation so be > aware of that.
Thanks for the link Ben - it does include a sensible property example, although including an example from UML muddies the waters a bit since AssociationClass built into the language already. One clarification … AFAIK the very concept of punning is not needed when under an OWL 2 RDF Semantics (i.e. OWL 2 Full) because there is no need in the logic to treat the same URI as two separate things. I’ve seen explanations like the following in online training slides I found (there are from from Pascal Hitzler): Punning • Description logics impose type separation, i.e. names of individuals, classes, and properties must be disjoint. • In OWL 2 Full, type separation does not apply. • In OWL 2 DL, type separation is relaxed, but a class X and an individual X are interpreted semantically as if they were different. I think all logics “beyond” DL don’t need punning as a concept at all, although I’m not an HOL expert. Cheers, David > > Best, > Ben > > On Thursday, January 13, 2022 at 9:14:22 AM UTC-5 David Price wrote: > >> On 13 Jan 2022, at 13:57, 'Bohms, H.M. (Michel)' via TopBraid Suite Users >> <topbrai...@googlegroups.com >> <applewebdata://488EA2E2-AAFB-4A5D-91E5-6B07E6249E3B>> wrote: >> >> Background >> >> In our NL standard we model quantities (‘stroefheid for some asphalt >> lanesection/strookvak’) like: >> >> :stroefheid >> rdf:type owl:ObjectProperty ; >> rdfs:domain :Strookvak ; >> rdfs:range nen2660:QuantityValue ; >> nen2660:hasQuantityKind quantitykind:FrictionCoefficient ; >> . >> >> So they become object properties (‘relations’). >> >> Especially for Measurements we want to reuse SSN/SOSA. >> >> In that case we get: >> >> :stroefheid >> rdf:type sosa:ObservervableProperty ; >> nen2660:hasQuantityKind quantitykind:FrictionCoefficient ; >> . >> >> Now my question, can we combine the 2 without too many issues? >> >> So we get: >> >> :stroefheid >> rdf:type owl:ObjectProperty ; >> rdf:type sosa:ObservableProperty ; >> >> so ‘stroefheid’ becomes a property AND a class. >> >> Doe this case fall under “owl punning”? (like when something is typed as >> individual and class). >> >> Do we enter OWL full or not? >> > > Off the top of my head so please confirm yourself by reading the OWL spec but > ... > > I think so. Punning or metamodellng is about two levels of class (class > member of class) as far as I know. Spec examplese are all classes. I’ve never > studied/tested what you’re doing though. > > Cheers, > David > > >> Thx ! Michel >> >> >> > >> >> Dr. ir. H.M. (Michel) Bohms >> Scientist Specialist >> Structural Reliability >> T +31 (0)88 866 31 07 >> M +31 (0)63 038 12 20 >> E michel...@tno.nl <applewebdata://488EA2E2-AAFB-4A5D-91E5-6B07E6249E3B> >> Location <http://www.tno.nl/locations/DTS> >> >> > >> <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-user...@googlegroups.com >> <applewebdata://488EA2E2-AAFB-4A5D-91E5-6B07E6249E3B>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/topbraid-users/d8bfd67d1b514465bc95bd9c6dee7376%40tno.nl >> >> <https://groups.google.com/d/msgid/topbraid-users/d8bfd67d1b514465bc95bd9c6dee7376%40tno.nl?utm_medium=email&utm_source=footer>. > > UK +44 (0) 7788 561308 <tel:+44%207788%20561308> > US +1 (336) 283-0808 <tel:(336)%20283-0808> > > > -- > 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/979dce13-39dc-4a15-87b9-df5b5f4eae52n%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/979dce13-39dc-4a15-87b9-df5b5f4eae52n%40googlegroups.com?utm_medium=email&utm_source=footer>. UK +44 (0) 7788 561308 US +1 (336) 283-0808 -- 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/46A2714D-BB97-4774-969E-44A8B941F49A%40topquadrant.com.
