- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Mar 2021 23:28:40 +0000
- To: public-dxwg-wg@w3.org
Coming back to the original topic of this issue: I've create a PR (https://github.com/w3c/dxwg/pull/1340) to add `adms:last`, `adms:next`, `adms:prev` to `dcat:Resource`. After having done that, I wonder whether we should define these properties in the DCAT namespace. The reason is as follows: `adms:last`, `adms:next`, and `adms:prev` are defined in ADMS as subproperties of `xhv:last`, `xhv:next`, and `xhv:prev`, which are specifically meant to relate resources that are part of an ordered collection. E.g., [the definition of `xhv:prev`](https://www.w3.org/1999/xhtml/vocab#prev) is: > prev refers to a previous resource (before the current one) in an ordered collection of resources. As a side note, these `xhv` properties basically correspond to those defined in the IANA Link Relations register (last, next, prev), and used both in HTTP Link headers and in HTML `LINK` elements. This makes `adms:last`, `adms:next`, and `adms:prev` fit for being used to relate resources in a dataset series. However, their textual description mentions explicitly the notion of version, which we are considering as distinct from the notion of series, and described by using dedicated properties (e.g., `dcat:previousVersion`). E.g., [the definition of `adms:prev`](https://www.w3.org/TR/vocab-adms/#adms-prev) is: > A link to the previous version of the Asset. Because of this, it is maybe preferable to define `dcat:last`, `dcat:next`, and `dcat:prev`, to avoid any confusion about the actual use of these properties in DCAT. WDYT? -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1308#issuecomment-808816992 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 March 2021 23:28:42 UTC