Changes between Initial Version and Version 1 of VLO-Taskforce/Meeting-2014-12-15


Ignore:
Timestamp:
12/18/14 16:10:02 (9 years ago)
Author:
haaf@bbaw.de
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VLO-Taskforce/Meeting-2014-12-15

    v1 v1  
     1= [wiki:VLO-Taskforce VLO Taskforce] Virtual meeting December 15, 2014 =
     2
     3== Overall Topic: How to handle Relations in CMDI ==
     4
     5Participants: Peter, Hanna, Susanne, Axel, Thomas, Jens
     6
     7* (1) Facets
     8 * Should //Continent// and //Country// be merged to one (new) facet //Spacial Coverage//?
     9 * How should //License// be filled? --> First implementation available under: http://aspra11.informatik.uni-leipzig.de:8080/vlo/search?1
     10 * Introduce a new facet //Speaker//? --> Hanna and Peter will provide a proposal.
     11 * Further discussion on facets in January (see below point (3))
     12
     13* (2) Relations
     14 * Different relations should be provided within the components part of CMDI metadata records.
     15 * The VLO-WG will provide recommendations for the handling of relations including:
     16  * a set of CMDI components (grouped together into one surrounding component) for different relations,
     17  * a list of recommended ISOcat-DCs for specific relations.
     18 * Relations under consideration not only include those between texts but also possible relations between tools and services.
     19 * Versioning is a type of relation in this context.
     20 * CMDI providers should provide information about relations at least in one way (from one document to another); the provision of the inverse relation is optional.
     21 * The basis for the creation of CMDI components for relations is the selection of relations supported by OLAC-DCMI. --> Peter will prepare a proposal
     22 * resourceProxy's within the CMDI-Headers are not used to model/record relations but for the provision of adresses for different instances of a document only.
     23 * The <isPartOf>-list element already existing within the CMDI-Header should be deprecated. --> A corresponding proposal will be handed to the CMDI-taskforce with the request to consider such changes to CMDI in one of the next CMDI versions.
     24
     25* (3) Next meeting
     26 * The next 2 meetings will take place in January and February 2015
     27  * 21.-23.01.15: Facets, Relations, Preparation for the QA-Meeting in Feb.
     28  * 18.-20.01.15: Quality Assurance
     29 * Doodle: http://doodle.com/ckvkwvyewifvmx3c
     30  * Please fill in your availabilities until December 29th, 2014