We have no draft proposal yet, but here is a list
of topics which might be covered in such a proposal
- Inheritance, Classes (multiple inheritance
or single inheritance with interfaces as in Java)
- a class hierarchy for the standard nodes of VRML 2.0
- Methods, Eventhandling vs. ROUTES
- Type System, Polymorphism, Dynamic Binding
- Abstracting Routing Structures
- Templates as in C++
To guide the design of the extensions there are several applications
which should be taken into consideration:
- multi-user environments
- animations
- libraries of objects and behaviors
- authoring tools
- practical experiences with authoring worlds in VRML 2.0
When it comes to implementing the extensions, we
have several options:
- To what extent can object-orientedness be
provided by basic prototypes and JAVA classes?
- Which extensions can be handled by a preprocessor?
- Are there essential extensions which need
support from VRML 2.0 or its External-Authoring
Interface, which is not present in the
current specifications?