520: VersionedTradeId has no id attribute
VersionedTradeId ought to carry an id (xsd:ID) attribute by symmetry with TradeId, enabling the versioned identifier to be referenced at the component level.
VersionedTradeId ought to carry an id (xsd:ID) attribute by symmetry with TradeId, enabling the versioned identifier to be referenced at the component level.
It now reads: … There can only be two domain values for this element: “aboveTrigger” or “belowTrigger”. The values are actually “Above” and “Below” as defined in type TriggerConditionEnum . I suggets to reword the annotation as follows: The condition that applies to a European-style trigger. It determines where the rate at expiry date and … Continued
The Stub complexType has defined as 1..* but the documentation consistently says that there can be up to two rates specified – suggest we change the cardinality to 1..2 instead.
There seem to be strange characters in the annotations in German. Apparently they make some tools choke. Example: fpml-shared-4-3.xsd Sofern nicht anderweitig festgelegt, das Haupt-Clearingsystem, das blicherweise fr die Regulierung von Geschften im entsprechenden Basiswert verwendet wird. I am not sure if this is a bug in the tools or in the schema. Same problem … Continued
Document element settlementType and settlementDate within OptionSettlement.model
Document element entitlementCurrency within OptionDenomination.model
Attached here are 11 additional rules proposed for Contracts Messaging.
We agreed to use XPath for paths and we use it everywhere except for contexts. The context paths should be changed to be XPath. ## Example with shared-5 ## Today we have: Context: payerPartyReference This would become: Context: //payerPartyReference ## Example with eqd-1 ## Today we have: Context: EquityAmericanExercise (complex type) This would become: Context: … Continued
In section 3.3.1.2 it says that the AcceptQuote is in response to the RequestQuoteResponse. How do I correlate them?
Add an existing assumption under “3.1.2 Design Assumptions”: “Communication order may vary from causal order. Communication order is the order in which messages are sent or received. Causal order is the order in which message should be processed. Use the definition of business process and the content of the messages to correlate them in causal … Continued