Latest Posts

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.

Add to the the Architecture Definition a pattern for distinguishing between Definitions and References. For example the distinction between the definition of a trade and a tradeId is clear from the element name. “trade” is a definition and “tradeId” is a reference. However for some types this is not consistent, for example asset. The distinction … Continued

Please find my feedback on the ext2 extensions: 1. Why is ext:flatOfAccruedInterest a property of the bond contract rather than the price? 2. I thought clean and flat were equivalent? 3. ext:Bond is not a bond but the reference to identify the Bond. This is analgous to the difference between a country definition and a … Continued

Add a rule to the architecture that requires the target of an href to be in scope of the schema referring to it. For example the schema containing the complex type AssetReference must directly or indirectly include or import the schema containing the complex type Asset. The effect of this rule was request by Simon … Continued

Add a category of “Architecture” to the issue management system. This would allow us to classify issues as being assigned against the architecture of FpML.

The FpML extensions in the ext2 branch should be properly reviewed. Please create a working group to review the extensions.

The annotation/documentation for complexType “Trade” in fpml-doc-4-x.xsd reads: “A type definiting an FpML trade.” – should read: “A type defining an FpML trade.” (we’ll leave the definition of what a “trade” actually means to another time …)

Documentation says “An abstract pricing structure base type.” but the abstract attribute is not set to true.

Add a rule to the architecture for 5.0 that states that each href must point to a single type. Leave the modelling of the implementation to the Product and Process groups.

Please add an FpML 6.0 WD1 to the Product Version for us to lodge items that won’t make it into FpML 5.0.