Changes between Version 25 and Version 26 of CMDI 1.2/Resource proxies/ResourceRelation

Timestamp:

04/01/14 07:04:55 (11 years ago)

Author:

oddrun.ohren@nb.no

Comment:

--

CMDI 1.2/Resource proxies/ResourceRelation

@@ -28 +28 @@
 
 A query targeted  towards all harvestable metadata early February 2012 resulted in  only 32 valid occurrences of ResourceRelation. 
-On the other hand, an investigation into metadata from Clarin-D revealed a plethora of ways to express relations between resources, none of which used the ResourceRelation mechanism. It is obvious that exploiting tools have a hard time interpreting relationships between resources, irrespective what is done to ResourceRelationList.
+On the other hand, an investigation into metadata from Clarin-D revealed a plethora of ways to express relations between resources, none of which used the ResourceRelation mechanism. It is obvious that exploiting tools will have a hard time interpreting relationships between resources, irrespective what is done to ResourceRelationList.
 
 During discussion, several solutions have been proposed:
 * Declare source and target resources explicitly as well as connect the relation type  to a concept registry, and thereby make the semantics clearer for binary relations 
 * Generalize the above by allowing the modeller to specify the resources’ roles in the relationship, instead of just source and target. 
-* Remove  the ResourceRelationList altogether, on account of the almost total lack usage, and the richness of other ways to express relatioships in CMDI
+* Remove  the ResourceRelationList altogether, on account of the almost total lack of usage, and the richness of other ways to express relationships in CMDI
 
 From the exchange on the wiki it is clear that discussions on this topic will have to go on beyond the deadline for CMDI 1.2.  Hence, it is felt that no drastic change should be performed in CMDI 1.2. The proposed solution merely attempts to clarify the semantics of the current specification, all the while keeping the door open for expressivity extension at a later date.
@@ -52 +52 @@
 
 The ''Resource'' elements @role and @ref should be mandatory, dcr:roledatcat optional, minOccurs=2, maxOccurs=2.
-(An alternative way of specifying this would be to define Roles as sub-elements of Resource. The choice should be made according to the decision on general schema consistency)
+(An alternative way of specifying this would be to define Roles as sub-elements of Resource. The choice concerning this should be made according to the decision on general schema consistency)