• From: Liam R E Quin <liam@w...>
• To: Jirka Kosek <jirka@k...>
• Date: Mon, 23 Apr 2012 16:28:47 -0400

On Mon, 2012-04-23 at 12:31 +0200, Jirka Kosek wrote:

> Might be I'm not understanding you correctly Liam, but IMHO namespace
> URI is perfect way to *indirectly* say where the schema is located.
> 
> Good XML application support mapping file where namespace URI can be
> mapped to schema which should be used for validation.

Yes, that aspect is fine. Blindly dereferencing the namespace and
expecting to find a schema there is what I was saying is not fine.

> In theory on namespace URI could reside RDDL document which can point to
> XML schema, but past experience with heavy loaded network resources
> (XHTML DTDs) shows that's not wise to depend on such approach in an
> application.

The XML Plenary failed to get consensus on whether it was acceptable to
define anything at a namespace URI, or even if it was OK to try to
dereference them.

If applications did start, you're right, W3C would have to block the
ones on our servers, as we have to do for the DTDs and XSD files.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/

• References:
  • If I want to use catalogs for XSDs, must document instances contain aschemaLocation?
    • From: "Graham Hannington" <graham_hannington@f...>
  • Re: If I want to use catalogs for XSDs, must documentinstances contain a schemaLocation?
    • From: Liam R E Quin <liam@w...>
  • Re: If I want to use catalogs for XSDs, must document instancescontain a schemaLocation?
    • From: Jirka Kosek <jirka@k...>