ISO/IEC Coding Guidelines: process editing-instruction in MN to STS XML

[Intelligent2013]

Source: #190

As titled. Currently, mnconvert doesn't generate editing-instruction from editor's notes.

[Intelligent2013]

In Metanorma there are 3 types of annotations:

• Editor’s notes

EDITOR: The contents of this clause will be changed in conjunction with the UML.

<admonition id="_" type="editorial">
   <p id="_">The contents of this clause will be changed in conjunction with the UML.</p>
</admonition>

NISO XML expected format:

<editing-instruction>
<p>The contents of this clause will be changed in conjunction with the UML.</p>
</editing-instruction>

• To-dos

TODO: Revise introduction.

<review date="2022-10-12T00:00:00Z" id="_" reviewer="(Unknown)">
                <p id="_">Revise introduction.</p>
</review>

NISO XML expected format:

<editing-instruction specific-use="review">
<p>Revise introduction.</p>
</editing-instruction>

• Reviewer notes

[reviewer=ISO,date=2017-01-01,from=foreword,to=foreword]
****
A Foreword shall appear in each document. The generic text is shown here. It does not contain requirements, recommendations or permissions.
****

<review date="2017-01-01T00:00:00Z" from="foreword" id="_" reviewer="ISO" to="foreword">
	<p id="_">A Foreword shall appear in each document. The generic text is shown here. It does not contain requirements, recommendations or permissions.</p>
</review>

NISO XML expected format:

<editing-instruction specific-use="review">
<p>A Foreword shall appear in each document. The generic text is shown here. It does not contain requirements, recommendations or permissions.</p>
</editing-instruction>

[Intelligent2013]

mnconvert updated. Now it generates editing-instruction for Metanorma XML elements:

• admonition[@type = 'editorial'], and
• review