<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Andreas,<br>
      <br>
    </div>
    <blockquote
cite="mid:CAKdk67u9AVX3gkZgY4Qq-TyWXtbBpDStrZgOjMJatzmwHLCvug@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>Hi Leonard,</div>
            <div><br>
            </div>
            <div>thanks for sharing your slides. They provide good
              perspective.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Thank you. Sorry for the delay - I had to catch up on some other
    work. I also was considering your comments and how best to respond.<br>
    <br>
    <br>
    <blockquote
cite="mid:CAKdk67u9AVX3gkZgY4Qq-TyWXtbBpDStrZgOjMJatzmwHLCvug@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>Some comments. While cobweb certainly is not used
              widely it probably would have deserved mentioning in the
              table of web technologies. Also, I think it is clear that
              A-Frame is quite a bit ahead in terms of providing VR
              capability, compared to others (unity may have something
              functional as well). The slides, at least, did not seem to
              make this obvious.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I wanted to include applications/packages people were familiar with.
    I was surprised at the lack of familiarity with X3DOM and A-Frame
    from those in the audience. I was limited by space on the chart. I
    would have listed Cobweb as open, declarative, and HTML with a
    'Level of Use' as "low".<br>
    <br>
    A-Frame's VR capability (as all of its rendering capability) is
    provided by Three.js. I know that Unreal has rather extensive VR
    (Rift, Vive) headset capability. I believe that Unity does too.
    Since the focus for this talk was on browser-based VR, I couldn't
    spend the time addressing VR capabilities of these platforms.<br>
    <br>
    <br>
    <br>
    <blockquote
cite="mid:CAKdk67u9AVX3gkZgY4Qq-TyWXtbBpDStrZgOjMJatzmwHLCvug@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>Did you get feedback after your presentation ? Anything
              you can share would be interesting.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Nothing significant. There was more in discussions with other
    attendees at the conference who did not see my presentation. I'll be
    posting that over the next month or so.<br>
    <br>
    <br>
    <blockquote
cite="mid:CAKdk67u9AVX3gkZgY4Qq-TyWXtbBpDStrZgOjMJatzmwHLCvug@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>The idea of combining of x3dom and A-Frame somehow is
              interesting. I think it would boil down to implementing a
              new x3d browser on top of A-Frame which may be quite
              possible. I experimented by reimplementing IndexedFaceSet
              and ElevationGrid in A-Frame and think that geometry and
              material nodes could be quite straightforward. Not sure
              about everything else but probably possible with a lot of
              work. It also would mean having a SAI on top of the DOM
              (as being manipulated by A-Frame and custom event
              interfaces). Your presentation made a good argument that
              there is a lot of value in having a wide set of
              standardized capabilites.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Personally, I think putting X3DOM on top of A-Frame is a bit like
    inverting a pyramid. A-Frame (as defined, not extended) is a rather
    limited-capability system. I think it would be much easier to put
    A-Frame on top of X3DOM -- except the part with A-Frame extensions.
    I think a better choice is to merge the two keeping the most
    important capabilities of both. I am formulating some ideas on that.<br>
    <br>
    <br>
    Leonard Daly<br>
    <br>
    <br>
    <blockquote
cite="mid:CAKdk67u9AVX3gkZgY4Qq-TyWXtbBpDStrZgOjMJatzmwHLCvug@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>-Andreas</div>
            <div><br>
            </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Message: 3<br>
              Date: Mon, 3 Apr 2017 21:02:28 -0700<br>
              From: Leonard Daly <<a moz-do-not-send="true"
                href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>><br>
              To: X3D Public <<a moz-do-not-send="true"
                href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br>
              Subject: [x3d-public] Presentation from SVVR2017<br>
              Message-ID: <<a moz-do-not-send="true"
                href="mailto:d3ded90c-4be7-17e3-af0c-7d82276acba6@realism.com">d3ded90c-4be7-17e3-af0c-<wbr>7d82276acba6@realism.com</a>><br>
              Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
              <br>
              I presented at Silicon Valley VR Expo 2017 last week. The
              title of the<br>
              presentation was "Open Source Declarative VR/3D
              Environment" where the<br>
              focus was on enterprise requirements for VR. In the
              presentation I<br>
              looked at high level requirements and capabilities of a
              declarative<br>
              VR/3D/AR language, and compared those requirements to the
              offerings from<br>
              X3DOM and A-Frame. I found that neither application met
              the<br>
              requirements, but both are close enough that a merge would
              get there.<br>
              <br>
              Presentation: <a moz-do-not-send="true"
                href="http://realism.com/svvr2017" rel="noreferrer"
                target="_blank">http://realism.com/svvr2017</a>
              (redirect to Google Slide)<br>
              <br>
              Blog: <a moz-do-not-send="true"
                href="http://realism.com/blog/report-svvr2017"
                rel="noreferrer" target="_blank">http://realism.com/blog/<wbr>report-svvr2017</a><br>
              <br>
              <br>
              --<br>
              *Leonard Daly*<br>
              3D Systems & Cloud Consultant<br>
              LA ACM SIGGRAPH Chair<br>
              President, Daly Realism - /Creating the Future/<br>
              -------------- next part --------------<br>
              An HTML attachment was scrubbed...<br>
              URL: <<a moz-do-not-send="true"
href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170403/16f60948/attachment-0001.html"
                rel="noreferrer" target="_blank">http://web3d.org/pipermail/<wbr>x3d-public_web3d.org/<wbr>attachments/20170403/16f60948/<wbr>attachment-0001.html</a>><br>
              <br>
            </blockquote>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<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>
</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>
        LA ACM SIGGRAPH Chair<br>
        President, Daly Realism - <i>Creating the Future</i>
      </font></div>
  </body>
</html>