Skip to content

Do we specify that in the version sequence there must be a monotonic sequence of non-decreasing OCFL version numbers? #544

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

Closed
zimeon opened this issue May 12, 2021 · 2 comments · Fixed by #550
Assignees
Milestone

Comments

@zimeon
Copy link
Contributor

zimeon commented May 12, 2021

Do we specify that in an objects version sequence there must be a monotonic sequence of non-decreasing OCFL version numbers? Ie. something like v1 is OCFL v1.0, v2 is OCFL v1.1, v3 is OCFL v1.1

@zimeon
Copy link
Contributor Author

zimeon commented May 12, 2021

I think that we should expect that within an object there should never be a decrease in OCFL version number across the version sequence, so:

  • 1.0, 1.0, 1.0 - OK
  • 1.0, 1.1, 2.0 - OK
  • 1.0, 2.0, 1.1 - NOT OK

@zimeon
Copy link
Contributor Author

zimeon commented May 18, 2021

Editors' discussion 2021-05-18: The requirement that existing versions are immutable is critical to maintain. Agreement that the OCFL version sequence of versions within an object must be monotonic non-decreasing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants