ANSI ISO IEC 10031-1-1991 Information technology - Text and office systems - Distributed-office-applications model - Part 1 General model Adopted by INCITS《信息技术.文本和办公系统.分布式办公应用摸式.第.pdf

1、INTERNATIONAL STANDARD ISOAEC 100314 First edition 1991-08-01 Information technology - Text and office systems - Distributed-office-applications model - Part I: General model Technologies de /information - Bureautique - Mode/e dapplication pour bureau distribue - Partie 1: Mode/e g b) their implemen

2、tation from the services of different vendors or service providers; cl their interworking; d) the optimization of development costs. In the interest of effective standardization, ISO/IEC 10031 is oriented towards well understood needs. It is capable of modular extensions to cover future developments

3、 in technology and needs. Although mainly intended for distributed-office-applications, the contents of ISO/IEC 10031 may be used in other information processing environments. iv Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or n

4、etworking permitted without license from IHS-,-,-INTERNATIONAL STANDARD IS0 / IEC 10031-l :1991(E) Information technology-Text and office systems - Distributed-office-applications model - Part 1: General model 1 Scope ISO/IEC 10031 provides a framework for the purpose of the development of protocol

5、standards for distributed-office-applications (DOAs). It applies to applications distributed over significant physical distances as well as “closely-coupled” office systems. ISO/IEC 10031 describes a model. Distributed-office-applications to be standardized shall use the principles specified in it.

6、ISO/IEC 10031 provides guidelines for the design of protocols which allow access to the various applications and ;,lberactions between applications. The protocols for distributed applications are within the OS1 Application Layer and conform to the Remote Operations defined in ISO/IEC 9072. ISO/IEC 1

7、0031 embraces the intent that elements of a system conforming to some parts of it can be implemented from devices supplied by different vendors and by different service providers. ISO/IEC 10031 does not define human-machine interfaces used with the distributed-applications. Also, it does not define

8、the interface between the software that interacts directly with the user and the software of specific applications. The content of ISO/IEC 10031 is comprised of two parts. This part of ISO/IEC 10031 describes the general model of distributed-office-applications and is divided into two sections: a) m

9、odel ; b) guidelines for the design of DOA protocols. ISO/IEC 10031-2 describes the Distinguished-object-reference and associated procedures that may be used by all DOAs. No requirement is made for conformance to this part of ISO/IEC 10031. Other parts of ISO/IEC 10031 may specify conformance for sy

10、stems implementing procedures of those other parts. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this part of ISO/IEC 10031. At the time of publication, the editions indicated were valid. All standards are subject t

11、o revision, and parties to agreements based on this part of ISO/IEC 10031 are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards, IS0 7498: 1984, Informa

12、tion processing systems - Open Systems Znterconnection - Basic Reference Model. 1 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/IEC10031-1:1991(E) IS0 7498-2: 1989, IS0 749

13、8-3: 1989, IS0 8649: 1988, IS0 8822:1988, ISO/IEC 8824: 1990, ISO/IEC 9066-l: 1989, ISO/IEC 9066-2: 1989, ISO/IEC 9072-l: 1989, ISO/IEC 9072-2: 1989, ISOAEC 9594-2: 1990, ISO/IEC 9594-3: 1990, IS0 9735: 1988, ISO/IEC 10021-2: 1990, ISO/IEC 10021-3: 1990, ISO/IEC 10021-5: 1990, 3 Definitions Znfornta

14、tion processing systems - Open Systems Znterconnection - Basic Reference Model - Part 2 : Security architecture. Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 3 : Naming and addressing. Znformation processing systems - Open Systems Interconnection - Ser

15、vice definition for Association Control Service Element. Znformation processing systems - Open Systems Znterconnection - Connection orientedpresentation service definition. Information processing systems - Open Systems Znterconnection - Specification ofAbstract Syntax Notation One (ASN.1). Informati

16、on processing systems - Text communication - Reliable Transfer - Part 1: Model and service definition. Information processing systems - Text communication - Reliable Transfer -Part 2: Protocol specification. Information processing systems - Text communication - Remote Operations - Part 1: Model, not

17、ation and service definition. Information processing systems - Text communication - Remote Operations - Part 2: Protocol specification. Information processing systems - Open Systems Interconnection - The Directory -Part 2: Models. Information processing systems - Open Systems Interconnection - The D

18、irectory -Part 3: Abstract service definition. Electronic data interchange for adminisiration, commerce and transport (EDZFACT) - Application level syntax rules. Information processing systems - Text communication - Message- Oriented Text Interchange Systems (MOTZS) - Part 2: Overall architecture. I

19、nformation processing systems - Text communication - Message- Oriented Text Interchange Systems (MOTZS) - Part 3: Abstract Service Definition conventions. Information processing systems - Text communication - Message- Oriented Text Interchange Systems (MOTZS) - Part 5: Message Store: Abstract servic

20、e definition. 3.1 OS1 basic reference model definitions This part of ISO/IEC 10031 makes use of the following terms defined in IS0 7498: a) Application Layer; b) application-entity; c) application-service-element; d) Presentation Layer; e) presentation-connection; f) protocol; 2 Copyright American N

21、ational Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-IS0 / IEC 10031-I :1991(E) g) service definition. 3.2 OS1 basic reference model Security part definitions This part of ISO/IEC 10031 makes use of the

22、following terms defined in IS0 7498-2: a) authentication; b) authorization; c) credentials; d) security policy. 3.3 Association control service element (ACSE) definitions This part of ISO/IEC 10031 makes use of the following terms defined in IS0 8649: a) application context; b) Association Control S

23、ervice Element. 3.4 Presentation service definition This part of ISO/IEC 10031 makes use of the following term defined in IS0 8822: a) abstract syntax. 3.5 Abstract syntax notation definitions This part of ISO/IEC 10031 makes use of the following terms defined in IS0 8824: a) ASN.l; b) external type

24、; c) Generalized Time; d) macro; e) object identifier; f) UTCTime. 3.6 Reliable transfer service element (RTSE) definition This part of ISO/IEC 10031 makes use of the following term defined in ISO/IEC 9066: a) Reliable Transfer Service Element. 3.7 Remote operations service element (ROSE) definition

25、s This part of ISO/IEC 10031 makes use of the following terms defined in ISO/IEC 9072: a) argument; b) bind-operation; c) invoke; d) operation; e) perform; fl Remote Operations; g) Remote Operations Service Element; h) result; i) unbind-operation. Copyright American National Standards Institute Prov

26、ided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/IEC10031-1:1991(E) 3.8 Directory definitions This part of ISO/IEC 10031 makes use of the following terms defined in ISO/IEC 9594: a) attribute; b) attribute macro; c) attribute t

27、ype; d) attribute value; e) filter. 3.9 EDIFACT definition This part of ISO/IEC 10031 makes use of the following term defined in IS0 9735: a) EDIFACT. 3.10 Message oriented text interchange systems (MOTIS) definitions This part of ISO/IEC 10031 makes use of the following terms defined in ISO/IEC 100

28、21-2: a) body part; b) IP-message; c) message. 3.11 Abstract service definition conventions definitions This part of ISO/IEC 10031 makes use of the following terms defined in ISO/IEC 10021-3: a) abstract model; b) abstract operations; cl abstract service; d) abstract service macro; e) asymmetric; D

29、port; g) refinement; h) symmetric. 3.12 Distributed-office-applications model (DOAM) definitions For the purposes of this part of ISO/IEC 1003 1, the following definitions apply: 3.12.1 accessee: An x-server which can assign distinguished-object-references (DORs) to objects which it manages upon req

30、uests from x-clients, and which can perform operations that designate objects by DORs which it assigned. 3.12.2 accessor: An x-server which can perform operations that designate objects by DORs, by accessing Accessees with the DORs. 3.12.3 control-attributes: Attributes, associated with a security-o

31、bject that, when matched against the privilege-attributes of a security-subject, are used to grant or deny access to the security-object. 3.12.4 control-attribute-package: A collection of control-attributes. 4 Copyright American National Standards Institute Provided by IHS under license with ANSINot

32、 for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/IEC10031-1:1991(E) 3.12.5 consume-operation: An operation invoked by an x-client to an Accessor that designates objects by DORs. 3.12.6 data-object: An object that represents data. 3.12.7 data-object-value: A value d

33、erived from a data object in accordance with a set of rules, or in the absence of such rules, the value of the entire object. 3.12.8 direct-value-access: Data-object access by value, instead of a reference. 3.12.9 direct-value-transfer: Direct transfer of data-object-value, instead of transfer of a

34、reference. 3.12.10 distinguished-object-reference: A unique reference to a real object in a DOA environment. 3.12.11 distributed-office-application: A set of information processing resources distributed over one or more open systems which provides a well defined set of functionality to (human) users

35、, to assist a given office task. 3.12.12 document: A structured amount of information intended for either direct or indirect human perception that can be interchanged, stored, retrieved and processed by means of office applications. 3.12.13 initiator: An x-client which invokes operations requesting

36、DORs instead of data object value to an Accessee, and which invokes operations that designate objects by DORs to an Accessor. 3.12.14 office-data-object: An object that represents office-information 3.12.15 office-information: Data used in the office environment. 3.12.16 privilege-attributes: Attrib

37、utes, associated with a security-subject that, when matched against control-attributes of a security-object, are used to grant or deny access to that security- object. 3.12.17 privilege-attribute-certificate: A certificate using privilege attributes. 3.12.18 produce-operation: A operation invoked by

38、 an x-client to an Accessee that requests an DOR instead of data object value. 3.12.19 qualified-attributes: Attributes that have qualification for their usage. 3.12.20 referenced-object-access: Access to objects by means of reference 3.12.21 ROA-operation: An operation invoked by an Accessor to an

39、Accessee. 3.12.22 security-attributes: A general term covering both privilege-attributes and control- attributes. The use of security-attributes is defined by a security policy. 3.12.23 security-object: An entity in a passive role to which access is granted or denied according to an authorization-po

40、licy. 3.12.24 security-subject: An entity in an active role that is granted or denied access to security- objects according to an authorization-policy. 3.12.25 user-application process: An application-process that contains an OA-user and one or more clients of distributedt-office)-applications (e.g.

41、 x-client, y-client, etc.). 3.12.26 x- : Generic placeholders for specific application names. 3.12.27 x-access: The definition of the functionality of an x-application, as visible between a x- client and a x-server. 3.12.28 x-access-abstract-service: The abstract service between an x-client and an x

42、-server. 5 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/IEC10031-1:1991(E) 3.12.29 x-access-protocol: The protocol used between an x-client and an x-server. 3.12.30 x-appl

43、ication: A distributedc-office b) messages; cl EDIFACT data; 4 attributes of documents; e) time; f) information relating to messages; d information to file documents; h) information to print documents (including fonts); i) management information for servers. This information is viewed as a collectio

44、n of office data objects, which can be accessed and manipulated individually or in groups. NOTE 2 - Exchange of information other than Office-information, is, and will be, delined by other International Standards. Copyright American National Standards Institute Provided by IHS under license with ANS

45、INot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/IEC10031-1:1991(E) 5.1.2 Abstract Model for Server-Systems The x-server-system in figure 1 may be refined to distribute the x-server-system by defining an abstract service between servers, as ISO/IEC 10021-3 sugg

46、ests. Figure 2 shows a refinement of an x-server-system. x-client a) x-access-abstract-service s) x-system-abstract-service Figure 2 - Refinement of x-server-system In figure 2, an x-client accesses an x-server-system via the x-access-abstract-service (a). In the x- server-system, an x-server respon

47、ds to the access. The x-server may interact with other x-servers via the x-system-abstract-service (5) to perform the service requested by the x-client. An x-server-system may comprise different types of x-servers. One or more ports may be defined between x-servers. Any type of port may be used. 9 C

48、opyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/IEC10031-1:1991(E) 5.2 Realization of DOA Abstract Model 5.2.1 Realization of Abstract Model for Access To realize the Abstract

49、 Model for access, ROSE defined by ISO/IEC 9072 and its OS1 mapping shall be used. The Layer Model is shown in figure 3. Further information about how x-clients and x-servers are identified, see 6.4.4. 5.2.2 Realization of Abstract Model for server-systems There is no restriction to realize the Abstract model for server-systems. Examples are shown in annex D. 5.3 Referenced-object-access 5.3.1 Classes of Data Access The acce