ISO 9735-3:2002 pdf download

ISO 9735-3:2002 pdf download.Electronic data interchange for
administration, commerce and transport (EDIFACT)一Application level syntax rules (Syntax version number: 4, Syntax release number: 1)一 Part 3: Syntax rules specific to interactive EDI.
7 Dialogue control
An I-EDI transaction, which is an instance of a particular scenario, consists of one or more dialogues, occurring either concurrently or sequentially between two or more parties.
A dialogue consists of an interleaved pair of EDIFACT interchanges; an initiator interchange and a responder interchange.
The following transfers shall take place:
— An initiator begins a dialogue by sending an interchange header segment to a responder, optionally preceded by a UNA, and optionally followed by a message.
The responder replies to the initiator with an interchange header segment, optionally followed by a message (note that the values of the UNA sent by the initiator also apply to the responder).
— The initiator sends a query message to the responder.
— The responder replies to the initiator with a response message.
— The initiator and responder exchange additional messages, as necessary.
— The initiator ends the dialogue by sending an interchange trailer segment to the responder, optionally preceded by a message.
— The responder replies to the initiator with an interchange trailer segment, optionally preceded by a message. The following variations are possible:
For each message from the initiator to the responder there may be zero, one, or more than one message from the responder to the initiator, and vice versa.
UIR service segments may be interleaved with messages.
A dialogue can be prematurely terminated at any time by either party, by using a UIR service segment. A message or messages may be combined with:
the interchange header, or
— the interchange trailer, or
— both the interchange header and the interchange trailer (a complete dialogue).
Whilst exchange of data controlled by the initiator is a common mode of operation for interactive applications, the
1-EDI syntax does not exclude other modes of operation.
See annex A for examples.
Figure 3 shows a flow diagram of two interchanges which together form a dialogue.
C.1 Summary of 1-EDI
Interactive EDI is a series of exchanges of information between the applications of independent parties in order to accomplish a joint task, where subsequent exchanges may depend upon the results of previous exchanges. Strict timing constraints frequently apply. Applications which are inherently interactive include airline reservation systems; healthcare pharmacy, claims submission and eligibility verification; and remote automated teller machines for banks.
Initially, Interactive EDI is aimed at those applications where the initiating party, sends data to the responder, and the responder sends data back in reply. This alternate exchange of data controlled by the initiator is by far the most common way of working among existing interactive applications, but the 1-EDI syntax does not exclude other modes of working.
The definition of interactive EDI depends upon the definition of EDI in general. The approach taken towards EDI in this document has been based on the “Report on the Open-edi Conceptual Model” prepared by the EDI Special Working Group of ISO/IEC JTC 1. Characteristics of the “Open-edi Conceptual Model” include:
generalizing EDI beyond trade;
— defining EDI as “open” (available to all parties, according to standards and without requiring special bipartite agreements);
— co-ordinating EDI with other International Standards in communications, modelling and open environments.
Two major elements of the business context of EDI have made the development of interactive EDI necessary. The first is pressure from the market on many organizations (not just in the private sector) for more competitive, more responsive performance. Many fundamental processes must, in fact, be “remodelled” to respond to these pressures. The second element is the desire for standard solutions, in contrast to the current proprietary (and therefore “non-Open-edi”) situations.
The following guiding principles were adopted in defining 1-EDI requirements:
Ease of user implementation is paramount and standards should define their elements accordingly.
— Interactive EDI mechanisms should be fully compatible with and where possible identical to those for other forms of EDI.
The required functions should be available no matter what communications methods are used.
Wherever equivalent functions are available in the underlying communications protocols (e.g. X.25, OSI Transaction Processing) they may be used.
EDI standards should be fully harmonized with all other relevant International Standards.
The business and functional models, and the contents of the information required in interactive EDI service segments, have been described below, to present the characteristics and requirements of interactive EDI independently of an underlying architecture. It is recommended though, but not mandatory, that the relevant ISO protocols be used to carry 1-EDI data.