[x3d-public] X3D Working Group agenda 13 JAN 2023: 2023 goals, ISO specification updates, X3D Node Inventory Comparison

[John Carlson]

I do realize the value of a JavaScript SAI library for C/C++/C#/Pascal/Java
browsers!

I don’t think X3DJSONLD.* is suited for this.   We can talk about a
separate product for generating something similar to x3d.py/X3DJSAIL in
JavaScript for a browser with a JavaScript engine.

When having discussions with C/C++ x3d browser engineers, it was decided
that a JSON to XML converter in a separate process would be a good first
step.  I have a prototype for that, in C++. Adopters welcome.

That is pretty much the niche i fit in.

There are also more converters, that take the DOM document from X3DJSONLD.*
and can render to a number of “encodings,” especially in batch fashion.
These converters might now be called SAI, I’ve not studied the standard.

The main input into X3DJSONLD is a JSON object.  The web page serves as an
NxM converter.

Please stop advertising X3DJSONLD as SAI.   What it can do is generate
Python, Java and JavaScript programs that use x3d.py and X3DJSAIL.

It’s in the name, X3D JSON LoaDer, more suitable for Inline use.

Sometimes I call X3DJSONLD the JSONParser.  This is similar to an XML DOM
parser.  DOM parsers produce DOM from XML.  My JSONParser produces DOM
documents from JavaScript from JSON.  The last part is done by regular JSON
parsers.

JSONParser.js is found in X_ITE and X3DOM, and is renamed and adapted from
X3DJSONLD.js

John

On Thu, Jan 12, 2023 at 10:46 AM John Carlson <yottzumm at gmail.com> wrote:

>
>
> On Thu, Jan 12, 2023 at 10:00 AM Brutzman, Donald (Don) (CIV) <
> brutzman at nps.edu> wrote:
>
>>
>>    1. Take a look at our X3D Node Inventory Comparison, lets prepare to
>>    regularly update.
>>
>>
>>
>>    - X3D Specifications: Schema and DOCTYPE Validation
>>    - https://www.web3d.org/specifications
>>    - These assets are commonly used for XML validation of X3D scenes,
>>    and in-depth documentation is also provided here.
>>
>>
>>
>>    - X3D Node Inventory Comparison (.pdf) shows node-by-node
>>    implementation coverage of the X3D Abstract Specification: validation using
>>    X3D Schema, X3D DOCTYPE, and X3D Schematron; X3D Tooltips and VRML97 node
>>    sets; plus selected open-source implementations: FreeWrl, X3DOM, X_ITE,
>>    view3dscene (Castle Game Engine), X3D-Edit, Xj3D.
>>    - https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf
>>
>>
> "Can John Carlson's open-source X3DJSONLD be regularized to match
> JavaScript SAI standard?"
>
> There are 2 parts in X3DJSONLD.  The loader, which requires modifications
> to SAI to support JSON scene loading.  This has been accomplished in X3DOM
> and X_ITE. but no one has stepped forward for standardization of this.
> Something like importDoc, importJSON, createX3DfromJSON might be
> appropriate. Andreas and I have worked on X3DOM to add more standard
> functions to the runtime.  I trust that once the standard is created, I or
> Holger will modify X_ITE to follow standard SAI for JSON loading. There is
> no issue with just specifying an X3D JSON file in an Inline right now, and
> is probably preferred over the SAI functionality.
>
> The other part is the JavaScript app files, which now align with X3DJSAIL
> using a buggy Node.js->Java FFI. found on npm.  Other solutions (Nashorn)
> worked well in the past. I am not sure why we aren't pursuing those.
>
> If we want a JavaScript SAI standard implementation, perhaps we should
> modify X3DOM or X_ITE?  What's the attraction of a 3rd JavaScript SAI
> implementation?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230113/4dfa6d88/attachment.html>