Hi David I see your point: “better use skos only separate from rdfs/owl/shacl”
But ok we said it would be handy to combine (many parties already did in NL like Cadastre). But then it seems we have to double….which goes a bit against the principle of separation of concerns…. Ie also (red): sml:Activity a rdfs:Class ; rdfs:isDefinedBy sml-term:Activity ; rdfs:subClassOf sml:Entity ; skos:definition "An activity is something possibly or actually happening in space and time"@en ; skos:prefLabel "Activity"@en ; . I hoped for less doubling like: sml:Activity a rdfs:Class ; rdfs:isDefinedBy sml-term:Activity ; rdfs:subClassOf sml:Entity ; skos:prefLabel "Activity"@en ; . Isn’t the skos:definition also for human interpretation only so that it can stays at skos-side? Wrt tools expecting labels..if I rember right edg also likes/needs labels right? If edg has no issue I might stay with the current approach (only having uris/names) for rdfs/owl/shacl side. 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. Van: [email protected] <[email protected]> Namens David Price Verzonden: dinsdag 29 juni 2021 12:37 Aan: [email protected] CC: Benno Koehorst <[email protected]>; Sander Stolk <[email protected]> Onderwerp: Re: [topbraid-users] label position On 29 Jun 2021, at 08:46, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <[email protected]<mailto:[email protected]>> wrote: Dear All, We use the pattern: sml-term:Activity a skos:Concept ; skos:broader sml-term:Entity ; skos:definition "An activity is something possibly or actually happening in space and time"@en ; skos:prefLabel "Activity"@en ; . sml:Activity a rdfs:Class ; rdfs:isDefinedBy sml-term:Activity ; rdfs:subClassOf sml:Entity ; . But this means that the label is only indirectly available for sml:Activity (via “isDefinedBy.prefLabel”) Is this an issue? (many tools like to have a direct label for their classes) I imagine tools will use one of the local name or perhaps URI or perhaps prefixed name. Being an issue depends on use case (i.e. no problem at all if for data exchange but perhaps for a human looking at a UI). Better solutions? (I’d like to define only once, not double; Not possible. label feels naturally close to definition; maybe only prefLabel to rdfs-variant and leave altLabel/definition at skos?) There are two different things with different URIs. They do not “share” properties. That’s just how RDF and RDFS/OWL and SKOS work, so will not surprise anyone or any tool. It’s unclear if you expect them to ever be used together, but as SKOS is an OWL ontology and the other seems RDFS I imagine not. A Concept and a Class are not the same thing at all. An RDFS Class (data modelling artefact) has members/class extension that are resources, while a SKOS Concept (e.g. a library science artefact) does not as it’s main purpose is as the Web identifier for the variety of labels/definitions in multiple languages and flexible, not-formally-defined relations that it holds. Note that the SKOS crew do want it used in a manner like this, but not with the specific approach being taken above: Looking to the future, SKOS occupies a position between the exploitation and analysis of unstructured information, the informal and socially-mediated organization of information on a large scale, and the formal representation of knowledge. By making the accumulated experience and wisdom of knowledge organization in the library and information sciences accessible, applicable and transferable to the technological context of the Semantic Web, in a way that is complementary to existing Semantic Web technology (and in particular formal systems of knowledge representation such as OWL), it is hoped that SKOS will enable many new and valuable applications, and will also lead to new integrative lines of research and development in both technology and practice. Every class and property should have its own label and more importantly its own local definition. Note that formal class definitions often place the class in the class hierarchy (i.e. a <class> is a <superclass> that <further membership criteria distinguishing class from other subclasses of superclass> ) whereas a concept definition would not do so. Concept labels/defs are for all humans, and those for Classes are aimed at software developers - or at least that IMO is the best practice of using these two together. Cheers, David Thx for advice, 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> <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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/65077d500edc4a6bb4f8289d08326df2%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/65077d500edc4a6bb4f8289d08326df2%40tno.nl?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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/A427481B-4F29-4C2A-95BA-8822183EE5B5%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/A427481B-4F29-4C2A-95BA-8822183EE5B5%40topquadrant.com?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/77f4ecc7e0064cf0991ea8560498b4fb%40tno.nl.
