Only response to proposal was from Jean-Jacques who stated that perhaps the transaction ids should be block specific rather than global to the entire envelope. Erik talked to Jeff about Jean-Jacques proposal and he felt that perhaps begging the question as to whether XMLP could recursively contain other Envelopes. That would handle the case that Jean-Jacques mentioned. To summarize, where we put the transaction id may be in envelope, app specific, or by block. Why not have block specific transaction ids.
Intent is to correlate requests and responses.
We should be using a different term such as correlation id. We need to think about the range of message patterns that we will support. Put in headers when we can, but it can sometimes be clunky. Question as to what is the scope. Because can mean something different to different applications we can't apply semantics to it.