[x3d-public] Action Needed: Need for acceptableStatements (ortypes)forchildren fields in X3DObject Model

[John Carlson]

Heh, here we are.  I ran my JSON schema minus the X3DChildNode info against my local files, which I believe most pass Roy’s schema.   Attached are the schema errors.  I will put the schema into a source code repository, here: https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/schema/x3d-5.1-JSONSchema.json .  The rejecting of non- at USE properties and the missing of the @USE property is typical, and is exemplified by the Group schema below. I don’t know if Roy tried correcting my code already or not, but someone (Roy?) correcting this Group would be useful for me.  I believe it’s something to do with additionalProperties, which I can remove, but were would I put it back?

If you like I will start running the schema against X3D Resource Examples, but I’m sure similar errors will crop up.

The ProtoDeclare and ROUTE issues are because those statements are not X3DChildNodes in my hierarchy, I believe, so thus are only used in hardcoded schema.  I can hardcode the required statements into my schema generator, but would that be ideal?  How do I find out that the 5-6 statements previously mentioned are X3DChildNodes in OM4X3D?  I really would like it in the definition of the statement.  Thanks!

John

Group is currently defined as:

    "Group": {
      "type": "object",
      "oneOf": [
        {
          "type": "object",
          "properties": {
            "@USE": {
              "type": "string"
            }
          },
          "required": [
            "@USE"
          ],
          "additionalProperties": false
        },
        {
          "type": "object",
          "properties": {
            "IS": {
              "$ref": "#/definitions/IS"
            },
            "@bboxCenter": {
              "type": "array",
              "minItems": 3,
              "maxItems": 3,
              "items": {
                "default": 0,
                "type": "number"
              }
            },
            "@bboxSize": {
              "type": "array",
              "minItems": 3,
              "maxItems": 3,
              "items": {
                "default": -1,
                "type": "number"
              }
            },
            "-children": {
              "$ref": "#/definitions/-X3DChildNodeMFNode"
            },
            "-metadata": {
              "$ref": "#/definitions/-X3DMetadataObjectSFNode"
            },
            "@DEF": {
              "type": "string"
            },
            "@class": {
              "type": "string"
            }
          },
          "additionalProperties": false
        }
      ]
    },



Sent from Mail for Windows 10

From: Don Brutzman
Sent: Saturday, July 29, 2017 9:53 PM
To: John Carlson; Roy Walmsley
Cc: X3D Graphics public mailing list
Subject: Re: Action Needed: Need for acceptableStatements (ortypes)forchildren fields in X3DObject Model

On 7/29/2017 6:42 PM, John Carlson wrote:
> I also question whether all ConcreteNodes should be X3DChildNodes.  I doubt it.  What do you think?

no

> If I take it out, what will break?  Frankly, I just threw X3DChildNode in there hoping it would fix something that was broken.  A more principled approach would be better—get the whole inheritance hierarchy into OM4X3D.
> 
> I will soon remove all references to X3DChildNode in my code and continue testing.  We will see what happens.
> 
> John
I'll be surprised if you find something broken... the X3DJSAIL adaptation of has been tested on the entire X3D Examples Archive.

Authoritative reference throughout: X3D Abstract Spec.

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 http://faculty.nps.edu/brutzman

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170729/a4dff99f/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: jsonschemaerrors.txt
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170729/a4dff99f/attachment-0001.txt>