Equal support for website / contact:website and phone / contact:phone

[riQQ]

Both variants, with and without prefix, should be supported equally as both have the status de facto and no consensus is in sight.

My proposal is to have a single field backed by both keys:

keys used	proposed behavior
neither specified	empty field that writes the new value to the website key
either specified	updating the value uses the existing key
both specified, different values	shows multiple values watermark
both specified, same value	updates both keys

At the moment, the fields Phone and Website are empty when the keys contact:phone and contact:website are used. Users that are not aware of the Tags section might fill in a new and different value leading to conflicting data.

Some related discussions:

• When a 'contact:*' is already present, ask for key uniformity like 'phone' → 'contact:phone' ecc. and vice-versa iD#8770
• Switch to contact: iD#3915
• Remove non-prefixed versions of contact: scheme iD#7566
• Validate social media tags #121