At 2009-03-19 10:19 +0100, Romain Pelisse wrote:
Provided I got this
page<http://wiki.services.openoffice.org/wiki/Xml#Validation>right it
seems to be no way to run an XSD validation either on import or
export (when using an XSL filter to convert the document). This is
definitely a "show-stopper" for me
It would help me to understand why this is a show-stopper. It it
only because you do not have the opportunity to validate your inputs
imperatively? Is it too awkward to write your content validation
checks in XSLT 2 logic that you need to use the schema?
I ask because I teach these topics (I'm in the middle of a 5-day
XSLT/XQuery delivery in Prague this week) and I am curious to know
which use cases users would qualify as "show-stoppers".
, therefore I was hoping you wouldn't mind
give me some more data about this issue (more exactly a missing
functionality).
Why is this so ?
The most robust implementation of XSLT 2.0 I know if is currently
included in OpenOffice and the non-schema-aware version of this tool
is available at no charge. That makes it a good candidate for
including in a free office tool.
Is there actually no need for it ? (ie i missed something)
That is why I'm asking the question the other way around ... why do
you think you need it?
Here are two links to three OpenOffice filters I sell that make
extensive use of XSLT 2.0 in OpenOffice 3 and I have no need for validation:
http://www.CraneSoftwrights.com/sales/Crane-gc2ods
http://www.CraneSoftwrights.com/sales/Crane-UBLProfile
Is this really complex to implement (I don't really see why it could be
complex, but i can very easily be mistaken on this matter).
Would you propose writing W3C Schema validation on your own? I think
it would be an incredible challenge to do it well ... which is why I
have such respect for Michael Kay and his high conformance and high
performance tools.
It is my opinion that you are mistaken. And you wouldn't be the
first one! Some of my students come to class thinking the same.
If it were to be reasonably easy to implement, I could be able to do it and
contribute back the code...
The interface is not the issue, as Vyacheslav said, it is the engine
that is the issue. OpenOffice ships with Saxon-B by Michael Kay, and
for you to get validation then I suspect all you have to do is
(1) - change the invocation of
Basis\program\classes\saxon9.jar
... to be saxon9sa.jar
(2) - turn on validation at invocation
The challenge is that saxon9sa.jar is not free but a commercial tool
available from Saxonica:
http://www.Saxonica.com
Also, were you aware that "turning on validation" also requires
changes to an XSLT stylesheet to engage the validation features? Not
only will you need to install a schema-aware processor, and change
the invocation to turn on validation, but you also need import
statements in the XSLT to pull in the type definitions that your
validation instructions refer to in order to indicate the validation you want.
BTW, there may very well be other validating W3C Schema processors
out there, but I'm not aware of them so I've not used them.
I hope this helps.
. . . . . . . . . Ken
--
XSLT/XQuery/XSL-FO training in Los Angeles (New dates!) 2009-06-08
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson: http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview: http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman mailto:[email protected]
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/i/
Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/i/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
