[x3d-public] Differences of default values between specification and dtd

Mon Jul 24 05:54:14 PDT 2017

Holger,

Thank you for your observations. And sincere apologies for the long time delay in responding to them.

I will go through each observation individually, and in alphabetical order of node, so this will be a long e-mail.

As a general reference the changelog for the DTD can be found here:

http://www.web3d.org/specifications/x3d-dtd-changelog.txt

-------------------------

Node: BallJoint, field: forceOutput

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#BallJoint, where the node signature lists the default as "NONE".

The DTD listing for this field is:   forceOutput %MFString; "NONE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: CollisionCollection, field: appliedParameters

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#CollisionCollection, where the node signature lists the default as "BOUNCE".

The DTD listing for this field is:   appliedParameters %MFString; "BOUNCE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: Contact, field: appliedParameters

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#Contact, where the node signature lists the default as "BOUNCE".

The DTD listing for this field is: appliedParameters %MFString; "BOUNCE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: DirectionalLight, field: global

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/lighting.html#DirectionalLight, where the node signature lists the default value as “FALSE”.

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 http://www.web3d.org/member-only/mantis/view.php?id=672. It is anticipated that the next version of the standard will keep the existing definitions, with additional explanation for the differences in default values.

-------------------------

Node: DISEntityManager, field: applicationID

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#DISEntityManager, where the node signature lists the default as 1.

The DTD listing for this field is:   applicationID %SFInt32; "0"

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.

There is a Mantis issue for this, namely 795 (members can view this at http://www.web3d.org/member-only/mantis/view.php?id=795).

-------------------------

Node: DoubleAxisHingeJoint, field: forceOutput

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#DoubleAxisHingeJoint, where the node signature lists the default as "NONE".

The DTD listing for this field is:   forceOutput %MFString; "NONE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: DoubleAxisHingeJoint, fields: anchorPoint, axis1, axis2

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#DoubleAxisHingeJoint, where the node signature lists the default for each of these fields as 0 0 0.

The DTD listings for these fields are:

                anchorPoint %SFVec3f; "0 1 0"

                axis1 %SFVec3f; "0 1 0"

                axis2 %SFVec3f; "0 1 0"

The "anchorPoint" field represents a location, and so the default should be "0 0 0".

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.

There is a Mantis issue covering the "axis1" and "axis2" fields. It is Mantis 788. Members can view this at http://www.web3d.org/member-only/mantis/view.php?id=788.

------------------------- 

Node: ElevationGrid, fields: xDimension, yDimension, height

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geometry3D.html#ElevationGrid, where the node signature lists the default for these fields as 0, 0, and [] respectively.

The DTD listings for these fields are:

                xDimension      %SFInt32; "2"

                zDimension      %SFInt32; "2"

                height          %MFFloat; "0 0 0 0"

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.

Mantis issue 872 (members can view that at http://www.web3d.org/member-only/mantis/view.php?id=872) covers this amendment.

-------------------------

Node: EspduTransform, fields: applicationID, eventApplicationID, munitionApplicationID

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#EspduTransform, where the node signature lists the defaults for all three  fields as 1.

The DTD listing for these fields are:

               applicationID %SFInt32; "0"

                eventApplicationID         %SFInt32;            "0"

                munitionApplicationID   %SFInt32;            "0"

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.

There is a Mantis issue for this, namely 795 (members can view this at http://www.web3d.org/member-only/mantis/view.php?id=795).

-------------------------

Node: GeoElevationGrid, fields: xDimension, yDimension, height

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#GeoElevationGrid, where the node signature lists the default for these fields as 0, 0, and [0 0] respectively.

The DTD listings for these fields are:

                xDimension      %SFInt32; "2"

                zDimension      %SFInt32; "2"

                height          %MFFloat; "0 0 0 0"

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.

Mantis issue 872 (members can view that at http://www.web3d.org/member-only/mantis/view.php?id=872) covers this amendment.

-------------------------

Node: HAnimJoint, field: stiffness

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/hanim.html#HAnimJoint, where the node signature lists the default as "0 0 0".

The DTD listing for this field is:   stiffness %MFFloat; "1 1 1"

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.

Mantis issue 1113 (members can view that at http://www.web3d.org/member-only/mantis/view.php?id=1113) covers this amendment.

-------------------------

Node: Layout, field: size

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/layout.html#Layout, where the node signature lists the default as "1 1".

The DTD listing for this field is:   size        %SFFloat;            "1.0"

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”. 

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.

-------------------------

Node: LinePickSensor, field: objectType

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#LinePickSensor, where the node signature lists the default as "ALL".

The DTD listing for this field is:   objectType         %MFString;         "ALL"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: MotorJoint, field: forceOutput

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#MotorJoint, where the node signature lists the default as "NONE".

The DTD listing for this field is:   forceOutput %MFString; "NONE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: PickableGroup, field: objectType

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PickableGroup, where the node signature lists the default as "ALL".

The DTD listing for this field is:   objectType         %MFString;         "ALL"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: PointPickSensor, field: objectType

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PointPickSensor, where the node signature lists the default as "ALL".

The DTD listing for this field is:   objectType         %MFString;         "ALL"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: PrimitivePickSensor, field: objectType

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PrimitivePickSensor, where the node signature lists the default as "ALL".

The DTD listing for this field is:   objectType         %MFString;         "ALL"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: ReceiverPdu, fields: applicationID, transmitterApplicationID

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#ReceiverPdu, where the node signature lists the defaults for both fields as 1.

The DTD listing for these fields are:

               applicationID %SFInt32; "0"

                transmitterApplicationID              %SFInt32;            "0"

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.

There is a Mantis issue for this, namely 795 (members can view this at http://www.web3d.org/member-only/mantis/view.php?id=795).

-------------------------

Node: RigidBody, field: finiteRotationAxis

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#RigidBody, where the node signature lists the default value as “0 0 0”.

The DTD listing for this field is: finiteRotationAxis              %SFVec3f;           “0 1 0”

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.

There is a Mantis issue covering this. It is Mantis 789. Members can view this at http://www.web3d.org/member-only/mantis/view.php?id=789.

-------------------------

Node:  ScreenFontStyle, field: pointSize

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/layout.html#ScreenFontStyle, where the node signature lists the default as “12.0”.

The DTD listing for this field is: pointSize                %SFFloat;            “1.0”

Another great spot, Holger. The XML schema and the JSON schema all agree with the abstract standard, and have default values of “12.0”. 

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.

-------------------------

Node: SignalPdu, field: applicationID

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#SignalPdu,  where the node signature lists the defaults for this field as 1.

The DTD listing for this field is: applicationID %SFInt32;   "0"

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.

There is a Mantis issue for this, namely 795 (members can view this at http://www.web3d.org/member-only/mantis/view.php?id=795).

-------------------------

Node: SingleAxisHingeJoint, field: forceOutput

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#SingleAxisHingeJoint, where the node signature lists the default as "NONE".

The DTD listing for this field is:   forceOutput %MFString; "NONE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: SliderJoint, field: forceOutput

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#SliderJoint, where the node signature lists the default as "NONE".

The DTD listing for this field is:   forceOutput %MFString; "NONE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: TransmitterPdu, field: applicationID

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/dis.html#TransmitterPdu, where the node signature lists the defaults for this field as 1.

The DTD listing for this field is: applicationID %SFInt32;   "0"

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.

There is a Mantis issue for this, namely 795 (members can view this at http://www.web3d.org/member-only/mantis/view.php?id=795).

-------------------------

Node: UniversalJoint, field: forceOutput

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#UniversalJoint, where the node signature lists the default as "NONE".

The DTD listing for this field is:   forceOutput %MFString; "NONE"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: VolumePickSensor, field: objectType

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#VolumePickSensor, where the node signature lists the default as "ALL".

The DTD listing for this field is:   objectType         %MFString;         "ALL"

Therefore, the DTD agrees with the standard. Why do you list the default as ' '?

-------------------------

Node: WindPhysicsModel, field: direction

See http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/particle_systems.html#WindPhysicsModel, where the node signature lists the default as “0 0 0”.

The DTD listing for this field is: direction %SFVec3f;           “1 0 0”

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”. 

There is a Mantis issue covering this point. It is Mantis 798, and is available to Web3D members at http://www.web3d.org/member-only/mantis/view.php?id=798.

-------------------------

All the best,

Roy

-----Original Message-----

From: Holger Seelig [mailto:holger.seelig at yahoo.de] 

Sent: 12 June 2017 09:22

To: X3D Graphics public mailing list <x3d-public at web3d.org>; Don Brutzman <brutzman at nps.edu>; Roy Walmsley <roy.walmsley at ntlworld.com>

Subject: Differences of default values between specification and dtd

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>

and the 3.3 dtd <http://www.web3d.org/specifications/x3d-3.3.dtd>.

The default values are not equal, thus it is not clear to me which values take precedence.

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.

The document attached and below list the affected fields showing the default values of the dtd. Please note the 'Volume rendering component' 

is still not verified.

Best regards,

Holger Seelig

<!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.3//EN" 

"http://www.web3d.org/specifications/x3d-3.3.dtd">

<X3D profile='Full' version='3.3' 

xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance' 

xsd:noNamespaceSchemaLocation='http://www.web3d.org/specifications/x3d-3.3.xsd'>

   <head>

     <meta name='title' content='NodeIndex.x3d'/>

   </head>

   <Scene>

     <Anchor/>

     <Appearance/>

     <Arc2D/>

     <ArcClose2D/>

     <AudioClip/>

     <Background/>

     <BallJoint

         forceOutput=''/>

     <Billboard/>

     <BooleanFilter/>

     <BooleanSequencer/>

     <BooleanToggle/>

     <BooleanTrigger/>

     <BoundedPhysicsModel/>

     <Box/>

     <CADAssembly/>

     <CADFace/>

     <CADLayer/>

     <CADPart/>

     <Circle2D/>

     <ClipPlane/>

     <CollidableOffset/>

     <CollidableShape/>

     <Collision/>

     <CollisionCollection

         appliedParameters=''/>

     <CollisionSensor/>

     <CollisionSpace/>

     <Color/>

     <ColorDamper/>

     <ColorInterpolator/>

     <ColorRGBA/>

     <ComposedCubeMapTexture/>

     <ComposedShader/>

     <ComposedTexture3D/>

     <Cone/>

     <ConeEmitter/>

     <Contact

         appliedParameters=''/>

     <Contour2D/>

     <ContourPolyline2D/>

     <Coordinate/>

     <CoordinateDamper/>

     <CoordinateDouble/>

     <CoordinateInterpolator/>

     <CoordinateInterpolator2D/>

     <Cylinder/>

     <CylinderSensor/>

     <DISEntityManager

         applicationID='0'/>

     <DISEntityTypeMapping/>

     <DirectionalLight

         global='false'/>

     <Disk2D/>

     <DoubleAxisHingeJoint

         forceOutput=''

         anchorPoint='0 1 0'

         axis1='0 1 0'

         axis2='0 1 0'/>

     <EaseInEaseOut/>

     <ElevationGrid

         xDimension='2'

         zDimension='2'

         height='0, 0, 0, 0'/>

     <EspduTransform

         applicationID='0'

         eventApplicationID='0'

         munitionApplicationID='0'/>

     <ExplosionEmitter/>

     <Extrusion/>

     <FillProperties/>

     <FloatVertexAttribute/>

     <Fog/>

     <FogCoordinate/>

     <FontStyle/>

     <GeneratedCubeMapTexture/>

     <GeoCoordinate/>

     <GeoElevationGrid

         xDimension='2'

         zDimension='2'

         height='0, 0, 0, 0'/>

     <GeoLOD/>

     <GeoLocation/>

     <GeoMetadata/>

     <GeoOrigin/>

     <GeoPositionInterpolator/>

     <GeoProximitySensor/>

     <GeoTouchSensor/>

     <GeoTransform/>

     <GeoViewpoint/>

     <ForcePhysicsModel/>

     <Group/>

     <HAnimDisplacer/>

     <HAnimHumanoid/>

     <HAnimJoint

         stiffness='1, 1, 1'/>

     <HAnimSegment/>

     <HAnimSite/>

     <ImageCubeMapTexture/>

     <ImageTexture/>

     <ImageTexture3D/>

     <IndexedFaceSet/>

     <IndexedLineSet/>

     <IndexedQuadSet/>

     <IndexedTriangleFanSet/>

     <IndexedTriangleSet/>

     <IndexedTriangleStripSet/>

     <Inline/>

     <IntegerSequencer/>

     <IntegerTrigger/>

     <KeySensor/>

     <LOD/>

     <Layer/>

     <LayerSet/>

     <Layout

         size='1'/>

     <LayoutGroup/>

     <LayoutLayer/>

     <LinePickSensor

         objectType=''/>

     <LineProperties/>

     <LineSet/>

     <LoadSensor/>

     <LocalFog/>

     <Material/>

     <Matrix3VertexAttribute/>

     <Matrix4VertexAttribute/>

     <MetadataBoolean/>

     <MetadataDouble/>

     <MetadataFloat/>

     <MetadataInteger/>

     <MetadataSet/>

     <MetadataString/>

     <MotorJoint

         forceOutput=''/>

     <MovieTexture/>

     <MultiTexture/>

     <MultiTextureCoordinate/>

     <MultiTextureTransform/>

     <NavigationInfo/>

     <Normal/>

     <NormalInterpolator/>

     <NurbsCurve/>

     <NurbsCurve2D/>

     <NurbsOrientationInterpolator/>

     <NurbsPatchSurface/>

     <NurbsPositionInterpolator/>

     <NurbsSet/>

     <NurbsSurfaceInterpolator/>

     <NurbsSweptSurface/>

     <NurbsSwungSurface/>

     <NurbsTextureCoordinate/>

     <NurbsTrimmedSurface/>

     <OrientationChaser/>

     <OrientationDamper/>

     <OrientationInterpolator/>

     <OrthoViewpoint/>

     <PackagedShader/>

     <ParticleSystem/>

     <PickableGroup

         objectType=''/>

     <PixelTexture/>

     <PixelTexture3D/>

     <PlaneSensor/>

     <PointEmitter/>

     <PointLight/>

     <PointPickSensor

         objectType=''/>

     <PointSet/>

     <Polyline2D/>

     <PolylineEmitter/>

     <Polypoint2D/>

     <PositionChaser/>

     <PositionChaser2D/>

     <PositionDamper/>

     <PositionDamper2D/>

     <PositionInterpolator/>

     <PositionInterpolator2D/>

     <PrimitivePickSensor

         objectType=''/>

     <ProgramShader/>

     <ProximitySensor/>

     <QuadSet/>

     <ReceiverPdu

         applicationID='0'

         transmitterApplicationID='0'/>

     <Rectangle2D/>

     <RigidBody

         finiteRotationAxis='0 1 0'/>

     <RigidBodyCollection/>

     <ScalarChaser/>

     <ScalarInterpolator/>

     <ScreenFontStyle

         pointSize='1'/>

     <ScreenGroup/>

     <Script/>

     <ShaderPart/>

     <ShaderProgram/>

     <Shape/>

     <SignalPdu

         applicationID='0'/>

     <SingleAxisHingeJoint

         forceOutput=''/>

     <SliderJoint

         forceOutput=''/>

     <Sound/>

     <Sphere/>

     <SphereSensor/>

     <SplinePositionInterpolator/>

     <SplinePositionInterpolator2D/>

     <SplineScalarInterpolator/>

     <SpotLight/>

     <SquadOrientationInterpolator/>

     <StaticGroup/>

     <StringSensor/>

     <SurfaceEmitter/>

     <Switch/>

     <TexCoordDamper2D/>

     <Text/>

     <TextureBackground/>

     <TextureCoordinate/>

     <TextureCoordinate3D/>

     <TextureCoordinate4D/>

     <TextureCoordinateGenerator/>

     <TextureProperties/>

     <TextureTransform/>

     <TextureTransform3D/>

     <TextureTransformMatrix3D/>

     <TimeSensor/>

     <TimeTrigger/>

     <TouchSensor/>

     <Transform/>

     <TransformSensor/>

     <TransmitterPdu

         applicationID='0'/>

     <TriangleFanSet/>

     <TriangleSet/>

     <TriangleSet2D/>

     <TriangleStripSet/>

     <TwoSidedMaterial/>

     <UniversalJoint

         forceOutput=''/>

     <Viewpoint/>

     <ViewpointGroup/>

     <Viewport/>

     <VisibilitySensor/>

     <VolumeEmitter/>

     <VolumePickSensor

         objectType=''/>

     <WindPhysicsModel

         direction='1 0 0'/>

     <WorldInfo/>

   </Scene>

</X3D>

--

Holger Seelig

Mediengestalter Digital – Digital Media Designer

Scheffelstraße 31a

04277 Leipzig

Germany

Cellular: +49 1577 147 26 11

E-Mail:   holger.seelig at create3000.de

Web:      http://titania.create3000.de

Future to the fantasy ★ ★

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170724/680f500b/attachment-0001.html>