CEN / CENELEC often adopts ISO or IEC standards.

EN ISO 14090:2019
EN ISO 17292
EN ISO 17292:2004
EN IEC 62115:2020 
EN IEC 62368-1:2020
EN IEC 55014-2:2021 

From https://experts.cen.eu/media/Experts/cen-clc_projex-online_user-guide.pdf

• EN
• HD
• CWA
• TS
• TR
• CG (CEN Guide)

All these documents, except CG can be created with an Amendment / Corrigendum.

From: https://experts.cen.eu/media/Experts/cen-clc_projex-online_user-guide.pdf

• EN = "European Norm" (which means European Standard).
• CEN = Center for European Normalization (the equivalent of ISO in the EU)
• CLC = European Committee for Electrotechnical Standardization (the equivalent of IEC in the EU)

Both CEN and CLC publish documents in their prefixes, e.g.:

• By CEN only:
  • CEN/TR 17833:2022
  • CEN/TS 17638:2021
• By CLC only:
  • CLC/TR 62125:2008
  • CLC/TS 50701:2021
• Copublished:
  • CEN/CLC/TR 17602-80-12:2021
  • CEN/CLC/TS 17880:2022

ENs are published by one of 3 organizations: CEN, CLC, and ETSI.

CEN and CLC can publish ENs:

• EN 16602-60-15:2014
• EN 17355:2020

CEN Guide 15
CEN Guide 414:2014
CEN Guide 414:2017
CLC GUIDE 1:2022
CEN-CLC Guide 32:2016
CEN/CLC Guide 25:2023
CEN/CLC Guide 28:2014
CEN/CLC Guide 34:2021
CEN/CLC/TR 17602-80-12:2021
CEN/CLC/TS 17880:2022
CEN/TR 16411:2022
CEN/TR 17654:2021 
CEN/TR 17833:2022
CEN/TS 14972
CEN/TS 17638:2021
CLC/TR 62125:2008
CLC/TS 50701:2021
EN 1177:2008
EN 1177:2018
EN 12464-1:2011
EN 13501-1:2018
EN 14885:2018
EN 15038
EN 16602-60-15:2014
EN 17355:2020
EN 196-3:2016
EN 228
EN 228:2008
EN 455-2:2015

The dependencies tree between pubid gems is making them unusable. Right now:

• I consume all of pubid-cen, pubid-iso, pubid-iec in the same stack
• I am supposed to test a pubid-iec PR, which is anchored to pubid-core 1.12
• The latest pubid-iso is anchored to pubid-core 1.8.6
• The latest pubid-cen is anchored to pubid-core 1.8.0
• The current relaton-iso release is anchored to pubid-core 1.8.6 (since it names the version of pubid-iso as 0.6.0)

This means it is impossible for me to do anything with the pubid-iec PR, without recompiling and removing the dependencies for pubid-iso, pubid-cen, and relaton-iso

Releases need to be anchored to a single gem's versions, which is updated whenever a pubid version is updated; this is what the relaton stack does with relaton-cli. Any major version updates are ONLY exposed to the outside world through relaton-cli, and whenever there is a minor version update in a child relaton gem, the minor version of relaton-cli is updated as well.

This may be the intent behind pubid-core, but it is not clear to me that this is happening; and @andrew2net and I are using pubid-core 1.8, which was last updated start of October: we have no idea about the updates to pubid-core since.

So you need to:

(a) notify us when a minor version of pubid-core changes, so that both of us can update our dependencies
(b) ensure that minor versions of pubid-* are synchronised with pubid-core, if they are not already

EN 196-3:2005+A1:2008
EN 527­2:2016+A1:2019
EN 60335-1:2012/A1
EN 60335-1:2012/A14
EN 60335-1:2012/A15
EN 60335-1:2012/A2:2019
EN 60335-1:2012/AC:2014
EN IEC 62368-1:2020+A11:2020 

There are 3 types of documents here:

• /A1 means the document is "Amendment 1"
• /AC means the document is "Corrigendum 1".
• +A1 means this document incorporates "Amendment 1".

Interestingly there is a way to tell IEC standards. IEC numbers start from 60000 to 79999. From 80000-89999 they are either ISO, IEC, or ISO/IEC or IEC/ISO standards. From 1 to 59999 it is only ISO.

Originally posted by @ronaldtse in metanorma/pubid-bsi#2 (comment)

Example: "BS EN 60038 AMD1 FRAG2"

prEN means "draft EN".

prEN 12464-1:2019
prEN 13241-1
prEN 13241-1:2013
prEN 14885:2020
prEN 15038:2004
prEN 16942:2016

FprEN means "final draft EN".

FprEN 16114:2011
FprEN 16798-3
FprEN 50600‑2‑4