tag:blogger.com,1999:blog-2200693733508292186.post7212620795369907012..comments2008-02-01T12:34:16.546-05:00Paulhttp://www.blogger.com/profile/10201367533944398106noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2200693733508292186.post-47761498983008938672008-02-01T12:34:00.000-05:002008-02-01T12:34:00.000-05:00I agree with you Tony that the important questions are as you stated. This is spot on. Using application logic to validate this code data is not the best approach. <BR/><BR/>I may respectfully disagree with your characterization that people worry too much about how many passes however. Simplicity often wins whether it is the best method or not. This just matters.<BR/><BR/>There are some folks looking at single pass validation of code lists in a different light. And some of the architects in OAGi are doing similar. <BR/><BR/>I'll end with total agreement with your statement "I'll be disappointed if we don't end up with a few different ways of using that code list information, so that users can choose the approach that best suits their particular situation" So true. I'll be learning and reading up on genericode as I do with other approaches. <BR/>PaulPaulhttp://www.blogger.com/profile/10201367533944398106noreply@blogger.comtag:blogger.com,1999:blog-2200693733508292186.post-81178206742584429332008-01-17T17:22:00.000-05:002008-01-17T17:22:00.000-05:00I'm the editor of the OASIS genericode specification. The 2-pass validation is proposed as a way to do genericode-based code list validation in conjunction with existing XML validating parsers. It's actually consistent with application of business rules engines post-validation to check rules that XML schemas can't check.<BR/><BR/>That said, the genericode specification and committee don't have a fixed opinion on this. If someone builds a piece of software that does schema and genericode validation in a single pass, that will be great. People worry too much about how many passes have to be done. The important questions are (i) how long does the total validation take, (ii) how big a percentage of your total end-to-end business process time is taken up by validation, and (iii) how much time can you same in writing validation code by moving data validation out into separate layers that simplify the coding and debugging of core application code.<BR/><BR/>If someone wants to use genericode files as a way to generate XML Schemas that just contain simple type enumerations for code lists, that is also fine, as long as they have an appropriate process for managing change to the code lists and republication of the affected Schemas to users and/or systems. There is no right or wrong way. Genericode is just a way to communicate that code list information, and I'll be disappointed if we don't end up with a few different ways of using that code list information, so that users can choose the approach that best suits their particular situation.<BR/><BR/>Cheers, Tony.<BR/>http://kontrawize.blogs.com/kontrawize/<BR/>http://www.genericode.org/abcoateshttp://www.blogger.com/profile/10467669766783304183noreply@blogger.com