[x3d-public] Number of nodes, standard vs X3DUOM

[Brutzman, Donald (Don) (CIV)]

Yes thanks for looking at the inventory of nodes and statements, that is an excellent sanity check.

The difference between v3.3 and v4.4 in the X3DUOM lists of ConcreteNodes and Statements is HAnimMotion node.  A diff shows that.  Also have attached a helpful diff display using XML-Spy showing that inventory differs by 1 node.

For anyone looking, all of these assets are in version control and published online at

	X3D Specifications: Schema and DOCTYPE Validation
	http://www.web3d.org/specifications

Not sure how rigorous the HTML document you attached might be - it has title X3D (Part 4: C++) language binding, which has not been formally reviewed by the working group yet.  Cursory inspection didn't reveal any mistaken entries.  Don't know if that page is manually edited (which is error prone for so many nodes) or autogenerated.  In general we have slowly been moving towards autogeneration of interface annexes like that, and such build scripts are in place already for X3D Java language specification.  We can do similar autogeneration of annexes for upcoming JSON and Python specifications.

Another set of useful autogenerated files which show all node names and default simple-type field values are

	http://www.web3d.org/specifications/AllX3dElementsAttributes3.3.xml
	http://www.web3d.org/specifications/AllX3dElementsAttributes3.3.txt

	http://www.web3d.org/specifications/AllX3dElementsAttributes4.0.xml
	http://www.web3d.org/specifications/AllX3dElementsAttributes4.0.txt

Excerpts:
------------------------------------------------------------------------------
<AllX3dElementsAttributes>
    <Anchor bboxCenter="0 0 0" bboxSize="-1 -1 -1" description="" parameter="" url="" containerField="children"/>
    <Appearance containerField="appearance"/>
    <Arc2D endAngle="1.570796" radius="1" startAngle="0" containerField="geometry"/>
------------------------------------------------------------------------------
<!-- All X3D elements and attributes, with default values, as defined in X3D Schema version 3.3 -->
    <Anchor bboxCenter='0 0 0' bboxSize='-1 -1 -1' description='' parameter='' url='' containerField='children'/>
    <Appearance containerField='appearance'/>
    <Arc2D endAngle='1.570796' radius='1' startAngle='0' containerField='geometry'/>
------------------------------------------------------------------------------

The attached diff between the .txt files reveals what nodes and fields have been added in X3Dv4.0 so far:  HAnimMotion node, and description field on the other HAnim nodes.

So our accounting is in good shape and we are progressing deliberately.  Next on TODO list, now that HAnim v2.0 is nearly done, will be the long-awaited ProgressiveTextureMapping component from Web3D Korea Chapter.  More to follow on review by X3D working group and community for that new component.

On 1/21/2019 3:16 PM, John Carlson wrote:
> If we added the list of statements to the concrete list, it would be close to the same.   Whew.
> 
> John
> 
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
> 
> *From: *John Carlson <mailto:yottzumm at gmail.com>
> *Sent: *Sunday, January 20, 2019 11:54 PM
> *To: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>; Don Brutzman <mailto:brutzman at nps.edu>
> *Subject: *Number of nodes, standard vs X3DUOM
> 
> Number of concrete nodes in the 3.3 standard = 251   WorldInfo is 3.250
> 
> ~/X3D/ISO-IEC 19777/ISO-IEC 19777-4/ISO-IEC
> 
> 19777-4 V3.3/ISO-IEC 19777-4 V3.3 CD/Part04
> 
> href="#X3D">C.3.251 X3D
> 
> WorldInfo is
> 
> ·C.3.234 WorldInfo <#WorldInfo>
> 
> In code generated from ConcreteNodes X3DUOM for 3.3 is 234
> 
> WorldInfo is
> 
> ·C.3.235 WorldInfo <#WorldInfo>
> 
> In code generated from ConcreteNodes  X3DUOM for 4.0 is 235
> 
> I am concerned that the figure for X3DUOM 3.3 is so distant from the standard.
> 
> Files I am working with included.
> 
> If more detail is needed, let me know.

Again thanks for checking on that.

One outcome of this week's meetings is that we will soon be making a list of available X3Dv4 implementation assets.

> Will we be moving X3Dv3.3 backwards when X3dV4 comes out?

Not sure what you mean by that?  X3Dv3.3 is stable.

We do not intend to pursue any modifications to that ISO specification, focusing efforts on X3Dv4.  When internal changes to XML schema, X3DUOM and DTD are possible for X3Dv3.0 through v3.3 that maintain long-approved scene content with improved validation power, they are applied.  This also helps us maintain consistent validation assets and perform validation tests if X3D Examples Archive scenes at all versions of X3D.

Have fun with X3D v3.3 and v4.0!  8)

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: X3duom3.3Diff4.0ConcreteNodesStatements.png
Type: image/png
Size: 374333 bytes
Desc: X3duom3.3Diff4.0ConcreteNodesStatements.png
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190121/19d52d10/attachment-0001.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: AllX3dElementsAttributes3.3Diff4.0.diff
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190121/19d52d10/attachment-0001.ksh>