Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-30 Thread Simon Poole
Am 30.11.2022 um 18:50 schrieb Minh Nguyen: .. The contributor terms in question state: This Agreement shall be governed by English law without regard to principles of conflict of law. [1] https://wiki.osmfoundation.org/wiki/Special:PermanentLink/9165#Miscellaneous My understanding of what

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-30 Thread Minh Nguyen
Vào lúc 06:49 2022-11-29, Simon Poole đã viết: Am 29.11.2022 um 15:30 schrieb Greg Troxel:    It seems obvious that asking a US entity to enter into a contract under foreign law (and the same is almost certainly true for any government entity in any other jurisdiction) is just not going to

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-30 Thread Tobias Knerr
On 29.11.22 16:38 Dave F wrote: If it's a licence change by OSM then how can a maintainer of a database possibly account for a future, unspecified change who's implementation was out of their control? Yes, it's about a license change by OSM. I don't think it's outlandish to assume that at

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-30 Thread Tobias Knerr
On 29.11.22 08:14 Simon Poole wrote: The main question is what "expect it to survive a hypothetical license change" implies. My expectation is that because of practical considerations any future licence would require downstream attribution of OSM so that the OSMF can continue to offer third

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread John Whelan
It was merely in response to Greg Troxel's comment. "In the case of your transit system, what were the key problems, and how were they overcome? I suspect that history is very useful for others." Cheerio John Dave F wrote on 11/29/2022 3:13 PM: Sorry, but I'm unclear what that detailed

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread Dave F via talk
Sorry, but I'm unclear what that detailed story has to do with my point? DaveF On 29/11/2022 16:54, John Whelan wrote: The story of the Ottawa bus stops... ___ talk mailing list talk@openstreetmap.org

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread John Whelan
The story of the Ottawa bus stops started when the City decided to announce the bus stops in an automated way to assist blind people. To do this they went round every bus stop with very accurate GPS equipment so the bus stops were measured to within a meter or so accuracy. One or two weren’t

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread Dave F via talk
On 28/11/2022 23:48, Tobias Knerr wrote: we would like to offer data donors a standard legal text that they can use to make their data available to OSM in such a way that we would expect it to survive a hypothetical license change. I'm confused. If a maintainer of a database wishes to change

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread Tobias Knerr
On 29.11.22 03:57 Minh Nguyen wrote: Could you clarify the "perhaps" here? If something has been explicitly dedicated to the public domain via CC0, a similar statement, or a relevant law, should it not survive any relicensing attempt? Or is this just about the editorial decision of whether to

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread Simon Poole
Am 29.11.2022 um 15:30 schrieb Greg Troxel: ... Also, what we need is a copyright license, so that's not necessarily -- and hopefully isn't -- a contract. Well there is this kind of underlying assumption that for most material in question, with the exception of actual maps, there is no

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread Greg Troxel
john whelan writes: > I have concerns about the amount of effort we seem to be asking open data > set creators to make. I think it took me seven years to get the licensing > correct to be able to import the local bus stops and very early in the > process the head of the transit system said

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-29 Thread Greg Troxel
Simon Poole writes: >> Could you clarify the "perhaps" here? If something has been >> explicitly dedicated to the public domain via CC0, a similar >> statement, or a relevant law, should it not survive any relicensing >> attempt? Or is this just about the editorial decision of whether to >>

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread Simon Poole
Hi Tobias That sounds better. The main question is what "expect it to survive a hypothetical license change" implies. My expectation is that because of practical considerations any future licence would require downstream attribution of OSM so that the OSMF can continue to offer third party

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread Simon Poole
Am 29.11.2022 um 03:57 schrieb Minh Nguyen: Vào lúc 15:48 2022-11-28, Tobias Knerr đã viết: On 28.11.22 at Simon Poole wrote: What is "OSM Contributor Terms compatibility" supposed to be? Ok, this is clearly imprecise wording.¹ The context is that we would like to offer data donors a

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread john whelan
I have concerns about the amount of effort we seem to be asking open data set creators to make. I think it took me seven years to get the licensing correct to be able to import the local bus stops and very early in the process the head of the transit system said 'but we want you to use our data.'

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread Minh Nguyen
Vào lúc 15:48 2022-11-28, Tobias Knerr đã viết: On 28.11.22 at Simon Poole wrote: What is "OSM Contributor Terms compatibility" supposed to be? Ok, this is clearly imprecise wording.¹ The context is that we would like to offer data donors a standard legal text that they can use to make

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread Tobias Knerr
On 28.11.22 at Simon Poole wrote: What is "OSM Contributor Terms compatibility" supposed to be? Ok, this is clearly imprecise wording.¹ The context is that we would like to offer data donors a standard legal text that they can use to make their data available to OSM in such a way that we

Re: [OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread Simon Poole
Am 28.11.2022 um 20:11 schrieb Amanda McCann: Hello fellow OSMers. As you are no doubt aware, OSM requires that data imports be listed on the OSM Wiki ( https://wiki.openstreetmap.org/wiki/Import/Catalogue ), including if the source is “ODbL OK status”. At the Nov. 2022 OSMF Board meeting

[OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

2022-11-28 Thread Amanda McCann
Hello fellow OSMers. As you are no doubt aware, OSM requires that data imports be listed on the OSM Wiki ( https://wiki.openstreetmap.org/wiki/Import/Catalogue ), including if the source is “ODbL OK status”. At the Nov. 2022 OSMF Board meeting (25 Nov), the Board voted that imports should,