Changes between Version 5 and Version 6 of Taskforces/CMDI/Meeting20160113


Ignore:
Timestamp:
01/14/16 08:37:50 (8 years ago)
Author:
Twan Goosen
Comment:

added meeting notes

Legend:

Unmodified
Added
Removed
Modified

  • Taskforces/CMDI/Meeting20160113

    v5 v6  
    2323
    2424== Meeting notes ==
    25 == Specification ==
     25
     26=== Specification ===
    2627
    2728* Some of the definitions need to be checked/finalised:
    28  * 'Digital object' -  is it needed? Only used in definition of 'PID'
     29 * 'Digital object': is it needed? Only used in definition of 'PID'
     30 * 'Concept' is too strict, not just 'generalised from particular instances'
    2931 * XML document, XML element declaration, XML attribute declaration require a definition, probably by means of a reference to an official W3C document
    3032  * ([https://www.w3.org/TR/REC-xml/#dt-xml-doc])
    3133  * '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
    32 * Desirable additions in other sections
    33  * Cycles are disallowed in the component hierarchy (CCSL, section "CMDI component definition")
    34  * Imported vocabularies can get out of sync with referenced original external vocabularies (CCSL)
     34* Proposed additions/changes in other sections
     35 * __Introduction/history__: mention ISO spec (CMD 1) and fact that CMDI 1.2 is released with conversion tools
     36 * __References__: CMD 1 ISO spec (normative or non-normative? Menzo will check with Daan)
     37 * __Structure of CMDI files__: Custom attributes on components and elements (section "The components")
     38 * __CCSL__: Default values for attributes (@isProfile, @Multilingual, cardinality, ...)
     39 * __CCSL__: Cycles are disallowed in the component hierarchy (section "CMDI component definition")
     40 * __CCSL__: Imported vocabularies can get out of sync with referenced original external vocabularies
     41 * __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)
     42 * Also see the remarks made in the [https://docs.google.com/document/d/1nP9GJsPsDoKfN3PHEsdaVzIT_ESmFwB1Nnuwf3jxWt4/edit?usp=sharing Google docs version of the spec]
    3543* Schedule
    3644 * Specification will stay in edit mode on Google docs until the end of week 2
    … …  
    3947* Menzo will check whether this new version is aligned with the current set of schematron rules
    4048
    41 == Toolkit ==
     49=== Toolkit ===
    4250
    4351* Currently working on downgrade xslt for component specs started
    … …  
    5159 * Most lacking: (erroneous) cases for CMDI 1.2 features
    5260
    53 == Schedule ==
     61=== Schedule ===
    5462A new version of the spec for commenting and editing will become available in the week of 18 February (see above).
    5563