- From: <andrea.perego@ec.europa.eu>
- Date: Fri, 8 Feb 2019 14:07:45 +0000
- To: <mail@makxdekkers.com>, <david.browning@refinitiv.com>, <public-dxwg-wg@w3.org>
I totally agree with Makx. Andrea ---- Andrea Perego, Ph.D. Scientific / Technical Project Officer European Commission DG JRC Directorate B - Growth and Innovation Unit B6 - Digital Economy Via E. Fermi, 2749 - TP 262 21027 Ispra VA, Italy https://ec.europa.eu/jrc/ ---- The views expressed are purely those of the writer and may not in any circumstances be regarded as stating an official position of the European Commission. >-----Original Message----- >From: Makx Dekkers [mailto:mail@makxdekkers.com] >Sent: Friday, February 08, 2019 10:46 AM >To: david.browning@refinitiv.com; public-dxwg-wg@w3.org >Subject: RE: DCAT Sprint 2 - Wednesday 13th February 21:00 UTC - feature: >versioning > >On the issue of versioning, I dug up an earlier message to the group >(https://lists.w3.org/Archives/Public/public-dxwg-wg/2017Jun/0006.html) >where I listed a number of versioning scenarios that I have come across: > >* Evolution: for example, a dataset that is published with >year-to-date information; every week or month, new, recent data is >appended >to the existing data. >* Replacement: for example, existing data was wrong in some way, >and a >new dataset is published that replaces the old data. >* Snapshots: for example, continuously changing data like the state of >traffic or weather maps with hourly snapshots. >* Time series: for example, annual budget data. >* Conversion: for example, data that is transformed from one >coordinate system to another, or from one set of units to another; similar >to translation of textual resources. >* Lower/higher granularity: for example, maps in different scales, >images in different resolutions, compression like MP3 versus CD sound, and >summaries of large amounts of data. > >In my mind, we should not discuss why or when to call one dataset a version >of another -- the owner/curator of the dataset will need to decide that >based on local or community rules, and it is really hard to give advice on >that -- but only how to describe the relationships between datasets for >various scenarios. > >Maybe helpful as a starting point for the discussion? > >Makx. > > > > > > >-----Original Message----- >From: david.browning@refinitiv.com <david.browning@refinitiv.com> >Sent: 07 February 2019 18:09 >To: public-dxwg-wg@w3.org >Subject: DCAT Sprint 2 - Wednesday 13th February 21:00 UTC - feature: >versioning > >The second DCAT sprint will take place next Wednesday 13th February 2100 >UTC >till 23:00 UTC. It will replace the normal, regular DCAT subgroup meeting. >This will be a working meeting looking at the outstanding issues (and any >associated concerns raised in external or internal feedback) and will aim to >pull together appropriate conclusions and text to be contributed to the >working draft. The working method will follow the approach for Sprint 1 >(plus any good ideas that people want to bring). > >The webex details for the meeting have already been sent out to the WG >mail >(http://lists.w3.org/Archives/Public/public-dxwg-wg/2019Feb/0167.html ). > >The agenda, containing useful links to previous discussions and other >material as well as the connection details can be found at >https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2019.02.13 If >there >is information that people believe is germane to the discussion then please >feel free to add to the agenda or by commenting on the issues. > > > >David Browning > >________________________________ > >This e-mail is for the sole use of the intended recipient and contains >information that may be privileged and/or confidential. If you are not an >intended recipient, please notify the sender by return e-mail and delete >this e-mail and any attachments. Certain required legal entity disclosures >can be accessed on our website.<https://www.refinitiv.com/> >
Received on Friday, 8 February 2019 14:08:11 UTC