A Validator Warning should be produced when Parking Access Tag Keys not correct

[anonymous]

What steps will reproduce the problem?

1. Create a polygon
2. Add amenity=parking access=destination
3. Observe no error

What is the expected result?

Parking access keys should be limited to {yes,permissive,private,customers}. Validator should produce warning

What happens instead?

Incorrect keys are accepted

Please provide any additional information below. Attach a screenshot if possible.

​http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dparking#Tags

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-08-11 21:54:24 +0200 (Thu, 11 Aug 2016)
Build-Date:2016-08-11 22:36:05
Revision:10786
Relative:URL: ^/trunk

Identification: JOSM/1.5 (10786 en) Linux Ubuntu 16.04.1 LTS
Memory Usage: 462 MB / 871 MB (177 MB allocated, but free)
Java version: 1.8.0_91-8u91-b14-3ubuntu1~16.04.1-b14, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-8-jre:amd64-8u91-b14-3ubuntu1~16.04.1
Dataset consistency test: No problems found

Plugins:
+ ColumbusCSV (32796)
+ DirectUpload (32699)
+ buildings_tools (32796)
+ colorscheme (32699)

[Klumbumbus]

The exact definition of access=destinantion depends on the laws of the country. So I think that access=destinantion on a parking lot can be valid in some circumstances (more opinions?).

The most used access values for amenity=parking according to ​taginfo are:

• private -> OK
• customers -> OK
• yes -> OK
• permissive -> OK
• destination -> could be OK in my eyes
• public -> duplicate of yes in my eyes
• unknown -> already has a warning
• no -> OK
• designated -> already has a warning