[Tagging] reduction of the number of different keys talking about booking.com

[Marc_marc]

Hello,

last year, we discussed migrating tags
booking=yes|required|no|recommended|only to the reservation=* key.
After doing the mass editing procedure last year and the modifications
yesterday [1], then manually processed some objects,
I propose to discuss the next step :
to add a booking.com url/id, contributors are using many keys :

there are 2 groups of keys :

- specific keys for booking.com
contact:booking.com
contact:bookingcom
url:booking_com

- generic keys to this kind of service
website (fine if the POI doesn't have another site)
booking
website:booking which has the advantage of being documented in an
unambiguous meaning but which will not manage where a poi is affiliated
to more than one booking site)
website:direct_booking
contact:booking
url:booking

I do *NOT* want to stimulate contributors to add information about
booking.com, but they *do*, so I think it's better to reduce the number
of keys having the same meaning and thus having only one key.

what's your feeling about that ?
which keys do you find the least valuable to keep and why ?

and there is also 55x webbsite~booking.com/$ (the url end with /),
it says that the poi is available on booking.com but it seems to me
wrong to do it this way, it's not the url of this poi here.

Regards,
Marc