> Just because one can use a regular expression to grep out a certain meaning doesn't mean it's a good thing to do and will always work We easily revert these edits in Russia. Quite often user who want to show their regex fu will fail so hard to guess actual properly of the real world.
We care about data we map. We document it instead of guessing by taginfo. We use real tags instead of regexes for users. We like our newbies. We don't want to insist to use f$#$g perl regexes simply to map things around them. I cannot stop you from using regex. But if I find your changsets erroneous I will revert them. > In fact, nobody forces us to only use yes and no as a value. Wrong. It not forces you anything. You can still tag currency:X=fixme. > The Healthcare 2.0 proposal uses partial, main, yes and no. This can easily applied to a lot of values where it makes sense and it gives the flexibility to distinguish between equal and distinguished importance . There way more tagging schemes than single Healthcare 2.0. Yes there differences, so what? > Using semicolon-lists for values was always considered a crutch until a better tagging-scheme comes along. You forgot to say "among English speaking users who fail to use JOSM search funtion or overpass or taginfo or wiki documentation". I don't care about them. > We all know that the only real solution would be a native data type for arrays in the database but as long as this isn't happening, we have to work around. And obviously you choose the worst way to do this. With complicating things with REGEX. 2015-01-21 11:42 GMT+03:00 Nadjita <tagg...@mark.reidel.info>: > On 21.01.2015 09:06, Никита wrote: > > > If you trying to parse name=school *with any regex *to map it as > > amenity=school* *you are wrong. OSM is not for you. > > If you trying to parse currency=bitcoin;coin for coin, then stop it > > right now. You have no idea how regexes or tags in osm work. > > While I think, you should really calm down a bit and not sound so > aggressive, I have to agree with you. The purpose of structuring data is > not having to use a complicated, but a simple parser. Just because one > can use a regular expression to grep out a certain meaning doesn't mean > it's a good thing to do and will always work. > The only downside of currency:X=yes, currency:Y=yes to currency=X;Y is > that it involves more typing. In fact, nobody forces us to only use yes > and no as a value. The Healthcare 2.0 proposal uses partial, main, yes > and no. This can easily applied to a lot of values where it makes sense > and it gives the flexibility to distinguish between equal and > distinguished importance . > Using semicolon-lists for values was always considered a crutch until a > better tagging-scheme comes along. > We all know that the only real solution would be a native data type for > arrays in the database but as long as this isn't happening, we have to > work around. > But please let's not drag this down to a personal level and start > insulting each other, this isn't going to accomplish anything but anger. > > - Nadjita > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
