Hi Robert, To preface, I'm not a lawyer and your should seek your own independent legal advice, but as I understand:
1. the department has made a decision to adopt OSM as your data source, accepting the terms this data is licensed under 2. you will adapt, modify, enhance, correct or extend OSM data with your gazetted place and road names, which likely creates a Derivative Database under the ODbL, we'll call this DTP Validated OSM 3. where you make this DTP Validated OSM data available to others, like your distribution partners or the public via your open data portal, it must continue to be licensed under the ODbL. 4. The implication for your distribution partners would likely be if they want to further adapt, enhance, correct or extend your DTP Validated OSM data, and they then use that adapted data publicly, they must continue to license their adaptations under the ODbL, ie. the license is viral. 5. There is nothing here preventing these distribution partners using your DTP Validated OSM data, or making further changes or adaptations to it. If they don't accept the terms then they don't need to use your data. One alternative, if you create your data independently of OSM may be to publish it with only references to OSM, e.g. to OSM object IDs or with location references eg. OpenLR. If created independently you may be able to license as you wish. You could in parallel still publish a full osm derived version of the data under ODbL for convenience for those who accept the ODbL terms. On Mon, 3 Jul 2023 at 10:13, Robert C Potter (DTP) via talk < talk@openstreetmap.org> wrote: > Hi OSM, > > Representing the state transport authority (Department of Transport and > Planning) we have made the strategic decision to use OSM as our > foundational mapping data source. We are confident that this is a decision > will be of value to both ourselves improving the management of the networks > (road, Train, Bus, tram) and adding significantly to the citizens of the > state. > > Our intended use of OSM is built on an extract being done then validating > that extract for the gazetted/official place and road names. The resultant > validated dataset will be shared that via our Opendata portal. Our state > government has a strong commitment to sharing all data openly. We are > currently developing that process and should be in production by the end of > the year. > > Alas, there has been concern from our distribution partners with the ODbl > license requirement to "Share alike". You know these companies; Google, > Here, Tomtom and Apple. > > The information we would share, and all shared as ODbl; > > - Disruptions > - Heavy vehicles > - Bicycles routes > - Public transport routes and timetables > > I am wondering how we, can continue engage with these partners and use and > improve OSM. > > > > If you have any further queries, please do not hesitate to contact me. > > > > Regards, > > > > Robert Potter > > *Helping people use the power of location to make better decisions* > > Manager, Spatial Data Strategy > Department of Transport and Planning > > 1 Spring Street > > MELBOURNE 3000 > > > *M *0402 484 739 > > *F* 03 9935 4111 > *E *robert.pot...@roads.vic.gov.au > *W dtp.vic.gov.au <http://dtp.vic.gov.au>* > > > I acknowledge the Traditional Aboriginal Owners of Country throughout > Victoria and pay my respect to Elders past and present and emerging and to > the ongoing living culture of Aboriginal people. > > DISCLAIMER > > The following conditions apply to this communication and any attachments: > VicRoads reserves all of its copyright; the information is intended for the > addressees only and may be confidential and/or privileged - it must not be > passed on by any other recipients; any expressed opinions are those of the > sender and not necessarily VicRoads; VicRoads accepts no liability for any > consequences arising from the recipient's use of this means of > communication and/or the information contained in and/or attached to this > communication. If this communication has been received in error, please > contact the person who sent this communication and delete all copies. > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
