FpML Issues Tracker
closed
Major
Always
Schema
Admin
mgratacos
Summary
Add support for sending the master agreement to set up the master defaults.
This is necessary for people such as custodians who need a copy of the Master Agreement.
closed
Major
Always
Schema
Admin
mgratacos
Add support for sending the master agreement to set up the master defaults.
This is necessary for people such as custodians who need a copy of the Master Agreement.
Notes:
matthew
04/02/07 10:28 am
JPMC’s ‘house’ view on this is:
* FpML contracts must contain a reference to a master agreement within the documentation section. This should be an optional field and enforced by usage policy.
* A master agreement should be identified as a code and scheme.
* There should be a business process to message Master Agreements messages as tagged up content. The process may allow maintenance and updates to the Master Agreement.
* Refer to Allen & Overy who created “Legal FpML” 6 years ago. This tags up a Master Agreement. It is marked up text and not a data document.
* Legal verbiage should in principle be ‘content’ rather than ‘data’. Specifically, this refers to style. For example there may be mixed content.
matthew
04/04/07 12:49 pm
This is confirmed as the Master Confirmation, not the Master Agreement as originally stated.
The SWIFT CUG will always now use the long form, and therefore this issue goes away.
matthew
04/04/07 12:49 pm
Long form will be used.