However, I still see a difference between an extension, which is *very* clearly declared as violating the SPEC and turned on the users behalf only and the addition of a "nil" element without further notice.
In my post yesterday, I was not referring to null values as in "<null/>" or "<nil/>", but rather to values such as "<int/>", and "<boolean/>". Should these values be considered valid?
Even if these are not valid, shouldn't the library be lenient about what values it accepts, for inter-operability sake? I find it endlessly frustrating when the parser stops everything in it's tracks when communicating with remote software that I have no control over, just because that software has a slightly different interpretation of the spec.
--
Steve
------------------------------------------------------------
"Always ... always remember: Less is less. More is more. More is
better. And twice as much is good too. Not enough is bad. And too
much is never enough except when it's just about right."
-- The Tick
------------------------------------------------------------
