SPEC: isA field occurs first?, minor spec. clarifications...

I'm currently in the proci> of experimenting with writing some VRML parser
code. A few things have emerged from this:

1) Is there any requirement for the isA field to occur before other fields
(except perhaps for the 'fields' field)? It make there is such a requirement, as you don't need to store the values of all
fields as you parse an extension node. I have a feeling, looking at the
sample node might be a good idea to make it explicit in the 1.1 spec.

2) There appears to be a requirement for all fields to occur before
children in group node objectname objecttype { fields children } ) but it would be a good idea to
point this out explicitly. This property becomes very important if you
want to draw the scene as it comes in - if all fields are required to be
before children, you can draw a node as soon as all fields are read and
don't have to worry about, say, a situation like this:

Switch {
Separator { ... }
Separator { ... }
Separator { ... }

whichChild 2 # before this line is read which node do we draw?!
}

3) The MFString type, while being a logical extension to the SF/MF
convention, needs to be defined explicitly.

Comments, anyone?

On another topic, I seem to be getting a lot of duplicate li> s from
the list. Anyone have any ideas as to why?

Seeya,
Oliver

--
Oliver Jowett                         Student, programmer-at-large,
[email protected]   and occasional scuba diver...
--------Time flies like an arrow. Fruit flies like a banana.-------