[X3D-Public] Contour2D containerField analysis

Michalis Kamburelis michalis.kambi at gmail.com
Mon Sep 2 08:20:28 PDT 2013


Brutzman, Donald (Don) (CIV) wrote:
> Apologies for being relatively quiet. Thanks for the dialog.
>
> Here is a Contour2D analysis regarding the XML encoding. Warning: kinda
> long (welcome to the wild and wonderful world of DTD/Schema forensics!)
>
> 1. When Annex 6 says containerField="geometry" it is describing the
> default value, not a required value.
>
> However this version (official draft but old) document appears to be
> incorrect; more to follow.
>
> http://www.web3d.org/files/specifications/19776-1/V3.3/Part01/EncodingOfNodes.html#NurbsCurve2D
>

Many thanks for the detailed analysis. To summarize, the proper behavior 
of X3D browser (the intended behavior, forgetting for a second about 
spec errors) should be this:

1. Contour2D should be derived from X3DNode, not X3DGroupingNode
2. Contour2D.containerField should be by default "trimmingContour"
3. NurbsCurve2D.containerField should be by default "children"

Right?

I checked view3dcene, we already had point 1 and point 2 right. Now I 
changed NurbsCurve2D.containerField to be by default "children", so we 
have point 3 right too.

Vincent: this means that the warning "Unknown X3D field name (indicated 
by containerField value) "geometry" by node "NurbsCurve2D" inside node 
"Contour2D"" for 
http://www.web3d.org/x3d/content/examples/Basic/NURBS/NurbsTrimmedSurface.x3d 
is now gone. You can try view3dscene from snapshots 
http://michalis.ii.uni.wroc.pl/castle-engine-snapshots/ to test it 
immediately.

Regards!
Michalis



More information about the X3D-Public mailing list