<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 19, 2021 at 3:34 PM Shawn K. Quinn <<a href="mailto:skquinn@rushpost.com">skquinn@rushpost.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 11/19/21 12:40, Paul Johnson wrote:<br>
> I think we're conflating name=* on the road with addr:street=* on<br>
> the thing with an address. These often don't match when the postal<br>
> service disagrees with the local authorities on what to call a road,<br>
> or when the road isn't named. This isn't really something that a<br>
> validator can easily check in an automated fashion, but it is<br>
> something that editors can and should tell the validator to ignore on<br>
> a case by case basis.<br>
<br>
This is something easily checkable with the Coloured Streets style,<br>
however. If anything, that style is *too* good at highlighting addresses<br>
which do not match the nearby street.<br>
<br>
This is why I think we might need something like addr_name which<br>
Coloured Streets would check first, as that might well differ from the<br>
signposted name.<br></blockquote><div><br></div><div>I like this idea and would be on board. Though I'd probably go with <font face="monospace">name</font><font face="monospace">:addr=*</font> for the key. </div></div></div>