Changes between Version 6 and Version 7 of CMDI 1.2/Resource proxies/Element

Timestamp:

01/17/14 15:13:49 (10 years ago)

Author:

oddrun.ohren@nb.no

Comment:

--

CMDI 1.2/Resource proxies/Element

@@ -62 +62 @@
 
 Oddrun: I find this sentence from above misleading: "Components ''[did you mean profiles?]'' describe resources and parts thereof; elements represent individual properties of those (sub)resources. Therefore the reference to an individual resource should always happen from the component. An individual element can never refer to entire resource." 
-Firstly, IMHO  individual elements may well refer to the entire resource. In fact, most often they do, - however, they  describe ''an aspect'' of the resource as a whole. Examples: resourceName, size, licence, and countless others. Secondly, given the recursive nature of components, whether modelling a piece of metadata as components or elements is often a matter of taste. Example: Information about the size of a resource may be modelled as an element (possibly with an attribute ''unit'') or as a component with 2 elements ''size'' and ''sizeUnit''. 
+
+Firstly, IMHO  individual elements may well refer to the entire resource. In fact, most often they do, - however, they  describe ''an aspect'' of the resource as a whole. Examples: resourceName, size, licence, and countless others. 
+
+Secondly, given the recursive nature of components, whether modelling a piece of metadata as components or elements is often a matter of taste. Example: Information about the size of a resource may be modelled as an element (possibly with an attribute ''unit'') or as a component with 2 elements ''size'' and ''sizeUnit''. 
+
 Components that are ''profiles'' on the other hand, do represent a holistic description of the resource as a whole, and I think it is preferable to  reserve the ResourceProxyList in a CMDI file for resources/files that actually constitute the ''described resource''. Other relevant resources (documentation, reviews, publications, a.o.) should be referenced from appropriate parts of the metadata instance. If such resources only can be referenced from components, one would have decide this at model time, which perhaps is no big deal? Especially if there is a risk of increased malpractice attached to allowing it for elements, too.