<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">It appears that the conversation should
      be on x3d-public...<br>
      <br>
      <br>
      On 6/21/2016 11:26 AM, John Carlson wrote:<br>
    </div>
    <blockquote cite="mid:576986d8.5623ed0a.653c.7ffc@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style>
      <div class="WordSection1">
        <p class="MsoNormal">I think just the top level and one level
          down would be sufficient, but I don’t really know for sure. 
          It may depend on testing the right proto to get a test case.</p>
      </div>
    </blockquote>
    <br>
    John,<br>
    <br>
    I know that JavaScript, PHP, Perl, and many other languages build
    arrays or arrays, arrays of hashes, hashes of arrays, etc. in
    multi-level structures. It is usually done to store a complete
    package of data. These structures frequently have cross and
    parent/child references to make them circular -- for example DOM
    does this. I presume that you are proposing a non-circular
    representation of the data. <br>
    <br>
    You may have answered these questions along the way, but I don't
    remember seeing it. What is the purpose of this structure from an
    X3D context? Is there some object that you cannot store in the
    existing X3D structure that would be able to be stored in this
    structure?<br>
    <br>
    My concern is that if the JSON encoding supports this structure does
    that mean the structure needs to also appear in the other encodings?
    If so, how would that be done?<br>
    <br>
    <br>
    Leonard Daly<br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <blockquote cite="mid:576986d8.5623ed0a.653c.7ffc@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">John<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Sent from <a moz-do-not-send="true"
            href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a>
          for Windows 10</p>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:"Times New
            Roman",serif"><o:p> </o:p></span></p>
        <div
          style="mso-element:para-border-div;border:none;border-top:solid
          #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
          <p class="MsoNormal" style="border:none;padding:0in"><b>From:
            </b><a moz-do-not-send="true"
              href="mailto:roy.walmsley@ntlworld.com">Roy Walmsley</a><br>
            <b>Sent: </b>Tuesday, June 21, 2016 10:29 AM<br>
            <b>To: </b><a moz-do-not-send="true"
              href="mailto:yottzumm@gmail.com">'John Carlson'</a>; <a
              moz-do-not-send="true" href="mailto:brutzman@nps.edu">'Don
              Brutzman'</a>; <a moz-do-not-send="true"
              href="mailto:x3d@web3d.org">'X3D Graphics member mailing
              list'</a><br>
            <b>Subject: </b>RE: [x3d] Proposal for X3D JSON encoding.
            Array of arrays for anyarray</p>
        </div>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:"Times New
            Roman",serif"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">Hi,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">My
            concern in considering this candidate extension is for
            validation tools. My gut reaction is to consider that it
            would be impossible to validate and MFxxxx. We have
            appreciated that the JSON schema can provide good validation
            for MFxxxx field validation. If arrays could be nested, we
            would likely lose this capability.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">Another
            question would be how many levels of nesting might be
            permitted?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB">Roy<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><b><span
              style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> x3d
            [<a class="moz-txt-link-freetext"
              href="mailto:x3d-bounces@web3d.org">mailto:x3d-bounces@web3d.org</a>]
            <b>On Behalf Of </b>John Carlson<br>
            <b>Sent:</b> 21 June 2016 13:37<br>
            <b>To:</b> Don Brutzman; X3D Graphics member mailing list<br>
            <b>Subject:</b> Re: [x3d] Proposal for X3D JSON encoding.
            Array of arrays for any array<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-family:"Times New
            Roman",serif" lang="EN-GB"><o:p> </o:p></span></p>
        <p><span lang="EN-GB">You could specify in the standard that any
            array of arrays would be treated like a single array with
            the elements in the same order as they appear textually
            (however you say that).<o:p></o:p></span></p>
        <div>
          <p class="MsoNormal"><span lang="EN-GB">On Jun 21, 2016 8:32
              AM, "John Carlson" <<a moz-do-not-send="true"
                href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>>
              wrote:<o:p></o:p></span></p>
          <p><span lang="EN-GB">Actually, I'm only asking where MFNode
              is already valid.<o:p></o:p></span></p>
          <div>
            <p class="MsoNormal"><span lang="EN-GB">On Jun 21, 2016 8:29
                AM, "John Carlson" <<a moz-do-not-send="true"
                  href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>
                wrote:<o:p></o:p></span></p>
            <p><span lang="EN-GB">Not required, but possible MFInt32:<o:p></o:p></span></p>
            <p><span lang="EN-GB">[5, [6,7],8,[9,1,0]]  MFFloat would be
                similar.  I'm not asking for a change to Vec or Matrix
                types.<o:p></o:p></span></p>
            <div>
              <p class="MsoNormal"><span lang="EN-GB">On Jun 21, 2016
                  8:11 AM, "John Carlson" <<a moz-do-not-send="true"
                    href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>
                  wrote:<o:p></o:p></span></p>
              <p><span lang="EN-GB">-children:[<br>
                  { Transform: ... },<br>
                  [ { Transform }, { Transform }],<br>
                  { Transform } ]<o:p></o:p></span></p>
              <div>
                <div>
                  <p class="MsoNormal"><span lang="EN-GB">On Jun 21,
                      2016 7:37 AM, "Don Brutzman" <<a
                        class="moz-txt-link-abbreviated"
                        href="mailto:brutzman@nps.edu"><a class="moz-txt-link-abbreviated" href="mailto:brutzman@nps.edu">brutzman@nps.edu</a></a>>
                      wrote:<o:p></o:p></span></p>
                  <p class="MsoNormal"><span lang="EN-GB">Interesting. 
                      There may be ways to accomplish what you want
                      already, when writing in source code.<br>
                      <br>
                      Examples would help, pseudo-syntax is OK.  Please
                      describe an example or two and let's see what
                      currently works and what doesn't.  TIA.<br>
                      <br>
                      <br>
                      On 6/20/2016 8:45 PM, John Carlson wrote:<o:p></o:p></span></p>
                  <p class="MsoNormal"><span lang="EN-GB">I am proposing
                      that implemenations and perhaps the standard
                      should accept arrays of arrays where arrays are
                      found.  So any MF* can be a combination of SF* and
                      MF*, where * is a type.  So an MFNode can be a
                      collection of SFNodes and MFNodes.  The
                      implementation may choose to flatten the array of
                      arrays into a single array.<br>
                      <br>
                      What do you think?<br>
                      <br>
                      John<o:p></o:p></span></p>
                </div>
              </div>
            </div>
          </div>
        </div>
        <p class="MsoNormal"><span lang="EN-GB"><br>
            all the best, Don<br>
            -- <br>
            Don Brutzman  Naval Postgraduate School, Code USW/Br       <a
              class="moz-txt-link-abbreviated"
              href="mailto:brutzman@nps.edu"><a class="moz-txt-link-abbreviated" href="mailto:brutzman@nps.edu">brutzman@nps.edu</a></a><br>
            Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   <a
              moz-do-not-send="true" href="tel:%2B1.831.656.2149"
              target="_blank">+1.831.656.2149</a><br>
            X3D graphics, virtual worlds, navy robotics <a
              class="moz-txt-link-freetext"
              href="http://faculty.nps.edu/brutzman"><a class="moz-txt-link-freetext" href="http://faculty.nps.edu/brutzman">http://faculty.nps.edu/brutzman</a></a><o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-family:"Times New
            Roman",serif"><o:p> </o:p></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
x3d mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d@web3d.org">x3d@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d_web3d.org">http://web3d.org/mailman/listinfo/x3d_web3d.org</a>
</pre>
    </blockquote>
    <br>
    <p><br>
    </p>
    <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>