ONORM ENV 41220-1994 Information technology. Functional standard for profil A/MH 31. Message Handling Systems (1988 and later). Electronic data interchange messaging service (EDIMS). EDIM end system to EDIM end system (P EDI & P1)
1. Introduction
The purpose of a functional profile is to recommend how certain information technology standards should be used to satisfy one or more specific requirements. In particular, a functional profile should determine which options, available in the Base Specifications are necessary or desirable if the specific requirements are to be met.
This functional profile applies to Message Handling Systems within the general context of the OSI Reference Model.
The scope of this functional profile is the following:
Specification of the conformance rules for the EDI-Uas.
Specification of the conformance rules for interchange of the message content type and the associated procedures as defined in [X.435 I ISO/EC 10021-9] and [F.435 I ISO/EC 10021-8]. This is known as Pedi and abbreviated as such in this functional standard.
2 General
This functional profile describes the rules for the behaviour of the EDI-UA required for conformance to this profile.
The precise interface between the EDI Messaging User (EDEMG user as defined in [Recommendation X.435 I ISO/IEC 10021-9] and [Recommendation F.435]) and the EDI Messaging System (EDIMS as defined in [Recommendation X.435 I ISO/IEC 10021-9] and [Recommendation F.435]) will require the definition of an Application Programming Interface (API). This interface is outside the scope of this profile.
Elements of Service, abstract services and abstract information objects are classified in a modular way by using the concept of Functional Groups. Optional functional groups may be required by procurement specifications in order to meet particular requirements.
Local MTS-user functions are not covered by this profile. In particular, mechanisms for the origination and rendition of graphic characters are outside the scope of this profile.
NOTE: It is recommended, in order to obtain the full functionality implied by this profile that EDI-UA's require the services of an MTS which as a minimum are classified as mandatory Elements of Service in this profile.
3 Position within the Taxonomy
This profile is developed in the following context.
Common Facilities
A/MH11 MTAandMTS A/MH12 UAtoMS(P7) A/MH13 MTS-user to MTA (P3)
IPMS
A/MH21 BPM end system to IPM end system (P2 over P1)
A/MH22 EPM UA to IPM MS (P2 over P7)
A/MH23 IPM UA or IPM MS to MTA (P2 over P3)
EDIMS
A/MH31 EDI-UA to EDI-UA (Pedi over PI)
A/MH32 EDI-UA to EDI-MS (Pedi over P7)
A/MH33 EDI-UA or EDI-MS to MTA (Pedi over P3)
The scenario is described in Figure 1.
Maintenance
The user is invited to check with the EWOS secretariat if any defect reports or corrigenda to this profile are available and may be obtained from:
European Workshop for Open Systems Attn: Mr Luc Van Den Berghe Rue de Stassart, 36 B- 1050 Brussels BELGIUM
Such documents may be subject to conformance.
6 Base Specifications
The Base Specifications comprise the CCITT X.400 series of Recommendations, Recommendation F.435 and the ISO/IEC 10021 Standards as modified by the MHS Implementor's Guide and the published ISO/EC Technical Corrigenda.
7 Normative Relationships With Other Functional Standards
This profile classifies and specifies the use of Elements of Service for an EDIMS. The MT Element of Service classification is based upon Annex B of ENV 41219.
ONORM ENV 41220-1994 history
1994ONORM ENV 41220-1994 Information technology. Functional standard for profil A/MH 31. Message Handling Systems (1988 and later). Electronic data interchange messaging service (EDIMS). EDIM end system to EDIM end system (P EDI & P1)