x_ite 8.8.7 → 8.9.1

package/docs/_posts/components/PointingDeviceSensor/TouchSensor.md

@@ -1,6 +1,6 @@
 ---
 title: TouchSensor
-date: 2022-01-07
+date: 2023-01-07
 nav: components-PointingDeviceSensor
 categories: [components, PointingDeviceSensor]
 tags: [TouchSensor, PointingDeviceSensor]
@@ -15,7 +15,7 @@ tags: [TouchSensor, PointingDeviceSensor]
 
 TouchSensor tracks location and state of the pointing device, detecting when a user points at or selects (activates) geometry.
 
-The TouchSensor node belongs to the **PointingDeviceSensor** component and its default container field is *children.* It is available since X3D version 2.0 or later.
+The TouchSensor node belongs to the **PointingDeviceSensor** component and its default container field is *children.* It is available from X3D version 2.0 or higher.
 
 ## Hierarchy
 
@@ -32,15 +32,20 @@ The TouchSensor node belongs to the **PointingDeviceSensor** component and its d
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFString [in, out] **description** ""
 
-Author-provided text tooltip that tells users the expected action of this node.
+Author-provided prose that describes intended purpose of this node.
 
 #### Hints
 
-- Use spaces, make descriptions clear and readable. Many XML tools substitute XML character references automatically if needed (such as &amp;#38; for &amp; ampersand, or &amp;#34; for " quotation mark).
+- Include space characters since a *description* is not a DEF identifier. Write short phrases that make descriptions clear and readable.
+- Many XML tools substitute XML character references for special characters automatically if needed within an attribute value (such as &amp;#38; for &amp; ampersand character, or &amp;#34; for " quotation-mark character).
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -50,21 +55,41 @@ Enables/disables node operation.
 
 When pointing device selects geometry, send event containing texture coordinates of surface at the hitPoint.
 
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+
 ### SFVec3f [out] **hitNormal_changed**
 
 When pointing device selects geometry, send event containing surface normal vector at the hitPoint.
 
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+
 ### SFVec3f [out] **hitPoint_changed**
 
 When pointing device selects geometry, send event containing 3D point on surface of underlying geometry, as measured in reference frame for TouchSensor's local coordinate system.
 
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+
 ### SFBool [out] **isOver**
 
-Hover over geometry by aiming the mouse (or pointing device) to generate isOver events. Sensor sends output event isOver=true event when pointing device moves over sensor's geometry, and later sends output event isOver=false event when pointing device moves off.
+Hover over geometry by aiming the mouse (or pointing device) to generate *isOver* events. Sensor sends output event *isOver*=true event when pointing device moves over sensor's geometry, and later sends output event *isOver*=false event when pointing device moves off.
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
 ### SFBool [out] **isActive**
 
-Select geometry by activating the pointing device (e.g. clicking the mouse) to generate isActive events. Output event isActive=true is sent when pointing device selection is activated, output event isActive=false is sent when pointing device is deselected.
+Select geometry by activating the pointing device (for example, clicking the mouse) to generate *isActive* events. Output event *isActive*=true is sent when pointing device selection is activated, output event *isActive*=false is sent when pointing device is deselected.
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
 ### SFTime [out] **touchTime**
 
@@ -72,16 +97,25 @@ Time event generated when sensor is touched by pointing device, and then deselec
 
 #### Hint
 
-- TouchTime event is generated when following three conditions are all met: (a) pointing device was pointing towards geometry when initially activated (isActive=true), (b) pointing device is currently pointing towards the geometry (isOver=true), and (c) pointing device selection is deactivated/deselected by user (isActive=false event is also generated).
+- *touchTime* event is generated when following three conditions are all met: (a) pointing device was pointing towards geometry when initially activated (isActive=true), (b) pointing device is currently pointing towards the geometry (isOver=true), and (c) pointing device selection is deactivated/deselected by user (isActive=false event is also generated).
 
-## Description
+#### Warning
 
-### Hint
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+
+## Advisories
+
+### Hints
 
 - This sensor detects user interactions affecting peer nodes and their child geometry.
+- [X3D Architecture 20.2.1 Overview of pointing device sensors](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/pointingDeviceSensor.html#OverviewOfPointingDeviceSensors){:target="_blank"}
+- [X3D Architecture 20.2.3 Activating and manipulating pointing device sensors](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/pointingDeviceSensor.html#Activatingandmanipulating){:target="_blank"}
+- [Example scenes and authoring assets](https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter08UserInteractivity){:target="_blank"}
+
+## Example
+
+<x3d-canvas src="https://create3000.github.io/media/examples/PointingDeviceSensor/TouchSensor/TouchSensor.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of TouchSensor](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#TouchSensor){:target="_blank"}
-- [See X3D Specification 20.2.1 Overview of pointing device sensors](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#OverviewOfPointingDeviceSensors){:target="_blank"}
-- [See X3D Specification 20.2.3 Activating and manipulating pointing device sensors](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#Activatingandmanipulating){:target="_blank"}
+- [X3D Specification of TouchSensor node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#TouchSensor){:target="_blank"}

package/docs/_posts/components/Rendering/ClipPlane.md

@@ -1,6 +1,6 @@
 ---
 title: ClipPlane
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Rendering
 categories: [components, Rendering]
 tags: [ClipPlane, Rendering]
@@ -15,7 +15,7 @@ tags: [ClipPlane, Rendering]
 
 ClipPlane specifies a single plane equation used to clip (i.e. cull or hide) displayed geometry. The plane field specifies a four-component plane equation that describes both inside and outside half space.
 
-The ClipPlane node belongs to the **Rendering** component and its default container field is *children.* It is available since X3D version 3.2 or later.
+The ClipPlane node belongs to the **Rendering** component and its default container field is *children.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -29,7 +29,11 @@ The ClipPlane node belongs to the **Rendering** component and its default contai
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -37,31 +41,32 @@ Enables/disables node operation.
 
 ### SFVec4f [in, out] **plane** 0 1 0 0 <small>[0,1] or (-∞,∞)</small>
 
-If (a,b,c,d) is the plane, with the first three components being a normalized vector describing the plane's normal direction (and thus the fourth component d being distance from the origin), a point (x,y,z) is visible to the user, with regards to the clipping plane, if a\*x+b\*y+c\*z+d is greater than 0.
+If (a,b,c,d) is the *plane*, with the first three components being a normalized vector describing the *plane*'s normal direction (and thus the fourth component d being distance from the origin), a point (x,y,z) is visible to the user, with regards to the clipping *plane*, if a*x+b*y+c*z+d is greater than 0.
 
-#### Hint
+#### Hints
 
-- Negate all plane values to reverse which side of plane has visibility clipped.
+- Negate all *plane* values to reverse which side of *plane* has visibility clipped.
+- [*plane*-geometry equations](https://en.wikipedia.org/wiki/Plane_(geometry)#Point-normal_form_and_general_form_of_the_equation_of_a_plane){:target="_blank"}
+- [*plane*-geometry distance to point](https://en.wikipedia.org/wiki/Plane_(geometry)#Distance_from_a_point_to_a_plane){:target="_blank"}
 
 #### Warning
 
-- (a, b, c) value of (0, 0, 0) is forbidden since the zero vector has ambiguous direction and is thus degenerate, not defining a plane.
+- (a, b, c) value of (0, 0, 0) is forbidden since the zero vector has ambiguous direction and is thus degenerate, not defining a *plane*.
 
-#### See Also
+## Advisories
 
-- [Plane-geometry equations](https://en.wikipedia.org/wiki/Plane_(geometry){:target="_blank"}
-#Point-normal_form_and_general_form_of_the_equation_of_a_plane) [Plane-geometry distance to point](https://en.wikipedia.org/wiki/Plane_(geometry){:target="_blank"}#Distance_from_a_point_to_a_plane)
+### Hint
 
-## Description
+- ClipPlane nodes only affect peer and descendant nodes, thus a parent grouping node can limit its effect.
 
-### Hint
+### Warning
 
-- Include `<component name='Rendering' level='5'/>`
+- [Requires X3D `profile='Full'` or else include `<component name='Rendering' level='5'/>` Examples: X3D Example Archives, Basic, CAD, Clip Plane Example](https://www.web3d.org/x3d/content/examples/Basic/CAD/ClipPlaneExampleIndex.html){:target="_blank"}
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/Rendering/ClipPlane/ClipPlane.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of ClipPlane](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#ClipPlane){:target="_blank"}
+- [X3D Specification of ClipPlane node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#ClipPlane){:target="_blank"}

package/docs/_posts/components/Rendering/Color.md

@@ -1,6 +1,6 @@
 ---
 title: Color
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Rendering
 categories: [components, Rendering]
 tags: [Color, Rendering]
@@ -13,9 +13,9 @@ tags: [Color, Rendering]
 
 ## Overview
 
-Color node defines a set of RGB color values that apply either to a sibling Coordinate/CoordinateDouble node, or else to a parent ElevationGrid node. Color is only used by ElevationGrid, IndexedFaceSet, IndexedLineSet, LineSet, PointSet, Triangle\* and IndexedTriangle\* nodes.
+Color node defines a set of RGB color values that apply either to a sibling Coordinate or CoordinateDouble node, or else to a parent ElevationGrid node. Color is only used by ElevationGrid, IndexedFaceSet, IndexedLineSet, LineSet, PointSet, Triangle* and IndexedTriangle* nodes.
 
-The Color node belongs to the **Rendering** component and its default container field is *color.* It is available since X3D version 2.0 or later.
+The Color node belongs to the **Rendering** component and its default container field is *color.* It is available from X3D version 2.0 or higher.
 
 ## Hierarchy
 
@@ -30,27 +30,27 @@ The Color node belongs to the **Rendering** component and its default container
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### MFColor [in, out] **color** [ ] <small>[0,1]</small>
 
-The color field defines an array of 3-tuple RGB colors.
+The *color* field defines an array of 3-tuple RGB colors.
 
-## Description
+## Advisories
 
-### Hint
+### Hints
 
 - Colors are often controlled by Material instead.
+- [X3D Scene Authoring Hints, Color](https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Color){:target="_blank"}
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/Rendering/Color/Color.x3d" update="auto"></x3d-canvas>
 
-<table class="x3d-widgets"><tbody><tr><td><button class="button" id="reset-colors-button">Reset Colors</button></td><td><select class="select" id="randomize-colors-button"><option value="0">Preserve Positions</option><option value="1">Move Colors To Left Side</option><option value="2">Move Colors To Right Side</option><option selected="selected" value="3">Randomize Colors</option></select></td></tr></tbody></table>
+## See Also
 
-- [/c3-source-example]
-
-## External Links
-
-- [X3D Specification of Color](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#Color){:target="_blank"}
-- [X3D Scene Authoring Hints, Color](https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Color){:target="_blank"}
+- [X3D Specification of Color node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#Color){:target="_blank"}

package/docs/_posts/components/Rendering/ColorRGBA.md

@@ -1,6 +1,6 @@
 ---
 title: ColorRGBA
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Rendering
 categories: [components, Rendering]
 tags: [ColorRGBA, Rendering]
@@ -13,9 +13,9 @@ tags: [ColorRGBA, Rendering]
 
 ## Overview
 
-ColorRGBA node defines a set of RGBA color values that apply either to a sibling Coordinate/CoordinateDouble node, or else to a parent ElevationGrid node. ColorRGBA is only used by ElevationGrid, IndexedFaceSet, IndexedLineSet, LineSet, PointSet, Triangle\* and IndexedTriangle\* nodes.
+ColorRGBA node defines a set of RGBA color values that apply either to a sibling Coordinate or CoordinateDouble node, or else to a parent ElevationGrid node. ColorRGBA is only used by ElevationGrid, IndexedFaceSet, IndexedLineSet, LineSet, PointSet, Triangle* and IndexedTriangle* nodes.
 
-The ColorRGBA node belongs to the **Rendering** component and its default container field is *color.* It is available since X3D version 3.0 or later.
+The ColorRGBA node belongs to the **Rendering** component and its default container field is *color.* It is available from X3D version 3.0 or higher.
 
 ## Hierarchy
 
@@ -30,22 +30,27 @@ The ColorRGBA node belongs to the **Rendering** component and its default contai
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### MFColorRGBA [in, out] **color** [ ] <small>[0,1]</small>
 
-The color field defines an array of 4-tuple RGBA colors.
+The *color* field defines an array of 4-tuple RGBA colors.
 
 #### Warning
 
 - ColorRGBA requires Rendering component level 3 (alpha fully supported), Rendering component level 1 (alpha optional), otherwise Full profile.
 
-## Description
+## Advisories
 
 ### Hints
 
 - Colors are often controlled by Material instead.
 - Alpha channel may be ignored under Interchange profile.
+- [X3D Scene Authoring Hints, Color](https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Color){:target="_blank"}
 
 ### Warning
 
@@ -55,7 +60,6 @@ The color field defines an array of 4-tuple RGBA colors.
 
 <x3d-canvas src="https://create3000.github.io/media/examples/Rendering/ColorRGBA/ColorRGBA.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of ColorRGBA](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#ColorRGBA){:target="_blank"}
-- [X3D Scene Authoring Hints, Color](https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Color){:target="_blank"}
+- [X3D Specification of ColorRGBA node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#ColorRGBA){:target="_blank"}

package/docs/_posts/components/Rendering/Coordinate.md

@@ -1,6 +1,6 @@
 ---
 title: Coordinate
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Rendering
 categories: [components, Rendering]
 tags: [Coordinate, Rendering]
@@ -13,9 +13,9 @@ tags: [Coordinate, Rendering]
 
 ## Overview
 
-Coordinate builds geometry by defining a set of 3D coordinate triplet values. Coordinate is used by IndexedFaceSet, IndexedLineSet, LineSet, PointSet, Triangle\* and IndexedTriangle\* nodes. Coordinate is also used by HAnimHumanoid, HAnimSegment, and various Nurbs nodes.
+Coordinate builds geometry by defining a set of 3D coordinate (triplet) point values. Coordinate is used by IndexedFaceSet, IndexedLineSet, LineSet, PointSet, Triangle* and IndexedTriangle* nodes. Coordinate is also used by HAnimHumanoid, HAnimSegment, and various Nurbs nodes.
 
-The Coordinate node belongs to the **Rendering** component and its default container field is *coord.* It is available since X3D version 2.0 or later.
+The Coordinate node belongs to the **Rendering** component and its default container field is *coord.* It is available from X3D version 2.0 or higher.
 
 ## Hierarchy
 
@@ -30,16 +30,20 @@ The Coordinate node belongs to the **Rendering** component and its default conta
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### MFVec3f [in, out] **point** [ ] <small>(-∞,∞)</small>
 
-*point* contains a set of 3D coordinate triplet values.
+*point* contains a set of 3D coordinate (triplet) *point* values.
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/Rendering/Coordinate/Coordinate.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of Coordinate](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#Coordinate){:target="_blank"}
+- [X3D Specification of Coordinate node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#Coordinate){:target="_blank"}

package/docs/_posts/components/Rendering/IndexedLineSet.md

@@ -1,6 +1,6 @@
 ---
 title: IndexedLineSet
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Rendering
 categories: [components, Rendering]
 tags: [IndexedLineSet, Rendering]
@@ -13,9 +13,9 @@ tags: [IndexedLineSet, Rendering]
 
 ## Overview
 
-IndexedLineSet is a geometry node that can contain a Coordinate|CoordinateDouble node and an (optional) Color|ColorRGBA node. Color values or a sibling Material emissiveColor is used to draw lines and points. Lines are not lit, are not texture-mapped, and do not participate in collision detection.
+IndexedLineSet defines polyline segments using index lists corresponding to vertex coordinates. IndexedLineSet is a geometry node that can contain a Coordinate or CoordinateDouble node and optionally a Color or ColorRGBA node.
 
-The IndexedLineSet node belongs to the **Rendering** component and its default container field is *geometry.* It is available since X3D version 2.0 or later.
+The IndexedLineSet node belongs to the **Rendering** component and its default container field is *geometry.* It is available from X3D version 2.0 or higher.
 
 ## Hierarchy
 
@@ -29,55 +29,77 @@ The IndexedLineSet node belongs to the **Rendering** component and its default c
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### MFInt32 [in] **set_colorIndex** <small>[0,∞) or -1</small>
 
-*colorIndex* values define the order in which Color|ColorRGBA values are applied to polygons (or vertices).
+*colorIndex* values define the order in which Color or ColorRGBA values are applied to polygons (or vertices).
 
 #### Hints
 
-- If *colorIndex* array is not provided, then Color|ColorRGBA values are indexed according to the coordIndex field.
+- If *colorIndex* array is not provided, then Color or ColorRGBA values are indexed according to the coordIndex field.
 - If colorPerVertex='false' then one index is provided for each polygon defined by the coordIndex array. No sentinel -1 values are included.
-- If colorPerVertex='true' then a matching set of indices is provided, each separated by sentinel -1, that exactly corresponds to individual
+- If colorPerVertex='true' then a matching set of indices is provided, each separated by sentinel -1, that exactly corresponds to individual values in the coordIndex array polygon definitions.
+
+#### Warning
+
+- It is an error to define this transient inputOnly field in an X3D file, instead only use it a destination for ROUTE events.
 
 ### MFInt32 [in] **set_coordIndex** <small>[0,∞) or -1</small>
 
-*coordIndex* indices provide the order in which coordinates are applied to construct each polygon face. Order starts at index 0, commas are optional between sets.
+*coordIndex* indices provide the order in which coordinates are applied to construct each polyline. Order starts at index 0, commas are optional between sets.
 
 #### Hint
 
-- Sentinel value -1 is used to separate indices for each successive polygon.
+- Sentinel value -1 is used to separate indices for each successive polyline.
+
+#### Warning
+
+- It is an error to define this transient inputOnly field in an X3D file, instead only use it a destination for ROUTE events.
 
 ### SFBool [ ] **colorPerVertex** TRUE
 
-Whether Color node color values are applied to each vertex (true) or per polyline (false).
+Whether Color node color values are applied to each point vertex (true) or per polyline (false).
 
-#### See Also
+#### Hint
 
 - [X3D Scene Authoring Hints, Color](https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Color){:target="_blank"}
 
 ### MFInt32 [ ] **colorIndex** [ ] <small>[0,∞) or -1</small>
 
-*colorIndex* values define the order in which Color|ColorRGBA values are applied to polygons (or vertices).
+*colorIndex* values define the order in which Color or ColorRGBA values are applied to polygons (or vertices).
 
 #### Hints
 
-- If *colorIndex* array is not provided, then Color|ColorRGBA values are indexed according to the coordIndex field.
+- If *colorIndex* array is not provided, then Color or ColorRGBA values are indexed according to the coordIndex field.
 - If colorPerVertex='false' then one index is provided for each polygon defined by the coordIndex array. No sentinel -1 values are included.
-- If colorPerVertex='true' then a matching set of indices is provided, each separated by sentinel -1, that exactly corresponds to individual
+- If colorPerVertex='true' then a matching set of indices is provided, each separated by sentinel -1, that exactly corresponds to individual values in the coordIndex array polygon definitions.
+- If rendering Coordinate points originally defined for an IndexedFaceSet, index values may need to repeat initial each initial vertex to close the polygons.
+
+#### Warning
+
+- If child Color or ColorRGBA node is not provided, then geometry is rendered using corresponding Appearance and material/texture values.
 
 ### MFInt32 [ ] **coordIndex** [ ] <small>[0,∞) or -1</small>
 
 *coordIndex* indices provide the order in which coordinates are applied to construct each polygon face. Order starts at index 0, commas are optional between sets, use -1 to separate indices for each polyline.
 
-#### Hint
+#### Hints
 
 - If rendering Coordinate points originally defined for an IndexedFaceSet, index values may need to repeat initial each initial vertex to close the polygons.
+- Sentinel value -1 is used to separate indices for each successive polyline.
+
+#### Warning
+
+- *coordIndex* is required in order to connect contained coordinate point values.
 
 ### MFNode [in, out] **attrib** [ ] <small>[X3DVertexAttributeNode]</small>
 
-Multiple contained FloatVertexAttribute nodes that can specify list of per-vertex attribute information for programmable shaders.
+Single contained FloatVertexAttribute node that can specify list of per-vertex attribute information for programmable shaders.
 
 #### Hint
 
@@ -89,7 +111,7 @@ Single contained FogCoordinate node that can specify depth parameters for fog in
 
 ### SFNode [in, out] **color** NULL <small>[X3DColorNode]</small>
 
-Single contained Color or ColorRGBA node that can specify color values applied to corresponding vertices according to colorIndex and colorPerVertex fields.
+Single contained Color or ColorRGBA node that can specify *color* values applied to corresponding vertices according to colorIndex and colorPerVertex fields.
 
 ### SFNode [in, out] **normal** NULL <small>[X3DNormalNode]</small>
 
@@ -99,24 +121,36 @@ Single contained Normal node that can specify perpendicular vectors for correspo
 
 - Useful for special effects. Normal vector computation by 3D graphics hardware is quite fast so adding normals to a scene is typically unnecessary.
 
+#### Warning
+
+- *normal* vectors increase file size, typically doubling geometry definitions.
+
 ### SFNode [in, out] **coord** NULL <small>[X3DCoordinateNode]</small>
 
 Single contained Coordinate or CoordinateDouble node that can specify a list of vertex values.
 
-## Description
+## Advisories
 
 ### Hints
 
-- Use a different color (or emissiveColor) than the background color.
-- If rendering Coordinate points originally defined for an IndexedFaceSet, index values may need to repeat each initial vertex to close each polygon outline. Step-wise colors or linear interpolation of colors can be used as a good scientific visualization technique to map arbitrary function values to a color map.
+- [Polygonal chain](https://en.wikipedia.org/wiki/Polygonal_chain){:target="_blank"}
+- Either values in a contained Color node, or else Material emissiveColor in corresponding Appearance node, are used for rendering lines and points.
+- Adding LineProperties to the corresponding Appearance node can modify the rendering style of these lines.
+- If rendering Coordinate points originally defined for an IndexedFaceSet, index values may need to repeat each initial vertex to close each polygon outline.
+- Step-wise variation or linear interpolation of color values can be used as a good scientific visualization technique to map arbitrary function values to a color map.
 - Insert a Shape node before adding geometry or Appearance.
-- You can also substitute a type-matched ProtoInstance node for contained content.
-- Consider including Fog to provide further depth cueing for IndexedLineSet (ILS).
+- For advanced extensibility, authors can substitute a type-matched ProtoInstance node (with correct containerField value) for contained node content.
+- Consider including Fog (with Fog color matching Background color) to provide further depth cueing for IndexedLineSet (ILS).
+
+### Warnings
+
+- Lines are not lit, are not texture-mapped, and do not participate in collision detection.
+- Use a different color (or Material emissiveColor) than the Background color, otherwise geometry is invisible.
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/Rendering/IndexedLineSet/IndexedLineSet.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of IndexedLineSet](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#IndexedLineSet){:target="_blank"}
+- [X3D Specification of IndexedLineSet node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rendering.html#IndexedLineSet){:target="_blank"}