Changes between Version 10 and Version 11 of VirtualCollectionRegistry/Help


Ignore:
Timestamp:
08/06/14 09:57:19 (10 years ago)
Author:
Twan Goosen
Comment:

processed TBD's, also see #607

Legend:

Unmodified
Added
Removed
Modified

  • VirtualCollectionRegistry/Help

    v10 v11  
    88 reference:: The virtual collection bundles resources, that are to be cited in a publication.
    99 sample:: This virtual collection bundles is intended to serve as an sample for research data
    10  future-use:: ('''TBD:''' Actually, this is more a placeholder, e.g. people are unsure, what their VC may become. Before publishing, they should select one of the the above. Or, if required, we'll need to add more purposes).
     10 future-use:: The purpose of this virtual collection is not specified yet. Used in published collection is advised against.
     11{{{#!comment
     12Original note by Oliver: ('''TBD:''' Actually, this is more a placeholder, e.g. people are unsure, what their VC may become. Before publishing, they should select one of the the above. Or, if required, we'll need to add more purposes).
     13See #607
     14}}}
    1115
    1216 reproducibility:: An indication of the degree to which results obtained from processing of the present collection can be expected to be stable
    … …  
    2428The following are only relevant for ''intensional'' virtual collections
    2529 [query] description:: A prose description of the procedure by which the collection items can be retrieved from the external service.
    26  [query] URI:: The location of the service from which the items should be retrieved. This value may be a persistent identifier, but could also be a plain URI ('''TBD:''' Should this always be a PID, because URIs are not sustainable by definition?). Example: In case of FCS this could be the URI of an endpoint or a more enhanced aggregator.
     30 [query] URI:: The location of the service from which the items should be retrieved. This value may be a persistent identifier, but could also be a plain URI although this is advised against for published collections.
     31{{{#!comment
     32Original note by Oliver:
     33('''TBD:''' Should this always be a PID, because URIs are not sustainable by definition?). Example: In case of FCS this could be the URI of an endpoint or a more enhanced aggregator.
     34See #607
     35}}}
    2736 query profile:: Identifier of the mechanism, i.e. the protocol to be used, by which the members of the virtual collection should be retrieved. A application exploiting the query can use this to use a proper driver to talk to the service. Example: In case of CLARIN-FCS access the endpoint by FCS-compatible means.
    2837 query value:: The query that should be passed on to the service by which it can look up the items that are part of this collection. This value should be in the query language supported by the service. Example: In case of CLARIN-FCS, this value is the CQL query to be send to the endpoint.