FpML Issues Tracker

139: Unique build number

November 2, 2005

closed

Major

Always

Request New Feature

Admin

mgratacos

Summary

I request a unique build number.

At the moment there is no unique identifier (such as a build number) to identify each release.

For example FpML 4.2 WD#2 went through 3 releases due to errata. It is currently impossible to distinguish each version of the errata.

This caused me problems with a vendor. The vendor coded to match FpML 4.2 WD#2 release 1. I had built software to FpML 4.2 WD#2 release 3. You can understand the problem.

Notes:

  • matthew

    05/16/06 6:03 am

  • matthew

    05/16/06 8:58 am

    In telephone discussion with Marc Gratacos I asked for the build number to go in the comment at the top of the XSD file.

  • matthew

    05/16/06 9:00 am

    Marc Gratacos stated the intent of the Coordination Committee wasn’t clear. Marc will ask for further clarification with suggestions.

  • matthew

    06/30/06 2:36 pm

    Any progress in the past 6 weeks?

  • mgratacos

    07/03/06 5:27 am

    The build number was added at the 4.2 Trial Recommendation specifications in the main page of the specifications http://www.fpml.org/spec/2006/tr-fpml-4-2-2006-05-08/html/fpml-4-2-intro-frame.html and the Errata page http://www.fpml.org/spec/errata/tr-fpml-4-2-2006-05-08-errata.html

    There hasn’t been agreement about publishing this in the schema as well since this is not versioning the schema but the entire set of specifications including schema, examples, validation rules, documentation. I need to follow up with AWG.

  • matthew

    10/05/06 5:44 pm

    This is nearly a year old. It is time to make some progress!

  • mgratacos

    10/06/06 9:35 am

    Add file revision number and build number to each subschema file.

  • mgratacos

    10/09/06 5:17 pm

    File revision number has been added to each subschema file in the version attribute: version=”$Revision$”

  • mgratacos

    10/10/06 9:02 am

    New actualBuild attribute defines the build number of the schema.




    Indicate which version of the FpML Schema an FpML message adheres to.











    The message creator can send the build number of the schema on which they built the messages against.




    Taken from the schemas that the recipient validated against. Every time there is an issue listed on the errata, not major, but that requires an update on the current specification, the actual build number is updated.


  • mgratacos

    10/17/06 10:47 am

    Changes have been committed to the trunk. They are ready to be published in the next release of FpML.

    • 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