Joint CMDI & Curation taskforces virtual meeting 2016-11-24

• What?
  • kickoff CMDI 1.2 best practices
• Who?
  • Members of the CMDI or the Curation taskforces and other people involved/interested in the specification of best practices for CMDI
• When?
  • 24 November 2016, 10.00 - 12.00 CET (on basis of ​doodle)
• Where?
  • Google Hangouts: ​https://hangouts.google.com/call/u5u6nb5abbc53ismfed5emby6ae

Documents

• existing (draft) best practices documents:
  • ​Existing best practices draft
    • derivatives (?):
      1. https://trac.clarin.eu/wiki/CmdiBestPracticeGuide
      2. https://trac.clarin.eu/wiki/Cmdi/QualityCriteria
  • CLARIN-D VLO-WG output
    • Recommendations document
  • ​Granularity recommendations
  • ​Metadata FAQ at clarin.eu
  • ​Paper by Thorsten Trippel and Claus Zinn
  • ​Paper by Thorsten Trippel, Daan Broeder, Matej Durco and Oddrun Ohren
  • Report by Marc Kemps-Snijders
  • ...
• a ​draft setup of a structure on Google Docs

Agenda

• overview of existing documents (see above)
  • what's there and what's missing
• walk through the draft setup of a structure
  • refine, rework based on the discussion
• assign editors
• planning of a first version

Notes

• add the LREC paper on quality to the existing documents (see the updated list above)
• basic structure of the document has been accepted and editors have been assigned
  • Introduction (Menzo)
  • Modelling Component Metadata
    • Components (Twan)
      • Concepts (Menzo)
    • Profiles (Thomas)
    • Workflow (Hanna)
    • Smells (Thomas)
  • Component Metadata
    • General XML (Menzo)
    • The envelope (Menzo)
      • Resource Relations (Oddrun)
    • The component section (Susanne)
    • Workflow (Hanna)
    • Smells (Twan)
  • Common approaches/problems
    • Multilingual metadata (Menzo)
    • Granularity (Dieter?)
    • Licensing (Twan)
    • Common use cases (Susanne)
  • Recommendations (Menzo)
• planning
  1. everyone adds suggestions for best practices
  2. next meeting to discuss them in second half of January (​doodle)
  3. editors will start streamlining text