FpML Issues Tracker

727: tightening up backwards compatability to support fpmlVersion attribute

May 29, 2008

closed

Minor

Always

Architecture

Admin

andrew

Summary

The current definition of "Backwards Compatability" is loosely defined. For the fpmlVersion attribute to work backwards compatability will need to be tightened up.

5.5 Backwards Compatibility Where possible, every attempt should be made to keep changes to the FpML schema as backwards compatible as possible. In general, the loosening of restriction, or the adding of new optional elements is backwards compatible. For example, adding a completely new financial product in the form of a new substitutable element to the schema will not affect any existing products and the model is backwards compatible with previous releases.

http://www.fpml.org/spec/2007/rec-fpml-arch-2-1-2007-12-14/rec-fpml-arch-2-1-2007-12-14.html#s5.5

Notes:

  • andrew

    10/02/08 11:13 am

    The suggested changes have be merged into the 2.2 and 3.0 specification texts with modification.

  • andrew

    10/02/08 1:54 pm

    AWG agreed on 02-10-2008 to close this issue.

  • Leave an update

    You must be logged in to post an update.