Extensible 3D (X3D) encodings
Part 1: Extensible Markup Language (XML) encoding

7 Encoding of statements

(NOTE this is an autogenerated page, produced using X3D XML Schema version 4.0)

--- X3D separator bar ---

cube 7.1  Introduction

7.1.1  Topics

This clause provides a detailed specification of the XML encoding for each structure statement defined in ISO/IEC 19775-1 X3D Architecture. The topics in this clause are listed in Table 7.1.

Table 7.1 — Topics in this clause

7.1 Introduction
  7.1.1 Topics
  7.1.2 XML encoding description

7.2 Statements
  7.2.1 component
  7.2.2 connect
  7.2.3 EXPORT
  7.2.4 ExternProtoDeclare
  7.2.5 field
  7.2.6 fieldValue
  7.2.7 head
  7.2.8 IMPORT
  7.2.9 IS
  7.2.10 meta
  7.2.11 ProtoBody
  7.2.12 ProtoDeclare
  7.2.13 ProtoInterface
  7.2.14 ROUTE
  7.2.15 Scene
  7.2.16 unit
  7.2.17 X3D

7.1.2  XML encoding description

This XML encoding is autogenerated using the XML Schema for the Extensible 3D (X3D) Graphics Specification tagset defined in Annex B Version 4. Schema.

The well-formed syntax of an XML file is governed by the Extensible Markup Language (XML).

X3D nodes and statements are represented by XML elements. Content models indicate the node and statement elements that can be contained by a given statement element. The validity of these parent-child element relationships can be checked using the X3D DTD and X3D XML Schema.

Simple-type X3D fields (meaning other than SFNode and MFNode) are represented by XML attributes. Field values can be validated with progressive degrees of precision and strictness using X3D DTD, X3D XML Schema, X3D Schematron, and X3D Regular Expressions (regexes).

Content models indicate the nodes or statements that can be contained by the given statement.

Notational conventions for this section are as follows.

  1. Each statement name is followed by a list of attributes (if any).
  2. Each attribute name is followed by the default value (if any) and type.
  3. After attributes, the content model (if any) is listed.
  4. Singleton tags or open/close tag pairs are used to complete each element, as appropriate.

NOTE 1  Type designations shown for each statement in this section are solely informational, and are not part of the valid XML encoding for an X3D scene.

Default attribute values and empty attributes are optional.

NOTE 2  Precise ordering is necessary for <IS><connect/></IS> connections, which are only allowed inside a ProtoDeclare body, and placed are defined prior to any contained nodes.

Note  Additional information about X3D XML scene structure, allowed field values, data type restrictions, authoring hints, warnings, and errors can be found in X3D Tooltips X3DTOOLTIPS and X3D Unified Object Model X3DUOM. Validation assets are maintained in human-readable and machine-readable forms, in version control, and with corresponding documentation at X3DVALIDATION.

--- X3D separator bar ---

cube7.2  Statements

Notational conventions for this section are as follows.

  1. Each statement name is followed by a list of attributes (if any).
  2. Each attribute name is followed by the default value (if any) and type.
  3. After attributes, the content model (if any) is listed.
  4. Singleton tags or open/close tag pairs are used to complete each element, as appropriate.

NOTE 1  Type designations shown for each statement in this section are solely informational, and are not part of the valid XML encoding for an X3D scene.

7.2.1  component

Statement, attributes, default values Type
<component  
id="" 
level="" 
name="" 
style="" 
class=""  />
NMTOKEN 
SFInt32 
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.2  connect

Statement, attributes, default values Type
<connect  
id="" 
nodeField="" 
protoField="" 
style="" 
class=""  />
NMTOKEN 
NMTOKEN 
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.3  EXPORT

Statement, attributes, default values Type
<EXPORT  
AS="" 
id="" 
localDEF="" 
style="" 
class=""  />
NMTOKEN 
NMTOKEN 
IDREF 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.4  ExternProtoDeclare

Statement, attributes, default values, content model Type
<ExternProtoDeclare  
appinfo="" 
documentation="" 
id="" 
name="" 
style="" 
url=' ' 
class=""  >
   <field />
</ExternProtoDeclare>
SFString 
SFString 
NMTOKEN 
NMTOKEN 
SFString 
MFString 
NMTOKENS 

--- X3D separator bar ---

7.2.5  field

Statement, attributes, default values, content model Type
<field  
accessType="" 
appinfo="" 
documentation="" 
id="" 
name="" 
style="" 
type="" 
value="" 
class=""  >
   <!-- SceneGraphFragmentContentModel -->
</field>
NMTOKEN 
SFString 
SFString 
NMTOKEN 
NMTOKEN 
SFString 
SFString 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.6  fieldValue

Statement, attributes, default values, content model Type
<fieldValue  
id="" 
name="" 
style="" 
value="" 
class=""  >
   <!-- SceneGraphFragmentContentModel -->
</fieldValue>
NMTOKEN 
NMTOKEN 
SFString 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.7  head

Statement, attributes, default values, content model Type
<head  
id="" 
style="" 
class=""  >
   <component />
   <unit />
   <meta />
</head>
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.8  IMPORT

Statement, attributes, default values Type
<IMPORT  
AS="" 
id="" 
importedDEF="" 
inlineDEF="" 
style="" 
class=""  />
ID 
NMTOKEN 
NMTOKEN 
IDREF 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.9  IS

Statement, attributes, default values, content model Type
<IS  
id="" 
style="" 
class=""  >
   <connect />
</IS>
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.10  meta

Statement, attributes, default values Type
<meta  
content="" 
dir="" 
http-equiv="" 
id="" 
lang="" 
name="" 
scheme="" 
style="" 
class=""  />
SFString 
NMTOKEN 
SFString 
NMTOKEN 
SFString 
SFString 
SFString 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.11  ProtoBody

Statement, attributes, default values, content model Type
<ProtoBody  
id="" 
style="" 
class=""  >
   <LayerSet />
   <!-- SceneGraphFragmentWithPrototypeDeclarationsContentModel -->
</ProtoBody>
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.12  ProtoDeclare

Statement, attributes, default values, content model Type
<ProtoDeclare  
appinfo="" 
documentation="" 
id="" 
name="" 
style="" 
class=""  >
   <ProtoInterface />
   <ProtoBody />
</ProtoDeclare>
SFString 
SFString 
NMTOKEN 
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.13  ProtoInterface

Statement, attributes, default values, content model Type
<ProtoInterface  
id="" 
style="" 
class=""  >
   <field />
</ProtoInterface>
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.14  ROUTE

Statement, attributes, default values Type
<ROUTE  
fromField="" 
fromNode="" 
id="" 
style="" 
toField="" 
toNode="" 
class=""  />
NMTOKEN 
IDREF 
NMTOKEN 
SFString 
NMTOKEN 
IDREF 
NMTOKENS 

--- X3D separator bar ---

7.2.15  Scene

Statement, attributes, default values, content model Type
<Scene  
id="" 
style="" 
class=""  >
   <LayerSet />
   <!-- ChildContentModelCore -->
   <!-- GroupingNodeChildContentModel -->
</Scene>
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.16  unit

Statement, attributes, default values Type
<unit  
category="" 
conversionFactor="" 
id="" 
name="" 
style="" 
class=""  />
NMTOKEN 
SFDouble 
NMTOKEN 
NMTOKEN 
SFString 
NMTOKENS 

--- X3D separator bar ---

7.2.17  X3D

Statement, attributes, default values, content model Type
<X3D  
id="" 
profile="" 
style="" 
version="" 
class=""  >
   <head />
   <Scene />
   <ds:Signature />
</X3D>
NMTOKEN 
NMTOKEN 
SFString 
NMTOKEN 
NMTOKENS 

--- X3D separator bar ---