Re: [OSM-legal-talk] OSM data on copy-protected storage

2013-04-12 Thread andrzej zaborowski
On 9 April 2013 21:43, Frederik Ramm frede...@remote.org wrote:
 The ODbL has a provision for parallel distribution in 4.7b:

 You may impose terms or technological measures on the Database ... in
 contravention of Section 4.74 a. only if You also make a copy of the
 Database or a Derivative Database available to the recipient of the
 Restricted Database ...

 So I guess they are fine; the recipient of the card (the Derivative
 Database) must have access to the data; it doesn't say how this access
 should work, i.e. the recipient has no right to an unencumbered database
 that is playable on his specific device.

 Or has he? 4.7b iii says that the unrestricted database must be

 at least as accessible to the recipient as a practical matter as the
 Restricted Database.

 - so if the recipient *only* has this special hardware device that can
 *only* play the encrypted cards, would a here's the pbf download link not
 be less accessible for him...?

Thanks for your observations.

I'll be checking with them if they can perhaps publish both raw OSM
data and a version with OSM data alone that the device can read. (I'm
not sure how that encryption works.  For example if each layer was a
separate file and the files were encrypted individually then it
shouldn't be hard to do)

However... the second piece you quote kind of makes it difficult to
make use of section 4.7b that you quote first.  Except in the cases
where anyone can produce that Restricted Database from the original
database and I imagine normally that's not the case. (?)

Cheers

___
legal-talk mailing list
legal-talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/legal-talk


[OSM-legal-talk] OSM data on copy-protected storage

2013-04-09 Thread andrzej zaborowski
Hi,

I'm relaying a license question from a company that collects lake
bathymetry data and sells specialised GPS devices to fishers and
sailors.  They don't make the software on those devices and have to
pay to get their data converted to the format understood by that
software.  They'd like to add layers of OpenStreetMap data to the
storage cards shipped with a new device, but they'd like to keep their
bathymetry and coastline data proprietary.  The cards are
copy-protected (encrypted, I believe).  Their question is whether
OpenStreetMap data can be distributed encrypted on those cards
together with their own data.  The company can publish, e.g. on their
website, whatever files are necessary but they can't publish the
conversion process or their own data unencrypted.

My understanding is that if their coastline data is not merged with
OSM coastline data (one or the other is shown), and if they publish
raw OSM data or information on how they extracted it, then they are
fine.  But I will appreciate any comment from someone who deals with
OSM licensing more.

Cheers

___
legal-talk mailing list
legal-talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/legal-talk


Re: [OSM-legal-talk] OSM data on copy-protected storage

2013-04-09 Thread LM_1
Even if keeping their data proprietary goes against the nature of OSM, yes
OSM data can be used as described - that is if the data is not mixed with
mentioned proprietary data. Copyright attribution is still required.

LM_1


2013/4/9 andrzej zaborowski balr...@gmail.com

 Hi,

 I'm relaying a license question from a company that collects lake
 bathymetry data and sells specialised GPS devices to fishers and
 sailors.  They don't make the software on those devices and have to
 pay to get their data converted to the format understood by that
 software.  They'd like to add layers of OpenStreetMap data to the
 storage cards shipped with a new device, but they'd like to keep their
 bathymetry and coastline data proprietary.  The cards are
 copy-protected (encrypted, I believe).  Their question is whether
 OpenStreetMap data can be distributed encrypted on those cards
 together with their own data.  The company can publish, e.g. on their
 website, whatever files are necessary but they can't publish the
 conversion process or their own data unencrypted.

 My understanding is that if their coastline data is not merged with
 OSM coastline data (one or the other is shown), and if they publish
 raw OSM data or information on how they extracted it, then they are
 fine.  But I will appreciate any comment from someone who deals with
 OSM licensing more.

 Cheers

 ___
 legal-talk mailing list
 legal-talk@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/legal-talk

___
legal-talk mailing list
legal-talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/legal-talk