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.

Sign up for GitHub

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

Jump to bottom

OCFL as a formal standard? #45

Open
zimeon opened this issue Sep 22, 2023 · 2 comments
Open

OCFL as a formal standard? #45

zimeon opened this issue Sep 22, 2023 · 2 comments
Labels
Component: Specification Confirmed: Out-of-scope Use case will not be included in the upcoming version of the spec or implementation notes.

Comments

@zimeon
Copy link
Contributor

zimeon commented Sep 22, 2023 •
edited
Loading

OCFL is an informal standard. It is openly available, openly licensed (CC BY 4.0), and archived in Zenodo. Are the implementation scenarios where OCFL being a formal standard would be important? And, if so, what formality is required?
@rosy1280 rosy1280 added the Proposed: In-Scope Use case is up for discussion and may change the spec, implementation notes, or become an extension. label Sep 22, 2023
@awoods awoods changed the title Are the implementation scenarios where OCFL being a formal standard would be important? Are there implementation scenarios where OCFL being a formal standard would be important? Sep 22, 2023
@rosy1280 rosy1280 changed the title Are there implementation scenarios where OCFL being a formal standard would be important? OCFL as a formal standard? Oct 26, 2023
@rosy1280
Copy link
Contributor

Feedback on Use Cases

In advance of version 2 of the OCFL, we are soliciting feedback on use cases. Please feel free to add your thoughts on this use case via the comments.

Polling on Use Cases

In addition to reviewing comments, we are doing an informal poll for each use case that has been tagged as Proposed: In Scope for version 2. You can contribute to the poll for this use case by reacting to this comment. The following reactions are supported:

In favor of the use case Against the use case Neutral on the use case
👍🏼 👎🏼 👀

The poll will remain open through the end of February 2024.

@zimeon
Copy link
Contributor Author

zimeon commented Feb 29, 2024

2024-02-29 Editors' agree that we will not pursue a path to formal standardization at this time (just +1 in voting at this point; no details of need/requirements).

@zimeon zimeon added Confirmed: Out-of-scope Use case will not be included in the upcoming version of the spec or implementation notes. and removed Proposed: In-Scope Use case is up for discussion and may change the spec, implementation notes, or become an extension. labels Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: Specification Confirmed: Out-of-scope Use case will not be included in the upcoming version of the spec or implementation notes.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rosy1280 @zimeon