<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    So, I would like to know what would be the technical pros and cons
    regarding heritage:ref:operator=* vs ref:operator=* , i.e. the
    database use, rendering, consulting, exporting etc.<br>
    <br>
    <br>
    <div class="moz-cite-prefix">Às 21:04 de 17/04/2020, Paul Allen
      escreveu:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPy1dOJUT2L51m1YPdNwytcBkaz=LHu1VnZSaO9EvrNQQdH66g@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Sat, 18 Apr 2020 at 00:43, Martin Koppenhoefer
          <<a href="mailto:dieterdreist@gmail.com"
            moz-do-not-send="true">dieterdreist@gmail.com</a>> wrote:</div>
        <div dir="ltr"><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">I still don’t see why we
            would need a new tag heritage_title rather than the
            established protection_title##<br>
          </blockquote>
          <div><br>
          </div>
          <div>From  <a
              href="https://wiki.openstreetmap.org/wiki/Key:protection_title"
              moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:protection_title</a></div>
          <div><br>
          </div>
          <div>    Requires</div>
          <div>        boundary=national_park</div>
          <div>        boundary=protected_area</div>
          <div><br>
          </div>
          <div>So not applicable to heritage=*.</div>
          <div><br>
          </div>
          <div>Admittedly, the wiki page for protected_area states that
            it can be used</div>
          <div>on heritage sites, but when you read through the rest of
            the page it's</div>
          <div>not talking about buildings.  Or even a castle complex. 
            It's talking about</div>
          <div> things like "registered historic landscapes" (a UK
            term), which are<br>
          </div>
          <div>historic and therefor e have heritage value, but aren't
            covered by the</div>
          <div> existing heritage=* key.  Instead they're covered by</div>
          <div>boundary=protected_area (I think).<br>
          </div>
          <div><br>
          </div>
          <div>The heritage=* and boundary=protected_area are pretty
            much orthogonal</div>
          <div> in what they cover.  There might be cases where both
            tags apply but they</div>
          <div>are going to be exceptions rather than the rule.</div>
          <div><br>
          </div>
          <div>-- <br>
          </div>
          <div>Paul</div>
          <div><br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>