- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Feb 2021 09:30:01 +0000
- To: public-dxwg-wg@w3.org
@agreiner said: > I think 'latest' is better than 'last' here, but it's still not intuitive in my opinion. Maybe we should have hasCurrentVersion and hasCurrentStableVersion. Based on what discussed so far, I'm still unsure whether there's a consensus that `dcat:hasLast(est)Version` is needed. About `dcat:hasCurrentVersion`, I'm actually re-considering my claim that this should point to a stable version, which was mainly reflecting the examples under discussion, but not alternative scenarios. `dcat:hasCurrentVersion` (as `pav:hasCurrentVersion`) links an unversioned resource to a version exactly corresponding to it. Nothing else. So, whether it points or not to a stable version depends on the publication rules in place. E.g., a publisher may decide that the unversioned resource must always correspond to the latest version, irrespective of its status (draft, stable, whatever). Or, as in the case of DCAT 3, if a stable version of a resource (e.g., a Recommendation) is not yet available, `dcat:hasCurrentVersion` points to the latest published draft. This may make even more unclear the difference between `dcat:hasCurrentVersion` and `dcat:hasLastVersion`, so it might be safer to drop `dcat:hasLastVersion` unless we have a strong use case to support it. PS: I'll update the draft to clarify the actual semantics and use of `dcat:hasCurrentVersion`. My apologies for having driven the discussion in the wrong direction. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1304#issuecomment-785753193 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 February 2021 09:30:03 UTC