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

Clarify valid content for the "version" field #134

Open
lpugin opened this issue Jun 10, 2024 · 1 comment
Open

Clarify valid content for the "version" field #134

lpugin opened this issue Jun 10, 2024 · 1 comment
Labels
Type: Spec Enhancement New, non-normative changes (examples, elaborations, etc)

Comments

@lpugin
Copy link
Contributor

lpugin commented Jun 10, 2024

The specs do not seem to be clear about what is valid in the version field. They read

The version key MAY be included. The value of the version key MUST be pe2 for incipits that conform to Version 2 of the specification. If a version key is not specified, the incipit SHOULD be interpreted as conforming to Version 1 of the specification.

is "version": "Plaine And Easie 1" valid for v1 incipits?" Or does v2 not allow to specify v1 explicitly at all?

@ahankinson
Copy link
Contributor

Since there is no value defined for version 1, we should probably stick with pe (the value in MARC). But since the empty string also means v1, then we may also have to state that any other value than pe2 must be interpreted as v1, probably with a clarifying note that says that subsequent paec versions are excepted since they will define a new string. (Pe3?)

@lpugin lpugin added the Type: Spec Enhancement New, non-normative changes (examples, elaborations, etc) label Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Spec Enhancement New, non-normative changes (examples, elaborations, etc)
Projects
None yet
Development

No branches or pull requests

2 participants