-
Notifications
You must be signed in to change notification settings - Fork 14
2020.09.09 Community Meeting
Andrew Woods edited this page Sep 10, 2020
·
8 revisions
- Time of the call
- Wednesday September 9th 4pm BST
- Wednesday September 9th 11am EDT
- Wednesday September 9th 8am PDT
- Thursday September 10th 1am AEST
- https://lyrasis.zoom.us/my/vivo1
- or Telephone:
- US: +1 669 900 6833 or +1 646 876 9923
- Canada: +1 647 558 0588
- Australia: +61 (0) 2 8015 2088
- United Kingdom: +44 (0) 20 3695 0088
- Meeting ID: 812 835 3771
- International numbers available: https://zoom.us/u/MO73B
- Rosalyn Metz
- Andrew Woods
- Ben Cail
- David Wilcox
- Josh Westgard
- Julian Morley
- Peter Winckles
- Neil Jefferies
- Dan Noonan
- Community updates (introductions, updates, implementations, plans, etc)
- Review of previous action items
- None: all completed
- Editorial updates
- Extensions Review and Merge Policy
- Seeking community input: Issue-23 - "Reconsider 'range' for string parameters"
- Seeking community input: Issue-22 - "JSON representation should not have a map at its root"
- Scoping 2.0
- Next community meeting: (second Wednesday of the month)
- Wednesday October 14th 8pm EDT
- Wednesday October 14th 5pm PDT
- Thursday October 15th 1am BST
- Thursday October 15th 10am AEST
- New OCFL client from Peter Winckles (UWM)
- https://github.com/pwinckles/rocfl/
- Potentially to demo on a future community call
- We would like to eventually getting more input from community on extension proposals before merging... it will come
- Mutable Head proposal: need to provide context in order to get community input
- Interest in community input on a new Use Cases
- Use case: being able to customize inventory.json
- https://github.com/OCFL/Use-Cases/issues/37
- Editors need to surface historical discussion on this use case
- Add above use case to next editors meeting
- Use case: being able to customize inventory.json
- Interest in having granular extensions, versus highly parameterized extensions
- Identifiers are used in layout as well as in other ways
- Interest in specifying the input identifiers to layout extensions
- Useful to be able to verify validity of IDs
-
Issue-23 - "Reconsider 'range' for string parameters"
- https://json-schema.org/understanding-json-schema/reference/string.html
- min, max, ??
- value: single or multi-valued (if single: size is fixed, if multi: range)
- Editorial team to resolve PR https://github.com/OCFL/extensions/pull/13 - merged
- Editorial team to create new PR describing process by which extensions are merged - done