This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: limitations in different parsers



> that do not work well in another compliant parser. Two examples include:
> 	
> 	dynamic template names supported in xalan and not in XT

I don't know what you mean by dynamic template names but if I guess
correctly then that should not be supported by any parser should it
(unless the XSLT system has extension functions providing this). xt can not
be called a "compliant" xslt system in any case, development of xt
finished before the XSLT spec was completed.

> I assumed compliant XSL templates written in one parser would be
> compliant in all. Was this a fair assumption?

Note that it's not really the parser that you are concerned about here,
many of the systems can use different XML parsers (eg any sax compliant
parser)

If you are using an extension feature in an extension namespace for one
particular system, then clearly it will only work on that system.

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]