Closed mico closed 1 year ago
Since users can utilize these references we need to parse them.
@ronaldtse @andrew2net do we have other identifiers like this?
@mico I’m not actually sure, but there probably are.
For “Regulatory Publications” (https://www.itu.int/pub/R-REG) there are other documents:
I can add to parser all this publications, but if they will add something else I'll need to update parser. If we use something like “ITU-R REG-RR”, “ITU-R REG-RTX”, “ITU-R REG-RR5”, etc. I don't need to add all these publications to parser, and it can accept any symbols after “ITU-R REG-”.
@ronaldtse what do you think? Why do we decide to use “ITU-R RR” without “REG”?
Why do we decide to use “ITU-R RR” without “REG”?
It's not our decision so we cannot speculate... we just have to accept it and produce that as given.
We need to also be aware that ITU-D, ITU-R and ITU-T use different identifier patterns (even for the same document type).
As I understand this is the identifier's document here: https://search.itu.int/history/HistoryDigitalCollectionDocLibrary/1.44.48.en.104.pdf
So it's a compilation of documents related to Radio Regulations. (also here https://www.itu.int/en/publications/Pages/publications.aspx?lang=en&media=electronic&parent=R-REG-RR-2020)
Identifier in URL: "R-REG-RR-2020".
So this is not a standard identifier, should we still parse it?