- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Apr 2021 22:56:14 +0000
- To: public-dxwg-wg@w3.org
andrea-perego has just created a new issue for https://github.com/w3c/dxwg: == Do we need the inverse of dcat:prev - i.e., dcat:next? == Issue originally raised in https://github.com/w3c/dxwg/issues/1308#issuecomment-812095271 by @agreiner : > [...] it just occurred to me that next/previous has the same issue for developers as we encountered with membership in a series, that developers won't know in advance which one is being used to hold the chain together and so would have to test for both in code. Also, assigning next when a dataset is first published seems like a stretch, so we again run into the problem of updating the metadata after the fact. Yet, having next when it's available would certainly be useful. I sort of want to make previous required but both encouraged, or say you can't use next without also using previous. Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1346 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 April 2021 22:56:16 UTC