<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Yves,<br>
<br>
My interest is running declarative 3D (X3D) in a browser. I knew
that several things were different and some browser-specific nodes
would be required to support both flat-3D and VR/AR. I very
intentionally did not work on the non-browser side of X3D. My time
resources were limited and I knew that a lot of work needed to be
done on the DOM side. Because of the fundamental differences (DOM
is an API, HTML5 defines the environment, and the event model is
different) I split the two and left the "Classic Environment" for
others to develop. Also note that "Classic Environment" !=
"Classic VRML" (encoding); however, there is no support for the
"Classic VRML" encoding (or the Compressed Binary Encoding) in
X3Dng as those structures do not fit into the HTML5 environment as
elements and attributes.<br>
<br>
From my standpoint serious discussions of X3Dng can be held
anywhere. The document is public and I will be working on
including and revising material based on development and
reasonable suggestions. According to Consortium rules, the
official discussion takes place within the X3D WG.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:FABBD6CB-FEC4-4770-83AC-32EB3C95631C@gmail.com"
type="cite">
<pre wrap="">For an outsider, it's difficult to know if it's worth commenting here or if serious discussions are held elsewhere, and the weight of your X3Dng specification document.
I'll just make a general remark. "Classic Environment" sounds a lot like "Classic VRML" (encoding). In both cases, I hope you don't equate "classic" with "obsolete", but I have doubts, to put it mildly. For instance in your first figure, the "Classic Environment" looks like it's frozen and kept only for the sake of compatibility with existing files (which is actually what you write above). It must be extended with "New nodes", but by writing "(also in Classic)" in the "DOM Environment" frame, that seems to imply it's a minor artifact nobody will be interested in.
Thanks,
Yves
On 4 nov. 2016, at 01:55, Leonard Daly wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have formally submitted the "X3D Next Generation" specification document for Working Group review. The document is also publicly available at <a class="moz-txt-link-freetext" href="http://tools.realism.com/specification/x3d-next-generation">http://tools.realism.com/specification/x3d-next-generation</a>. This document describes how X3D (as declarative 3D) is integrated into the HTML and DOM environment. Many new nodes are added to bring some capabilities up to current industry practice.
This document is the initial public draft and may be updated or revised at any time. The version submitted to the WG is a copy of this content taken on 2016-11-03.
--
Leonard Daly
3D Systems & Cloud Consultant
LA ACM SIGGRAPH Chair
President, Daly Realism - Creating the Future
_______________________________________________
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>
<pre wrap="">
</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>