Changes between Version 2 and Version 3 of CMDI 1.2/Resource proxies/ResourceRelation
- Timestamp:
- 12/03/13 16:08:14 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Resource proxies/ResourceRelation
v2 v3 60 60 ==== Pros ==== 61 61 62 It adds semantic grounding of the relation which is an improvement 62 * It adds semantic grounding of the relation 63 63 64 64 ==== Cons ==== 65 65 66 It still forces direction on the relation, and limits the number of resources taking part in the relation to two. 66 * Forces direction on the relation 67 * Limits the number of resources taking part in the relation to two. 67 68 68 69 ==== Centre impact ==== 69 70 71 Tools that generate/process resource relation lists will need to be adapted 70 72 71 73 ==== Implementation examples ==== 72 74 75 Instance: see example above. comp2schema example: TODO 73 76 74 77 ==== Discussion ==== … … 76 79 Discuss this solution proposal in this section 77 80 78 79 81 === Second solution === 80 82 83 A more flexible solution was discussed recently. It would have for example: 84 85 {{{#!xml 86 <ResourceRelationList> 87 <ResourceRelation> 88 <RelationType dcr:datcat="http://www.isocat.org/datcat/DC-2318">annotates</RelationType> 89 <Resource ref="rp1"> 90 <Role dcr:datcat="http://www.isocat.org/datcat/DC-4009">annotation</Role> 91 </Resource> 92 <Resource ref="rp2"/> 93 <Role dcr:datcat="http://www.isocat.org/datcat/DC-2656">annotated</Role> 94 </Resource> 95 </ResourceRelation> 96 </ResourceRelationList> 97 }}} 98 99 The ''dcr:datcat'' attributes should probably be optional. 100 101 The maximal number of <Resource> elements should be unbounded, allowing for relations between any number of resources. (EXAMPLE? USE CASE?) 81 102 82 103 ==== Pros ==== 83 104 84 ... 105 * Semantic marking of both relation type and roles of resources 106 * Option to have more than two resources involved in a relation 107 * No forced relational direction 85 108 86 109 ==== Cons ==== 87 110 88 ... 111 * More verbose 112 * More processing of datacategories 113 * No default direction (while most cases will be covered by subject-object in that order) 89 114 90 115 ==== Centre impact ==== 91 116 117 Tools that generate/process resource relation lists will need to be adapted 92 118 93 119 ==== Implementation examples ==== 94 120 121 Instance: see example above. comp2schema example: TODO 95 122 96 123 ==== Discussion ==== … … 99 126 100 127 == Tickets == 101 {{{#!comment102 Below replace the word 'keyword' in both the the text and the ticket query103 }}}104 128 Tickets in the CMDI 1.2 milestone with the keyword ''resourcerelationlist'': 105 129 [[TicketQuery(keywords=~resourcerelationlist,milestone=CMDI 1.2,format=table,col=summary|owner|component|priority|status)]]
