This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Transport"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
#The entire infrastructure that serves the HL7 messages transfer from the Sending [[Application Role]] to the Receiving [[Application Role]]. In other words: all transport activities supported by OSI layers 1-6. The OSI layers 1-6 are perceived by the [[HL7 Application]]s as the unified interface for message transfer, meaning that an [[HL7 Application]] is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5. Note however that the usage of the term Transport in this context is '''strongly discouraged''', since it's misleading and does not comply to OSI defintions of layers responsibilities. We strongly recommend the usage of term [[Messaging Infrastructure Layer]] for this purpose in all HL7 documents. | #The entire infrastructure that serves the HL7 messages transfer from the Sending [[Application Role]] to the Receiving [[Application Role]]. In other words: all transport activities supported by OSI layers 1-6. The OSI layers 1-6 are perceived by the [[HL7 Application]]s as the unified interface for message transfer, meaning that an [[HL7 Application]] is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5. Note however that the usage of the term Transport in this context is '''strongly discouraged''', since it's misleading and does not comply to OSI defintions of layers responsibilities. We strongly recommend the usage of term [[Messaging Infrastructure Layer]] for this purpose in all HL7 documents. | ||
#A specific [[Transport Protocol]] (OSI layer 1-4) that facilitates the routing, switching and transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control (for example TCP/IP, UDP/IP, NETBEUI). | #A specific [[Transport Protocol]] (OSI layer 1-4) that facilitates the routing, switching and transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control (for example TCP/IP, UDP/IP, NETBEUI). | ||
| − | ##(Miroslav) Question - does this refers to the MLLP | + | ##(Miroslav) Question - in the HL7 world, does this refers to the MLLP transports only? Or in other words, do we have in SOA environments the usage of the word transport refering to for 1-4 OSI layers in (which would be a potential problem in interpretation of the term)? |
##All the above states is that there are 2 known usages of the word "Transport". If SOA environments have a third one (which is different) then it should simply be added. The word "Transport" is too generic to assign 1 single meaning to it within HL7. [[User:Rene spronk|Rene spronk]] 09:27, 10 Mar 2006 (CST) | ##All the above states is that there are 2 known usages of the word "Transport". If SOA environments have a third one (which is different) then it should simply be added. The word "Transport" is too generic to assign 1 single meaning to it within HL7. [[User:Rene spronk|Rene spronk]] 09:27, 10 Mar 2006 (CST) | ||
###(Miroslav) Additional comment - we need to ensure that SOA SIG and other Messaging Infrastructure technologies use the word transport in the right manner as well. | ###(Miroslav) Additional comment - we need to ensure that SOA SIG and other Messaging Infrastructure technologies use the word transport in the right manner as well. | ||
Revision as of 14:49, 12 April 2006
Transport is an ambiguous term, which is used in HL7 to identify the following:
- The entire infrastructure that serves the HL7 messages transfer from the Sending Application Role to the Receiving Application Role. In other words: all transport activities supported by OSI layers 1-6. The OSI layers 1-6 are perceived by the HL7 Applications as the unified interface for message transfer, meaning that an HL7 Application is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5. Note however that the usage of the term Transport in this context is strongly discouraged, since it's misleading and does not comply to OSI defintions of layers responsibilities. We strongly recommend the usage of term Messaging Infrastructure Layer for this purpose in all HL7 documents.
- A specific Transport Protocol (OSI layer 1-4) that facilitates the routing, switching and transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control (for example TCP/IP, UDP/IP, NETBEUI).
- (Miroslav) Question - in the HL7 world, does this refers to the MLLP transports only? Or in other words, do we have in SOA environments the usage of the word transport refering to for 1-4 OSI layers in (which would be a potential problem in interpretation of the term)?
- All the above states is that there are 2 known usages of the word "Transport". If SOA environments have a third one (which is different) then it should simply be added. The word "Transport" is too generic to assign 1 single meaning to it within HL7. Rene spronk 09:27, 10 Mar 2006 (CST)
- (Miroslav) Additional comment - we need to ensure that SOA SIG and other Messaging Infrastructure technologies use the word transport in the right manner as well.
Back to the Open_ATS_Issues
