home *** CD-ROM | disk | FTP | other *** search
-
- Recommendation T.541
-
-
-
-
- OPERATIONAL APPLICATION PROFILE FOR VIDEOTEX INTERWORKING
-
-
- CONTENTS
-
-
-
-
- 1 Scope
- 2 Field of application
- 3 References
- 4 Definitions
- 5 Characteristics supported by this operational application profile
- 5.1 Overview
- 5.2 Range of operational structures
- 5.3 Generic characteristics
- 5.4 Specific characteristics
- 6 Definition of the operational application profile
- 6.1 Complexity level of operational structures
- 6.2 Operational profile level
- 6.3 Specification of operational structures
- 6.4 Specification of attributes
- 6.5 Attribute values for constituents of the operational structure
- 6.6 Default values for application defined attributes
- 6.7 Implicitly created constituents
- Annex A - Operational structure
- Annex B
- Annex C - Summary of ASN.1 object identifiers
-
-
-
- 1 Scope
-
-
- This Recommendation defines an operational application profile which conforms to T.400 Series of
- Recommendations.
-
- Its purpose is to specify an operational structure class suitable for videotex interworking as defined in configuration
- 1 of CCITT Recommendation F.300 and in Recommendation T.564.
-
-
-
- 2 Field of application
-
-
-
- This Recommendation defines an operational application profile, that is in conformance with DTAM (T.400 Series of
- Recommendations) and that allows operational structures to be interchanged for the purpose of an international videotex
- interworking.
-
- This operational application profile defines the features of the operational structure that can be interchanged. These
- features are depending on the document structures as specified in the document application profile (see Recommendation
- T.504).
-
-
-
- 1 Fascicle VII.7 - Rec. T.541
-
-
-
-
- 3 References
-
-
- - Rec. F.300: Videotex service
-
- - Rec. X.200: Reference model of open systems interconnection for CCITT applications
-
- - Rec. X.213: Network service definition for open systems interconnection for CCITT applications
-
- - Rec. X.214: Transport service definition for open systems interconnection for CCITT applications
- - Rec. X.224: Transport protocol specification for open systems interconnection for CCITT applications
- - Rec. X.215: Session service definition for open systems interconnection for CCITT applications
- - Rec. X.225: Session protocol specification for open systems interconnection for CCITT applications
- - Rec. X.216: Presentation service definition for open systems interconnection for CCITT applications
- - Rec. X.226: Presentation protocol specification for open systems interconnection for CCITT applications
- - Rec. X.217: Association control service definition for open systems interconnection for CCITT applications
- - Rec. X.227: Association control protocol specification for open systems interconnection for CCITT
- applications
- - Rec. T.101: International interworking for videotex services
- - Rec. T.400: Introduction to document architecture, transfer and manipulation
- - Rec. T.411: Open document architecture (ODA) and interchange format - Introduction and general principles
- - Rec. T.412: Open document architecture (ODA) and interchange format - Document structures -Rec. T.414:
- Open document architecture (ODA) and interchange format - Document profile
- - Rec. T.415: Open document architecture (ODA) and interchange format - Open document interchange
- format (ODIF)
- - Rec. T.431: Document transfer and manipulation (DTAM) - Services and protocols - Introduction and
- general principles
- - Rec. T.432: Document transfer and manipulation (DTAM) - Services and protocols - Service definition
- - Rec. T.433: Document transfer and manipulation (DTAM) - Services and protocols - Protocol specification
- - Rec. T.441: Document transfer and manipulation (DTAM) - Services and protocols - Operational structure
- - Rec. T.504: Document application profile for videotex interworking
- - Rec. T.523: Communication application profile DM-1 for videotex interworking
- - Rec. T.564: Gateway characteristics for videotex interworking
-
-
- 4 Definitions
-
-
- The definitions of T.400 Series of Recommendations apply also to this Recommendation.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.7 - Rec. T.541 2
-
-
- 5 Characteristics supported by this operational application profile
-
-
- 5.1 Overview
-
- For the purpose of videotex interworking operational structures are associated with a videotex document to provide
- an environment for interactive communication, necessary for a recipient to handle the userw's input data as intended by the
- originator.
- Therefore the purpose of this section is to specify the functional description of the features supported by this
- operational application profile.
- 5.2 Range of operational structures
- For the purpose of an international videotex interworking four operational structures are specified, one of each
- representing the "data entry structure", the "application control memory", the "administrative structure" and the "special
- terminal facilities structure" as defined in Recommenda- tion T.564.
- 5.3 Generic characteristics
- Not used.
- 5.4 Specific characteristics
- Each of the operational structures specified in this operational application profile only supports specific features of
- operational structures.
-
-
- 6 Definition of the operational application profile
-
-
- 6.1 Complexity level of operational structures
- For further study.
- 6.2 Operational profile level
- One operational profile has to be defined for every application using operational structures.
- This operational profile specifies:
- - Four operational structures are used;
- - Each of the operational structures only contains specific features.
- Details are for further study.
- 6.3 Specification of operational structures
- Four operational structures are specified by this operational application profile.
- 6.3.1 Data entry structure
- The data entry structure as defined in draft Recommendation T.564 is mapped onto one specific operational
- structure. No generic operational structure is present.
- The Data-Entry-SE is mapped to the specific operational root. The object identifier of the root of this operational
- structure has an assigned value of 11.
- The subordinates of Data-Entry-SE are: Data-Entry-Program-SE, Field-SE, Rules-SE, Prompt-SE, and Result-SE.
- Data-Entry-Program-SE is mapped to composite operational object. Field-SE, Rules-SE, Prompt-SE and Result-SE
- are mapped to basic operational objects.
- Field-SE, Prompt-SE and Result-SE may have associated operational elements.
- Subordinate to Data-Entry-Program-SE is Data-Entry-Subprogram-SE. Data-Entry-Subprogram-SE is mapped to
- basic operational object.
- For each of the SEs specified above, constraints are defined on the number of SEs which may exist at one time.
- These constraints are defined in Recommendation T.564.
-
-
-
-
-
- 3 Fascicle VII.7 - Rec. T.541
-
-
-
-
- 6.3.2 Application control memory structure
-
- The application control memory structure as defined in Recommendation T.564 is mapped onto one specific
- operational structure. No generic operational structure is present.
-
- The Application-Control-Memory-SE is mapped to the specific operational root. The object identifier of the root of
- this operational structure has an assigned value of 12.
-
- Subordinate to the Application-Control-Memory-SE is the Record-SE. The Record-SE is mapped to basic
- operational object.
-
- For each of the SEs specified above, constraints are defined on the number of SEs which may exist at one time.
- These constraints are defined in Recommendation T.564.
-
- 6.3.3 The administrative structure
-
- The administrative structure as defined in Recommendation T.564 is mapped onto one specific operational
- structure. No generic operational structure is present.
-
- The Administrative-Information-SE is mapped to the specific operational root. The object identifier of the root of this
- operational structure has an assigned value of 13.
-
- 6.3.4 Special terminal facilities structure
-
- The special terminal facilities structure as defined in Recommendation T.564 is mapped onto one specific
- operational structure. No generic operational structure is present.
-
- The Specific-Terminal-Facilities-SE is mapped to the specific operational root. The object identifier of the root of
- this operational structure has an assigned value of 14.
-
- Subordinate to the Special-Terminal-Facilities-SE is the Redefinition-Entity-SE. Redefinition- Entity-SE is mapped to
- basic operational object.
-
- For each of the SEs specified above, constraints are defined on the number of SEs which may exist at one time.
- These constraints are defined in Recommendation T.564.
-
- 6.4 Specification of attributes
-
- The attributes applicable to constituents of the operational structure are defined in the following tables, using the
- following notation:
-
- -- attribute not applicable
- m attribute is mandatory
- nm attribute is non-mandatory
- d attribute is defaultable
-
- From the attributes specified for operational structures in Annex A to this Recommendation, videotex interworking
- will not use the attributes operational object class and subordinates.
- The use of the attribute document fragment is for further study.
-
- 6.4.1 Attributes of the data entry structure
-
-
-
-
- Fascicle VII.7 - Rec. T.541 4
-
-
- Table 1/T.541 shows the use of attributes defined for objects of operational structures.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 5 Fascicle VII.7 - Rec. T.541
-
-
-
-
- TABLE 1/T.541
-
- w
- ┌─────────────────────────┬────────────────────────────────────────────────┐
- │ Attributes │ Data-Entry-SE │
- │ │ ┌──────────────────────────────────────────┤
- │ │ │ Data-Entry-Program-SE │
- │ │ │ ┌────────────────────────────────────┤
- │ │ │ │ Data-Entry-Subprogram-SE │
- │ │ │ │ ┌──────────────────────────────┤
- │ │ │ │ │ Field-SE │
- │ │ │ │ │ ┌────────────────────────┤
- │ │ │ │ │ │ Rules-SE │
- │ │ │ │ │ │ ┌──────────────────┤
- │ │ │ │ │ │ │ Prompt-SE │
- │ │ │ │ │ │ │ ┌────────────┤
- │ │ │ │ │ │ │ │ Result-SE │
- ├─────────────────────────┼─────┼─────┼─────┼─────┼─────┼─────┼────────────┤
- │ │ │ │ │ │ │ │ │
- │ Object type │ m │ m │ m │ m │ m │ m │ m │
- │ │ │ │ │ │ │ │ │
- │ Object identifier │ m │ m │ m │ m │ m │ m │ m │
- │ (Note) │ │ │ │ │ │ │ │
- │ │ │ │ │ │ │ │ │
- │ Reference attribute │ -- │ d │ d │ -- │ -- │ -- │ nm │
- │ │ │ │ │ │ │ │ │
- │ Application defined │ │ │ │ │ │ │ │
- │ attribute lists │ d │ d │ d │ d │ d │ d │ d │
- │ │ │ │ │ │ │ │ │
- │ Default value lists │ nm │ -- │ -- │ -- │ -- │ -- │ -- │
- │ │ │ │ │ │ │ │ │
- └─────────────────────────┴─────┴─────┴─────┴─────┴─────┴─────┴────────────┘
-
- Note - This attribute may be omitted when the value can be unambiguously derived
- from the transmission sequence of the relevant objects.
-
- Values for the attribute object-type
-
- Data-Entry-SE: 0
-
- Data-Entry-Program-SE: 1
-
- Data-Entry-Subprogram-SE: 2
-
- Field-SE: 3
-
- Rules-SE: 4
-
- Prompt-SE: 5
-
- Result-SE: 6
-
- Table 2/T.541 shows the use of attributes defined for operational elements.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.7 - Rec. T.541 6
-
-
- TABLE 2/T.541
-
- w
- ┌───────────────────────────────────┬───────────────────────────────────────┐
- │ │ Field-content portion
- │
- │ │ ┌───────────────────────────────┤
- │ │ │ Prompt-content portion
- │
- │ │ │ ┌───────────────────────┤
- │ │ │ │ Result-content portion│
- ├───────────────────────────────────┼───────┼───────┼───────────────────────┤
- │ Operational element │ │ │ │
- │ identifier (Note) │ m │ m │ m │
- │ │ │ │ │
- │ Operational element content type │ d │ d │ d │
- │ │ │ │ │
- │ Operational element content │ d │ d │ d │
- └───────────────────────────────────┴───────┴───────┴───────────────────────┘
-
-
- Note - This attribute may be omitted when the value can be unambiguously derived
- from the transmission sequence of the relevant elements.
-
- 6.4.1.1 Data-Entry-SE
-
- 6.4.1.2 Data-Entry-Program-SE
-
- The attribute first-subprogram, defined in Recommendation T.564, is mapped to the
- reference attribute, defined in Recommendation T.441 (or currently in Annex A of this
- Recommendation).
-
- This application profile specifies the use of this attribute as defaultable.
- Currently no default value is defined within this standard.
-
- The application defined attribute list for the Data-Entry-Program-SE contains the
- following attributes:
-
- w
- ┌──────────────────────────────────────────────────────┐
- │ Data-Entry-Type d │
- │ │
- │ Allowed-characters-for-keyword-access nm │
- │ │
- │ Character-list-for-keyword-access nm │
- │ │
- │ Max-length-keyword-access d │
- │ │
- │ Allowed-characters-for-a-direct-access-command nm │
- │ │
- │ Max-length-direct-access d │
- └──────────────────────────────────────────────────────┘
-
- 6.4.1.3 Result-SE
-
- The attribute Last-sub-program defined in Recommendation T.564 is mapped to the
- reference attribute defined in Recommendation T.441 (or currently in Annex A of this
- Recommendation). The application defined attribute-list for the Result-SE contains the
- following attribute:
-
- w
- ┌───────────────────────────────────────────────────┐
- │ Termination reason d │
-
-
-
- 7 Fascicle VII.7 - Rec. T.541
-
-
-
-
- └───────────────────────────────────────────────────┘
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.7 - Rec. T.541 8
-
-
- 6.4.1.4 Field-SE
-
- The application defined attribute list for the field-SE contains the following
- attributes:
- w
- ┌───────────────────────────────────────────────────┐
- │ Field-layout d │
- │ │
- │ Field-type nm │
- │ │
- │ Protected nm │
- │ │
- │ Data-source nm │
- │ │
- │ Field-text-marking nm │
- └───────────────────────────────────────────────────┘
-
- 6.4.1.5 Data-Entry-Subprogram-SE
-
- The attributes:
-
- reference-to-rules-SE
- reference-to-field-SE
- reference-to-prompt-in-SE, and reference-to-a-prompt-out-SE
-
- defined in Recommendation T.564, are mapped to the reference attribute defined in
- Recommenda- tion T.441 and in Annex A of this Recommendation.
-
- This application profile specifies the use of these attributes as defaultable.
- Currently no default values are defined within this standard.
-
- The application defined attribute list for the Data-Entry-Subprogram-SE contains the
- following attributes:
- w
- ┌────────────────────────────────────────────────────┐
- │ Echo d │
- │ │
- │ Echoed-character d │
- │ │
- │ Echo-parameter nm │
- └────────────────────────────────────────────────────┘
-
- 6.4.1.6 Rules-SE
-
- The application defined attribute list for the Rules-SE contains the following
- attributes:
- w
- ┌────────────────────────────────────────────────────┐
- │ Time-out d │
- │ │
- │ List-of-valid-commands d │
- │ │
- │ Length-of-choice d │
- │ │
- │ List-of-enabled-choices d │
- │ │
- │ Allowed-characters nm │
- │ │
- │ Character-list nm │
- │ │
- │ Entry-invoke-character nm │
- │ │
- │ Local-editing nm │
-
-
-
- 9 Fascicle VII.7 - Rec. T.541
-
-
-
-
- └────────────────────────────────────────────────────┘
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.7 - Rec. T.541 10
-
-
- 6.4.1.7 Prompt-SE
-
- The application defined attribute list for the Prompt-SE contains the following
- attributes:
- w
- ┌────────────────────────────────────────────────────┐
- │ Position d │
- │ │
- │ Dimensions d │
- └────────────────────────────────────────────────────┘
-
- 6.4.1.8 Prompt content portion
-
- The application defined attribute content portion is the following:
- w
- ┌────────────────────────────────────────────────────┐
- │ Coding attributes d │
- └────────────────────────────────────────────────────┘
-
- 6.4.2Attributes of the application control memory structure
-
- Table 3/T.541 shows the use of attributes defined for operational structures.
-
- TABLE 3/T.541
- w
- ┌──────────────────────────────────────────┬────────────────────┐
- │ Attributes │ Data-Entry-SE │
- │ │ ┌──────────────┤
- │ │ │ Record-SE │
- ├──────────────────────────────────────────┼─────┼──────────────┤
- │ Object type │ m │ m │
- │ │ │ │
- │ Object identifier (Note) │ m │ m │
- │ │ │ │
- │ Reference attribute │ -- │ -- │
- │ │ │ │
- │ Application defined │ d │ d │
- │ attribute lists │ │ │
- │ │ │ │
- │ Default value lists │ nm │ -- │
- └──────────────────────────────────────────┴─────┴──────────────┘
-
- Note - This attribute may be omitted when the value can be unambiguously
- derived from the transmission sequence of the relevant objects.
- Values for the attribute object-type
- Application-Control-Memory-SE: 7
- Record-Content: 8
- 6.4.2.1 Application-Control-Memory-SE
- 6.4.2.2 Record-SE
- The application defined attribute list for the Record-SE contains the following
- attributes:
- w
- ┌────────────────────────────────────────────────────┐
- │ Record-content d │
- └────────────────────────────────────────────────────┘
-
- Note - Specifying the record content by using operational elements is for further
- study.
- 6.4.3Attributes of the administrative structure
-
-
-
- 11 Fascicle VII.7 - Rec. T.541
-
-
-
-
- Table 4/T.541 shows the attributes defined for operational structures.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.7 - Rec. T.541 12
-
-