Changes between Version 6 and Version 7 of Taskforces/CMDI/Meeting20160810

Timestamp:

08/11/16 07:11:10 (8 years ago)

Author:

Twan Goosen

Comment:

--

Taskforces/CMDI/Meeting20160810

@@ -4 +4 @@
  * CMDI 1.2 implementation/specification meeting
 * Who?
- * Members of the [[Taskforces/CMDI|CMDI taskforce]] and other people involved/interested in the specificaiton, implementation and rollout of CMDI 1.2
+ * Members of the [[Taskforces/CMDI|CMDI taskforce]] and other people involved/interested in the specification, implementation and rollout of CMDI 1.2
 * When? 
  * 8 August 2016, 14.00 - 16.00 CEST (on basis of [http://doodle.com/poll/g2q5nuzs79na4uer doodle])
@@ -31 +31 @@
   * Registering new components in the component registry did not work due to bad initialisation, this was fixed in Component Registry 2.1.1 (some days after the 2.1.0 deployment)
  * Some issues related to component downgrade that surfaced very recently have been fixed in a maintenance release of the toolkit, [https://github.com/clarin-eric/cmdi-toolkit/releases/tag/cmdi-1.2.1 version 1.2.1], used by [https://github.com/clarin-eric/component-registry-rest/releases/tag/ComponentRegistry-2.1.3 Component Registry 2.1.3] (both currently in production)
+* Versioning of the specification: only major and minor version, all toolkit versions with matching major and minor (regardless of 'patch' level) should be compliant. Revisions of the specification within a minor release will simple be dated. A footnote will be added to the spec to explain this. Semantic versioning is applied (at least to the toolkit) although the transition from 1.1 to 1.2 technically would have required an increase at the major version level. 
+* UML diagrams need to be unified (task for Oddrun and Mitch)
+* Specification will be open for commenting/suggesting on Google Docs until Monday 15 August, then changes will be transferred to wiki and a new document will be made available
+* Doodle for next meeting: http://doodle.com/poll/zzwmk979zr3b87pv