search

relaton / relaton-nist

NistBib: retrieve NIST Standards for bibliographic use using the BibliographicItem model
https://www.metanorma.com
MIT License
2 stars 1 forks source link

Relaton NIST mistakes `FIPS 210 EP` for being FIPS #37

Closed ronaldtse closed 4 years ago

ronaldtse commented 4 years ago

Source:

* [[[FIPS199,FIPS199]]], Federal Information Processing Standard 199, _Standards for Security Categorization of Federal Information and Information System_, February 2004. https://doi.org/10.6028/NIST.FIPS.199[https://doi.org/10.6028/NIST.FIPS.199].

* [[[FIPS201,FIPS201]]], Federal Information Processing Standard 201-2, _Personal Identity Verification (PIV) of Federal Employees and Contractors_, August 2013. https://doi.org/10.6028/NIST.FIPS.201-2[https://doi.org/10.6028/NIST.FIPS.201-2].

* [[[FIPS201EVALUATIONPROGRAM,FIPS 201 EP]]], _FIPS 201 Evaluation Program_. https://www.idmanagement.gov/fips201/[https://www.idmanagement.gov/fips201/] [accessed 5/16/18].

Output:

FIPS199 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC.
See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them.
FIPS199 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC.
See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them.
FIPS201 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC.
See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them.
FIPS201 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC.
See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them.
fetching NIST FIPS 201 EP...
  1. FIPS199 should NOT be recognized
  2. FIPS 201 EP should not be recognized because it contains "EP" at the end.