<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>I have added an alternate encoding for NavigationInfo@type to the X3D JSON Schema:</div><div><br></div><div>The essential parts are below.</div><div><br></div><div>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 <a class="gmail_plusreply" id="plusReplyChip-2">@justify.</a></div><div><br></div><div> See <a href="https://www.web3d.org/x3d/stylesheets/X3dToJson.html">https://www.web3d.org/x3d/stylesheets/X3dToJson.html</a></div><div><br></div><div>(this is in just one of 3 schemas for NavigationInfo. The other specifies a JSON string.).</div><div><br></div><div>+      "@type": {</div><div>+       "$comment": "MFString inputOutput",</div><div>+       "type": "array",</div><div>+       "items": {</div><div>+        "anyOf": [</div><div>+         {</div><div>+          "enum": [</div><div>+           "ANY",</div><div>+           "WALK",</div><div>+           "EXAMINE",</div><div>+           "FLY",</div><div>+           "LOOKAT",</div><div>+           "NONE",</div><div>+           "EXPLORE"</div><div>+          ]</div><div>+         },</div><div>+         {</div><div>+          "type": "string"</div><div>+         }</div><div>+        ],</div><div>+        "default": [ "EXAMINE", "ANY" ],</div><div>+        "type": "string"</div><div>+       }</div><div>+      },</div></div></div></div>