- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Feb 2021 09:47:03 +0000
- To: public-dxwg-wg@w3.org
@aisaac said: > @andrea-perego Maybe we could just continue with the bus stop example, for the sake of simplicity. That example is not completely fit to illustrate all the properties, but we can give it a try. Anyway, if the WG has any real-world cases we can re-use, that would be much better. > As for the name of the property, I guess I can live with re-using PAV's "current" wording, as long as there is no "last" just next to it in DCAT. So maybe just changing the name of `dcat:hasLastVersion` would be alright. I am open to proposals. > Coming back to my questions, considering @andrea-perego 's point on the experimental nature of `dcat:hasLastVersion` I assume that the answer to my first point/question > > > In other words, I would expect dcat:hasCurrentVersion to be always present, while dcat:hasLastVersion would be used for specific cases. > > would be that yes, `dcat:hasCurrentVersion` should be always present, while `dcat:hasLastVersion` would be used for specific cases. Yes. It is likely that the presence of an instance of `dcat:hasLastVersion` implies also that an instance of `dcat:hasCurrentVersion` is used. But this does not mean that `dcat:hasCurrentVersion` should always be present. The only properties that should be used to specify a version chain and hierarchy are, respectively, `dcat:previousVersion` and `dct:hasVersion`. Using of not the other properties depends on the use case, as said in [ยง10.1.1 Version chains and hierarchies](https://raw.githack.com/w3c/dxwg/dcat-versioning-v2/dcat/index.html#version-history) - quoting: _Property dcat:previousVersion is used to build a version chain, that can be navigated backward from a given version to the first one. This reflects the most typical use case - i.e., linking different versions published as distinct resources in a catalog._ _In addition to this, property dcat:hasVersion can be used to specify a version hierarchy, by linking an abstract resource to its versions._ _If needed, the version hierarchy can be further described by specific properties. More precisely, property dcat:isVersionOf (inverse of dcat:hasVersion) gives the possibility of specifying a back link from a version to the abstract resource, whereas properties dcat:hasCurrentVersion and dcat:hasLastVersion link to, respectively, the current and last versions of the resource. Note that the current version of a resource may be different from the last version: e.g., when the last version is still in draft status, the current one may correspond to the latest stable version of the resource._ > And this would be in favour of not introducing `dcat:hasLastVersion` (or whatever new name for it) at the same level as the others. Do you have any suggestion on how to revise the text? > I'm still wondering about the other one: > > > if the 'latest' version that can be accessed is an 'official' one, would DCAT recommend that two statements are created to link twice the same pair of resources, one with dcat:hasCurrentVersion and one with dcat:hasLastVersion? Possibly yes. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1304#issuecomment-784949659 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 February 2021 09:47:05 UTC