• To: "'W. E. Perry'" <wperry@f...>,"'XML DEV'" <xml-dev@l...>
• Subject: RE: Are hyperlinks presentation or content?
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Thu, 3 Oct 2002 09:12:15 +0100
• Importance: Normal
• In-reply-to: <3D9B72D3.78349777@f...>
• Reply-to: <michael.h.kay@n...>

> There is no question that the XSLT solution is a more 
> promising basis for interoperability than a priori 
> standardization of markup vocabulary. The residual problem 
> with XSLT for translation to "local standard" is in its 
> 'push' nature. XSLT transformations are premised on an 
> intimate understanding of the source tree and are designed to 
> render that source tree into multiple output forms--as 
> understood from a source-tree-centered perspective.

An interesting perspective, but not one I fully share.

Firstly, XSLT allows output-driven pull processing just as much as
source-driven push processing.

Secondly, the push model actually binds the stylesheet less tightly to
the structure of the source document than the pull model.

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s... 

• Follow-Ups:
  • Re: Are hyperlinks presentation or content?
    • From: "W. E. Perry" <wperry@f...>

• References:
  • Re: Are hyperlinks presentation or content?
    • From: "W. E. Perry" <wperry@f...>

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