Hi Alok, Thank you for your feedback. Please see my responses in-line.
Alok Aggarwal wrote: > Hi Karen, > > On Thu, 18 Jun 2009, Karen Tung wrote: > >> A few days ago, I posted an email about implementing a module to provide >> dynamic default setting and semantic validation features for the parser. >> >> http://www.opensolaris.org/jive/thread.jspa?threadID=105651&tstart=15 >> >> We also discussed this at the Tuesday technical meeting. >> >> At this point, I am recommending that we do not make a special module >> to provide these features. Consumers that need to do >> dynmaic default setting and semantic validation can do so as part >> of their application. >> >> I wrote up the problem statement, the requirements, proposed >> solutions and my conclusion >> in the following document: >> >> http://www.opensolaris.org/os/project/caiman/XML_Parsing/dynamic-default-semantic-val-req-v1.odt >> >> >> >> Please send me other suggestions on solving the >> problem or any comment you might have on this. > > After reading through this document, it is clear > to me that semantic validation doesn't need to be > done specifically in the parser. > > Given this, how is DC going to deal with the parser > not supporting semantic validation? When we change over to the new parser, I imagine that we can just put all the existing default setting and semantic validation functions in DC into a library or something. Then, change the DC application itself to use these functions. > > I agree with you in general that the validation can be done in the > respective clients for this functionality, AI and DC. However I think > the common attributes that need to be verified across both AI and DC > (for the time being atleast) should be encapsulated within a separate > library at the very least. Yes, I certainly agree. All the common functions should be place in a library so any projects in the install team can call them to avoid duplicate code. Thanks, --Karen > > Alok > >
