Re: RS/RE, again (sorry)

>Fine. So in your opinion, should the "validator" be part of the XML 
>specification or not? 

Not part of the *language* specification.

I do think we need pGroves and validator behaviour defined though.

>If so, does it really matter what the "parser" returns?

Yes, because it is the *foundation* of the entire application
architecture. If it is not rigourously defined such that it
is trivial to prove it correct, no other part of the system can
be known to be correct. I like foundations of stone, not sand.

>Should we specify a single standardized validation scheme or not? If we do,
>what do you propose it should say about whitespace? If we do not, how can we
>claim to be even vaguly SGML compatible? As you mentioned in your last 
>message, SGML's validation scheme would be just one of an infinite number
>of equally "valid" schemes.

I propose two: a "pure" XML validator, which does no transformation,
of pGroves and another "SGML" validator, that removes whitespace 
according to "normal" SGML rules.

I am not against whitespace removal at the application level, but am
strongly against putting such functionality into the parser for the

Follow-Ups: References: