<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 12/23/2015 9:42 AM, John Carlson
      wrote:<br>
    </div>
    <blockquote
      cite="mid:D905DB80-0387-4F2C-A26E-E2FD22183963@gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      Purpose:  Avoid XML and the DOM api (probably not the best
      reason).  The loader uses the DOM api, so…</blockquote>
    <br>
    <br>
    When you load a JSON file into the DOM don't you get the DOM
    interface anyway? (or am I misunderstanding the statement)<br>
    <br>
    Stating you want to avoid XML is insufficient. Why do you want to
    avoid XML? Is it the parsing? Don't like angle brackets? Want an
    object representation vs. a document one?<br>
    <br>
    HTML is very like XML. Is there a problem there too?<br>
    <br>
    <br>
    Leonard Daly<br>
    <br>
    <br>
    <br>
    <br>
    <blockquote
      cite="mid:D905DB80-0387-4F2C-A26E-E2FD22183963@gmail.com"
      type="cite">
      <div class=""><br class="">
      </div>
      <div class="">Purpose:  Near native access times.  JavaScript
        only.  Does not apply to parsing. Cecile can weigh in here.<br
          class="">
        <div class=""><br class="">
        </div>
        <div class="">Joh<br class="">
          <div>
            <blockquote type="cite" class="">
              <div class="">On Dec 23, 2015, at 10:49 AM, Leonard Daly
                <<a moz-do-not-send="true"
                  href="mailto:Leonard.Daly@realism.com" class="">Leonard.Daly@realism.com</a>>
                wrote:</div>
              <br class="Apple-interchange-newline">
              <div class="">
                <meta content="text/html; charset=windows-1252"
                  http-equiv="Content-Type" class="">
                <div bgcolor="#FFFFFF" text="#000000" class="">
                  <div class="moz-cite-prefix">I have been following the
                    discussion on JSON for a while. I got behind on
                    email reading, so I don't know if this was addressed
                    after this email.<br class="">
                    <br class="">
                    I think there is one question that need to be asked
                    first:<br class="">
                    <br class="">
                    <b class="">What is the purpose of the JSON
                      encoding?</b><br class="">
                    <br class="">
                    JSON is used for a variety of purposes, including
                    efficient data transfer, storage, and archive. Each
                    of these purposes has its own requirements. For
                    example for transfer you typically want a compact
                    format that takes little time and memory to process
                    on the receiving end. Small sizes are important for
                    archive formats, but they also need to have
                    longevity. Taking additional time to unpack is
                    generally not a problem.<br class="">
                    <br class="">
                    If a file is hand-created or edited; then comments
                    are important. While auto-generated, intermediate,
                    or data-base generated files typically do not have
                    comments (or contain only minimal comments).<br
                      class="">
                    <br class="">
                    So, back to my question. If the JSON format is
                    primarily for transfer, then it should be compact
                    and without non-essential data. Since comments are
                    not part of the X3D content model; they are
                    non-essential data to the file and should not be
                    included in it.<br class="">
                    <br class="">
                    If the purpose is for archival or non-archival
                    storage, then comments are important and need to be
                    included (unless the JSON format is strictly an
                    intermediate format).<br class="">
                    <br class="">
                    I do not think it reasonable to state that all X3D
                    encodings are storage (or all choices). That ignores
                    the best features of any encoding and forces all
                    encodings to support the worst features of each.<br
                      class="">
                    <br class="">
                    <br class="">
                  </div>
                  <br class="">
                  <div class="moz-signature">-- <br class="">
                    <font class="tahoma,arial,helvetica san serif"
                      color="#333366"> <font class="" size="+1"><b
                          class="">Leonard Daly</b></font><br class="">
                      3D Systems & Cloud Consultant<br class="">
                      X3D Co-Chair on Sabbatical<br class="">
                      LA ACM SIGGRAPH Chair<br class="">
                      President, Daly Realism - <i class="">Creating
                        the Future</i> </font></div>
                </div>
                _______________________________________________<br
                  class="">
                x3d-public mailing list<br class="">
                <a moz-do-not-send="true"
                  href="mailto:x3d-public@web3d.org" class="">x3d-public@web3d.org</a><br
                  class="">
                <a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br
                  class="">
              </div>
            </blockquote>
          </div>
          <br class="">
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <font class="tahoma,arial,helvetica san serif" color="#333366">
        <font size="+1"><b>Leonard Daly</b></font><br>
        3D Systems & Cloud Consultant<br>
        X3D Co-Chair on Sabbatical<br>
        LA ACM SIGGRAPH Chair<br>
        President, Daly Realism - <i>Creating the Future</i>
      </font></div>
  </body>
</html>