EN ISP 11185-10:1995

SLOVENSKI STANDARD
01-december-1997
Information technology - International Standardized Profiles FVT2nn - Virtual
Terminal Basic Class - Register of control object type definitions - Part 10: FVT231
- Forms FEPCO (Field Entry Pilot Control Object) No.1 (ISO/IEC ISP 11185-10:1994)
Information technology - International Standardized Profiles FVT2nn - Virtual Terminal
Basic Class - Register of control object type definitions - Part 10: FVT231 - Forms
FEPCO (Field Entry Pilot Control Object) No.1 (ISO/IEC ISP 11185-10:1994)
Informationstechnik - Internationale Profilnorm FVT2nn - Virtuelles Terminal Grundstufe -
Verzeichnis der Definitionen von Kontrollobjekttypen - Teil 10: FVT231 - Kontrollobjekt
zur Behandlung von Feldeingaben im Formatbetrieb Nr.1 (ISO/IEC ISP 11185-10: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
10: FVT231 - Formulaires FEPCO (Objet de commande pilote d'entrée de zone) no 1
(ISO/IEC ISP 11185-10:1994)
Ta slovenski standard je istoveten z: EN ISP 11185-10: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
lSO/IEC
STANDARDIZED ISP
PROFILE
11185-10
First edition
1994-10-01
Information technology - International
Standardized Profiles FVT2nn - Virtual
Terminal Basic Class - Register of control
Object type definitions -
Part 10:
FvT23 1 - Forms FEPCO (Field Entry Pilot
Control Object) No. 1
Technologies de I ’informa tion - Profils normalk& in terna tionaux
FW2nn - Classe de base de terminal virtuel - ßegistre de definitions
de type d ’objet de commande -
Partie IO: FVT.223 - Formulaires FEPCO (objet de commande pilote
d ‘entrde de Zone) no 1
ISO/IEC ISP 1118510: 1994(E)
Page
Contents
iii
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Scope .
1.1 General .
1.2 Position within the taxonomy .
1.3 Scenario .
2 Normative references . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . .
................................................ 4
3 Definitions
3.1 General OSI terminology .
........................... 4
3.2 Terminology of VT base standards
3.3 Terminology of VT-user structure .
.......................... 5
3.4 Terminology of controlled data entry
....................... 5
3.5 Definitions of value types and properties
4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Principles of conformance to VT Profiles . . . . . . . . . . . , . . , . . . . . . . . .
6 Entrynumber. 6
7 Name of sponsoring authority . . n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO Descriptor value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 CO Parameters . . . . . . . . . , . . , . . . . . . . . . . . , . . . . . . . . . . . . . . . . . .
12 CO values, Syntax and semantics 6
.............................
12.1 The VT-user model .
12.2 Local processing function .
12.3 FEPCO structure .
12.4 FEE definitions .
jl
12.5 FEC definitions .
12.6 FER definitions 12
.......................................
12.7 UpdateSyntax .
12.8 Initial Content 17
........................................
13 Additional information . , , . . . . . . . . . . . . . . . . . . . , . . . . . e . . , . . . . . 17
14 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
ANNEX A ISPICS Requirements List . 18
A.l Protocol requirements .
A.2 Profile-specific requirements . 18
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.
lSO/IEC Copyright Office l Case Postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
ii
0 ISO/IEC
ISO/IEC ISP 1118510: 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 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 ISO/IEC ISP 11185-10 was prepared with the
collaboration of
- OSI Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- Open Systems Environment Implementors Workshop (OMI).
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 ISO/IEC 9834. lt is issued in Parts, with
additional Parts being issued as further entries are added to the register. Esch patt is
prepared in accordance with an approval and maintenance process laid down by the
Special Group on Functional Standardization of lSO/lEC JTCI, Informatr ’on technology.
lSO/lEC ISP 11185 is issued under the general title Informati ’on technology -
International Standardized 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: M211, M212 - Sequenced and Unsequenced Application
Control Objects
Part 2: M213, M214 - Sequenced and Unsequenced Terminal Control
Objects
Application RIO Record Loading Control Object,
Part 3: M215, M216 -
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 Control Object
- Entry-Control Control Object
Part 7: M2110
Part 8: M22I - Forms FEICO (Field Entry Instruction Control Object) No.1
Part 9: M222 - Paged FEICO (Field Entry Instruction Control Object) No.1
Part IO: M23I - 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
- Waiting Time Control Object
Part 13: M2IiI
Part 14: M2112 - Printer Control Object
Part 15: M2113 - Field Definition Management Control Object
Part 16: M2114 - Terminal Signal Titles Control Object
Part 17: M2115 - Help Text Control Object
Annex A of this part of ISO/IEC ISP 11185 forms an integral patt of this International
Standardized Profile.
ISO/IEC ISP 11185-10: 1994(E) 0 ISO/IEC
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/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/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 (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 from a
control Object specification contained within the S-mode Forms VTE-Profile of the OIW
Stable Implementation Agreements, Version 3 (December 1989). 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 ISO/IEC ISP 11185-10: 1994(E)
International Standardized
Information technology -
Virtual Terminal Basic Class - Register
Profiles FVT2nn -
of control Object type definitions -
Part 10:
FVT231 - Forms 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 .l 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/lEC TR 10000-1. Such Profiles are divided into
a number of different classes and sub-classes. Two of these
- ISO/IEC 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/lEC 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/lEC 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.
- lSO/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 sf 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
(VTE-Profile), and of particular values for any arguments of
network and the application process, and may substantially
that VTE-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 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 Interchange
instance constitutes an F-Profile within the framework of
Format and Representation Profiles.
lSO/lEC 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
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-10: 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 senke-protider
- a=
1 for Basic Class VTE-profiles;
- a=
2 for Basic Class Control Objects;
~~
- a=
3 for Basic Class Assignment Types.
Values of a g reater than 3 are reserved for future Figure 1 - Confrol objects in the VT Service model
developments.
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
- 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 ISO/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.1 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 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
FVT231 - Forms 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
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
Communication Area (CCA) that is a conceptual part of the The control Object type defined in this part of lSO/IEC
VT service-provider. Information exchange is modelled by ISP 11185 assumes an asymmetry between the two
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
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
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
figure 1, in which CO-l, CO-2, . . . CO-n represent a number desires to access.
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 part of lSO/lEC
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/lEC ISO/IEC ISP 11185-10: 1994(E)
given in this part of ISO/IEC ISP 11185 is expressed in terms
A control Object of the type defined in this part of ISO/IEC ISP
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-8.
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 lSO/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
Ap lication
Terminal
en System
end System 8 lSO/IEC 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
VT-user A
Standardized Profile are warned against automatically
I
applying any more recent editions of the documents listed
W senke
Devices primitives below, since the nature of references made by ISPs to such
@E$
i
documents is that they may be specific to a particular edition.
Members of IEC and ISO maintain registers of currently valid
J L
I
International Standards and ISPs, and CCITT maintains
published editions of its current Recommendations.
r
ISO 7498:1984, Information processing Systems - Open
VI- 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 Abstact 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
notification of changes to the content of its CCA. This is ISO 9041-1 :1990, Information technology - Open Systems
illustrated in figure 2 in the context of the asymmetric end Interconnection - Virtual Terminal Basic Class Protocol-
Systems described above. The control Object type definition Part 1: Specification.
0 lSO/IEC
lSO/IEC ISP 1118540: 1994(E)
control Object;
lSO/IEC 9041-2: 1993, Information technology - Open
C>
Virtual Terminal Basic Class
Systems lnterconnection -
device Object;
Protocol - Part 2: Protocol lmplementation Conformance
d)
Statement (PICS) Proforma.
display Object;
e>
lSO/IEC 9834-1: 1993, Information technology - Open
field;
Systems Interconnection - Procedures for the Operation of
OS/ Registration Authorities - Part 1: General Procedures.
Field Definition Record;
9)
lSO/IEC 9834-5: 1991, Information technology - Open
Systems Interconnection - Procedures for the Operation of Field Entry Condition;
hl
OS/ Registration Authorities - Part 5: Register of VT Control
Field Entry Event;
Object Definitions.
.
Field Entry Instruction;
lSO/lEC TR 10000-1: 1992, Information technology -
1)
Framework and taxonomy of International Standardized
Field Entry Instruction Record;
Profiles - Part 1: Framework (second edition).
k)
Field Entry Pilot Record;
lSO/IEC TR 10000-2: 1992, Information technology -
I>
Framework and taxonomy of International Standardized
Field Entry Reaction;
Profiles - Part 2: Taxonomy of Profiles (second edition).
m>
logical pointer;
t-0
3 Definitions
Object updating device;
0)
For the purposes of this part of ISO/IEC ISP 11185 the
primary attribute;
following definitions apply. P>
rendition attribute;
3.1 General OSI terminology s>
S-mode;
3.1.1 This part of lSO/IEC ISP 11185 makes use of the
following terms defined in lSO/TR 8509:
secondary attribute;
S>
Service primitive;
VT-association;
t>
service-provider.
b)
VT-environment (VTE);
U)
3.1.2 This part of ISO/IEC ISP 11185 makes use of the
VT-User;
following terms defined in ISO 8822: V>
W-E-Parameter;
abstract Syntax; W
VTE-Profile;
presentation context.
XI
b)
VTE-Profile argument.
3.1.3 This part of lSO/IEC ISP 11185 makes use of the
Y>
following terms defined in lSO/lEC 8824:
3.2.2 This part of ISO/IEC ISP 11185 makes use of the
following term defined in ISO 9041-1:
4 any tYPei
a) protocoi element.
null type;
b)
Object descriptor type; 3.3 Terminology of VT-user structure
C>
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 lSO/IEC ISP 11185 makes use of the of the VT-user that are not associated with a specific Object
following terms defined in lSO/lEC 9834-1: updating device.
registration; 3.3.2 device Status store: A conceptual store containing
abstract objects which represent aspects of the state of a
registration-hierarchical-name. specific Object updating device.
3.2 Terminology of VT base Standards 3.3.3 external CCA: A conceptual copy of the CCA
maintained by a VT-user which takes account of all update
3.2.1 This patt of lSO/IEC ISP 11185 makes use of the operations that either have been received from, or have been
following terms defined in ISO 9040:
issued to, the VT service-provider,
array element; 3.3.4 internal CCA: A conceptual copy of the CCA
maintained by a VT-user which takes account of all update
Character-repertoire; operations that either have been received from the VT

0 ISO/lEC
ISO/IEC ISP 11185-10: 1994(E)
service-provider or have been accepted from Object updating the internal CCA before updates to the content of that field
devices. Its content may differ from that of the external CCA are issued to the VT service-provider. A Validation failure may
when controlled data entry is in use. In these circumstances result in a Field Entry Event but it cannot Cause any updates
it takes account of accepted update operations that have not to be discarded.
yet been issued to the VT service-provider,
3.4.10 protected field: A field with a content that is not
local action function: An abstract Object within the
3.3.5 subject to update by Object updating devices. The Field
device control store that associates a local action Operation, Definition Record determines whether or not a field is a
possibly null, with each integer value. protected field.
3.3.6 local action Operation: An Operation that updates
3.4.11 selectable field: A field for which the device control
a device Status store or device contr ‘01 store.
the content of store contains an associated binary state variable that takes
a value from the set ( “selected ”, “not selected ”). The Field
3.3.7 logical entry location: An abstract Object within a Definition Record determines whether or not a field is a
device Status store, containing a logical address as defined selectable field.
in 13.1.3 of ISO 9040.
3.4.12 Signal event: An atomic event with an associated
3.4 Terminology of controlled data entry integer Parameter that may occur for control purposes during
data entry by a VT-User.
3.4.1 activated (of an FEPR): The state of an FEPR in
which an event has occurred that is referenced by its FEE, 3.5 Definitions of value types and properties
the conditions referenced by its set of FECs are all satisfied,
3.5.1 Character: An item that is
and its sequence of FERs is performed. either a qualified Character
or an unqualified Character.
3.4.2 current Signal: An abstract Object within the device
control store that contains an integer value stored by the 3.5.2 Character-string: An item that is either a qualified
event processing function. Character-string or an unqualified Character-string.
3.5.3 local action specifier: An item that references
3.4.3 event processing: A function that generates
reactions dependent on the Field Definition Record of a field either a specific integer value or the value of the current
Signal.
when specified events occur during the entry of data into the
field.
3.5.4 qualified Character: An unqualified Character
together with a rendition qualifi
3.4.4 field-waiting-time: A value associated with a count- er.
down timer that is maintained for a particular field in a device
3.5.5 qualified Character-string: An unqualified character-
Status store. lt provides the value to which the timer is reset.
string together with a rendition qualifier; such a string also
Operation of such a timer is under the control of the FEICOs
has a natura1 interpretation as a sequence of qualified
present in the CCA. Expiry of the timer is an identifiable
characters.
event that may be recognised by the event processing
function.
3.5.6 rendition qualifier: A specification of a value for
each rendition attribute. Esch value may, but need not, be
3.4.5 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.6 input-Status: An abstract Object within the device
value of “null” is resolved as specified in 19.2.2.1 of ISO 9040
control store that takes a symbolic value from the set
for the LOGICAL-TEXT update Operation.
( “allowed ”, “not allowed ”). When the value is “not allowed”
then Object updating devices are not permitted to add data to
3.5.7 unqualified Character: A Primat-y attribute value
any data buffers that may be maintained by the VT-User; all
together with a value for the Character-repertoire secondary
actions of such devices shall be discarded. The initial value
attribute.
of this Object is “allowed” and it is reset to this value when
WAVAR is received by the VT-user concerned.
3.5.8 unqualified Character-string: A sequence of
3.4.7 input Validation: A function applied to test the unqualified characters that all have the same value for the
validity of display Object update requests that are generated Character-repertoire secondary attribute.
by an Object updating device and that use the logical pointer.
The function is applied before the requested updates are 4 Abbreviaticms
applied to the internal CCA. A Validation failure may result in
a Field Entry Event and may Cause an update request to be For the purposes of this patt of ISO/IEC ISP 11185 the
discarded. following abbreviations apply.
3.4.8 linked (of an FEIR or FEPR): Assignment of the AOW OSI Asia-Oceania Workshop;
semantic properties of an FEIR or FEPR to a particular field EWOS European Workshop for Open Systems;
OIW OSE Implementors Workshop;
by reference to that FEIR or FEPR in the Field Definition
Record of that field. OSE Open Systems Environment.
3.4.9 output Validation: A function that may be applied All other abbreviations used are defined in lSO/IEC
to test the validity of the content of a field as maintained by TR 10000-1 or ISO 9040.
0 ISO/IEC
lSO/IEC ISP 11185-10: 1994(E)
include an ASN.l Object identifier as defined in lSO/IEC 8824
5 Principles of conformance to VT Profiles and a relative distinguished name as defined in ISO/IEC
9594-2.
An implementation of the Virtual Terminal Protocol conforms
to an FVT2nn Profile that defines a control Object type if the In accordance with A.4 of ISO/IEC 9834-5, this register
protocol implementation is capable of sending and receiving assigns the following Object identifier form for the name of
PDUs corresponding to all update operations permitted for this register entry:
that CO type.
{ iso(1) Standard(O) 9834 vt-co-def(5) fepco(2) 1 }
Conformance of a protocol implementation to an FVT2nn
Profile does not place requirements on the ability of the
In accordance with 20.1 .l of ISO 9040, this Object identifier
implementation to negotiate the presence in the CCA of an
shall be used as the value of the CO-type-identifier VTE-
instance of this CO type. Such requirements fall within the
Parameter for a control Object in Order to identify this register
scope of conformance to an FVTlnn Profile that specifies a
entry as the source ’of the information structure and semantic
mE-Profile.
content of the control Object. This Object identifier shall also
be used to identify the ASN.l module specified within this
A System that includes an implementation of the VT Protocol
register entry as the Source of abstract Syntax by which
may be claimed to conform also to an AVTnn Profile.
update operations on this CO are specified within the VT
Conformance to an AVTnn Profile may require that CO
protocol of ISO 9041-1.
update operations received by the VT-user component of the
System are interpreted in accordance with the semantics
This register does not assign any other form to the name of
defined within the appropriate CO type definition.
this entry.
Conformance to CO semantics is not within the scope of
conformance to any FVTnnn Profile. NOTE - By ISO/IEC 9834-1 a relative distinguished name for the
purposes of the OSI Directory may only be assigned together with an
The conformance requirements of the Virtual Terminal Object identifier when the Object identifier form is generated under
the arc { joint-iso-ccitt(2) country(16) country-name }.
Protocol are specified in clause 13 of ISO 9041-1. The
supplier of a protocol implementation which is claimed to
conform to ISO 9041-1 is required to complete a copy of the
10 Descriptor value
PICS proforma provided in ISO/IEC 9041-2. Annex A of this
part of lSO/lEC ISP 11185 provides an ISPICS Requirements
The value of the ASN.1 Object descriptor type assigned to
List (IPRL) for the Profile FVT231 specified herein. This IPRL
this register entry is:
specifies constraints on the answers that may be given in the
completed PICS for a protocol implementation that Claims
“First harmonized FEPCO for use by Forms VTE-profiles ”.
conformance to this Profile.
11 CO Parameters
6 Entry number
This CO type presumes S-mode Operation in which one VT-
The remaining clauses of this patt of lSO/IEC ISP 11185
user is designated as the Terminal VT-user and the other as
provide the entry for the Forms FEPCO No.1 in the
the Application VT-user in accordance with 19.3.2 of ISO
International Register of VT Control Object Type Definitions.
9040.
The entry is structured in accordance with the requirements
of lSO/lEC 9834-5. These requirements specify that this
This register entry specifies the following values for VTE-
International Register shall consist of a nunaber of sub-
Parameters of this control Object type:
registers, each corresponding to a major classification of VT
Control Object.
CO-structure: “non-parametric”
CO-access: takes the same value as the CO-
This entry is the first in the sub-register for Field Entry Pilot
access VI-E-Parameter for the FDCO.
Control Objects. This register assigns it the entry number:
CO-priority: “normal”
CO-trigger: “not selected”
FEPCO-1.
The CO-access VTE-Parameter for the FDCO, and thus also
7 Name of sponsoring authority for this FEPCO, should be assigned the value that permits
access only by the VT-user with the application role. This
This entry is sponsored by the European Workshop for Open value will depend on whether the VT-association was initiated
Systems (EWOS). by the terminal or application end System.
NOTE - A Single VTE-Profile argument may be used to assign
8 Date
values to the CO-access VTE-Parameter for all control objects in the
CGA that presume an asymmetric assignment of terminal and
The date of Submission of this proposal was 1992-09-02. 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 12.1 The VT-user model
International Register is required by ISO/IEC 9834-1 to be a
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
0 ISO/lEC
ISO/IEC ISP 111854 0: 1994(E)
System that is illustrated in figure 3. This model is intended Status stores and the device control store. Only the Object
solely to assist the process of definition. lt is not intended to updates may be issued to the VT service-provider.
provide a model for implernentations. The requirement upon Communication with the VT service-provider uses a model of
VT-user implernentations is only that their external behaviour update queues and priority handling that is specified in 24.5
corresponds to the external behaviour of the model. of ISO 9040. Local action operations have an effect that is
purely internal to the VT-User.
Real devices may possess internal state information. For an
A sequence of DO updates and local action operations may
Object updating device this information determines, among
be generated by a Single action of an Object updating device.
other things, the location of the DO array element that will be
The VT-user may treat such a sequence as an indivisible
updated by the next data input and the manner in which this
macro Operation, provided that a Single macro Operation shall
location will be made known to the human user of the device.
not contain both operations that use the display pointer and
In the model, the state information is represented by the
those that use the logical pointer. Such macros assume
content of abstract objects held in a device Status store.
significance when controlled data entry is in use as defined
There will be one device Status store for each real device.
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.
VT-user A ’
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:
- alog ical addressing Operation, if required, to set the logical
pointer to the current Position of the input cursor;
entry
a LOGICAL-TEXT Operation to make an appropriate
into the array element at this address;
a local action Operation to move the cursor Position to the
final positio n of the logical pointer.
store
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
take place.
During the processing of data from its Object updating
Figure 3 - Structure of the terminal VT-user
devices, the VT-user may identify events that have a
significance in the semantics of objects present in the CCA.
Examples are Field Entry Events and termination-events as
NOTE - For an Object updating device that consists of a
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 t
...