[x3d-public] X3D JSON Schema Updates

[John Carlson]

The only differences between the draft06 and draft07 X3D JSON schema is the following diff:

$ diff x3d-3.3-JSONSchema.json ~/x3droundtrip/
2c2
<       "$schema": "http://json-schema.org/draft-06/schema#",
---
>       "$schema": "http://json-schema.org/draft-07/schema#",


So it should be simple to bring up to draft-07.

I will file a specification comment. Done.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Sunday, April 15, 2018 2:59 AM
To: Don Brutzman; x3d-public at web3d.org; X3D Graphics member mailing list; npolys at vt.edu
Subject: RE: X3D JSON Schema Updates

Don’s comments are in green, mine are varied colored.

Sorry for the early send.

John

Sent from Mail for Windows 10

From: Don Brutzman
3. *Next Steps.*

Just prior to this task, I have separately added some minimum-allowed values to X3D XML Schema constraints on various SFTime duration fields.  They are all tested in X3DJSAIL satisfactorily. Hoping you can inspect them.  If agreed, please apply them to the JSON schema.

                https://sourceforge.net/p/x3d/code/26640/#diff-4

Checking 3.3 standard:
X3DSoundSourceNode
duration_changed
Minimum Inclusive: -1

Not present in standard:
https://www.web3d.org/files/specifications/19775-1/V3.3/Part01/components/sound.html#X3DSoundSourceNode

Note:  This is the only -1 minimum in the schema for these patches, correct?


X3DTimeDependentNode
elapsedTime
Minimum Inclusive: 0
timestamp
Minimum Inclusive: 0
cycleInterval
Minimum Inclusive: 0
readInterval
Minimum Inclusive: 0
writeInterval
Minimum Inclusive: 0

Not present in standard:
https://www.web3d.org/files/specifications/19775-1/V3.3/Part01/components/time.html#X3DTimeDependentNode


TimeSensor
cycleTime
Minimum Inclusive: 0
time
Minimum Inclusive: 0

Minimums not included in standard:
https://www.web3d.org/files/specifications/19775-1/V3.3/Part01/components/time.html#TimeSensor



X3DNetworkSensorNode
readInterval
Minimum Inclusive: 0
writeInterval
Minimum Inclusive: 0
timestamp
Minimum Inclusive: 0
disableTime
Minimum Inclusive: 0

None of these are present in
https://www.web3d.org/files/specifications/19775-1/V3.3/Part01/components/networking.html#X3DNetworkSensorNode


I don’t know enough about the standard to show whether these are proper additions or not. You say separately, but I thought this was a group thing.  Can you show me the Mantis issues where we are adding these, so I have a better idea of what I am concurring to?

Normally, I copy the 3.3 JSON schema to 3.0, 3.1, 3.2 and 4.0, so that will be what I do.  If this is drastically different than previous schemas for those versions, let me know.  I don’t know what I’ll do, but at least I’ll know.

I think it’s best to autogenerate these schema fields as snippets from the X3DUOM and upgrade the JSON schema by using autogenerated snippets.    It appears according to the standard that many of these fields are new ones. Plus snippets are less error prone.   So let’s get them into the object model soon.

On 4/11/2018 7:38 AM, John Carlson wrote:
> to this mantis:
> 
> http://www.web3d.org/member-only/mantis/view.php?id=1227

I have updated that specification-draft editor issue and assigned it to me.  Will test further before updating draft X3D JSON specification in github.

(As noted earlier, it is better to submit spec changes via the spec comment form, since some muttered incantations are involved).

Wondering, should we immediately try for draft-07?  Or do you think that the differences are minuscule because they've only just started that version?

I think we only have to change the referenced metaschema for draft-07.  The draft-07 schema is at the normal link (which would require a one character change), but I don’t know if that’s the official URL.  I believe references to schemas will vary drastically with draft-08 if it ever comes out, or they may continue to offer a compatible single point of reference.   I think we should go with the one character change, and upgrade to draft-08 once we have the autogenerated schema.

John



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180415/25ad65bd/attachment-0001.html>