metanorma / pubid-ieee

PubID spec and implementation for IEEE deliverables
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

Parse IRE identifiers #41

Open mico opened 2 years ago

mico commented 2 years ago
52 IRE 7.S2
55 IRE 2.S1 (IEEE Std No 147)
61 IRE 15.S1 (IEEE 182)
61 IRE 28 S1 (IEEE 216)
62 IRE 12.S1 (IEEE 174)
62 IRE 7.S2 (IEEE 161)
IEEE Std 159-1972 (52 IRE 7 S2)
IEEE Std 218-1956 (Reaffirmed 1980, 56 IRE 28.S2)
IEEE Std 59 IRE 12, S1
IEEE Std 175-1960 (60 IRE 13 S1)

Seems the first number here is a year, for example: "52 IRE 7.S2" actually "IRE/IEEE 7.S2-1952" @ronaldtse Should we generate output with IRE/IEEE for all this identifiers?

ronaldtse commented 2 years ago

@mico yes you are right.

According to https://ewh.ieee.org/cmte/pa/Status/IEEE.html , IRE is one of two predecessor organizations (the other is AIEE):

The American Institute of Electrical Engineers (AIEE) and the Institute of Radio Engineers (IRE) united in 1963 to form the IEEE.

So these documents are by nature, dual-published by IRE and IEEE as they are re-labeled as IEEE standards after being published by IRE.

We should treat this list somewhat separately:

The original formats of IRE PubIDs can be seen here: https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=4051609

Screenshot 2022-03-23 at 8 19 18 PM

Another sample (published in 1957): https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=4056467

Screenshot 2022-03-23 at 8 40 48 PM Screenshot 2022-03-23 at 8 40 57 PM Screenshot 2022-03-23 at 8 41 04 PM

The display is not even that consistent in this sheet, but in general the pattern is:

I think we should support: