OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Dereferencing a namespace URI {WAS: Success factors for the Weband S

[ Lists Home | Date Index | Thread Index ]
  • From: Uche Ogbuji <uche.ogbuji@fourthought.com>
  • To: Michael Fitzgerald <mike@wyeast.net>
  • Date: Thu, 21 Dec 2000 17:38:21 -0700 (MST)

> In Sean's defense, XML Schema does allow you to "attempt to resolve the
> namespace URI to locate such a [schema] resource." It is the last of five
> methods for dealing with a validating schema. [*]
> Eleven words in an official W3C document. A chink in the armor. A namespace
> URI, at least under XML Schema, is more than just an identifier!

Thanks for the reference.  But I don't think it addresses the issue.
Regardless of what some spec says should come back when you "access" a
URI, neither that spec nor those putting namespaces in their document have
any control of what actually _will_ come back in real life.

Again, what about URNs?  What about proxies?  What about DNS bandits?

Uche Ogbuji                               Principal Consultant
uche.ogbuji@fourthought.com               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS