Well, This demands completely changing of the OSM API. I only think if it is good idea to change the whole protocol just to make history more clear.
Maybe to make some intelligent analyse service, something like ITOWorld's OSM Mapper, but a bit different. This service collects diffs and "prepares" the history. And then it is possible to integrate it with editors through web-services. Regards, Igor 2009/3/20 Frederik Ramm <[email protected]> > Hi, > > sometimes it is difficult to see from the history of an object what > has happened. > > For example, you may look at the history of one way and it looks like > user X has deleted the way, but instead user X has merged the way with > another, existing way. (Similar for splitting ways.) > > Ideally of course, the API would support such complex operations (so you > could call an API function "split way" and it would be recorded in > history as such). But this is not going to happen any time soon. > > I wonder if we should make an effort to better record such things > through the existing history. For example, wehn merging two ways, > instead of just deleting one of them, should we perhaps first upload a > new version of it that has no nodes and just one tag ("note=merged with > way #1234"), and then immediately delete it afterwards? This would make > it so much clearer what happened to someone reading the history. Maybe > we could even formalise this somehow. > > I know it is not strictly a JOSM issue and ideally all editors would > support this, but you have to start somewhere. > > Bye > Frederik > > -- > Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" > > _______________________________________________ > josm-dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/josm-dev > _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
