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

Re: XPath/XSLT 2.0 concerns

• To: Paul Prescod <paul@p...>
• Subject: Re: XPath/XSLT 2.0 concerns
• From: Robin Berjon <robin.berjon@e...>
• Date: Wed, 02 Oct 2002 17:42:48 +0200
• Cc: xml-dev@l...
• Organization: Expway
• References: <72RLYT04POLJXV95A7FBMJXRM82TRVT.3d9a6f4c@MChamp> <144498584266.20021002103555@j...> <3D9B0101.4020504@t...> <3D9B0CB4.6010207@p...>
• Reply-to: robin.berjon@e...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

Paul Prescod wrote:
> Tim Bray wrote:
>> The problem with that wordview is that Xpath/Xquery are clearly mostly 
>> going to be used at application run-time.  I think the proportion of 
>> cases where XMLSchema validation happens at application run-time is 
>> going to be way short of 100%.  I personally think's actually going to 
>> be way short of 25%, it's useful for design support and debugging but 
>> it's just not at the right level for business-logic validation.
> 
> There is a faith out there that schemas are the right way to bootstrap 
> from the world of dynamically typed XML to the world of statically typed 
> C# and Java. It is thought that this will enhance, rather than degrade 
> performance by pushing type conversion from application logic down into 
> infrastructure. I don't personally believe this myself but I think that 
> you need to understand it to understand the schema mindset.

I don't believe that either and I'd add that it takes a pretty narrow 
view on XML but I can in fact see use cases for having access to types 
in XPath. For instance when I see an XSLT processor chew for several 
minutes on a very predictable document (granted, it's Java based, but 
still) I think that if it had access to schema information it could 
optimize a lot of what it's doing by skipping entire subtrees.

My issue here is that typing should be an option, available to those 
that want it but not enforced upon others. XML Schema has too many 
issues to be enforced upon anyone wishing to implement simple XPath.

-- 
Robin Berjon <robin.berjon@e...>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488

• Follow-Ups:
  • Re: XPath/XSLT 2.0 concerns
    • From: Paul Prescod <paul@p...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Jeni Tennison <jeni@j...>

• References:
  • Re: XPath/XSLT 2.0 concerns
    • From: Mike Champion <mc@x...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Jeni Tennison <jeni@j...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Tim Bray <tbray@t...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Paul Prescod <paul@p...>

• Prev by Date: RE: XPath/XSLT 2.0 concerns
• Next by Date: RE: XPath/XSLT 2.0 concerns
• Previous by thread: RE: XPath/XSLT 2.0 concerns
• Next by thread: Re: XPath/XSLT 2.0 concerns
• Index(es):
  • Date
  • Thread