- From: <Simon.Cox@csiro.au>
- Date: Tue, 28 Nov 2017 02:43:21 +0000
- To: <aisaac@few.vu.nl>, <public-dxwg-wg@w3.org>
+1 It is not possible to have universal hard rules for versions, so our approach to versioning must be to enable any and all local strategies, and maybe demonstrate patterns for how to record some of the most well-known strategies. -----Original Message----- From: Antoine Isaac [mailto:aisaac@few.vu.nl] Sent: Monday, 27 November, 2017 21:01 To: public-dxwg-wg@w3.org Subject: Re: dxwg-ACTION-61: Rewrite 6.6.1 (now 6.2.2) Hi, I'm going to stay in line with my previous statements that we should avoid try to introduce 'hard' rules for what's a version. This would be too prescriptive. So David's wording is an improvement. Actually I'd even suggest to change 'that motivate the creation of a new version' into 'that are likely to motivate the creation of a new version' so that the final word is left to data publishers themselves. Best, Antoine On 27/11/17 08:51, Karen Coyle wrote: > Dave, I like this wording. The requirement, as it strikes me, sounds > like guidance for best practices rather than specific rules. Is that > how others see it? > > kc > > On 11/26/17 10:12 AM, david.browning@thomsonreuters.com wrote: >> (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 Tuesday, 28 November 2017 02:44:48 UTC