Re: [xml-dev] Cost of catching data errors at the periphery during XML validation vice inside the system, during application processing?

At 2014-10-10 14:27 +0000, Costello, Roger L. wrote:
>Have you done a cost analysis of catching and dealing with data 
>errors during XML validation (at the periphery, before the data has 
>gone into the system) versus catching and dealing with data errors 
>during application processing (after the data has gotten inside the system)?

I have no numbers for you, but there is also a cost to development 
you may want to include in your numbers.

Development costs will be much lower to create a 
application/stylesheet written for data known to have been pre-validated.

Clients may have schemas for authoring content but not have anything 
for their data after it has been processed for publishing.  For a 
number of clients I have written a quickie RELAX-NG schema of my 
expectations for XML input to an XSLT/XSL-FO stylesheet and I 
pre-validate the data before producing my final content.  Such a 
schema has proved to be a bonus in catching pre-processing problems 
on the client's side that would have produced incorrect (but not 
necessarily invalid) results with my stylesheets.  But my stylesheets 
end up executing faster without spending cycles on cruft, and I spend 
less time by not having to write that cruft in the first place.

I hope this helps.

. . . . . . . Ken


--
Public UBL and code list hands-on classes - Stockholm, Dec. 3&4,2014 |
Contact us for world-wide XML consulting and instructor-led training |
Free 5-hour lecture: http://www.CraneSoftwrights.com/links/video.htm |
Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/x/ |
G. Ken Holman                   mailto: |
Google+ profile:      http://plus.google.com/+GKenHolman-Crane/about |
Legal business disclaimers:    http://www.CraneSoftwrights.com/legal |


---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com