Re: [vocab-dcat-3] previousVersion, NextVersion, hasCurrentVersions Questions

This is a really good question. We ought to support semantic versioning, but our next/previous only supports linear versioning. I wonder if we should consider nextMajorVersion, nextMinorVersion, nextPatchVersion, previousMajorVersion, previousMinorVersion, previousPatchVersion?
-Annette

> On Dec 13, 2022, at 5:00 AM, Martial.Honsberger@bfs.admin.ch wrote:
> 
> Hello,
> I have a question about the implementation of Versioning in DCAT 3.
>  
> Using the dcat:previousVersion, I can find a previous Version of a dataset.
> Let’s say we have the following versioning example :
> Classification v1.0
>             Classification v1.1
> Classification v2.0
> If I set previousVersion to Classification v1.0 for v1.1 as well as for v2.0, what would be the inverse property nextVersion ? Would it be v1.1 and v2.0 (multiple values) or is it forbidden to set two datasets on the same previous version ?
>  
> Furthermore, how is meant to be evaluated the value of “hasCurrentVersion” ? Should this be manually set or would this be “calculated” by means of subsequents previousVersion sets ?
>  
> Thank you in advance for your help
>  
> Martial Honsberger
> Spécialiste en Interopérabilité
>  
> Département fédéral de l'intérieur DFI
> Office fédéral de la statistique OFS
>  
> Espace de l'Europe 10, CH-2010 Neuchâtel
> Tel.   +41 58 467 10 03
> martial.honsberger@bfs.admin.ch <mailto:martial.honsberger@bfs.admin.ch>
> http://www.statistique.admin.ch <http://www.statistique.admin.ch/>