> The alternative, is that VRML grows to have some behaviors, but does not
> become the distributed object action broadcast standard. VRML stays as
> a rich graphics language that is the graphics part of "the matrix." In that
> case,
> c.g.vrml is more appropriate.
But what about sound? That suggests comp.audio.vrml. Why not
comp.dcom.tcpip, since the Internet runs on TCP/IP, and much of VRML will
run on the Internet?
I think comp.infosystems.vrml is best, because vrml will be used to
display information through a distribution system. Maybe comp.vrml, since
vrml kind of combines a lot of diffewrent areas.
> Can we postpone the newsgroup until we set the architectural direction for
> VRML 2.0?
I think we should. I mean, we just came up with the idea of "sound". What
else is there we need to discuss?
---
Andrew C. Esh mailto:[email protected]
Computer Network Technology [email protected] (finger for PGP key)
6500 Wedgwood Road 612.550.8000 (main)
Maple Grove MN 55311 612.550.8229 (direct)
<A HREF="http://www.mtn.org/~andrewes">ACE Home Page</A>