[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Multi-stage schema validation and schema design
- From: Mike_Leditschke@nemmco.com.au
- To: firstname.lastname@example.org
- Date: Tue, 27 Mar 2001 12:55:30 +1000
I am designing XML Schemas for a B2B application and would
appreciate some comments as to the schema design options available
for multi-stage validation. I would like to use one namespace at the
I have a simple "message" wrapper which is used to carry
transactions between back-end systems in different organisations.
This wrapper contains sufficient information to determine the application
targetted by the transaction.
I would like to allow the message gateway to validate the message
"envelope" of incoming messages sufficiently to route transactions
to the correct application. However, the gateway need know nothing
of the structure of the transactions themselves.
I envisage that the applications would then schema validate
There would appear to be two ways to proceed - global elements or
In this approach, I use global elements for any wrapper elements and each
The downside is that I must include namespaces on these elements
in instance documents, and I loose the ability to "hide" the namespace, as
suggested by the best practice guidelines.
In this approach, I use types for the wrapper and transactions and have a
top-level element, as discussed in the best practices.
Whilst the XML Schema section on validation (data structure - 5.2) suggests
it should be possible to ask a validator to validate an element if you a
the type, comments I have received suggest this is not a capability the
crop of schema validators support.
Is this in fact the case?
Does anyone know of validators supporting this functionality?
Are there any downsides with using this approach as opposed to
Any comments on any of the above much appreciated.