[dxwg] How to model dct:temporal for continously evolving Datasets? (#1403)

init-dcat-ap-de has just created a new issue for https://github.com/w3c/dxwg:

== How to model dct:temporal for continously evolving Datasets? ==
In GovDataOfficial/DCAT-AP.de#17 we discussed a real usecase where I am surprised to find no obvious answer. 
I escalated the issue to https://github.com/SEMICeu/DCAT-AP/issues/201 where we concluded, that we don't have a (structured) solution.

**Use Case**
There is a Dataset which is updated constantly (`dcterms:accrualPeriodicity`) with a resolution of one hour (`dcat:temporalResolution`). But you can only get the data of the last 10 days.
(Something that's probably pretty common for sensor data. A [sliding window](https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/datastream/operators/windows/#sliding-windows) is what we need to be able to describe.

**How would you model this?** 
Neither `xsd:date` nor `dcterms:PeriodOfTime` allows this. We could maybe get it to work with `xsd:duration`:
```
_:ds  a dcat:Dataset ;
  dcterms:accrualPeriodicity <http://publications.europa.eu/resource/authority/frequency/UPDATE_CONT> ;
  dcat:temporalResolution "PT1H"^^xsd:duration ;
  dcterms:temporal "P10D"^^xsd:duration .
```

But that would not be allowed. And it would only be implicit, that you get the last 10 days.

Does anyone have an idea?

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


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

Received on Monday, 20 September 2021 19:13:45 UTC