<html><head><style type="text/css">body, p, li { font-family: NokiaPureTextLight; }</style></head><body><div id="fenix-user-content">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">oneway=yes;no is clearly wrong, and not a tag where semicolons should supported.</span></p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; font-family:'NokiaPureTextLight';"><br></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">However amenity=pub;hotel makes perfect sense. </span></p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; font-family:'NokiaPureTextLight';"><br></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">Phil (trigpoint)</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">--</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';"> </span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">Sent from my Nokia N9</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';"> </span></p></div><br><div id="fenix-reply-header"><p>On 24/09/2013 8:54 Jochen Topf wrote:<br></p></div><div id="fenix-quoted-body"><div>
On Tue, Sep 24, 2013 at 09:50:41AM +0200, Martin Koppenhoefer wrote:<br>
> > Am 23/set/2013 um 22:44 schrieb Paul Norman <<a href="mailto:penorman@mac.com">penorman@mac.com</a>>:<br>
> > <br>
> > This of course doesn't avoid contradictory tags like tiger:separated=yes;no <br>
> > but it at least avoids tiger:separated=yes;no;no;no;yes;no;yes;...<br>
> <br>
> <br>
> at least they remain as indication where a combine shouldn't have been done, so you can find these easier for reverting/fixing. Insofar this is preferable behavior compared to forcing the mapper to choose one, which would result in a consistent-LOOKING situation afterwards.<br>
<br>
</div>
<div>
I disagree. If the mapper who does the merge doesn't know which tag is<br>
right, he should not do the merge. He is mapping in the blind. A broken<br>
tag like "oneway=yes;no" isn't usable and it isn't fixable without local<br>
knowledge (which the mapper who broken things might have had, but it<br>
is unlikely that somebody seeing the broken tag has). So these cases<br>
linger around for too long a time.<br>
<br>
</div>
<div>
Jochen<br>
</div>
<div>
-- <br>
</div>
<div>
Jochen Topf <a href="mailto:penorman@mac.com">penorman@mac.com</a> <a href="http://www.jochentopf.com/">http://www.jochentopf.com/</a> +49-721-388298<br>
<br>
_______________________________________________<br>
</div>
<div>
talk mailing list<br>
</div>
<div>
<a href="mailto:penorman@mac.com">penorman@mac.com</a><br>
<a href="http://www.jochentopf.com/">http://www.jochentopf.com/</a><br>
<br>
</div>
</div><br></body></html>