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

RE: XPath/XSLT 2.0 concerns

• To: "'J.Pietschmann'" <j3322ptm@y...>,"'Jeni Tennison'" <jeni@j...>
• Subject: RE: XPath/XSLT 2.0 concerns
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Thu, 3 Oct 2002 19:22:32 +0100
• Cc: <xml-dev@l...>
• Importance: Normal
• In-reply-to: <3D9C79B5.70708@y...>
• Reply-to: <michael.h.kay@n...>

> I just had an example where writing 
> select="output" instead of select="outputs/output" had cost 
> me two full days :-\.
> 

I think that catching what I call "void path expressions" is one of the
big potential advantages of binding a stylesheet to a schema.
Unfortunately, while a lot of the type inferencing machinery is in place
to do it, the last few links in the chain aren't there yet. In
particular, it can only work in a template rule that is associated
firmly with a schema type. So long as you are allowed to construct
non-valid temporary trees and then process them using the same template
rules as you use for the source document, there's no way of knowing
statically what path expressions are guaranteed to be void.

Michael Kay

• Follow-Ups:
  • Re: XPath/XSLT 2.0 concerns
    • From: "J.Pietschmann" <j3322ptm@y...>
  • Re: RE: XPath/XSLT 2.0 concerns
    • From: Mike Champion <mc@x...>

• References:
  • Re: XPath/XSLT 2.0 concerns
    • From: "J.Pietschmann" <j3322ptm@y...>

• Prev by Date: Re: Are hyperlinks presentation or content?
• Next by Date: Re: RE: XPath/XSLT 2.0 concerns
• Previous by thread: Re: XPath/XSLT 2.0 concerns
• Next by thread: Re: RE: XPath/XSLT 2.0 concerns
• Index(es):
  • Date
  • Thread