> This is a desirable goal but don't forget there is another side to
> that - if i as an entrepreneur consider contributing to the OSM
> database it could be important for me that my contributions cannot be
> used by the competition against my interests. Share-alike might play a
> significant
Am Fr, 10.06.2016, 17:22 schrieb Simon Poole:
>
>> Would this make "my" data trigger share-alike?
> The specific term simply says that when there is no references between
> the datasets it is a Collective Database, or in other words that the
> trivial case when there is no interaction is OK too.
Am 10.06.2016 um 16:25 schrieb Tobias Wendorff:
> A question to "the non-OSM and OSM datasets do not reference each other":
>
> Let's say, I've added municipal road identification numbers to the OSM
> database (not in my extract, but the "real" database).
>
> I later want to join other
Am Do, 9.06.2016, 13:43 schrieb Simon Poole:
> http://wiki.openstreetmap.org/wiki/Collective_Database_Guideline
A question to "the non-OSM and OSM datasets do not reference each other":
Let's say, I've added municipal road identification numbers to the OSM
database (not in my extract, but the
On Thursday 09 June 2016, Simon Poole wrote:
> >
> > But we are happy with uses that invoke share-alike as well, aren't
> > we?
>
> Basically the issue is that the guidelines are essentially "safe
> harbour" statements, "we are ok if you do X", to provide a more
> secure and stable environment for
Am 09.06.2016 um 17:40 schrieb Christoph Hormann:
> On Thursday 09 June 2016, Simon Poole wrote:
>> I can understand the desire for a negative example, but:
>>
>> - this is documentation of use that we are happy with, not of the
>> opposite.
> But we are happy with uses that invoke share-alike as
Am 09.06.2016 um 17:36 schrieb Simon Poole:
>
> Am 09.06.2016 um 17:06 schrieb Robert Whittaker (OSM lists):
>> Also (and it may be deliberate) this guideline doesn't address the
>> question of what filtering / querying you can do with your collective
>> database. For instance, under the
On Thursday 09 June 2016, Simon Poole wrote:
> I can understand the desire for a negative example, but:
>
> - this is documentation of use that we are happy with, not of the
> opposite.
But we are happy with uses that invoke share-alike as well, aren't we?
> - as the preamble says there may be
Am 09.06.2016 um 17:06 schrieb Robert Whittaker (OSM lists):
>
> Also (and it may be deliberate) this guideline doesn't address the
> question of what filtering / querying you can do with your collective
> database. For instance, under the guideline I can take OSM restaurant
> data, and add
On 9 June 2016 at 13:08, Christoph Hormann wrote:
> On Thursday 09 June 2016, Simon Poole wrote:
>>
>> The LWG has just forwarded the text of
>> http://wiki.openstreetmap.org/wiki/Collective_Database_Guideline to
>> the OSMF board for approval and publishing as definite
I can understand the desire for a negative example, but:
- this is documentation of use that we are happy with, not of the opposite.
- as the preamble says there may be other ODbL compliant ways that to
not invoke share-alike to combine datasets outside of those detailed in
the guideline.
-
On Thursday 09 June 2016, Simon Poole wrote:
>
> The LWG has just forwarded the text of
> http://wiki.openstreetmap.org/wiki/Collective_Database_Guideline to
> the OSMF board for approval and publishing as definite guidance from
> the OSMF.
IIRC it was already noted by others that the lack of an
FYI
The LWG has just forwarded the text of
http://wiki.openstreetmap.org/wiki/Collective_Database_Guideline to the
OSMF board for approval and publishing as definite guidance from the OSMF.
Simon
signature.asc
Description: OpenPGP digital signature
13 matches
Mail list logo