Changes between Version 12 and Version 13 of CMDI 1.2/Resource proxies/Element

Timestamp:

01/23/14 08:22:41 (10 years ago)

Author:

oddrun.ohren@nb.no

Comment:

--

CMDI 1.2/Resource proxies/Element

@@ -68 +68 @@
     Oddrun: What you describe here is ''one'' way of using components to compartmentalise the description of a resource, but not necessarily the most typical one. '''Example''': Consider a resource (corpus)  R with 2 parts Ra and Rb, where Ra is audio and Rb text (transcription of Ra). Now select the profile ''resourceInfo'' for corpora to describe this resource. resourceInfo contains several components pertaining to the decsribed resource (R) as a whole, e.g.   ''contactPerson'' and ''distributionInfo''. These components decsribe specific aspects of R as a whole, they do not concern any one of Ra and Rb in particular.  On the other hand, resourceInfo also contains components pertaining to specific mediatypes (deeper down, in component corpusInfo). In our case we would need to instantiate  ''corpusTextInfo'' and ''corpusAudioInfo''. Here,  each of the components does pertain to one specific part of R, in that corpusAudioInfo obviously describe Ra and corpusTextInfo describe Rb.
 
-The above example illustrates two different criteria for defining components,  both equally legitimate, in my opinion.
+    The above example illustrates two different criteria for defining components,  both equally legitimate, in my opinion.
 
   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.