Changes between Version 17 and Version 18 of VLO-Taskforce/Relations


Ignore:
Timestamp:
01/23/14 09:21:37 (10 years ago)
Author:
fankhauser@ids-mannheim.de
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VLO-Taskforce/Relations

    v17 v18  
    102102[[Image(mkhz-representation.jpg)]]
    103103
    104 === Leibzig ===
     104=== Leipzig ===
    105105
    106 TBD when the webservice is available again.
     106Leipzig's approach to representing relationships is similar to IDS (and BAS) Option b. The differences are as follows:
     107
     108a. For each relationship there exists a separate Component, which already has a built-in attribute ref of type idrefs.
     109b. The description of a relationship is structured rather than just a simple anchor text.
     110c. Inverse relationships seem not to be represented explicitly.
     111
     112Example:
     113
     114{{{
     115<ResourceProxy id="ulei-11858-00-229C-0000-0001-B06F-3-component-dataprovider-1">
     116  <ResourceType mimetype="text/xml">Metadata</ResourceType>
     117  <ResourceRef>http://hdl.handle.net/11858/00-229C-0000-0001-B06F-3@type=dataprovider&id=1</ResourceRef>
     118</ResourceProxy>
     119...
     120<LCC_DataProvider ComponentId="clarin.eu:cr1:c_1381926654509" ref="ulei-11858-00-229C-0000-0001-B06F-3-component-dataprovider-1">
     121  <Id>1</Id>
     122  <Name>LCC data provider "www.shortnews.de" in resource with identifier 11858/00-229C-0000-0001-B06F-3</Name>
     123  <Description xml:lang="eng">Data provider of the Leipzig Corpora Collection: www.shortnews.de</Description>
     124</LCC_DataProvider>
     125}}}
    107126
    108127=== Summary on Representation of Relationships ===