Re: Versioning

Hi Makx,

Yes, "version" is a polyseme term and all of us may not necessarily mean
the same thing by a version. What I had in mind when I wrote that use case
was mainly dataset evolution and I think how a dataset evolves (by
modification, extension, replacement) and when (snapshots, time series) are
closely related to evolution. However, the use of term versions for
conversions and different granularities may have more notable differences
from the evolution-based versions. So I agree it will be beneficial to
break this use case into more specific ones and add more specific
requirements to each.

Best Regards,
Nandana

On Mon, Jun 5, 2017 at 12:44 PM, Makx Dekkers <mail@makxdekkers.com> wrote:

> Apologies for my slow reaction in the discussion today in the call on the
> versioning use case, https://www.w3.org/2017/dxwg/
> wiki/Use_Case_Working_Space#Dataset_Versioning_Information. I was
> struggling with my connection and just managed to note in IRC that I didn’t
> agree with the use case. Disagreeing is not the right word but I felt that
> we maybe need to discuss first what we mean by ‘version’, because in my
> work over the years I have engaged in discussions where people didn’t have
> the same opinion on what we were talking about.
>
>
>
> As I see it, there may be various types of ‘versioning’ relationships
> between datasets. For example:
>
>
>
>    - Evolution: for example, a dataset that is published with
>    year-to-date information; every week or month, new, recent data is appended
>    to the existing data.
>    - Replacement: for example, existing data was wrong in some way, and a
>    new dataset is published that replaces the old data.
>    - Snapshots: for example, continuously changing data like the state of
>    traffic or weather maps with hourly snapshots.
>    - Time series: for example, annual budget data.
>    - Conversion: for example, data that is transformed from one
>    coordinate system to another, or from one set of units to another; similar
>    to translation of textual resources.
>    - Lower/higher granularity: for example, maps in different scales,
>    images in different resolutions, compression like MP3 versus CD sound, and
>    summaries of large amounts of data.
>
>
>
> In my mind, the use case https://www.w3.org/2017/dxwg/
> wiki/Use_Case_Working_Space#Dataset_Versioning_Information is a useful
> placeholder for a number of more specific cases that might have different
> requirements. I am pretty sure that some of those requirements could be
> satisfied by some explanatory text in the DCAT specification; some others
> might need addition of other properties (or even classes?) to DCAT.
>
>
>
> I am planning to write some of this up in separate use cases over the next
> few weeks.
>
>
>
> Makx.
>
>
>
>
>