FpML Issues Tracker

225: No operation use of xsd:restriction

September 29, 2006

closed

Major

Always

Schema

apparry

mgratacos

Summary

Schema commonly uses xsd:restriction for "no-op" where content is restricted out, and them restored, providing no value to the content model produced, and causing additional difficulty for software tools and our user community

Please review the file "fpml-msg-4-2.xsd" in the "choreography" branch on the FpML Subversion Server

where I have derived the current content model without the use of restriction

This approach should be extended to remove the derivation of Cash by restriction of UnderlyingAsset, so that we would not longer have to use xsd:restriction within FpML, but would have identicial content models

Notes:

  • mgratacos

    10/04/06 4:28 am

    xsd:restriction has been removed from message header and from cash underlying asset. Proposal will be presented to Coord and if no objections are raised, this will be published in the next release of FpML (4.3 WD or 4.2 Third Trial Recommendation).

    • 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