-
Notifications
You must be signed in to change notification settings - Fork 6
2021 04 22 Board Meeting Notes
Attendees
- Karin Bredenberg
- Bertrand Caron
- Aaron Elkiss (host)
- Inge Hofsink (minutes)
- Juha Lehtonen
- Sean Mosely
- Tobias Steinke
- Robin Wendler
Aaron updated the METS2 XSD and added some METS 2 examples and Inge gathered all proposed changed in the white paper on Google docs. We discuss the questions and remarks in the white paper.
- Use mdGroup (in draft XSD) or mdGrp (parallel to fileGrp) as an element name? After discussing using abbreviated element names or extended names it sounds like the consensus is to keep the abbreviations but make sure to have good explanations in the primer & documentation.
- Element mdGrp: add attribute @ID to make transformation from METS1 easier
Removal of attribute FLocat/@LOCTYPE is discussed related to Robin’s use case of database ids and/or storage identifiers that are not files. Also use case of relative paths are discussed. Possible solutions could be
- removing the typing from href, e.g. make it not xsd:anyUri
- create a private URL scheme
- use an attribute other than href to reference the database ID (because @href implies an actionable link)
- Maybe make sense to retain LOCTYPE (defaulted to URL), but change the name of the element to something other than href?
- For relative URLs it might make sense to have some documented semantics for determining the base URL (i.e. wherever you found the METS file) as well as a way to specify a base URL
Perhaps it’s helpful to try to find some other cases where people have used OTHERLOCTYPE. We should at least provide a recommendation and standard way for coding local identifiers, even if they are not actionable elsewhere.
Optional structMap is discussed related to remark of Bertrand to have at least one mandatory entry point into an XML document. Use cases to make structMap optional:
- Same structure is used in fileSec and structMap for structure of filesystems; structMaps are then only made because it's a mandatory element.
- At first structMap was mandatory for digitization projects, and then structure is important.
- Although it would be good to at least have one mandatory section, it seems not a maintainable solution; fileSec can be optional as well e.g. for describing collections.
Consensus seems to be to keep it optional but to explain more about the purpose of the structMap, and to provide a set of best practices /schematron around structMap that are not enforced by the XSD schema.
There are still some enumerations of attribute values left in fileSec in METS2 XSD. Although they have a different character than the attributes with @OTHER*, we decide to remove all hardcoded value lists. We still want to document recommended values and could probably refer to existing controlled vocabularies if possible.
Juha added two considerations about METS 2 to the Trello board. Request to all is to add all questions, remarks and considerations to the white paper in Google docs.
Our METS tutorial submission has to be updated because of a new template. Karin will arrange this and will send an updated submission next week because of the deadline of 30 April. Information about registration for presenters is not clear yet.
[addition after meeting: see http://ipres2021.ac.cn/dct/page/70007 “It is expected that all accepted submissions are from individuals who are registered as conference attendees and are able to present the submission at the conference on-site or online.”]
[addition after meeting: submission deadline is extended to 31 May - https://twitter.com/iPRES2020/status/1387609968942010373]