[x3d-public] v5 > DOM EAI for v3

[doug sanden]

A fuzzy idea is to take the idea of EAI Scene Authoring Interface and invert it, so that DOM based nodes are a subset / selection of all nodes in a scene. Then a v5 DOM node set would be a v4-like subset of all nodes in a v3 scene: just the ones selected  for exposure to DOM scripting. EAI would be much like SAI in V3, putting nodes in fields of a script node to expose them to the script.


Instead of  v4 (in html / dom)
<X3D>
<Scene>
<nodes/>
</Scene>
</X3D>


 it would be v5
<X3D>
<Script>
<exposed nodes or more precisely DOM wrappers/interfaces on subset of nodes in  v3 Scene/>

(url script is in html head, and can programmatically create nodes, instance pre-defined protos, traverse whole scenegraph via js SAI, as v3 EAI can , or just program against DOM exposed nodes like v3 SAI via script node)

</Script>
<v3Scene - DOM-opaque nodes />
</X3D>

thread synchronization issues have already been dealt with in V3-  EAI.

-Doug