<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
So, what's the rationale for using heritage:operator and not
heritage:ref?<br>
It's these inconsistencies that breaks my logic...<br>
<br>
<br>
<div class="moz-cite-prefix">Às 22:19 de 20/04/2020, Paul Allen
escreveu:<br>
</div>
<blockquote type="cite"
cite="mid:CAPy1dOJxpwDQa6yfzgiOd_zrStZeO8UuceF0BwViJXCU=bAWmQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Tue, 21 Apr 2020 at 02:10, António Madeira
<<a href="mailto:antoniomadeira@gmx.com"
moz-do-not-send="true">antoniomadeira@gmx.com</a>> wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div> 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>
</div>
</blockquote>
<div><br>
</div>
<div>Most of the heritage stuff I've mapped has been in Wales,
so I search for</div>
<div>ref:cadw not ref:. If you know the heritage operator you
can get reasonably</div>
<div>sensible results. If you were after a count of heritage
sites over the<br>
</div>
<div>whole worlds then search for heritage:operator at
taginfo.</div>
<div><br>
</div>
<div>-- <br>
</div>
<div>Paul</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>