At present Cash is derived by restriction, which is a challenge for both Software Tools and Developers This could be avoided by forming a new UnderlyingAsset base class which contains only Cash and the present content of UnderlyingAsset could then be derived by extension
These are not related by any class relationship, both extend directly from UnderlyingAsset, using the same elements for all but the last two elements 1. Identical Content in Extension 2. Different Content in Extension ( naming only ? or intent ? ) ExchangeTradedContract Future
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
http://www.fpml.org/coding-scheme/ Forbidden You don’t have permission to access /coding-scheme/ on this server. Apache/2.0.50 (Fedora) Server at www.fpml.org Port 80
All samples should make correct use of business messages
________________________________________ 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
Elsewhere productType is minOccurs=”0″ maxOccurs=”unbounded”, such as in complex type product Please use model group to ensure consistent content