1124: BusinessEventIdentifier should not reference “issuer”

Type BusinessEventIdentifier was introduced in 5-3 to support regulatory reporting workflows. The type contains an eventId element, preceded by a reference to the party who issued the eventId – this part is modelled as a choice between PartyAndAccountReferences.model and an “issuer” element of type PartyId. This model was introduced in 5-3 specfically to support the … Continued

1123: Wrong attribute type for complex type IdentifiedPayerReceiver

The fpml IRD xsd defines a complex type called IdentifiedPayerReceiver in file fpml-shared-5-3.xsd. This type has a single attribute called id of type xsd:ID which should indicate which counterparty of the trade is the payer or receiver. Using type xsd:ID is defining a new reference to be used somewhere else in the XML document when … Continued

1122: Fx Options – Strategy document

Hi I am working to build fx-ex23-straddle.xml in recordkeeping view. I am not able to add two fxoption elements to Strategy. In Strategy there is no method to set product. It’s accepting ProductIdArray and to set Array size there is no method available. With out defining the size of the array we not able to … Continued

1121: TradeReferenceInformation has no mandatory content

(1) Complex type TradeReferenceInformation has no mandatory content. This means that in the contexts where it is deployed within a choice (as TradeReferenceInformation.model, or indirectly via EventsOrInfo.model), the schema permits *no useful trade information* to be produced. This should be fixed by setting the occurrence of the partyTradeInformation element to 1..unbounded, instead of 0..unbounded as … Continued

1118: cd-21 first invalid input

It is unclear why the first invalid input, invalid-cd-21-01.xml, of rule cd-21 at http://www.fpml.org/spec/fpml-5-3-4-lcwd-1/html/confirmation/index.html is invalid. There is a comment in file invalid-cd-21-01.xml Based on this comment it seems that the cashSettlementTerms element should not exist at all in the invalid input. However, the rule states that the following elements must not exist (and not … Continued

1117: JAXB failed to generate Java calsses for all child types of Product

When people use xjc in JAXB to generate Java POJO classes for FpML 5.3, all the sub types under Product (eg. Swap, Fra & etc) become empty classes. The reason is that, in the Product.Model, FpML 5.3 uses a choice to support backward compatbility for assetClass enhancement. it contains 2 pieces: 1. new setup: primaryAssetClass, … Continued

1116: Recordkeping ‘valid’ message fails to parse

Test message valid-record_ex100a_new_trade_ack.xml appears to be invalid. The message fails to parse as elements and on lines 59 and 60 are unexpected. These data items are not present in the PartyTradeInformation complex type within the NonpublicExecutionReport structure in the fpml-recordkeeping-processes-5-3 schema

1115: Ambiguous XPath crashes JAXB compiler

We get an error when attempting to create JAXB business objects from the reporting schema because of an ambiguous XPath. The problem is with child elements named “definePosition” within complexType “PositionsAsserted”. I have attached XMLSpy snapshots illustrating the issue and our temporary resolution of it. I have also attached the modified XSD file. This is … Continued