[x3d-public] Call to Progress on X3D V4

[Joe D Williams]

Hi Doug,

> If x3dom node definitions are not proprietary ...

Please have a look at the x3dom web pages. Most all of the nodes use 
standard X3D definitions but there are a couple of new (favorite) 
ones. I think the plan is to bring new ones in via V4. This is all 
xhtml or xml or html but uses the X3D XML encoding. Of course this is 
the way I like it to be because I can just use normal X3D XML encoding 
pasted into the html to make the scene. Also, the same code would run 
in a standalone tool, like BSContact and other vrml/X3D browsers. I 
think the biggest break we are having is that the DOM is improving 
through evolution so that it finally has the power to be compatible 
with a really realtime event system.

So just go ahead and play with the X3D. It is easy to find a free one 
that you can use with a simple text editor to compose the user code. 
Or, use the html browser, like for x3dom or cobweb. I think you can be 
sure that if you study X3D you will learn all the basics for the types 
of data and events required to construct a running scene. Then you can 
evaluate any other syntax of animated graphics you might find.

Best Wishes,
Joe







----- Original Message ----- 
From: "doug sanden" <highaspirations at hotmail.com>
To: <x3d-public at web3d.org>
Sent: Thursday, January 14, 2016 8:17 AM
Subject: Re: [x3d-public] Call to Progress on X3D V4


> 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.
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org