[DFDL-WG] What are the consequences of a failed assert?

Garriss Jr., James P. jgarriss at mitre.org
Wed Jul 3 14:00:42 EDT 2013


I have an element with an assert,

           <xsd:element name="Type" dfdl:inputValueCalc="{ fn:lower-case(../MixedCaseType) }">
                <xsd:annotation>
                    <xsd:appinfo source="http://www.ogf.org/dfdl/dfdl-1.0/">
                        <dfdl:assert test="{ dfdl:checkConstraints(.) }" message="The type must match one of the values on the enumerated list."/>
                    </xsd:appinfo>
                </xsd:annotation>
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="application"/>
                        <xsd:enumeration value="multipart"/>
                        <xsd:enumeration value="message"/>
                        <xsd:enumeration value="text"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:element>

and the assert is failing (as it should in this case!).

Parse Error: Assertion failed. The type must match one of the values on the enumerated list.

What are the consequences of a failed assert?  I have an old version of the spec-is there a place to a get a current, complete copy?-but it says "An unsuccessful dfdl:assert causes a processing error."


1.     What does "processing error" mean in English?

2.     Does it mean the input is invalid?

3.     Does it mean the processor should stop here and go no further?

4.     Does it mean the process should simply ignore the problem and move on to the next item in the schema?

TIA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/dfdl-wg/attachments/20130703/c70e4800/attachment.html>


More information about the dfdl-wg mailing list