-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terms and definitions: allow authors to import a term from a glossary #34
Comments
This issue now relates to this: metanorma/metanorma-standoc#154 |
OGC Glossary maintenance needs to be factored into this - the Glossary should be collated automatically from normative content managed through the OGC Naming Authority, which assigns identifiers to concepts. There are a range of abstract concepts that emerge from more informal processes. The OGC Glossary is available at http://www.opengis.net/def/glossary and can potentially be delivered in any format required. for example in TTL or as JSON (as JSON-LD semantically annotated using SKOS model) https://www.opengis.net/def/glossary?_profile=conceptscheme&_mediatype=application/ld%2Bjson Note if python code to convert one of these to an XML format can be supplied we can arrange to generate that format in addition and advertise it as an available format. (best for someone familar with and abl;e to validate the XML format undertake this) |
The issue also relates to metanorma/metanorma#75 OGC Staff briefed on 2023-09-04. |
There is also a role to play by the glossarist-ruby gem. |
Pending debugging of metanorma-plugin-glossarist: see metanorma/metanorma#75 |
2025-01-07 Glossarist has been reimplemented and is now more extensible. @ronaldtse will provide a demo ahead of the next OGC Member Meeting. |
Thanks @ghobona . For reference, the reimplementation is in reference to: |
Very often a standards author needs to import a term from the OGC glossary.
It is however an annoyance to copy/paste/re-type/re-format the term, definition, source, notes and examples.
This ticket is to:
Establish a Metanorma AsciiDoc syntax to automate this process
Allow Metanorma to import a term into a document (TBX, RDF/SKOS, Metanorma Term...)
Allow the author to override a term from the glossary while maintaining a reference to the unmodified source.
The glossary can be “cited” and used as an authoritative source, i.e. “[SOURCE: OGC Glossary x.y version z]” (something like that)
If a term exists in the OGC glossary, and is being used in the document, but does not provide a reference to the term, Metanorma can produce a warning to that effect.
The text was updated successfully, but these errors were encountered: