> HTML documents ARE, generally, static. VRML documents SHOULD BE,
> generally, dynamic. I believe part of the initial specification should
> require some kind of scripting ability. I'm not so sure, however, that
> the MEME language is it, however. To my mind, the language should
> fulfill these criteria:
>
> 1) Interpreted.
> 2) Standard, if possible.
> 3) Easily implementable and/or Fairly portable
> 4) Object Oriented
I'm not at all convinced that a language is required in the specification (or
even in VRML); but I do think that some form of object manipulation interface
would be useful and not very difficult to spec out; IMHO this should allow an
external application to create objects, read/write their properties ("attributes"
and/or sub-objects), receive events (and hopefully property changed
notifications), and destroy objects.
Given the existance of such an interface, it's not so hard to bind any existing
or future language to a VRML implementation, thus avoiding the task of
specifing an interaction language and providing an incredibly high degree of
flexibility.
-- Mike