<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Our next meeting is on Wednesday, 22 July 2015 at 8:00 AM PDT
(GMT-0700). <br>
<br>
ALL members of the Web3D Consortium Community (Consortium members +
public) are invited to attend. We use the standard Web3D Conference
phone number. The information is available to Web3D members at
<a class="moz-txt-link-freetext" href="http://www.web3d.org/member/teleconference-information">http://www.web3d.org/member/teleconference-information</a>. If you are
not a member, please contact me for details.<br>
<br>
This is the draft agenda. If you have any additional topics or
details to add to existing topics, please email me.<br>
<br>
Focus: X3D Futures for SIGGRAPH<br>
<br>
Regular Members Known Missing: No one<br>
<br>
<br>
1. Introductions (All)<br>
<br>
2. Spec Status (Dick)<br>
2.1. Diagram showing spec document relationships:<br>
2.1.1. Chart with specification relationships<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/specifications/X3dSpecificationRelationships.png">http://www.web3d.org/specifications/X3dSpecificationRelationships.png</a><br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/specifications/X3dSpecificationRelationships.pdf">http://www.web3d.org/specifications/X3dSpecificationRelationships.pdf</a><br>
2.2. Editor’s Meeting Report on 19777-1 (ECMAScript Language
Binding)<br>
<br>
3. Schedule through the September<br>
3.1. Topics (tentative)<br>
3.1.1. 29 July 2015 – SIGGRAPH Planning<br>
3.1.2. 5 August 2015 – SIGGRAPH Planning<br>
3.1.3. 11 August 2015, 3:30pm Room 504 (LACC)<br>
3.1.4. 19 August 2015 – SIGGRAPH Review, SC-24 preparation<br>
3.1.5. 26 August 2015 – TBD (SC-24 meeting)<br>
3.1.6. 2 September 2015 – X3D Futures (V3.4, V4.x, or any topic
related to future specifications)<br>
3.1.7. 9 September 2015 – TBD<br>
3.1.8. 16 September 2015 – TBD<br>
3.1.9. 23 September 2015 – TBD<br>
3.1.10. 30 September 2015 – TBD<br>
<br>
<br>
4. X3D Futures<br>
4.1. SIGGRAPH in 3- weeks<br>
4.2. Major announcement on X3D V4<br>
4.3. SRC (binary geometry) standard <br>
4.4. Other topics<br>
<br>
<br>
5. X3D V 4 <br>
5.1. A number of significant compatibility issues between X3D and
X3DOM<br>
<br>
5.2. Pages at URLs below highlight differences between X3D and
X3DOM<br>
5.2.1.
<a class="moz-txt-link-freetext" href="http://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx">http://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx</a><br>
5.2.2.
<a class="moz-txt-link-freetext" href="http://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf">http://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf</a><br>
5.2.3. <a class="moz-txt-link-freetext" href="http://realism.com/x3d-tools/Specifications/comparison.php">http://realism.com/x3d-tools/Specifications/comparison.php</a><br>
<br>
5.3. Need to determine which nodes (or classes or nodes) are to
be present in X3D V4<br>
5.3.1. Requirements <br>
5.3.1.1. X3D as a whole must support everything in X3D V3.3,
except for nodes or components that are deprecated<br>
5.3.1.2. End result must be implementable and have two
implementations<br>
5.3.1.3. May add features and./or profiles that are needed,
documented, and implemented<br>
5.3.2. A new ‘HTML’ profile may overlap with existing profiles
and include nodes and./or fields not in any existing profile.<br>
5.3.3. My causes for concern (not necessarily complete)<br>
5.3.3.1. Script node name conflict<br>
5.3.3.2. DOM Namespaces (includes need for IMPORT/EXPORT)<br>
5.3.3.3. DOM/X3D interaction not using the SAI<br>
5.3.3.4. PROTO and EXTERNPROTO<br>
5.3.3.5. Miscellaneous fields (e.g., url, render)<br>
5.3.3.6. Miscellaneous STATEMENTS (e.g., UNITS)<br>
5.3.3.7. Geometry (Mesh, Extrusion, ElevationGrid, SRC)<br>
5.3.3.8. Appearance (Shaders)<br>
5.3.3.9. Spec-compliant implementations<br>
5.3.4. How to go about creating an HTML profile that can be
documented and implemented by December?<br>
<br>
5.4. Source Resource Container (SRC)<br>
5.4.1. A structure for holding geometry that can be directly
imported onto a graphics card<br>
5.4.2. Start on document at
<a class="moz-txt-link-freetext" href="http://realism.com/x3d-tools/Specifications/SRC/">http://realism.com/x3d-tools/Specifications/SRC/</a><br>
5.4.3. Fraunhofer paper and documentation at <a class="moz-txt-link-freetext" href="http://x3dom.org/src">http://x3dom.org/src</a><br>
5.4.4. Is this done as 1 or 2 documents? IOW, are multiple
encodings possible?<br>
<br>
5.5. Other topics (from 4.4)<br>
<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<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>