looking at the latest in the trunk of SVN, there are a few problems with this example: 1) I see two loans examples in SVN with labeled 7, one is a repayment notice, the other an interest payment notice 2) loan-ex07-interest-payment-notice-jpm-1.xml has a few weird or wrong things, e.g. a. partyMessageInformation/partyReference is set and points … Continued
Section 3.1.7 on extending FpML 4.x needs updating to refer to FpML 5.0 and the updated architecture document. 3.1.7: “The FpML coordination committee is currently considering the types of information that would be useful to add for internal processing (i.e. management, risk and P&L reports, etc.) and the most appropriate location within the schema to … Continued
The MessageRejected process requires an observable completion to be valid with the FpML Business Process Architecture Design Assumptions. Section 3.1.2 states: “All business process definitions must have an observable completion. The set of messages defining a business process needs to be complete. In addition, timeouts must be defined if necessary.” Today, a MessageRejected may be … Continued
As agreed in the 4.x series (see AWG minutes, issue #161 resolution, and 4.x schema), the MessageAddress attribute partyIdScheme should be renamed messageAddressScheme in the 5.0 release. fpml-msg.xsd ” The data type used for identifying a message address. It includes a partyIdScheme for keeping the type backward compatible with the PartyId complex type. In the … Continued
Today the definition of NotificationMessage is: 1. NotificationMessage extends Message and mixes in NotificationMessageHeader. 2. Message does not contain MessageHeader. 3. NotificationMessageHeader extends MessageHeader. I suggest instead: 1. Message contains a Message Header. 2. NotificationMessage extends Message. The same is also true for RequestMessage and ResponseMessage. I propose the same for them also. This would … Continued
The invalid validation examples invalid-ird-32-00.xml is schema invalid. The validation examples should be schema invalid. The example invalid-ird-32-00.xml should be fixed. The offending piece of XML is: Standard ACT/360 It is missing an element.
The validation rule ird-35 doesn’t take into account schema optionality. The correct behaviour is for the validation rule to take into account the schema. The rule today is: ” Context: PaymentDates (complex type) ird-35 (Mandatory) firstPaymentDate < lastRegularPaymentDate. " The problem is that both firstPaymentDate and lastRegularPaymentDate are not required elements. A good example of … Continued
The validation invalid example invalid-ird-38-00.xml is schema invalid. The validation rule examples should all be schema valid. The problem is that the //fpml:initialStub and //fpml:finalStub are missing. Below is the offending snippet of XML.
The validation rule ird-46 doesn’t take account of the optionality of elements. The current rule is: ” Context: OptionalEarlyTermination (complex type) ird-46 (Mandatory) In cashSettlement/cashSettlementValuationDate/dateRelativeTo, the @href attribute must point to the @id attribute of cashSettlement/cashSettlementPaymentDate. ” A good example is valid-ird-46-01.xml. In this example, supposedly valid for this rule, the path //element(*, OptionalEarlyTermination)/cashSettlement/cashSettlementPaymentDate/relativeDate/dateRelativeTo/@href does … Continued
ird-47 doesn’t use XPath for axis. The Validation Architecture requires paths to be given using XPath for axis in the body of the rules. The rule should be changed to use XPath for axis. The rule today: ” ird-47 (Mandatory) In cashSettlement/cashSettlementPaymentDate/relativeDate/dateRelativeTo, the @href attribute must point to the @id attribute of americanExercise, bermudaExercise or … Continued