[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [xml-dev] When to Validate XML?
May be it will help to understand use of functional acknowledgement (FA)
messages in EDI. When an EDI message arrives (let's say purchase order -
PO), it is checked for it's "syntax" by the EDI translators and they
generate a positive/negative FA appropriately. A positive ack does not mean
that the PO has been "accepted" in the business sense. A positive FA only
communicates to the sender ("application") that the PO they sent was syntax
wise correct. The PO is then processed by the receiver ("application") and
any semantic related problems are communicated by way of a separate business
message. A negative FA will contain enough information on the syntax problem
that occurred in the PO message for sender to be able to correct it.
The message syntax validation and business semantic validation are better
handled separately and necessarily in that order.
[mailto:email@example.com]On Behalf Of Michael Kay
Sent: Tuesday, November 06, 2001 9:10 PM
To: 'Champion, Mike'; firstname.lastname@example.org
Subject: RE: [xml-dev] When to Validate XML?
> Hi JJ ... now that you're out there in the Real World
> <grin>, maybe you
> could help us understand the role of RDBMS-level validation
> vs application
> logic. I suspect that will be the pattern that XML B2B/A2A
> systems will
> tend to follow once XML Schema implementations and
> applications mature. Are
> you saying that the RDBMS triggers, rules, etc. are mostly
> used during the
> debugging phase, and perhaps that application logic
> (JavaBeans in an app
> server or whatever) tends to handle the validation in the production
> applications? If so, is that because the DB
> triggers/rules/etc. have too much of a performance burden?
Actually I think a lot of people use database-level validation during normal
running, and then duplicate most of the checks at application level. The
main reason for doing the checks at the application level (or somewhere
close to the user interface) is that you can give much more responsive
diagnostics to the person who made the mistake. By the time a database
integrity check squeals, you've no idea where to position the cursor so the
user can correct the data.
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 elist use the subscription