Re: [dxwg] Version subject [RVSS] (#93)

I think that this is something that can be illustrated in a primer, some of
the options and how DCAT might be used together with prov, pav, or similar

On Thu, 7 May 2020, 17:27 Riccardo Albertoni via GitHub, <sysbot+gh@w3.org>
wrote:

> I think we are close to an agreement on this issue,  as the following
> sentence, already included in  DCAT 2, shows that we apply versioning on
> all the first-class entities (datasets, distribution, but in principle also
> catalogs and data service)
>
> see section about [Versioning](
> https://www.w3.org/TR/vocab-dcat-2/#dataset-versions)
> >Versioning can be applied to any of the first-class citizens DCAT
> resources, including Catalogs, Datasets, Distributions. The notion of
> versions is very much related to the community practices, data management
> policy and the workflows in place. It is up to data providers to decide
> when and why a new version should be released. For this reason, DCAT
> refrains from providing definitions or rules about when changes in a
> resource should turn in a new release of it.
>
> Some concerns were expressed on versioning for data services, in
> particular,  whether content or service changes should trigger a new
> version for data Service, but I think this is up to the adopters to decide.
>
> I suggest adding the requirement mentioned by Andrea about the "resource
> status" as a separate issue. Then if there are no objections, I think we
> can close this GitHub issue.  What do others think?
>
> --
> GitHub Notification of comment by riccardoAlbertoni
> Please view or discuss this issue at
> https://github.com/w3c/dxwg/issues/93#issuecomment-625359493 using your
> GitHub account
>
>