<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Symbol";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Holger,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thank you for your observations. And sincere apologies for the long time delay in responding to them.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> I will go through each observation individually, and in alphabetical order of node, so this will be a long e-mail.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>As a general reference the changelog for the DTD can be found here:<o:p></o:p></p><p class=MsoPlainText><a href="http://www.web3d.org/specifications/x3d-dtd-changelog.txt">http://www.web3d.org/specifications/x3d-dtd-changelog.txt</a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: BallJoint, field: forceOutput<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#BallJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#BallJoint</a>, where the node signature lists the default as "NONE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: forceOutput %MFString; "NONE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: CollisionCollection, field: appliedParameters<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#CollisionCollection">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#CollisionCollection</a>, where the node signature lists the default as "BOUNCE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: appliedParameters %MFString; "BOUNCE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: Contact, field: appliedParameters<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#Contact">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#Contact</a>, where the node signature lists the default as "BOUNCE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: appliedParameters %MFString; "BOUNCE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: DirectionalLight, field: global<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/lighting.html#DirectionalLight">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/lighting.html#DirectionalLight</a>, where the node signature lists the default value as “FALSE”.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>You observed that the other light nodes have a default value for their “global” field as “TRUE”. The inconsistencies with the “global” field have been noted in Mantis issue 672, available to Web3D members at <a href="http://www.web3d.org/member-only/mantis/view.php?id=672">http://www.web3d.org/member-only/mantis/view.php?id=672</a>. It is anticipated that the next version of the standard will keep the existing definitions, with additional explanation for the differences in default values.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText>Node: DISEntityManager, field: applicationID<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#DISEntityManager">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#DISEntityManager</a>, where the node signature lists the default as 1.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: applicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This has been updated in the DTD, and will be changed in the standard for the next version. The reason is that the IEEE DIS standard 1278.1-2012, clause 4.2.5.8 Identified number assignments, Table 3 - Valid range of identifier numbers, lists valid IDs as ranging from 1 to 65534. A value of 0 (which has the symbolic name NO_APPLIC) means that no value is specified. Therefore, the standard was incorrect to use a default of 1. The DTD changelog indicates that the DTD was amended on 27 May 2015.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue for this, namely 795 (members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=795">http://www.web3d.org/member-only/mantis/view.php?id=795</a>).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: DoubleAxisHingeJoint, field: forceOutput<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#DoubleAxisHingeJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#DoubleAxisHingeJoint</a>, where the node signature lists the default as "NONE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: forceOutput %MFString; "NONE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: DoubleAxisHingeJoint, fields: anchorPoint, axis1, axis2<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#DoubleAxisHingeJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#DoubleAxisHingeJoint</a>, where the node signature lists the default for each of these fields as 0 0 0.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listings for these fields are:<o:p></o:p></p><p class=MsoPlainText> anchorPoint %SFVec3f; "0 1 0"<o:p></o:p></p><p class=MsoPlainText> axis1 %SFVec3f; "0 1 0"<o:p></o:p></p><p class=MsoPlainText> axis2 %SFVec3f; "0 1 0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The "anchorPoint" field represents a location, and so the default should be "0 0 0".<o:p></o:p></p><p class=MsoPlainText>The "axis1" and "axis2" fields all represent vectors. The default of "0 0 0" is an invalid vector, and will be corrected in the next version of the standard.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue covering the "axis1" and "axis2" fields. It is Mantis 788. Members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=788">http://www.web3d.org/member-only/mantis/view.php?id=788</a>.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>------------------------- <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: ElevationGrid, fields: xDimension, yDimension, height<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geometry3D.html#ElevationGrid">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geometry3D.html#ElevationGrid</a>, where the node signature lists the default for these fields as 0, 0, and [] respectively.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listings for these fields are:<o:p></o:p></p><p class=MsoPlainText> xDimension %SFInt32; "2"<o:p></o:p></p><p class=MsoPlainText> zDimension %SFInt32; "2"<o:p></o:p></p><p class=MsoPlainText> height %MFFloat; "0 0 0 0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The default values in the standard do not represent an elevation grid, and it was decided that these should be updated to the minimum representation of an elevation grid. The DTD change log reports that the DTD was changed on 23 December 2015. The change will be reflected in the next version of the specification.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Mantis issue 872 (members can view that at <a href="http://www.web3d.org/member-only/mantis/view.php?id=872">http://www.web3d.org/member-only/mantis/view.php?id=872</a>) covers this amendment.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: EspduTransform, fields: applicationID, eventApplicationID, munitionApplicationID<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#EspduTransform">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#EspduTransform</a>, where the node signature lists the defaults for all three fields as 1.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for these fields are:<o:p></o:p></p><p class=MsoPlainText> applicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText> eventApplicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText> munitionApplicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>These have been updated in the DTD, and will be changed in the standard for the next version. The reason is that the IEEE DIS standard 1278.1-2012, clause 4.2.5.8 Identified number assignments, Table 3 - Valid range of identifier numbers, lists valid IDs as ranging from 1 to 65534. A value of 0 (which has the symbolic name NO_APPLIC) means that no value is specified. Therefore, the standard was incorrect to use a default of 1. The DTD changelog indicates that the DTD was amended on 27 May 2015.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue for this, namely 795 (members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=795">http://www.web3d.org/member-only/mantis/view.php?id=795</a>).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: GeoElevationGrid, fields: xDimension, yDimension, height<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#GeoElevationGrid">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#GeoElevationGrid</a>, where the node signature lists the default for these fields as 0, 0, and [0 0] respectively.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listings for these fields are:<o:p></o:p></p><p class=MsoPlainText> xDimension %SFInt32; "2"<o:p></o:p></p><p class=MsoPlainText> zDimension %SFInt32; "2"<o:p></o:p></p><p class=MsoPlainText> height %MFFloat; "0 0 0 0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The default values in the standard do not represent an elevation grid, and it was decided that these should be updated to the minimum representation of an elevation grid. The DTD change log reports that the DTD was changed on 23 December 2015. The change will be reflected in the next version of the specification.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Mantis issue 872 (members can view that at <a href="http://www.web3d.org/member-only/mantis/view.php?id=872">http://www.web3d.org/member-only/mantis/view.php?id=872</a>) covers this amendment.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: HAnimJoint, field: stiffness<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/hanim.html#HAnimJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/hanim.html#HAnimJoint</a>, where the node signature lists the default as "0 0 0".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: stiffness %MFFloat; "1 1 1"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The default values in the standard were noted to effectively prohibit all joint rotation. It was decided that a value of “1 1 1” would be more appropriate, providing better support for inverse kinematics. The DTD change log reports that the DTD was changed on 26 December 2016. The change will be reflected in the next version of the specification.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Mantis issue 1113 (members can view that at <a href="http://www.web3d.org/member-only/mantis/view.php?id=1113">http://www.web3d.org/member-only/mantis/view.php?id=1113</a>) covers this amendment.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: Layout, field: size<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/layout.html#Layout">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/layout.html#Layout</a>, where the node signature lists the default as "1 1".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: size %SFFloat; "1.0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Great spot, Holger. The node signature lists the layout field as being of type MFFloat. The descriptive text states that there should be two values. Checking the XML schema the listing is for type MFFloat, default “1 1”. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD is incorrect. These needs to be changed to correspond to the standard. This will be verified by the working group, and then implemented.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: LinePickSensor, field: objectType<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#LinePickSensor">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#LinePickSensor</a>, where the node signature lists the default as "ALL".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: objectType %MFString; "ALL"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: MotorJoint, field: forceOutput<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#MotorJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#MotorJoint</a>, where the node signature lists the default as "NONE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: forceOutput %MFString; "NONE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: PickableGroup, field: objectType<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PickableGroup">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PickableGroup</a>, where the node signature lists the default as "ALL".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: objectType %MFString; "ALL"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: PointPickSensor, field: objectType<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PointPickSensor">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PointPickSensor</a>, where the node signature lists the default as "ALL".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: objectType %MFString; "ALL"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: PrimitivePickSensor, field: objectType<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PrimitivePickSensor">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PrimitivePickSensor</a>, where the node signature lists the default as "ALL".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: objectType %MFString; "ALL"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: ReceiverPdu, fields: applicationID, transmitterApplicationID<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#ReceiverPdu">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#ReceiverPdu</a>, where the node signature lists the defaults for both fields as 1.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for these fields are:<o:p></o:p></p><p class=MsoPlainText> applicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText> transmitterApplicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>These have been updated in the DTD, and will be changed in the standard for the next version. The reason is that the IEEE DIS standard 1278.1-2012, clause 4.2.5.8 Identified number assignments, Table 3 - Valid range of identifier numbers, lists valid IDs as ranging from 1 to 65534. A value of 0 (which has the symbolic name NO_APPLIC) means that no value is specified. Therefore, the standard was incorrect to use a default of 1. The DTD changelog indicates that the DTD was amended on 27 May 2015.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue for this, namely 795 (members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=795">http://www.web3d.org/member-only/mantis/view.php?id=795</a>).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: RigidBody, field: finiteRotationAxis<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#RigidBody">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#RigidBody</a>, where the node signature lists the default value as “0 0 0”.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: finiteRotationAxis %SFVec3f; “0 1 0”<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The "finiteRotationAxis" field represents a vector. The default of "0 0 0" is an invalid vector, and will be corrected in the next version of the standard. The DTD for version 3.2 was updated in 2009.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue covering this. It is Mantis 789. Members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=789">http://www.web3d.org/member-only/mantis/view.php?id=789</a>.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: ScreenFontStyle, field: pointSize<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/layout.html#ScreenFontStyle">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/layout.html#ScreenFontStyle</a>, where the node signature lists the default as “12.0”.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: pointSize %SFFloat; “1.0”<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Another great spot, Holger. The XML schema and the JSON schema all agree with the abstract standard, and have default values of “12.0”. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD is incorrect. These needs to be changed to correspond to the standard. This will be verified by the working group, and then implemented.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: SignalPdu, field: applicationID<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#SignalPdu">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#SignalPdu</a>, where the node signature lists the defaults for this field as 1.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: applicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This have been updated in the DTD, and will be changed in the standard for the next version. The reason is that the IEEE DIS standard 1278.1-2012, clause 4.2.5.8 Identified number assignments, Table 3 - Valid range of identifier numbers, lists valid IDs as ranging from 1 to 65534. A value of 0 (which has the symbolic name NO_APPLIC) means that no value is specified. Therefore, the standard was incorrect to use a default of 1. The DTD changelog indicates that the DTD was amended on 27 May 2015.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue for this, namely 795 (members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=795">http://www.web3d.org/member-only/mantis/view.php?id=795</a>).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: SingleAxisHingeJoint, field: forceOutput<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#SingleAxisHingeJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#SingleAxisHingeJoint</a>, where the node signature lists the default as "NONE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: forceOutput %MFString; "NONE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: SliderJoint, field: forceOutput<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#SliderJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#SliderJoint</a>, where the node signature lists the default as "NONE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: forceOutput %MFString; "NONE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: TransmitterPdu, field: applicationID<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#TransmitterPdu">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#TransmitterPdu</a>, where the node signature lists the defaults for this field as 1.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: applicationID %SFInt32; "0"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This have been updated in the DTD, and will be changed in the standard for the next version. The reason is that the IEEE DIS standard 1278.1-2012, clause 4.2.5.8 Identified number assignments, Table 3 - Valid range of identifier numbers, lists valid IDs as ranging from 1 to 65534. A value of 0 (which has the symbolic name NO_APPLIC) means that no value is specified. Therefore, the standard was incorrect to use a default of 1. The DTD changelog indicates that the DTD was amended on 27 May 2015.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue for this, namely 795 (members can view this at <a href="http://www.web3d.org/member-only/mantis/view.php?id=795">http://www.web3d.org/member-only/mantis/view.php?id=795</a>).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: UniversalJoint, field: forceOutput<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#UniversalJoint">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#UniversalJoint</a>, where the node signature lists the default as "NONE".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: forceOutput %MFString; "NONE"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: VolumePickSensor, field: objectType<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#VolumePickSensor">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#VolumePickSensor</a>, where the node signature lists the default as "ALL".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: objectType %MFString; "ALL"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Therefore, the DTD agrees with the standard. Why do you list the default as ' '?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Node: WindPhysicsModel, field: direction<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>See <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/particle_systems.html#WindPhysicsModel">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/particle_systems.html#WindPhysicsModel</a>, where the node signature lists the default as “0 0 0”.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The DTD listing for this field is: direction %SFVec3f; “1 0 0”<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The value of “0 0 0” is an illegal value for a vector. Furthermore, the text states that this should be a “normalized, unit vector”. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There is a Mantis issue covering this point. It is Mantis 798, and is available to Web3D members at <a href="http://www.web3d.org/member-only/mantis/view.php?id=798">http://www.web3d.org/member-only/mantis/view.php?id=798</a>.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-------------------------<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>All the best,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Roy<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<o:p></o:p></p><p class=MsoPlainText>From: Holger Seelig [mailto:holger.seelig@yahoo.de] <o:p></o:p></p><p class=MsoPlainText>Sent: 12 June 2017 09:22<o:p></o:p></p><p class=MsoPlainText>To: X3D Graphics public mailing list <x3d-public@web3d.org>; Don Brutzman <brutzman@nps.edu>; Roy Walmsley <roy.walmsley@ntlworld.com><o:p></o:p></p><p class=MsoPlainText>Subject: Differences of default values between specification and dtd<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I detected some differences of the default values between the 3.3 Specification <http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/Architecture.html><o:p></o:p></p><p class=MsoPlainText>and the 3.3 dtd <http://www.web3d.org/specifications/x3d-3.3.dtd>.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The default values are not equal, thus it is not clear to me which values take precedence.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>A second issue I detected is that the default value for the global field of the DirectionalLight node is FALSE, although all other light nodes have a global TRUE value, which makes sense because if the global field is default FALSE it would break backward compatibility to VRML2.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The document attached and below list the affected fields showing the default values of the dtd. Please note the 'Volume rendering component' <o:p></o:p></p><p class=MsoPlainText>is still not verified.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Best regards,<o:p></o:p></p><p class=MsoPlainText>Holger Seelig<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.3//EN" <o:p></o:p></p><p class=MsoPlainText>"http://www.web3d.org/specifications/x3d-3.3.dtd"><o:p></o:p></p><p class=MsoPlainText><X3D profile='Full' version='3.3' <o:p></o:p></p><p class=MsoPlainText>xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance' <o:p></o:p></p><p class=MsoPlainText>xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.3.xsd'><o:p></o:p></p><p class=MsoPlainText> <head><o:p></o:p></p><p class=MsoPlainText> <meta name='title' content='NodeIndex.x3d'/><o:p></o:p></p><p class=MsoPlainText> </head><o:p></o:p></p><p class=MsoPlainText> <Scene><o:p></o:p></p><p class=MsoPlainText> <Anchor/><o:p></o:p></p><p class=MsoPlainText> <Appearance/><o:p></o:p></p><p class=MsoPlainText> <Arc2D/><o:p></o:p></p><p class=MsoPlainText> <ArcClose2D/><o:p></o:p></p><p class=MsoPlainText> <AudioClip/><o:p></o:p></p><p class=MsoPlainText> <Background/><o:p></o:p></p><p class=MsoPlainText> <BallJoint<o:p></o:p></p><p class=MsoPlainText> forceOutput=''/><o:p></o:p></p><p class=MsoPlainText> <Billboard/><o:p></o:p></p><p class=MsoPlainText> <BooleanFilter/><o:p></o:p></p><p class=MsoPlainText> <BooleanSequencer/><o:p></o:p></p><p class=MsoPlainText> <BooleanToggle/><o:p></o:p></p><p class=MsoPlainText> <BooleanTrigger/><o:p></o:p></p><p class=MsoPlainText> <BoundedPhysicsModel/><o:p></o:p></p><p class=MsoPlainText> <Box/><o:p></o:p></p><p class=MsoPlainText> <CADAssembly/><o:p></o:p></p><p class=MsoPlainText> <CADFace/><o:p></o:p></p><p class=MsoPlainText> <CADLayer/><o:p></o:p></p><p class=MsoPlainText> <CADPart/><o:p></o:p></p><p class=MsoPlainText> <Circle2D/><o:p></o:p></p><p class=MsoPlainText> <ClipPlane/><o:p></o:p></p><p class=MsoPlainText> <CollidableOffset/><o:p></o:p></p><p class=MsoPlainText> <CollidableShape/><o:p></o:p></p><p class=MsoPlainText> <Collision/><o:p></o:p></p><p class=MsoPlainText> <CollisionCollection<o:p></o:p></p><p class=MsoPlainText> appliedParameters=''/><o:p></o:p></p><p class=MsoPlainText> <CollisionSensor/><o:p></o:p></p><p class=MsoPlainText> <CollisionSpace/><o:p></o:p></p><p class=MsoPlainText> <Color/><o:p></o:p></p><p class=MsoPlainText> <ColorDamper/><o:p></o:p></p><p class=MsoPlainText> <ColorInterpolator/><o:p></o:p></p><p class=MsoPlainText> <ColorRGBA/><o:p></o:p></p><p class=MsoPlainText> <ComposedCubeMapTexture/><o:p></o:p></p><p class=MsoPlainText> <ComposedShader/><o:p></o:p></p><p class=MsoPlainText> <ComposedTexture3D/><o:p></o:p></p><p class=MsoPlainText> <Cone/><o:p></o:p></p><p class=MsoPlainText> <ConeEmitter/><o:p></o:p></p><p class=MsoPlainText> <Contact<o:p></o:p></p><p class=MsoPlainText> appliedParameters=''/><o:p></o:p></p><p class=MsoPlainText> <Contour2D/><o:p></o:p></p><p class=MsoPlainText> <ContourPolyline2D/><o:p></o:p></p><p class=MsoPlainText> <Coordinate/><o:p></o:p></p><p class=MsoPlainText> <CoordinateDamper/><o:p></o:p></p><p class=MsoPlainText> <CoordinateDouble/><o:p></o:p></p><p class=MsoPlainText> <CoordinateInterpolator/><o:p></o:p></p><p class=MsoPlainText> <CoordinateInterpolator2D/><o:p></o:p></p><p class=MsoPlainText> <Cylinder/><o:p></o:p></p><p class=MsoPlainText> <CylinderSensor/><o:p></o:p></p><p class=MsoPlainText> <DISEntityManager<o:p></o:p></p><p class=MsoPlainText> applicationID='0'/><o:p></o:p></p><p class=MsoPlainText> <DISEntityTypeMapping/><o:p></o:p></p><p class=MsoPlainText> <DirectionalLight<o:p></o:p></p><p class=MsoPlainText> global='false'/><o:p></o:p></p><p class=MsoPlainText> <Disk2D/><o:p></o:p></p><p class=MsoPlainText> <DoubleAxisHingeJoint<o:p></o:p></p><p class=MsoPlainText> forceOutput=''<o:p></o:p></p><p class=MsoPlainText> anchorPoint='0 1 0'<o:p></o:p></p><p class=MsoPlainText> axis1='0 1 0'<o:p></o:p></p><p class=MsoPlainText> axis2='0 1 0'/><o:p></o:p></p><p class=MsoPlainText> <EaseInEaseOut/><o:p></o:p></p><p class=MsoPlainText> <ElevationGrid<o:p></o:p></p><p class=MsoPlainText> xDimension='2'<o:p></o:p></p><p class=MsoPlainText> zDimension='2'<o:p></o:p></p><p class=MsoPlainText> height='0, 0, 0, 0'/><o:p></o:p></p><p class=MsoPlainText> <EspduTransform<o:p></o:p></p><p class=MsoPlainText> applicationID='0'<o:p></o:p></p><p class=MsoPlainText> eventApplicationID='0'<o:p></o:p></p><p class=MsoPlainText> munitionApplicationID='0'/><o:p></o:p></p><p class=MsoPlainText> <ExplosionEmitter/><o:p></o:p></p><p class=MsoPlainText> <Extrusion/><o:p></o:p></p><p class=MsoPlainText> <FillProperties/><o:p></o:p></p><p class=MsoPlainText> <FloatVertexAttribute/><o:p></o:p></p><p class=MsoPlainText> <Fog/><o:p></o:p></p><p class=MsoPlainText> <FogCoordinate/><o:p></o:p></p><p class=MsoPlainText> <FontStyle/><o:p></o:p></p><p class=MsoPlainText> <GeneratedCubeMapTexture/><o:p></o:p></p><p class=MsoPlainText> <GeoCoordinate/><o:p></o:p></p><p class=MsoPlainText> <GeoElevationGrid<o:p></o:p></p><p class=MsoPlainText> xDimension='2'<o:p></o:p></p><p class=MsoPlainText> zDimension='2'<o:p></o:p></p><p class=MsoPlainText> height='0, 0, 0, 0'/><o:p></o:p></p><p class=MsoPlainText> <GeoLOD/><o:p></o:p></p><p class=MsoPlainText> <GeoLocation/><o:p></o:p></p><p class=MsoPlainText> <GeoMetadata/><o:p></o:p></p><p class=MsoPlainText> <GeoOrigin/><o:p></o:p></p><p class=MsoPlainText> <GeoPositionInterpolator/><o:p></o:p></p><p class=MsoPlainText> <GeoProximitySensor/><o:p></o:p></p><p class=MsoPlainText> <GeoTouchSensor/><o:p></o:p></p><p class=MsoPlainText> <GeoTransform/><o:p></o:p></p><p class=MsoPlainText> <GeoViewpoint/><o:p></o:p></p><p class=MsoPlainText> <ForcePhysicsModel/><o:p></o:p></p><p class=MsoPlainText> <Group/><o:p></o:p></p><p class=MsoPlainText> <HAnimDisplacer/><o:p></o:p></p><p class=MsoPlainText> <HAnimHumanoid/><o:p></o:p></p><p class=MsoPlainText> <HAnimJoint<o:p></o:p></p><p class=MsoPlainText> stiffness='1, 1, 1'/><o:p></o:p></p><p class=MsoPlainText> <HAnimSegment/><o:p></o:p></p><p class=MsoPlainText> <HAnimSite/><o:p></o:p></p><p class=MsoPlainText> <ImageCubeMapTexture/><o:p></o:p></p><p class=MsoPlainText> <ImageTexture/><o:p></o:p></p><p class=MsoPlainText> <ImageTexture3D/><o:p></o:p></p><p class=MsoPlainText> <IndexedFaceSet/><o:p></o:p></p><p class=MsoPlainText> <IndexedLineSet/><o:p></o:p></p><p class=MsoPlainText> <IndexedQuadSet/><o:p></o:p></p><p class=MsoPlainText> <IndexedTriangleFanSet/><o:p></o:p></p><p class=MsoPlainText> <IndexedTriangleSet/><o:p></o:p></p><p class=MsoPlainText> <IndexedTriangleStripSet/><o:p></o:p></p><p class=MsoPlainText> <Inline/><o:p></o:p></p><p class=MsoPlainText> <IntegerSequencer/><o:p></o:p></p><p class=MsoPlainText> <IntegerTrigger/><o:p></o:p></p><p class=MsoPlainText> <KeySensor/><o:p></o:p></p><p class=MsoPlainText> <LOD/><o:p></o:p></p><p class=MsoPlainText> <Layer/><o:p></o:p></p><p class=MsoPlainText> <LayerSet/><o:p></o:p></p><p class=MsoPlainText> <Layout<o:p></o:p></p><p class=MsoPlainText> size='1'/><o:p></o:p></p><p class=MsoPlainText> <LayoutGroup/><o:p></o:p></p><p class=MsoPlainText> <LayoutLayer/><o:p></o:p></p><p class=MsoPlainText> <LinePickSensor<o:p></o:p></p><p class=MsoPlainText> objectType=''/><o:p></o:p></p><p class=MsoPlainText> <LineProperties/><o:p></o:p></p><p class=MsoPlainText> <LineSet/><o:p></o:p></p><p class=MsoPlainText> <LoadSensor/><o:p></o:p></p><p class=MsoPlainText> <LocalFog/><o:p></o:p></p><p class=MsoPlainText> <Material/><o:p></o:p></p><p class=MsoPlainText> <Matrix3VertexAttribute/><o:p></o:p></p><p class=MsoPlainText> <Matrix4VertexAttribute/><o:p></o:p></p><p class=MsoPlainText> <MetadataBoolean/><o:p></o:p></p><p class=MsoPlainText> <MetadataDouble/><o:p></o:p></p><p class=MsoPlainText> <MetadataFloat/><o:p></o:p></p><p class=MsoPlainText> <MetadataInteger/><o:p></o:p></p><p class=MsoPlainText> <MetadataSet/><o:p></o:p></p><p class=MsoPlainText> <MetadataString/><o:p></o:p></p><p class=MsoPlainText> <MotorJoint<o:p></o:p></p><p class=MsoPlainText> forceOutput=''/><o:p></o:p></p><p class=MsoPlainText> <MovieTexture/><o:p></o:p></p><p class=MsoPlainText> <MultiTexture/><o:p></o:p></p><p class=MsoPlainText> <MultiTextureCoordinate/><o:p></o:p></p><p class=MsoPlainText> <MultiTextureTransform/><o:p></o:p></p><p class=MsoPlainText> <NavigationInfo/><o:p></o:p></p><p class=MsoPlainText> <Normal/><o:p></o:p></p><p class=MsoPlainText> <NormalInterpolator/><o:p></o:p></p><p class=MsoPlainText> <NurbsCurve/><o:p></o:p></p><p class=MsoPlainText> <NurbsCurve2D/><o:p></o:p></p><p class=MsoPlainText> <NurbsOrientationInterpolator/><o:p></o:p></p><p class=MsoPlainText> <NurbsPatchSurface/><o:p></o:p></p><p class=MsoPlainText> <NurbsPositionInterpolator/><o:p></o:p></p><p class=MsoPlainText> <NurbsSet/><o:p></o:p></p><p class=MsoPlainText> <NurbsSurfaceInterpolator/><o:p></o:p></p><p class=MsoPlainText> <NurbsSweptSurface/><o:p></o:p></p><p class=MsoPlainText> <NurbsSwungSurface/><o:p></o:p></p><p class=MsoPlainText> <NurbsTextureCoordinate/><o:p></o:p></p><p class=MsoPlainText> <NurbsTrimmedSurface/><o:p></o:p></p><p class=MsoPlainText> <OrientationChaser/><o:p></o:p></p><p class=MsoPlainText> <OrientationDamper/><o:p></o:p></p><p class=MsoPlainText> <OrientationInterpolator/><o:p></o:p></p><p class=MsoPlainText> <OrthoViewpoint/><o:p></o:p></p><p class=MsoPlainText> <PackagedShader/><o:p></o:p></p><p class=MsoPlainText> <ParticleSystem/><o:p></o:p></p><p class=MsoPlainText> <PickableGroup<o:p></o:p></p><p class=MsoPlainText> objectType=''/><o:p></o:p></p><p class=MsoPlainText> <PixelTexture/><o:p></o:p></p><p class=MsoPlainText> <PixelTexture3D/><o:p></o:p></p><p class=MsoPlainText> <PlaneSensor/><o:p></o:p></p><p class=MsoPlainText> <PointEmitter/><o:p></o:p></p><p class=MsoPlainText> <PointLight/><o:p></o:p></p><p class=MsoPlainText> <PointPickSensor<o:p></o:p></p><p class=MsoPlainText> objectType=''/><o:p></o:p></p><p class=MsoPlainText> <PointSet/><o:p></o:p></p><p class=MsoPlainText> <Polyline2D/><o:p></o:p></p><p class=MsoPlainText> <PolylineEmitter/><o:p></o:p></p><p class=MsoPlainText> <Polypoint2D/><o:p></o:p></p><p class=MsoPlainText> <PositionChaser/><o:p></o:p></p><p class=MsoPlainText> <PositionChaser2D/><o:p></o:p></p><p class=MsoPlainText> <PositionDamper/><o:p></o:p></p><p class=MsoPlainText> <PositionDamper2D/><o:p></o:p></p><p class=MsoPlainText> <PositionInterpolator/><o:p></o:p></p><p class=MsoPlainText> <PositionInterpolator2D/><o:p></o:p></p><p class=MsoPlainText> <PrimitivePickSensor<o:p></o:p></p><p class=MsoPlainText> objectType=''/><o:p></o:p></p><p class=MsoPlainText> <ProgramShader/><o:p></o:p></p><p class=MsoPlainText> <ProximitySensor/><o:p></o:p></p><p class=MsoPlainText> <QuadSet/><o:p></o:p></p><p class=MsoPlainText> <ReceiverPdu<o:p></o:p></p><p class=MsoPlainText> applicationID='0'<o:p></o:p></p><p class=MsoPlainText> transmitterApplicationID='0'/><o:p></o:p></p><p class=MsoPlainText> <Rectangle2D/><o:p></o:p></p><p class=MsoPlainText> <RigidBody<o:p></o:p></p><p class=MsoPlainText> finiteRotationAxis='0 1 0'/><o:p></o:p></p><p class=MsoPlainText> <RigidBodyCollection/><o:p></o:p></p><p class=MsoPlainText> <ScalarChaser/><o:p></o:p></p><p class=MsoPlainText> <ScalarInterpolator/><o:p></o:p></p><p class=MsoPlainText> <ScreenFontStyle<o:p></o:p></p><p class=MsoPlainText> pointSize='1'/><o:p></o:p></p><p class=MsoPlainText> <ScreenGroup/><o:p></o:p></p><p class=MsoPlainText> <Script/><o:p></o:p></p><p class=MsoPlainText> <ShaderPart/><o:p></o:p></p><p class=MsoPlainText> <ShaderProgram/><o:p></o:p></p><p class=MsoPlainText> <Shape/><o:p></o:p></p><p class=MsoPlainText> <SignalPdu<o:p></o:p></p><p class=MsoPlainText> applicationID='0'/><o:p></o:p></p><p class=MsoPlainText> <SingleAxisHingeJoint<o:p></o:p></p><p class=MsoPlainText> forceOutput=''/><o:p></o:p></p><p class=MsoPlainText> <SliderJoint<o:p></o:p></p><p class=MsoPlainText> forceOutput=''/><o:p></o:p></p><p class=MsoPlainText> <Sound/><o:p></o:p></p><p class=MsoPlainText> <Sphere/><o:p></o:p></p><p class=MsoPlainText> <SphereSensor/><o:p></o:p></p><p class=MsoPlainText> <SplinePositionInterpolator/><o:p></o:p></p><p class=MsoPlainText> <SplinePositionInterpolator2D/><o:p></o:p></p><p class=MsoPlainText> <SplineScalarInterpolator/><o:p></o:p></p><p class=MsoPlainText> <SpotLight/><o:p></o:p></p><p class=MsoPlainText> <SquadOrientationInterpolator/><o:p></o:p></p><p class=MsoPlainText> <StaticGroup/><o:p></o:p></p><p class=MsoPlainText> <StringSensor/><o:p></o:p></p><p class=MsoPlainText> <SurfaceEmitter/><o:p></o:p></p><p class=MsoPlainText> <Switch/><o:p></o:p></p><p class=MsoPlainText> <TexCoordDamper2D/><o:p></o:p></p><p class=MsoPlainText> <Text/><o:p></o:p></p><p class=MsoPlainText> <TextureBackground/><o:p></o:p></p><p class=MsoPlainText> <TextureCoordinate/><o:p></o:p></p><p class=MsoPlainText> <TextureCoordinate3D/><o:p></o:p></p><p class=MsoPlainText> <TextureCoordinate4D/><o:p></o:p></p><p class=MsoPlainText> <TextureCoordinateGenerator/><o:p></o:p></p><p class=MsoPlainText> <TextureProperties/><o:p></o:p></p><p class=MsoPlainText> <TextureTransform/><o:p></o:p></p><p class=MsoPlainText> <TextureTransform3D/><o:p></o:p></p><p class=MsoPlainText> <TextureTransformMatrix3D/><o:p></o:p></p><p class=MsoPlainText> <TimeSensor/><o:p></o:p></p><p class=MsoPlainText> <TimeTrigger/><o:p></o:p></p><p class=MsoPlainText> <TouchSensor/><o:p></o:p></p><p class=MsoPlainText> <Transform/><o:p></o:p></p><p class=MsoPlainText> <TransformSensor/><o:p></o:p></p><p class=MsoPlainText> <TransmitterPdu<o:p></o:p></p><p class=MsoPlainText> applicationID='0'/><o:p></o:p></p><p class=MsoPlainText> <TriangleFanSet/><o:p></o:p></p><p class=MsoPlainText> <TriangleSet/><o:p></o:p></p><p class=MsoPlainText> <TriangleSet2D/><o:p></o:p></p><p class=MsoPlainText> <TriangleStripSet/><o:p></o:p></p><p class=MsoPlainText> <TwoSidedMaterial/><o:p></o:p></p><p class=MsoPlainText> <UniversalJoint<o:p></o:p></p><p class=MsoPlainText> forceOutput=''/><o:p></o:p></p><p class=MsoPlainText> <Viewpoint/><o:p></o:p></p><p class=MsoPlainText> <ViewpointGroup/><o:p></o:p></p><p class=MsoPlainText> <Viewport/><o:p></o:p></p><p class=MsoPlainText> <VisibilitySensor/><o:p></o:p></p><p class=MsoPlainText> <VolumeEmitter/><o:p></o:p></p><p class=MsoPlainText> <VolumePickSensor<o:p></o:p></p><p class=MsoPlainText> objectType=''/><o:p></o:p></p><p class=MsoPlainText> <WindPhysicsModel<o:p></o:p></p><p class=MsoPlainText> direction='1 0 0'/><o:p></o:p></p><p class=MsoPlainText> <WorldInfo/><o:p></o:p></p><p class=MsoPlainText> </Scene><o:p></o:p></p><p class=MsoPlainText></X3D><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText>Holger Seelig<o:p></o:p></p><p class=MsoPlainText>Mediengestalter Digital – Digital Media Designer<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Scheffelstraße 31a<o:p></o:p></p><p class=MsoPlainText>04277 Leipzig<o:p></o:p></p><p class=MsoPlainText>Germany<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Cellular: +49 1577 147 26 11<o:p></o:p></p><p class=MsoPlainText>E-Mail: holger.seelig@create3000.de<o:p></o:p></p><p class=MsoPlainText>Web: http://titania.create3000.de<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Future to the fantasy <span style='font-family:"Segoe UI Symbol",sans-serif'>★</span> <span style='font-family:"Segoe UI Symbol",sans-serif'>★</span><o:p></o:p></p></div></body></html>