- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Apr 2021 23:03:10 +0000
- To: public-dxwg-wg@w3.org
> > Hm, 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. > > Thanks for the heads-up, @agreiner . > > As #1335, I think this relates to the more general discussion on the possible approach to be used in DCAT to define inverse properties - see #1336 > > I'll create a separate issue to keep track of it, and link to it from the ED. Done - see issue https://github.com/w3c/dxwg/issues/1346 and PR https://github.com/w3c/dxwg/pull/1345 (https://github.com/w3c/dxwg/pull/1345/commits/8ce4db285ea90102b77ce346e888606b156d9db2) -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1308#issuecomment-814488787 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 23:03:12 UTC