These examples are used in the X3D Specifications to illustrate correct X3D usage and capabilities.

The X3D Abstract Specification authoritatively defines the functionality of X3D scenes. It specifically describes how geometry rendering and user interaction can be accomplished on any 3D device. Multiple file encodings (.x3d, .x3dv, .x3db) and multiple language bindings (ECMAScript .js, Java .java) can equivalently represent an X3D scene. These examples support five different X3D specifications:

• XML encoding (.x3d file extension) scenes found in the XML encoding examples.
• Classic VRML encoding (.x3dv file extension). Autogenerated examples matching the master .x3d model can be compared favorably to the Classic VRML encoding examples.
• Compressed Binary Encoding (CBE) (.x3db file extension). Autogenerated examples matching the master .x3d model can be compared favorably to the Binary encoding examples.
• ECMAScript Scene Access Interface (SAI) scenes and source (.js file extension) are provided that match the X3D ECMAScript language binding examples.
  TODO, transcription work in progress.
• Java Scene Access Interface (SAI) scenes and source (.java file extension) are provided that match the X3D Java language binding examples.
  TODO, testing in progress.