Changes between Version 4 and Version 5 of Taskforces/CMDI/Meeting20170517

Timestamp:

05/30/17 08:32:20 (7 years ago)

Author:

Menzo.Windhouwer@mpi.nl

Comment:

--

Taskforces/CMDI/Meeting20170517

@@ -40 +40 @@
         * Status support at centres: Leipzig providing; Meertens work on FLAT, CMDI 1.2 is not high priority however so will be 1.1 initially (also MPI); ACDH will be providing CMDI 1.2 at time of assessment; META-SHARE should be combined effort, no initiative yet; EURAC has intention to start off with CMDI 1.2; to be discussed with D-Space development team
     2. CLAVAS
-        * Running at Meertens, now embedded in CMDI (1.2). Being upgraded to OpenSKOS, some technical difficulties causing a delay.
+        * Running at Meertens, now embedded in CMDI (1.2). Being upgraded to OpenSKOS 2, some technical difficulties causing a delay.
         * CCR Data stays as it is; old CLAVAS vocabularies are forgotten. CLAVAS instance now runs at a CLARIN host - to be replaced by Meertens instance. Then additional vocabularies can be added.
         * Licences: Oddrun has a licence vocabulary (140 licences). To be merged/aligned with curation TF's licence vocabulary? 
@@ -57 +57 @@
 "The CMDI profiles, that a centre uses, have to be public to be accepted in assessment. As mentioned above, in the current version of CMDI, public profiles cannot get updates of links to CCR. We hope that the metadata curation taskforce looks into this dilemma." ([https://office.clarin.eu/v/CE-2017-1015-centre-assessments-round8-to_CAC_v1_1.docx document])
 
-`TODO` Proposed the rephrased sentence to the SCCTC (through Lene?)
+We propose the following rephrased sentence: "The CMDI profiles, that a centre uses for their published metadata, have to be public, with preferably status production but draft or deprecated are acceptable, to be accepted in assessment."
+
+`TODO` Proposed this rephrased sentence to the SCCTC (through Lene?)
+
 === Adding of concept links after production? ===
     1. Option: allow this to be done by the owner (only add, not update)
     2. Preferred option: compreg admins remains the 'doorkeeper'
         * `TODO`: propose a note gets added to the requirement document stating that the !CompReg admin (registry manager?) can be contacted to get this done.
+
 === CMDI best practices ===
     * Order based on priority?