[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [xml-dev] When to Validate XML?
- From: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
- To: email@example.com
- Date: Tue, 06 Nov 2001 09:42:13 -0500
> -----Original Message-----
> From: Leigh Dodds [mailto:firstname.lastname@example.org]
> Sent: Tuesday, November 06, 2001 9:28 AM
> To: Champion, Mike; email@example.com
> Subject: RE: [xml-dev] When to Validate XML?
> If you've got multiple systems accessing
> a database then the only way to enforce these kind of checks is within
> the RDBMS. There's no guarantees that the application level
> logic will be consistent across all your applications.
Ahh, good point, and one for the validation decision tree: Use a
Schema/DTD and XML-level validation to enforce constraints that are
universal across applications that use a specific data format. Use
application logic (procedural code?) to enforce constraints that specialized
applications know about. For (a quickly contrived) example, a bookstore
site might need some specialized module that knows about ISBNs and how to
validate them against a database; most other modules just need to ensure
that the ISBN value doesn't get lost and "trust" that nobody mucks with the