FpML Issues Tracker

227: Version Identification

September 29, 2006

closed

Major

Always

Schema

apparry

mgratacos

Summary

Version Identification is required in order to support unambiguous and correct automation of business processes

Please review file "fpml-doc-4-2.xsd" in branch "choreography"

Notes:

  • mgratacos

    10/11/06 9:44 am

    The Coordination Committee agreed to incorporate trade versioning.

  • mgratacos

    10/17/06 10:45 am

    Change has been committed to the trunk.

    • 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