Changes between Version 3 and Version 4 of CMDI 1.2/Header/MdType

Timestamp:

12/20/13 14:43:31 (10 years ago)

Author:

schiel@bas.uni-muenchen.de

Comment:

--

CMDI 1.2/Header/MdType

@@ -10 +10 @@
 
 Due to the difference in granularity it might be good to be able to select CMD records of a specific granularity, e.g., collection or item level.
+
+==== Discussion ====
+
+[[schiel|Florian]]: Why restrict this to a a two-level granularity 'collection' and 'part_of_collection'? Most of us agree that relations between MD instances are necessary and should be made possible (see for instances the discussions in the VLO task force group). The very first relations that all MD providers using hierarchical MD structures will apply are 'is_part_of' and 'has_part'. Once these relations are encoded, you don't need any rigid two-level granularity as proposed here: just the fact that a relation 'is_part_of' is present indicates that this MD cannot be the root of a resource. In fact both relations are already used in CMDI 1.1: namely the header element 'isPartOf' (= relation 'is_part_of') and the ResourceProxyLink of type 'Metadata' (= relation 'has_part').
+To my knowledge even in IMDI unrestricted hierarchies have been used. In the current CMDI at least the centers BAS and IDS uses relations like above. Relations will make MdType obsolete.
 
 == Proposed solutions ==