Skinned animation using the Skin node

IndexedFaceSet {
  coord Coordinate {
    point [
      0 0 0 # 1st vertex
      1 0 0 # 2nd vertex
      1 1 0 # 3rd vertex
    ]
  }
  coordIndex [ 0 1 2 ] # make a triangle
  skinJoints0  [
    0 1 0 0 # 1st vertex is affected by joints 0, 1 (rest has 0 weights in skinWeights0)
    1 2 3 4 # 2nd vertex is affected by joints 1 2 3 4
    5 0 0 0 # 3rd vertex is affected by joint 5 (rest has 0 weights in skinWeights0)
  ]
  skinWeights0 [
    0.5 0.5 0 0 # 1st vertex is affected 50% by joint 0, 50% by joint 1
    0.2 0.3 0.4 0.1 # 2nd vertex is affected 20% by joint 1, 30% by joint 2, 40% by joint 3, 10% by joint 4
    1 0 0 0 # 3rd vertex is affected 100% by joint 5
  ]
}

Skin {
    # Shapes that are affected by the skinned animation.
    # They are displayed as part of displaying the Skin node.
    # Note that this list can only contain Shape nodes, not more
    # complicated compositions like transformations of them.
    shapes [
        DEF SkinnedMeshShape1 Shape {
            geometry IndexedFaceSet {
                ...
                skinWeights0 ...
                skinJoints0  ...
            }
        }
        DEF SkinnedMeshShape2 Shape {
            geometry IndexedFaceSet {
                ...
                skinWeights0 ...
                skinJoints0  ...
            }
        }
    ]

    # Joints hierarchy, starting from root node.
    #
    # Note: The hierarchy below is *just a trivial example*,
    # not a proper example of how joints for a typical humanoid
    # look like. Follow H-Anim conventions for joints to define
    # typical humanoid joints hierarchy.
    #
    # Any X3D node graph is allowed here, in particular:
    #
    # - You can also specify Shape nodes within the transformations here.
    #   Such Shape nodes will be just rigid 3D shapes attached to
    #   the joints (like a sword may be attached to the avatar's hand).
    #   Contrast this with shapes that are affected by the skin mechanism,
    #   which are listed in the "shapes" field.
    #
    # - The root node (skeleton) doesn't have to be a Transform,
    #   it can be any X3DGroupingNode (TAbstractGroupingNode for Pascal) node,
    #   so a simple Group is also OK.
    #   Though remember that if it's not Transform, you cannot list it later in
    #   "joints" field, so it cannot be a joint that affects the skin.
    #
    # The Shape(s) that should be affected by the skin mechanism
    # (modified by joints) should *not* be listed here, they should
    # be placed only in the Skin.shapes field.
    skeleton DEF RootJoint Transform {
        children [
            DEF Body Transform {
                children [
                    DEF LeftThigh Transform {
                        children [
                            DEF LeftShin Transform {
                                children [
                                    DEF LeftFoot Transform {
                                    }
                                ]
                            }
                        ]
                    }
                    DEF RightThigh Transform {
                        children [
                            DEF RightShin Transform {
                                children [
                                    DEF RightFoot Transform {
                                    }
                                ]
                            }
                        ]
                    }
                ]
            }
        ]
    }

    # List of joints.
    # This is a list of all the joints that control the shapes
    # in the "shapes" list.
    #
    # If a human writes the X3D content,
    # we suggest placing all the joints in "skeleton" hierarchy,
    # with names (DEF). Then in the "joints" field just list them with "USE".
    # This is easier to read and write for humans.
    #
    # That said, following X3D, it is possible to write using any order,
    # as long as each USE is after a corresponding DEF.
    # So you can also start by writing
    # joints in "joints" list, only interlinking to previous joints by USE,
    # and then define the "skeleton" hierarchy by a USE to the root joint.
    # For software, this is equally easy to write and later read, so not a problem.
    # For humans, it will likely look more complicated.
    #
    # The order of joints here matters:
    # joint indexes specified in the skinJoints0 array
    # refer to the position of joint on this list.
    #
    # All the joints listed here must also be part of the "skeleton"
    # hierarchy.
    # However, not *all* transformation nodes (Transform) from the "skeleton"
    # need to be listed here and considered "joints". You only need to list
    # the joints that actually affect some vertex in some some shape,
    # to be able to refer to this joint from skinJoints0 array.
    # If a joint is merely a parent for other joints but doesn't *directly*
    # influence any vertex, there's no need to list it here.
    joints [
        USE RootJoint
        USE Body
        USE LeftThigh
        USE LeftShin
        USE LeftFoot
        USE RightThigh
        USE RightShin
        USE RightFoot
    ]
}