[OSM-dev] way 7062297, is this new?

Hugh Barnes list.osm at hughbris.com
Thu Oct 9 13:07:34 BST 2008


On Thursday 09 October 2008 18:56:42 Andy Robinson (blackadder-lists) wrote:
> Duplicate keys were perfectly valid
> then and indeed I recall we discussed how we might use duplication for
> tagging purposes. It was only the lack of support in the editors that
> stopped duplication in its tracks.

OK, so sounds like the editors didn't share the vision here. What were some of 
the use cases you came up with? Do they still apply?

>
> Times change and the format of the database tables has changed and a more
> sophisticated method of storage for tags has come about. 

That's under-the-hood stuff. What does it have to do with requirements for the 
data?

> While duplication 
> is still valid under API 0.5 its really a legacy functionality that's not
> being used for any useful purpose and hence why its any easy decision to
> drop duplication support going forwards. 

Why is it legacy functionality? Because it's not being used? It doesn't make 
sense unless perhaps you explain more.

It's not being used because the editors don't support it.

I agree it's an easy decison to drop it, but that does that make it the right 
decision?

I had a *lot* of trouble with that para.

> Till that time I suggest you use 
> one of the workarounds suggested for your own work.
>

Happy to do so, but would like more explaining, because they're not ideal and 
won't help to encourage take-up in API clients.

(The next response is much nicer.)

Cheers




More information about the dev mailing list