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: Michael Mealling <michael@bailey.dscga.com>
  • To: Uche Ogbuji <uche.ogbuji@fourthought.com>
  • Date: Thu, 21 Dec 2000 20:04:44 -0500

On Thu, Dec 21, 2000 at 05:38:21PM -0700, Uche Ogbuji wrote:
> > 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?

The intent for things like this from the IETF side is to use something
like RESCAP to determine if the URI in question has the capabilities
you desire.... Its a two stage process but its one that can give you
the granularity you need before you ever actually access the Resource
being identified by the URI....

Now its just a matter of putting the final touches on the RESCAP protocol...


Michael Mealling	|      Vote Libertarian!       | www.rwhois.net/michael
Sr. Research Engineer   |   www.ga.lp.org/gwinnett     | ICQ#:         14198821
Network Solutions	|          www.lp.org          |  michaelm@netsol.com


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

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