I don't see the main application of common objects, classes and property sets
in bandwidth reduction - most people will want to design their own objects
anyway.
But common concepts about the nature of objects are needed for any reasonable
implementation of interactive VRML. The only way to handle a hot teapot without
a common notion of the terms 'hot' and 'teapot' in the VRMLworld would be
trial-and-error, which I don't consider feasible in a world where everything
could have any possible shape.
Sevo
-- Sevo Stille [email protected] Visuals & Interfacing Department [email protected]Institut fuer Neue Medien Tel: ++49 (69) 94196314 Daimlerstrasse 32 Fax: ++49 (69) 94196322 D 60314 Frankfurt a.M.