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

Extension parameters still necessary? #18

Closed
pwinckles opened this issue Jun 12, 2020 · 2 comments
Closed

Extension parameters still necessary? #18

pwinckles opened this issue Jun 12, 2020 · 2 comments
Assignees

Comments

@pwinckles
Copy link
Contributor

Given that one of the original ideas was to allow extensions parameters to be defined within core OCFL JSON files, but this is no longer allowed, is there still a need for the OCFL Extension repository to officially define extension parameterization?

If extensions are parameterized, then they must store the parameters in an extension file. The nature of this file could really be entirely up to the extension to define. I don't necessarily have a problem with the extension spec defining parameterization, but it does seem perhaps unnecessary now.

@awoods
Copy link
Member

awoods commented Aug 18, 2020

Discussed during 2020-08-18 editors meeting. The downside of retaining the current parameter specification is presently unclear. Decided to let extension definitions to emerge, and determine based on practice whether parameters are useful as currently defined.

@neilsjefferies
Copy link
Member

As per above, we will leave things as they are for now.

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

No branches or pull requests

3 participants