[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FpML-AWG core data types



I’d like to re-launch the work on core data types. Please, see issue ticket for some background discussion http://www.fpml.org/issues/view.php?id=313

 

My opinion in terms of principles for this:

  1. Enforcement should be done at the schema level, not as guideline.
    • People pay less attention to guidelines than schema definitions.
    • Benefits of schema implementation are not available in a guideline document.
  2. Data types should bring value to the grammar. Data types that don’t bring any value to existing types or to existing xsd simple types should not be incorporated.
    • i.e. What’s the value of a new type that is equivalent to an existing xsd type?
    • i.e. There is value in having a common data type for all schemes. Inconsistency between them is a problem currently.
  3. Convergence with other standards is good and necessary but only when types bring value to the grammar and don’t confuse existing users.
    • The distinction between basis points and percentage would introduce confusion to FpML.
    • What’s the value of having a generic Numeric data type?

 

Opinions on this are very welcome.

 

I’ll send a separate e-mail with my suggested changes to the current proposal.

 

Kind Regards,

-Marc

+13472846531

 

 

************************************************************************************************************************** The information contained in either this email and, if applicable, the attachment, are confidential and are intended only for the recipient. The contents of either the email or the attachment may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, or distribution is prohibited and may be unlawful. If you have received this communication in error, please notify us by e-mail at isda@xxxxxxxx then delete the e-mail and all attachments and any copies thereof. This communication is part of an ISDA process and is not intended for unauthorized use or distribution. **************************************************************************************************************************