Cannot use XSD 1.1 in a pipeline? #140

Closed
ndw opened this Issue Feb 10, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@ndw
Owner

ndw commented Feb 10, 2014

I've been trying to get up to date on XML-related standards, and am
currently learning XProc and using your XProc driver running on top of
Saxon-EE.

The problem that I am having is getting Saxon to use XML Schema 1.1 by
using a Saxon configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://saxon.sf.net/ns/configuration" edition="EE">
    <xsd version="1.1"/>
    <xslt version="2.0" schemaAware="true"/>
</configuration>

If I validate directly with Saxon, it works:

java com.saxonica.Validate -config:config.xml -xsd:schema.xsd -s:data.xml

But if I pass the same file through Calabash, it doesn't:

java com.xmlcalabash.drivers.Main --saxon-configuration=config.xml -i
source=data.xml pipeline.xpl

I get this from the p:validate-with-xml-schema step:

Feb 10, 2014 2:15:14 AM com.xmlcalabash.util.DefaultXProcMessageListener error
SEVERE: file:/home/pmenso57/2014.02.10/system/system.xsd:74:46:The
xs:assert element requires XSD 1.1 to be enabled

I am not sure how to properly get XML Schema 1.1 + Saxon-EE (with
schema-aware Transform) + Calabash working together.

Thanks in advance for whatever tips you can give.

@ndw

This comment has been minimized.

Show comment
Hide comment
@ndw

ndw Feb 10, 2014

Owner

Yeah, I see what happens. The processor gets (re)created with the wrong options. Working on a fix.

Owner

ndw commented Feb 10, 2014

Yeah, I see what happens. The processor gets (re)created with the wrong options. Working on a fix.

ndw added a commit that referenced this issue Feb 12, 2014

Fix issue #140 by making sure that if a saxon-configuration file is s…
…pecified, the parser settings it contains trump any parser settings requested elsewhere. As a consequence, attempting to request an HE parser when your saxon configuration specifies an EE parser will mean you get an EE parser. Don't do that, if that's not what you want.

ndw added a commit that referenced this issue Feb 12, 2014

Fix issue #140 by making sure that if a saxon-configuration file is s…
…pecified, the parser settings it contains trump any parser settings requested elsewhere. As a consequence, attempting to request an HE parser when your saxon configuration specifies an EE parser will mean you get an EE parser. Don't do that, if that's not what you want.

@ndw ndw closed this Feb 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment