Skip to content
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

Support long notation references #194

Open
andrew2net opened this issue Sep 9, 2023 · 4 comments
Open

Support long notation references #194

andrew2net opened this issue Sep 9, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@andrew2net
Copy link

andrew2net commented Sep 9, 2023

This gem parses short notation references like NIST SP 800-67r1 and NIST SP 800-57pt1 but fails to parse long notation NIST SP 800-67 Rev. 1 and NIST SP 800-57 Part. 1

> Pubid::Nist::Identifier.parse "NIST SP 800-67 Rev.1"
Failed to match sequence (OLD_STAGE? (' ' / '.') REPORT_NUMBER PARTS{0, } DRAFT? STAGE? TRANSLATION?) at line 1 char 8.
cause: Failed to match sequence (OLD_STAGE? (' ' / '.') REPORT_NUMBER PARTS{0, } DRAFT? STAGE? TRANSLATION?) at line 1 char 8.
`- Don't know what to do with ".1" at line 1 char 12.

We need to parse the long notations as well.

@andrew2net andrew2net added the bug Something isn't working label Sep 9, 2023
@mico
Copy link
Contributor

mico commented Sep 12, 2023

@andrew2net for NIST SP series it was fixed in #192
Do we need long notation parsing for other series? Do we have full list of long notations?

@andrew2net
Copy link
Author

@mico users can utilize long notaion references to fetch any document. So yes, we need to parse long notation for other series.

@ronaldtse
Copy link
Contributor

As per the original pubid blog post we stated the 4 different pubid outputs: short, abbreviated, long and machine readable.

We should be able to parse all 4 types.

@mico
Copy link
Contributor

mico commented Sep 13, 2023

As per the original pubid blog post we stated the 4 different pubid outputs: short, abbreviated, long and machine readable.

We should be able to parse all 4 types.

@ronaldtse we cannot parse long and abbreviated formats right now, examples for NIST FIPS 140-3:

  • National Institute of Standards and Technology Federal Information Processing Standards Publication 140-3 (long)
  • Natl. Inst. Stand. Technol. Federal Inf. Process. Stds. 140-3 (abbreviated)

How we can confirm that long and abbreviated series names in https://github.com/metanorma/pubid-nist/blob/main/series.yaml are correct?

Should we reconsider what is "long" and "abbreviated" formats in light of updates from pubs-export? (Or introduce extra long and short formats, with publisher and series in short format?)
Examples:

  • NIST SP 800-40 Version 2
  • NIST SP 800-27 Revision (r)
  • NIST SP 800-26 Rev. 1
  • NIST SP 800-57 Part 2 Rev. 1

Identifier parts using "long" or "abbreviated" format, but publisher and series using short form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants