- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Feb 2021 09:20:51 +0000
- To: public-dxwg-wg@w3.org
@makxdekkers I'm not claiming that using DCAT for vocabularies and ontology doesn't work (and in fact I wouldn't hesitate characterize some 'vocabularies' as datasets, especially thesauri) but it's just that using this example may lead us to give more importance to rather untypical cases. @andrea-perego Maybe we could just continue with the bus stop example, for the sake of simplicity. 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. 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. 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? -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1304#issuecomment-784933079 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:20:54 UTC