Hereby also the actual code example for modelling implicit groups of assets. (via a nested constraint for an individual)
Example: a road crash barrier having associated an implicit group of 300 yellow km-signs. No complaints from TBC. Still special way of modelling, comments welcome. # baseURI: https://w3id.org/igtest/owl/def # imports: https://w3id.org/nen2660/owl/def @prefix nen2660: https://w3id.org/nen2660/def# . @prefix owl: http://www.w3.org/2002/07/owl# . @prefix quantitykind: http://qudt.org/vocab/quantitykind/ . @prefix qudt: http://qudt.org/schema/qudt/ . @prefix rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# . @prefix rdfs: http://www.w3.org/2000/01/rdf-schema# . @prefix skos: http://www.w3.org/2004/02/skos/core# . @prefix unit: http://qudt.org/vocab/unit/ . @prefix wn: https://w3id.org/wegennetwerk/def# . @prefix xsd: http://www.w3.org/2001/XMLSchema# . @prefix ig: https://w3id.org/igtest/def# . https://w3id.org/igtest/owl/def a owl:Ontology ; owl:imports https://w3id.org/nen2660/owl/def ; . ig:GeleideConstructie a owl:Class ; . ig:HectometerPaal a owl:Class ; . ig:GCnoorderZijberm-hm15dot-hm25dot3 a ig:GeleideConstructie ; ig:hasGroupedParts ig:HMPgroup_1 ; . ig:HMPgroup_1 a rdfs:Container ; a [a owl:Restriction ; owl:onProperty rdfs:member; owl:qualifiedCardinality 300 ; owl:onClass [ rdfs:subClassOf ig:HectometerPaal; rdfs:subClassOf [ a owl:Restriction; owl:hasvalue "Geel"; owl:onProperty ig:kleur] ] ] ; . ig:hasGroupedParts a owl:ObjectProperty ; rdfs:range rdfs:Container ; . ig:kleur a owl:DatatypeProperty ; rdfs:range xsd:string ; . 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 [email protected]<mailto:[email protected]> Location<http://www.tno.nl/locations/DTS> [cid:[email protected]]<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: 'Bohms, H.M. (Michel)' via TopBraid Suite Users <[email protected]> Sent: Friday, October 8, 2021 12:52 PM To: [email protected] Subject: [topbraid-users] owl restrictions for individuals? In asset management/modelling we often see the need to define groups of (many) things that are not (yet) fully explicitly modelled. Ie a rdfs:Bag instance where not all rdfs:member’ s are known explicitly. Such ‘implicit groups’ as we call them, we would like to represent using OWL restriction classes in owl (and later also shacl shapes) that are used to classify such group instances. Typically all examples we see is using such restriction classes for subclassing on class-level. So now the idea is to use them for classifying instances. Would that be possible within TBC/EDG? In my perception, such instance-level constraint was only a shacl-benefit. But now one of my partners says that this can be done with owl restrictions too. Here is a sketch of the proposal: [cid:[email protected]] Not that the restriction R (left side) is related to the instance of the group #1 working on its member property. Note also its is a nested restriction: onClass has further subrestrictions. If allowed (owl full?) and practically working in TBC/EDG, it would be a very nice language-level approach, better than own inventions like an own hasReferenceIndividual relationship etc. 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 [email protected]<mailto:[email protected]> Location<http://www.tno.nl/locations/DTS> [cid:[email protected]]<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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/8dcd808efee34cb7aac43463f7051a2c%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/8dcd808efee34cb7aac43463f7051a2c%40tno.nl?utm_medium=email&utm_source=footer>. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/316603ffe60c4eaa8715f65c13325f2d%40tno.nl.
