[x3d-public] Support for both JSON string and JSON array for NavigationInfo @type

[John Carlson]

I have added an alternate encoding for NavigationInfo at type to the X3D JSON
Schema:

The essential parts are below.

This will allow @type to be coded either as a string, like XML MFString, or
as an array.  This will allow @type to be specified like other MFStrings,
like @justify.

See https://www.web3d.org/x3d/stylesheets/X3dToJson.html

(this is in just one of 3 schemas for NavigationInfo.  The other specifies
a JSON string.).

+            "@type": {
+              "$comment": "MFString inputOutput",
+              "type": "array",
+              "items": {
+                "anyOf": [
+                  {
+                    "enum": [
+                     "ANY",
+                     "WALK",
+                     "EXAMINE",
+                     "FLY",
+                      "LOOKAT",
+                     "NONE",
+                     "EXPLORE"
+                    ]
+                  },
+                  {
+                    "type": "string"
+                  }
+                ],
+                "default": [ "EXAMINE", "ANY" ],
+                "type": "string"
+              }
+            },
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230824/e7717a30/attachment.html>