Hi,
please check the wiki about how to map charging stations.
None of these tags is correct:

charge-capacity
charging_capacity
charge_capacity
num_stations
num-station
num-stations
num_sations

amenity=charging_station#Examples

That's not access=permissive - that means that someone tolerates people accessing the way without asking, but has can revoke this right at any time.

access=private would be appropriate - someone decides on a case-by-case basis who is allowed to enter.

Hi,
please check this way, it didn't get any proper tags:
way/1378582103

See e.g.
https://community.openstreetmap.org/t/opinions-on-internet-access-password/117581

The pure existence of such a code implies that the door is not meant to be used by everyone. If they distribute the code to all their customers, that is their decision, but making the information public to everyone in the world is likely not their intention.

Just take this example:
node/12741716368

The next town is ten kilometers away and Bundibugyo district is even further away.

I checked 5 more nodes - non of them is even remotely close to the place the addr:* tags claim it to be. Not even in the same district.

This import definitely has to be reverted.

What about all the other non-standard tags?

floors
materials
resources
sections
services

There are also libraries in the middle of a lake or on top of an uninhabited mountain.

No matter what the source of this data is, the large scale of the edit makes it an import that needs to be properly documented.

Hi,
you used this tag on two stone:
"inscription:direction_east"
I think this should either be
inscription:E or direction_east, but not a combination of both. It's highly unlikely that any tool will be able to interpret this tag.

Hi,
you added some strange tags like "OBTC = UAIBIT". Could you explain what they are supposed to mean?

Fine with me - but the 'danger' key was added somewhere else:
changeset/163883089

Hi,
it seems something went wrong with this import of libraries.
First of all, we're missing the mandatory source and description of the import, see
osm.wiki/Import/Guidelines

Second, there are many tags that are not used in any other place and should be replaced by proper ones.

For now I suggest to revert this import, so that it can be redone with proper tagging and attribution.

Hi,
could you check this building? It got a strange 'shutter' tag.
way/85994237#map=19/43.786039/5.762005

Hi,
the language code 'uum' doesn't seem to exist. Could you check that?

If there's nothing on ground, I don't understand what the tags mean.

way/1371007612
May I suggest to tag this way with :lanes?
Neither bicycle:both nor bicycle:centre are currently in use.

Hi,
that wasn't my edit. The tags were added in changeset/160007751

Well, even if the underscore is not the formally correct symbol, the direction_* scheme is by now very well established, with way more than 100,000 uses. Introducing your own tagging scheme now (actually a fifth way for destination signs!) won't have any good chance to be adopted at any larger scale and will render the data more or less useless.

Hi,
this highway got a 'direction' tag which most likely should be on a guidepost node:
way/1375345149

Hi,
could you check your 'direction:*' tags? These are not in use up to now.

The typical spelling is
'direction_northeast' with an underscore and the full name of one of the 8 cardinal directions.