This wiki has undergone a migration to Confluence found Here
Open ATS Issues
Revision as of 09:33, 29 March 2006 by Rene spronk (talk | contribs) (add source and estination as open gloassary items)
- 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?
(Miroslav) Adding the defintions of the terms used throughout ATS. The aim of this section is to identify the most important ATS notions and artefacts, and word smith their defintions. Once we reach the consensus, we'll transfer them to the normative material for official balloting.
- Transport (in regard to the ATS ballot reconciliation package line item 2, database record number 5)
- Message Exchange Pattern (Action Item 1026)
- Message Infrastructure Fault (in regard to the ATS ballot reconciliation package line item 49, database record number 61, related to Application Fault)
- Gateway, Bridge, Interface Engine, Transformer Bridge, Message Broker (in regard to the ATS ballot reconciliation package line items 53-57)
- HL7 Application
- Source, Destination (unified glossary definition from both ATS as well as webservices perspective)
