EN ISP 11185-11:1995

SLOVENSKI STANDARD
01-december-1997
Information technology - International Standardized Profiles FVT2nn - Virtual
Terminal Basic Class - Register of control object type definitions - Part 11: FVT232
- Paged FEPCO (Field Entry Pilot Control Object) No.1 (ISO/IEC ISP 11185-11:1994)
Information technology - International Standardized Profiles FVT2nn - Virtual Terminal
Basic Class - Register of control object type definitions - Part 11: FVT232 - Paged
FEPCO (Field Entry Pilot Control Object) No.1 (ISO/IEC ISP 11185-11:1994)
Informationstechnik - Internationale Profilnorm FVT2nn - Virtuelles Terminal Grundstufe -
Verzeichnis der Definitionen von Kontrollobjekttypen - Teil 11: FVT232 - Kontrollobjekt
zur Behandlung von Feldeingaben im Seitenbetrieb Nr.1 (ISO/IEC ISP 11185-11: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
11: FVT 232 - Page FEPCO (Objet de commande pilote d'entrée de zone) no 1 (ISO/IEC
ISP 11185-11:1994)
Ta slovenski standard je istoveten z: EN ISP 11185-11: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
PROFILE
11185-11
First edition
1994-10-01
Information technology - International
Standardized Profiles FVT2nn - Virtual
Terminal Basic Class
- Register of control
Object type definitions -
Part 11:
FVT232 - Paged FEPCO (Field Entry Pilot
Control Object) No. 1
Technologies de I ’informa tion - Profils normalk& in terna tionaux
FVT2nn
- Classe de base de terminal virtuel - Registre de definitions
de type d ’objet de commande -
Partie 11: FVr232 - Page FEPCO (objet de commande pilote d ’entke
de Zone) no 1
lSO/IEC ISP 1118511: 1994(E)
Contents
. . .
Ill
Foreword. .
iv
.................................................
Introduction
Scope .
..............................................
1.1 General
...............................
1.2 Position within the taxonomy
..............................................
1.3 Scenario
.......................................
Normative references
................................................
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
.............................................
Abbreviations
........................
Principles of conformance to VT Profiles
..............................................
Entrynumber
.................................
Name of sponsoring authority
Date .
Identifier .
IO Descriptor value . . , , , . , , , , . , . . . . . . . . . . . . . . . , . . . . . . . . . . . . . .
11 CO Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . .
.............................
12 CO values, Syntax and semantics
.....................................
12.1 The VT-user model
................................
12.2 Local processing function
12.3 FEPCO structure .
........................................
12.4 FEE definitions
i0
12.5 FEC definitions .
IO
12.6 FER definitions .
........................................
12.7 UpdateSyntax
........................................
12.8 Initial Content
13 Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANNEX A ISPICS Requirements List .
A.l Protocol requirements .
A.2 Profile-specific requirements .
0 ISO/IEC 1994
All rights reserved. No part 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.
ISO/IEC Copyright Office l Case Postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
0 ISO/lEC
ISO/IEC ISP 1118541: 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 particular 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 part in the work.
In the field of information technology, ISO and IEC have established a joint technical
committee, lSO/IEC JTCl. In addition to developing International Standards, lSO/IEC
JTCI 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 ISO/IEC ISP 11185-11 was prepared with the
collaboration of
- OSI Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- Open Systems Environment Implementors Workshop (OIW).
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 of lSO/IEC JTCl, Information technology.
lSO/IEC ISP 11185 is issued under the general title Information technology -
International Standardized Profiles M2nn - Vjrtuai Terminal Basic Ciass - Register
of controi Object type definitions. At present the following Parts are published or are
in the course of preparation:
Part 1: M211, M212 - Sequenced and Unsequenced Appijcation
Controi Objects
Part 2: M213, M214 - Sequenced and Unsequenced Terminal Controi
Objects
Part 3: M215, M216 - Appikation RIO Record Losding Controi Object,
Terminal RIO Record Notjfjcatjon Controi Object
Part 4: M217 - Horizontal Tabuiatjon Controi Object
Part 5: M218 - Logicai Image Controi Object
Part 6: M219 - Status Message Controi Object
Part 7: M2110 - Entry-Controi Controi Object
Part 8: M221 - Forms FEiCO (Fjeld Entry instruction Controi Object) No.1
Part 9: M222 - Paged FEICO (Fjeld Entry instruction Controi Object) No.1
Part 10: M231 - Forms FEPCO (Fjeld Entry Pilot Controi Object) No.1
Part 11: M232 - Paged FEPCO (Fjeld Entry Pilot Controi Object) No.1
Part 12: M2116, M2117, M2118, M2119 - Generaijzed Teinet Synch,
Signal, Negotiation and Subnegotjatjon Controi Objects
Part 13: M2111 - Waiting Time Controi Object
Part 14: FV72112 - Printer Controi Object
Part 15: M2113 - Fjeld Definition Management Controi Object
Part 16: M2114 - Terminal Signal Tjties Controi Object
- Heip Text Controi Object
Part 17: M2115
Annex A of this part of lSO/IEC ISP 11185 forms an integral part of this International
Standardized Profile.
. . .
Ill
0 ISO/IEC
lSO/IEC ISP 11185-11: 1994(E)
Introduction
This International Standardized Profile ISO/IEC ISP 11185 is defined within the context
of Functional Standardization, in accordance with the principles specified in lSO/IEC
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 ISO/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/IEC TR 10000.
This part of ISO/IEC ISP 11185 was developed in close cooperation between the three
Regional OSI Workshops, namely the OSE Implementors Workshop (ON) 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.
INTERNATIONAL STANDARDIZED PROFILE @ ‘So ”EC lSO/lEC ISP 1118541: 1994(E)
Information technology - International Standardized
Profiles FVT2nn - Virtual Terminal Basic Class - Register
of control Object type definitions -
Part 11:
FVT232 - Paged FEPCO (Field Entry Pilot Control Object)
No.1
1 Scope interoperability constitutes a Virtual Terminal A-Profile within
the framework of ISO/IEC TR 10000.
1.1 General
The three International Registers of VT information structures
The concept of Profiles for OSI, and the structure of the
and the specifications of VT Application Profiles are each
International Standardized Profiles that document them, are
published as a separate multi-part ISP as follows:
defined in lSO/IEC TR 10000-1. Such Profiles are divided into
a number of different classes and sub-classes. Two of these
- lSO/lEC ISP 11184 is the Register of VTE-profiles;
classes contain sub-classes comprising functions of the
Virtual Terminal Basic Class Service and Protocol specified
- lSO/IEC ISP 11185 is the Register of control Object
in the base Standards ISO 9040 and ISO 9041. These are the
type definitions;
Application Profiles (A-Profiles) and the Interchange Format
and Representation Profiles (F-Profiles).
- lSO/IEC ISP 11186 is the Register of assignment-type
definitions;
The relationship between A-Profiles and F-Profiles is
described in 7.3.2 of ISO/IEC TR 10000-1 and is as follows.
- ISO/IEC ISP 11187 contains the specifications of VT
Application Layer base Standards require, implicitly or
Application Profiles.
explicitly, the structure of information carried or referenced by
them to be specified for each instance of communication. lt
This part of ISO/IEC ISP 11185 contains the type definition of
is the purpose of F-Profiles to specify such information
a Field Entry Pilot Control Object that provides substantial
structures. Particular functional requirements may then be
facilities during data entry for local processing under
met by the combination of an A-Profile with one or more F-
application control. lt is intended for use in form-filling, text
Profiles.
editing and similar applications during a VT-association in S-
mode (synchronous mode) Operation. The delegation of
Establishment of a VT-association involves the selection by
such processing to the terminal end System may reduce
negotiation of a particular Virtual Terminal Environment Profile
significantly the demands placed on the communication
(VI-E-Profile), and of particular values for any arguments of
network and the application process, and may substantially
that VI-E-Profile. The VTE-Profile specification, and possibly
improve the reaction time to users’ actions.
also the values of certain VI-E-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 lSO/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 Interchange
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 FVT&c, 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
appropriate VT functional units, F-Profiles and other VTE- three levels of subdivision of the subclass. The values of a
Profile argument values. The specification of the selection and b are Single digits but c is an integer that is not
required to realise a particular function and to promote necessarily a Single digit.
0 ISO/IEC
ISO/IEC ISP 11185-11: 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:
- a=
1 for Basic Class VTE-profiles;
Conceptual Communbtlon Area
-a = 2 for Basic Class Control Objects;
a = 3 for Basic Class Assig nment Types.
Values of a greater than 3 are reserved for future Figure 1 - Confrol objects in the VT Service model
developments.
This International Standardized Profile ISO/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
- b = 2 for Field Entry Instruction Control Objects;
the issue of VT Service primitives by the service-provider to
the peer VT-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/lEC 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 sf 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 Po 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 Pilot Control Object type with the Profile
NOTE 1 - The VTE-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
FVT232 - Paged FEPCO (Field Entry Pilot Control
COS these values do not determine the details of the Syntax. Such
Object) No. 1
values and details form part of the registered definition of the CO.
Since the VT service-provider is not required to have knowledge of
1.3 Scenario
this registered definition, in principle the VT-users provide the VT
service-provider with such information through local management
The specification of the Virtual Terminal Service is given in
procedures. Whether or not this is necessary in practice depends on
ISO 9040. lt is based on a model in which two VT-users the configuration of the implernentations concerned.
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 part sf the
ISP 11185 assumes an asymmetry between the two
VT service-provider. Information exchange is modelled by
one VT-user updating the content of the CCA and the communicating end Systems. One end System is assumed
changed state of the CCA then being made accessible to the to have a terminal role and to contain devices for the input
peer VT-User. and display of data and for signalling. These devices form
part of the VT-user component of that end System. The other
Control objects (COS) form one of the types of information end System is assumed to have an application role and to
Object that may be present in the CCA. This is illustrated in
contain an application package that the terminal end System
desires to access.
figure 1, in which CO-l, CO-2, . . . CO-IJ represent a number
of different control objects present in the CCA. The
negotiation during establishment of a VT-association will This control Object is intended for use in S-mode
determine whether or not these will include a control Object (synchronous mode) Operation only. In S-mode Operation
of the type whose definition is given in this patt of ISO/IEC
such asymmetry is recognised by the VT Service in
ISP 11185.
accordance with 19.3.2 of ISO 9040. One VT-user is
designated as the Terminal VT-User, the other as the
The CCA is structured by the Virtual Terminal Service into a Application VT-User, and the two do not have equal access
number of components. For a control Object the Data to the functions of the VT Service.
0 ISO/IEC ISO/IEC ISP 11185-11: 1994(E)
A control Object of the type defined in this part of lSO/lEC ISP given in this part of lSO/IEC ISP 11185 is expressed in terms
of this model.
11185 is a Field Entry Pilot Control Object (FEPCO) as
defined in 20.3.5 of ISO 9040. The content of a FEPCO is an
Esch VTPM is permitted to store updates to its CCA before
array of records known as Field Entry Pilot Records (FEPRs)
onward delivery, in accordance with the data transfer
that may be referenced by a Field Definition Record (FDR).
mechanisms of annex A of ISO 9041-1. These mechanisms
Such reference determines reactions that should occur in
permit storage both for updates that result from the reception
response to specified events that may occur during data
of Service primitives and for those that result from the
entry. Provision is available for reactions to be conditional on
reception of protocol elements. The combined effect of these
the internal state of the VT-user at the time that the event
mechanisms in both VTPMs is to implement the delivery
occurs.
control mechanisms of ISO 9040. But the effect of such
storage is that the content of the two CCAs may differ from
The definition of a FEPCO type specifies the events that it
one another and that neither need correspond to the CCA of
recognises and the conditions and reactions which may be
the VT Service model. The CCA of each VTPM should
used in the construction of a FEPR. The event definitions
properly be regarded as an incompletely updated copy of the
may make use of properties of a field, including Validation
true CCA of the VT service-provider.
rules for data entry, that are determined by one or more Field
Entry Instruction COS (FEICOs) present in the VTE and
For certain types of control Object the abstract Syntax of ISO
referenced by the FDR of the field. A FEICO type suitable for
9041-1 does not provide a complete specification for the
use with the event definitions of this FEPCO type is defined
representation of CO update operations. This arises where
in ISO/IEC ISP 11185-9.
the abstract Syntax of ISO 9041-1 makes use of an ASN.1 any
type, or where symbolic values have to be encoded in terms
The reactions permitted by a FEPCO may be recursive in that
of an ASN.1 integer type. Control Object type definitions are
they may include the generation of further events to be
required by ISO/IEC 9834-5 to provide the necessary
processed in accordance with other FEPRs. These features
refinement of the abstract Syntax.
permit powerful local processing capabilities to be specified
by an Application VT-user for Operation by the Terminal VT-
NOTE 2 - Since an abstract Syntax is made available for use
user without further confirmation. through its inclusion in a presentation context, and since the
Presentation service-provider has no knowledge of control Object
type definitions, in principle the VT-users provide the Presentation
The VT service-provider may store updates received from
service-provider with these refinements to the abstract Syntax through
one VT-user before delivery to the peer VT-user in
local management procedures. Whether or not this is necessary in
accordance with the delivery control mechanisms of
practice depends on the configuration of the implernentations
clause 24 of ISO 9040. So although the model of the
concerned.
VT Service is expressed in terms of a Single shared CCA, at
any instant the various elements of the two communicating
end Systems may have differing knowledge of its current 2 Normative references
content.
The following documents contain provisions which, through
reference in this text, constitute provisions of this part of
Terminal Ap IkatSon
en CP System
end System lSO/lEC ISP 11185. At the time of publication, the editions
indicated were valid. All documents are subject to revision,
and Parties to agreements based on this International
VT-user 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
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 CClll maintains
published editions of its current Recommendations.
r
ISO 7498:1984, Information processing Systems - Open
v-r Protocol
Systems Interconnection - Basic Reference Model.
ISO/TR 8509: 1987, Information processing Systems - Open
Systems Interconnection - Service conventions.
Figure 2 - Control objects in the VT Protocol model
ISO 8822:1988, Information processing Systems - Open
Systems Interconnection - Connection orientedpresentation
This Variation in knowledge extends within the VT service-
Service definition.
provider itself. The Virtual Terminal Protocol specification
given in ISO 9041-1 models the VT service-provider in terms
lSO/IEC 8824: 1990, Information technology - Open Systems
of protocol exchange between two Virtual Terminal Protocol Interconnection - Specification of Abstract Syntax Notation
Machines (VTPMs), each with its own CCA. The CCA of
One (ASN. 1).
each VTPM is updated both by Service primitives received
from its own VT-user and by protocol elements received from ISO 9040: 1990, Information technology - Open Systems
the peer VTPM. Corresponding Service primitives and Interconnection - Virtual Terminal Basic Class Service.
protocol elements are issued by the VTPM to provide
ISO 9041-1: 1990, Information technology - Open Systems
notification of changes to the content of its CCA. This is
illustrated in figure 2 in the context of the asymmetric end Interconnection - Vittual Terminal Basic C/ass Protocol-
Systems described above. The control Object type definition Part 1: Specification.
0 ISO/IEC
ISO/IEC ISP 1118511: 1994(E)
ISO/lEC 9041-2: 1993, Information technology - Open c) control Object;
Systems Interconnection - Virtual Terminal Basic Class
Protocol - Part 2: Protocol lmplementation Conformance d) device Object;
Statement (PICS) Proforma.
e) display Object;
lSO/IEC 9834-1: 1993, Information technology - Open
9 field;
Systems Interconnection - Procedures for the Operation of
OS/ Registration Authorities - Part 1: Genera/ Procedures.
g) Field Definition Record;
lSO/IEC 9834-5: 1991, Lqformation technology - Open
h) Field Entry Condition;
Systems Interconnection - Procedures for the Operation of
OS/ Registration Authorities - Part 5: Register of VT Control
Field Entry Event;
Object Definitions.
j) Field Entry Instruction;
lSO/lEC TR 10000-1: 1992, Information technology -
Framework and taxonomy of International Standardized
k) Field Entry Instruction Record;
Profiles - Part 1: Framework (second edition).
Field Entry Pilot Record;
lSO/IEC TR 10000-2: 1992, Information technology -
1)
Framework and taxonomy of International Standardized
m) Field Entry Reaction;
Profiles - Part 2: Taxonomy of Profi/es (second edition).
n) logical pointer;
3 Definitions
o) Object updating device;
For the purposes of this part of lSO/IEC ISP 11185 the
p) primary attribute;
following definitions apply.
q) rendition attribute;
3.1 General OSI terminology
r) S-mode;
3.1 .l This part of lSO/IEC ISP 11185 makes use of the
following terms defined in ISO/TR 8509:
s) secondary attribute;
a) Service primitive;
t) VT-association;
b) service-provider.
u) VT-environment (VTE);
3.1.2 This part of lSO/IEC ISP 11185 makes use of the
v) Vb-User;
following terms defined in ISO 8822:
w) mE-Parameter;
a) abstract Syntax;
x) VTE-Profile;
b) presentation context.
y) VTE-Profile argument.
3.1.3 This part of lSO/IEC ISP 11185 makes use of the
following terms defined in lSO/IEC 8824:
3.2.2 This part of ISO/IEC ISP 11185 makes use of the
following term defined in ISO 9041-1:
a> any typei
protocol element.
null type;
b)
3.3 Terminology of VT-user structure
c) Object descriptor type;
d) Object identifier. 3.3.1 device control store: A conceptual store containing
abstract objects which represent aspects of the internal state
3.1.4 This part of ISO/IEC ISP 11185 makes use of the of the VT-user that are not associated with a specific Object
following terms defined in ISO/IEC 9834-1: updating device.
3.3.2 device Status store: A conceptual store containing
a) registration;
abstract objects which represent aspects of the state of a
specific Object updating device.
b) registration-hierarchical-name.
3.3.3 external CCA: A conceptual copy of the CCA
3.2 Terminology of VT base Standards
maintained by a VT-user which takes account of all update
operations that either have been received from, or have been
3.2.1 This part of lSO/IEC ISP 11185 makes use of the
issued to, the VT service-provider.
following terms defined in ISO 9040:
3.3.4 interne1 CCA: A conceptual copy of the CCA
a) array element;
maintained by a VT-user which takes account of all update
operations that either have been received from the VT
b) Character-repertoire;
0 ISO/IEC
ISO/IEC ISP 11185-11: 1994(E)
service-provider or have been accepted from Object updating 3.4.10 Signal event: An atomic event with an associated
devices. Its content may differ from that of the external CCA integer Parameter that may occur for control purposes during
when controlled data entry is in use. In these circumstances data entry by a VT-User.
it takes account of accepted update operations that have not
yet been issued to the VT service-provider. 3.5 Definitions of value types and properties
3.3.5 local action function: An abstract Object within the 3.5.1 Character: An item that is either a qualified Character
device control store that associates a local action Operation, or an unqualified Character.
possibly null, with each integer value.
3.5.2 Character-string: An item that is either ualified
aq
3.3.6 local action operatio n: An Operation that updates
Character-string or an unq ualified Character-string
a device Status st0 re or device control store.
the content of
3.5.3 local act ion spec ifier: An item that references eith ler
3.3.7 logical entry location: An abstract Object within a
a specific integer value or the value of the current Signal.
device Status store, containing a logical address as defined
in 13.1.3 of ISO 9040.
3.5.4 qualified Character: An unqualified Character
together with a rendition qualifier.
3.4 Terminology of controlled data entry
3.5.5 qualified Character-string: An unqualified character-
3.4.1 activated (of an FEPR): The state of an FEPR in
string together with a rendition qualifier; such a string also
which an event has occurred that is referenced by its FEE,
has a natura1 interpretation as a sequence of qualified
the conditions referenced by its set of FECs are all satisfied,
characters.
and its sequence of FERs is performed.
3.5.6 rendition qualifier: A specification of a value for
3.4.2 current Signal: An abstract Object within the device
each rendition attribute. Esch value may, but need not,
control store that contains an integer value stored by the
be specified explicitly. Values that are not specified
event processing function.
explicitly take dynamic default values that are determined
The first choice default is the
at the time of access.
3.4.3 event processing: A function that generates
field modal attribute value defined in 13.1.3.2 of ISO
reactions dependent on the Field Definition Record of a field
9040. A first choice default value of “null” is resolved as
when specified events occur during the entry of data into the
specified in 19.2.2.1 of ISO 9040 for the LOGICAL-TEXT
field.
update Operation.
3.4.4 free field: A field with a content that is subject to
3.5.7 unqualified Character: A primary attribute value
The Field Definition
update by Object updating devices.
together with a value for the Character-repertoire secondary
Record determines whether or not a field is a free field.
attribute.
3.4.5 input-Status: An abstract Object within the device
3.5.8 unqualified Character-string: A sequence of
control store that takes a symbolic value from the set
unqualified characters that all have the same value for the
( “allowed ”, “not allowed ”). When the value is “not allowed”
Character-repertoire secondary attribute.
then Object updating devices are not permitted to add data to
any data buffers that may be maintained by the VT-User; all
4 Abbreviations
actions of such devices shall be discarded. The initial value
of this Object is “allowed” and it is reset to this value when
For the purposes of this part of ISO/lEC ISP 11185 the
WAVAR is received by the VT-user concerned.
following abbreviations apply.
3.4.6 input Validation: A function applied to test the
AOW OSI Asia-Oceania Workshop;
validity of display Object update requests that are generated
EWOS European Workshop for Open Systems;
by an Object updating device and that use the logical pointer.
OIW OSE Implementors Workshop;
The function is applied before the requested updates are
OSE Open Systems Environment.
applied to the internal CCA. A Validation failure may result in
a Field Entry Event and may Cause an update request to be
All other abbreviations used are defined in ISO/IEC
discarded.
TR 10000-1 or ISO 9040.
3.4.7 linked (of an FEIR or FEPR): Assignment of the
semantic properties of an FEIR or FEPR to a particular field
5 Principles of conformance to VT Profiles
by reference to that FEIR or FEPR in the Field Definition
Record of that field.
An implementation of the Virtual Terminal Protocol conforms
to an FVPnn Profile that defines a control Object type if the
A function that may be applied
3.4.8 output Validation:
protocol implementation is capable of sending and receiving
to test the validity of the content of a field as maintained by
PDUs corresponding to all update operations permitted for
the internal CCA before updates to the content of that field
that CO type.
are issued to the VT service-provider, A Validation failure may
result in a Field Entry Event but it cannot Cause any updates
Conformance of a protocol implementation to an FVT2nn
to be discarded.
Profile does not place requirements on the ability of the
3.4.9 protected field: A field with a content that is not implementation to negotiate the presence in the CCA of an
subject to update by Object updating devices. The Field instance of this CO type. Such requirements fall within the
scope of conformance to an FVTlnn Profile that specifies a
Definition Record determines whether or not a field is a
protected field. VTE-Profile.
0 ISO/IEC
ISO/IEC ISP 11185-11: 1994(E)
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.l 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
does not assign any other of
This register form to the name
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 Directory 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(16) country-name }.
PICS proforma provided in ISO/IEC 9041-2. Annex A of this
part of ISO/IEC ISP 11185 provides an ISPICS Requirements
List (IPRL) for the Profile FVT232 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.l Object descriptor type assigned to
conformance to this Profile.
this register entry is:
“First harmonized FEPCO for use by Paged VTE-profiles ”.
6 Entry number
The remaining clauses of this part of lSO/lEC ISP 11185
11 CO Parameters
provide the entry for the Paged FEPCO No.1 in the
International Register of VT Control Object Type Definitions.
This CO type presumes S-mode Operation in which one VT-
The entry is structured in accordance with the requirements
user is designated as the Terminal VT-user and the other as
of lSO/IEC 9834-5. These requirements specify that this
the Application VT-user in accordance with 19.3.2 of ISO
International Register shall consist of a number of sub-
9040.
registers, each corresponding to a major classification of VT
Control Object.
This register entry specifies the following values for VTE-
Parameters of this control Object type:
This entry is the second in the sub-register for Field Entry
Pilot Control Objects. This register assigns it the entry
CO-structure: “non-parametric”
number:
CO-access: takes the same value as the CO-
access VTE-Parameter for the FDCO.
FEPCO-2.
CO-priority : “normal”
CO-trigger: “not selected”
7 Name of sponsoring authority
The CO-access VTE-Parameter for the FDCO, and thus also
for this FEPCO, should be assigned the value that permits
This entry is sponsored by the European Workshop for Open
access only by the VT-user with the application role. This
Systems (EWOS).
value will depend on whether the VT-association was initiated
by the terminal or application end System.
8 Date
NOTE - A Single VTE-Profile argument may be used to assign
values to the CO-access VTE-Parameter for all control objects in the
The date of Submission of this proposal was 1992-09-02. CCA that presume an asymmetric assignment of terminal and
application roles to the two communicating end Systems.
9 Identifier
12 CO values, Syntax and semantics
The name assigned to an information Object by an
International Register is required by ISO/IEC 9834-1 to be a 12.1 The VT-user model
registration-hierarchical-name. A registration-hierarchical-
12.1.1 The semantic definition of this FEPCO is based on
name may have more than one form. The permitted forms
the structured model of the VT-user of the terminal end
include an ASN.l Object identifier as defined in lSO/IEC 8824
System that is illustrated in figure 3. This model is intended
and a relative distinguished name as defined in ISO/IEC
solely to assist the process of definition. lt is not intended to
9594-2.
provide a model for implernentations. The requirement upon
In accordance with A.4 of ISO/IEC 9834-5, this register VT-user implernentations is only that their external behaviour
assigns the following Object identifier form for the name of corresponds to the external behaviour of the model.
this register entry:
Real devices may possess internal state information. For an
{ iso(1) Standard(O) 9834 vt-co-def(5) fepco(2) 2 } Object updating device this information determines, among
other things, the location of the DO array element that will be
In accordance with 20.1 .l of ISO 9040, this Object identifier updated by the next data input and the manner in which this
shall be used as the value of the CO-type-identifier VTE- location will be made known to the human user of the device.
Parameter for a control Object in Order to identify this register In the model, the state information is represented by the
0 ISO/IEC
ISO/IEC ISP 11185-11: 1994(E)
not contain both operations that use the display pointer and
those that use the logical pointer. Such macros assume
significance when controlled data entry is in use as defined
by 14.2 of ISO 9040, since it is the effect of a macro as a
whole and not that of any individual constituent item that is
considered by input Validation procedures.
’ Devlce
NOTE - In the example of the note in 12.1 .l , entry of a Single
Character at the keyboard during controlled data entry may generate
a Single indivisible macro consisting of the following items:
- a logical addressing Operation, if required, to set the logical
pointer to the current Position of the input cursor;
D0Vb
control
- a LOGICAL-TEXT Operation to make an appropriate entry
store
into the array element at this address;
r--l
Local
- a local action Operation to move the cursor Position to the
action
/ Inteiteal / /c ”c ”A ’i
final p osition of the Iogical pointer.
function
1 L-----J
Subsequent Character entries immediately after the first will then not
need to perform the first Step. If any entered Character is rejected by
the input Validation procedures of controlled data entry then use of
a macro ensures that the associated cursor movement also does not
Figure 3 - Structure of the terminal VT-user
take place.
During the processing of data from its Object updating
content of abstract objects hel d in ad evice stat us store.
devices, the VT-user may identify events that have a
There will be one device Status store for each real device.
significance in the semantics of objects present in the CCA.
Examples are Field Entry Events and termination-events as
- For an Object updating device that consists of a
NOTE
defined in 3.3.65 and 3.3.72 of ISO 9040 respectively. These
keyboard and display Screen, the above aspects of the state
events Cause actions determined by the semantics of these
information correspond to the location and Screen representation of
objects. These actions may result in the generation of Object
an input cursor. Movement of the input cursor does not need to
updates or of a ‘deliver’ Stimulus for issue to the VT service-
generate DO addressing operations until data is actually entered at
provider, but the event notification itself is not issued to the
the cursor location. The cursor location is thus internal state
information that is separate from the display pointer of the CCA. service-provider.
The VT-user processes data received both from its Object 12.1.3 When controlled data entry is in use, the VT-user
updating devices and from the VT service-provider. lt may
operates a local processing function that performs Validation
possess internal state information of its own that affects this
tests on DO update requests before they are issued to the VT
processing. Any such information is represented in the VT-
service-provider, Only those DO update requests that use
user model by abstract objects held in a device control store.
the logical pointer are subject to Validation. In accordance
with B.18.4 of ISO 9040, update requests that are accepted
The semantic definition of a control Object may include the
as valid are stored by the local processing function until
specification of one or more abstract objects that are to be
some specific action Causes their release. When release
maintained in a device Status store or the device control
occurs, the stored updates are not forwarded as a simple
store. In this way the implementation of a control Object may
queue. Instead, the effect on the DO of the stored updates
place requirements on, and may exert control over, the
is made available to the VT service-provider in accordance
capabilities of the real devices of the VT-User. The
with the transmission policy for the fields concerned; see
specification of such objects shall include any required rules
20.3.3.3 of ISO 9040.
that concern update access to these objects. Abstract
o
...