- From: David Browning via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Feb 2018 15:36:29 +0000
- To: public-dxwg-wg@w3.org
@makxdekkers - yes, I agree it needs to be part of a broader/more thorough discussion on versioning (persummably under action #90 ). I also agree that these are both examples of dct:Dataset so could use some links as you describe, if that mechanism is available. What the publisher is usually trying to achieve by calling the new set of published data a new version of a pre-existing set is to signall that its a successor or evolution of what was previously available, and perhaps _in the publishers perspective_ essentially replaces it (eventually). It can also help with alignment with non-technical documentation like contracts of supply (though that usually gets confused anyway). I'll put together some coherant notes and we can discuss under #90. The point I was trying to make here is that version delta info can cover a wide range of stuff, not all of it that would come from some easily referenceable process tool like github. [Assuming I've understood the suggestion, of course] -- GitHub Notification of comment by davebrowning Please view or discuss this issue at https://github.com/w3c/dxwg/issues/89#issuecomment-369277974 using your GitHub account
Received on Wednesday, 28 February 2018 15:36:34 UTC