RE: Examples or best-practices with versioning SKOS

XKOS is also worth a look.
In particular see https://linked-statistics.github.io/xkos/xkos-best-practices.html#bp-evolution

Cheers - Simon

dr.shorthair@pm.me
https://github.com/dr-shorthair
+61 403 302 672

On Boonwurrung land

Sent with [Proton Mail](https://proton.me/mail/home) secure email.

On Friday, 22 November 2024 at 05:30, Mark Wallace <mark.wallace@semanticarts.com> wrote:

> - how can you properly attach a version number?
>
> I have typically used owl:versionIRI to assign a version to a Concept Scheme.
>
> - is there any consensus or vocabulary on how to describe versioning?
>
> We use http://semver.org version numbering conventions, e.g. something like:
>
> <http://example.com/taxo/myScheme> a skos:ConceptScheme
>
> ; owl:versionIRI <http://example.com/taxo/myScheme1.3.2>
>
> .
>
> - how to deal with deprecation?
>
> For the scheme as a whole? Interesting. Have not done that. We just load the ‘right’ version into our triple store. I guess one could deprecate a version w/ this triple:
>
> <http://example.com/taxo/myScheme1.3.2> owl:deprecated true.
>
> - how can users migrate from version a to version b?
>
> See below answer.
>
> - how to properly version concept and concept scheme URIs, let alone the links between them?
>
> We have generally not put version info into the particular IRIs of each concept nor the scheme. So upgrading to a new version generally just means loading the new version into the triple store.
>
> FWIW, and respectfully,
>
> Mark
>
> From: Miel Vander Sande <miel.vandersande@meemoo.be>
> Sent: Thursday, November 21, 2024 4:10 AM
> To: SW-forum <semantic-web@w3.org>; public-esw-thes-request@w3.org
> Subject: Examples or best-practices with versioning SKOS
>
> Hello all,
>
> I was wondering if any of you has some experience with maintaining multiple versions of a SKOS Concept Scheme and its Concepts.
>
> Some specific guidance I'm looking for:
>
> - how can you properly attach a version number?
>
> - is there any consensus or vocabulary on how to describe versioning?
>
> - how to deal with deprecation?
>
> - how can users migrate from version a to version b?
>
> - how to properly version concept and concept scheme URIs, let alone the links between them?
>
> - ...
>
> For each of these, I can think of some solution, but I was wondering if anyone has faced the same questions and can share how you solved them? Any examples or best-practices would be very welcome.
>
> Best,
>
> --
>
> https://meemoo.be/nl
>
> Miel Vander Sande
> Data Architect
>
> meemoo vzw | Ham 175, 9000 Gent | [https://www.meemoo.be/](https://meemoo.be/nl)
> t +32 9 298 05 01 | m +32 496 83 21 29
>
> [App Banner Image](https://kennisbank.meemoo.be/)
>
> [__tpx__]