<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 13px;" lang="x-unicode">
<br>
On 11/05/2020 10:29, Shawn K. Quinn wrote:
<br>
<blockquote type="cite" style="color: #000000;">On 5/10/20 7:36
PM, Cj Malone wrote:
<br>
<blockquote type="cite" style="color: #000000;">I think I stand
by that quote, but I'm happy to discus it. I'm not
<br>
arguing that over night we should stop people using the phone
tag.
<br>
Currently phone has at least 2 uses. A contact number and an
incoming
<br>
number for a phone box. We should split these out. If we are
left with
<br>
totally_new_tag_for_phoneboxes and phone, where
<br>
totally_new_tag_for_phoneboxes is defined as incoming phone
number and
<br>
phone is defined as the contact number. I'm OK with that too,
it's the
<br>
definitions that really matter.
<br>
</blockquote>
Why should we split these out?
<br>
<br>
In fact, I'm not sure how useful it is for us to tag phone
numbers on
<br>
phoneboxes at all. Does anyone actually use this data for
something useful?
<br>
</blockquote>
<br>
This is OSM, people can map anything that is verifiable.
<br>
<br>
I do map phone numbers of phoneboxes and can see various uses for
this data.
<br>
<br>
The number of the phonebox in the village where my grandmother
lived is still ingrained on my memory, we used to phone her at the
phonebox at the same time every Sunday, being able to find out the
number to call someone without visiting first is useful.
<br>
<br>
Taxi firms could find this useful to locate a customer who is
unsure of their location.
<br>
<br>
I used to let my parents know I was ready to be picked up by
letting the phone at home ring twice, I had to be at a specific
place for that to work. But being able to look up the location of
the phonebox would have meant I could be at any phonebox.
<br>
<br>
I am sure others will see other applications.
<br>
<br>
Phil (trigpoint)
<br>
<br>
<br>
</div>
</body>
</html>