[x3d-public] X3DBoundedObject always X3DChildNode ?

Andreas Plesch andreasplesch at gmail.com
Mon Feb 17 10:10:57 PST 2020

Nodes which implement X3DBoundedObject also implement X3DChildNode,
except for one node:

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 ?



Andreas Plesch
Waltham, MA 02453

More information about the x3d-public mailing list