1、CCITT FASCICLE VII.7 * 48b2593 0532405 3 B.4.2 Checkpoint-con firmed This Boolean variable is TRUE, if at least one checkpoint was confirmed during the transfer procedure. It is set FALSE at the beginning of the transfer procedure (specific action a30). It is set TRUE, if an S-MINOR-SYNCHRONIZE conf
2、irm primitive is issued to the sending DTAM-PM (specific action a32). B.4.3 Transfer-completed This Boolean variable is TRUE, if the receiving DTAM-PM aborted the association because it could not discard an already completed transfer. It is set by the specific actions a931 and a94. This Boolean vari
3、able is tested in the predicate p37. B .4.4 Outstanding-minor-syncs This integer variable indicates the number of outstanding checkpoint confirmations during the transfer procedure. It is set to zero at the beginning of the transfer procedure (specific action a30). It is incremented by one, if a S-M
4、INOR-SYNCHRONIZE request primitive is issued by the sending user to the sending DTAM-PM (specific action a3 i). The value of this variable is compared with the value of the window-size field of the S-CONcnf in the predicate p32. The value of this variable is compared with the value zero in the predi
5、cate p33. Recommendation T.441 DOCUMENT TRANSFER AND MANIPULATION (DTAM) - OPERATIONAL STRUCTURE CONTENTS Scope 1 Overview of operational concept 2 3 Operational structures 4 Operational re ference model 5 6 Operaiional dala formats Operational application pro file rules Operational pro file in form
6、ation Scope This Recommendation has been established to cover the needs of videotex interworking. It will The operational structure should be developed as a set of rules for an interface between be further developed to cover the needs of other telematic services. telematic applications based on T.40
7、0 Series of Recommendations and an ODA-document. Fascicle W.7 - Rec. T.441 131 _ CCITT FASCICLE VII.7 * 486257L 0532406 5 1 Overview of operational concept A document is defined in terms of logical and/or layout structure according to the specifica- tions of the T.410 Series of Recommendations. The
8、basic principle of the operational concept is to provide the means for the integration of telematic services requirements, not covered by the T.410 Series of Recommendations within the applications on the top of DTAM (see Figure 1/T.441). DTAM user I I I I l l l I I I I I I L_ Communication function
9、s Association use control Capability Document bulk transfer Document manipulation Typed data transfer Session management I I i DTAM I protocol t- I I I I I I I I FIGURE 1/T.441 Overview of DTAM (including operational structure) Document handling, e.g. access to parts of a document and manipulation o
10、f a document requires detailed considerations; two aspects of document handling shall be distinguished: a) In addition to the document, structural concepts need to be defined in T.400 Series of Recommendations; these concepts shall define the structural aspect of the document handling (as for exampl
11、e “forms for data entry“). Nole - The definition of structural concepts is not in the scope of this Recommenda- tion. Specifications concerning such concepts require further detailed study. b) In addition to the document, applications may require operational features which provide information for th
12、e interface between the document and the application. Interfaces are for example necessary for “Data Entry“, “Spread Sheet“, “Remote Editing“, etc. As an application on top of DTAM shall solely use DTAM service and protocol, this Recommendation provides the operational concept which allows to integr
13、ate operationai features within the concept of DTAM. The operational structure is introduced as a set of rules to structure the interface between a document and the application (see Figure 2/T.441). By defining a mapping onto the operational structure, the application integrates its operational feat
14、ures within DTAM. The mapping has to be specified within the appropriate Recommendation for the relevant appIication. The semantic of the interface is generally determined by the relevant application. 132 Fascicle VI1.7 - Rec. T.441 - L- - CCITT FASCICLE VII.7 * 4862571 0512Y07 7 = T. 410 Seriez of
15、Recommendations provide the document structure The application handles the document in a,specific way: (For example data entry programs) using the structured interface This Recornmendation provides operational structures 4 TOdOlO1O-d9 Additional features such as forms for data entry, for further stu
16、dy FIGURE 2/T.44 1 Operational structures provide the information for a structured interface between the document and the application 2 Operational application profile rules 2.1 General principles This section specifies how operational application profiles can be implemented by using this Recommenda
17、tion. Application defined usage of T.400 Series of Recommendations is specified in terms of application profiles. An application profile consists of a combination of: - - - operational structure application profiles according to the rules which will be defined document application profiles according
18、 to the rules defined in T.411; communication application profiles according to the rules defined in T.431; in this Recommendation. 3 Operational structures This section describes the operational concept which is the basis for remote operation on a document. It facilitates access and manipulation to
19、 parts of a document through operations defined in T.430 Series of Recommendations. The concept can be used to associate application defined attributes and content with constituents of documents. For example, it may be used to specify fields for data entry and actions on the content of these fields.
20、 In this example, the semantics for data entry and actions may be expressed by the application. The operational structure follows in general the structuring principles typical of the The constituents of the operational structure reference the document constituents they are Multiple operational struc
21、tures may be defined referring to a single document class. document architecture as described in T.412. operating on. KJ33-7 Fascicle W.7 - Rec. T.441 4 Operational reference model This section describes the common understanding of operations on: - - parts of document. This section provides a narrat
22、ive description of these operations. At present two types of operations will be defined: the document as a whole; - partial document transfer; - remote document update. Any complete set of operations on a document using the operational structure should result in a document conforming to the rules of
23、 the T.410 Series of Recommendations. 5 Operational profile information An operational structure profile includes information concerning: - - application dependent references; - operational structure levei; the reference to a document or a document class; - the type of the content. 6 Operational dat
24、a formats This section describes the format of the datastream used to interchange operational structures. The operational structure can be interchanged as a whole or in parts. The datastream is described in terms of a set of operational interchange data units which represent the constituents (e.g. operational profile, object class descriptors, object descriptors, and content) of an operational structure. The formats of the interchanged data units are defined using the abstract syntax notation one (ASN. 1 ). 134 Fascicle m.7 - Rec. T.441
