FpML Issues Tracker

538: The meaning of optional Boolean fields is not always clear and consistent.

January 4, 2008

closed

Major

Always

Modeling Task Force

Admin

benjlis

Summary

Modeling change recommendation: Eliminate the optional empty element as a synonym for Boolean and replace with Boolean. This will clarify meaning, e.g. for short form vs. long form, at the expense of some extra verbosity.

Attachments

  • MTF-538-Booleans_FpML_40vs44_v103_20080730.xls

    • Notes:

  • iyermakova

    01/04/08 9:09 pm

    Reviewed at Modeling Task Force on 01-04-2008. Assigned the issue to CD Working Group.

  • lyteck

    07/30/08 8:08 pm

    The attached spreadsheet lists:
    1. Booleans of type xsd:Boolean
    2. Booleans of type Empty

    (previous version of the Excel Spreadsheet was last circulated in January via the MTF mailing list)

  • lyteck

    08/07/08 8:36 pm

    MTF 8/01/08 action item: Lyteck to split list of booleans by working group and ask for input on each, creating a separate issue for each WG.

  • mgratacos

    02/06/20 1:08 pm

    AWG 2020-02-06

    • Most empty elements were changed to booleans in version 5.0.
    • The issue can be closed.

    • 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