On 04/08/2015 14:07, Michał Brzozowski wrote:
This means just not to add contact details of private persons like me or you.
OK, but it needs to be amended because that's not what it says
As per contact: prefix, opponents argue it's redundant. Isn't so addr:
as well? In reality keys with and without contact: are equivalent.
My argument for using it is that new popular services for
communication appear every year nowadays, and contact: prefix makes it
clear and easy to standardize. You can have contact:facebook,
contact:twitter, contact:instagram and so on.
I don't see how it standardizes when, as you point out, the popular
content for the key on the right ie facebook, twitter etc varies yearly.
If data manipulators want to process 'contacts' they still have to
perform the same parsing so there's no gain there.
For some tag developments i can see the benefits, but I'm struggling
with this one I'm afraid.
Cheers
Dave F.
Michał
On Tue, Aug 4, 2015 at 2:57 PM, Dave F. <dave...@madasafish.com> wrote:
Hi
wiki.openstreetmap.org/w/index.php?title=Key:contact
I remember a discussion a while back about this. As the page makes no
mention of the logic behind, could someone please remind me of the reasoning
& advantage over straight forward phone, fax, website etc.
"You should only add contact informations to POIs and not to any private
address!"
By 'POI' does he mean 'public company'?
Thanks
Dave F.
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
