Re: Versioning

Hi,

As it was correctly pointed out in the call that the requirements of the
UC-ID4 was more in the solution space, I've tried to reword the
requirements [1] as following and added links to DWBP:

Requirements:

   - A definition of what is meant by version in this context and how it
   relates to dataset, distribution should be provided.
   - Different versioning scenarios should be supported (e.g., dataset
   evolution, conversions/translations, granularities/subsets).
   - Each version should provide a version identifier and other relevant
   metadata.
   - It should be possible to provide metadata about when a version was
   created (released).
   - It should be possible to provide identifiers for the previous/next
   versions when applicable (if they are in chronological order).
   - It should be possible to provide what has been changed when applicable
   (if they are in chronological order).
   - It should be possible to discover versions of a given dataset in a
   catalog.
   - W3C DWBP guidelines on versioning: BP7. Provide a version indicator,
   BP8. Provide version history, BP11. Assign URIs to dataset versions and
   series.

Best Regards,
Nandana

[1]
https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Dataset_Versioning_Information

On Tue, Jun 6, 2017 at 7:03 AM, Makx Dekkers <mail@makxdekkers.com> wrote:

> Jacco,
>
> Good point that we should look at earlier work.
>
> I looked through the use cases at https://www.w3.org/TR/dwbp-ucr/ but
> there are only a few that explicitly address versioning.
>
> Two requirements were identified:
>
> https://www.w3.org/TR/dwbp-ucr/#R-VocabVersion: "Vocabularies should
> include versioning information"
> https://www.w3.org/TR/dwbp-ucr/#R-DataVersion: "If different versions of
> data exist, data versioning should be provided."
>
> In DXWG, we could look a bit more into the requirements to express the
> possible *relationships* between versions of datasets which apparently DWBP
> did not do.
>
> Makx.
>
> -----Original Message-----
> From: Jacco van Ossenbruggen [mailto:Jacco.van.Ossenbruggen@cwi.nl]
> Sent: 06 June 2017 11:41
> To: public-dxwg-wg@w3.org
> Subject: Re: Versioning
>
> On 06/06/2017 09:51 AM, Phil Archer wrote:
> > Taking a standards design angle on this, we have a concept, versioning,
> that is understood in different ways by different people and in different
> circumstances.
>
> @Phil, I think we can all agree on this. But I'm with Makx, this should
> not be a reason to stop us from collecting use cases relevant to different
> versions of versioning...
>
> @all: To speed up the versioning use case collection process, would it
> make sense to look at our use cases in terms of a delta with the ones
> already collected in [1]?
> Then the questions could be
> - which of the version-related use cases collected by #dwbp would be also
> applicable to #dxwg
> - are there important use cases missing from #dwbp we would like to add?
>
> I briefly skimmed [1] and I think it does a pretty good job in covering
> the versioning-related requirements I had in mind.
>
> Luiz, Makx, what do you think?
>
> Jacco
>
> [1] https://www.w3.org/TR/dwbp-ucr/
>
>
>