FpML Issues Tracker

233: ValuationReport and PositionReport have the same content model

October 18, 2006

closed

Major

Always

Schema

Admin

mgratacos

Summary

Both messages have a very similar content model. We should deprecate one of them.

Notes:

  • BrianLynn

    03/14/07 10:15 pm

    PositionReport was added to support the type of report required by the DSWG. It has a different representation from ValuationReport. It doesn’t support reporting on portfolios, nor reporting of sensitivity sets. On the other hand, it does support reporting of scheduled dates. At the time the working group added the PositionReport the overlap was considered and the group concluded that the benefits of the new message outweighed the potential overlap, as the messages have different purposes and audiences. Unless a member of the group proposes a new message that includes the capabilities of both existing messages, and the group agrees to this, no action is recommended.

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue