[x3d-public] X3D JSON Schema updated for axis++ defaults

[Brutzman, Donald (Don) (CIV)]

John, I can replace the schema in the official repository, but we still have
a severe difficulty in that there is no build process to check it against
X3D Examples scenes.  As ever, using Java latest and Ant build tasks will be
the path to mainstreaming.  We have been blocked by that for several years,
and JSON Schema is still in draft status.

 

Don't want to sound discouraging, seems like you are close, but these are
the final hurdles to get past.

 

Recent update found on json schema page indicates that they are still draft
and still progressing.

 

*	http://json-schema.org

 

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: Wednesday, February 9, 2022 10:43 PM
To: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>; X3D Graphics public
mailing list <x3d-public at web3d.org>
Subject: Re: [x3d-public] X3D JSON Schema updated for axis++ defaults

 

NPS WARNING: *external sender* verify before acting.

 

See attached JSON schema to get #comment next to USE (practically everywhere
in the schema).  Shortened versions of the schema welcome.  I'm not quite
sure what to do. 

 

This adds about 3660 lines to the schema.

 

If you can suggest a better JSON encoding or X3D JSON schema, that would be
welcome at this point.

 

On Thu, Feb 10, 2022 at 12:29 AM John Carlson <yottzumm at gmail.com
<mailto:yottzumm at gmail.com> > wrote:

Please confirm that you want me to accept @USE with sibling -children
fields, as shown in recently mentioned Trebuchet.json.

 

See below snippet of X3D JSON schema, that I will add back in *many* places.
The code to be added is embolden.

 

Thanks!

 

John

 

On Sat, Feb 5, 2022 at 9:06 AM Brutzman, Donald (Don) (CIV)
<brutzman at nps.edu <mailto:brutzman at nps.edu> > wrote:

 

2. Saw a documentation problem:  USE nodes can't indicate anything besides
the @USE value (except for containerField value for relevant parent-child
relationship in XML encoding).  So your following guidance about comments is
not portable outside of JSON.

    "RigidBody": {

      "type": "object",

      "oneOf": [

        {

          "type": "object",

          "properties": {

            "@class": {

              "type": "string"

            },

            "@USE": {

              "type": "string"

            },

            "-children": {

              "type": "array",

              "minItems": 1,

              "items": {

                "type": "object",

                "properties": {

                  "#comment": {

                    "type": "string",

                    "$comment": "#comment statements are the only allowed in
-children node when using a USE field"

                  }

                },

                "additionalProperties": false

              }

            }

         },

          "required": [

            "@USE"

          ],

          "additionalProperties": false

        },

 

 

 

_______________________________________________
x3d-public mailing list
x3d-public at web3d.org <mailto: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/20220216/34ec39bd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5353 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220216/34ec39bd/attachment-0001.p7s>