[OSM-talk] Who interprets semicolon in tag values?

[Colin Smale]

amenity=hotel;pub makes perfect sense to me as well. One of OSM's basic
rules is "one real-world object maps to one OSM object". There are
plenty of pubs which are also hotels, and hotels which also have/are
pubs. 

OSMs data model should be flexible enough to evolve. Currently
"multivalued tags" are not addressed within the data model so various
communities are inventing their own solution. I firmly believe that the
maintenance of the data model (I don't mean the tagging model here!)
should be managed centrally. Changes would be well thought out,
discussed with data/information architects, communicated in a timely
fashion to stakeholders (both on the mapping side and on the data
consumer side) and supported by updates to tooling. 

But I realise I am pretty much alone in this, and that my dream of some
way of maintaining some kind of structure and order in the data is not
going to happen. 

Colin 

On 2013-09-26 13:12, NopMap wrote: 

> Hi!
> 
> Philip Barnes wrote
> 
>> However amenity=pub;hotel makes perfect sense.
> 
> Only in a very academical way.
> 
> It would force an additional processing step onto every data consumer and as
> you can read in Jochens result, in practice it is not evaluated at all. It's
> just using randomly invented tags which nobody recognizes.
> 
> bye, Nop
> 
> --
> View this message in context: http://gis.19327.n5.nabble.com/Who-interprets-semicolon-in-tag-values-tp5763540p5779047.html [1]
> Sent from the General Discussion mailing list archive at Nabble.com.
> 
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk [2]



Links:
------
[1]
http://gis.19327.n5.nabble.com/Who-interprets-semicolon-in-tag-values-tp5763540p5779047.html
[2] https://lists.openstreetmap.org/listinfo/talk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20130926/941c8d68/attachment.html>