[dxwg] Using dcat:next and dcat:version in Dataseries (#1409)

sde01 has just created a new issue for https://github.com/w3c/dxwg:

== Using dcat:next and dcat:version in Dataseries ==
### Revising a dataset in a Dataserie
Status:

Identifier:

Creator: sde

## Tags
''Optional space-separated list of tags out of the above catalog (extend on demand)''
dcat Dataserie pav:version


## Problem statement
Should dcat:prev and dcat:next be updated when a dataset in the serie is revised ?

Let’s consider example  38
```

ex:budget a dcat:DatasetSeries ;
  dcterms:title "Budget data"@en ;
  .
  
ex:budget-2018 a dcat:Dataset ;
  dcterms:title "Budget data for year 2018"@en ;
  dcat:inSeries ex:budget ;
  dcterms:issued "2019-01-01"^^xsd:date ;
  dcat:next ex:budget-2019 ;
  .
  
ex:budget-2019 a dcat:Dataset ;
  dcterms:title "Budget data for year 2019"@en ;
  dcat:inSeries ex:budget ;
  dcterms:issued "2020-01-01"^^xsd:date ;
  dcat:prev ex:budget-2018 ;
  dcat:next ex:budget-2020 ;
  .
  
ex:budget-2020 a dcat:Dataset ;
  dcterms:title "Budget data for year 2020"@en ;
  dcat:inSeries ex:budget ;
  dcterms:issued "2021-01-01"^^xsd:date ;
  dcat:prev ex:budget-2019 ;
  .
```

Now let’s consider that budget-2019 is revised with a new dataset budget-2019-rev1

Dataserie can be updated in different ways

* budget-2019-rev1 can replace budget-2019 in the serie 
  * As a consequence budget-2018 and budget-2020 have to be updated for dcat:next / dcat:prev fields
* budget-2019-rev1 can be inserted in the Dataserie in between budget-2019 and budget-2020 
  * As a consequence, budget-2019 and budget-2020 have to be updated for dcat:next / dcat:prev fields
* No update to the dataserie. 
  * When encountering a dataset is a serie, one must check if a new version is available for this dataset. 
* budget-2019 is turned into a Dataserie and holds budget-2019-rev0 and budget-2019-rev1
  * This seems to be over engineering here


What will be the recommendation? 

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1409 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 1 October 2021 09:45:43 UTC