FpML Issues Tracker
closed
Minor
Always
Architecture
Admin
andrew
Summary
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 place it. These enhancements will be included in a future release of FpML but in the mean time the FpML 2.0 Architecture specification contains examples of how bespoke extensions can be made to achieve this with the FpML 4.0 schema."
Notes:
andrew
03/17/08 12:29 pm
I disagree. There is no need for this document to refer directly to later version. The Architecture 3.0 is published along side FpML 5.0 working drafts.
If the 4.x series continues to be updated in parallel to 5.0 then there may be a need to release updated 2.x architecture specifications to accompany them.
matthewdr
03/17/08 12:39 pm
Andrew – it is not clear what you disagree about. Your comment to update 2.x architecture works fine with the proposal.
The proposal is that FpML 5.x should refer to how to extend FpML 5.x, and not FpML 4.x. Guidelines for extending 4.x won’t help when 5.x is being used.
mgratacos
05/29/08 2:30 pm
I’d change the current text from:
3.1.7 Representing Internal Trades
The focus of FpML to date has been on the focus description of trades for B2B purposes. At the same time many of the existing implementations have been for internal trade exchanges between systems.
Extending FpML to handle internal trade information entails adding additional elements to the current schema to hold the values needed to categorize a trade for internal purposes. There are several ways this information could be added to the schema (e.g. optional elements, alternative inheritance structures, inheritance by restriction) each with its own properties in terms of ease of validation or affects on document style.
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 place it. These enhancements will be included in a future release of FpML but in the mean time the FpML 2.0 Architecture specification contains examples of how bespoke extensions can be made to achieve this with the FpML 4.0 schema.
to:
3.1.7 Representing Internal Trades
The focus of FpML to date has been on the focus description of trades for B2B purposes. At the same time many of the existing implementations have been for internal trade exchanges between systems.
Extending FpML to handle internal trade information entails adding additional elements to the current schema to hold the values needed to categorize a trade for internal purposes. There are several ways this information could be added to the schema (e.g. optional elements, alternative inheritance structures, inheritance by restriction) each with its own properties in terms of ease of validation or affects on document style. The FpML Architecture specification contains examples of how bespoke extensions can be made to the schema.
Thanks
Andrew Jacobs
Director, HandCoded Consulting Ltd.
Director, HandCoded Software Ltd.
mgratacos
06/16/08 10:11 am
This has been committed to the 5.0 branch and trunk since the suggested change was also applicable to the 4.x versions.