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

RE: XPath/XSLT 2.0 concerns

• To: <michael.h.kay@n...>,"J.Pietschmann" <j3322ptm@y...>,"Jeni Tennison" <jeni@j...>
• Subject: RE: XPath/XSLT 2.0 concerns
• From: "Dare Obasanjo" <dareo@m...>
• Date: Thu, 3 Oct 2002 12:02:14 -0700
• Cc: <xml-dev@l...>
• Thread-index: AcJrDZJDQSGGl+WkTai6x5cEHhvftwAAXdb2
• Thread-topic: XPath/XSLT 2.0 concerns

Furthermore attempts at static guarantees tend to give undesirable results once XML Schema features like type derivation and substitution groups enter the picture. 

	-----Original Message----- 
	From: Michael Kay [mailto:michael.h.kay@n...] 
	Sent: Thu 10/3/2002 11:22 AM 
	To: 'J.Pietschmann'; 'Jeni Tennison' 
	Cc: xml-dev@l... 
	Subject: RE:  XPath/XSLT 2.0 concerns
	
	

	> 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
	
	
	-----------------------------------------------------------------
	The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
	initiative of OASIS <http://www.oasis-open.org>
	
	The list archives are at http://lists.xml.org/archives/xml-dev/
	
	To subscribe or unsubscribe from this list use the subscription
	manager: <http://lists.xml.org/ob/adm.pl>
	
	

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