Author: apparry

Any differences in the resulting content model should be signed off by the relevant working group

FpML-4-X has an implicit confirmation view. No operation entries should all be removed, example FpML-5-0 branch at revision 3382 file fpml-cd.xsd This element contains all the terms relevant to defining the fixed amounts/payments per the applicable ISDA definitions. FpML-4-4-4-WD-3 tag file fpml-cd.xsd This element contains all the terms relevant to defining the fixed amounts/payments per … Continued

Should use messageAddressScheme attribute as documented The data type used for identifying a message address. It includes a partyIdScheme for keeping the type backward compatible with the PartyId complex type. In the next major version, partyIdScheme attribute will be replaced by a messageAddressScheme attribute.

Marc Gratacos confirms that the FpML-5-0 trunk source code is being kept in the branch “FpML-5-0” within Subversion Source Control. This code does not build C:svnfpmlbranchesFpML-5-0>do-all confirmation > do-all-confirmation.log a copy of the build log is attached to this issue

Refers to version 4.3 and sourcecast module fpml401 Needs to be updated to FpML-5 and current build system

Samples in trunk are still FpML-4-4

Currently refers to FpML-4-4 Working Draft 2007-12-24

Currently refers to FpML-4-4

Remove types deprecated in FpML-4 from FpML-5

Caused by complex type BasicQuotation The base type which all FpML products extend. Per R. Stowsky proposal for pre-trade. TODO: This will require migrating BasicQuotation into shared to eliminate the dependency errors.