[x3d-public] X3DBoundedObject always X3DChildNode ?

[Andreas Plesch]

Nodes which implement X3DBoundedObject also implement X3DChildNode,
except for one node:
https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#f-Objecthierarchy

Ignoring for second the exception, I think that means there is a
opportunity for simplification of the hierarchy by requiring
X3DBoundedObject to implement X3DChildNode.

The exception is X3DNBodyCollisionSpaceNode (X3DBoundedObject)* -+-
CollisionSpace .

It seems curious that CollisionSpace is special. Could CollisionSpace
become a X3DChildNode ? It seems carefully defined not to be able to
participate in a Grouping but why ?

Refs:

https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#f-Objecthierarchy
https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#CollisionSpace


-- 
Andreas Plesch
Waltham, MA 02453