Skip to content
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

Make MRGT/HRGT work without TRRT (or other (new) tools) #30

Open
RieksJ opened this issue Jan 9, 2025 · 0 comments
Open

Make MRGT/HRGT work without TRRT (or other (new) tools) #30

RieksJ opened this issue Jan 9, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request impact: MRGT This issue has an impact on the MRGT impact: specifications impact: TRRT

Comments

@RieksJ
Copy link
Member

RieksJ commented Jan 9, 2025

Currently, an MRG entry has fields that are needed to accommodate for term ref resolution. Examples include 'locator', and 'website'.

There are situations in which term ref resolution is not needed; the tools are simply used to generate MRGs and HRGs from them.

To better accommodate such situations, it should be possible to have CTEXT headers (and MRG entries) to ONLY have fields that are relevant for the contexts in which they will be used. That would obviously include MRG-generation, but whatever else would be relevant depends on context.

It seems as if the following terms would remain 'required', and the rest not (to be verified):

  • scopetag
  • vsntag
  • termid
  • term
  • termType
@RieksJ RieksJ added documentation Improvements or additions to documentation enhancement New feature or request impact: MRGT This issue has an impact on the MRGT impact: TRRT impact: specifications labels Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request impact: MRGT This issue has an impact on the MRGT impact: specifications impact: TRRT
Projects
None yet
Development

No branches or pull requests

1 participant