[x3d-public] x3d-3.3-JSONSchema documentation available

[Yves Piguet]

Thanks, Roy.

> On 6 Dec 2016, at 11:39, Roy Walmsley <roy.walmsley at ntlworld.com> wrote:
>  
> 3)      Use of the distinct prefixes “@” and “-“: I’ll let Don answer this one more fully. However, below is the section from the draft standard (which is at the stage where we are working to get approval for release to the public for review – see also comment 5)) which covers this important point :

I'm not sure to understand why the distinction is important. Which ambiguity would there be with a single prefix, e.g. "@" also used for SFNode and MFNode? I understand that for a translator from json to xml encoding which doesn't understand x3d, it would be a problem; but imo it isn't a sufficient reason.

> 4)      Rationale for use of prefix “@”: We tried to keep the prefix for use on fields, or properties of “statements” that are like fields. “Statements” do not get a prefix.

Since there are already unprefixed names for other parts of the json encoding, I'd rather reserve prefixes to x3d node field names. The type of "@protoField" is likely an Id, not an sfstringValue (see http://www.web3d.org/documents/specifications/19776-2/V3.3/index.html )...

> 5)      Access to draft standard: Sorry, but the draft standard is currently only available to members. This is a requirement of the Consortium bylaws which arises because of possible IPR issues (it applies to all new drafts). There are procedures for making it public. It is hoped to do that soon.

I understand. It's just that not all subscribers to x3d-public can fully benefit from links sent by Don. No problem.

Best,

Yves