I am not saying it is easy. But if you keep most imports as thier own layers and only merge when trusted, look at how git manages many branches, you pull only from trusted branches. In my module TIGER would be its own layer that would not be merged at all, it would be kept separate. You would want tools to compare layers and mark and remove matching items, but I dont see why we need one monolithic system. A hostile layer would just be kept separate and then deleted. Users would be able to pull together layers and create views as needed.
mike On Sun, Jun 12, 2011 at 11:51 AM, Nic Roets <nro...@gmail.com> wrote: > On Sun, Jun 12, 2011 at 11:42 AM, Mike Dupont > <jamesmikedup...@googlemail.com> wrote: > > The code is the law, > > http://www.lessig.org/content/standard/0,1902,4165,00.html and we need > to > > change the code so that these discussions about licensing and all that > are > > less important. > > If it was easy, someone would have done it already. > > Think of how much trouble we already have with once-off imports > (Canvec, TIGER, etc). What will happen if the upstream source is > dynamic or hostile ? > -- James Michael DuPont Member of Free Libre Open Source Software Kosova and Albania flossk.org flossal.org
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
