-
Notifications
You must be signed in to change notification settings - Fork 6
2019 04 18 Board Meeting Notes
Attendees:
- Aaron Elkiss (host)
- Inge Hofsink (minutes)
- Andreas Nef
- Karin Bredenberg
- Sean Mosely
- Bertrand Caron
- Jukka Kervinen
Need to decide if we want to maintain the http://www.loc.gov/standards/mets/mets-registry.html and http://www.loc.gov/standards/mets/mets-registry.html and if so, review the content. Currently Karin’s name and the METS listserv are listed as contacts. Listserv doesn't allow attachments anymore; Aaron suggests updating the page to ask people to include a link to their profile rather than including it as an attachment. Board agrees. Karin will ask Glenn to make these updates on mentioned web pages.
Aaron worked on METS overview lately (see next item) and Russian translation is already one year old. Board agrees to include a link to https://www.prlib.ru/mets and make sure that they get a notification via the METS mailing list when we update something on our end. We should add a new header for full translations on http://www.loc.gov/standards/mets/mets-schemadocs.html and say that if people want to translate stuff they should have a landing page for their translations that we can link to. Karin will ask Glenn to make the updates for that as well and mail the Russian contributor to let them know we posted a link and to watch the mailing list for updates.
Aaron worked on METS overview; see changes on GitHub https://github.com/mets/METS-board/issues/31. Translations should also be updated:
- Bertrand will update the French translation and possibly the Spanish one.
- Aaron will ask Angela di Orio if she can update the Italian one.
- Andreas will update the German one.
- Karin will ask José Borbinha (the original translator for the Portuguese one)
- We aren't sure who produced the Chinese one.
- Karin will reach out to the Russian translators. Aaron will copy the Russian translation into the Markdown format & apply the XML updates.
- We aren't sure who created the Persian translation either. Everyone is happy with the current state of the overview, but there might be additional changes that come up when revising the translations.
Karin mentioned on Trello that listserv doesn’t permit files to be sent. Karin had tried to forward some Russian files and it didn’t work, but Robin was able to forward some files to the list. It seems inconsistent. Glenn said that file attachments were not allowed at all. We are aware of it, just keep an eye on it when you're sending something to the board. We won't take any action on this for now.
See primer xlink issue on https://github.com/mets/METS-board/issues/19 for 3 options by Aaron; Karin mentions 4th option. Bertrand mentions this was brought up before. Karin tells in talking with people from W3C, they thought the XLink schema was dead. It has not been widely adopted; web browsers don't understand XLink. EAD2002 does use XLink. EAD3 does not use XLink at all. The PREMIS2 schema at least imports the LOC XLink schema. It does not appear that PREMIS3 references the XLink schema at all. Not aware of any users that really take advantage of the XLink attributes. Betrand would be in favor of getting rid of it. We will look into removing XLink from the METS schema. This does imply a non-backwards-compatible change for METS. It should be possible to ensure that old METS files continue to validate with the new version of the profile. Aaron will create a first draft of a schema revision that does not include XLink; he will look at PREMIS and EAD how it was implemented in those schemas. Question how this will effect file locations in fileSec because they are recorded xlink:href. Answer that the approach is just to have the same attributes, but removing the xlink namespace from METS schemas.
Question if there are unified suggestions for how to make the revision history of a schema? The suggestion was to use the documentation element in the schema rather than as comments.
See https://github.com/mets/METS-board/issues/25 and mail from Robin about rights and authorship of METS Right schema. Question is do we need to formally ask DLF for transferring intellectual property rights? The general feeling was that since the METS rights schema was created by a subgroup of the METS board, we don't need to ask DLF separately for permission, especially as DLF has not claimed the METS schema in any way in the last 16 years.
See https://github.com/mets/METS-board/issues/28 Tom posted sample oXygen-generated XML Schema Documentation on https://mets.github.io/METS_Docs/mets.html Aaron sees problem that images are not accessible; Karin suggests to add the change history. We agree this oXygen-generated XML Schema Documentation is enough. We'll try adding the documentation elements to the schema and then exporting with Oxygen again. That might be sufficient for something to put on the web page, but there might be an issue with publishing the whole folder output by Oxygen. Karin will check with Glenn.
- When will we hear about iPRES papers: May 24. So we know on next Board meeting (May 30)
- We discuss date of next meeting on May 30 (Ascension Day), because for some it’s a holiday. We decide to keep it on that day