(1)re: groups - after watching the debate surrounding this, I'd suggest
(sorry!)
comp.3d.vrml
Here's why: if the subject matter at hand spans both comp.infosystems and
comp.graphics AND if it is NOT a subset of either, then it should be more
generic. Furthermore, if we accept that VRML will find its way into non-web
and even non-computational paltforms, then 3d deserves a category of its own
(after all, that is the main objective, if I undeerstand things). Finally,
this would allow spaces for non-VRML groups to hold discussions while
remaining hierarchically related to VRML.
So...all those for comp.3d.vrml, say hey.
(2)re: sound
Again, please forgive my likely ignorance...this may be balderdash, or already
have long since discussed, but:
does each object require a sound-related specificity, or can this be inherited
from a class superset? eg, all trees are made of wood, and <wood> for the
purposes of VRML has a well-defined absorption/reflectivity value; houses are
made of glass, metal, etc, so although more complicated, at lease every like
surface would automatically inherit the same property, making for consistency;
etc.
Just a thought.
-Stuart Dambrot