Charlie Echo wrote: > The proposal you mention is a radical change in the way we would tag. We > would move from tag=value to tag:subtag:subtag=value.
It's really not different in any significant way from the psv_directions proposal. The only differences: psv_directions uses an underscore instead of a colon to separate the tag from the subtag. (trivial/superficial difference) The access namespace proposal explicitly says that the vehicle type can be replaced. I'm sure we'd end up with bicycle_directions, hgv_directions, etc. so we might as well say it up front. And then we might as well have all the other "access restrictions" (psv_maxweight, etc.). And we might as well bundle them together so it's a little more obvious that they all have the same meaning (I might not know offhand what "psv_directions=no" is, since psv is not a common term around here. Same for hgv_directions) And once you get there, you're at the access namespace proposal. > In your example, access:psv:oneway=no could also be access:oneway:psv=no or > even psv:access:oneway=no with the same spirit (I mean we can decide to put > access first, but the next subtags should be all defined and ordered, or we > would have to tolerate mis-order) They are defined and ordered in the relevant proposal. you might say the same about psv_directions: it could also be directions_psv. ;-) -Alex Mauer "hawke" -- Bad - You get pulled over for doing 90 in a school zone and you're drunk off your ass again at three in the afternoon. Worse - The cop is drunk too, and he's a mean drunk. FUCK! - A mean drunk that's actually a swarm of semi-sentient flesh-eating beetles. OpenPGP key id: 51192FF2 @ subkeys.pgp.net
signature.asc
Description: OpenPGP digital signature
_______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
