In section 15 Choices, we define the direct dispatch method of choice resolution. For the choiceDispatchKey, we make the statements that... The expression must evaluate to an xs:string which must not be the empty string. and The resultant string must match the dfdl:choiceBranchKey property value of one of the element branches of the choice. This match is case insensitive. The use of a case insensitive match can be a bit of a performance inhibitor, and given that direct dispatch is intended to aid performance optimising the model, it kinda gets in the way. If an end user needs case insensitive searches then they can always define all of their branchKeys in one case and manually fold the dispatchKey into that case in their expression (toLower/toUpper). Can I propose that we remove the criteria that the match be case insensitive. The ignoreCase option may also play a part here. Cheers, Andy Andy Edwards - IBM Integration Bus - DFDL Email: andy.edwards@uk.ibm.com Snail Mail: MP211, Hursley park, Hursley, WINCHESTER, Hants, SO21 2JN Tel int: 247222 Tel ext: +44 (0)1962 817222 Desk: DE3 V17 The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer -- Murray Gell-mann in the NY Times Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU