Changes between Version 54 and Version 55 of VLO-Taskforce/Relations


Ignore:
Timestamp:
11/29/14 14:24:37 (9 years ago)
Author:
fankhauser@ids-mannheim.de
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VLO-Taskforce/Relations

    v54 v55  
    296296
    297297The inverse relationship should (must?) be represented by means of isPartOfList. ([[herold|Axel]]: Why this redundancy? The inverse can always be derived.)
     298([[Fankhauser|Peter]]: Indeed for the VLO which has a full harvest of all repository metadata, this can in principle be derived. However, when some agent is just
     299accessing the CMDI-record for some part of a resource, it does not know, to which resource(s) this part belongs. I am fine with dropping this as a requirement,
     300and rather just allow the representation of isPartOf relationships in the component part, just like any other relationship. In this case we could also consider to
     301drop isPartOfList in the header.)
    298302
    299303This seems to be consistent with e.g. https://trac.clarin.eu/attachment/wiki/CMDI%201.2/header.pdf,