[x3d-public] X3D Specifications ready for review: XML, ClassicVRML, and Compressed Binary Encodings

[Don Brutzman]

Thanks for the thoughtful review comment, Holger.

Please be advised that the three specifications open for review (XML,
Classic VRML, and Compressed Binary encodings) are precisely aligned with

   - X3D Architecture ISO/IEC 19775-1:2023 *version* *4.0*
   -
   https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/Architecture.html

and so you are not seeing version 4.1 changes in the grammar.

   - X3D 19776-2 Classic VRML Encoding, Annex A (normative) Grammar
   -
   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-2v4.0-WD1/Part02/grammar.html
   (with markup)
   -
   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-1v4.0-CD/Part01/X3D_XML.html
   (pristine draft)

That said, if DESCRIPTION reaches consensus and is added to IMPORT/EXPORT
in X3D version 4.1 draft someday,

   - X3D Architecture ISO/IEC 19775-1:2023 *version 4.1 draft*, clause 9
   Networking component, 9.2.5 IMPORT statement and 9.2.6 EXPORT statement
   -
   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/networking.html#IMPORTStatement
   -
   https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/networking.html#EXPORTStatement

then future XML syntax will probably be something like the following in 4.1,
and expected syntax in other encodings/languages might be inferred in the
translations.

   - X3D Example Archives: Basic, X3D Specifications, Inline Export, line 48
   <https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineExport.html#48>
   - <EXPORT localDEF='T1
   <https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineExport.html#T1>
   ' AS='RootTransform' description='allow other models to load and utilize
   the T1 subgraph'/>
   -
   https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineExportIndex.html


   - X3D Example Archives: Basic, X3D Specifications, Inline Import, line 37
   <https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImport.html#37>

   - <IMPORT inlineDEF='MyInlineModel
   <https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImport.html#MyInlineModel>
   ' importedDEF='RootTransform' AS='MyInlineRootTransform'
   description="load and then animate that subgraph'/>
   -
   https://www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/InlineImportIndex.html

If progress continues as planned, we should be able to have a draft XML
DTD/Schema (and hopefully JSON Schema too) in the spring in order to start
building, validating, and evaluating models with such new features.

Have fun with X3D: extensible, evolving, with consistent expressive power
and functionality across every variation!  😀👍

all the best, Don
-- 
X3D Graphics, Maritime Robotics, Distributed Simulation
Relative Motion Consulting  https://RelativeMotion.info


On Sat, Oct 4, 2025 at 12:12 PM Holger Seelig <holger.seelig at yahoo.de>
wrote:

> The upcoming X3D4.1 specification defines a DESCRIPTION keyword for the
> IMPORT and EXPORT statement:
>
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/networking.html#IMPORTStatement
>
> Because the showed syntax looks like Classic VRML Encoding, I would expect
> to find it again in the draft grammar:
>
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-2v4.0-WD1/Part02/grammar.html
>
> Additionally I would expect to have a similar syntax (attribute for XML, a
> property for JSON) for the other encodings.
>
> Best regards,
> Holger
>
> —
> Holger Seelig
> Leipzig, Germany
>
> holger.seelig at yahoo.de
> https://create3000.github.io/x_ite/
> https://patreon.com/X_ITE
>
>
>
> Am 04.10.2025 um 02:27 schrieb Don Brutzman via x3d-public <
> x3d-public at web3d.org>:
>
> Dick Puk and I have been quietly toiling all year to update multiple X3D
> specifications, as part of the X3D Standards Working Group.
>
> The X3D Standards Progress page shows a concise summary of marked-up and
> pristine HTML updates of all these long-standing standards documents.
>
>
>    - X3D Standards Progress | Web3D Consortium
>    <https://www.web3d.org/x3d/progress>
>    - https://www.web3d.org/x3d/progress
>
> <image.png>
> We are now requesting review and comments for the X3D XML, ClassicVRML,
> and Compressed Binary Encodings to match the X3D version 4.0 Architecture.
> You are welcome to view markup changes, pristine versions, or both
> side-by-side for careful comparison. For example, see attached screen
> comparison.
>
> All changes are carefully documented in the Web3D Consortium Mantis issue
> tracker, and maintained in github version control.
>
> In coming months we will begin following a new ISO process for PAS
> submission and standardization.
>
> *Many thanks to many implementers, modelers, and users over the years who
> have steadily improved X3D. *😀*👌*
>
> All comments appreciated, best discussed on x3d-public mailing list (or
> x3d mailing list for member-only, private concerns.
>
> Have fun with X3D!
>
> all the best, Don
> --
> X3D Graphics, Maritime Robotics, Distributed Simulation
> Relative Motion Consulting  https://RelativeMotion.info
> <https://relativemotion.info/>
> <X3dXmlSpecificationComparison-1200x620.png>
> _______________________________________________
> 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/20251004/be8e97ee/attachment-0001.html>