ANSI INCITS ISO IEC 14363-1996 Information technology - Test methods for measuring conformance to MHS-based electronic messaging - Application Program Interface (API) [Language ind.pdf

《ANSI INCITS ISO IEC 14363-1996 Information technology - Test methods for measuring conformance to MHS-based electronic messaging - Application Program Interface (API) [Language ind.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 14363-1996 Information technology - Test methods for measuring conformance to MHS-based electronic messaging - Application Program Interface (API) [Language ind.pdf（592页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL STANDARD ISO/IEC 14363 First edition 1996-06-01 Information technology-Test methods for measuring conformance to MHS-based electronic messaging - Application Program Interface (API) Language independent Technologies de /information - MBthodes dessai pour mesurer la conform Telephone: +

2、1202 371-0101; FAX: +1202 728-9614. . . . Vlll Introduction INTERNATIONAL STANDARD OISO/IEC ISO/IEC 14363:1996(E) 1 Information technology-Test methods for 2 measuring conformance to MHS-based 3 electronic messaging-Application Program 4 Interface (API) Language independent 5 6 7 This International

3、Standard defines requirements for test methods for measuring 8 conformance to ISO/IEC 14361 (31. 9 ISO/IEC 14361 (3) is stated in terms that are independent of any particular pro- 10 gramming language, but each implementation that conforms to it implements a 11 particular programming language bindin

4、g, and conforms to its programming 12 language binding specification. Each set of test methods for measuring confor- 13 mance to ISO/IEC 14361 (31 assumes a particular programming language binding 14 specification. Each programming language binding specification may impose 15 further programming lan

5、guage specific requirements on the test methods which, in 16 conjunction with the requirements imposed by this International Standard, consti- 17 tute the requirements that shall be satisfied by test methods used for measuring 18 conformance to that programming language binding specification. This I

6、nterna- 19 tional Standard applies to all sets of test methods for measuring conformance to 20 any programming language binding specification for ISO/IEC 14361 (31. 21 1.2 Normative References 22 The following standards contain provisions which, through reference in this text, 23 constitute provisio

7、ns of this International Standard. At the time of publication, 24 the editions indicated were valid. All standards are subject to revision, and parties 25 to agreements based on this International Standard are encouraged to investigate 26 the possibility of applying the most recent editions of the s

8、tandards indicated Section 1: General 1.1 Scope 1.2 Normative References 1 27 ISO/IEC 14363:1996(E) OISO/IEC below. Members of IEC and IS0 maintain registers of currently valid Interna- tional Standards. 28 IS0 3166: 1993,l Codes for the Representation of Names of Countries. 29 30 31 (11 ca ISO/IEC

9、14360: 1996, I f n ormation technology-Open Systems Interconnec- tion (OSI) abstract data manipulation-Application Program Interface (API) Language independent. 32 33 34 35 36 37 38 39 40 41 13) ISO/IEC 14361: 1996, I f n ormation technology-MHS-based electronic messaging-Application Program Interfa

10、ce (API) Language independent. 4) ISO/IEC 14362: 1996, I n ormation technology-Test methods for measuring f conformance to Open Systems Interconnection (OSI) abstract data manipulation-Application Program Interface (API) Language indepen- dent. I5) 161 IEEE Std 1003.3-1991,2 IEEE Standard for Inform

11、ation Technology-Test Methods for Measuring Conformance to POSIX. CCITT Recommendation X.121: 1984,3 International Numbering Plan for Public Data Networks. CCITT Red Book, Fascicle VIII.4. 42 1.3 Conformance 43 A set of test methods that conforms to this International Standard shall conform to 44 IE

12、EE Std 1003.3-1991 5), with references to the “P0SIX.n test method 45 specification” being interpreted as references to this International Standard, and 46 references to “the POSIX standard for which conformance is being measured” being 47 interpreted as references to ISO/IEC 14361 (3). 48 49 50 51

13、52 In addition to meeting the conformance criteria defined in IEEE Std 1003.3-1991 (5), a set of test methods that conforms to this International Standard shall test all documentation assertions defined in this International Standard. NOTE: Conformance to IEEE Std 1003.3 (5) implies that the test me

14、thods will test all other asser- tions defined in this International Standard. 53 1) ISO/IEC documents can be obtained from the IS0 Central Secretariat, 1 Rue de Varembe, Case 54 Postale 56, CH-1211, Geneve 20, Switzerland/Suisse. 55 2) IEEE documents can be obtained from the IEEE Service Center, 44

15、5 Hoes Lane, P.O. Box 1331, 56 Piscataway, NJ, 08855-1331, USA. Telephone: 1(800)678-IEEE or +l (908) 981-1393 (outside 57 US). 58 3) CCITT documents can be obtained from the Telecommunication Standardization Bureau of the 59 International Telecommunication Union, Sales Section, Place des Nations, C

16、H-1211, Geneve 20, 60 SwitzerlandfSuisse. 2 1 General 0 ISO/IEC Iso/IEC 14363:1996(E) 1 Section 2: Terminology and General Requirements 2 3 2.1.1 General and Typographical Conventions 10 11 12 13 14 15 16 17 18 19 - The bold font is used for: 20 - Language-independent concrete OM class names, such a

17、s Delivered- 21 Report 22 23 24 25 26 27 2.1 Conventions Language-independent concrete OM class names, OM attribute names, and OM- attribute value names are spelled with hyphens between words (e.g., conversion-loss-prohibited). The first letters of language-independent OM class and OM attribute name

18、s are capitalized (e.g., Redirection-Record). Language-independent datatype, operation, argument and error names are lowercase and are spelled with underscores between words (e.g., ma-start-delivery ). The use of fonts in this International Standard is as follows: - The Helvetica font is used for: -

19、 Language-independent operation names, such as ma-start-delivery - Language-independent datatype names, such as mh-interval-type - Language-independent error names, such as feature-unavailable - The it&c font is used for: - Language-independent operation arguments, such as user-czddress - The introd

20、uction of important terms - Cross-references in 2.2 - Language-independent OM attribute names, such as Algorithm-Datum - Language-independent OM attribute values, such as conversion-loss- prohibited - The bold italic font is used for: - Language-independent abstract OM class names, such as Delivery-

21、 Report 2.1 Conventions 3 ISOLIEC 14363:1996(E) OISO/IEC 28 29 - The constant width (Courier) font is used for: - References to terms defined in international standards upon which this International Standard is based. 30 2.2 Definitions 31 2.2.1 Terminology 32 For the purposes of this International

22、Standard, the following definitions apply: 33 2.2.1.1 conformance document: A document provided by an implementor that 34 contains implementation details. ISOLIEC 9945-l (Bill 35 2.2.1.2 may: An indication of an optional feature. ISO/IEC 9945-l Bl 36 With respect to implementations, the word may is

23、to be interpreted as an optional 37 feature that is not required in this International Standard, but that can be pro- 38 vided. With respect to Strictly Conforming Applications, the word may means that 39 the optional feature shall not be used. 40 2.2.1.3 shall: An indication of a requirement on the

24、 implementation or on Strictly 41 Conforming Applications, where appropriate. ISO/IEC 9945-l Bl) 42 2.2.1.4 should: 43 44 45 (2) With respect to applications, an indication of a recommended program- 46 ming practice for applications and a requirement for Strictly Conforming 47 Applications. ISO/IEC

25、9945-l Bl) 48 2.2.1.5 supported: A condition regarding optional functionality. 49 Certain functionality in this International Standard is optional, but the interfaces 50 to that functionality are always required. If the functionality is supported, the 51 interfaces work as specified by this Internat

26、ional Standard (except that they do not 52 return the error condition indicated for the unsupported case). If the functionality 53 is not supported, the interface shall always return the indication specified for this 54 situation. ISO/IEC 9945-l Bl) 55 2.2.1.6 system documentation: All documentation

27、 provided with an implemen- 56 tation, except the conformance document. 57 Electronically distributed documents for an implementation are considered part of 58 the system documentation. ISO/IEC 9945-l Bl (1) With respect to implementations, an indication of an implementation recommendation, but not

28、a requirement. 4 2 Terminology and General Requirements 59 For the purposes of this International Standard, the following definitions apply: 60 2.2.2.1 assertion: A statement that is derived from the standard to which confor- 61 mance is being measured, that is true for a conforming implementation,

29、and that 62 pertains either to functionality or behavior of a functional interface or namespace 63 allocation or to the documentation associated with the implementation being tested 64 ISO/IEC 14360 1211. 65 2.2.2.2 generic interface: A version of an interface that is independent of any 66 particula

30、r programming language. 67 2.2.2.3 programming language binding specification: For a language- 68 independent specification, a document that specifies, in terms of a particular pro- 69 gramming language, the behavior that the language-independent specification 70 specifies in language-independent te

31、rms. 71 It may also specify additional behavior that is relevant to the usage of the particu- 72 lar programming language ISOAEC 14360 1211. 73 2.2.2.4 test methods: The software, procedures, or other means specified to 74 measure conformance to a specification ISOLIEC 14360 (211. 75 76 77 OISO/IEC

32、ISO/IEC 14363:1996(E) 2.2.2 General Terms 2.2.3 Abbreviations For the purposes of this International Standard, the following abbreviations apply: 2.2.3.1 OM: Object Management. 2.2 Definitions 5 0 ISO/IEC ISO/IEC 14363:1996(E) 1 Section 3: Test Assertions for Section General 2 3.1 Scope 3 There are

33、no test assertions for this clause. 4 5 3.2 Normative References There are no test assertions for this clause. 6 3.3 Conformance 7 3.3.1 Implementation Conformance 8 3.3.1.1 Conformance Requirements 9 10 11 DO1 The manufacturer shall identify the interface (MA, MT, or both) that the product implemen

34、ts, and state what roles (client, service, or both) it plays for each. 12 13 14 001(A) The product shall implement the OM interface as defined in ISO/IEC 14360 (2, satisfying its conformance requirements, and play the same roles for that interface as it plays for the MA and MT interfaces. 15 16 17 D

35、O2 If the product plays the role of service for the MA or MT interface: The manufacturer shall state which features the product imple- ments. 18 19 002(C) 003(C) 004(C) If the product plays the role of service for the MA interface: The product shall implement the Basic Access FU. 20 21 22 If the pro

36、duct plays the role of service for the MA interface: The product shall implement the Submission FU, the Delivery FU, the Retrieval FU, or any combination of the three. 23 24 If the product plays the role of service for the MT interface: The product shall implement the Basic Transfer FU. 3.3 Conforma

37、nce 7 ISO/JEC 14363:1996(E) OISO/IEC 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 005(C) If the product plays the role of service for the MT interface: The product shall implement the Transfer In FU, the Transfer Out

38、 FU, or both. 006(C) If the product plays the role of service for the MA or MT interface: The product shall implement the MH 88 Package, the MH 84 Package, or both. GAO1 For FU of Basic Access FU, Submission FU, Delivery FU, Retrieval FU, Basic Transfer FU, Transfer In FU, Transfer Out FU: If the pr

39、oduct plays the role of service for FU: The product shall implement every aspect of every func- tion in FU. DO3 DO4 Forpuckuge of IM 88 Package, MH 88 Package: If the product implements package: The product documentation shall state which (if any) of the 1988 classes ofpuckuge the product implements

40、. For package of IM 88 Package, IM 84 Package: If the product implements package: The product documentation shall state which (if any) immediate subclasses of the Body-Part class the pro- duct implements. GAO2 For package of IM 84 Package, SM 88 Package: If the product implements package: The produc

41、t shall implement every class the package contains. 007(C) If the product implements the MH 84 package: The product shall implement all of those classes that are used by the functional units that it supports. 008(A) DO5 The product shall implement the closures of all classes it implements. The produ

42、ct documentation shall state what classes it provides the om-encode function for. DO6 DO7 If the product plays the role of service for the MA interface: The manufacturer shall state whether or not the product real- izes the interface by means of X.400s Message Submission and Delivery Protocol (P3) o

43、r Message Retrieval Protocol (P7). If the product plays the role of service for the MT interface: The manufacturer shall state whether or not it realizes the interface by means of X.400s Message Transfer ProtocoZ (PI). DO8 If the product plays the role of service for the MA interface or the MT inter

44、face and implements the IM 88 Package or the IM 84 Package: The manufacturer shall state whether or not the product real- izes the interface by means of X.400s Interpersonal Messaging Protocol (PZ) . GAO3 Forprotocol of P1(1988), P3 (1988), P7 (1988): If the product implements protocol: The manufact

45、urer and product shall satisfy the 8 3 Test. Assertions for Section General 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 OISO/IEC ISOKEC 14363:1996(E) 009(D) 010(D) 011(D) DO9 conformance requirements of X.400 (1988) with respect to

46、protocol. If the product implements Pl(1988): The manufacturer and product shall satisfy the conformance requirements of X.400 (1988) with respect to Pl (1988). (See GAO3 in 3.3.1.1.) If the product implements P3 (1988): The manufacturer and product shall satisfy the conformance requirements of X.40

47、0 (1988) with respect to P3 (1988). (See GAO3 in 3.3.1.1.) If the product implements P7 (1988): The manufacturer and product shall satisfy the conformance requirements of X.400 (1988) with respect to P7 (1988). (See GAO3 in 3.3.1.1.) If the product plays the role of service for the MA or MT interfac

48、e: The manufacturer shall state the behavior of implementation- defined options. 3.3.1.2 Conformance Documentation There are no test assertions for this subclause. 3.3.1.3 Conforming Implementation Options DlO The circumstances that define abnormal termination of a session shall be documented. Dll F

49、or fund of ma-open, mt-open : The features of a session that funct supplies as defaults shall be documented. D12 Documentation shall state whether the service shall accept any cir- cumstances as causes of temporary delivery failure. D13 The maximum number of users that may be assigned to a single delivery queue shall be documented. D14 The maximum number of sessions that may exist simultaneously shall be documented. D15 The documentation shall state which qualifying object in the delivery queue (if there are several such objects) ma-start-delivery sele