[x3d-public] Action Needed: Need for acceptableStatements (or types) forchildrenfields in X3DObject Model

[John Carlson]

I see that acceptableNodeTypes already contains some Statements (near the bottom of the object model)?   Clarify?

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Thursday, July 20, 2017 1:58 PM
To: Don Brutzman; Roy Walmsley; list
Subject: RE: Action Needed: Need for acceptableStatements (or types) forchildrenfields in X3DObject Model

Suggest combining acceptableNodeTypes and acceptableStatements into acceptableElementTypes.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Thursday, July 20, 2017 1:22 PM
To: Don Brutzman; Roy Walmsley; list
Subject: Action Needed: Need for acceptableStatements (or types) for childrenfields in X3DObject Model

Sorry for the repeat, mailed to Don’s wrong address:

I believe we need acceptableStatements to restrict acceptable statements for children fields in the X3D Object Model.  If it’s ProtoInstance we have a acceptable statements which are comments. If no children field is found, then we have -commentRoute in JSON schema (temporarily now -childrenStatements). However if there are children, there’s no way to specify which statements are allowed. Previously, I tacked X3DChildNode above the statement inheritance hierarchy in my schema generator, which was wrong.

Do we need to extend this extra children field to other nodes so they can accept statements? And then just don’t support any acceptableNodeTypes for those children?

Can we separate nodes and statements into separate children arrays in X3DJSON?

Things to think about.

John




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170720/f5527a07/attachment.html>