<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
This is the main reason why I came up with this refinement.<br>
For example, if I search for "ref:" at taginfo, there are *millions*
of results. I believe this has implications in data management,
although I'm by no means an expert on that matter.<br>
<br>
<br>
<div class="moz-cite-prefix">Às 20:57 de 20/04/2020, Paul Allen
escreveu:<br>
</div>
<blockquote type="cite"
cite="mid:CAPy1dOKUigLwuhvTHtSSiXy8R7_tB-VShnCrPDhHjCXBJwhw_g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">As it stands, there is a possibility
for namespace collision. That is theoretically
<div>a problem. An object might have two references, but
we've made heritage</div>
<div>references take the form ref:xxx=* so if the other ref is
of the form ref=*</div>
<div>there won't be a collision. But it's also possible that
both schemes want</div>
<div>to use ref:xxx. So adding heritage to the ref key fixes
that remote</div>
<div>possibility.</div>
<div><br>
</div>
<div>As it stands, overpass queries would not be able to
distinguish the right ref</div>
<div>if an object has a heritage ref:xxx=yyy and a
non-heritage ref:aaa=bbb. A</div>
<div>remote possibility. Adding heritage to the ref key fixes
it.</div>
<div><br>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>