390: Provide the ability to unmatch

Provide the mechanism to unmatch a trade. Omgeo has this ability, and we need it for OTC’s. The typical scenario is that a counterparty matches a trade incorrectly or more than once.

389: Add additional value to settlement rate option coding scheme to support Brazilian Real

We request the following code be added to the settlement rate option coding scheme to support FpML representation of Brazilian Real interest rate swaps. BRL09 is defined by ISDA/EMTA in the Compendium of Amendments to Annex A to the 1998 FX and Currency Option Definitions available at the following link: http://www.isda.org/publications/pdf/Annex-A-Compendium.pdf Code: BRL.PTAX/BRL09 The Spot … Continued

385: Ban on floating comments

Add a section to the Architecture document that prohibits the use of floating comments. xsd:annotation must be used instead.

384: Remove floating comments

Line 97 of fpml-credit-event-notification Describes the resource that contains the media representation of a business event. For example, can describe a file or a URL that represents the event.

383: Is annotation for TradeAmended type correct?

The annotation reads as follows: “This message is DEPRECATED and should not be used in new implementations. See ContractCreated. A notification to inform downstream systems when a system that acts as source of trade information detects that a trade has been modified.” Why should ContractCreated be used in place of TradeAmended? Should it not be … Continued

382: Deprecated annotation

Add a deprecated flag as an attribute to the FpML XML Schema for deprecated features. Visual Studio uses “vs:deprecated” in XML Schema as XSD anntotation. I suggest we use “fpa:deprecated” to mark something as deprecated.