[x3d-public] announce: X3D4 updates

[Don Brutzman]

"X3DScript" is non standard and will not be included in the X3D specification.

It may be a useful hack to get X3DOM to coexist in a well-behaved way with HTML.  Should simply debugging a lot, eliminating ambiguity to get things working.

Once it is working, we can then address how to let X3DOM be in charge of all Script nodes within an X3D scene.

If no one can get X3DOM to handle it, it simply remains a curious noncompliant deviation from X3D.

p.s. Gee we got Script working in 1997, didn't seem so hard then.  Hopefully you can get X3DScript working now, that is most of the work.

On 10/14/2020 7:47 PM, John Carlson wrote:
> 
> Don’t forget to add X3DScript as previously mentioned.  Note I don’t expect X3DOM to support Script node for backwards compatibility.
> 
> John
> 
> 
> On Wed, Oct 14, 2020 at 7:03 PM Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>> wrote:
> 
>     I have updated X3D4 nodes and fields and documentation to support all changes for Physically Based Rendering (PBR) and glTF, plus most changes for Projective Texture Mapping (PTM).
> 
>     a. X3D XML Schema and DOCTYPE
>     b. X3D Unified Object Model (X3DUOM)
>     https://www.web3d.org/specifications/
> 
>     c. X3DJSAIL: X3D Java Scene Access Interface Library
>     http://www.web3d.org/specifications/java/X3DJSAIL.html
> 
>     d. X3DPSAIL (Python X3D Package)
>     https://pypi.org/project/x3d/
>     https://www.web3d.org/x3d/stylesheets/python/python.html
> 
>     e. X3D Ontology (Turtle)
>     https://www.web3d.org/x3d/content/semantics/semantics.html
> 
>     f. X3D JSON
>     https://www.web3d.org/x3d/stylesheets/X3dToJson.html
> 
>     g. X3D Tooltips
>     https://www.web3d.org/x3d/content/X3dTooltips.html
> 
>     h. X3D Validator
>     https://savage.nps.edu/X3dValidator/
> 
>     i. X3D Specification (github), editorial smoothing continues
>     https://github.com/Web3DConsortium
> 
>     Needless to say, it takes a lot of cross-checking to get all this to hang together.  That is good, high reliability.
> 
>     Everything is published and checked into version control, along with build output logs for comparison.
> 
>     Next, I expect one more X3D4 update prior to Web3D 2020 Conference:
> 
>     - Sound component updates for W3C Audio API,
>     - A few more hanges to PTM (texture transform, X3DLightingNode) resolution planned for this friday
>     - shadowIntensity, in or out?
> 
>     At that point we will have the entire infrastructure needed to support all X3D4 implementation capabilities.  No really.
> 
>     All feedback and testing welcome.  Have fun with X3D4!  8)
> 
>     all the best, Don
>     -- 
>     Don Brutzman  Naval Postgraduate School, Code USW/Br brutzman at nps.edu <mailto:brutzman at nps.edu>
>     Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
>     X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
> 
>     _______________________________________________
>     x3d-public mailing list
>     x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>     http://web3d.org/mailman/listinfo/x3d-public_web3d.org
> 

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman