> Using a xxx:yyy schema also requires checkboxes besides every existing value in JOSM presets. So I don't see how it is any easier for new mappers or preset creators. Problem in multiple values in value part in *key=value.*
How iD should parse cuisine=mexican;japanese? This work repeated every time by wiki editors, by iD developers, by JOSM preset developers. There no point for this. Just ban semicolon and write actual page about *whatever*:mexican=yes *whatever*:japanese=yes *We don't have native arrays right now*. We have to decide which part of key=value will be ugly for some time so we can re-tag them back using real arrays. xxx:yyy=yes / semantic subtags are ugly, this is terrible for absolutely new to OSM people the same way key=value tags are terrible, but - we can provide newbies them with link to wiki. - we don't need to teach every person how to parse "japanese" from cuisine=mexican;japanese using f#$% regexes - we can provide clear definition at wiki page for iD or JOSM developers with description of tag instead of guessing by taginfo stats EVERY time they want to adjust something in presets - custom strings in editors or JOSM presets are easier to add - we get benefits from taginfo stats by using xxx:yyy=yes - advanced set querying for users, - reduced cpu load for database because there no need to compute *smart regexes*
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
