Related datasets [RRDS]

[jpullmann]

Related datasets [RRDS]

Ability to represent the different relationships between datasets, including: versions of a dataset, collection of datasets, to describe their inclusion criteria and to define the 'hasPart'/'partOf' relationship, derivation, e.g. processed data that is derived from raw data

this requriement to be rolled in here: Update method of Dataset: Indicate the update method of a Dataset description, e.g. whether each new dataset entirely supercedes previous ones (is stand-alone), or whether there is a base dataset with files that effect updates to that base.

Related requirements:  Provenance information [RPIF] 
Related use cases: Relationships between Datasets [ID32] Define update method [ID47] 

[dr-shorthair]

Comment received by email from Nuno Friere suggests using void:rootResource to point to a manifest.

[dr-shorthair]

A general solution for relations from dcat:Resource to any other resource is discussed in #253 and a solution provided in #295.

Guidance on use of more specific properties for relationships between dcat:Datasets should continue here.
In particular considering
(a) the more specialized DCT predicates dct:hasPart/dct:isPartOf , dct:conformsTo , dct:isFormatOf/dct:hasFormat , dct:isVersionOf/dct:hasVersion , dct:replaces/dct:isReplacedBy , dct:references/dct:isReferencedBy , dct:requires/dct:isRequiredBy
(b) the fully general case (possibly using qualified relation pattern and an extensible list of relationship roles)

Should we add local (guarded) constraints on dcat:Dataset so that the range of these properties in this context is required to be dcat:Dataset - see discussion starting here: #253 (comment)

[dr-shorthair]

We should leverage the IANA link relations for the general case.
Perhaps as the value of a specified 'role' property on a qualified relationship #79.
e.g.

ex:Test987
  a dcat:Dataset ; 
  dcat:qualifiedRelation [
    a dcat:QualifiedRelationship ;
    dcat:target <http://example.org/Test123> ;
    dcat:relationRole "canonical" ;
  ] ;
.

[dr-shorthair]

I made a proposal for this in the Wiki page: https://github.com/w3c/dxwg/wiki/Qualified-relations#related-datasets

[davebrowning]

Now that we have introduced dcat:DataService, does the above requirement apply to those catalogued resources as well? In particular, we have specific properties tying dcat:Dataset to dcat:Distribution to dcat:DataDistributionService (dcat:accessService) and back to dcat:Dataset (dcat:servesDataset) but this kind of general requirement seems to suggest an additional/parallel mechanism is desired - or am I missing something?

[dr-shorthair]

General approach to relations in #651