Add ISO identifiers, dated, undated references and reference number to docid

[ronaldtse]

The proposal here is to provide 3 types of docids for a document.

• ISO "Reference number" (reference PubID): ISO 10303-52:2011(E)
• ISO dated reference (dated PubID): ISO 10303-52:2011
• ISO undated reference (undated PubID): ISO 10303
• ISO machine readable reference (RFC 5141 "ISO URN"): urn...

This will solve issues such as #607 and also consolidate all identifiers under the docid attribute in a Bibitem.

Originally posted by @ronaldtse in metanorma/metanorma-iso#607 (comment)
Posted to: metanorma/metanorma-iso#608

[ronaldtse]

@andrew2net #607 has been completed. What needs to be done here? Thanks.

[andrew2net]

@ronaldtse it seems dated and undated references could be derived from a primary ID, couldn't it?
Machine-readable reference provided by ISO

    <docidentifier type="ISO" primary="true">ISO 19115-2:2019</docidentifier>
    <docidentifier type="URN">urn:iso:std:iso:19115:-2:stage-60.60:ed-2:en,fr</docidentifier>

[ronaldtse]

it seems dated and undated references could be derived from a primary ID, couldn't it?

docidentifier should provide all three:

ISO "Reference number" (reference PubID): ISO 10303-52:2011(E)
ISO dated reference (dated PubID): ISO 10303-52:2011
ISO undated reference (undated PubID): ISO 10303

You can separate by type, e.g. type="ISO" scheme="undated" type="ISO" scheme="refnum" type="ISO" scheme="dated".

[andrew2net]

You can separate by type, e.g. type="ISO" scheme="undated" type="ISO" scheme="refnum" type="ISO" scheme="dated".

@ronaldtse ok but we don't have a scheme attribute in the RelatonBib model. We have scope.

[andrew2net]

@ronaldtse what's the difference between "reference PubID" and "dated PubID"?
It seems in many cases they are identical. Do we need to have both refnum and dated PubIDs if they are identical?

[ronaldtse]

what's the difference between "reference PubID" and "dated PubID"?

ISO "Reference number" (reference PubID): ISO 10303-52:2011(E)
ISO dated reference (dated PubID): ISO 10303-52:2011

The "Reference number" includes the language code.

[ronaldtse]

[andrew2net]

There isn't a language in the references on the ISO search page. Moreover, in the RelatonBib model, we have translated metadata inside documents. We don't have separate document for each translation, so we don't use references with language.

[ronaldtse]

@andrew2net there are actually two needs here.

1. Metanorma needs to encode the "Reference number" in Relaton.

2. Some documents are available in multiple languages

If you click on "Preview", you will be sent to the ISO OBP.

Standards only in one language does not have language buttons.
https://www.iso.org/obp/ui/#iso:std:iso:8601:-1:ed-1:v1:en

ISO 6709 is in multiple languages, and you can see the URL change with the URN:

https://www.iso.org/obp/ui/#iso:std:iso:6709:ed-2:v1:en

https://www.iso.org/obp/ui/#iso:std:iso:6709:ed-2:v1:fr

https://www.iso.org/obp/ui/#iso:std:iso:6709:ed-2:v1:ru

I think we should allow people to put in the ISO URN to cite the correct reference (by language), in addition to the language-less resource.

[andrew2net]

@ronaldtse I've inspected the OPB preview page. It uses JavaScrip heavily. We can try to reverse engineer it and fetch metadata using the Web app API. But there is an easier, simpler, and faster way: ISO API Portal.
The problem is that they allow only staff employed by the ISO member. Is it possible for Ribose to get access to the API?