CMDI Taskforce virtual meeting 2015-11-17

• What?
  • CMDI 1.2 specification meeting
• Who?
  • Members of the CMDI taskforce and other people involved/interested in specification process
• When?
  • 17 November 2015: 10.00 - 12.00 CET
• Where?
  • Skype (Please send your skype handle to twan.goosen or Twan Goosen)

Agenda

(tentative)

0. General discussion of specification and the way it is heading?
1. Specification main sections
   0. Structure of CMDI files
   1. The CMDI Component Specification Language
   2. Transformation of CCSL into a CMD profile schema definition
2. ​Glossary
3. Next steps
   0. Round of review on Google Docs?
   1. ISO draft..

Meeting notes

• General discussion of specification and the way it is heading?
  • Write introduction & history (Menzo makes a draft before the review round)
  • XML examples: suggestions from Menzo, need to be enriched for 1.2. Shared with toolkit tests as much as possible
    • should not focus on difference cmdi 1.1 vs cmdi 1.2
  • Use of MUST, SHOULD, MAY etc
  • Namespaces
    • dcr and ann can go (already removed from toolkit: https://trac.clarin.eu/changeset?reponame=&new=6751%40metadata%2Ftrunk%2Ftoolkit%2Fsrc&old=6684%40metadata%2Ftrunk%2Ftoolkit%2Fsrc)
    • cue namespace: change to http://www.clarin.eu/cmd/cues/1
  • Add normative(?) reference for XML regular expressions
  • Add section before 'structure of cmdi files': "Overview of cmd infrastructure" to link the main sections together
    • ties in with editing task that glues sections together (mainly through references) - Matej
• Specification main sections
  • Structure of CMDI files (Oddrun)
    • Table
      • Replace attribute/element column with usage of typographical conventions (<elem>,@attr)
      • We will prepare an example of a hierarchical table (Twan)
      • Document potential values for some elements, if there is an (open) vocabulary such as <ResourceType>
  • The CMDI Component Specification Language (Thomas)
    • Replace attribute/element column with usage of typographical conventions (<elem>,@attr)
    • Expand complex types in tables (add level in the table hierarchy)
    • Reference to XML regex specification in section on value restrictions
    • Externally defined components can be referenced with @ComponentId, do not need to be specified (actually @ComponentId should not be used in those cases)
  • Transformation of CCSL into a CMD profile schema definition (Twan)
    • Add profile specific namespaces
• Next steps
  • Round of review on Google Docs?
    • editing phase until Dec 4th
    • commenting in Google Docs (spec will be exported by Twan) until next meeting in the second week of January
      • Doodle: ​http://doodle.com/poll/yxwa53xt3fs7xh95
  • ISO draft..
    • Thorsten was not present unfortunately
• Toolkit
  • remains to be done (by Mitchell and Menzo):
    • 1.2 to 1.1 specification transformation
    • conversion of closed external vocabularies to embedded enumeration items in the profile schema
  • make test cases for issues found