Thanks for your comments ... Please see my responses to your questions below.
On Sat, Aug 30, 2008 at 10:40 PM, Florent Georges
<lists(_at_)fgeorges(_dot_)org> wrote:
I had a look at the initial article, but if I am right, though the
article is entitled "Schema aware processing with XSLT 1.0," this
presents rather a "Xalan extension function for WXS schema validation,"
doesn't it?
my intention of writing this article was to discuss how validation of
"output trees" / "result tree fragments" in an XSLT 1.0 environment
can be done. I used Xalan-J for my work, just as an example product.
This can be done similarly with Saxon 6.5.x also (I believe, it
supports Java extensions very well).
In fact, in the next version I am planning to make the stylesheet
portable for Xalan and Saxon 6.5.x.
This is really different. Schema-awarness does much more than
validating nodes.
About the validation function itself, I find quite strange to pass
the schema document as a string. Why not pass it as a document or
element node? Or enable the user to pass either a node (document or
element, the schema itself) or a string (the schema's URI.)
I agree with you. I actually wanted to write inline Schema in
stylesheet as below:
<xsl:variable name="schemaDoc">
<xs:schema
...........
</xs:schema>
</xs:variable>
But I was facing some problem passing this Schema as a RTF, or as a
node-set and accessing it in the Java extension function. The Schema
string worked for me.
An example is there in the article, where I pass the Schema URI to the
extension function, and that works fine.
--
Regards,
Mukul Gandhi
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--