There are two different issues here. One is namespaces. In the example you
give, its just whether namespace validation is on or not. In the Xerces
parser its off by default, because it has associated overhead and lots of
people don't use it.
The issue being discussed was namespaces relative to DTDs. The point being
that you cannot just define element 'a' in your DTD had have the parser
recognize money:a as that element. It don't work that way. DTDs know nothing
of namespaces, becuase you cannot indicate in a DTD what namespace an
element belongs to. In order for namespace parsing to work, you must be able
to indicate that element 'a' is really '{http://whatever/boo.com}a', so that
the parser can check whether 'money:a' resolves to that fully qualified
name. Since there is no way to indicate what namespace URL a DTD element
belongs to, the DTD based validation cannot check for that.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: Boris Tarasyuk [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 7:57 AM
To: [EMAIL PROTECTED]
Subject: Re: namespaces and Valid XML
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
