-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing identifiers from mapping exercise from relaton-data-misc #6
Comments
In particular, I can't find these in the official NIST dataset:
|
As per #7, these should be mapped to different documents:
These two are identical (the correct doc id is "NIST FIPS 146", but it does not exist in the official dataset yet)
Filed at usnistgov/NIST-Tech-Pubs#22 |
Actually, I somehow missed these:
Not sure why I missed... |
In #15 we have determined that:
|
All issues have been filed to the NIST authoritative repository at https://github.com/usnistgov/NIST-Tech-Pubs . |
The resulting YAML mapping file is below: ---
reference.FIPS.1-1.1980.xml: NBS FIPS 1
reference.FIPS.113.1985.xml: NBS FIPS 113
reference.FIPS.146-1.1989.xml: fallback_unless_available(NIST FIPS 146)
reference.FIPS.146-1.1991.xml: NIST FIPS 146-1
reference.FIPS.146.1988.xml: fallback_unless_available(NIST FIPS 146)
reference.FIPS.146.1990.xml: NIST FIPS 146-1
reference.FIPS.161-1.1993.xml: fallback_unless_available(NIST FIPS 161-1)
reference.FIPS.180-1.1994.xml: NIST FIPS 180-1
reference.FIPS.180-1.1995.xml: NIST FIPS 180-1
reference.FIPS.180-2.2002.xml: fallback_unless_available(NIST FIPS 180-2)
reference.FIPS.180.1993.xml: NIST FIPS 180
reference.FIPS.186-1.1998.xml: fallback_unless_available(NIST FIPS 186-1)
reference.FIPS.186.1994.xml: NIST FIPS 186
reference.FIPS.197.2001.xml: NIST FIPS 197
reference.FIPS.35.1975.xml: NBS FIPS 35
reference.FIPS.4.1968.xml: fallback_unless_available(NBS FIPS 4)
reference.FIPS.46-1.1988.xml: fallback_unless_available(NBS 46-1)
reference.FIPS.46-2.1993.xml: NIST FIPS 46-2
reference.FIPS.46.1977.xml: fallback_unless_available(NBS 46)
reference.FIPS.5-2.1987.xml: NBS FIPS 5-2
reference.FIPS.500-166.1989.xml: NBS SP 500-166
reference.FIPS.500-20.1977.xml: fallback_unless_available(NBS SP 500-20)
reference.FIPS.500-61.1980.xml: NBS SP 500-61
reference.FIPS.55-2.1987.xml: fallback_unless_available(NBS FIPS 55-2)
reference.FIPS.58.1979.xml: NBS FIPS 58-1979
reference.FIPS.59.1979.xml: NBS FIPS 59
reference.FIPS.6-4.1990.xml: NIST FIPS 6-4
reference.FIPS.74.1981.xml: NBS FIPS 74
reference.FIPS.81.1980.xml: NBS FIPS 81
reference.FIPS.95-1.1993.xml: NBS FIPS 95-1
reference.FIPS.98.1983.xml: NBS FIPS 98
reference.NIST.500-162.1988.xml: NIST SP 500-162
reference.NIST.500-162.1990.xml: NIST SP 500-162
reference.NIST.500-163.1989.xml: NIST SP 500-163
reference.NIST.500-166.1989.xml: NIST SP 500-166
reference.NIST.500-183.1990.xml: NIST SP 500-183
reference.NIST.500-20.1977.xml: fallback_unless_available(NBS SP 500-20)
reference.NIST.500-214.1993.xml: fallback_unless_available(NIST SP 500-214)
reference.NIST.500-61.1980.xml: NBS SP 500-61
reference.NIST.FIPS.202.xml: NIST FIPS 202
reference.NIST.SP.800-185.xml: NIST SP 800-185 The syntax |
Just as a note—you can omit the special syntax and just provide the identifiers, the service will fall back automatically if they don’t exist yet. |
@strogonoff please feel free to remove them. I just wanted to differentiate those with existing data and those with no data provided. Thanks. |
I revisited FIPS 1 1968, but it is not the correct target. So this is also missing:
|
From: ietf-tools/relaton-data-misc#8
mapping.yaml.zip
I was able to map these entries, but there are a number of them that are not available from the official NIST database.
The text was updated successfully, but these errors were encountered: