Not that I'm getting involved in this... but if there is to be a multiplicity of servers, why not have the server provide a REST call* that can be used by PL/JOSM (or anything else) to establish which tracing sources are permitted for that server and which aren't? That way, the tools don't need to cater for specific needs, they become more generall.
cheers b (writing as just an interested software engineer for once) * Just returning a static file of filters, or the like, to make implementation simple. On 31 January 2011 08:18, John Smith <[email protected]> wrote: > On 31 January 2011 10:04, Grant Slater <[email protected]> > wrote: > > Frederik is also a member of the Data Working Group, along with > > myself, who have to deal with the consequences of people recklessly > > tracing in from inappropriate sources. > > Although a little different, see a recent case here: > > > http://lists.openstreetmap.org/pipermail/talk-ec/2011-January/000055.html > > Which leads back to Anthony's suggestion about a special build for > OSM-F with what ever filtering they deem appropriate, they could go so > far as to host some kind of config that JOSM interacts with *IF* and > only if the data is being uploaded to OSM-F's API address. > > _______________________________________________ > Talk-au mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/talk-au > -- Ben Last Development Manager nearmap.com
_______________________________________________ Talk-au mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-au
