This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XSL-List Digest V4 #485
- From: Bill Cohagan <bill dot cohagan at teraquest dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Cc: Bill Cohagan <bill dot cohagan at teraquest dot com>, cohagan at acm dot org
- Date: Thu, 27 Jun 2002 14:12:36 -0500
- Subject: [xsl] RE: XSL-List Digest V4 #485
- Reply-to: xsl-list at lists dot mulberrytech dot com
Michael-
Yes, and treating it as a literal element is *precisely* what causes the
problem. As I said, these are not syntax errors; thus detecting them will
take some semantic knowledge. Were I to write a transform to detect this I'd
simply look for *any* element (not in the xsl namespace) whose element name
begins with the charater string "xsl" (or whatever the namespace prefix is
defined to be). I'd flag any such occurence as "suspect".
For the case I was describing it was in fact <xsl-value-of .../> so there
was no well-formedness error.
So, what's the purpose of the RELAX-NG schema?
Thanks,
bill
-----Original Message-----
Date: Thu, 27 Jun 2002 10:40:02 +1000
From: "Michael Leditschke" <mike@ammd.com.au>
Subject: RE: [xsl] XSL lint?
There is already a RELAX-NG schema for XSLT at
http://thaiopensource.com/relaxng/xslt.rng
However, for the "error" quoted;
<xsl-value-of ...> rather than <xsl:value-of ...>
I don't think it would complain - it would simply
treat the xsl-value-of as a literal result element.
(presumably the above example was produced with a tool that
managed the tags for you, e.g. added closing tags,
otherwise a well-formedness error would be likely)
Regards
Michael
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list