Open ronaldtse opened 1 week ago
The error is different: the terms are not being recognised as terms at all:
<clause id="_terms_related_to_specific_technologies" obligation="normative">
<title>Terms related to specific technologies</title>
<clause id="_calendar_data_formats" obligation="normative">
<title>Calendar data formats</title>
<clause id="_icalendar" obligation="normative">
<title>iCalendar</title>
<p id="_f659ec5d-98f0-a569-e214-ae67c6afbc49">standard format for representing calendar data</p>
That is because Metanorma has inherited from ISO the constraint that there is only one Terms and Definitions section per document, outside of ISO/IEC vocabulary documents; and 03-22-misc.adoc is marked up as a distinct sister clause to the Terms and Definitions clause, not a subclause of it.
If I comment out that bit:
//[heading=terms and definitions]
//== Terms related to specific technologies
The concepts process fine, because the "Calendar data formats" are recognised as terms fine.
So we have two alternatives:
include::03-22-misc.adoc[leveloffset=+1]
), because CC doesn't know about vocabulary documents, and the Metanorma constraint that there can be only one Terms section per document is good and needs to be preempted in markup@ronaldtse Which do you want?
Given that vocabulary documents are quite widespread amongst SDOs, perhaps it is easier if we relax the "one terms section only per document" rule.
For this particular document, I am planning to also cross-publish to ISO as a proper vocabulary document, so I prefer keeping the same structure across documents.
These errors have gone away with the fix to standoc, as the clause is now recognised as a second terms clause.
We now have a different error: isodoc still is expecting to find a single terms section, so the second term section is not getting any anchors processed for it.
Have addressed that issue too.
Errors:
And this also causes metanorma-ietf to crash.
The way to work with vocabulary documents is documented here: