[x3d-public] X3D standards: Scene Access Interface (SAI) addition for flexible application support, updated relationships diagram

[John Carlson]

Don,

This sounds like a positive response to the is=“x3d” attribute reality
for React and X3DOM.

All the more reason to stay away from Three and WebGPU.  But it seems like
with React, we wouldn’t need ROUTEs to/from Scripts, and if we construct
React effects/components/states from X3D or X3D JSON, there will be state
changes that avoid a bunch of event listeners, at least on the surface.
Interesting possible work ahead.

I’m going to watch some React tutorials.

Thank you!

John

On Wed, May 7, 2025 at 3:54 PM Brutzman, Donald (Don) (CIV) via x3d-public <
x3d-public at web3d.org> wrote:

> The X3D Scene Access Interface (SAI) is ISO/IEC 19775-2.  It is an
> abstract reference defining critical capabilities for standard language
> bindings that support X3D. These application programming interface (API)
> features can be used to interact with X3D worlds either from within the
> worlds or from external programs.
>
> This specification is functionally aligned with ISO 19775-1, the X3D
> Architecture. The SAI is another abstract reference, meaning that it is not
> implemented directly but is used by other specifications.  It specifically
> defines requirements for the other X3D programming-language bindings:
> ECMAScript (JavaScript), Java, C, C++, C#, Python, and (possibly someday)
> Pascal.
>
> An updated diagram showing all of the various X3D specifications and their
> relationships can be found at
>
>    - X3D Graphics Standards Relationships
>    -
>    https://web3d.org/specifications/X3dGraphicsStandardsRelationships.png
>
>
> Dick Puk and I have made the following recommended addition to the SAI:
>
>
>    - X3D Part 2: Scene access interface (SAI) version 4.0, CD version
>    (with markup)
>    -
>    https://web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-2v4.0-CD/Part02/X3D_SAI.html
>    - clause 7 Conformance and minimum support requirements, 7.3.1
>    Requirements for implementations
>    - "X3D programming language bindings have the option of defining
>    suggested common invocation patterns for external X3D applications.
>    Implementations remain free to provide additional application-oriented
>    properties and methods as appropriate for each tool and programming language
>    ."
>    -
>    https://web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-2v4.0-CD/Part02/conformance.html#RequirementsforImplementations
>    X3D SAI, ISO/IEC 19775-2:202x, 7 Conformance and minimum support
>    requirements
>    <https://web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-2v4.0-CD/Part02/conformance.html#RequirementsforImplementations>
>    7.1 Introduction and topics 7.1.1 Introduction. This clause defines
>    the minimum required support for language bindings conforming to this part
>    of ISO/IEC 19775.
>    web3d.org
>
>
> Comments on this change, and any other changes, are welcome.  Please be
> advised that we intend to advance X3D SAI version 4.0 to Draft
> International Standard (DIS) status in July, which is expected to result in
> final international balloting for approval as an updated International
> Standard (IS).
>
> Each of the documents is in github version control by the Web3D
> Consortium, with the CD document being scrubbed using an XSLT stylesheet to
> produce the DIS document.  In this case, the cleaned-up version shows the
> same added prose with no highlighting:
>
>
>    - X3D — Part 2: Scene access interface (SAI) version 4.0, DIS version
>    (no markup)
>    -
>    https://web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-2v4.0-DIS/Part02/X3D_SAI.html
>    -
>    Https://web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-2v4.0-DIS/Part02/conformance.html#RequirementsforImplementations
>
>
>
> We are performing this work as ISO editors working in the X3D Standards
> Group.  We offer a weekly discussion window on the Web3D Consortium zoom
> line, 0900-1000 pacific time each Friday.
>
>
>    - X3D Standards Working Group
>    - https://www.web3d.org/working-groups/x3d-standards
>    - Web3D Consortium Calendar
>    - https://www.web3d.org/calendar/month
>
>
> Thanks in advance for all scrutiny and comments.
>
> Our march continues to formally and consistently define X3D4 across all
> major file formats and programming languages.  Have fun with X3D!  🙂
>
>
> 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
> https://faculty.nps.edu/brutzman
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250508/ccb24664/attachment-0001.html>