The Terminology Engine (v2) is a set of specifications and tools that caters for the creation and maintenance (i.e. curation) of terminologies. This repository contains the sources for the tools.
Within TOIP, and I think we should expect to see that in other contexts as well, dealing with terminology, glossaries, etc. is highly 'experimental'. One thing they are contemplating is to have a 'central glossaries repo' in which a small group of people collects glossaries from all over the place that can then be used by other working groups (and some of their haphazard tooling).
In order for TOIP to benefit from/be able to use TEv2, they could collect MRGs there (with the other stuff they have), and there should then be a TEv2-mechanism that could import such MRGs if needed. A simple solution could be to have the MRG importer have the following object (or list of such objects) added to its configuration file:
a URL pointing to the repo-path where the collection of MRGs is located.
a list of terminology-identifiers using the following syntax:
<stag> which would import all files named mrg.<stag>*.yaml (all MRGs with scopetag <stag>)
<stag>:<vtag> which would import the file mrg.<stag>.<vtag>.yaml (if it exists)
Doing this may require that the user specifies whether to use this way of importing, or the traditional way, or perhaps both (to be decided)
Within TOIP, and I think we should expect to see that in other contexts as well, dealing with terminology, glossaries, etc. is highly 'experimental'. One thing they are contemplating is to have a 'central glossaries repo' in which a small group of people collects glossaries from all over the place that can then be used by other working groups (and some of their haphazard tooling).
In order for TOIP to benefit from/be able to use TEv2, they could collect MRGs there (with the other stuff they have), and there should then be a TEv2-mechanism that could import such MRGs if needed. A simple solution could be to have the MRG importer have the following object (or list of such objects) added to its configuration file:
<stag>which would import all files namedmrg.<stag>*.yaml(all MRGs with scopetag<stag>)<stag>:<vtag>which would import the filemrg.<stag>.<vtag>.yaml(if it exists)Doing this may require that the user specifies whether to use this way of importing, or the traditional way, or perhaps both (to be decided)