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

Timestamp:

01/22/14 11:03:35 (10 years ago)

Author:

twagoo

Comment:

--

CMDI 1.2/Resource proxies/Element

@@ -65 +65 @@
 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. 
 
+  [[twagoo|Twan]]: Here's how I understand the intended relation between profiles, (non-profile) components and elements: profiles define the description of a resource or a set of related resources; in the latter case, different components can be used to define the description of individual resources within that set by collecting a set of properties/aspects that make up this description; elements finally define these properties/aspects in terms of value scheme, cardinality etc. 
+
+  So in the metadata instances that reflect this hierarchy, we need to distinguish between, on the one hand, a ''reference'' to resource as a whole, which creates a context for describing its properties, and, on the other hand, the fields (i.e. element instantiations) nested within this context that describe the resource one property at a time. 
+
+  This relation between component (instantiations) and element (instantiations) is reflected by the fact that a ref can occur on the component level but not on the element level.
+
 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''.