We are looking for existing solutions which may serve as a basis from which
VRML can be built. We are asking ANY list members who have used one of
these systems to contribute to a knowledge-base we are building. Once this
knowledge base exists, all list members will be able to examine it, and from
this, select a VRML base technology, if any are suitable.
VRML must be built upon a platform-independent language which is capable
of describing both the shape and visual qualities of three-dimensional
VRML must be able to create a "scene" where these objects can be arranged.
Finally, these objects must be capable of becoming "anchors" to data
Those are the ONLY basic specification requirements.
The language should be non-proprietary, although this should not restrict
suggestions; we may be able to learn from the useful parts of a proprietary
system for use in our own designs.
We expect that, in further revisions, VRML will become an "active" language,
and that objects in VRML environments will express dynamic behaviors. Any
suggested solution must also be considered this light.
WHAT YOU SHOULD SUBMIT:
While perhaps bounded by plenty of real-world experience, personal opinions
are more useful in the discussion phase (which follows the request for
information) than they are during the ROI phase. We are looking for
CONCRETE, COMPLETE PROPOSALS/SPECIFCATIONS which define existing systems.
Please try to get us _as much_ data as you can about a particular system.
Send us a URL, or, if need be, send us the data itself. We will be
compiling a database that all list members will have access to, so that we
can make an informed decision _together_.
We would like to complete the investigation process in two weeks.
We will consider the submissions period open from 12 June to 26 June 1994.
HOW TO REPLY:
In the interests of keeping LIST TRAFFIC as LOW as possible, we ask that
contributors SEND their CONTRIBUTIONS DIRECTLY to list moderator Brian
Behlendorf (firstname.lastname@example.org). Brian will take the contributions, edit them
down, and post daily or twice-daily digests of the contributions. DO NOT
POST YOUR CONTRIBUTIONS TO THE LIST.
Thanks for your help!
Mark D. Pesce (email@example.com)
Brian Behlendorf (firstname.lastname@example.org)