Context Navigation

Element

v8	v9
73	73	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''.
74	74
	75	[[twagoo\|Twan]]: That's true, a component does not define the specification of a full resource ''per se''. My point is that, I think, elements never do/can/should. If an element describes a property of a resource, there will always be component higher up in the tree that selects the resource. Even with bad modeling, I think that would be hard to avoid but maybe someone can provide a counterexample.
	76
75	77	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.
76	78