Clash of docidentifiers

[strogonoff]

Here are two docs with the same primary docidentifier. The sources are in slightly different directories (one has -v1 and the other one -v1.1), but directory names are not relevant. However, docidentifiers are relevant.

Primary docidentifier is not expected to be shared by two published documents, even if they are versions of the “same” document. IETF identifiers handle this with numerical suffixes like -00, -01.

[ronaldtse]

Primary docidentifier is not expected to be shared by two published documents, even if they are versions of the “same” document. IETF identifiers handle this with numerical suffixes like -00, -01.

It's a little bit more confusing than a strict "a new revision of a document needs a new document identifier" because it's not always the case in some SDOs. For example, IEC documents continue to use the same doc identifier even when they include a Corrigendum document inside, but they apply an additional "patch version" inside the XML (which is unfortunately not visible externally)...

Can we either:

1. Call the new version CC/Adv 0707.1:2007
2. Differentiate the version (I think the version is encoded... or not?)

[strogonoff]

It looks like currently the version is not encoded in primary docidentifier, if we can include it then that would help get CC running on Firelight.

[ronaldtse]

In this case let’s change the document identifier to make it work first. It is rare that a CC document uses versions because it was not previously defined but maybe that is something we need to think about.

[strogonoff]

That works for me, but I’m not sure how to proceed. I haven’t been actively authoring this document so I am not sure how it works, where the document is originally specified and what are all the places that it needs to be updated.

[ronaldtse]

I wonder if it works by just changing this line to 0707.1:

cc-admin-documents/sources/cc-0707-edst-reflections-v1.1/document.adoc

Line 2 in d7531ce

:docnumber: 0707

[strogonoff]

Is it allowed by docid schema or going to break any external consumers?

[ronaldtse]

@strogonoff I don't know... I'll try and report back

[ronaldtse]

It worked!

<docidentifier primary="true" type="CalConnect">CC/Adv 0707.1:2007</docidentifier>
<docnumber>0707.1</docnumber>

I'll make a PR.

[ronaldtse]

I've pushed to #35

[strogonoff]

Nice! I deleted cache and re-ran workflow, because it seems that MN cache in GHA was not updated after the build.

[strogonoff]

@ronaldtse It’s deployed at https://calconnect.github.io/cc-admin-documents/.