Long time JOSM user here. While following this thread my idea would also have been to write conversion scripts to get from one format to another, and indeed coming up with a common denominator from which the different formats can be distilled would seem like the next logical step in that train of thought.
I do understand that it's not nice to expect translators to duplicate their efforts. We're all volunteers and our time is priceless, just like the time of the developers and the mappers. We should be able to find a system that effectively reduces the effort to create, maintain and translate presets for all the editors that are out there. This will also enhance consistency. The same should be true for validator rules, when these other editors will support them at some point. Now I also understand Dirk's point of view. Why couldn't the developers of iD have opted to use JOSM's format to begin with? Why did they choose to reinvent the wheel? Was the format that bad/unsuitable when development on iD started? Polyglot 2015-06-23 9:03 GMT+02:00 Dirk Stöcker <[email protected]>: > On Mon, 22 Jun 2015, Ian Dees wrote: > > I created a repo to keep track of this here: >> https://github.com/osmlab/editor-presets >> >> I understand Dirk and the JOSM team's position, so let's stop clogging up >> their inboxes and take further discussion to tickets on this repo? >> >> To get started, I like your suggestion, Daniel; let's start with the core, >> make it transformable to the existing editor preset styles, and then >> expand >> where needed. I'm indexing the existing formats here: >> https://github.com/osmlab/editor-presets/issues/1 >> > > Which will actually lead to what? Another place where the information is > duplicated. Seems you again ignore the "dropping what we have in favor of > something else is extremely unlikely". And now again you suggest exactly > that again. > > Instead of any tries to improve situation or working together you come > again with the suggestion to start something new from scratch and then > later probably ask us to drop our solution. And you already know the answer > from last time. > > And BTW with the MIT license you are now allowed to use any of the stuff > JOSM already has, so you really need to start from scratch. > > Ciao > -- > http://www.dstoecker.eu/ (PGP key available) > > _______________________________________________ > josm-dev mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/josm-dev > _______________________________________________ josm-dev mailing list [email protected] https://lists.openstreetmap.org/listinfo/josm-dev
