- From: Jesper Zedlitz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Sep 2021 13:55:32 +0000
- To: public-dxwg-wg@w3.org
> If the dataset is that dynamic, shouldn't it be possible to update the timestamps in the metadata whenever it is accessed? It's hard to imagine a desire to use start and end times unless they contain actual times. I'm very uncomfortable with the notion of assigning "now" to anything, as the meaning becomes very unclear to the consumer. The problem occurs when metadata is forwarded to other portals. In Germany the federal states operate their own open data portals. Once a day or one a week the metadata is harvested by the national open data. This in turn is harvested by the European portal. So it takes a few days for the data to arrive at the European portal. In some cases also municipal portals are involved, adding to the delay. In that case it is important *not* to have to specify fixed times. Without "floating" time data, we often (or nearly always) would have incorrect temporal metadata. For example, the end date in the European data portal would be already a week old, while the federal has already updated its end date. -- GitHub Notification of comment by jze Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1403#issuecomment-925839278 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 September 2021 13:55:35 UTC