<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div class="ApplePlainTextBody">I saw border_type=hamlet;CDP in Kevin’s LAST CALL post and found it a bit odd, too. (The mechanical edit as a whole seems otherwise very sensible).<br><br>Minh’s suggestion is excellent: one extra relation that shares existing members ways (but with different relation tags) is something both I (and software, implies Minh, and I think he is correct) find preferable after a bit of chin stroking. Yes, there may be some times when heavily-loading (over-loading?) the value side of a tag with a semicolon-containing multiple values is exactly the syntax to use. But in this case, especially as the option to “spread across two” can be done with relations, I stroked my chin, thought about it and agree with Minh that his is a good solution.<br><br>We do this (duplicate relations with slightly different tags but exactly the same or very similar member ways that already exist in another relation) in a variety of other solutions in OSM, like for road and bicycle routes, to denote a scenic highway that is the same as a “just plain” highway (relation), and more. It is elegant, readily understandable by humans, doesn’t require that softwares parse semicolon values (some can, likely more can’t), and seems pretty “data compact” (doesn’t take up a lot of storage space in OSM’s database: simply another relation — efficient — albeit with different tags, and existing member ways (which are already stored for another relation). Lots of “wins” there.<br></div></body></html>