• To: xml-dev@l...
• Subject: Re: Schema style and parser performance
• From: Richard Tobin <richard@c...>
• Date: Thu, 1 May 2003 15:12:13 +0100 (BST)
• Cc:
• In-reply-to: <195d01c30f5d$26f19e90$1401a8c0@snobird>
• Organization: HCRC, University of Edinburgh

>If validating and converting the schema to internal form is a large part of
>validation cost, would transformations that "flatten" a schema make a
>significant difference?
...
>I am thinking of things like
>flattening type derivations, putting the contents of included schemas
>inline, etc.

Certainly type derivation is one of the most complicated parts of
schema compilation, but I don't know whether it's expensive in CPU
time.  XSV is full of inefficiencies, and when we've profiled it it
has usually turned out that lots of the time is spent in some piece of
code written without any thought for efficiency, or some idiom that
turns out to be expensive in Python.  I've never profiled a schema
validator written with efficiency as an important goal.

-- Richard

• Follow-Ups:
  • RE: Schema style and parser performance
    • From: "Marcel Jemio" <mjemio@d...>

• Prev by Date: Re: iTunes XML on the web
• Next by Date: [ANN] XInclude.NET 1.0alpha released
• Previous by thread: Re: iTunes XML on the web
• Next by thread: RE: Schema style and parser performance
• Index(es):
  • Date
  • Thread