XMLBeans doesn't use the XSLT part of Saxon, just the Xquery/Xpath. Absolutely, the first step is get the XmlBeans source code from SVN and build it (should be pretty easy).
Are you planning to use just the XSLT support from Saxon or the Schematron part also (in case something like that exists)? Do you know what is the license status of the part you want to use? (basically you will need to be able to use the Saxon jar that XmlBeans downloads by default when you build). Other observations: 1. All the code that depends on Saxon needs to be built into xbean_xpath.jar, xbean.jar can have no Saxon dependency; in order to do that, the code needs to be checked in under src/xbean_xpath. 2. If you want the Schematron validation to be completely transparent for the user, the way you thought about it in one of your original e-mails, the code will have to plug-in into the Schema validation: org.apache.xmlbeans.impl.Validator. Note that there is not DOM access there, the way to get to the XML is via SAX events, so there is no Saxon integration at that level either. Therefore there is a chance that even after your work, Schematron validation will require a separate step. 3. You need to extract the Schematron bits from the Schema annotations. If the annotations are children of the <schema> element, you would use SchemaTypeSystem.getAnnotations() to get them. If they can be present at other levels (like on a Schema type or element), you need to look at the SchemaAnnotated interface and see how to get to them in those cases. Finally, if you are subscribed to the dev list, could we move the discussion over there now? Thanks, Radu -----Original Message----- From: Rafael Tatsuya Icibaci [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 17, 2007 1:23 PM To: [email protected] Subject: RE: XMLBeans and SchemaTron Radu, Ok, probably a good start is checkout XMLBeans code from SVN and start looking into. Schematron is a collection of some XSLT stylesheets, so to support it, we need to use a XSLT engine like Saxon, I think that XMLBeans already use it. And then input into Saxon Schematron *.xsl files. What is the best way to take ? Schematron Architecture: http://www.dpawson.co.uk/schematron/introduction.html Atenciosamente Rafael T. Icibaci IBM Middleware EAI Team * + 55 11 2113-7685 * + 55 11 8184-5303 * [EMAIL PROTECTED] -----Original Message----- From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] Sent: segunda-feira, 16 de abril de 2007 19:37 To: [email protected] Subject: Re: XMLBeans and SchemaTron This is true in broad lines. This however being a bigger enhancement, before achieving 2) we'll probably need to have an extended e-mail conversation so that I can explain how the code works and where would the plug-in points be. Certainly, having some code that "understands" the Schematron grammar would be a prerequisite. Radu On Mon, 2007-04-16 at 09:19 -0700, Jacob Danner wrote: > Hi Rafael, > I'm sure one of the commiters can give more specific details, but I've > always thought the general process for contributing was something > like: > 1) File a Jira issue/enhancment request > 2) Implement the feature/fix > 2)a- don't forget to include tests > 3) attach a patch to the Jira issue > 4) email the dev list upon completion. > 5) commiters review the patch > > Hope this helps, > -Jacob Danner > > > On 4/16/07, Rafael Tatsuya Icibaci <[EMAIL PROTECTED]> wrote: > > Hi again, > > > > > > One time you said me that maybe a volunteer can implement Schematron > > support for XMLBeans. How would be the process if I offer myself to do that > > ? > > > > > > Atenciosamente > > > > Rafael T. Icibaci > > IBM Middleware EAI Team > > * + 55 11 2113-7685 > > * + 55 11 8184-5303 > > * [EMAIL PROTECTED] > > > > -----Original Message----- > > From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] > > Sent: quarta-feira, 11 de abril de 2007 18:28 > > To: [email protected] > > Subject: RE: XMLBeans and SchemaTron > > > > Yes, by "not work" meaning that the Schematron rules will not be > > processed and enforced against documents at run-time. The Schema > > will compile of course. > > > > Radu > > > > On Wed, 2007-04-11 at 17:41 -0300, Rafael Tatsuya Icibaci wrote: > > > Hunm....if I understand correctly what you said. If I include schematron > > > tags into a XML Schema and give the XML Schema to XMLBeans to use, it > > > will not work ??? Because XMLBeans doesn't have a engine to process the > > > embed schematron tags ?? > > > > > > Atenciosamente > > > > > > Rafael T. Icibaci > > > IBM Middleware EAI Team > > > * + 55 11 2113-7685 > > > * + 55 11 9299-7840 > > > * [EMAIL PROTECTED] > > > > > > > > > -----Original Message----- > > > From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] > > > Sent: quarta-feira, 11 de abril de 2007 17:28 > > > To: [email protected] > > > Subject: RE: XMLBeans and SchemaTron > > > > > > This is only half of it though. Having the Schematron rules inside > > > a Schema means that you can get to the rules from XmlBeans, but > > > you still need a Schematron validation engine to process the rules > > > and apply them to the incoming document. What is this validation engine > > > (if you can? > > > > > > Radu > > > > > > On Wed, 2007-04-11 at 10:02 -0300, Rafael Tatsuya Icibaci wrote: > > > > Radu, > > > > > > > > > > > > > > > > XMLBeans support XML Schemas so, if we have a way to embed > > > > schematron tags within XSD, so my problem is solved. I think I > > > > found it..BTW, > > > > > > > > It's the same solution that I found earlier in this > > > > note(schematron tags into <appinfo> context), see sample XSD below: > > > > > > > > > > > > > > > > Marcelo: Seems that we are good to proceed this way. We only > > > > need to check if this solution will catch up all our scenarios. > > > > > > > > > > > > > > > > <?xml version="1.0"?> > > > > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > targetNamespace="http://www.demo.org"; > > > > xmlns="http://www.demo.org"; > > > > xmlns:sch="http://www.ascc.net/xml/schematron"; > > > > elementFormDefault="qualified"> > > > > <xsd:annotation> > > > > <xsd:appinfo> > > > > <sch:title>Schematron validation</sch:title> > > > > <sch:ns prefix="d" uri="http://www.demo.org"/> > > > > </xsd:appinfo> > > > > </xsd:annotation> > > > > <xsd:element name="Demo"> > > > > <xsd:annotation> > > > > <xsd:appinfo> > > > > <sch:pattern name="Check A greater than B"> > > > > <sch:rule context="d:Demo"> > > > > <sch:assert test="d:A > d:B" > > > > diagnostics="lessThan"> > > > > A should be greater than B. > > > > </sch:assert> > > > > </sch:rule> > > > > </sch:pattern> > > > > <sch:diagnostics> > > > > <sch:diagnostic id="lessThan"> > > > > Error! A is less than B > > > > A = <sch:value-of select="d:A"/> > > > > B = <sch:value-of select="d:B"/> > > > > </sch:diagnostic> > > > > </sch:diagnostics> > > > > </xsd:appinfo> > > > > </xsd:annotation> > > > > <xsd:complexType> > > > > <xsd:sequence> > > > > <xsd:element name="A" type="xsd:integer"/> > > > > <xsd:element name="B" type="xsd:integer"/> > > > > </xsd:sequence> > > > > </xsd:complexType> > > > > </xsd:element> > > > > </xsd:schema> > > > > > > > > > > > > > > > > Reference: http://www.xfront.com/ExtendingSchemas.html > > > > > > > > > > > > > > > > > > > > > > > > Atenciosamente > > > > > > > > Rafael T. Icibaci > > > > IBM Middleware EAI Team > > > > ( + 55 11 2113-7685 > > > > È + 55 11 9299-7840 > > > > * [EMAIL PROTECTED] > > > > > > > > > > > > > > > > ________________________________________________________________ > > > > ______ > > > > From: Radu Preotiuc-Pietro [mailto:[EMAIL PROTECTED] > > > > Sent: segunda-feira, 9 de abril de 2007 18:22 > > > > To: [email protected]; Webber, David (NIH/OD) [C] > > > > Cc: Marcelo Martins Pereira > > > > Subject: RE: XMLBeans and SchemaTron > > > > > > > > > > > > > > > > > > > > First time I hear abour JCam, so no. > > > > > > > > > > > > > > > > What I suggest you do is the following: > > > > > > > > > > > > > > > > If you can find a Schematron validator somewhere that can act as > > > > a "filter" for a SAX or StAX stream or that works over DOM, you > > > > can plug that in as a separate step and still use XMLBeans and > > > > Schema validation. XMLBeans supports all three of these standard > > > > APIs so maybe you can get around it this way. > > > > > > > > > > > > > > > > The thing about it is that implementing a validation engine is a > > > > lot of work, so we had to limit ourselves to 1 and that had to > > > > be pretty much XMLSchema. Now, if someone who knows Schematron > > > > would be willing to contribute something in XmlBeans in that > > > > area it would be a welcome addition, but without a volunteer, > > > > it's unlikely to happen, I would say. > > > > > > > > > > > > > > > > Anyway, if you do find such a "filter" validator, please do post > > > > back and let us know. > > > > > > > > > > > > > > > > Radu > > > > > > > > > > > > > > > > > > > > ________________________________________________________________ > > > > ______ > > > > From: Rafael Tatsuya Icibaci > > > > [mailto:[EMAIL PROTECTED] > > > > Sent: Monday, April 09, 2007 12:08 PM > > > > To: Webber, David (NIH/OD) [C]; [email protected] > > > > Cc: Marcelo Martins Pereira > > > > Subject: RE: XMLBeans and SchemaTron > > > > > > > > Yes, I need content validation. What we exactly want to do is: > > > > We have a requirement to use XMLBeans, also today we have a need > > > > to include conditional expressions in XSD files (e.g.: if we > > > > have a tag so we need to have the other as well). Schematron > > > > appears to be the solution, because we can set these conditions > > > > using XPath, but now the question is: If we are going to use > > > > XMLBeans and we will pass a XSD file to XMLbeans to validate, > > > > XMLBeans support SchemTron ? I can pass a .SCH file to XMLBeans > > > > ? or I have a way to include SchemTron tags into .XSD files ?? I > > > > found a sample of using SchemTron tags into .XSD(see below), but > > > > appears that this is only valid when schematron tags are inside of > > > > <xs:annotation> tag. > > > > > > > > > > > > > > > > I'm checking out JCam, seems that it's very similar to SchemaTron. > > > > XMLBeans support JCam ?? > > > > > > > > > > > > > > > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > > > > <xs:schema xmlns="http://www.ascc.net/xml/schematron"; > > > > > > > > xmlns:xs="http://www.w3.org/2001/XMLSchema"; > > > > > > > > targetNamespace="http://www.rafael.com"; > > > > elementFormDefault="qualified" > > > > > > > > attributeFormDefault="unqualified"> > > > > > > > > <xs:annotation> > > > > > > > > <xs:appinfo> > > > > > > > > <schema xmlns="http://www.ascc.net/xml/schematron";> > > > > > > > > <title>Meds</title> > > > > > > > > <ns uri="http://www.rafael.com"; prefix="ns"/> > > > > > > > > <pattern name="Medications"> > > > > > > > > <rule context="ns:E18"> > > > > > > > > <assert test="preceding::E18_02"> > > > > > > > > If <name/> is used you must list the > > > > Medications listed > > > > > > > > </assert> > > > > > > > > <assert test="preceding::E18_07"> > > > > > > > > If <name/> is used you must list the > > > > patient response > > > > > > > > </assert> > > > > > > > > </rule> > > > > > > > > <rule context="ns:Header"> > > > > > > > > <report test="count(ns:Record) > 0"> > > > > > > > > There are <value-of select = > > > > "count(ns:Header\Record)"/> <name/> > > > > > > > > </report> > > > > > > > > </rule> > > > > > > > > </pattern> > > > > > > > > </schema> > > > > > > > > </xs:appinfo> > > > > > > > > </xs:annotation> > > > > > > > > > > > > > > > > Atenciosamente > > > > > > > > Rafael T. Icibaci > > > > IBM Middleware EAI Team > > > > ( + 55 11 2113-7685 > > > > È + 55 11 9299-7840 > > > > * [EMAIL PROTECTED] > > > > > > > > > > > > > > > > ________________________________________________________________ > > > > ______ > > > > From: Webber, David (NIH/OD) [C] [mailto:[EMAIL PROTECTED] > > > > Sent: sexta-feira, 6 de abril de 2007 13:02 > > > > To: [email protected] > > > > Cc: Rafael Tatsuya Icibaci > > > > Subject: RE: XMLBeans and SchemaTron > > > > > > > > > > > > > > > > > > > > Rafael, > > > > > > > > > > > > > > > > > > > > > > > > If you need content validation services - check out the latest > > > > OASIS CAM tool > > > > > > > > > > > > > > > > > > > > > > > > http://www.jcam.org.uk/ > > > > > > > > > > > > > > > > > > > > > > > > DW > > > > > > > > > > > > > > > > > > > > > > > > ________________________________________________________________ > > > > ______ > > > > From: Rafael Tatsuya Icibaci > > > > Sent: Thu 4/5/2007 2:57 PM > > > > To: [email protected] > > > > Subject: XMLBeans and SchemaTron > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > Anyone knows if XMLBeans support SchemaTron ? > > > > > > > > Atenciosamente > > > > > > > > Rafael T. Icibaci > > > > IBM Middleware EAI Team > > > > ( + 55 11 2113-7685 > > > > È + 55 11 9299-7840 > > > > * [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > Notice: This email message, together with any attachments, may > > > > contain information of BEA Systems, Inc., its subsidiaries and > > > > affiliated entities, that may be confidential, proprietary, > > > > copyrighted and/or legally privileged, and is intended solely > > > > for the use of the individual or entity named in this message. > > > > If you are not the intended recipient, and have received this > > > > message in error, please immediately return this by email and then > > > > delete it. > > > > > > Notice: This email message, together with any attachments, may contain > > > information of BEA Systems, Inc., its subsidiaries and affiliated > > > entities, that may be confidential, proprietary, copyrighted and/or > > > legally privileged, and is intended solely for the use of the individual > > > or entity named in this message. If you are not the intended recipient, > > > and have received this message in error, please immediately return this > > > by email and then delete it. > > > > > > ------------------------------------------------------------------ > > > --- To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > --- To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > Notice: This email message, together with any attachments, may contain > > information of BEA Systems, Inc., its subsidiaries and affiliated > > entities, that may be confidential, proprietary, copyrighted and/or > > legally privileged, and is intended solely for the use of the individual or > > entity named in this message. If you are not the intended recipient, and > > have received this message in error, please immediately return this by > > email and then delete it. > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
