318: Consistent tagging convention

Please adopt a simple, consistent tagging convention, that states version, status, and revision within a status The most recent tag appears to be FpML43WD1-wd-fpml-4-3-2007-02-05 this should just simply be tagged FpML-4-3-WD-1 following the suggested convention FpML-major-minor-status-revision

269: MessageRejected content model

MessageRejected content model does not allow identification of the message which has been rejected by the sender of MessageRejected, the only content allowed at present is reason and additionalData, which also does not allow explicit identification of the system which rejected the message, as opposed to the system which is sending the MessageRejected message

258: relatedExchangeId and optionsExchangeId

Repeated and inconsistent declerations of this content are made throughout the file “fpml-asset-4-2.xsd” #1 Bond: why does this have no optionsExchangeId to allow for on exchange bond options ? #2 EquityAsset: repeated decleration, optionsExchangeId should be unbounded, option on this equity could be traded on many exchanges #3 ExchangeTradedAsset: repeated and inconsistent declaration ! now … Continued

257: Refactor UnderlyingAsset

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

256: ExchangeTradedContract vs Future

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