> key[1]=value1 key[2]=value2 > and returning to the semicolon mode on the output again. That would probably help avoid too much regexping.
I see your point, but sadly this is not solution. I was always mentioning xxx:yyy scheme as *semantic subkeys*, there no semantic in: key[1] - what does 1 mean? nothing. There no wiki page about it. Even there page for it, how do you memorize them? In contrast to this, my suggestion work decently, but it may look too verbose at first: color:yellow=yes color:red=yes Back your example, how do you query for yellow? key[1]=*? key[2]=*? Okay you know the answer, this is your indexes. But how do you know that? At first it seems like good idea, but sadly not solution to the question, instead of regexes you have to deal with meaningless numeric indexes in keys. PS. We need arrays/native multivalued support for values in key=value tags anyway. There native arrays in PostgreSQL but I'm not sure if it will be good idea to adapt them, this will be only up to back-end developers, not about tagging.
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
