FpML Issues Tracker

591: Definition of the semantics of optionality

February 22, 2008

closed

Major

Always

Modeling Task Force

Admin

andrew

Summary

I was exchanging messages with a counterparty and we couldn't agree on the meaning of an optional element.

The element is //element(*, Trade)/documentation. It is an optional element. What does it mean when the field is present or not present? Is it: - Whether it is known or not by the sender? - Whether it matters or not? - Whether it exists or not? - Whether is it implicit or not? - etc.

We couldn't find a definition in the documentation of what it meant. What does it mean? Does this apply to all optional elements? Should they be defined?

http://www.fpml.org/dev/modules/newbbex/viewtopic.php?topic_id=37&forum=4

Notes:

  • matthewdr

    03/13/08 2:01 pm

    Discussed at the AWG.

    The prevailing view, led by Andrew Jacobs, is that the Documentation is a property of the product/instrument and not the trade.

    Brian proposed a code to say there is none. Jason and Marc proposed using xsi:nil to say there is no value. The interpretation of non-null absence means it just isn’t being stated.

    Agreed to pass to the MTF.

  • iyermakova

    09/05/08 4:54 pm

  • mgratacos

    11/12/19 7:33 am

    AWG 2019-11-07

    • The changes in booleans and the generation of views, in which we are capable of removing elements, should solve this issue.
    • Agreement to close the issue.

    • 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