Author: Admin

513: Use XPath for contexts for precision

By

We agreed to use XPath for paths and we use it everywhere except for contexts. The context paths should be changed to be XPath. ## Example with shared-5 ## Today we have: Context: payerPartyReference This would become: Context: //payerPartyReference ## Example with eqd-1 ## Today we have: Context: EquityAmericanExercise (complex type) This would become: Context: … Continued

511: Causal order design assumption

By

Add an existing assumption under “3.1.2 Design Assumptions”: “Communication order may vary from causal order. Communication order is the order in which messages are sent or received. Causal order is the order in which message should be processed. Use the definition of business process and the content of the messages to correlate them in causal … Continued

510: Confusion of normative and non-normative

By

# http://www.fpml.org/spec/2007/wd-fpml-4-4-2007-09-10/html/index.html “Business Process All the parties must follow the same business processes and respond appropriately to any communication they receive. To support business process the messaging working group has extended the core FpML grammar to add a framework for defining messages and their content. This section describes some business processes and shows how they … Continued

509: ChangeContract definition for date

By

The date property of ChangeContract is incorrectly defined. Today: The date on which the the parties enter into the change. It should be changed in both property name and definition: The date on which the the parties agreed to enter into the change.

508: ContractFullTermination

By

The definition is incorrect. It is not just notification of the historic fact of termination, but also notice of an agreed termination. There is nothing to stop the effectiveDate being future dated. Please change the comment. Notification of the historic fact that a Contract has been Fully Terminated. A seperate notification message is provided for … Continued