RE: dxwg-ACTION-61: Rewrite 6.6.1 (now 6.2.2)

(Given that we're aiming to agree the FPWD of the UCR on Tuesday, I decided that I'd send this out as an email rather than changing it in github where I'm something of a nervous neophyte...but learning...)

The renumbering of the requirements since the recent f-to-f means this action now applies to requirement 6.2.2.  The text has already been pared back since San Francisco, and is much better but I suggest it's still somewhat misleading.

Existing: "Provide a conceptual definition of what is considered a version with regard to modifications of the respective subject. The definition should provide a clear guidance on conditions, type and severity of a resource's update that motivate the creation of a new version in scenarios like dataset evolution, conversion, translations etc".

Proposed: "Provide clear guidance on conditions, type and severity of a resource's update that motivate the creation of a new version in scenarios such as dataset evolution, conversion, translations etc, including how this may assist change management processes for consumers (e.g. semantic versioning techniques)"

That ties in better with the content of the use cases (especially what DWPB actually says about the lack of any consensus on versioning strategy other than in specific limited domains).


· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 
David Browning
Platform Technology Architect

Thomson Reuters

Phone: +41(058) 3065054
Mobile: +41(079) 8126123

david.browning@thomsonreuters.com
thomsonreuters.com




-----Original Message-----
From: Dataset Exchange Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] 
Sent: 15 November 2017 16:57
To: public-dxwg-wg@w3.org
Subject: dxwg-ACTION-61: Rewrite 6.6.1

dxwg-ACTION-61: Rewrite 6.6.1

https://www.w3.org/2017/dxwg/track/actions/61


Assigned to: David Browning




Rewrite 6.6.1

Received on Sunday, 26 November 2017 18:12:43 UTC