[x3d-public] Take down X3DJSONLD+JSON Validator website

[John Carlson]

Future plans.

I am thinking of taking down the X3DJSONLD website and perhaps the X3D JSON
validation website, mainly because they are becoming out of date (technical
debt) and difficult to maintain.   Plus, I rarely use them these days.

https://coderextreme.net/X3DJSONLD/src/main/html/index.html

https://coderextreme.net/X3DJSONLD/src/main/html/validator.html


X3DOM, X_ITE and Sunrize already support X3D JSON, and “npx x3dvalidate”
provides JSON validation, including create3000’s PBR extensions.

I’m not really an HTML/CSS programmer, being more familiar with various
command-line tools, with a history of Java 2D/3D GUI development.

What I might do is expand my use of Vercel/Next.js/React/Shadcn/
v0.dev/Supabase/claude.ai/Blender, and I’ve already set up a couple of
v0.dev websites.   What I’m thinking of is a React site for loading X3D
JSON, similar to X3DJSONLD, realizing that it will require more server-side
support than just Apache.

If anyone is currently using the links above and can’t replace them easily,
let me know.   I do know that STL/PLY/EXI conversion tools may be hard to
find, and I may work on a combination of Java/GraalJS GUIs for conversions,
etc., which might eventually see adoption or replacement in X3D-Edit.  I
will have to research plugins for NetBeans as well.  I already have some
GraalJS integration with the Jaminate app.   I am also moving in the
direction of GraalPy, developing conversions from X3D JSON to Python which
make use of X3DJSAIL (recently reported).  The main issue with combining
X3DJSAIL+Python seems to be issues with memory on large HAnim files, which
Java itself already has issues with.   I haven’t seen these issues with
x3d.py.

At some point, I plan to do an X3DJSONLD.pas to incorporate X3D JSON into
CGE.  I do have a skeleton API laid out.   This should leverage the
excellent validation tools found in castle-model-viewer, and I may extend
that to support X3D JSON.   If anyone is actually interested in
x3djsonld.cpp, let me know, I have some code which “works” to convert JSON
to XML, but it might have memory leaks.

I will continue to pursue various other options for X3D JSON conversion and
validation, since I’ve been able to keep that up-to-date.

The main reason for this is that JavaScript/TypeScript now seems to require
a build step, and that’s unacceptable.   We got to a point where build
steps were not required, and now we seem to be going backwards.  If I’m
going to do builds, I might as well have the full IDE/Framework plus tools
doing the builds for me.

I am open to supporting other non-standard X3D encoding conversions, and I
might even consider an X3D JSON to VRML conversion app.

What I plan to do is a bit more work on relieving the technical deb in the
X3DJSONLD website, and if it doesn’t work out, just move on.

I have recently been working on serializing XML to other formats, including
JSON and may develop similar capabilities.

I still have some outstanding tasks in Blender, including multiple
animations, HAnim export (with single skinCoord for multiple meshes).

I’m also interested in JSON to CPPON/C/C++/C#, especially with rendering.

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