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
"20220721" is the date when the package was generated
This command can also be used by a new GitHub Action that automatically builds the package on a Git tag in a metanorma document repository. Then the user can do:
Push git tag of v50.00.20220721
The workflow will build the document and upload the contents (the submission package) to that release.
The text was updated successfully, but these errors were encountered:
Only ISO and IEC utilize Harmonized Stage Codes. Other organizations like OGC have their own stage codes. So the packaging mechanism / file name patterns will have to be different per flavor.
Note that metanorma-iso already validates for this.
Simply validating the file names is not useful by itself -- what is useful is to compile the set of images together for submission to ISO/CS in one archive. The DRG directives specify the folder name as well as file names. The current validation scheme does not actually follow those rules.
In ISO, there are defined "submission points" for a document to be sent to ISO/CS editors.
These are the steps that a "submission package" is necessary:
At any of these stages, a user can type "metanorma package" and then Metanorma will generate a submission package.
The submission package should contain:
File names of the figures:
I also want to generate the "name" of the package, which can be named like this:
(ISO 34000: https://github.com/CalConnect/iso-34000)
Where:
This command can also be used by a new GitHub Action that automatically builds the package on a Git tag in a metanorma document repository. Then the user can do:
The text was updated successfully, but these errors were encountered: