Version 6 (modified by Twan Goosen, 8 years ago) (diff)

added meeting notes

CMDI Taskforce virtual meeting 2016-01-13

  • What?
    • CMDI 1.2 specification meeting
  • Who?
    • Members of the CMDI taskforce and other people involved/interested in specification process
  • When?
    • 13 January 2016: 14.00 - 16.00 CET (on basis of doodle)
  • Where?
    • Skype (Please send your skype handle to twan.goosen or Twan Goosen)



(Tentative - Feel free to edit or suggest)

Meeting notes


  • Some of the definitions need to be checked/finalised:
    • 'Digital object': is it needed? Only used in definition of 'PID'
    • 'Concept' is too strict, not just 'generalised from particular instances'
    • XML document, XML element declaration, XML attribute declaration require a definition, probably by means of a reference to an official W3C document
      • (
      • 'Described resource' as it is used in the section "The Structure of CMDI files" - possibly we could come up with an alternative term that does not use the term "resource", as there seems to be some potential for confusion
  • Proposed additions/changes in other sections
    • Introduction/history: mention ISO spec (CMD 1) and fact that CMDI 1.2 is released with conversion tools
    • References: CMD 1 ISO spec (normative or non-normative? Menzo will check with Daan)
    • Structure of CMDI files: Custom attributes on components and elements (section "The components")
    • CCSL: Default values for attributes (@isProfile, @Multilingual, cardinality, ...)
    • CCSL: Cycles are disallowed in the component hierarchy (section "CMDI component definition")
    • CCSL: Imported vocabularies can get out of sync with referenced original external vocabularies
    • CCSL: Appinfo in <Valuescheme> may need to be revisitied (see e-mail thread [TF-CMDI] CMDI 1.2 specification - CCSL Schema from late November 2015)
    • Also see the remarks made in the Google docs version of the spec
  • Schedule
    • Specification will stay in edit mode on Google docs until the end of week 2
    • After this, this version will be merged back into the wiki page
    • A new version will be available for comments and suggestions after this until the next meeting
  • Menzo will check whether this new version is aligned with the current set of schematron rules


  • Currently working on downgrade xslt for component specs started
  • @ref attributes are allowed on elements (also in CMDI 1.1)
  • Todo: tests for component downgrade and "re-upgrade"
  • Todo: stylesheet CLAVAS Skos to enumeration (for closed vocabularies from external vocabularies)
    • Note: this process should be under command of the metadata modeler
      • manual update with warning at time of publication
      • Possibility to detach from the external vocabulary
  • More test cases needed!
    • Most lacking: (erroneous) cases for CMDI 1.2 features


A new version of the spec for commenting and editing will become available in the week of 18 February (see above).

A follow-up virtual meeting will take place in the beginning of February - a doodle will be created to pick an exact date and time.