[x3d-public] Purpose of X3D

[doug sanden]

> 
>  1) X3D is for static models only (no texture). This is a very good
>  match. There are just a few things that X3D doesn't handle and most of
>  those are having to deal with interchange with other formats.

.web3dit image file format
I have a text-only image format .web3dit (i=image t=text (vs xml or json)) I could donate. Handles 2D, cube and 3D textures. Then web3d would have its own image format too. (Its really just pixeltexture in a separate file, with a few tricks). I use it for round-trip testing. But if you are desparate for web3d to own texture file formats it might be a good starting point.
https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/opengl/LoadTextures.c
L.620-905

> 
> Given that we have maybe 7 part time people (right now) where does X3D
>  go?
> If you have other
>  contributions, please feel free to state so along with what you think
>  it would take to get there from X3D V3.3.

IDEA: onus shifting: When someone proposes something new, they also submit refactored specs.
For example if I propose a change to rendering modulation, Protos_II, .web3dit image file format - I would need to also submit refactored specs pages that show how the old would keep working/stay valid in specs, while allowing the new.