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

Re: Visiting your cake and eating it too (was Stupid Question

• To: <xml-dev@l...>
• Subject: Re: Visiting your cake and eating it too (was Stupid Question)
• From: "Rick Jelliffe" <ricko@a...>
• Date: Wed, 6 Mar 2002 20:16:43 +1100
• References: <2X3W74B8GAHBN4Z63D8A6KFZIHHGNJ.3c855805@MChamp> <200203060138.g261ctu10329@d...> <3C85BA20.857FCE4D@r...> <5.1.0.14.2.20020306083458.02b0ee60@p...>

From: "Sean McGrath" <sean.mcgrath@p...>


> At 18:32 06/03/2002 +1100, Rick Jelliffe wrote:
> 
> >There is a case to be made that, for implementability reasons, it is actually
> >good to bundle together as many orthogonal functions that can act as
> >visitors on the same traversal of the infoset.

> This makes no sense to me. I must be missing something. What do you
> mean "for implementability reasons". My gut tells me quite the
> opposite!
 
Oops, I meant "for efficiency reasons".  Rather than traversing an infoset
many times, it can be more efficient if different functions can be performed
in a single pass through a document. *

So stream-based processing is efficient because it operates on a single
traversal. Contrast this with DOM, if you implement "layered"
functions naively as separate passes. 

But not all layers can be implemented well using streams. (XPath
systems requiring arbitrary context, for example.) So instead, to
get efficiency of tree-based data structures, we need to perform
as many functions as possible during one traversal.  

So it makes sense for an implementation, for efficiency reasons,
for a schema processor to do datatyping, augmentation, and 
defaulting at the same time.

So the modularity of Schema languages should not only be seen
in terms of "what functions can be split out into independent
passes?", but rather "what functions can be split out into notional
independent passes, but implemented using the same pass?"

In practice (i.e. for designers of schema languages and scissor-happy
layerists), it means that for efficiency the node-selection mechanism 
should be shared, while the node manipulation mechanism should
be modular.


Cheers
Rick Jelliffe 

* Obviously there are other aspects at work too: the availability
of keys or IDs gathered from previous passes, and whether
a layer should act based on a traversal of each node or by following 
an XPath.

• Follow-Ups:
  • Re: Visiting your cake and eating it too (was Stupid Question)
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: Visiting your cake and eating it too (was Stupid Question)
    • From: Sean McGrath <sean.mcgrath@p...>

• References:
  • Re: Stupid Question (was RE: XML doesn't deserveits "X".)
    • From: Mike Champion <mc@x...>
  • Re: Stupid Question (was RE: XML doesn't deserve its "X".)
    • From: Joe English <jenglish@f...>
  • Re: Stupid Question (was RE: XML doesn't deserve its "X".)
    • From: Ronald Bourret <rpbourret@r...>
  • Re: Visiting your cake and eating it too (was Stupid Question)
    • From: Sean McGrath <sean.mcgrath@p...>

• Prev by Date: RE: Can't get XML to display through XSLT
• Next by Date: Re: Visiting your cake and eating it too (was Stupid Question)
• Previous by thread: Re: Visiting your cake and eating it too (was Stupid Question)
• Next by thread: Re: Visiting your cake and eating it too (was Stupid Question)
• Index(es):
  • Date
  • Thread