• From: "Champion, Mike" <Mike.Champion@S...>
• To: xml-dev@l...
• Date: Tue, 06 Nov 2001 09:42:13 -0500

> -----Original Message-----
> From: Leigh Dodds [mailto:ldodds@i...]
> Sent: Tuesday, November 06, 2001 9:28 AM
> To: Champion, Mike; xml-dev@l...
> Subject: RE:  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
value.

• Follow-Ups:
  • Re: When to Validate XML?
    • From: Subrahmanyam Allamaraju <subbu@b...>

• Prev by Date: RE: Re: determining ID-ness in XML
• Next by Date: RE: Re: determining ID-ness in XML
• Previous by thread: RE: When to Validate XML?
• Next by thread: Re: When to Validate XML?
• Index(es):
  • Date
  • Thread