[x3d-public] X3D JSON Schema updated for axis++ defaults
John Carlson
yottzumm at gmail.com
Mon Feb 7 22:31:59 PST 2022
This one looks like a good test for X3dToJson.xslt to produce a validatable
JSON. So far, the JSON is failing my tests.
https://www.web3d.org/x3d/content/examples/Basic/StudentProjects/TrebuchetIndex.html
I suggest doing a validation with XMLSpy of the X3D JSON file to test the
X3D JSON schema's power.
On Mon, Feb 7, 2022 at 11:52 PM John Carlson <yottzumm at gmail.com> wrote:
> Comment validation removed. Did not find any examples. Please test.
>
> Thanks!
>
> John
>
> On Mon, Feb 7, 2022 at 11:16 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> Can we put this and any outstanding JSON schema modifications on the
>> agenda for next week?
>>
>>>
>>>
>>> 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
>>>
>>> },
>>>
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220208/decfa5bd/attachment-0001.html>
More information about the x3d-public
mailing list