<div dir="ltr"><div dir="ltr">Current X3D JSON schema is here: <a href="https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/schema/x3d-4.0-JSONSchema.json">X3DJSONLD/src/main/schema/x3d-4.0-JSONSchema.json at master · coderextreme/X3DJSONLD (github.com)</a></div><div dir="ltr"><br></div><div>Enjoy!</div><div><br></div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 24, 2023 at 9:16 AM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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="m_-3642935975724894771plusReplyChip-2">@justify.</a></div><div><br></div><div> See <a href="https://www.web3d.org/x3d/stylesheets/X3dToJson.html" target="_blank">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>
</blockquote></div>