<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hey,</p>
<p>for objects such as parking lots that cannot be used by the
general public (access=private), it can be helpful to specify the
"private" user group more precisely, e.g. residents or employees.
(This can also be of interest for paths/ways, barriers or other
objects.)</p>
<p>I can find several taggings for this in the database (none of
them documented, as far as I can see), in particular:</p>
<p>1: access=private + private=residents/employees<br>
2: access=private +
access:residents/access:employees=yes/designated/...<br>
3: access=private + residents/employees=yes/designated/...<br>
4: access=residents/employees.</p>
<p>Which tagging would you use/prefer? I like the approach using
"access:residents" etc., as it would offer the widest range of
tagging possibilities (e.g. a more precise distinction of access
for this or even several special user groups) and makes clear,
that this information is an access tag. A similar syntax seems to
be already in wide use in particular for disabled parking spaces
(access:disabled) resp. was once proposed for parking spaces and
it's various user groups. "access=residents" or "access=employees"
each have thousands of uses, but seem inappropriate to me because
they break with typical access conventions/classes.</p>
<p>Thanks,<br>
Alex<br>
</p>
</body>
</html>