could nextVal just as well die?

I'm in the process of whacking RDF/XML parsing/serialization into a 
shape where I can actually do regression tests on it. One of the things 
I'm whacking hard is parsing of containers, and now I see that our 
assertion of nextVal is pretty brittle. Looking at the mozilla codebase, 
it's hardly used, though, so I was wondering wether I should remove the 
nextVal arc alltogether, and just cache the nextVal integer inside the 
RDFContainer helpers.

That would help with some perf problems, and it would fix a cumbersome 
almost-spec problem (nextVal being in the RDF namespace).

Comments?

Axel