Changes between Version 13 and Version 14 of CMDI 1.2/Resource proxies/ResourceRelation

Timestamp:

01/23/14 10:55:06 (10 years ago)

Author:

twagoo

Comment:

--

CMDI 1.2/Resource proxies/ResourceRelation

@@ -235 +235 @@
 
 Oddrun: I partly agree, Oliver here touch on the key characteristics of CMDI: While it's flexibility allows us to configure our metadata according to any specific needs, it is equally the case that one and the same phenomenon may be expressed in many different ways. Which is sometimes confusing...Relationships between resources  is such a case. Any metadata modeller may define components or elements with the specific purpose of handling relationships.  OLAC DCMI-terms is one example, - another is the ResourceRelationInfo component included in all 4 resourceInfo profiles from METASHARE. Then, in addition, CMDI offer the integrated relationship elements in the Resources section, some "hard coded"/defined (isPartOf), others to be defined by the modeller or metadata creator. For the hard coded ones, the advantage of storing them outside components is the possibility of imposing a shared semantics, making exploitation easier. However, this does not apply to the ResourceRelation element, which increasingly - after its generalisation - looks like a regular component. Maybe it would be better to define ResourceRelation as a recommended component in CR, and exclude it from the Resources element?
-
+----
 Peter: [[ VLO Taskforce]] contains a summary of how some CLARIN-D centers currently represent relationships. None of the examples
 collected so far uses the element ResourceRelationships. Instead, the generic (binary) relationships expressed by ResourceProxy, are often further described
 in the component part of a CMDI record. 
+----
+Twan: [[attachment:header.pdf:wiki:CMDI 1.2|This document]] by Thorsten Trippel from 2012 describes the various non-component header sections of CMDI and expresses the originally intended usage of Resource Relation as well as the Part Of List (emphasis mine):
+
+ '''The Resource Relation List'''
+
+ Resource files do not exist independent of each other if a resource consists of more than one file. For example, audio files and transcriptions are related to each other. ''The !ResourceProxyList only lists these files, the !ResourceRelationList makes the relation between pairs of files explicit.'' For this purpose the !ResourceRelation contains a triple of elements defining a directed relation between a Resource 1, which is referenced by a ref-pointer to an id from the !ResourceProxy, and a Resource 2 respectively. The relation between the two is given as a string in the !RelationType element.
+
+ '''The Is-Part-of List'''
+
+ Resources that are defined in bundles are listed under !ResourceProxy. The individual parts can be seen as independent resources as well, such as a subcorpus that can also be distributed on its own. ''To point out that a resource is part of a larger unit or created as part of a larger unit'', the !IsPartOfList is introduced referring to one or more larger units by giving the PID of the larger units with the !IsPartOf element.