You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<term-secid="sec_3.6">
<label>3.6</label>
<tbx:termEntryid="term_3.6">
<tbx:langSetxml:lang="en">
<tbx:subjectField>dispute resolution</tbx:subjectField>
<tbx:definition> disagreement, arising from a <tbx:entailedTermtarget="term_3.3">complaint (3.3)</tbx:entailedTerm>, submitted to a <tbx:entailedTermtarget="term_3.9">provider (3.9)</tbx:entailedTerm>
</tbx:definition> ... </term-sec>
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.
The text was updated successfully, but these errors were encountered:
Source: #190
XML example:
From
9.3.9 Subject fields of a terminological entry
:In Metanorma this entity means
domain
: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.The text was updated successfully, but these errors were encountered: