Re: [OSM-dev] Working with OSM data with less or no metadata

2018-02-14 17:49 GMT+01:00 Simon Poole : > Generally I would prefer if we could simply have two versions of > everything, one with metadata for authenticated users/consumers one > without. > +1. This sounds like sane measures, the metadata is really an important part for the

Re: [OSM-dev] Working with OSM data with less or no metadata

The LWG won't be making any "decisions" we will be making recommendations to the board, which may or may not take action on them. Generally I would prefer if we could simply have two versions of everything, one with metadata for authenticated users/consumers one without. This likely will not be

Re: [OSM-dev] Working with OSM data with less or no metadata

Hi, - timestamps however cannot only potentially be used in lieu of changeset ids to group contributions, the information itself is problematic because it allows to profile contributions over time Timestamps are necessary to correctly figure out which nodes have belonged to a certain

Re: [OSM-dev] Working with OSM data with less or no metadata

General comments: - we are just considering removing metadata from what is publicly available outside of the OSM community, the current thinking is that it can remain available to authenticated users - while there might be a tiny bit of leakage from providing version numbers we haven't

Re: [OSM-dev] Working with OSM data with less or no metadata

On Wednesday 14 February 2018, Darafei "Komяpa" Praliaskouski wrote: > > > > While this seems a useful test to do i wonder how the timestamp and > > version fields are relevant regarding privacy and personal data > > protection? > > If OSM API were fast enough, it would allow to rather easily

Re: [OSM-dev] Working with OSM data with less or no metadata

ср, 14 февр. 2018 г. в 17:47, Christoph Hormann : > On Wednesday 14 February 2018, Michael Reichert wrote: > > > > All challenges are run four times, one iteration with full metadata, > > one with timestamp and version fields, one with version field only > > and one without any

Re: [OSM-dev] Working with OSM data with less or no metadata

On Wednesday 14 February 2018, Michael Reichert wrote: > > All challenges are run four times, one iteration with full metadata, > one with timestamp and version fields, one with version field only > and one without any metadata. [...] While this seems a useful test to do i wonder how the

Re: [OSM-dev] Working with OSM data with less or no metadata

Hi, On 14.02.2018 15:23, Martin Koppenhoefer wrote: > it seems Brexit could become effective March next year. Maybe we just wait? We would still have to apply EU regulations to processing the data of EU citizens. > I really hope we will not obfuscate or remove meta data because of some > EU

Re: [OSM-dev] Working with OSM data with less or no metadata

2018-02-14 10:30 GMT+01:00 Michael Reichert : > Hi, > > people are talking about potential changes to the amount of (personal) > data distributed by OSM, in the light of new data protection laws > becoming effective in the EU this May. it seems Brexit could

[OSM-dev] Working with OSM data with less or no metadata

Hi, people are talking about potential changes to the amount of (personal) data distributed by OSM, in the light of new data protection laws becoming effective in the EU this May. There haven't been any official statements by the OSMF but discussions are going on in the LWG [1]. Even though it