This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Open ATS Issues"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (new page, copied ATS contents from open MCCI issues list) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | |||
*Translations: add "derived from .. ID" attribute ?, much like acknowledgementOf. See also MCCI line-item 157. | *Translations: add "derived from .. ID" attribute ?, much like acknowledgementOf. See also MCCI line-item 157. | ||
*[[Message.id]] "sameness" discussion after transformation by a Gateway. | *[[Message.id]] "sameness" discussion after transformation by a Gateway. | ||
**New motion of MnM: 20060113: "At the semantic (or: business process level) the contents of the Transmission wrapper, with the exception of InteractionID, are not relevant when determining if 2 interactions are the same. At the transmission-level 2 Transmissions are the same if they have the same Transmission.id." | **New motion of MnM: 20060113: "At the semantic (or: business process level) the contents of the Transmission wrapper, with the exception of InteractionID, are not relevant when determining if 2 interactions are the same. At the transmission-level 2 Transmissions are the same if they have the same Transmission.id." | ||
**This has the consequence that the sameness of Transmission.id is not linked to the wider topic of semantic-transmission sameness. | **This has the consequence that the sameness of Transmission.id is not linked to the wider topic of semantic-transmission sameness. | ||
| + | *Use of the AttentionLine class to add route-tracing information in a Transmission that's being routed/gatewayed to its destination. Are Gateways/Bridges able to add their own information to the Transmission Wrapper in the form of an additional AttentionLine? | ||
Revision as of 07:39, 5 March 2006
- Translations: add "derived from .. ID" attribute ?, much like acknowledgementOf. See also MCCI line-item 157.
- Message.id "sameness" discussion after transformation by a Gateway.
- New motion of MnM: 20060113: "At the semantic (or: business process level) the contents of the Transmission wrapper, with the exception of InteractionID, are not relevant when determining if 2 interactions are the same. At the transmission-level 2 Transmissions are the same if they have the same Transmission.id."
- This has the consequence that the sameness of Transmission.id is not linked to the wider topic of semantic-transmission sameness.
- Use of the AttentionLine class to add route-tracing information in a Transmission that's being routed/gatewayed to its destination. Are Gateways/Bridges able to add their own information to the Transmission Wrapper in the form of an additional AttentionLine?
