I also think the "browser" vs. "author/editor" is an interesting
point. I've only recently begun reading the VRML list mail, so I
apologize if this issue has been hashed over thoroughly earlier. But,
it seems to me that VRML specification poses a possibly significant new
direction from "traditional Web browsers" (:-). Mosaic, et al, are
primarily (though certainly not 100%) just that -- browsers, i.e.,
"look, but don't touch".
However, many in the VR field would say "look, but don't touch" apps
aren't "real" VR (which expands to the truly oxymoronic phrase "real
virtual reality"). User interaction with the virtual environment
(i.e., editing) is one of the main distinguishing features of VR
relative to apps that have been around for a decade or two and that
merely let one examine or navigate through a 3D geometric database.
So, my point is: Should there really be such a thing as a "virtual
world browser"? If so, does that imply that a VR browser isn't true or
complete VR? And, if that is so, what should the paradigm be for using
Web links to virtual world databases that we can not only visit
(browse) but interact with (edit) as well. Perhaps two paradigms are
needed: a passive browser as well as some kind of an active
interaction system. My personal opinion is that the analogy of
Mosaic-like links to Web pages is insufficient when extended to VR.
History has shown that extending 2D graphics paradigms to 3D graphics
has rarely produced the best result (e.g., CORE and GKS).
Lew Hitchner
Virtual Reality and Visual Simulation Consultant
Mountain View, CA
Voice: 415-964-9425
FAX: 800-825-7689 (USA)
FAX: 510-472-6951 (international)
email: [email protected]
URL: ftp://ftp.netcom.com/pub/hitchner/hitchner.html