[x3d-public] X3D JSON Schema updated for axis++ defaults

[John Carlson]

Then there was the Monty Python Trebuchet:
https://www.youtube.com/watch?v=JQ8jGqdE2iw

Good for a few laughs.

On Wed, Feb 9, 2022 at 10:16 PM John Carlson <yottzumm at gmail.com> wrote:

>
> https://www.web3d.org/x3d/content/examples/Basic/StudentProjects/TrebuchetIndex.html
>
> Please provide validatable JSON (Trebuchet.json) from the above website.
> Thanks!
>
> (throwing 3 darts in hopes of hitting a bullseye--or at least 3 triple
> 20's).
>
> Note that schema updates have been applied.
>
> Updated JSON validator here:
> http://coderextreme.net/X3DJSONLD/src/main/html/validator.html
>
> I suggest grabbing the X3D JSON schema from here:
>
>
> https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/schema/x3d-4.0-JSONSchema.json
>
>
> and testing Trebuchet.json as downloaded from the first link with XMLSpy.
>
> Then reconsider the request in your original message on this thread.
>
> We probably already discussed this exact thing quite some time ago.
> Luckily we have a good email thread to go back to should this discussion
> arise again.
>
> John
>
> On Tue, Feb 8, 2022 at 12:31 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> 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/20220209/3e429631/attachment.html>