Jean McCormack wrote: > >>>>> >>>> With your design on this component, what kind of semantic >>>> validation are you planning to do with the user's input? >>>> When are you planning to do the semantic validation, and how are >>>> you going to do the validation? >>>> I am asking because in the semantic validation part of >>>> the XML parser redesign effort, I would need to have this kind of >>>> information. >>> At this point in time, I'm not sure it will need any semantic >>> validation from the XML parser. Since the manifest comes in rather >>> late in the install, it's not the preferred way of interacting with >>> the user. >> Surely a user will be able to explicitly state a field in a >> manifest. What about users and passwords? Those aren't going to be >> derived or determined by the installer. There's also been lots of >> discussion about disk specifications in the manifest. These fields >> also include fields which, when not explicitly specified by a user, >> would otherwise be given a derived default value. >> >> As long as there is user input in a manifest which requires >> validation above the syntax checking afforded by schemas, then there >> is a need for semantic validation. >> >> >> A different issue is *where* that semantic validation will be done. >> Will it be done in the parser, or will it be done in the installer >> code itself? IMO it is more maintainable to do it in the parser, >> because both the server and the client can do the checks from the >> same "template", and keep all validation code in one place. >> >> This assessment is part of the XML parsing work AI is one customer >> of that work. If all projects (AI and DC) decide parser-based >> semantic validation isn't needed, then it doesn't need to get done. >> Please let the XML parsing rework team know. > > Sorry. I thought Karen was talking explicitly about the user control > issue. For that I didn't see anything beyond what the client project > in general needs. Have you received the client project requirements? > > Jean > Hi Jean,
The XML parsing rework team hasn't received the any requirements in terms of semantic validation of the manifests. This work is included as one of the problem statements, because Alok was saying that we need this kind of feature for the AI client. Then, I saw your posting about AI client dry run, I thought that is very much related, since I imagine part of dry run is to validate the provided manifest somehow, so, I thought I will ask. --Karen
