The CORBA specifications will be helpful in deciding on implementation
decisions,
but not in describing VRML itself.
What needs to occur if you want to describe the topology in an object-hierarchy
is to describe the behavior of the objects in question (or the interface
and types).
A "behavioral model" will need to be created. A client would
just interpret the script and behave according to it's own environment. We
basically would be creating an SQL for VR.
An example of a work in progress of something like this is the Open Geodata
Interoperability Specification (OGIS) project. This is creating a
behavioral model
for the distributed processing of spatial data. The clients in this case
are GIS's.
OGIS info:
Home Page: http://ginko.cecer.army.mil:8000
Page Of Particular Interest:
http://ginko.cecer.army.mil:8000/~liberte/OGIS/space.html
>
> Rick Duffy, Martin Marietta Astronatics
> duffy@den.mmc.com or rduffy@nyx.cs.du.edu
..........................................................................
Sam Gustman tel - (603) 646-4711
Computer Engineer email: samg@hanover-crrel.army.mil
QBE Entertainment, Inc. and
Amblin Studios
..........................................................................