> Rather than permitted=*, why not use parking_use=*? That would then be > consistent with your proposed relation. Though "permitted" is more > general and might be able to be generalised to other features...
Or perhaps something like "permitted_parkers"; I don't think there's anything wrong with a somewhat specific tag like that. It'll prevent ambiguity in the future such as what we're trying to resolve here with the "access" one. :) > I suggested a similar solution a couple of days ago: > "Alternatively, for parking, use the key "use" (as a noun) instead of > [or in addition to] access, as in use=public/customer/private." > There are then a few options for defining the values of parking_use, > e.g. my public/customer/private or your patron/staff/permit_holder, or > some combination thereof... Ooops, yes, you did. Great idea! :) So many emails, so little time. Agreed; similar words to mean similar things. I opted for patron rather than customer so that it was a little more generic; it sounds a little funny to say patient parking for a doctor is "customer parking". :) Patron is a little more generic I think. Tyler _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
