x_ite 8.8.6 → 8.9.0

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

@@ -1,6 +1,6 @@
 ---
 title: PlaneSensor
-date: 2022-01-07
+date: 2023-01-07
 nav: components-PointingDeviceSensor
 categories: [components, PointingDeviceSensor]
 tags: [PlaneSensor, PointingDeviceSensor]
@@ -15,7 +15,7 @@ tags: [PlaneSensor, PointingDeviceSensor]
 
 PlaneSensor converts pointing device motion into 2D translation parallel to the local Z=0 plane.
 
-The PlaneSensor node belongs to the **PointingDeviceSensor** component and its default container field is *children.* It is available since X3D version 2.0 or later.
+The PlaneSensor 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,21 +32,26 @@ The PlaneSensor 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.
 
-### SFBool [in, out] **enabled** TRUE
+#### Hint
 
-Enables/disables node operation.
+- [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).
 
-### SFRotation [in, out] **axisRotation** 0 0 1 0
+### SFBool [in, out] **enabled** TRUE
+
+Enables/disables node operation.
+
+### SFRotation [in, out] **axisRotation** 0 0 1 0 <small>[-1,1] or (-∞,∞)</small>
 
 *axisRotation* determines local sensor coordinate system by rotating the local coordinate system.
 
@@ -64,51 +69,69 @@ Sends event and remembers last value sensed.
 
 ### SFVec2f [in, out] **minPosition** 0 0 <small>(-∞,∞)</small>
 
-*minPosition* and maxPosition clamp translations to a range of values measured from origin of Z=0 plane default maxPosition \< minPosition means no clamping.
+*minPosition* and maxPosition clamp translations to a range of values measured from origin of Z=0 plane default maxPosition \< *minPosition* means no clamping.
 
 #### Hint
 
-- Create a LineSensor by constraining one axis (minPosition.x=maxPosition.x) or (minPosition.y=maxPosition.y).
+- Create a LineSensor by constraining one axis (*minPosition*.x=maxPosition.x) or (*minPosition*.y=maxPosition.y).
 
 ### SFVec2f [in, out] **maxPosition** -1 -1 <small>(-∞,∞)</small>
 
-MinPosition and maxPosition clamp translations to a range of values measured from origin of Z=0 plane default maxPosition \< minPosition means no clamping.
+MinPosition and *maxPosition* clamp translations to a range of values measured from origin of Z=0 plane default *maxPosition* \< minPosition means no clamping.
 
 #### Hint
 
-- Create a LineSensor by constraining one axis (minPosition.x=maxPosition.x) or (minPosition.y=maxPosition.y).
+- Create a LineSensor by constraining one axis (minPosition.x=*maxPosition*.x) or (minPosition.y=*maxPosition*.y).
 
 ### SFVec3f [out] **trackPoint_changed**
 
 *trackPoint_changed* events give intersection point of bearing with sensor's virtual geometry.
 
+#### Warnings
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+- *trackPoint_changed* events represent unclamped intersection points on plane surface. Browsers can interpret drags off of the surface in various ways. Note that translation_changed events are clamped by minPosition/maxPosition and thus may be preferable.
+
 ### SFVec3f [out] **translation_changed**
 
 *translation_changed* events equal sum of relative translation change plus offset value.
 
+#### 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 geometry is selected (e.g. when primary mouse button is pressed), output event isActive=false is sent when geometry is deselected (e.g. when primary mouse button is released).
+Select geometry by activating the pointing device (for example, clicking the mouse) to generate *isActive* events. Output event *isActive*=true is sent when geometry is selected (for example, when primary mouse button is pressed), output event *isActive*=false is sent when geometry is deselected (for example, when primary mouse button is released).
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
-## Description
+## Advisories
 
 ### Hints
 
 - Create a LineSensor by constraining one axis: (minPosition.x=maxPosition.x) or (minPosition.y=maxPosition.y).
 - This sensor detects user interactions affecting peer nodes and their child geometry.
 - Add semi-transparent surrounding geometry to see the effect of the sensor.
+- [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.2 Drag sensors](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/pointingDeviceSensor.html#DragSensors){: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/PlaneSensor/PlaneSensor.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of PlaneSensor](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#PlaneSensor){: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.2 Drag sensors](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#DragSensors){: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 PlaneSensor node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#PlaneSensor){:target="_blank"}

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

@@ -1,6 +1,6 @@
 ---
 title: SphereSensor
-date: 2022-01-07
+date: 2023-01-07
 nav: components-PointingDeviceSensor
 categories: [components, PointingDeviceSensor]
 tags: [SphereSensor, PointingDeviceSensor]
@@ -15,7 +15,7 @@ tags: [SphereSensor, PointingDeviceSensor]
 
 SphereSensor converts pointing device motion into a spherical rotation about the origin of the local coordinate system.
 
-The SphereSensor node belongs to the **PointingDeviceSensor** component and its default container field is *children.* It is available since X3D version 2.0 or later.
+The SphereSensor 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,19 +32,24 @@ The SphereSensor node belongs to the **PointingDeviceSensor** component and its
 
 ### 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.
 
-### SFBool [in, out] **enabled** TRUE
+#### Hint
 
-Enables/disables node operation.
+- [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
+
+Enables/disables node operation.
 
 ### SFBool [in, out] **autoOffset** TRUE
 
@@ -62,28 +67,45 @@ Sends event and remembers last value sensed.
 
 *trackPoint_changed* events give intersection point of bearing with sensor's virtual geometry.
 
+#### Warnings
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+- *trackPoint_changed* events represent unclamped intersection points on plane surface. Browsers can interpret drags off of the surface in various ways. Note that translation_changed events are clamped by minPosition/maxPosition and thus may be preferable.
+
 ### SFRotation [out] **rotation_changed**
 
 *rotation_changed* events equal sum of relative bearing changes plus offset value.
 
+#### 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 geometry is selected (e.g. when primary mouse button is pressed), output event isActive=false is sent when geometry is deselected (e.g. when primary mouse button is released).
+Select geometry by activating the pointing device (for example, clicking the mouse) to generate *isActive* events. Output event *isActive*=true is sent when geometry is selected (for example, when primary mouse button is pressed), output event *isActive*=false is sent when geometry is deselected (for example, when primary mouse button is released).
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
-## Description
+## Advisories
 
 ### Hints
 
 - This sensor detects user interactions affecting peer nodes and their child geometry.
 - Add semi-transparent surrounding geometry to see the effect of the sensor.
+- [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.2 Drag sensors](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/pointingDeviceSensor.html#DragSensors){: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"}
 
-## External Links
+## See Also
 
-- [X3D Specification of SphereSensor](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#SphereSensor){: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.2 Drag sensors](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#DragSensors){: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 SphereSensor node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/pointingDeviceSensor.html#SphereSensor){:target="_blank"}

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,39 +32,64 @@ 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.
 
-### SFBool [in, out] **enabled** TRUE
+#### Hint
 
-Enables/disables node operation.
+- [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
+
+Enables/disables node operation.
 
 ### SFVec2f [out] **hitTexCoord_changed**
 
 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).
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
-## Description
+## Advisories
 
-### Hint
+### 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,39 +29,44 @@ 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
 
 Enables/disables node operation.
 
-### SFVec4f [in, out] **plane** 0 1 0 0 <small>[0,1]</small>
+### 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"}