With two exceptions*, every sample message under the recordkeeping and transparency views uses an LEI as the UTI issuer identifier (issuerIdScheme=”http://www.fpml.org/coding-scheme/external/iso17442″). The CFTC has explicitly stated the the LEI will *not* be used to identify the issuer of the unique transaction identifier. The samples must be amended to so that the issuer conforms to the … Continued
“Validation of the Recordkeeping view for a Post trade event generates a warning with the following message : /fpml-riskdef-5-3.xsd includes itself recursively To correct the line below needs to be removed or commented:
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
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
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
(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
There is an inconsistent representation of rule cd-1b in FpML Version 4.9 REC. The English description saying “must be after” I would have thought should be ‘ gt ‘ in the XPath rather than ‘ ge ‘ as below. Reported via email by Ivan Djurkin.
i am using XMLBeans for code generation form the master schema. code generator hasn’t generated class for TradeInformation which is an important tag if i have to create the RT message. Any help or guidance would be highly appreciated.
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
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