The current definition of PartyRoleType seems specific to the reporting views but it is available in the Confirmation view too. The current scheme only has two values: AllPositions and SomePositions, which only make sense in position report context. I’d suggest making the type element within RelatedParty available only to the Reporting view.
In confirmation view the Events.model has an additionalEvent element defined as This in turn is defined as: Is this meant to be a sustitution point? None of the other ‘Events’ are built from any sort of abstract event model.
[Per Last Call Working Draft – July 29, 2011 (build 3)] The ClearingStatus message model is confusing: – is it the status of clearing as a whole or specific item(s) within clearing that is the subject matter? The wording clearingStatusItem suggests the latter; the specification documentation the former. – clearingStatusValue is unusual naming – without … Continued
In fpml-doc.xsd in version 5, per the original design of the new namespace approach in FpML 5, the version attribute should be validated using a pattern (5-?) rather than an enumeration. This will allow forward compatibility as defined in that decision. This change was overlooked in the setup of version 5.
Codelist bullion-delivery-location-1-0 (all versions from FpML 4-6 to 5-1): Copy-and-paste error in documentation of value “Zurich” (my *emphasis*): Delivery will be made to the Purchaser of Bullion’s custodian bank in *London*. Custodian bank to be agreed by the parties.
Tried validating trades after unzipping the confirmation-5-2_xml.zip. Found that the fpml-mktenv-5-2.xsd includes itself. This doesn’t make sense and illegal (section 2.6 of the xslt 1.0 spec).
Could we evaluate if the FX Average Rate Option’s strike is properly represented see a question on the forum – http://www.fpml.org/dev/modules/newbbex/viewtopic.php?topic_id=146&forum=4 Should the “strike” be expanded to support the average strike option product?
We need to cross check the points in the schema that use the payer/receiver and buyer/seller model group. Some rules may need to be revised and some rules may be missing.
– quantityFrequencyScheme – attribute name is inconsistent with scheme name (commodityFrequencyScheme) – The following coding schemes are missing from http://www.fpml.org/coding-scheme: – commodityOilProductTypeScheme – commodityExpireRelativeToEventScheme – commodityPayRelativeToEventScheme – deliveryPointScheme – gasQualityScheme
On behalf of andyjm on the FpML Forum(http://www.fpml.org/dev/modules/newbbex/viewtopic.php?forum=2&post_id=325&topic_id=143#forumpost325): Float Rate Index I would like to propose that CNY-CNREPOFIX=CFXS-Reuters be added as float rate index in the next update. The index is noted as supplement #21 to the 2006 ISDA defintions. Thanks.