[x3d-public] Call to Progress on X3D V4

[doug sanden]

Joe,
If x3dom node definitions are not proprietary -if they are web3d.org- then why doesn't Leonard just snapshot x3dom node definitions and call it version 4?
-Doug
more..
PS if there's a difference between dom and classic, I would prefer a separate numerical series for the DOM vs Classic, since cobweb can do classic in a browser, and we may need more revisions of classic.
ie 
classic v3.4 -> v4 v5 ...
dom v1.0 ... or start dom at 4, and call it dom 4
OR
classic v1 v2 v3 v4 v5
dom  .............\ v4 v5
more..
4 hypotheses for delay in v4/dom:
H0: proprietary blockage
H1: resistance from classic supporters not wanting their numerical series cut off
H2: desire by standards designers to add some value, beyond copy and pasting, and no broad support for it
H3: confusion over what is standardizable wrt dom: node definitions vs. browser functionality. I gather the standard would cover the node definitions as seen by exporters, but not how wrapped in the html file for a particular dom-based browser implemention.