EN ISP 11185-9:1995

SLOVENSKI STANDARD
01-december-1997
Information technology - International Standardized Profiles FVT2nn - Virtual
Terminal Basic Class - Register of control object type definitions - Part 9: FVT222 -
Paged FEICO (Field Entry Instruction Control Object) No. 1 (ISO/IEC ISP 11185-
9:1994)
Information technology - International Standardized Profiles FVT2nn - Virtual Terminal
Basic Class - Register of control object type definitions - Part 9: FVT222 - Paged FEICO
(Field Entry Instruction Control Object) No. 1 (ISO/IEC ISP 11185-9:1994)
Informationstechnik - Internationale Profilnorm FVT2nn - Virtuelles Terminal Grundstufe -
Verzeichnis der Definitionen von Kontrollobjekttypen - Teil 9: FVT222 - Kontrollobjekt zur
Prüfung von Feldeingaben im Seitenbetrieb Nr.1 (ISO/IEC ISP 11185-9:1994)
Technologies de l'information - Profils normalisés internationaux FVT2nn - Classe de
base de terminal virtuel - Registre de définitions de type d'objet de commande - Partie 9:
FVT222 - Page FEICO (Objet de commande d'instruction d'entrée de zone) no 1
(ISO/IEC ISP 11185-9:1994)
Ta slovenski standard je istoveten z: EN ISP 11185-9:1995
ICS:
35.100.05 9HþVORMQHXSRUDEQLãNH Multilayer applications
UHãLWYH
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERNATIONAL
ISO/IEC
STANDARDIZED
ISP
PROFILE
11185-9
First edition
1994-10-01
Information technology - International
Standardized Profiles FVT2nn - Virtual
Terminal Basic Class
- Register of control
Object type definitions -
Part 9:
FVT222 - Paged FEICO (Field Entry
Instruct ion Contro I Object) No. 1
Technologies de Yin forma tion - Profils normalis& in tema tionaux
FW2nn - Classe de base de terminal virtuel - Registre de definitions
de type d ’objet de commande -
Partie 9: FvT222 - Page FEICO (objet de commande d ’instruction
d ’entrke de Zone) no 1
Reference number
ISO/IEC ISP 11185-9:1994(E)
lSO/IEC ISP 11185-9: 1994(E)
Contents
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
1 Scope .
1.1 General
..............................................
1.2 Position within the taxonomy . 1
1.3 Scenario .
2 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
................................................ 4
3 Definitions
3.1 General OSI terminology .
3.2 Terminology of VT base Standards .
3.3 Terminology of VT-user structure .
3.4 Terminology of controlled data entry .
3.5 Definitions of value types and properties .
4 Abbreviations . . . . . . . . . , . . . , . . . . . . . . . . . . , . . . . , . , . . , . , . . . 0 . . 6
5 Principles of conformance to VT Profiles . . . . . . . . . . . . . . . . . . . . . . . . 6
6 Entrynumber. 6
7 Name of sponsoring authority . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8 Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO Descriptor value . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 CO Parameters . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
12 CO values, Syntax and semantics 7
.............................
12.1 The VT-user model
.....................................
12.2 Local processing function
................................
12.3 FEI-attributes 9
..........................................
12.4 FEI definitions i2
........................................
12.5 Mutually Exclusive FEls .
12.6 UpdateSyntax 14
........................................
12.7 Initial Content
........................................
13 Additional information . , . . , . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 Mage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANNEX A ISPICS Requirements List .
A.l Protocol requirements 16
...................................
A.2 Profile-specific requirements 16
..............................
0 ISO/IEC 1994
All rights reserved. No patt of this publication may be reproduced or utilized in any form or by
any means, electronie or mechanical, including photocopying and microfilm, without Permission
in writing from the publisher.
lSO/IEC Copyright Office l Case Postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
0 ISO/IEC
ISO/IEC ISP 111859: 1994(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form
the specialized System for worldwide
standardization. National bodies that are members of ISO or IEC participate in the
development of International Standards through technical committees established by
the respective organization to deal with patticular fields of technical activity. ISO and
IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take patt in the work.
In the field of information technology, ISO and IEC have established a joint technical
committee, lSO/lEC JTCI. In addition to developing International Standards, lSO/IEC
JTCl has created a Special Group on Functional Standardization for the elaboration
of International Standardized Profiles.
An International Standardized Profile is an internationally agreed, harmonized document
which identifies a Standard or group of Standards, together with Options and
Parameters, necessary to accomplish a function or set of functions.
Draft International Standardized Profiles are circulated to national bodies for voting.
Publication as an International Standardized Profile requires approval by at least 75%
of the national bodies casting a vote.
International Standardized Profile lSO/lEC ISP 111859 was prepared with the
collaboration of
- OSI Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- Open Systems Environment Implementors Workshop (OW).
This International Standardized Profile lSO/IEC ISP 11185 forms an International
Register of information objects in accordance with the procedures for the Operation of
OSI Registration Authorities laid down in lSO/IEC 9834. lt is issued in Parts, with
additional Parts being issued as further entries are added to the register-. Esch part is
prepared in accordance with an approval and maintenance process laid down by the
Special Group on Functional Standardization sf lSO/lEC JTCl, Information technology.
lSO/IEC ISP 11185 is issued under the general title Informatjon technology -
International Standardlied Profiles M2nn - Virtual Terminal Basic Class - Register
of control Object type definitions. At present the following Parts are published or are
in the course of preparation:
Part 1: M2II, M212 - Sequenced and Unsequenced Application
Control Objects
Part 2: M213, M214 - Sequenced and Unsequenced Terminal Control
Objects
Part 3: M2?5, M216 - Application RIO Record Loading Control Object,
Terminal RIO Record Notification Control Object
Part 4: M217 - Horizontal Tabulation Control Object
Part 5: M218 - Logical Image Control Object
Part 6: M219 - Status Message Contol Object
Part 7: M2110 - Entry-Control Control Object
Part 8: M221 - Forms FEICO (Field Entry Instruction Control Object) No.1
Part 9: M222 - Paged FEICO (Field Entry Instruction Control Object) No.1
Part IO: M231 - Forms FEPCO (Field Entry Pilot Control Object) No.1
Part 11: M232 - Paged FEPCO (Field Entry Pilot Control Object) No.1
Part 12: M2116, M2117, M2118, M2119 - Generalized Telnet Synch,
Signal, Negotiation and Subnegotiation Control Objects
Part 13: M2111 - Waiting Time Control Object
Part 14: M2112 - Printer Control Object
Part 15: M2113 - Field Definition Management Control Object
- Terminal Signal Titles Control Object
Part 16: M2114
Part 17: M2115 - Help Text Control Object
Annex A of this part of ISO/IEC ISP 11185 forms an integral part of this International
Standardized Profile.
0 ISO/IEC
lSO/IEC ISP 11185-9: 1994(E)
Introduction
This International Standardized Profile lSO/IEC ISP 11185 is defined within the context
of Functional Standardization, in accordance with the principles specified in lSO/lEC
TR 10000, “Framework and Taxonomy of International Standardized Profiles ’!. The
context of Functional Standardization is one part of the Overall field of Information
Technology (IT) standardization activities, covering base Standards, profiles and
registration mechanisms.
The Open Systems Interconnection (OSI) Standard ISO 9040 for the Virtual Terminal
Basic Class Service identifies a requirement for an International Register of VT Control
Object type definitions. Procedures for the Operation of this International Register are
laid down in lSO/IEC 9834-5. This International Standardized Profile provides this
register. The individual entries in this register constitute Interchange Format and
Representation Profiles (F-Profiles) within the framework of lSO/lEC TR 10000.
This part of lSO/IEC ISP 11185 was developed in close cooperation between the three
Regional OSI Workshops, namely the OSE Implementors Workshop (OMI) of the
United States, the European Workshop for Open Systems (EWOS) and the OSI Asia-
Oceania Workshop (AOW). lt was developed under the editorship of EWOS. The text
is harmonized between these three Workshops and it has been ratified by the plenary
assemblies of each Workshop.
iv
ISO/IEC ISP 11185-9: 1994(E)
INTERNATIONAL STANDARDIZED PROFILE @ ‘So ”EC
Information technology - International Standardized
Profiles FVT2nn - Virtual Terminal Basic Class - Register
of control Object type definitions -
Part 9:
Paged FEC0 (Field Entry Instruction Control
FVT222 -
Object) No. 1
1 Scope required to realise a particular function and to promote
interoperability constitutes a Virtual Terminal A-Profile within
1 .l General
the framework of ISO/IEC TR 10000.
The concept of Profiles for OSI, and the structure of the The three International Registers of VT information structures
International Standardized Profiles that document them, are and the specifications of VT Application Profiles are each
defined in lSO/lEC TR 10000-1. Such Profiles are divided into published as a separate multi-part ISP as follows:
a number of different classes and sub-classes. Two of these
classes contain sub-classes comprising functions of the - lSO/IEC ISP 11184 is the Register of VTE-profiles;
Virtual Terminal Basic Class Service and Protocol specified
in the base Standards ISO 9040 and ISO 9041. These are the - ISO/IEC’ ISP 11185 is the Register of control Object
Application Profiles (A-Profiles) and the Interchange Format
type definitions;
and Representation Profiles (F-Profiles).
- ISO/IEC ISP 11186 is the Register of assignment-type
The relationship between A-Profiles and F-Profiles is definitions;
described in 7.3.2 of ISO/IEC TR 10000-1 and is as follows.
Application Layer base Standards require, implicitly or - ISO/IEC ISP 11187 contains the specifications of VT
explicitly, the structure of information carried or referenced by Application Profiles.
them to be specified for each instance of communication. lt
is the purpose of F-Profiles to specify such information
This part of ISO/lEC ISP 11185 contains the type definition of
structures. Particular functional requirements may then be
a Field Entry Instruction Control Object that provides
met by the combination of an A-Profile with one or more F- substantial capabilities for local Validation of data entry under
Profiles. application control. lt is intended for use in form-filling and
similar applications. The delegation of such verification to the
Establishment of a VT-association involves the selection by
terminal end System may reduce significantly the demands
negotiation of a particular Virtual Terminal Environment Profile placed on the communication network and the application
(VTE-Profile), and of particular values for any arguments of process, and may substantially improve the reaction time to
that VTE-Profile. The VTE-Profile speciflcation, and possibly users’ actions.
also the values of certain VTE-Profile arguments, may in turn
reference the definitions of VT control Object types and 1.2 Position within the taxonomy
assignment types. These VTE-profiles, control Object types
and assignment types are thus information structures that The taxonomy of International Standardized Profiles for OSI
require explicit reference within the VT protocol. Particular is laid down in ISO/IEC TR 10000-2. Within the classification
instances of these structures are fully defined within the base
scheme of this taxonomy, the OSI Profiles specified in this
Standards, but the base Standards also provide for further
International Standardized Profile are in the Virtual Terminal
instances to be defined by registration. Esch registered
Registered Object sub-class of the class of lnterchange
instance constitutes an F-Profile within the framework of
Format and Representation Profiles.
ISO/IEC TR 10000.
A Profile within this subclass has a Profile identifier of the
The Virtual Terminal Basic Class Service and Protocol may
form FVTabc, where abc is a structured numerical identifier
be used to realise a wide range of distinct functions.
that identifies the Position of the Profile within each of the
Particular functions may be realised through the selection of
three levels of subdivision of the subclass. The values of a
appropriate VT functional units, F-Profiles and other VTE- and b are Single digits but c is an integer that is not
Profile argument values. The specification of the selection necessarily a Single digit.
0 lSO/IEC
ISO/IEC ISP 11185-9: 1994(E)
In principle the ISO Virtual Terminal model allows for multiple
classes of Operation, although at the time of publication of
this International Standardized Profile only the Basic Class
has been defined. The value of the identifier component a
distinguishes between distinct types of information Object as
follows:
VT service-protider
- a=
1 for Basic Class VTE-profiles;
- a= ~
2 for Basic Class Control Objects;
- a=
3 for Basic Class Assignment Types.
Figure 1 - Confrol objects in the VT Service model
Values of a greater than 3 reserved for future
develop ments.
This International Standardized Profile lSO/IEC ISP 11185
Structure Definition (DSD) component of the CCA contains
contains the specifications of the Profiles with identifiers of
the Syntax of its information content, including the range of
the form FVT2bc. For this form of identifier, the component possible values and the permitted update operations. The
b distinguishes between the five major classifications of Basic
current value of its information content is contained in the
Class Control Objects as follows: Control, Signal and Status store (CSS) component. Updates
to the current value take place through the issue of VT
- bz
1 for Miscellaneous Control Objects; Service primitives by one VT-user to the service-provider,
Changes of state of the CCA are made accessible through
the issue of VT Service primitives by the service-provider to
- b = 2 for Field Entry Instruction Control Objects;
the peer W-User.
- b = 3 for Field Entry Pilot Control Objects;
By clause 14 of ISO 9040, COS enable VT-users to handle
b = 4 for Reference Information Objects;
control information related to virtual terminal functions and to
real devices. This control is exercised by the VT-users
- b = 5 for Termination Conditions Control Objects.
through semantics associated with the information content
and with the update operations of the CO. Definition of the
Esch of these classifications corresponds to a sub-register
semantics, or specification of the Source of the semantics if
under the procedures of lSO/IEC 9834-5. The identifier
the semantic details are not fully prescribed, forms part of the
component c is the serial number of the control Object type
registered definition of the CO. These semantics are not
in the appropriate sub-register. Values of b greater than 5 are
however of concern to the VT service-provider itself. The
reserved for new classifications of Basic Class Control
DSD will contain an ASN.l Object identifier that identifies the
Objects that may be defined in future amendments to ISO
registered definition, but the VT service-provider merely acts
9040.
as a repository of this value. lt is only the VT-user that
requires knowledge of the registered definition.
This part of ISO/IEC ISP 11185 contains the definition of the
Field Entry Instruction Control Object type with the Profile
NOTE 1 - The V-TE-Parameter values that determine the Syntax of
identifier
the information content may not be negotiated explicitly during
association establishment. Moreover, in the case of non-parametric
FVT222 - Paged FEICO (Field Entry Instruction Control
COS these values do not determine the details of the Syntax. Such
Object) No. 1 values and details form patt of the registered definition of the CO.
Since the VT service-provider is not required to have knowledge of
this registered definition, in principle the VT-users provide the VT
1.3 Scenario
service-provider with such information through local management
procedures. Whether or not this is necessary in practice depends on
The specification of the Virtual Terminal Service is given in
the configuration of the implernentations concerned.
ISO 9040. lt is based on a model in which two VT-users
communicate by means of a shared Conceptual
The control Object type defined in this part of lSO/IEC
Communication Area (CCA) that is a conceptual patt of the
ISP 11185 assumes an asymmetry between the two
VT service-provider. Information exchange is modelled by
communicating end Systems. One end System is assumed
one VT-user updating the content of the CCA and the
to have a terminal role and to contain devices for the input
changed state of the CCA then being made accessible to the
and display of data and for signalling. These devices form
peer VT-user-.
part of the VT-user component of that end System. The other
end System is assumed to have an application role and to
Control objects (COS) form one of the types of information
contain an application package that the terminal end System
Object that may be present in the CCA. This is illustrated in
desires to access. This asymmetry may, but need not, be
figure 1, in which CO-I, CO-2, . . . CO-n represent a number
recognised by the VT Service; Provision for such recognition
of different control objects present in the CCA. The
negotiation during establishment of a VT-association will is made in 19.3.2 of ISO 9040 only for an S-mode VT-
determine whether or not these will include a control Object association.
of the type whose definition is given in this part of lSO/lEC
ISP 11185. A control Object of the type defined in this part of lSO/IEC ISP
11185 is a Field Entry Instruction Control Object (FEICO) as
The CCA is structured by the Virtual Terminal Service into a defined in 20.3.4 of ISO 9040. The content of a FEICO is an
number of components. For a control Object the Data array of records known as Field Entry Instruction Records

0 ISO/IEC
ISO/IEC ISP 111859: 1994(E)
Machines (VTPMs), each with its own CCA. The CCA of
(FEIRs) that may be referenced by a Field Definition Record
each VTPM is updated both by Service primitives received
(FDR). Such reference imposes either or both of constraints
the from its own VT-user and by protocol elements received from
on th e update operations permitted for the content of
this the peer VTPM. Corresponding Service primitives and
field, and instructions concerning the manner in which
protocol elements are issued by the VTPM to provide
content is to be represented by a real display device. Such
notification of changes to the content of its CCA. This is
constraints apply only to updates by the terminal end System.
illustrated in figure 2 in the context of the asymmetric end
The contents of the FEICO and FDR may be updated only by
Systems described above. The control Object type definition
the application end System.
given in this patt of lSO/lEC ISP 11185 is expressed in terms
of this model.
The definition of a FEICO type specifies the individual Field
Entry Instructions (FEls) that may be used in an FEIR. An
Esch VTPM is permitted to store updates to its CCA before
FEIR consists of a set of such FEls. The FEICO type
definition also specifies the semantic interpretation of
onward delivery, in accordance with the data transfer
references to such FEIRs by an FDR. Semantic significance mechanisms of annex A of ISO 9041-1. These mechanisms
for a particular FDR applies to the set of referenced FEIRs as permit storage both for updates that result from the reception
a whole. There need not be a one-to-one correspondence of Service primitives and for those that result from the
between elements of the semantics and individual FEls or
reception of protocol elements. The combined effect of these
FEIRs. The FEICO type definition may, for example, both
mechanisms in both VTPMs is to implement the delivery
assign semantics to individual FEls and specify the manner
control mechanisms of ISO 9040. But the effect of such
in which conflicts between FEls are to be resolved.
storage is that the content of the two CCAs may differ from
one another and that nesther need correspond to the CCA of
When a FEICO is present in the CCA, it is required by 14.2 of
the VT Service model. The CCA of each VTPM should
ISO 9040 that a Field Entry Pilot Control Object (FEPCO)
properly be regarded as an incompletely updated copy of the
shall also be present. An attempt to update the content of a
true CCA of the VT service-provider,
field in Violation of the FEIRs sf its FDR constitutes an event
that may be recognised as a Field Entty Event by such a
For certain types of control Object the abstract Syntax of ISO
FEPCO. The reaction to the attempted Violation will be
9041-1 does not provide a complete specification for the
determined by the content of the FDR in conjunction with the
representation of CO update operations. This arises where
type definition of the FEPCO concerned. For S-mode
the abstract Syntax of ISO 9041-1 makes use of an ASN.1 any
Operation a FEPCO type suitable for used with a FEICO of
type, or where symbolic values have to be encoded in terms
the present type is defined in ISO/IEC ISP 11185-11.
of an ASN.1 integer type. Control Object type definitions are
required by lSO/IEC 9834-5 to provide the necessary
The VT service-provider may store updates received from one
refinement of the abstract Syntax.
VT-user before delivery to the peer VT-user in accordance
with the delivery control mechanisms of clause 24 of ISO
NOTE 2 - Since an abstract Syntax is made available for use
9040. So although the model of the VT Service is expressed
through its inclusion in a presentation context, and since the
in terms of a Single shared CCA, at instant the various
anY Presentation service-provider has no knowledge of control Object
elements of the two communicating end Systems may have
type definitions, in principle the VT-users provide the Presentation
differing knowledge of its current content.
service-provider with these refinements to the abstract Syntax through
local management procedures. Whether or not this is necessary in
practice depends on the configuration of the implernentations
Terminal Ap Iication
concerned.
en System
end System CP
B
VT-user A VT-user B
2 Normative references
VT sehe
The following documents contain provisions which, through
prlmkbes
reference in this text, constitute provisions of this part of
lSO/IEC ISP 11185. At the time of publication, the editions
J L
I
\
indicated were valid. All documents are subject to revision,
and Parties to agreements based on this International
VTPM-A VTPM-B
Standardized Profile are warned against automatically
applying any more recent editions of the documents listed
below, since the nature of references made by ISPs to such
VT Protocol
documents is that they may be specific to a particular edition.
Members of IEC and ISO maintain registers of currently valid
International Standards and ISPs, and CCITT maintains
published editions of its current Recommendations.
Figure 2 - Control objects in the VT Protocol model
ISO 2375: 1985 ”, Data processing - Procedure for
registration of escape sequences.
This Variation in knowledge extends within the VT service-
provider itself. The Virtual Terminal Protocol specification
ISO 7498:1984, Information processing Systems - Open
given in ISO 9041-1 models the VT service-provider in terms
Systems Interconnection - Basic Reference Model.
of protocol exchange between two Virtual Terminal Protocol
1) The Registration Authority for ISO 2375 is the European Computer Manufacturers Association (ECMA), 114 rue du Rhone, CH-1204 Geneve,
Switzerland, from whom the corresponding register, the ISO /nfernat/ona/ Register of Coded Character Sefs to be used with Escape Sequences,
may be obtained.
0 ISO/IEC
lSO/lEC ISP 111859: 1994(E)
lSO/TR 8509: 1987, Information processing Systems - Open null type;
b)
Systems Interconnection - Service conventions.
c) Object descriptor type;
ISO 8822:1988, Information processing Systems - Open
Systems Interconnection - Connection orientedpresentation
d) Object identifier.
Service definition.
3.1.4 This part of ISO/IEC ISP 11185 makes use of the
lSO/lEC 8824: 1990, Information technology - Open Systems
following terms defined in lSO/IEC 9834-1:
Interconnection - Specification of Abstract Syntax Notation
One (ASN. 1).
registration;
ISO 9040:1990, Information technology - Open Systems
registration-hierarchical-name.
b)
Interconnection - Virtual Terminal Basic Class Service.
3.2 Terminology of VT base Standards
ISO 9041-1 :1990, Information technology - Open Systems
Interconnection - Virtual Terminal Basic Class Protocol-
3.2.1 This part of ISO/IEC ISP 11185 makes use of the
Part 1: Specification.
following terms defined in ISO 9040:
lSO/lEC 9041-2: 1993, Information technology - Open
a) A-mode;
Systems Interconnection - Virtual Terminal Basic Class
Protocol - Part 2: Protocol lmplementation Conformance
array element;
W
Statement (PICS) Proforma.
Character-repertoire;
C>
lSO/IEC 9834-1: 1993, Information technology - Open
Systems Interconnection - Procedures for the Operation
d) control Object;
of OS/ Registration Authorities - Part 1: General
Procedures.
device Object;
e>
lSO/IEC 9834-5: 1991, Information technology - Open
Systems Interconnection - Procedures for the Operation of f) display Object;
OS/ Registration Authorities - Part 5: Register of VT Control
Object Definitions. g) field;
lSO/lEC TR 10000-1: 1992, Information technoiogy -
h) Field Definition Record;
Framework and taxonomy of International Standardized
Profiles - Part 1: Framework (second edition).
Field Entry Instruction;
lSO/lEC TR 10000-2: 1992, Information technology -
j) Field Entry Instruction Record;
Framework and taxonomy of International Standardized
- Part 2: Taxonomy of Profiles (second
Profiles
logical pointer;
k)
edition).
Object updating device;
3 Definitions
m) primary attribute;
For the purposes of this patt of ISO/IEC ISP 11185 the
n) rendition attribute;
following definitions apply.
S-mode ’;
0)
3.1 General OSI terminology
secondary attribute;
P>
3.1.1 This part of lSO/IEC ISP 11185 makes use of the
following terms defined in ISO/TR 8509:
VT-association;
Service primitive;
r) VT-environment (VTE);
service-provider.
b)
s) VT-user-;
3.1.2 This part of ISO/IEC ISP 11185 makes use of the
t) V-TE-Parameter;
following terms defined in ISO 8822:
u) VTE-Profile;
abstract Syntax;
v) VhE-Profile argument.
b) presentation context.
3.1.3 This part of ISO/IEC ISP 11185 makes use of the 3.2.2 This part of lSO/IEC ISP 11185 makes use of the
following terms defined in ISO/IEC 8824: following term defined in ISO 9041-1:
protocol element.
a> any type;
0 ISO/IEC
ISO/IEC ISP 11185-9: 1994(E)
3.3 Terminology of VT-user structure the internal CCA before updates to the content of that field
are issued to the VT service-provider, A Validation failure may
3.3.1 device control store: A conceptual store containing result in a Field Entry Event but it cannot Cause any updates
abstract objects which represent aspects of the internal state to be discarded.
of the VT-user that are not associated with a specific Object
3.4.6 protected field: A field with a content that is not
updating device.
subject to update by Object updating devices. The Field
Definition Record determines whether or not a field is a
3.3.2 device Status store: A conceptual store containing
protected field.
abstract objects which represent aspects of the state of a
specific Object updating device.
3.5 Definitions of value types and properties
3.3.3 DO mask: An abstract Object within a device Status
3.5.1 Character: An item that is either a qualified Character
store that contains a conceptual overlay for the display Object
or an unqualified Character.
of the internal CCA. The overlay modifies the attribute values
to be represented by the device, to indicate the location of an
3.5.2 Character-string: An item that is either a qualified
entry cursor or for other reasons of local significance.
Character-string or an unqualified Character-string.
3.3.4 DO mask element: An element of a DO mask that
3.5.3 Character-string range: An item that is either a
forms the overlay to a Single attribute of a Single DO array
qualified Character-string range or an unqualified character-
element.
string range.
3.3.5 extemal CCA: A conceptual copy of the CCA
3.5.4 less than (of unqualified Character-strings): Two
maintained by a VT-user which takes account of all update
unqualified Character-strings s and s’ of the same length and
operations that either have been received from, or have been
with the same character-repertoire value are compared by
issued to, the VT service-provider,
comparing sequentially the primary attribute values of
corresponding elements, starting from the beginning of each
3.3.6 internal CCA: A conceptual copy of the CCA
sequence. The string s is defined to be less than s’ (s c s ’)
maintained by a VT-user which takes account of all update
if the same inequality is satisfied by the numeric values of the
operations that either have been received from the VT
first pair of primary attribute values that are numerically
service-provider or have been accepted from Object updating
unequal. If no such pair exists then the Character-strings are
devices. Its content may differ from that of the external CCA
when controlled data entry is in use. In these circumstances defined to be equal (s = s ’). The notation s 5 s’ is used to
it takes account of accepted update operations that have not denote that either s < s’ or s = s ’.
yet been issued to the VT service-provider.
3.5.5 lower bound (of an unqualified Character-string
3.3.7 local action Operation: An Operation that updates range): This term is defined in 3.513.
the content of a device Status store or device control store.
3.5.6 qualified Character: An unqualified Character
3.3.8 logical entry location: An abstract Object within a together with a rendition qualifier.
device Status store, containing a logical address as defined
in 13.1.3 of ISO 9040. 3.5.7 qualified Character-string: An unqualified character-
string together with a rendition qualifier; such a string also
3.4 Terminology of controlled data entry has a natura1 interpretation as a sequence of qualified
characters.
3.4.1 event processing: A function that generates
reactions dependent on the Field Definition Record of a field
3.5.8 qualified Character-string range: An unqualified
when specified events occur during the entry of data into the Character-string range together with a rendition qualifier; such
field.
a range also has a natura1 interpretation as a set of qualified
Character-strings.
3.4.2
FEI-attribute: An abstract Object that is associated
with afield and whose value is assigned by the content of the 3.5.9 partial rendition: A set of explicit values for one or
Field Definition Record for that field. The contents of all the
more of the rendition attributes.
FEI-attributes for a field together determine the entry rules for
controlled data entry into that field.
3.5.10 rendition qualifier: A specification of a value for
each rendition attribute. Esch value may, but need not, be
3.4.3 free field: A field with a content that is subject to specified explicitly. Values that are not specified explicitly
update by Object updating devices. The Field Definition take dynamic default values that are determined at the time
Record determines whether or not a field is a free field. of access. The first choice default is the field modal attribute
value defined in 13.1.3.2 of ISO 9040. A first choice default
3.4.4 input Validation: A function applied to test the value of “null” is resolved as specified in 19.2.2.1 of ISO 9040
validity of display Object update requests that are generated for the LOGICAL-TEXT update Operation.
by an Object updating device and that use the logical pointer.
The function is applied before the requested updates are 3.5.11 unqualified Character: A primary attribute value
applied to the internal CCA. A Validation failure may result in together with a value for the Character-repertoire secondary
a Field Entry Event and may Cause the update request to be attribute.
discarded.
3.5.12 unqualified Character-string: A sequence of
3.4.5 output Validation: A function that may be applied
unqualified characters that all have the same value for the
to test the validity of the content of a field as maintained by
Character-repertoire secondary attribute.

ISO/IEC ISP 11185-9: 1994(E) 0 ISO/IEC
3.5.13 unqualified Character-string range:
A set of sub-registers, each corresponding to a major classification of
unqualified Character-strings, all of the same length and with
VT Control Object.
the same Character-repertoire value, that has two
distinguished members s (known as the lower bound) and s’ This entry is the second in the sub-register for Field Entry
(known as the upper bound) such that s” is a member of the Instruction Control Objects. This register assigns it the entry
set if, and only if, s 5 s” 5 s ’. number:
3.5.14 upper bound (of an unqualified Character-string FEICO-2.
range) : This term is defined in 3.5.13.
7 Name of sponsoring authority
4 Abbreviations
This entry is sponsored by the European Workshop for Open
For the purposes of this part of lSO/IEC ISP 11185 the Systems (EWOS). .
following abbreviations apply.
8 Date
AOW OSI Asia-Oceania Workshop;
EWOS European Workshop for Open Systems;
The date of Submission of this proposal was 1992-09-02.
OIW OSE Implementors Workshop;
OSE Open Systems Environment.
9 Identifier
All other abbreviations used are defined in lSO/IEC
TR 10000-1 or ISO 9040.
The name assigned to an information Object by an
International Register is required by lSO/lEC 9834-1 to be a
registration-hierarchical-name. A registration-hierarchical-
5 Principles of conformance to VT Profiles
name may have more than one form. The permitted forms
include an ASN.l Object identifier as defined in ISO/IEC 8824
An implementation of the Virtual Terminal Protocol conforms
and a relative distinguished name as defined in lSO/IEC
to an FVT2nn Profile that defines a control Object type if the
9594-2.
protocol implementation is capable of sending and receiving
PDUs corresponding to all update operations permitted for
In accordance with A.4 of lSO/lEC 9834-5, this register
that CO type.
assigns the following Object identifier form for the name of
this register entry:
Conformance of a protocol implementation to an FVT2nn
Profile does not place requirements on the ability of the
{ iso(l) Standard(O) 9834 vt-co-def(5) feico(1) 2 }
implementation to negotiate the presence in the CCA of an
instance of this CO type. Such requirements fall within the
In accordance with 20.1.1 of ISO 9040, this Object identifier
scope of conformance to an FVTlnn Profile that specifies a
shall be used as the value of the CO-type-identifier VTE-
VTE-Profile.
Parameter for a control Object in Order to identify this register
entry as the Source of the information structure and semantic
A System that includes an implementation of the VT Protocol
content of the control Object. This Object identifier shall also
may be claimed to conform also to an AVTnn Profile.
be used to identify the ASN.1 module specified within this
Conformance to an AVTnn Profile may require that CO
register entry as the Source of abstract Syntax by which
update operations received by the VT-user component of the
update operations on this CO are specified within the VT
System are interpreted in accordance with the semantics
protocol of ISO 9041-1.
defined within the appropriate CO type definition.
Conformance to CO semantics is not within the scope of
This register does not assign other form to the name of
anY
conformance to any FVTnnn Profile.
this entry.
The conformance requirements of the Virtual Terminal
NOTE - By ISO/IEC 9834-1 a relative distinguished name for the
Protocol are specified in clause 13 of ISO 9041-1. The
purposes of the OSI Directoty may only be assigned together with an
supplier of a protocol implementation which is claimed to
Object identifier when the Object identifier form is generated under
conform to ISO 9041-1 is required to complete a copy of the
the arc { joint-iso-ccitt(2) country(l6) country-name }.
PICS proforma provided in lSO/IEC 9041-2. Annex A of this
part of lSO/IEC ISP 11185 provides an ISPICS Requirements
List (IPRL) for the Profile FVT222 specified herein. This IPRL IQ) Descriptor value
specifies constraints on the answers that may be given in the
completed PICS for a protocol implementation that Claims The value of the ASN. 1 Object descripto Ir type assigned to
conformance to this Profile.
this register entry is:
“First harmonized FEICO for use by Paged VTE-profiles ”.
6 Entry number
The remaining clauses of this part of ISO/IEC ISP 11185
11 CO Parameters
provide the entry for the Paged FEICO No.1 in the
International Register of VT Control Object Type Definitions.
This CO type presumes an asymmetry of use between the
The entry is structured in accordance with the requirements two end Systems in which one has a terminal role and the
of lSO/lEC 9834-5. These requirements specify that this other an application role. Such an asymmetry is assigned in
International Register shall consist of a number of accordance with note 1 to clause 12 of ISO 9040. lt is not
0 ISO/IEC
ISO/IEC ISP 11185-9: 1994(E)
necessary for this asymmetry to be recognised by the VT
service-provider in accordance with 19.3.2 of ISO 9040, which
provides for the assignment, in S-mode only, of Terminal VT-
VT-user A
user and Application W-User roles.
Local processhg
This register entry specifies the following values for WE-
functlon
Parameters of this control Object type:
CO-structure: “non-parametric”
CO-access: takes the same value as the CO-
\
access VTE-Parameter for the FDCO
associated with the same display
Object
CO-priority : “normal”
CO-trigger: “not selected”
D8Vb
control
store
The CO-access VTE-Parameter for the FDCO, and thus also
for this FEICO, should be assigned the value that permits
~
access only by the VT-user with the application role. This
value will depend on whether the VT-association was initiated
by the terminal or application end System.
NOTE - A Single VTE-Profile argument may be used to assign Figure 3 - Structure of the terminal VT-user
values to the CO-access VTE-Parameter for all control objects in the
CCA that presume an asymmetric assignment of terminal and
application roles to the two communicating end Systems.
place requirements on, and may exert control over, the
capabilities of the real devices of the VT-User. The
specification of such objects shall include any required rules
12 CO values, Syntax and semantics
that concern update access to the Object. Abstract objects
specified in this way by one control Object may be updated
12.1 The VT-user model
and referenced by other control objects if their definitions so
permit.
12.1.1 The semantic definition of this FEICO is based on the
structured model of the VT-user of the terminal end System
12.1.2 The VT-user receives data from its Object updating
that is illustrated in figure 3. This model is intended solely to
devices and assembles it into Object updates that form
assist the process of definition. lt is not intended to provide
permitted content for VT-DATA request primitives, and into
a model for implernentations. The requirement upon VT-user
local action operations that update objects held in the device
implernentations is only that their external behaviour
Status storesand the device control store. Only the Object
corresponds to the external behaviour of the model.
updates may be issued to the VT service-provider.
Communication with the VT service-provider uses a model of
Real devices may possess internal state information. For an
update queues and priority handling that is specified in 24.5
Object updating device this information determines, among
of ISO 9040. Local action operations have an effect that is
other things, the location of the DO array element that will be
purely internal to the VT-User.
updated by the next data input and the manner in which this
location will be made known to the human user of the device.
A sequence of DO updates and local action operations may
In the model, the state information is represented by the
be generated by a Single action of an Object updating device.
content of abstract objects held in a device Status store.
The VT-user may treat such a sequence as an indivisible
There will be one device Status store for each real device.
macro Operation, provided that a Single macro Operation shall
not contain both operations that use the display pointer and
NOTE - For an Object updating device that consists of a
those that use the logical pointer. Such macros assume
keyboard and display Screen, the above aspects of the state
significance when controlled data entry is in use as defined
information correspond to the location and Screen representation of
by 14.2 of ISO 9040, since it is the effect of a macro as a
an input cursor. On some Object updating devices th
...