t for the discussion.
On 2 January 2013 14:50, wrote:
> I have been told ( on the talk-US email list ) that use of {{key|source}} on
> objects has been deprecated for years and that such information is only of
> historical interest and its use should be restricted to changesets.
--
intact, in good quality for any emergent uses we're
not even thinking about yet.
I think it's a very, very good approach. Uses come and go, but the
data is what matters, in the end. It's the data itself, the modelling
of reality, we need to focus on.
--
- Ilari Kajaste -
E
On 13 July 2012 20:30, Martin Koppenhoefer wrote:
> 2012/7/13 Ilari Kajaste :
>> This isn't all that surprising. "drinkable" is an attribute,
>> "drinking_water" is a service. Different types of things are used in
>> different tagging cont
of deciding the better
term (e.g. "drinkable" vs. "potable").
I'm not saying it's not a good idea to suggest the use of only one tag
instead of two that are used to convey the same result ("ok there's
probably water for me there"), Bu
nd at least
internationally, it seems "drinkable" is considered more natural. And
since it's also a synonym in any normal use (so no specificity is
lost), that's the word that should be used for the tag.
--
- Ilari Kajaste -
E-Mail: ilari.kaja...@iki.fi
WWW: http://iki.fi/ilari.kajaste
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
even the right place for such detailed opening hours, but that's a
whole other discussion.
--
- Ilari Kajaste -
E-Mail: ilari.kaja...@iki.fi
WWW: http://iki.fi/ilari.kajaste
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
01) = closed
Though the given example is unusually complex, so it's not a good
example of a common case. And as a sidenote I'm not sure OSM database
is even the right place for such detailed opening hours, but that's a
whole other discussion.
nmapper-intuitive computer-understandable then I would
suggest these tags or values could always be prefixed with something
(eg. "special:", "code:", "computer:",
"extended:"). That way editors could know to only display them via a
special editor, instead of p
