Fetching Cor and Amd documents

[ronaldtse]

We currently don't handle Cor and Amd documents. We should do so. Here are the examples.

Amd: (an Amendment document on a standard)

• ISO 3964:2016/Amd 1:2018 https://www.iso.org/standard/73624.html
• ISO 8124-3:2010/Amd 2:2018 https://www.iso.org/standard/74083.html
• ISO/IEC 14496-12:2015/Amd 2:2018 https://www.iso.org/standard/71851.html

Amd + CD: (in progress development of an Amendment document)

• ISO 14040:2006/CD Amd 1 https://www.iso.org/standard/76121.html

Cor: (a Correction document on a standard)

• ISO/IEC 27001:2013/Cor 2:2015 https://www.iso.org/standard/69378.html
• ISO 14155:2011/Cor 1:2011 https://www.iso.org/standard/59992.html
• ISO/IEC 2022:1994/Cor 1:1999 https://www.iso.org/standard/31104.html
• ISO/IEC 8825-4:2015/Cor 1:2018 https://www.iso.org/standard/73971.html

Cor + CD: (in progress development of a Correction document)

• ISO/IEC 9075-4:2016/CD Cor 1 https://www.iso.org/standard/75937.html

Cor + Amd: (i.e. Correction document of an Amendment document)

• ISO/IEC 19794-2:2005/Amd 1:2010/Cor 2:2014 https://www.iso.org/standard/64755.html
• ISO/IEC 26300:2006/Amd 1:2012/Cor 1:2014 https://www.iso.org/standard/66550.html

From https://github.com/riboseinc/tc211-termbase/issues/7#issuecomment-508964886

[andrew2net]

@ronaldtse is published year of documet ISO 19110:2005/Amd 1:2011 2005 or 2011? On the page publication date is Publication date : 2011-06, but in reference it has 2005 year. So there is a problem when we search the document by the reference because year in the reference doesn't mutch year of document.

[ronaldtse]

@andrew2net the way to parse this is:

ISO 19110:2005/Amd 1:2011

• Document identifier of base document that is getting amended: ISO 19110:2005
• Document identifier of amendment document: {base-document}/Amd 1:2011.

The edition year is therefore 2011.