Modeling change recommendation: Eliminate the use of a leg substitution group in EQD and replace with specific products containing defined leg types. General clean up of eqd-, eq-shared, return-swap files to ensure that products are defined consistently and in the right file.
Modeling change recommendation: Review element names and remove product prefixes where they are present (e.g. equityEffectiveDate).
Modeling change recommendation: Eliminate use of substitution groups in favor of choices with a restricted list of values for underlying assets, similar to the reference obligation for CDS.
Modeling change recommendation: consolidate singlePayment and initialPayment into one type with multiple cardinality and explicit directionality. The name of this element should if possible be consistent with IRD if possible.
Modeling change recommendation to standardize payment and premium structures. For the option premiums, this will be achieved by fully implement the generic model. For other payment types, we will migrate to the content model of SimplePayment.
Modeling Task Force recommendation: Eliminate standalone adjustable[…]Date and adjusted[…]Date elements throughout the schema, and replace with the version 5 AdjustableDate types, which includes either or both.
A simple adjustment to the content model of Discounting allows business rule ird-32 to be retired – please see proposal document and modified ird schema attached.
Feedback from Harry: The explanation of how preconditions for validation rules are evaluated. The following text needs to be revised: “The Validation Preconditions only apply when specific rules reference them. The following preconditions are always to be executed relative to the root of the FpML document being validated. The context of the rule is NOT … Continued
FpML 4.3 states it is backwards compatible with 4.2 (http://www.fpml.org/spec/2007/lcwd-fpml-4-3-2007-10-30/html/index.html with one proviso 1.6.2.1) If this is true, one should be able to validate a 4.2 message using the 4.3 schema in any tool that supports validation against schema. However, this is not possible due to the namespace naming policy. http://www.fpml.org/spec/2007/tr-fpml-arch-2-1-2007-09-17/ – 4.4.1 That calls … Continued
At the moment it is just a TODO in the trunk: ISDA2002 ISDA2002Equity TODO