2022 09 29 Board Meeting Notes
METS Board Notes, 2022-09-29
- Karin Bredenberg
- Aaron Elkiss
- Inge Hofsink
- Andreas Nef
- Juha Lehtonen
- Tobias Steinke
- Robin Wendler
5 Board members attended. Good interest in the presentation about METS2. Questions about why not JSON, whether existing implementations need to be changed (no), about transitioning from 1 to 2, whether the files will become smaller (it depends). Board. Encouraged people to join the mailing list. Notes about questions at https://docs.google.com/document/d/14cY91sJTIvI9C56yrhI_NliwpQSQ6W85I9fO4bRLJfQ/edit
iPres papers can be changed until later in October and will be made public.
The Board should go ahead with the white paper as planned and release draft schema of METS2 for review. Aaron updated the readme on github to point to the draft schema. Should we also put something on the METS homepage at LoC? Not the draft schema, but an announcement and maybe a link to github.
Should more comments be added to the schema to clarify the changes or rely on documentation? Prefer not to load the schema with too many comments, and should not focus on changes from METS1, but describe the METS2 schema as it is.
Release the white paper and alpha schema together on github. Make sure a notification with references to them are easily found on the METS page. Can we get a timely update from LC, and release on the METS list simultaneously? Robin will draft an announcement news item: e.g., The METS Editorial board is developing METS 2, a simpler, lighter alternative to METS 1. A white paper describing the new generation and the rationale for the differences, along with a corresponding draft schema https://github.com/mets/METS-schema/blob/mets2/METS2.md To see the work in progress and feedback and questions, see… Note original METS will continue to be actively maintained.
- Remove XML examples to a separate file in github rather than as part of the white paper.
- Organize a feedback mechanism.
- Addition to white paper to describe similarities between 1 and 2.
- Should we add something to the motivation section to cover why we are still using XML Schema rather than JSON? If you want to do RDF or linked data, have alternatives such as IIIF or JSON-LD. There is no standard for JSON validation and the embedded metadata from external schemas is typically XML rather than JSON.
- Add a little more to the white paper about METS profile: still available and relevant for METS2, will be a revision of that forthcoming.
- Supply brief conclusion and future work.
What do we want people to think about in their feedback? Comment on specific changes? Missed opportunities? Would there be benefits to you from this simplified schema?
Aaron will make updates in the coming week. (Done, 2022-10-05)
Finalize at the next meeting on Nov 10 and release to the METS list, asking for feedback by end of February. Send out reminders, too. Can continue working on new documentation in the meantime (tutorial, overview).