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

Re: XPath/XSLT 2.0 concerns

• To: robin.berjon@e...
• Subject: Re: XPath/XSLT 2.0 concerns
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Fri, 4 Oct 2002 08:35:46 -0400
• Cc: xml-dev@l..., public-qt-comments@w...
• In-reply-to: <3D9D882C.1020605@e...>
• References: <72RLYT04POLJXV95A7FBMJXRM82TRVT.3d9a6f4c@MChamp><144498584266.20021002103555@j...><3D9B0101.4020504@t...> <3D9B0CB4.6010207@p...><3D9B13F8.20608@e...> <12522921521.20021002172133@j...><3D9B2667.1050004@e...> <p04330100b9c3317a3b5a@[192.168.254.4]><3D9D882C.1020605@e...>

At 2:23 PM +0200 10/4/02, Robin Berjon wrote:

>The document needs to be type-decorated, which isn't much different 
>from validated in the case of XML Schema, so yes in the normal case 
>you will have a performance hit that will most likely be higher than 
>what you gain in msot cases.
>
>In the case I am considering however, the document can only be valid 
>because it has been binary encoded using a schema, and it won't 
>encode if it ain't valid.


OK. That may make sense for you, but it seems a very weird and 
unusual use-case. If this is accurate, I don't think the cost of 
complexifying the XPath 2.0/XQuery specs with schema awareness vastly 
outweighs the benefit to strange applications that want to binary 
encode documents according to a schema.

And since I'm ccing this to the W3C comments list, let me state 
formally that I think the XPath 2.0/XQuery 2.0 should not add any 
complexity in order to support this experimental use-case. I think 
the current drafts are vastly too complex as a result of this, and 
need to be radically simplified before recommendation, probably by 
removing type-support and schema-awareness completely. The 
implementation experience does not yet exists to decided whether this 
is useful or even possible. It's better to let this stuff be 
experimented with before anybody attempts to standardize it.
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@m... | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          XML in a  Nutshell, 2nd Edition (O'Reilly, 2002)          |
|              http://www.cafeconleche.org/books/xian2/              |
|  http://www.amazon.com/exec/obidos/ISBN%3D0596002920/cafeaulaitA/  |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |
+----------------------------------+---------------------------------+

• Follow-Ups:
  • Re: XPath/XSLT 2.0 concerns
    • From: Robin Berjon <robin.berjon@e...>

• 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...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Robin Berjon <robin.berjon@e...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Jeni Tennison <jeni@j...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Robin Berjon <robin.berjon@e...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: XPath/XSLT 2.0 concerns
    • From: Robin Berjon <robin.berjon@e...>

• 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