[Imports] [OSM-talk] tag with value lists Was: Proposed mechanical edit to convert alt_name tags

[Andrew Buck]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If we want to convert them to single values with ; to separate that is
fine, but I cannot wait around for a discussion like that to finish.
I will have to keep working with them as is and then convert them
after the discussion settles down and finally reaches a decision.
This is fine with me, it is not hard to concatenate them at the end,
but that is the situation.  As soon as everyone is in agreement that
this is the way to proceed that is what I will do.

- -AndrewBuck


On 09/08/2014 06:33 PM, Jason Remillard wrote:
> Hi Andrew,
> 
> By my count, we have 25,000 instances of ";" in name, 5,600
> instances of ";" in alt_name, versus 2500 instances of alt_name_1,
> and 1000 instances of alt_name_2. A 30:1 difference in usage. Looks
> to me like the community has in fact decided the ;  is preferred
> over alt_name_1. I suggest you convert to the bad alt_name:1 tags
> into alt_name with ";" .
> 
> Tagging is on topic when discussing imports and mechanical edits.
> 
> Generally, consultations periods for mechanical edits should take
> at least week or two.
> 
> Jason
> 
> On Mon, Sep 8, 2014 at 6:52 PM, Andrew Buck
> <andrew.r.buck at gmail.com> wrote: On 09/08/2014 05:44 PM, Eugene
> Alvin Villar wrote:
>>>> On Tue, Sep 9, 2014 at 3:00 AM, Florian Lohoff <f at zz.de>
>>>> wrote:
>>>> 
>>>>> Isnt the semicolon the list seperator typically used in
>>>>> OSM? My intuitive answer would have been alt_name=a;b;c;d
>>>>> 
>>>> 
>>>> +1
>>>> 
>>>> I think using a semicolon-delimited list is better than a 
>>>> potentially open-ended set of keys such as "alt_name_x", and 
>>>> already has precedent. While it is true that semicolon as a 
>>>> multi-value separator is not written as a "law" of OSM
>>>> tagging, it is quite frequent enough to be a de facto tagging
>>>> guideline.
>>>> 
> 
> Both systems are in use and were in use before we started working
> on this GNS stuff.  The tiger tags are one example, but there were 
> alt_name_N tags before we started as well.  If you want to have a 
> discussion about changing all of these worldwide, that is fine,
> but this thread is about fixing the alt_name:2 ones.
> 
> Please either weigh in on that, or keep silent.  I do not have time
> to have a general discussion about broader topics of how
> multi-valued keys should be handled.  There have been dozens of
> threads that discussed that and no one has ever come up with a good
> solution, so I am not going to have this thread get dragged into
> the same discussion that has been had many times before.
> 
> There has been one person who has said it makes sense to change
> them, and all of the other posts have been about discussion of
> other topics. So unless someone has some concrete reason _not_ to
> convert the few mistaken ones, I will go ahead and do that.  We can
> have these other discussions some other time when people are not
> waiting on the results.
> 
> -AndrewBuck
>> 
>> _______________________________________________ talk mailing
>> list talk at openstreetmap.org 
>> https://lists.openstreetmap.org/listinfo/talk

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJUDkFiAAoJEK7RwIfxHSXbUBIP/R+8wEW3UbwECUmNnRXG9mhE
izzXMgMOEaXaRRuS550uYKmcCWiys9limOB196KVUaKQ2qwouqeS7w6tustfPit/
4X8QJpqzVJ6+d41CttkwyVpVvpFEnS+avf3DIIQfPJfxm/bfGWchfalUbwY/zlPb
mY4HtXwAl6NZua7IgdrxJNdQB4yzEenzyr9CzwaXcH78fS9iDaIG+d/7CEhi6yNh
hq1Fo5rfxbV0BsCaxYL5ZyCyMN8Mgh6x63A0OEWcuOJAtSBdmwDdTb57FYx7Ebk5
pcCggrOCEgPmbJHBTlTfLUrP8g+8uxefne/dMP6hWbRrjfik2rsMTkl08Ab4qu4y
URccKR642K+dieVtUpj9SUx3OaAFCi5HslRyuw118hIZkSQplAamBUHhJ7KllBkI
mVaTSCSPhQtWEW5QKIsgyNZpKWysoI5OBH3/eCz3wrhZCPTmFD1eV/Yxeg114LU4
/lpzUWyBEZ116ULhfj7X0RffNnqgx3yMA43wolq9KQVz00hahyQ6DYUaZgL6h5l3
cFCq1bMD56LdajB+LVY/IzDJaH6UPNJeZiwvjiOCEU18rg6YCxIiML/+xUQTs9o3
5E9VZj3XV4J54SILZPfHg8imNn3i9uHabGLIWPFRxVmNZvDhbCYu0GhhhiHBDc+J
PclH2MdMJxpbVheAnVG4
=epbI
-----END PGP SIGNATURE-----