New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attributes @sequence and @kind should not be allowed on p:input in invocation of steps #279

Closed
raducoravu opened this Issue Aug 9, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@raducoravu

raducoravu commented Aug 9, 2018

If I have an XProc like this:

    <p:declare-step xmlns:p="http://www.w3.org/ns/xproc" version="1.0">
        <p:input port="source">
            <p:document href="document.xml"/>
        </p:input>
        <p:output port="result">
            <p:pipe step="checkReservedWords" port="result"/>
        </p:output>
        
        
        <p:validate-with-schematron phase="classificationValidation" name="checkClassifications">
            <p:input port="schema">
                <p:document href="check-classifications-and-reserved-words.sch"/>
            </p:input>
            <p:input port="parameters" sequence="true" kind="document">
                <p:empty/>
            </p:input>
        </p:validate-with-schematron>
        
        
        <p:validate-with-schematron phase="reservedWordValidation" name="checkReservedWords">
            <p:input port="source">
                <p:pipe step="checkClassifications" port="result" />
            </p:input>
            <p:input port="schema">
                <p:document href="check-classifications-and-reserved-words.sch"/>
            </p:input>
            <p:input port="parameters" sequence="true">
                <p:empty/>
            </p:input>
        </p:validate-with-schematron>
        
    </p:declare-step>

you can create an XProcRuntime object and load the XProc in it without any error reported. But the usages of the @sequence and @kind attributes on the p:input elements should be flagged as errors.
Validating the XProc with the RNG schema flags the problems.

@raducoravu

This comment has been minimized.

Show comment
Hide comment

ndw added a commit that referenced this issue Aug 26, 2018

ndw added a commit that referenced this issue Aug 26, 2018

@ndw

This comment has been minimized.

Show comment
Hide comment
@ndw

ndw Aug 26, 2018

Owner

Fixed in 1.1.22.

Owner

ndw commented Aug 26, 2018

Fixed in 1.1.22.

@ndw ndw closed this Aug 26, 2018

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