<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">This does NOT mark any of the prefixed social media, messengers, or web services keys as approved. This is a proposal that only deprecates social media, messengers, web services keys that are not prefixed under the contact:*=* namespace.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Removes tag fragmentation by using the most used keys.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is an unnecessary existence of a parallel tagging scheme on only some of the social media contact methods.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Without diving too deep into the benefits of the contact prefix, which has been discussed very thoroughly on other pages, having all contact information under one namespace simplifies the usage while preventing any contact methods from
overlapping with any other tags for real world usage.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Simplifies the usage for data consumers who would otherwise have to support both at the same time. On the other side this also gives data consumers with all the necessary data they need if they are unaware of some of the several non-prefixed
versions that still exist.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://wiki.openstreetmap.org/wiki/Proposed_features/Social_media_contact_prefix">https://wiki.openstreetmap.org/wiki/Proposed_features/Social_media_contact_prefix</a></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please discuss this proposal on its Wiki Talk page.</p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>