RE: essential test cases?

> >OK, to clarify:
> >
> >I think that XSLT should treat them as equal if they are literally equal.
> >This is not what the XPath spec says, but it seems that all current
> >implementations work this way and (many? most?) people are happy
> with this.
> >So I would suggest to bring XPath in line with the Namespace rec.
> >
>
> In what sense do you feel that XSLT sees whether "they are the same or
> different"?

Hmmm, is that question directed at me?

> It seems to me that users of XSLT should have the opportunity to select on
> a class that they both match or to select on two classes that distinguish
> the two, as they please.
>
> If the InfoSet contains both the literal attribute and the BASE for the
> context, can one do that?

Seems to me that maybe there should be *two* XPath functions
(namespace-uri() and namespace-name(), where the latter would return the
literal value).

> I agree that the hardwired "absolutize" functionality in XPath should be
> removed.  My rationale was too mystical for Jon Cowan but I stand by it.
> The abolutizing transformation is purely textual, but it ain't _XML_
> syntax.  It's URI stuff.  And because the BASE can be inherited from
> non-syntactic application contexts, it isn't reallly syntactic at all.
>
> XPath should give paths terminating at everything in the InfoSet.  Should
> not keep you from addressing the literal attribute value.

At least it must allow to access the literal value if the namespace REC is
not changed...

Julian

Received on Wednesday, 14 June 2000 16:18:30 UTC