[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Entity resolution vs. URI resolution

• To: "'xml-dev@l...'" <xml-dev@l...>
• Subject: RE: Entity resolution vs. URI resolution
• From: "Arnold, Curt" <Curt.Arnold@h...>
• Date: Fri, 25 Jan 2002 10:33:49 -0700

Schema location resolution is not just a special case and is more complex
than just URI redirection.  An application would typically want to locate a
schema resource by the namespace URI or the namespace URI plus some
additional information (such as the version attribute on an <xsl:transform>
element) and ignore any xsi:schemaLocation hint.

Since schema validation augments the infoset, it is necessary (or at least
useful) to resolve the location during the parsing of the document.

Sandy Gao, others and I had a very long discussion on this on the
Xerces-J-Dev mailing list in August 2001
(http://archive.covalent.net/xml/xerces-j-dev/2001/08/0119.xml and
following).  I believe that most of that got reflected in the Xerces-J 2's
schema resolution interfaces, but I haven't really followed it.

Basically, my take was that the parser should throw an event when it
encounters content that it cannot find an existing schema resource to
handle.  The handler should have access to any previously encountered
xsi:schemaLocation, the namespace URI and local name of the content that
caused the event and the untyped content of the start tag (so that you could
use something like an version attribute).

• Follow-Ups:
  • Re: Entity resolution vs. URI resolution
    • From: Edwin Goei <edwingo@s...>
  • Re: Entity resolution vs. URI resolution
    • From: David Brownell <david-b@p...>

• Prev by Date: Re: Push and Pull?
• Next by Date: Re: Push and Pull?
• Previous by thread: CALL FOR PAPERS and PARTICIPATION: Business Agents and the Semantic Web (BASeWEB)
• Next by thread: Re: Entity resolution vs. URI resolution
• Index(es):
  • Date
  • Thread