Probably they do 'nonstandard validation'. But you don't
need turn on it explicitly. IE can recognize it. This is example:
1. <TEST AT1 = "ff" xmlns:money = "urn:Finance:Money">
<money:a>content text</money:a>
</TEST>
Validation correct. Namespace is declared
2. <TEST AT1 = "ff" >
<money:a>content text</money:a>
</TEST>
Validation failed. Namespace is not declared
>
> Sorry, but it explicitly violates the XML spec's definition of validity,
so
> if they're claiming to be a validating XML parser it really is a bug.
>
> (If they did this nonstandard validation only when you explicitly turned
on
> a custom switch which put the parser into an explicitly incompatable mode,
> _then_ they could claim it was a feature. But then they wouldn't really be
> validating XML, they'd be validating against some custom language which
> just happened to look like XML.)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
