The party definition in fpml-doc-4-2.xsd at /xsd:schema/xsd:complexType/xsd:complexContent/xsd:extension/xsd:sequence/xsd:element/xsd:annotation/xsd:documentation is incorrect. It states: “The parties obligated to make payments from time to time during the term of the trade. This will include, at a minimum, the principal parties involved in the swap or forward rate agreement. Other parties paying or receiving fees, commissions etc. must also be … Continued
There is no definition of what a scheme is and how it is to be used within the manual. For example I had a user add a scheme for a “parent account”, and “child account”, and “currency scheme” within a party’s Account in a trade. There needs to be a rule in the manual that … Continued
A global type describing the payment exposed to the matching process, along with its gross component(s) and calculation details. Unique identifier assigned by either party or matching service, as agreed, to a payment.
paymentAmount should be renamed amount. The word “payment” is redundant. A global type describing the payment exposed to the matching process, along with its gross component(s) and calculation details. Unique identifier assigned by either party or matching service, as agreed, to a payment.
FpML currently supports placing an order with a single market participant. We need FpML to support placing an order with a market. The main additional type will be the taking of the order from the market.
credit-seniority-trading is a coding scheme that contains two values – its contents declare that it “Specifies the seniority of the reference obligation used in a single name credit default swap trade”. There is however no defined type in FpML that lists this coding scheme as its default. So we do not know if there is … Continued
________________________________________ From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-comments-request@w3.org] On Behalf Of Jonathan Marsh Sent: 20 October 2006 21:57 To: matthew.d.rawlings@jpmchase.com Cc: ylafon@w3.org; Steve Ross-Talbot; stabet@ruleml.org; public-ws-desc-comments@w3.org Subject: RE: XML Schema requires a type in addition to name to identify an element Thanks for your comment. The WS Description Working Group tracked this issue as a CR078 [1]. The Working … Continued
Indication Of Interest and Advertisements are currently not supported in FpML.
Part of the Messaging Layer: BusinessMessage ConsistentStateMessage DestroyUniverseOfInterest EventMarkerRequest MessageAccepted MessageConsumed MessageDelivered MessageHandled MessagesConsumedByAll MessagesHandledByAll NotYetConsistent RegisterUniverseOfInterest RequestReply
If the choreography model shows that some message types are not needed, they should be deprecated and removed in the next major version.