W3C home > Mailing lists > Public > xml-uri@w3.org > June 2000

Re: A proposed solution

From: Clark C. Evans <cce@clarkevans.com>
Date: Sat, 10 Jun 2000 13:20:58 -0400 (EDT)
To: James Clark <jjc@JCLARK.COM>
cc: David Turner <dturner@microsoft.com>, "'XML-uri@w3.org'" <XML-uri@w3.org>, Henrik Frystyk Nielsen <henrikn@microsoft.com>, Andrew Layman <andrewl@microsoft.com>
Message-ID: <Pine.LNX.4.10.10006101313360.14989-100000@clarkevans.com>
On Sat, 10 Jun 2000, James Clark wrote:
> If multiple levels of hierarchy count as the same context, then this
> proposal does not solve the problem.

...

> 1. A1 is character for character identical to A2, and
> 
> 2. either
>    (a) A1 and A2 are absolute, or
>    (b) both
>       (i)  A1 and A2 are relative, and
>       (ii) C1 and C2 are character for character identical
> 

...

> A. cases where namespace names are identical but the corresponding
> resources are not
> 
> B. cases where namespace names are not identical but the corresponding
> resources are
> 
> Now type B cases are relatively harmless and an unavoidable fact of
> life, but type A cases are (to some of us anyway) unacceptable.  The
> Microsoft proposal appears to be getting rid of type A mismatches by
> accepting additional type B mismatches.

Consider the following directory...

  /home/
  /home/xsl/
  /home/xsl/test.xsl
  /home/xml/
  /home/xml/test.xml

  Let test.xml := "<x:x xmlns:x="test"/>
  Let test.xsl contain "xmlns:x="test"  and  "<template match='x:x'>"

  Run, from the /home directory,
   
    "xt xml/test.xml xsl/test.xsl"

In the "literal" interpretation, this would match just perfectly.

However, in the above proposal, this is one of those "additional
type B mismatches" ?

Just checking,

Clark
Received on Saturday, 10 June 2000 13:15:05 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Tuesday, 12 April 2005 12:17:25 GMT