<div dir="ltr">On Thu, Aug 22, 2013 at 9:01 AM, OpenStreetmap HADW <span dir="ltr"><<a href="mailto:osmhadw@gmail.com" target="_blank">osmhadw@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On 22 August 2013 08:43, Oliver Jowett <<a href="mailto:oliver.jowett@gmail.com">oliver.jowett@gmail.com</a>> wrote:<br>
<br>
>> - no delimiter (+442079460676)<br>
>> - misplaced delimiter (+44 207 946 0676)<br>
><br>
><br>
> Aren't these unambiguous already?<br>
><br>
<br>
</div>They breach the existing guidelines, which call for the (UK usage)<br>
area code to be delimited. In particular, in London, you can dial<br>
this number as 00442079460676, 02079460676 or 79460676. On the other<br>
hand, dialing it as 9460676 will fail. (Always assuming it weren't a<br>
bogus number for drama use.)<br>
<br>
In any case, about 90% of people who used international format seemed<br>
to agree that +44 20 7946 0676 was the right grouping, even if some of<br>
them added the (0).<br></blockquote><div><br></div><div>My point is that in this case, it's unambiguous what the fully-qualified number means, regardless of where the spaces fall, so the edit is not actually adding anything other than a particular display format. Isn't that a policy to impose in the frontend that presents the data, not in the data itself?</div>
<div><br></div><div>In the case of numbers such as 79460676, they suffer from ambiguity as you need to know some extra information (country code, area code, etc) to be able to produce a globally-unique number - so fixing those is a good plan.</div>
<div><br></div><div>Oliver</div><div><br></div></div></div></div>