Hi guys, thanks for your kindly reply, I will work on it, and let you know.
Luis El vie, 23 feb 2024 a las 12:47, 'Bohms, H.M. (Michel)' via TopBraid Suite Users (<[email protected]>) escribió: > Fully agree. > > > > In SML the proposed “maps-to-term” relation is reusing rdfs:seeAlso. > > > > > > Dr. ir. H.M. Böhms (Michel) > Scientist Specialist > Mobility & Built Environment > > T: > M: +31630381220 > E: [email protected] > > Location <https://www.tno.nl/locaties/MSG> > > > > > > <https://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] <[email protected]> *On > Behalf Of *David Price > *Sent:* vrijdag 23 februari 2024 11:10 > *To:* 'Felix Sasaki' via TopBraid Suite Users < > [email protected]> > *Subject:* Re: [topbraid-users] linking glossaries to ontologies ( or > taxonomies) > > > > Hi Luis, > > > > One note of caution … > > > > A Glossary Term is seldom “the same thing” as an ontology class/property > or a database table/column. Instead, what we typically do is say that a > class/property or table/column “maps to” the term. > > > > Glossary Terms are usually for a less technical audience, are > technology-independent and are self contained in most cases. > > > > However, a class definition, for example, often takes its place in the > class hierarchy into account and so is a more technical thing (e.g. a > <class> is a <superclass> with <additional contraints or characteristics> > ). > > > > Additionally, need to remember that all instances of any subclass are also > members of all superclasses and so every definition all the way up the > class hierarchy is also applicable. That sometimes puts a lot of burden on > glossary terms being reused as class definitions. > > > > So, RDF-wise it is certainly possible to do as Holger explained, but > business need/requirements-wise it may not be the best practive. As I said, > in our Data Asset+Glossary architecture solution Data Elements/Database > Columns include a “maps to term’ to Glossary Term relation allowing > separate, clean definitions for the different audiences. > > > > Cheers, > > David > > > > UK +44 (0) 7788 561308 > US +1 (336) 283-0808 > > > > On 23 Feb 2024, at 09:08, Holger Knublauch <[email protected]> wrote: > > > > Hi Luis, > > > > any asset collection can use assets/resources from other asset > collections. Just owl:import the Glossary (from Settings > Includes). Then, > to link a class with a glossary term, navigate to the definition of > rdfs:Class or owl:Class and add a property/relationship there, with > Glossary Terms as values. To navigate to rdfs:Class and owl:Class, find the > "Up" button in the upper right corner of the Class Hierarchy panel, to > switch to rdfs:Resource as root class. > > > > If you further want to copy values such as the definition into the > classes, you could define a property that uses a sh:path expression such as > > > > ex:glossaryTerm/rdfs:comment > > > > or declare a sh:values rule that does the same. See > https://www.linkedin.com/pulse/inferencing-shacl-using-shvalues-holger-knublauch-0metf/ > for > some background on sh:values rules. > > > > HTH > > Holger > > > > > > On 23 Feb 2024, at 8:28 am, 'Luis Enrique Ramos García' via TopBraid Suite > Users <[email protected]> wrote: > > > > Hi guys, > > > > I wonder if there is a way to link glossaries to ontologies. > > > > I mean, let's say I have a group of geographical terms in a list, that I > create as glossary, and then I would like to use this glossary definition > to fill the skos:definition of the corresponding class (concept) in my > ontology. > > Could you share any documentation or example of how I could do that?. > > > > Best regards > > > > > > Luis Ramos. > > > > -- > The topics of this mailing list include TopBraid EDG and related > technologies such as SHACL. > To post to this group, send email to [email protected] > --- > 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/91b23e2e-9d7b-4c6a-8d08-423bff8fc06fn%40googlegroups.com > <https://groups.google.com/d/msgid/topbraid-users/91b23e2e-9d7b-4c6a-8d08-423bff8fc06fn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > > > > -- > The topics of this mailing list include TopBraid EDG and related > technologies such as SHACL. > To post to this group, send email to [email protected] > --- > 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/D7053F4F-B98B-447C-BE19-15BB85F8F796%40topquadrant.com > <https://groups.google.com/d/msgid/topbraid-users/D7053F4F-B98B-447C-BE19-15BB85F8F796%40topquadrant.com?utm_medium=email&utm_source=footer> > . > > > > -- > The topics of this mailing list include TopBraid EDG and related > technologies such as SHACL. > To post to this group, send email to [email protected] > --- > 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/F30E7BFA-A12D-4F53-B906-902837DD596A%40topquadrant.com > <https://groups.google.com/d/msgid/topbraid-users/F30E7BFA-A12D-4F53-B906-902837DD596A%40topquadrant.com?utm_medium=email&utm_source=footer> > . > > -- > The topics of this mailing list include TopBraid EDG and related > technologies such as SHACL. > To post to this group, send email to [email protected] > --- > 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/GVXP192MB19041B9055F4AD552227904DF0552%40GVXP192MB1904.EURP192.PROD.OUTLOOK.COM > <https://groups.google.com/d/msgid/topbraid-users/GVXP192MB19041B9055F4AD552227904DF0552%40GVXP192MB1904.EURP192.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> > . > -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- 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/CABy94XnD7Dzy-hsYu_Z47m0YUj7an9uOx%2BSapmJvX4R0NAc4mA%40mail.gmail.com.
