<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">There was a time when the "holy-grail"
of X3D was to be included in every browser so it would not be
necessary to download and install a plug-in for it to function.
Several years ago X3DOM came along and provided a means to not
only play X3D in a browser without a plugin, but it also had some
integration with HTML/DOM. This was a major step to realizing that
early initial hope.<br>
<br>
Now it appears that the effort is to have X3D run stand-alone. I
come to this conclusion based on the number of languages that are
on the list below to have a standardized binding to the SAI, the
lack of DOM as an API as one of those listings, and the lack of
concrete progress on determining how to integrate X3D into an HTML
environment while handling HTML events, CSS, and node name
collisions (i.e., Script).<br>
<br>
Meanwhile there never seems to be enough people and time to work
on the existing issues involved in V4 and clean up from V3.x. Very
little work has been done to understand and investigate
integration of other technologies (e.g., A-Frame and XML3D being
the most notable ones) into the structure of X3D. Also no
significant work has been done to investigate what is necessary to
VR requirements and how X3D could meet those. X3D is woefully
behind the time in the appearance of geometry as it really only
has uniform colors and texture maps. It is missing techniques
such as advanced/alternate lighting models, bump maps,
reflections, shadows, ambient occlusion, physically based
rendering, and others. (For example, see the THREE.js
documentation on what it provides at
<a class="moz-txt-link-freetext" href="https://threejs.org/docs/index.html#api/materials/MeshPhongMaterial">https://threejs.org/docs/index.html#api/materials/MeshPhongMaterial</a>).
It is also important to address VR now because the current plans
call for AR to be part of V4.1 and there is a lot of overlap.<br>
<br>
I do not know what to make of this extensive expanding of X3D when
current work is so resource limited right now.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:9153a138-647a-be1f-6bc0-3b9ae3e9b12b@nps.edu">Following
discussions, the editors have decided to also produce a separate C
language binding for X3D. Languages and editors:
<br>
<br>
a. Dick Puk, Roy Walmsley, Don Brutzman and John Carlson,
EcmaScript 19777-1
<br>
b. Dick Puk, Don Brutzman, Roy Walmsley and John Carlson,
Java 19777-2
<br>
c. Roy Walmsley and Myeong Won Lee,
C 19777-3
<br>
d. Roy Walmsley and Myeong Won Lee,
C++ 19777-4
<br>
e. Myeong Won Lee and Roy Walmsley,
C# 19777-5
<br>
f. Masaki Aono, John Carlson, Brutzman, Walmsley,
Python 19775-6
<br>
<br>
Attached please find updated draft revision to the X3D
Specification Relationships diagram reflecting this change.
<br>
<br>
Roy we will need to initiate ISO New Work Item Proposals (NWIPs)
as part of the formal commencement of work for each project.
<br>
<br>
A new multilingual playing field is emerging... pretty exciting!
<br>
<br>
On 8/8/2017 8:16 AM, Don Brutzman wrote:
<br>
<blockquote type="cite">Some very interesting progress on X3D SAI
implementations is being presented during our ISO meeting at
Virginia Tech Advanced Research Center (VTARC) in Alexandria VA
this week. This work is part of ISO Standards Committee (SC) 24
Working Group 6, convened by Dr. Dick Puk.
<br>
<br>
In addition to existing X3D implementations for JSON, JavaScript
and Java, additional programming-language binding
implementations are emerging. Slidesets to follow.
<br>
[...]
<br>
<br>
Attached please find draft revision to the X3D Specification
Relationships diagram. Change summary:
<br>
- split out C++/C# into separate documents and add Python,
reflecting above changes.
<br>
- note that NumPy scientific libra data types
(<a class="moz-txt-link-freetext" href="http://www.numpy.org">http://www.numpy.org</a>) are needed to add strict typing to
Python.
<br>
- note Java v8 expected as new baseline (supporting lambda
functional programming).
<br>
- note Object Model for X3D (OM4X3D) expected to become part of
future X3D Abstract Specification.
<br>
- note that changes are needed for X3D Scene Access Interface
(SAI) 19775-2 that relax need for Browser object and allow
standalone programming APIs.
<br>
<br>
Needed: any external version dependencies expected for
JavaScript, C++ C#, Python.
<br>
Needed: ISO referencing of Python, NumPy.
<br>
<a class="moz-txt-link-freetext" href="https://stackoverflow.com/questions/1535702/python-not-a-standardized-language">https://stackoverflow.com/questions/1535702/python-not-a-standardized-language</a><br>
<br>
Currently approved version of this diagram is maintained along
with schemas and other specification-support assets at
<br>
<br>
X3D Specifications: Schema and DOCTYPE Validation
<br>
<a class="moz-txt-link-freetext" href="http://2014.web3d.org/specifications">http://2014.web3d.org/specifications</a>
<br>
<br>
For those who care to join, we will discuss both C++/C# and
Python implementations, plus standards drafting, on *Thursday
08-0830 Eastern (0500 Pacific, 1300 GMT)*. As usual, we will
use the Web3D Member Teleconference line.
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/member/teleconference-information">http://www.web3d.org/member/teleconference-information</a>
<br>
<br>
All feedback welcome. These and any subsequent draft changes
will be reviewed by the X3D Working Group, likely in 2 weeks
(Wednesday 23 August).
<br>
</blockquote>
<br>
<br>
</blockquote>
<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>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>