FpML Issues Tracker

Summary

It is highly probable that if an FpML product definition is used internally with an organization the FpML may be embedded within some proprietary XML. In such cases it may prove desirable to be able to reference in to the FpML product definition.

FpML 1.0 provides a basic reference mechanism based on the use of the id and href attributes. Currently, the requirement for each id attribute in FpML 1.0 has been driven from a need to reference that id from one or more href attributes defined within the FpML 1.0 tag set. For example, the id attribute on the tag would logically be referenced through href attributes on the tags , , , and .

It would seem sensible to extend this concept and allow id attributes to optionally be specified on additional elements where there may be a requirement to reference those elements from outside the existing FpML 1.0 tag set. For example, consider a case where an FpML trade definition is used for application integration within an organization. An application may have a identifier for each individual stream within a trade, e.g. a simple sequence number such as 1, 2, 3 etc. or a named type - simpleFixed, simpleFloating etc. and may wish to associate additional information such as a trading book with each stream. By adding an id attribute to the swapStream element it would be possible to reference an individual stream from within a proprietary tag set where additional stream attributes could be held.

A review of the current tag set would suggest the following elements where there is arguably a business rationale for allowing an id attribute. These elements all have occurrence rules or '*' or '+', i.e. they are repeating elements. Alternatively, an id attribute could be allowed on any FpML 1.0 element.

additionalPayment calculationPeriod floatingRate otherPartyPayment partyTradeIdentifier paymentCalculationPeriod principalExchange rateObservation step swapStream trade tradeId

Guy Gurden J.P. Morgan