Regular monthly LEXIDMA TC meeting

Find connection link within this action item

https://www.oasis-open.org/apps/org/workgroup/lexidma/members/action_item.php?action_item_id=3939

To start 1 hour later than the usual time!

This preliminary agenda will be finalized by 14th June 2021.

1. Administrative

• roll call
• appoint scribe
• approve minutes from 17th May
  https://markmail.org/message/snbulnorycxkwlpl
  and from 19th April
  https://markmail.org/message/76jk7k4vxgdsb2iw

??2. Material

• DMLex Working Draft  https://github.com/oasis-tcs/lexidma
• DMLex WD Technical discussion
  • https://markmail.org/thread/fbai62qur3q6twtu
  • Development in forks? PRs to review?

3. Closing Admin

• Recap of agreed actions
• AOB
• Adjourn [no later than 1500 UTC]

1. Administrative

• roll call
  Jelena, dF, Miloš, Iztok, Simon, John, Michal, Adam, Carole, Arvi
• appoint scribe
  Miloš
• approve minutes from 17th May
  https://markmail.org/message/snbulnorycxkwlpl
  and from 19th April
  https://markmail.org/message/76jk7k4vxgdsb2iw
  • dF moved, Simon seconded, no objections, both minutes were approved

??2. Material

• DMLex Working Draft  https://github.com/oasis-tcs/lexidma
• DMLex WD Technical discussion
  • https://markmail.org/thread/fbai62qur3q6twtu

    • Michal Mechura presented a review of his proposal for the data model specification

      • questions were asked by Arvi Tavast (new member) to clarify purpose of the LEXIDMA standard
        • the data model should serve to create lexicographic exchange format(s) in different serializations
        • Established publishers should be able to use LEXIDMA format for excahnge (export and import), not as their processing format
        • "Naive" implemeters could use the spec drive their lexicographic projects
      • questions were asked by John McCrae to clarify target users of the LEXIDMA standard
        • TC agreed to document use cases to be addressed
        • Simon stressed that retrodigitisation is out of scope

    • Consensus was reached that the current proposal was in line with agreed design principles and a good starting point for detailed specification develiopment, with some caveats:

      • controlled vocabulary and inline data model are orthogonal issues that should be addressed within specialized modules

      • the controlled vocabulary feature should be addressed in the form of authority driven registry(ies)

      • Detailed modules discusions were agreed to be postponed for later, after the core has been specified in an agreed form

3. Closing Admin

• Recap of agreed actions
  • Michal to convert his current core proposal into the OASIS Docbook template before the next editorial meeting (July 26th)
  • dF to post Doodle for August meeting
• AOB - None
• Adjourned 1450 UTC