Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable mnconvert to generate NISO STS (and confirm compliant with IEC format) #95

Closed
Tracked by #111
ronaldtse opened this issue Nov 16, 2021 · 9 comments
Closed
Tracked by #111
Assignees
Labels
enhancement New feature or request

Comments

@ronaldtse
Copy link
Contributor

metanorma/metanorma-iec#111

@Intelligent2013
Copy link
Contributor

mnconvert updated and v.1.13.0 released: https://github.com/metanorma/mnconvert/releases/tag/v1.13.0
Example of resulted NISO STS xml:
iec-60050-192.sts.niso.zip

@ronaldtse
Copy link
Contributor Author

ronaldtse commented Nov 17, 2021

We also need to confirm that the NISO STS generated is conformant to IEC style. They have provided their STS documents here: https://github.com/metanorma/mn-samples-iec-private.

@Intelligent2013 can you help confirm the generated output? Thanks.

Because they need to run our generated STS into their STS -> PDF toolchain.

@ronaldtse ronaldtse changed the title Enable mnconvert to generate NISO STS Enable mnconvert to generate NISO STS (and confirm compliant with IEC format) Nov 17, 2021
@Intelligent2013
Copy link
Contributor

Intelligent2013 commented Nov 17, 2021

IEC uses another/new xml structures:

  • std-meta (it's not 100% compatible with iso-meta)
  • new element std-id-group
  • another structure for copyright data
  • foreword includes data from legal-statement + foreword
  • std
  • reference to non-standard in <mixed-citation> (bibliography section)
  • new element self-uri
  • new element editing-instruction

In metanorma xml there aren't data for :

  • @std-meta-type
<std-meta std-meta-type="international">
  • 64291 is number of some another document (not current)
<std-id-group>
	<std-id originator="IEC" std-id-link-type="id" std-id-type="dated">iec:pub:64291</std-id>
	<std-id originator="IEC" std-id-link-type="ooi" std-id-type="dated">64291</std-id>
	...
</std-id-group>

(example from "iec62830-8{ed1.0}en.xml")

  • page count
<counts>
	<page-count count="36"/>
</counts>

@Intelligent2013
Copy link
Contributor

Intelligent2013 commented Nov 17, 2021

Regarding <editing-instruction>, there are 3 kind in (`iec63159-2-2{ed1.0}en.xml):

  • Addition
<editing-instruction>
<p id="p-25">
<italic>Addition:</italic>
</p>
</editing-instruction>
  • Replacement
<editing-instruction>
<p id="p-35">
<italic>Replacement:</italic>
</p>
  • Modification
<editing-instruction>
<p id="p-48">
<italic>Modification:</italic>
</p>
</editing-instruction>

In the metanorma (https://www.metanorma.org/author/topics/document-format/changes/) there are:

  • add
  • modify (If the change attribute has the value modify, the replacement text needs to be provided.)
  • delete

I.e. mapping table between Metanorma and STS XML is:

@Intelligent2013
Copy link
Contributor

@ronaldtse resulted STS NISO examples: IEC.NISO.STS.zip

@ronaldtse
Copy link
Contributor Author

Thank you @Intelligent2013 !

Ping @opoudjis re: #95 (comment)

@ronaldtse
Copy link
Contributor Author

@Intelligent2013 is this done? Then we can close it, thanks.

@Intelligent2013
Copy link
Contributor

Done.

@ronaldtse
Copy link
Contributor Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants