A model group (FloatingRateIndex.model) would keep consistency between types using the floatingRateIndex and the indexTenor elements (floatingRateCalculation, Fra,…) and it would facilitate extensions.
In Business Process Architecture, section 3.1.6, a text segment is repeated (see *repeated text* below) 3.1.6 Identification of Purpose The receiver of a message … The FpML message framework is based on type substitution (option 3 – By Element Type) as it gives the greatest control over validation whilst allowing easy extension of the message … Continued
FpML needs a consistent set of Core Data Types. There is a gap today where this part of the standard is left unspecified and it is causing us problems with implementing FpML. There is incompatability between market participants on data types, no agreement on field sizes, and efficiency problems in the implementation. Here is a … Continued
The use of the abbreviation MIME should always be capitalized. An example of misuse: Indicates the type of media used to store the content. mimeType is used to determine the software product(s) that can read the content. MIME Types are described in RFC 2046.
Money has no identity, it is a data type rather than a class type. Therefore it should not have an xsd:ID attribute. A type defining a currency amount. The currency in which an amount is denominated. The monetary quantity in currency units. Is the id attribute used anywhere?
The following types should be positiveInteger and not just integer: fpml-asset.xsd(325): fpml-asset.xsd(371): fpml-cd.xsd(639): fpml-cd.xsd(644): fpml-eqd.xsd(433): fpml-eq-shared.xsd(1188): fpml-riskdef.xsd(25): fpml-shared.xsd(611): fpml-shared.xsd(1327):
Party Portfolio name should not contain a party reference, just a name. Either the field is mis-named and mis-documented, or it is mis-modelled. A type to represent a portfolio name for a particular party. A pointer style reference to a party identifier defined elsewhere in the document. The party referenced has allocated the trade identifier.
There are message exchanges in FpML for which the completion is unobservable. It is not apparent to an observer when there will be a follow-up message and when the exchange is completed. For example, for the request quote it is not observable whether the interation completes with the RequestQuoteResponse, or whether there will be a … Continued
Please removed eventId. It duplicates conversationId. It should be removed. There seems to be a rough consensus on this (ex Brian), so please can we discuss at the AWG.
The FpML specification is unclear on the distinction between Transport Level and Business Level messages. For example, it is a generally received understanding, but remains unstated, that you cannot reject a rejectionMessagin. Either we follow 20022 and FIX and treat this as distinct levels: Transport Level and Business Level, or we create some sort of … Continued