Take a look at the html in the src/choreography/html folder and see what you think.
Questions and issues to consider: 1. Is this correct? If not what is wrong with it? 2. Identity - xsi:type + tradeIdentifier + versionIs this correct? The choreography can support multiple and different identities as single or composite keys. What is important is to locate or bind these identities in the message to the ChannelType. You can see this in the choreography. We do need identities because without them one cannot monitor what is going on at all. With a choreography one has the possibility of monitoring against plan (the choreography description) which
is a stronger form of monitoring.What about allocations? How do they relate to trades? How do we distinguish between them and the underlying trade?
3. +ve ack as opposed to noneThere are none in this model. Should it be supported? Do we need two models on for +ve ack and one for no ack?
4. Confirmations for other business eventsOnly for new's and maybe amendments, what about increase/decrease/ novation etc? If we can agree to this process then what about doing the rest? How do we deal with things that might happen as opposed to things that have happened.
5. What artifacts from a choroegraphy suite are desirable for the standard (i.e. to be included)?
The model itself in various forms (BPMN, UML, WS-CDL, HTML)?Scenarios that have been validated against the model (i.e. sequence diagrams)? Does the HTML textual version need to be changed - to add more or less - to be included directly in the
documentation?These are some of my questions/issues at the moment. I am sure there will be others from Matthew and Brian in due course
as well as from many others. Cheers Steve T
Attachment:
Confirmations-FpML4.3.zip
Description: Zip archive