Thanks Irene ! Simon
On Wednesday, May 22, 2019 at 10:05:14 AM UTC+10, Irene Polikoff wrote: > > Business terms in a glossary are typically expected to be mapped to some > logical or physical data elements. The use case is to create some common > set of business definitions (e.g., customer ID) and connect them to data > sources that store customer IDs and, more specifically to the data elements > in the source that store them. > > Further, business glossaries typically capture business rules about these > assets e.g., customer ID is always 9 characters, etc. And other information > that applies to data mapped to the term irrespective of where is stored. > For example, the fact that email addresses are personally identifiable > information, that certain regulations apply to data that corresponds to the > term, etc. > > > On May 21, 2019, at 7:22 PM, Simon Opper <[email protected] <javascript:>> > wrote: > > Thanks very much for your advice Irene. > > My feeling is that non-technical SMEs favour to work on flat vocab/term > lists in glossary and introducing even a simple taxonomy and minimal skos > concepts weeds out many people, placing the job of hierarchical taxonomy > development more with technical users and a knowledge architect to bring it > together. This use case was what was driving me to be able to easily work > with non-tech users in a glossary but then pull it into more structured > assets over time with maximum re-use out of the box. Your simple > suggestions help me do that. > > > Cheers > > Simon > > On Thursday, May 16, 2019 at 5:01:13 PM UTC+10, Simon Opper wrote: >> >> Hi folks >> >> I'm looking to sanity check my understanding of the re-use of terms >> between taxonomies, glossaries, other assets and ontologies in EDG. >> >> If I understand the EDG documentation correctly: >> >> - glossary terms can trace to other terms via the "traces to" >> property - ok and have this working >> - glossary terms can be mapped to another data asset type by the >> "maps to term" property - ok and have this working >> >> But I'm unclear on how to re-use glossary terms (in a bidirectional) way >> with taxonomy. >> >> - adding a taxonomy to the includes of a glossary doesn't bring the >> concepts in. >> - adding a glossary to the includes of a taxonomy also doesn't bring >> in terms in the opposite direction. >> >> I'm guessing a result of the import rules between the two model >> ontologies. >> >> Sure, the taxonomy can be exported as a spreadsheet and imported into a >> glossary but this seems against the grain and disconnects the two assets. >> >> >> 1. So.... is there a recommended approach or workflow to develop >> glossary, taxa and other asset types ? e.g. begin at glossary, add some >> shapes??, import/include to taxonomy and then consume in other assets >> 2. Is there a direct way extract/annotate/use shapes/magic >> properties/transform taxa and glossaries to inter-operate with each other >> ? >> >> >> Finally, regarding ontologies and asserting classes as skos concepts I've >> done some reading, gone down the rabbit hole and come back out with the >> understanding that avoid to messy and un-intended entailment issues this >> type of assertion is to be avoided. >> >> So leaving class and skos assertions behind: >> >> 3. how then does one re-use the labels from a glossary or taxonomy when >> developing ontologies ? It seems manual to me so far unless I'm missing >> something. >> >> 4.Can existing taxa or gloss labels be made available to pick at the time >> of ontology class, property and attribute creation ? >> >> >> Once an ontology is created, I assume but haven't got on to testing, that >> cross walks and/or EDG search can perform some entity matching and >> recommendation. Hence hopefully close the loop back to gloss or taxa terms. >> Is this right ? >> >> Many thanks in advance ! >> >> Simon >> >> >> > -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/85330630-78c0-4893-bfd4-2a7e4678a1ea%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/85330630-78c0-4893-bfd4-2a7e4678a1ea%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/6d15e7fc-34fb-4109-afda-468421e14961%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
