- From: makxdekkers via GitHub <sysbot+gh@w3.org>
- Date: Sat, 17 Mar 2018 10:17:57 +0000
- To: public-dxwg-wg@w3.org
@andrea-perego I am not sure it is doable to look for ways that different communities are handling versions. There are a lot of communities that could be considered. In the end, I agree with what @dr-shorthair wrote back in October 2017 (https://lists.w3.org/Archives/Public/public-dxwg-wg/2017Oct/0017.html): "_the notion of 'version' is usually a publisher's choice to assign a memorable identifier to a product_". So it may depend on the type of product, the intentions of the publisher and the expectations of the consumer. There might not be much consensus even within a particular community. In my mind, a fundamental characteristic of a version is that it is a resource that results from a change that was applied to or occurred in a pre-existing resource. In my mind, such a definition would point to the need, as a minimum, to be able to provide: - a reference to the resource of which it is a version - a name, number or time (e.g. 'MkII', '3.0.1 build 1902', '2018' etc.) - a description of what the changes were (e.g a change log) I think that we may not be able to go much further than that without digging into the particular aspects of specific products and communities. This could take a lot of time for little gain. -- GitHub Notification of comment by makxdekkers Please view or discuss this issue at https://github.com/w3c/dxwg/issues/90#issuecomment-373909384 using your GitHub account
Received on Saturday, 17 March 2018 10:18:00 UTC