W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > April 2018

Re: [dxwg] Temporal coverage [RTC]

From: Andrea Perego via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Apr 2018 21:25:51 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-382885830-1524173150-sysbot+gh@w3.org>
Checking [the relevant use case (UC27)](https://www.w3.org/TR/dcat-ucr/#ID27), I'm not sure about the relevance of some of the mentioned approaches (in particular, DATS and DataCite):

> To address this issue, [VOCAB-ADMS] makes use of properties schema:startDate and schema:endDate [SCHEMA-ORG]. [DCAT-AP] follows the same approach. Other existing approaches are: DATS, DataCite and Google datasets

As far as I know, DataCite has no specific element for temporal coverage, and the same seems to apply to [DATS](https://docs.google.com/spreadsheets/d/1aHj_Qvlr7Sf4DlU4uc37PQEOPha8jTxMEdyL_Q7geLQ/edit#gid=0) (@agbeltran , please correct me if I'm wrong).

On the other hand, the [Google's approach](https://developers.google.com/search/docs/data-types/dataset#time) outlines another solution not explicitly mentioned so far, namely, specifying the period with a literal (following ISO 8601) and with a datatype property. It is worth noting that this approach cannot be applied with the property used in DCAT, i.e., `dct:temporal`, which is an object property (so it can be at most a complementary solution).

Coming back to the use case, I think it may be worth providing a brief description of the approach used by Google (and, if relevant, DataCite and DATS).

GitHub Notification of comment by andrea-perego
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/85#issuecomment-382885830 using your GitHub account
Received on Thursday, 19 April 2018 21:25:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:02 UTC