[dxwg] Including more machine-actionable Version Delta? (#1271)

riccardoAlbertoni has just created a new issue for https://github.com/w3c/dxwg:

== Including more machine-actionable Version Delta? ==
Besides the human-readable descriptions of the changes of version #89, we might want to discuss suggestions on also considering more machine-friendly references. See below:

>What about a pointer to a Git transaction?
_Originally posted by @nicholascar in https://github.com/w3c/dxwg/issues/89#issuecomment-368896015_ 

>I quite like the idea of a Git transaction but not all new versions would naturally be picked up that way, I think.  For those that do, then perhaps we should encourage it
An example where the textual approach works better would be where a publisher has changed coverage in some way, but the rest stays the same.  [This is fairly common practice with financial data - I may have a dataset that claims to cover corporates across the EU for example but has systematic issues for the UK (for example).  When I address those issues, I may want to treat it as a new version of the original dataset rather than a new dataset as a way of signaling to users that its an important change but still an evolution of what I produced before]  This is all information domain-specific, of course.
_Originally posted by @davebrowning in https://github.com/w3c/dxwg/issues/89#issuecomment-368914163_



Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1271 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 November 2020 22:46:27 UTC