On Tue, Aug 2, 2011 at 7:31 PM, Frederik Ramm <frede...@remote.org> wrote:
> And to Steve Bennett ("people need a solution now, not vapourware") -
> sometimes settling for a half-baked solution too early has the risk of
> entrenching half-bakedness and never getting around to implement a good
> solution.Right. With an ever evolving project like OSM we need to find creative ways to support existing usage, but not lock ourselves into a bad long term solution. One way to do this, using your "link server" idea would be to support a legacy ID query mode, eg "/legacyid/xyz" which points to whatever object had xyz on a given cutover date. At some future date, we renumber all the IDs, breaking everything, but all the services that point to those IDs could just point to the legacyid/ service instead. It's a break, but it's a trival one to fix. Meanwhile new services would be built around the persistent id service, requesting permanent handles as required. (You do have the problem defining what it is that you want to persistently link to: the way? the relation? the relation with the members that it had when you linked to it?) Just brainstorming... Steve _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
