[x3d-public] X3D Working Group meeting 8 DEC 2023: proposed charter improvements

John Carlson yottzumm at gmail.com
Wed Dec 13 10:27:15 PST 2023


Don, it’s okay to equate X3D definitions between standards.  It’s not okay
to equate a binding with an encoding.

I did get on the JSON schema Slack, but I haven’t gotten the courage to ask
about standardization. It seems like they are busy working on a lot of
things since 2020, and not necessarily the core standard.   There’s a
#specification channel, which is mildly active.  I guess we haven’t seen a
draft standard for 3 years now.

If someone wants to help promote JSON for a Java binding, adding hooks to
enable using JSON with Java, please check out
https://github.com/coderextreme/x3dschema (I’m moving away from schema,
this used to be the Java JSON schema validator).

On Wed, Dec 13, 2023 at 11:37 AM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

> Good points John.  When reviewing I will confer with Dick Puk to ensure
> that all of our terms of reference align correctly with ISO terminology.
> Our X3D Standards Relationships diagram helps with that careful
> cross-checking.
>
>
>
>    -
>    https://www.web3d.org/specifications/X3dGraphicsStandardsRelationships.png
>
>
>
> Thanks for your review and this suggestion.
>
>
>
> When we get to that point of specification drafting, am expecting that our
> draft documents will
>
>    - use ECMA standards for ECMAScript and JSON
>    - ensure that X3D definitions for each of these are 100% interoperable
>    (and likely identical).
>
>
>
> 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
>
>
>
> *From:* John Carlson <yottzumm at gmail.com>
> *Sent:* Monday, December 11, 2023 9:05 AM
> *To:* Extensible 3D (X3D) Graphics public discussion <x3d-public at web3d.org
> >
> *Cc:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>;
> consortium at web3d.org; x3d at web3d.org
> *Subject:* Re: [x3d-public] X3D Working Group meeting 8 DEC 2023:
> proposed charter improvements
>
>
>
> Looks good Don.   Note in section (b) that JSON is independent of
> JavaScript in many cases, so it’s ok to list them separately.  We can
> accomplish a JavaScript SAI without JSON, and we can accomplish a JSON
> encoding without JavaScript.  It may also be preferable to use ECMAScript
> instead of JavaScript.
>
>
>
> On Mon, Dec 11, 2023 at 10:43 AM Brutzman, Donald (Don) (CIV) via
> x3d-public <x3d-public at web3d.org> wrote:
>
> Attendees Anita Havele, Vince Marchetti, Dick Puk, Don Brutzman.
>
>
>
> The X3D Working Group meets each Friday 09-1000 pacific (12-1300 eastern).
>
>
>
>    -
>    https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
>    <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fus02web.zoom.us%2Fj%2F81634670698%3Fpwd%3Da1VPeU5tN01rc21Oa3hScUlHK0Rxdz09&data=05%7C02%7Cbrutzman%40nps.edu%7C0a073250882642d185a408dbfa6b5e92%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638379111285264610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BXCm0QRgxkRilA%2BDaSLEWKu7izNBH2M0wSQRxSBfbWY%3D&reserved=0>
>    - https://zoom.us/j/148206572
>    <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fj%2F148206572&data=05%7C02%7Cbrutzman%40nps.edu%7C0a073250882642d185a408dbfa6b5e92%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638379111285264610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1qQl6ejbcuUK%2B7vEfGll%2BtzCnmmf2msnz68MUV7lHYI%3D&reserved=0>
>    Password 483805
>    - https://www.web3d.org/member/teleconference-information
>
>
>
> We again looked at updating the X3D Working Group Charter for 2024.
> Current charter is online at
>
>
>
>    - https://www.web3d.org/working-groups/x3d
>
>
>
> First section with suggested edits follows.  None of the current charter
> words are incorrect, am looking to simplify and make clearer:
>
>
>
>
>
> Overview:
>
>
>
> *The Extensible 3D (X3D) Graphics Working Group forms the core of the
> provides the core technical foundation for all working groups within the
> Web3D Consortium. It is responsible for the development of specification of
> core technologies for the X3D suite of Specifications, and the integration
> of the maximum interoperability with related specifications for non-core
> technologies, and coordinating the technical aspects of all Web3D working
> group efforts broad deployment of interactive X3D models. The **X3D
> Graphics Standards: Specification Relationships
> <https://www.web3d.org/specifications/X3dGraphicsStandardsRelationships.png>**
> graphic nicely diagram illustrates these capabilities the interaction and
> relationships between the various X3D specifications.*
>
>
>
> *Interest in metaverse and augmented reality, improvements in high-quality
> audio and visual fidelity on any computer platform, and new support for
> multiple file encodings and programming languages including JSON and
> streaming binary are driving the broad deployment of interactive X3D4
> models across the Web into new domains of real-time 3D human interaction
> development of the next revision of the standard. The Working Group is
> looking for people to help with these and other technical fields in
> creating the X3D V4.0 standard.*
>
>
>
> *The wide-spread adoption of WebGL in all browsers is driving X3D into the
> future. The next generation of X3D (V4.0) will be embedded in the browser
> and support full interaction with the web page. It will include all of the
> features of X3D that are currently available plus new rendering,
> interaction, and device support all running in your browser, whether it is
> on your desktop or your phone. In addition to X3D continuing to work in
> non-browser environments.*
>
>
>
> Condensed:
>
>
>
> *The Extensible 3D (X3D) Graphics Working Group provides the core
> technical foundation for all working groups within the Web3D Consortium. It
> is responsible for development of the X3D suite of specifications, maximum
> interoperability with related technologies, and coordinating the broad
> deployment of interactive X3D models. The X3D Graphics Standards:
> Specification Relationships
> <https://www.web3d.org/specifications/X3dGraphicsStandardsRelationships.png>
> diagram illustrates these capabilities.*
>
>
>
> *Interest in metaverse and augmented reality, improvements in high-quality
> audio and visual fidelity on any computer platform, and new support for
> multiple file encodings and programming languages including JSON and
> streaming binary are driving the broad deployment of interactive X3D4
> models across the Web into new domains of real-time 3D human interaction.*
>
>
>
>
>
> [The next proposed sections are updates from last week’s meeting and email
> discussion.]
>
>
>
> X3D Working Group priorities for 2024 follow.
>
>
>
>    1. *Specifications Synchronization*.  Update, review, implement and
>    advance all corresponding X3D specifications for file encodings and
>    language encodings, continuing rigorous attention to detail through Web3D
>    Consortium, W3C, US INCITS H3, and ISO/IEC standards development
>    organizations (SDOs).
>    2. *Implementations*.  Provide a technical forum that encourages the
>    greatest possible development for functionally complete X3D4 applications,
>    authoring tools, and model converters such as Blender and MeshLab.  Pay
>    special attention to implementations using Humanoid Animation (HAnim), glTF
>    model import, Web Audio API and MIDI 2.0 capabilities for integrated
>    spatial auralization, projective texture mapping, HTML5 integration, XML,
>    JSON/JavaScript, Java, Python, C/C++/C#, compressed binary formats, and
>    additional new X3D 4.0 features.
>    3. *Publications*.  Demonstrate how X3D can make 3D Graphics part of
>    the modern Web by integrating with key infrastructure such as Web3D
>    Conference series, Wikipedia, and other major publication resources.
>    4. *Innovation Foundation*.  Show how Extensibility mechanisms for X3D
>    can implement new capabilities in a standards-compatible way.  Much is
>    possible, model correctness is validatable, and few barriers to exploration
>    exist.
>    5. *Metaverse*.  Support 3D Web Interoperability and Metaverse
>    Standards Register groups in the Metaverse Standards Forum (MSF),
>    implementing shared use cases to provide helpful feedback on successes and
>    next-step goals.
>
>
>
> These renewed priorities fit well as next steps in a quarter century of
> stable evolution using Virtual Reality Modeling Language (VRML) and X3D.
>
>
>
>    - *Past as Prologue*.  The X3D Working Group carefully follows Web3D
>    policies and procedures, integrating much public/private comment that is
>    well documented in X3D email archives and Mantis issue tracker.  Both
>    backwards compatibility and forwards extensibility have been carefully
>    preserved throughout, enabling effective reuse of every VRML97 and X3D
>    model for the past quarter century. Seventh in a specification series
>    starting with VRML97, successful completion of the X3D 4.0 Architecture
>    once again proves that this collaborative process is effective.
>
>
>
>    - *Present, 2024*.  There is much capability in X3D 4.0 already that
>    deserves broader implementation and exposure in high-capability models.
>    Consequently we are deliberately *not* pursuing X3D 4.1 specification
>    improvements with ISO/IEC in 2024.  Meanwhile we do encourage
>    *Innovation* by emphasizing X3D extensibility mechanisms:  Inline,
>    Script, Prototype, software libraries supporting source-code
>    implementations that generate X3D, etc. etc.  New candidate nodes (such as *Image
>    Atlas*) that rise to the level of broad usefulness can be formally
>    considered as contributions to Web3D Recommended Practice.
>
>
>
>    - *Future, 2025+*.  Once all of the corresponding X3D specifications
>    have been updated to match X3D 4.0 architecture, development of a future
>    X3D 4.1 specification revision will be possible.
>
>
>
>
>
> What’s missing?  What’s unclear and might be better expressed?  What else
> do *you* need?
>
>
>
> All improvements are welcome, a big year awaits us…
>
>
>
> Thanks for considering the possibilities.  Have fun with X3D!  8)
>
>
>
>
>
> 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/20231213/89b06c1f/attachment-0001.html>


More information about the x3d-public mailing list