FpML Issues Tracker
closed
Minor
Always
Equity Derivatives
Admin
apparry
Summary
In the EQDWG rules the context of Equity Option needs to be indicated as a complex type, rather than a element.
The XPath for a type is "//element(*, EquityOption)". Although the VWG chose to use XPath for axis, they don't do this for contexts, where instead they use plain-ish English.
This change is to propose the EQD rules come into line with the VWG.
The contexts today: "# EquityOption, EquityDerivativeShortFormBase (complex type): eqd-17 eqd-18 eqd-19 eqd-20 "
The proposed contexts: "# EquityOption (complex type), EquityDerivativeShortFormBase (complex type): eqd-17 eqd-18 eqd-19 eqd-20 "
Without this change I would be looking for an element named "EquityOption", something which doesn't exist.
Notes:
mgratacos
05/09/08 1:40 pm
EQDWG 2008-05-09: agreement to implement as suggested.
matthewdr
08/20/08 9:15 am
This should have been implemented. It is 3 months since agreed, and nearly two months since the VWG agreed on the form of rules.
lyteck
08/20/08 2:12 pm
eqd-17: added (complex type) qualification to EquityOption context as agreed by Valwg (eqd-18, eqd-19, eqd-20 already fixed previously)
matthew
08/20/08 8:30 pm
Accepting upon review of resolution.