Re: [dxwg] Should we specialize dcterms:hasPart for dcat:DatasetSeries? (#1307)

Some discussions about the names of these properties have taken place in PR  #1328.
I am going to report the gist of the discussions below, as this issue seems to be a better place where to discuss.
_Originally posted by @andrea-perego in
>For the inverse of `dcat:inSeries` I suggest we use something shorter: `dcat:hasMember`.

>Another option for the names of these properties is `dcat:hasParent` / `dcat:hasChild` , following the terminology used in ISO 19115 for dataset series.

_Originally posted by @riccardoAlbertoni in
>Yes, the names are long. However, I wonder if mentioning 'series' in the property names can help recall and use these properties more coherently. This also considering possible confusion with `dcterms:hasPart` and other parts-related properties.  What do you think?

_Originally posted by @andrea-perego in
>I don't think it's necessary to recall the scope of this property, as it has its own domain (`dcat:DatasetSeries`). For the same reason, including "series" in the property name looks redundant, and I am not very worried about being confused with `dcterms:hasPart`.

>However, if the close semantics of "part" and "series" raises concerns on improper use, we should consider other options.

>`dcat:hasChild` / `dcat:hasParent` are a good alternative, IMO, and they reflect the hierarchical structure of dataset series, as already mentioned in PR and in

_Originally posted by @riccardoAlbertoni in

>Andrea, If you think `dcat:hasSeriesMember` is too long and not acceptable then `dcat:hasMember` will be my choice.

>Using `dcat:hasChild` and `dcat:hasParent` helps those familiar with ISO dataset series.  However, we target a larger audience. In this target, I suspect people might have different views of what is considered a child of a dataset (potentially, anything originated by a dataset can be considered a 'child'!? and that might be confusing).

GitHub Notification of comment by riccardoAlbertoni
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 16 March 2021 20:50:36 UTC