Changes between Version 2 and Version 3 of Taskforces/CMDI/Meeting20151117


Ignore:
Timestamp:
11/17/15 11:01:34 (9 years ago)
Author:
Twan Goosen
Comment:

added meeting notes

Legend:

Unmodified
Added
Removed
Modified
  • Taskforces/CMDI/Meeting20151117

    v2 v3  
    2424
    2525== Meeting notes ==
     26
     27- General discussion of specification and the way it is heading?
     28    - Write introduction & history ('''Menzo''' makes a draft before the review round)
     29    - XML examples: suggestions from '''Menzo''', need to be enriched for 1.2. Shared with toolkit tests as much as possible
     30        - should not focus on difference cmdi 1.1 vs cmdi 1.2
     31    - Use of `MUST`, `SHOULD`, `MAY` etc
     32    - Namespaces
     33        - ''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])
     34        - cue namespace: change to `http://www.clarin.eu/cmd/cues/1`
     35    - Add normative(?) reference for XML regular expressions
     36    - Add section before 'structure of cmdi files': "Overview of cmd infrastructure" to link the main sections together
     37        - ties in with editing task that glues sections together (mainly through references) - '''Matej'''
     38- Specification main sections
     39    - Structure of CMDI files ('''Oddrun''')
     40        - Table
     41            - Replace attribute/element column with usage of typographical conventions (`<elem>`,`@attr`)
     42            - We will prepare an example of a hierarchical table ('''Twan''')
     43            - Document potential values for some elements, if there is an (open) vocabulary such as  `<ResourceType>`
     44    - The CMDI Component Specification Language ('''Thomas''')
     45        - Expand complex types in tables (add level in the table hierarchy)
     46        - Reference to XML regex specification in section on value restrictions
     47        - Externally defined components can be referenced with `@ComponentId`, do not need to be specified (actually `@ComponentId` should not be used in those cases)
     48    - Transformation of CCSL into a CMD profile schema definition ('''Twan''')
     49        - Add profile specific namespaces
     50- Next steps
     51    - Round of review on Google Docs?
     52        - editing phase until Dec 4th
     53        - commenting until next meeting in the second week of January
     54            - Doodle: http://doodle.com/poll/yxwa53xt3fs7xh95
     55    - ISO draft..
     56        - Thorsten was not present unfortunately
     57- Toolkit
     58    - remains to be done: 1.2 to 1.1 specification transformation and
     59    - make test cases for issues found