|
|
|||||||
|
I'm not sure why the author had to go with a 'hybrid' solution -- mixing hierarchical data structure with the relational. Wouldn't it be easier to simply implement the solution as a full blown hierarchical data structure? Something like the following: <act:ActionList version='1.0' xmlns:act='http://www.good_thang.net/xmlns/ActionList'> <act:Action type='Question'> <act:Content value ='What type of vehicle did you purchase?'/> <act:Explanation value='Pick your choice'/> <act:AnswerList> <act:Answer value='Car'/> <act:Action type='Question'> <act:Content value ='What type of car?'/> <act:AnswerList> <act:Answer value='Sport Coupe'/> <act:Answer value='Sedan'/> </act:AnswerList> </act:Action> <act:Answer value='Truck'/> <act:Action type='Question'> <act:Content value ='What type of truck?'/> <act:AnswerList> <act:Answer value='Pickup'/> <act:Answer value='4x4'/> </act:AnswerList> </act:Action> <act:Answer value='SUV'/> <act:Action type='Question'> <act:Content value ='What type of SUV?'/> <act:AnswerList> <act:Answer value='Ford Runner'/> <act:Answer value='Passport'/> <act:Answer value='Path Finder'/> </act:AnswerList> </act:Action> </act:AnswerList> </act:Action> </act:ActionList> |