<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 19-Sep-17 03:56 AM, Kevin Kenny
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALREZe9N-sw1A_=zWeZrkvhk409AxD33EmrcXuNF01ja-jQ7Mw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Sep 18, 2017 at 12:37 PM,
joost schouppe <span dir="ltr"><<a target="_blank"
href="mailto:joost.schouppe@gmail.com"
moz-do-not-send="true">joost.schouppe@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>
<div class="gmail_extra">That said, even if this
hivemind of ours (and let me add to that "one of us,
one of us, one of us") maybe does not like an extra
value for the access key, I see no reason why you
would need to use another database. There are very
many things which are not mapped by just one key,
but by many keys combined. You just need a key to
classify WHY a thing has a certain access key. I see
someone already suggested
permit=registration_at_entry/r<wbr>egistration_offsite/online/lot<wbr>tery.
That could work as a subtag: access:permit=*,
foot:permit=*. You could then simply tag it as
*:permit=yes meaning "there is some permitting
process in place". That would save you the hassle of
defining all the many different permitting schemes.
It would of course best be extended with some
information about the difficulty of the process (on
arrival, in advance and simple, in advance and
complicated) and contact information. That would
also be quite useful to extend the limited model now
used on Low Emission Zones (see <a target="_blank"
href="http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dlow_emission_zone"
moz-do-not-send="true">http://wiki.openstreetmap<wbr>.org/wiki/Tag:boundary%3Dlow_<wbr>emission_zone</a>).
It would certainly be better then the
now-used access=green_sticker_<wbr>germany :)</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Similar things were counterproposed the last time I had
mentioned this.<br>
<br>
</div>
<div>The reason that I don't like it as much is that the
'permit=*' stuff then grew layer upon layer of qualifiers
in the discussion - the denizens of 'tagging' got bogged
down with trying to simplify the messy, human-centered
process of access control into a few keys, and got
nowhere.<br>
<br>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
<blockquote type="cite"
cite="mid:CALREZe9N-sw1A_=zWeZrkvhk409AxD33EmrcXuNF01ja-jQ7Mw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
The real-life sign says, "Access by permit only, for
information contact..." and that's what I propose to map!<br>
</div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<br>
Yep. <br>
I think the important thing is the contact information - this is
where the detail of what is required can be obtained rather than
having those details in OSM. <br>
It is the details that vary a lot from place to place and maybe too
varied around the world for renders to be bothered with. It might
just change from time to time, rather not have the dynamic stuff on
OSM? <br>
<br>
So access=permit with permit_contact:web/email/phone/*=* ??? <br>
Would that be a compromise 'we' can all use? <br>
<br>
<br>
<br>
<p><br>
</p>
</body>
</html>