metanorma / mn-samples-iso Goto Github PK

ISO 17301-1:2023 uses URIs with HTTPS protocol throughout the document.

ISO 17301-1:2023/Amd uses URIs with HTTP protocol throughout the document.

Considering these URIs are used in the predefined text as well (e.g. copyright statement, first part of the Foreword that applies to all committees, intro of the Terms and definitions), I believe these should be consistent. What would be the correct choice? Based on the redirection to https://(...), it should be HTTPS.

The amendment is currently encoded to follow the rules of the original document. Please let me know if this should be adjusted.

From #89

This involves finding the exact differences in the English files, and then updating the French files from 2016 to 2023.

We current have a Rice sample in Chinese Simplified. However there's a warning when compiling it.

Document Attributes: Hans is not a recognised script

I have requested a copy from ISO.

Table 1 includes the following elements:

• notes
• footnotes
• abbreviations

They are ordered as above in the original document.

However, they cannot be properly generated if the abbreviation is put last

using the following markup (same result without [%key]; footnotes are added inline):

NOTE: Ce tableau est basé sur l'<<ISO7301,table=1>>.

NOTE: Certains contrats commerciaux peuvent exiger des complémentaires à celles fournies dans le présent tableau.

NOTE: Seul le riz (cargo) rouge entièrement décortiqué est pris en considération dans le présent tableau.

[%key]
N/A:: N'est pas applicable.

I believe it is not intended to use [%key] after the notes. Therefore, these elements are encoded in the following order:

• abbreviations
• notes
• footnotes

and generated like this:

Is it fine to keep the current encoding, or we need to address this issue as a request for enhancement/a bug?

From #89

This involves finding the exact differences in the English files, and then updating the Chinese files from 2016 to 2023.

As in title.

The fonts used on PDF are wrong right now -- we need to have Cambria installed. Refer to mn-native-pdf (its GHA) for fonts to be installed.

https://github.com/metanorma/mn-samples-iso/pull/66/checks?check_run_id=2378612873

2021-04-19T07:46:56.0744104Z Document Attributes:  is not a recognised iteration
2021-04-19T07:46:56.5965012Z C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/ruby-jing-0.0.1/lib/jing.rb:127:in `split': invalid byte sequence in UTF-8 (ArgumentError)
2021-04-19T07:46:56.5966813Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/ruby-jing-0.0.1/lib/jing.rb:127:in `parse_output'
2021-04-19T07:46:56.5967964Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/ruby-jing-0.0.1/lib/jing.rb:88:in `validate'
2021-04-19T07:46:56.5969296Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-standoc-1.9.0/lib/asciidoctor/standoc/validate.rb:85:in `block in schema_validate'
2021-04-19T07:46:56.5970546Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/2.4.0/tempfile.rb:295:in `open'
2021-04-19T07:46:56.5971769Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-standoc-1.9.0/lib/asciidoctor/standoc/validate.rb:81:in `schema_validate'
2021-04-19T07:46:56.5973214Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-iso-1.8.0/lib/asciidoctor/iso/validate.rb:268:in `validate'
2021-04-19T07:46:56.5974591Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-standoc-1.9.0/lib/asciidoctor/standoc/base.rb:182:in `makexml'
2021-04-19T07:46:56.5976041Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-standoc-1.9.0/lib/asciidoctor/standoc/base.rb:154:in `document'
2021-04-19T07:46:56.5977454Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-standoc-1.9.0/lib/asciidoctor/standoc/utils.rb:14:in `convert'
2021-04-19T07:46:56.5978914Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/asciidoctor-2.0.13/lib/asciidoctor/document.rb:938:in `convert'
2021-04-19T07:46:56.5980205Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/asciidoctor-2.0.13/lib/asciidoctor/convert.rb:119:in `convert'
2021-04-19T07:46:56.5981480Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-1.3.0/lib/metanorma/input/asciidoc.rb:24:in `process'
2021-04-19T07:46:56.5982741Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-1.3.0/lib/metanorma/processor.rb:24:in `input_to_isodoc'
2021-04-19T07:46:56.5984008Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-1.3.0/lib/metanorma/compile.rb:93:in `process_input'
2021-04-19T07:46:56.5985252Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-1.3.0/lib/metanorma/compile.rb:26:in `compile'
2021-04-19T07:46:56.5986583Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/compiler.rb:45:in `compile_file'
2021-04-19T07:46:56.5987926Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/compiler.rb:30:in `compile'
2021-04-19T07:46:56.5989262Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/compiler.rb:35:in `compile'
2021-04-19T07:46:56.5990622Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/site_generator.rb:81:in `compile'
2021-04-19T07:46:56.5992032Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/site_generator.rb:28:in `block in generate'
2021-04-19T07:46:56.5993435Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/site_generator.rb:28:in `each'
2021-04-19T07:46:56.5994791Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/site_generator.rb:28:in `generate'
2021-04-19T07:46:56.5996197Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/site_generator.rb:23:in `generate'
2021-04-19T07:46:56.5997566Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli/commands/site.rb:25:in `generate'
2021-04-19T07:46:56.5998845Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
2021-04-19T07:46:56.5999963Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-hollaback-0.2.0/lib/thor/hollaback.rb:62:in `run'
2021-04-19T07:46:56.6001164Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
2021-04-19T07:46:56.6002252Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
2021-04-19T07:46:56.6003461Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor/invocation.rb:116:in `invoke'
2021-04-19T07:46:56.6004549Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor.rb:243:in `block in subcommand'
2021-04-19T07:46:56.6005709Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
2021-04-19T07:46:56.6006848Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-hollaback-0.2.0/lib/thor/hollaback.rb:62:in `run'
2021-04-19T07:46:56.6008131Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
2021-04-19T07:46:56.6009212Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
2021-04-19T07:46:56.6010238Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
2021-04-19T07:46:56.6011346Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/lib/ruby/gems/2.4.0/gems/metanorma-cli-1.4.7.1/lib/metanorma/cli.rb:67:in `start'
2021-04-19T07:46:56.6012375Z 	from C:/Users/RUNNER~1/AppData/Local/Temp/ocr22CD.tmp/src/metanorma:198:in `<main>'
2021-04-19T07:46:59.7992544Z ##[error]Process completed with exit code 1.

Check how https://github.com/riboseinc/csand-devsecops-whitepaper does it with Travis and Gitlab.

Add badge to README too.

The website URI in the Copyright statement of the ISO Rice Amendment (2023) is broken. It points to http://www.iso.orgPublished which is an unreachable link. Maybe we should inform ISO about this?

The metanorma setup command probably should have be run?

I am the covenor related to updating ISO 5598 which is a three column document. Do you know if Metanorma can support such a document? How would you recommend managinga three language document with Metanorma?

ISO 5598 on the Online Browsing Platform

The working group likes seeing the definitions side by side:

With this set of issues, if you cannot remove the embedded assets, don't, but we will not accept crossreferences to nested assets.

You are looking for errors in the error logs that look like:

Compiling /metanorma/sources/directives/part2/document.adoc

Syntax: (XML Line 000870): There is an instance of example nested within table
Syntax: (XML Line 000876): There is an instance of example nested within table
Syntax: (XML Line 000879): There is an instance of example nested within table
Syntax: (XML Line 000903): There is an instance of example nested within table
Syntax: (XML Line 000929): There is an instance of example nested within table
Syntax: (XML Line 000932): There is an instance of example nested within table
Syntax: (XML Line 000963): There is an instance of example nested within table
Syntax: (XML Line 000966): There is an instance of example nested within table
Syntax: (XML Line 000969): There is an instance of example nested within table
Syntax: (XML Line 000972): There is an instance of example nested within table
Syntax: (XML Line 000996): There is an instance of example nested within table
Syntax: (XML Line 001002): There is an instance of example nested within table
Syntax: (XML Line 001240): There is an instance of figure nested within example
Syntax: (XML Line 001347): There is an instance of table nested within example
Syntax: (XML Line 001386): There is an instance of table nested within example
Syntax: (XML Line 001400): There is an instance of table nested within example
Syntax: (XML Line 001417): There is an instance of table nested within example
Syntax: (XML Line 001993): There is an instance of table nested within example
Syntax: (XML Line 002008): There is an instance of table nested within example
Syntax: (XML Line 002018): There is an instance of table nested within example
Syntax: (XML Line 002029): There is an instance of table nested within example
Syntax: (XML Line 002479): There is an instance of table nested within example
Syntax: (XML Line 002819): There is an instance of table nested within example
Syntax: (XML Line 003008): There is an instance of formula nested within example
Syntax: (XML Line 003028): There is an instance of formula nested within example
Syntax: (XML Line 003046): There is an instance of table nested within example
Syntax: (XML Line 003048): There is an instance of formula nested within example
Syntax: (XML Line 003065): There is an instance of formula nested within example
Syntax: (XML Line 003048): There is an instance of formula nested within table
Syntax: (XML Line 003065): There is an instance of formula nested within table
Syntax: (XML Line 003084): There is an instance of table nested within example
Syntax: (XML Line 003092): There is an instance of table nested within example
Syntax: (XML Line 003094): There is an instance of formula nested within example
Syntax: (XML Line 003111): There is an instance of formula nested within example
Syntax: (XML Line 003115): There is an instance of formula nested within example
Syntax: (XML Line 003094): There is an instance of formula nested within table
Syntax: (XML Line 003111): There is an instance of formula nested within table
Syntax: (XML Line 003115): There is an instance of formula nested within table
Syntax: (XML Line 003167): There is an instance of figure nested within example
Syntax: (XML Line 003284): There is an instance of figure nested within example
Syntax: (XML Line 003314): There is an instance of figure nested within example
Syntax: (XML Line 003444): There is an instance of figure nested within example
Syntax: (XML Line 003448): There is an instance of table nested within example
Syntax: (XML Line 003630): There is an instance of table nested within example
Syntax: (XML Line 003656): There is an instance of table nested within example
Syntax: (XML Line 003671): There is an instance of table nested within example
Syntax: (XML Line 003682): There is an instance of figure nested within example
Syntax: (XML Line 003921): There is an instance of example nested within table
Syntax: (XML Line 003921): There is an instance of table nested within table
Syntax: (XML Line 003930): There is an instance of example nested within table
Syntax: (XML Line 003930): There is an instance of table nested within table
Syntax: (XML Line 003939): There is an instance of example nested within table
Syntax: (XML Line 003939): There is an instance of table nested within table
Syntax: (XML Line 003953): There is an instance of example nested within table
Syntax: (XML Line 003960): There is an instance of example nested within table
Syntax: (XML Line 003960): There is an instance of table nested within table
Syntax: (XML Line 003971): There is an instance of example nested within table
Syntax: (XML Line 003971): There is an instance of table nested within table
Syntax: (XML Line 003992): There is an instance of example nested within table
Syntax: (XML Line 003992): There is an instance of table nested within table
Syntax: (XML Line 004005): There is an instance of example nested within table
Syntax: (XML Line 004005): There is an instance of table nested within table
Syntax: (XML Line 004022): There is an instance of example nested within table
Syntax: (XML Line 004028): There is an instance of example nested within table
Syntax: (XML Line 004033): There is an instance of example nested within table
Syntax: (XML Line 004046): There is an instance of example nested within table
Syntax: (XML Line 004053): There is an instance of example nested within table
Syntax: (XML Line 004053): There is an instance of table nested within table
Syntax: (XML Line 004064): There is an instance of example nested within table
Syntax: (XML Line 004064): There is an instance of table nested within table
Syntax: (XML Line 004083): There is an instance of example nested within table
Syntax: (XML Line 004083): There is an instance of table nested within table
Syntax: (XML Line 004100): There is an instance of example nested within table
Syntax: (XML Line 004100): There is an instance of table nested within table
Syntax: (XML Line 004102): There is an instance of formula nested within table
Syntax: (XML Line 004104): There is an instance of formula nested within table
Syntax: (XML Line 004108): There is an instance of formula nested within table
Syntax: (XML Line 004110): There is an instance of formula nested within table
Syntax: (XML Line 003921): There is an instance of table nested within example
Syntax: (XML Line 003930): There is an instance of table nested within example
Syntax: (XML Line 003939): There is an instance of table nested within example
Syntax: (XML Line 003960): There is an instance of table nested within example
Syntax: (XML Line 003971): There is an instance of table nested within example
Syntax: (XML Line 003992): There is an instance of table nested within example
Syntax: (XML Line 004005): There is an instance of table nested within example
Syntax: (XML Line 004053): There is an instance of table nested within example
Syntax: (XML Line 004064): There is an instance of table nested within example
Syntax: (XML Line 004083): There is an instance of table nested within example
Syntax: (XML Line 004100): There is an instance of table nested within example
Syntax: (XML Line 004102): There is an instance of formula nested within example
Syntax: (XML Line 004104): There is an instance of formula nested within example
Syntax: (XML Line 004108): There is an instance of formula nested within example
Syntax: (XML Line 004110): There is an instance of formula nested within example
Syntax: (XML Line 004102): There is an instance of formula nested within table
Syntax: (XML Line 004104): There is an instance of formula nested within table
Syntax: (XML Line 004108): There is an instance of formula nested within table
Syntax: (XML Line 004110): There is an instance of formula nested within table
Syntax: (XML Line 004274): There is an instance of figure nested within example

Clearly ISO/IEC DIR 2 is impossible to do much with....

https://www.iso.org/files/live/sites/isoorg/files/developing_standards/docs/en/model_document-rice_model.pdf

During troubleshooting release issues on mnconvert-ruby https://github.com/metanorma/mnconvert-ruby/actions/runs/3550365759/jobs/5963710053

I have found that gh-pages branch have no documents

Originally docker workflow was responsible for GHPages publishing but now in this repo we have also https://github.com/metanorma/mn-samples-iso/actions/workflows/pages/pages-build-deployment which is missing in https://github.com/metanorma/mn-samples-iso/tree/main/.github/workflows I suppose it comes somewhere from configuration or some third-party service

@ronaldtse maybe you can share some context why was added ?

P.S. I have restarted docker manually to see if it will work

Per @ronaldtse

"""
Can you help fix the font setup in mn-samples-iso? They're using the wrong font (https://metanorma.github.io/mn-samples-iso/documents/amendment/rice-amd.wd.pdf)
"""

For @Intelligent2013

This occurs in mn-samples-iso for Rice:

• #89

// can't join two bibliographic localities with "and" currently
Calculate the crude protein content of the dry product by multiplying the value
of the nitrogen content by the conversion factor specified in
<<ISO20483,Annex C>> and <<ISO20483,Table C.1>>, that is adapted to the type of
cereals or pulses <<ref13,fn>><<ref14,fn>> and to their use.

Content should be:

• https://github.com/metanorma/mn-samples-iso/runs/3113680436?check_suite_focus=true#step:8:1694

for sources/guide/document.adoc

Anchors: (XML Line 000115): Concept GHG is pointing to , which is not a term or symbol
Anchors: (XML Line 000122): Concept GHG is pointing to , which is not a term or symbol
Concept not cross-referencing term or symbol

Cover:

Heading:

Table B.1 is completely broken:

ISO Rice Amendment (2023) cross-references a page within the document.

Should we support cross-references in the reviewer notes? PDF currently does not add a hyperlink that can be clicked.

Considering this cross-reference is actually added to point to a modified clause, and that clause gets generated within the same page in Metanorma, I found it more appropriate to use a cross-reference to the amendment's section the comment points to, i.e. to use the following markup ("Page 2 of this Amendment" is omitted):

[reviewer=ISO]
****
* In this case, the dated reference in the Normative references clause has been updated to correspond to the updated reference in Clause 8, second paragraph (<<cls8-comment>>)
****

However, this markup leads to generating a clause number (if not specified differently within the anchor), while the clause numbers are "hidden" in amendments.

Therefore, I think the following markup would be the best to use (and is currently applied), but I am not sure whether it satisfies ISO's requirements.

[reviewer=ISO]
****
* In this case, the dated reference in the Normative references clause has been updated to correspond to the updated reference in <<cls8-comment,Clause 8, second paragraph>>
****

Please let me know what you think would be the appropriate way to encode cross-references like this one.

Wording in some parts of the text was initially different in French vs English version of the document from 2016. For example, "grain ou partie de grain" (translates to "kernel or part of kernel") is used in French, while "kernel, whole or broken" is used in English.

Parts like this have not been altered when French version was updated to the 3rd edition, considering the French version of the document from 2016 was provided by ISO itself, as I was able to conclude from the tickets. Only the analogous changes found between the two editions (2016 and 2023) in English were applied to the French 2023 document.

In other words, after applying changes with this approach, the initial differences in wording remained as is, e.g.:

2016 (EN):

"The absolute difference between two independent single test results, obtained using the same method on identical test material in the same laboratory by the same operator using the same equipment within a short interval of time, shall not exceed the arithmetic mean of the values for r obtained from the interlaboratory study for husked rice in more than 5 % of cases:"

2016 (FR):

"La différence absolue entre deux résultats d’essai individuels indépendants, obtenus à l’aide de la même méthode, sur un matériau identique, soumis à essai dans le même laboratoire, par le même opérateur, utilisant le même appareillage dans un court intervalle de temps, n’excédera que dans 5 % des cas au plus la moyenne arithmétique des valeurs de r découlant de l’essai interlaboratoires"

(translates to "The absolute difference between two independent individual test results, obtained using the same method, on identical material, tested in the same laboratory, by the same operator, using the same equipment within a short time interval, will only exceed in 5% of cases at most the arithmetic mean of the r values resulting from the interlaboratory test")

2023 (EN):

"The absolute difference between two independent single test results shall not exceed the arithmetic mean of the values for the repeatability limit, r, obtained from the interlaboratory study for husked rice in more than 5 % of cases"

2023 (FR):

"La différence absolue entre deux résultats d'essai individuels indépendants, n'excédera que dans 5 % des cas au plus la moyenne arithmétique des valeurs de limite de répétabilité, r, découlant de l'essai interlaboratoires"

(translates to "The absolute difference between two independent individual test results will only exceed in 5% of cases at most the arithmetic mean of the repeatability limit values, r, resulting from the interlaboratory test")

French version from 2016 also uses "modified" additions to the sources for terms 3.11 and 3.12, which is not present in English version (neither 2016 nor 2023). These additions are kept in 2023 French version.

English (original, 2023):

English (original, 2016):

French (generated, 2016):

Are these differences expected, or these should also be matched between English and French document for the 3rd edition?

Let's consider the value of reproducing ISO Directives Part 1 in IsoDoc.

Here's the value that I can see:

• Its "Annex SL" is a template document within the document, so basically a document-in-document. This will push IsoDoc's boundaries in terms of the model and .

• It contains many variants of syntax that fulfills the rules stated in Directives Part 2, so this will make sure our output works.

• Directives Part 1 is a normative reference for ISO so it would have at least some symbolic meaning.

Thoughts? @opoudjis

Files here:

• iso-17301-1-amd-1-2023.pdf
• model_amendment-rice_model-202312.pdf

@anermina can you please help do the blog post for the new Rice docs? Thanks.

reference-docs/model_amendment-rice_model.pdf has been uploaded, @metanorma/editors can someone help create the sample for amendments?

I believe the template for authoring an amendment and a corrigenda is identical.

From: metanorma/metanorma-gb#52

The original document lists the following normative references:

In all places except from the following, they are cross-referenced as listed in the Normative references.

These exceptions are by Metanorma's default encoded as in Normative references. Is there a specific reason why these should be manually encoded differently?

Set lang to fr, all autofilled terms must be in French too.