Thanks for the replies above… I understand there may be more value in rules on the confirmation view than on the reporting view. Does the VWG still plan to produce XQuery rules for any FpML 5-x views? If so, upon what timescale? IMHO, the priority order should be : precise > maintainable > optimised As (only one) member of the user community, I support the idea that the normative specification is written in a formally precise language and that any english text is non-normative and is designed to aid understanding. XPath/XQuery/xs:assert might not roll off the tongue, but at least they’re readily accessible open standards. If the specification is precise, I (and vendors) stand a fair chance of being able to implement alternative optimised versions. I thought XQuery is a full Turing-complete language, thus allowing the expression of potentially complex algorithms. Is the difficulty around “common financial markets practice” related to access to external reference data or transactional state? {{{ Andy
