Difference between revisions of "BallJoint"

From Web3D.org
Jump to: navigation, search
Line 24: Line 24:
 
# A single, optional IS.
 
# A single, optional IS.
 
# A single, optional node derived from X3DMetadataObject for the ''metadata'' field.
 
# A single, optional node derived from X3DMetadataObject for the ''metadata'' field.
# Any number of RigidBody or Prototype nodes in any order.
+
# Any number of [[RigidBody]] or Prototype nodes in any order.
  
 
===Attributes===
 
===Attributes===
Line 38: Line 38:
 
# A single, optional IS.
 
# A single, optional IS.
 
# A single, optional node derived from X3DMetadataObject for the ''metadata'' field.
 
# A single, optional node derived from X3DMetadataObject for the ''metadata'' field.
# A maximum of two additional children, which may be either RigidBody or Prototype nodes in any order.
+
# A maximum of two additional children, which may be either [[RigidBody]] or Prototype nodes in any order.
  
 
===Attributes===
 
===Attributes===

Revision as of 13:54, 23 April 2015

Background

Specification Link: BallJoint

BallJoint : X3DRigidJointNode {
  SFVec3f  [in,out] anchorPoint      0 0 0  (-∞,∞)
  SFNode   [in,out] body1            []     [RigidBody]
  SFNode   [in,out] body2            []     [RigidBody]
  MFString [in,out] forceOutput      "NONE" ["ALL", "NONE", ...]
  SFNode   [in,out] metadata         NULL   [X3DMetadataObject]
  SFVec3f  [out]    body1AnchorPoint []
  SFVec3f  [out]    body2AnchorPoint []
}

DTD Validation

Children

Children must appear as follows:

  1. A single, optional IS.
  2. A single, optional node derived from X3DMetadataObject for the metadata field.
  3. Any number of RigidBody or Prototype nodes in any order.

Attributes

  • There is no check that the values in the forceOutput field are acceptable.

Schema Validation

Children

Children must appear as follows:

  1. A single, optional IS.
  2. A single, optional node derived from X3DMetadataObject for the metadata field.
  3. A maximum of two additional children, which may be either RigidBody or Prototype nodes in any order.

Attributes

  • There is no check that the values in the forceOutput field are acceptable.


Schematron validation

TBD