FpML Issues Tracker

987: changeEvent element has a redundant default value

October 8, 2009

closed

Minor

Have not tried

Schema

ktdonovan

mgratacos

Summary

The changeEvent element in the fpml-contract-notification-4-6 schema is abstract and has a default value set. I don't think this default is inherited by any substitutes of changeEvent so isn't the default redundant? Perhaps more importantly is default="ChangeEvent" just a typo and should it read type="ChangeEvent" which would make a great deal more sense.

Notes:

  • mgratacos

    10/08/09 3:09 pm

    Yes, you are absolutely right. It’s a typo and it should read type=”ChangeEvent”. I don’t think this issue has any impact on instance documents since the ChangeEvent type is empty so I propose we correct it in 4.7 and leave 4.6 Recommendation as it is.

  • mgratacos

    10/08/09 4:26 pm

    This has been corrected in the trunk (4.7).

  • mgratacos

    10/14/09 9:05 am

    This has been corrected in the 5.0 branch.

  • mgratacos

    10/14/09 9:14 am

    The correction will be published in the second working draft of version 4.7 and the fourth working draft of version 5.0.

    • 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