<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 23/05/2015 3:57 PM, Bryce Nesbitt
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAC9LFPdGZimjbOSNh6OZ-6qCzJauxS+eEN2jo=7jy8zviSNj7g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Fri, May 22, 2015 at 9:34 PM, Dave
            Swarthout <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:daveswarthout@gmail.com" target="_blank">daveswarthout@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Thanks
              for the great suggestions.  I'm typing on an iPhone so
              will respond fully after I reach my final destination.  
              <div><br>
              </div>
              amenity=charging_station with subtags for
              clarification seems to fill the bill. 
              <div class="">
                <div class="h5"><br>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>I think that's a choice with high long term costs to
              rendering and processing engines.</div>
            <div><br>
            </div>
            <div>What will happen is that you're asking rendering and
              processing software to keep up with a blizzard of subtags.</div>
            <div>"charging_station" presently is understood to mean a
              vehicle charging station,<br>
            </div>
            <div>not a generic charging station.  Suddenly icons
              designed for vehicle charging will start appearing inside
              airports.</div>
            <div><br>
            </div>
            <div>Similarly:</div>
          </div>
        </div>
        <blockquote style="margin:0 0 0 40px;border:none;padding:0px">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div>power_supply=cee_17_red</div>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div>power_supply=cee_7_4</div>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>power_supply=usb</div>
            </div>
          </div>
        </blockquote>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>forces rendering to understand a long series of
              values.  For an AC wall plug that means understanding</div>
            <div>that  nema_5_15<span style="white-space:pre"> </span>sev_1011
              and cei_23_16 are all types of AC wall plugs, but that USB
              is something different.</div>
            <div>It's asking too much from the maintainers of rendering
              software.</div>
            <div><br>
            </div>
            <div>------------<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    bbq has the same problem.. electric, wood, gas ... <br>
    as does building .. school, retail, residential, church, post office
    ... <br>
    <br>
    The rendering 'problem' ?<br>
    <br>
    <i>To render or not .. that is the question?   (to misquote Bill). </i><br>
    <br>
    The data can be added .. rendering is another problem.<br>
     First the tagging, then the mapping .. then the rendering. They all
    have their problems. <br>
  </body>
</html>