[x3d-public] Issue: X3D V4 Functionality

Limper, Max max.limper at igd.fraunhofer.de
Thu Jul 9 15:25:15 PDT 2015

I really like the idea of identifying "convenience nodes"!

This should help us to define a minimal subset for HTML. X3DOM already has some nodes that are not really necessary, so it could make sense to also check X3DOM for convenience nodes that could be removed from the HTML Profile.


Am 09.07.2015 3:23 nachm. schrieb doug sanden <highaspirations at hotmail.com>:
> How do we determine what should be in the HTML Profile of X3D V4?
Option 1: if a node can be automatically generated from another node, then its a convenience node
In desktop x3d some nodes are 'convenience' nodes. Extrusions simplify indexedfacesets.
One thought is to eliminate all convenience nodes from html profile, if a transform can be done automatically:
convenience node -> automatic transform -> primitive node

Then if someone has a desktop x3d scene, they can upload it to a cloud facility that automatically converts it to html profile compliant.

Option 2: As-is
The gurus working on x3dom invested their time and life, and they want to make it popular/a success,, and their judgement about tradeoffs can be trusted, so ask them. Or -since their judgement went into the current distro of x3dom- simply document the current distro as the defacto x3d html standard.

I suspect unlike native browsers, there will be few ground-up competitors to x3dom, so when you are documenting standards, its primarily for authoring tools.

x3d-public mailing list
x3d-public at web3d.org

More information about the x3d-public mailing list