Lists Home |
Date Index |
Try using xsd:all in your WXS.
Order is important in apps where one element must precede another
because of some dependency on the previous value when processing as
From: Wadsworth, Geoffrey [mailto:GWadsworth@thedoctors.com]
Sent: Thursday, December 05, 2002 1:11 PM
Subject: [xml-dev] Curious XML Validation issue.
I have defined a schema for an import business document. The process that is
producing the xml that the schema is validating is producing a useable xml
document. It does not validate because the some of the nodes are in a
<REMITTANCE_DESCR>1 of 4</REMITTANCE_DESCR>
<NUM_OF_PAYMENTS_QTY>1 of 4</NUM_OF_PAYMENTS_QTY>
The above is what is being sent. The schema complains because the
<PAY_PLAN_TYPE_CODE> & <REMITTANCE_DESCR> nodes are defined as being before
the <INSTALLMENT> node. This puzzles me because the order of the nodes under
doesn't matter when I am accessing the data but the schema complains anyway.
I am doing the validation in VB using MSXML4. Is there a way for the schema
to ignore the order? I would also be curious as to why the schema even cares
about the order.
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription