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

ISO/IEC Coding Guidelines: subject fields of a terminological entry #234

Closed
Intelligent2013 opened this issue Sep 7, 2022 · 1 comment
Closed
Assignees
Labels
enhancement New feature or request

Comments

@Intelligent2013
Copy link
Contributor

Intelligent2013 commented Sep 7, 2022

Source: #190

XML example:

<term-sec id="sec_3.6">
	<label>3.6</label>
	<tbx:termEntry id="term_3.6">
		<tbx:langSet xml:lang="en">
			<tbx:subjectField>dispute resolution</tbx:subjectField>
			<tbx:definition> disagreement, arising from a <tbx:entailedTerm target="term_3.3">complaint (3.3)</tbx:entailedTerm>, submitted to a <tbx:entailedTerm target="term_3.9">provider (3.9)</tbx:entailedTerm>
			</tbx:definition> ... </term-sec>

image

From 9.3.9 Subject fields of a terminological entry:

In legacy documents, there may be cases where the definition of a term starts with text enclosed in angle brackets 〈…〉.

In Metanorma this entity means domain:

domain:[dispute resolution]

Currently, mnconvert supports domain:[...] for text in the angle brackets in the description <...> ...., and converts Metanorma XML into NISO STS <tbx:term>dispute resolution</tbx:term>. It should be fixed.

@Intelligent2013
Copy link
Contributor Author

Done.
mnconvert converts the NISO STS XML element tbx:subjectField into

domain:[dispute resolution]

and Metanorma XML:

<domain>dispute resolution</domain>

into NISO STS XML

<tbx:subjectField>dispute resolution</tbx:subjectField>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

1 participant