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

Re: Interoperability [long]

• To: Ronald Bourret <rpbourret@r...>
• Subject: Re: Interoperability [long]
• From: Francis Norton <francis@r...>
• Date: Fri, 16 Nov 2001 10:11:02 +0000
• Cc: xml-dev@l...
• References: <5.0.2.1.0.20011114080102.01d79208@p...> <5.1.0.14.2.20011113110910.02085170@p...> <3BF0B887.C0F6461@r...> <200111102048.PAA11544@h...> <3BEF8749.87CD5F1D@r...> <3BEFD820.FE803A93@f...> <5.0.2.1.0.20011115101818.01fbf6f8@p...> <3BF43AF8.FDD211C3@r...>
• Reply-to: francis@r...

Ronald Bourret wrote:
> 
> Sean McGrath wrote:
> > BTW, have you guys on xml-dev seen the collateral damage
> > in terms of  complexity/readability to the SAX/DOM/XSLT
> > programs that have become "namespace aware"?
> 
> I can imagine this in XSLT programs, but what's the problem with
> SAX/DOM? Adding namespace processing to my SAX program added a single
> line of code to startElement and endElement:
> 
I'm sorry, but maybe I'm so corrupted by over-exposure to XSLT that I've
simply got acclimatised. What do you mean, Sean, by collateral damage to
namespace aware XLST programs?

Are you referring to the fact that all XSLT transforms have to be
namespace aware to distinguish between code and data, or are you
referring to the added complexity of dealing with input or output from
one or more namespaces? Or are you talking about writing the XSLT engine
in the first place? If it's one of the first two I really don't see much
collateral damage, but maybe you've had a different experience you could
illustrate?

Francis.

• References:
  • Re: Caught napping!
    • From: Sean McGrath <sean.mcgrath@p...>
  • Re: Caught napping!
    • From: Tim Bray <tbray@t...>
  • Re: Caught napping!
    • From: Ronald Bourret <rpbourret@r...>
  • Re: Caught napping!
    • From: Dan Weinreb <dlw@e...>
  • Re: Caught napping!
    • From: Ronald Bourret <rpbourret@r...>
  • Re: Caught napping!
    • From: "W. E. Perry" <wperry@f...>
  • Re: Interoperability [long]
    • From: Sean McGrath <sean.mcgrath@p...>
  • Re: Interoperability [long]
    • From: Ronald Bourret <rpbourret@r...>

• Prev by Date: RE: Interoperability
• Next by Date: Re: so why don't more browsers support XSLT?
• Previous by thread: Re: Interoperability [long]
• Next by thread: Re: Interoperability [long]
• Index(es):
  • Date
  • Thread