Hi Pat, You could create a bridge ontology between your ad hoc local ontology and SNOMED, but since your ad hoc ontology is under your control creating a mapping property is probably the most straight forward (not reusable but straight forward) approach. We have created bridge ontologies between curated ontologies, such as OBO DIOD, SYMP, and FMA ontologies, and others, that could have been reusable by a larger community as well as by our own ad hoc local ontologies. Bridges ontologies, their creation, choices and variants, strengths and weaknesses, are well documented in the literature and you may already be familiar with them.
Jack Hodges, Siemens On Friday, April 5, 2019 at 6:20:34 AM UTC-7, Pat Bell wrote: > > Apologies in advance because I suspect this question comes up quite often > but I haven't found anything directly appropriate. > > I have created a set of local taxonomies, and I want to show how the > concepts in those taxonomies might map against SNOMED CT. For various > reasons, I'm trying to avoid creating an instance of SNOMED in our topbraid > installation, but the various mapping functions (crosswalks and the > matching fields) seem to require me to do that. > > If I'm adamant I won't load SNOMED CT into topbraid, what is the most > sensible next-best solution I can apply? > -- 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. For more options, visit https://groups.google.com/d/optout.
