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

[John Carlson]

On Sat, Oct 4, 2025 at 3:22 PM Don Brutzman via x3d-public <
x3d-public at web3d.org>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.

Don:

Any time you want help with validating JSON documents, let me know.   I can
always rev-up my x3droundtrip project as well!

I also note that jsonlint provides schema validation that I apparently
missed!

Here’s a version which supports
draft JSON Schema 2020-12:

https://www.npmjs.com/package/@prantlf/jsonlint

If you can work with uncertainties in npm (check package.json and
package-lock.json dependencies and pinned versions, make sure you’re not
running postinstall scripts).   Note that npm already checks for
vulnerabilities.  And if you have GitHub, it also checks for issues in the
package*.json files.

I have not seen these features in ant, maven or gradle, but I have seen
that maven repositories do report vulnerabilities.

One issue I haven’t resolved is choosing emoji’s versus X3D URNs in url
fields.  It’s a matter of iri-reference verses uri-reference in the format
properties in the schema.

Note that I think you’ll probably find many issues with MFNode vs SFNode in
X3dToJson.xslt which I haven’t reported.  Most of my XML to JSON
conversions have migrated to Holger’s x3d-tidy.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20251004/43900fc9/attachment.html>