ETSI ETS 300 498-2 ed.1 (1998-04)

SLOVENSKI STANDARD
01-december-2003
Odprta arhitektura dokumentov (ODA) – Komunikacijske storitve ODA – 2. del:
Združeno sinhronizirano urejanje, združeno prikazovanje in gledanje dokumentov
Open Document Architecture (ODA); ODA communication services; Part 2: Joint
synchronous editing, joint document presentation/viewing
Ta slovenski standard je istoveten z: ETS 300 498-2 Edition 1
ICS:
35.240.20 Uporabniške rešitve IT pri IT applications in office work
pisarniškem delu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 498-2
TELECOMMUNICATION April 1998
STANDARD
Source: MTA Reference: DE/MTA-042023
ICS: 33.020
Key words: ODA, CONF, multipoint, generic, service
Open Document Architecture (ODA);
ODA communication services;
Part 2: Joint synchronous editing,
joint document presentation/viewing
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

Page 2
ETS 300 498-2: April 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 498-2: April 1998
Contents
Foreword .7
Introduction.7
1 Scope .8
2 Normative references.8
3 Definitions and abbreviations .9
3.1 Definitions .9
3.2 Abbreviations .9
4 Introduction to document communication complex services.10
4.1 Classification of complex services.11
4.2 Joint Synchronous Editing (SE) .12
4.2.1 Description .12
4.2.2 Service construction rules .13
4.3 Joint document Presentation/Viewing (PV).16
4.3.1 Joint document Presentation/viewing with 1 presenter (PV1).16
4.3.1.1 Description.16
4.3.1.2 Service construction rules .17
4.3.2 Joint document Presentation/viewing with n presenters (PVn) .17
4.3.2.1 Description.17
4.3.2.2 Service construction rules .18
5 Document aspects concerning the SE and PV complex services .19
5.1 Non-ODA documents.19
6 Communication aspects concerning the SE and PV complex services.19
6.1 Combined DTAM-DM and DTAM-TK (DTAM-DM/TK) .19
6.1.1 Description .19
6.1.2 Services, protocols and profiles .19
6.1.3 Use for document communication .20
6.2 Multipoint Communication Service (MCS) .20
6.2.1 Description .20
6.2.2 Services, protocols and profiles .20
6.2.3 Use for document communication .20
6.3 Generic Conference Control (GCC).21
6.3.1 Description .21
6.3.2 Services, protocols and profiles .21
6.3.3 Use for document communication .21
7 Components and design rules for the SE and PV complex services.21
7.1 Definition of document related service attributes.22
7.1.1 The service attribute "document location".23
7.1.2 The service attribute "document copies".24
7.1.3 The service attribute "document access rights" .24
7.1.4 The service attribute "store access rights" .24
7.1.5 The service attribute "document format".24
7.1.6 The service attribute "functionality level".24
7.1.7 The service attribute "document access order".24
7.2 Definition of communication related service attributes .25
7.2.1 The service attribute "number of communicating entities" .25
7.2.2 The service attribute "communication type" .26
7.2.3 The service attribute "communication module".26
7.2.4 The service attribute "association" .26

Page 4
ETS 300 498-2: April 1998
7.2.5 The service attribute "synchronization". 27
7.2.6 The service attribute "conference type" . 27
7.3 Definition of implementation related service attributes. 27
7.3.1 The service attribute "basic services". 27
7.3.2 The service attribute "static information" . 28
7.4 Rules for the formal definition of Complex Services . 28
7.4.1 Rules and notation for the assignment of values to the document related
service attributes. 29
7.4.2 Rules and notation for the assignment of values to the communication
related service attributes. 30
7.4.3 Rules and notation for the assignment of values to the implementation
related service attributes. 31
7.4.4 Rules and notation for the selection of the communication modules . 31
7.4.5 Application rules . 32
8 Formal definition of the SE complex service .32
8.1 Document related service attributes. 32
8.2 Communication related service attributes. 33
8.3 Implementation related service attributes . 33
8.4 Selection of communication modules . 34
8.5 Application rules. 34
8.5.1 Application rules when using DTAM-DM/TK. 34
8.5.1.1 Case 1: "association" = 'one-to-one' and "conference
type" = 'fixed' . 35
8.5.1.2 Case 2: "association" = 'one-to-several' and "conference
type" = 'fixed' . 36
8.5.1.3 Case 3: "association" = 'one-to-several' and "conference
type" = 'flexible'. 39
9 Formal definition of the PV1 complex service . 41
9.1 Document related service attributes. 42
9.2 Communication related service attributes. 42
9.3 Implementation related service attributes . 42
9.4 Selection of communication modules . 43
9.5 Application rules. 43
9.5.1 Application rules when using DTAM-DM/TK. 43
9.5.1.1 Case 1: "association" = 'one-to-one' and "conference
type" = 'fixed' . 43
9.5.1.2 Case 2: "association" = 'one-to-several' and "conference
type" = 'fixed' . 45
9.5.1.3 Case 3: "association" = 'one-to-several' and "conference
type" = 'flexible'. 47
10 Formal definition of the PVn complex service .49
10.1 Document related service attributes. 49
10.2 Communication related service attributes. 49
10.3 Implementation related service attributes . 49
10.4 Selection of communication modules . 50
10.5 Application rules. 50
10.5.1 Application rules when using DTAM-DM/TK. 51
10.5.1.1 Case 1: "association" = 'one-to-one' and "conference
type" = 'fixed' . 51
10.5.1.2 Case 2: "association" = 'one-to-several' and "conference
type" = 'fixed' . 52
10.5.1.3 Case 3: "association" = 'one-to-several' and "conference
type" = 'flexible'. 55
Annex A (normative): ASN.1 specification. 58
Annex B (informative): Implementation guidelines .60
B.1 General implementation guidelines . 60
B.1.1 Quality of Service (QoS). 60

Page 5
ETS 300 498-2: April 1998
B.1.2 Security .60
B.1.3 Handling documents in non-ODA formats .60
B.1.4 Complex services token distribution .61
B.1.5 Steps co-ordination in MCS .61
B.1.6 Alternative implementation to the CSS .61
B.1.7 Leaving the session .62
B.1.8 Handling of error situations.62
B.2 Specific implementation hints for the SE complex service.62
B.3 Specific implementation hints for the PV1 complex service.62
B.4 Specific implementation hints for the PVn complex service.63
Annex C (informative): Bibliography.64
C.1 Document architectures .64
C.2 Communication architectures.64
History.66

Page 6
ETS 300 498-2: April 1998
Blank page
Page 7
ETS 300 498-2: April 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Multimedia Terminals and
Applications (MTA) Project of the European Telecommunications Standards Institute (ETSI).
This ETS consists of 2 parts as follows:
Part 1: "Basic services";
Part 2: "Joint synchronous editing, joint document presentation/viewing".
Transposition dates
Date of adoption of this ETS: 20 March 1998
Date of latest announcement of this ETS (doa): 31 July 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 January 1999
Date of withdrawal of any conflicting National Standard (dow): 31 January 1999
Introduction
This ETS specifies document communication services to be provided on top of existing base standards or
profiles, giving constraints on them and rules on how to use and combine them.
ETSI Technical Report (ETR) ETR 081 [7] has been taken into consideration as one of the sources for
this ETS. The purpose of ETR 081 [7] was to define the scope and priorities for the initialization of
standardization in the area of Open Document Architecture (ODA) communication services.

Page 8
ETS 300 498-2: April 1998
1 Scope
The Open Document Architecture (ODA) base standard and associated profiles specify the means to
represent and interchange complex documents.
Communication base standards and associated profiles, specifying interchange, remote manipulation and
management of documents at the application layer of the Open Systems Interconnection (OSI) reference
model, have also been specified, as Document Transfer And Manipulation (DTAM) and Document Filing
and Retrieval (DFR).
Standards concerning multipoint communication and multimedia conferencing applications
(ITU-T T.120 series of recommendations, see bibliography) are being specified to support the needs of a
rapidly growing telecommunication market.
Standardizing document communication services will help implementors and service providers to extend
the use and acceptance of these services in Europe. Furthermore, the standardization of document
communication service profiles will facilitate interworking.
This ETS specifies document communication services to be provided on top of existing base standards or
profiles, giving constraints on them and rules on how to use and combine them.
The first part of this ETS specifies basic services, such as storing, retrieval, manipulation, pointing or
token-interchange. Some of these basic services can be used as stand-alone services, but all of them are
candidates to build more complex services, such as joint synchronous editing and joint document
presentation/viewing.
This second part of the ETS specifies complex document communication services that are built on top of
the basic ones.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
For the purposes of this part of the ETS, all the references in ETS 300 498-1 [1] apply. In addition, the
following references apply:
[1] ETS 300 498-1 (1996): "Open Document Architecture (ODA); ODA
communication services; Part 1: Basic services".
[2] ITU-T Recommendation T.122 (1993): "Multipoint communication service for
audiographics and audiovisual conferencing service definition".
[3] ITU-T Recommendation T.125 (1994): "Multipoint communication service
protocol specification".
[4] ITU-T Recommendation T.124 (1995): "Generic Conference Control".
[5] ISO/IEC 10031-2 (1991): "Information technology - Text and office systems -
Distributed-office-applications model - Part 2: Distinguished-object-reference
and associated procedures".
[6] ISO/IEC 9594 (1988): "The Directory".
[7] ETR 081 (1993): "Open Document Architecture (ODA); Identification of
characteristics Integrated Services Digital Networks (ISDN) for ODA
applications".
Page 9
ETS 300 498-2: April 1998
[8] ITU-T Recommendation T.435 (1995): "Document Transfer And Manipulation
(DTAM) - Services and protocols - Abstract service definition and procedures for
confirmed document manipulation".
[9] ITU-T Recommendation T.436 (1995): "Document Transfer and Manipulation
(DTAM) - Services and protocols - Protocol specifications for confirmed
document manipulation".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, all the definitions in ETS 300 498-1 [1] apply. In addition, the following
definitions apply:
central service server: A server that controls the complex service token and centralizes the distribution
of the document updates for a specific complex service. It is used to simplify the communication
mechanism, since only one communication link between a user and the server is needed.
complex service session: The whole of the processes and events in the time interval between
initialization and termination of an application implementing a complex service.
initiator: The user that initiates a complex service session.
master copy: The copy of a document that is used as a reference. It is updated at the end of a complex
service session.
moderator: The user that is in charge of distributing the complex service token. It may be the initiator, a
specific user, or the owner of the complex service token (in this case, the moderator role is changing
during the complex service session).
presenter: A user who presents the content and the structure of a document to other users (the viewers).
Joint document Presentation/Viewing complex service (PV) session: A complex service session with
the PV complex service.
PV token: A token used in the PV session to indicate which user is in turn to access and present a
document.
Joint Synchronous Editing complex service (SE) session: A complex service session with the SE
complex service.
SE token: A token used in the SE session to indicate which user is in turn to access and manipulate a
document.
viewer: A user who follows the presentation of the content and the structure of a document provided by
another user (the presenter).
3.2 Abbreviations
For the purposes of this ETS, all the abbreviations in ETS 300 498-1 [1] apply. In addition, the following
abbreviations apply:
ACSE Association Control Service Element
AEE Associations Establishment End step
AEI Associations Establishment Initiation step
AP Asynchronous document Production complex service
AR Associations Release step
CDH Co-operative Document Handling
CS Complex Service
CSS Central Service Server
Page 10
ETS 300 498-2: April 1998
DTAM-DM/TK Combined Document Transfer And Manipulation - Document
Manipulation/ToKen exchange
DTAM-DM-SYM Document Transfer And Manipulation - Document Manipulation - Symmetric
EWOS European Workshop for Open Systems
FDS Final Document Synchronization step
GAI Generic Abstract Interface
GC GCC conference Creation step
GCC Generic Conference Control
GE GCC conference invitation End step
GI GCC conference Invitation step
GT GCC conference Termination step
IDS Initial Document Synchronization step
ISSS Information Society Standardization System
MCJ MCS Channel Joining step
MCR MCS Channel Release step
MCS Multipoint Communication Service
MCU Multipoint Control Unit
M-DTAM-DM Multipoint - Document Transfer And Manipulation - Document Manipulation
MDE MCS Domain Establishment step
MDR MCS Domain Release step
M-RPC Multipoint - Remote Procedure Call
MUA MCS Users Attachment step
MUD MCS Users Detachment step
O Operation step
PV Joint document Presentation / Viewing complex service
PV1 PV with 1 presenter
PVn PV with n presenters
ROSE Remote Operations Service Element
SE Joint Synchronous Editing complex service
SM Selection / Management step
SP Sequential document Production complex service
SP1 SP with 1 document server
SPn SP with n document servers
4 Introduction to document communication complex services
This ETS specifies services for document communication. Basic services are specified in
ETS 300 498-1 [1]. This part of the ETS specifies Complex Services (CS) with clause 4 providing an
introduction and clauses 8, 9 and 10 providing the formal definition of the complex services.
Complex services are built on top of basic services and make use of existing document and
communication base standards and profiles.
Six CS in four categories are considered, a number in the range 1 to 6 is assigned to each CS:
a) category 1: joint Synchronous Editing (SE), which consists of:
- SE, Joint Synchronous Editing (CS 1).
b) category 2: joint document Presentation/Viewing (PV), which consists of:
- PV1, joint document presentation/viewing with 1 presenter (CS 2);
- PVn, joint document presentation/viewing with n presenters (CS 3).
c) category 3: Sequential document Production (SP), which consists of:
- SP1, sequential document production with 1 document server (CS 4);
- SPn, sequential document production with n document servers (CS 5).
d) category 4: Asynchronous document Production (AP), which consists of:
- AP, Asynchronous document Production (CS 6).

Page 11
ETS 300 498-2: April 1998
The complex services of category 1 (SE) and category 2 (PV) are specified in this ETS. The complex
services of categories 3 (SP) and 4 (AP), both introduced in ETS 300 498-1 [1], are left for further study.
4.1 Classification of complex services
Table 1 classifies the complex services taking into account the following characteristics:
a) granularity: complex services working on:
- full documents; and/or
- document fragments.
b) altering, or type of operations provided:
- altering: information in the document is modified;
- non-altering: information in the document is not modified.
c) connectivity, or communicating entities relationships:
- one communicating entity associated to several communicating entities;
- several communicating entities associated to one communicating entity;
- several communicating entities associated to several communicating entities.
d) synchronization:
- synchronous: user access to the document(s) is controlled (and serialized) by means of the
complex service (normally using a token handling mechanism);
- asynchronous: user access to the document(s) may occur in random order (and is normally
managed by an application).
e) document production:
- sequential production: a document is generated in a sequential manner, following certain
rules;
- non-sequential production: no rules are defined for the order in which different parts of a
document need to be generated;
- no production: documents are not produced with the complex service.
f) use of the Multipoint Communication Service (MCS) (ITU-T Recommendation T.122 [2] and
ITU-T Recommendation T.125 [3]):
- no need: there is no need for MCS;
- possible: MCS is useful, although other alternatives exist.

Page 12
ETS 300 498-2: April 1998
Table 1: Classification of complex services
Complex services
Characteristic SE PV1 PVn SP1 SPn AP
Granularity works on full documents
works on document fragments
Altering altering operations3333
non-altering operations 33
Connectivity one to several comm. entities3
several to one comm. entities
several to several comm. entities
Synchronization synchronous
asynchronous3
Document pro- sequential production
duction non-sequential production33
no production 33
MCS use no need for MCS 333
MCS may be used
4.2 Joint Synchronous Editing (SE)
For the SE complex service, the following subclauses give a description and some service construction
rules, that highlight the basic services on which the complex service is founded and how these basic
services are combined together. Figures 1 and 2 are used for this purpose. Let n be the number of users
participating in a SE session, n > 1.
4.2.1 Description
The SE complex service consists of the remote editing of one or more documents by several users in an
interactive and synchronous manner.
The basic principles which constitute the SE complex service are:
- several pre-determined users co-operate to jointly edit one or more pre-determined documents.
Although every user may have a full or partial copy of a document, only one copy is designated the
master copy, in which the result of the joint editing is stored. The master copy may be stored in one
of the user servers. Local copies of a document can be useful to avoid data transfer overheads
when some users view a document;
- one user will initiate the SE session. This user is called the initiator;
- optionally, the initiator, or another user, may take the role of moderator of the SE session. The
moderator is in charge of distributing the SE token, introduced below;
- users may establish several one-to-one associations or one one-to-several association to other
communicating entities;
- users communicate to a Central Service Server (CSS) or to all the other users;
- if users communicate to a CSS, the CSS is in charge of co-ordinating the whole process of joint
synchronous editing. The CSS takes the role of moderator of the SE session. One-to-one
symmetric associations will be established between the users and the CSS. All the updates will be
sent from a user to the CSS, that, in turn, will send the updates to the other users;
- if users communicate to all the other users, two communication alternatives are possible:
- use of MCS. MCS provides interactive multipoint communication functions to the users. One
one-to-several association (one MCS channel) will be established between all users. All the
updates will be sent from a user to all the other users;

Page 13
ETS 300 498-2: April 1998
- use of the Generic Conference Control (GCC) facilities (ITU-T Recommendation T.124 [4]).
GCC provides, together with MCS, interactive multipoint conferencing functions to the users;
NOTE: A third possible communication alternative could be the use of one-to-one associations
without any CSS. Then n*(n-1)/2 one-to-one associations need to be established in
order to allow for communication between all users. This is not specified as a solution
in this ETS because of the high costs (e.g., a SE session with 10 users requires 45
associations with a very complicated token handling procedure). Nevertheless, some
further information for this case is given in annex B, subclause B.1.6;
- before manipulation starts, an Initial Document Synchronization (IDS) phase is necessary, where all
users get, if not yet available, the document(s) or document fragment(s) which are to be jointly
edited during the SE session;
- there is no specific pre-established order in which the users access and manipulate the documents;
- a SE token exists. The SE token is used to indicate which user is next in line to manipulate a
document. Only the holder of the SE token can manipulate a document at any one time, while the
others optionally view. The moderator controls the SE token and distributes it according to requests
of users. The moderator can be the initiator, a pre-defined specific user, the user holding the SE
token (i.e. the moderator role may change during the complex service session), or the CSS, if any;
- when a user manipulates a document fragment, this operation is sent to all other users;
- before the SE session terminates, a Final Document Synchronization (FDS) phase is necessary,
where the final version of the master copy of the document(s) is validated.
4.2.2 Service construction rules
Depending on the association type, two variants of the SE complex service are considered:
- several one-to-one associations, i.e. SE with CSS;
- one one-to-several association, i.e. SE without CSS.
The two variants are illustrated in figures 1 and 2 respectively.
Figure 1 gives an overview of the SE complex service using a CSS.

Page 14
ETS 300 498-2: April 1998
Client 2
Client 1
Server 2
Server 1
User 2
User 1 / CSS
Client 3
Server 3
...
User 3
Legend:
SE token
Document manipulation
[, storing, retrieval]
Client n
Master copy of the document
Server n
Optional local copy of the document
User n
Figure 1: Joint Synchronous Editing (SE) with Central Service Server (CSS),when CSS has the
master copy of the document
In this case, the SE complex service consists of the remote editing of one or more documents by several
users in an interactive and synchronous manner, where n-1 users communicate with an intermediate
CSS, located at user 1.
One-to-one associations are established between the n-1 users and the CSS. The CSS receives the
manipulation operations and sends updates to the rest of the users. The CSS has the moderator role,
meaning that it is responsible for assigning the SE token during the SE session.

Page 15
ETS 300 498-2: April 1998
Figure 2 gives an overview of the SE complex service without CSS.
Client 1
Server 1
User 1
...
Document Server
Client 2
Server 2
User 2
...
...
Legend:
SE token
...
[Document storing]
Document manipulation
[, storing, retrieval] Client n
Master copy of the document
Server n
Optional local copy of the document
User n
Figure 2: Joint Synchronous Editing (SE) without Central Service Server (CSS),when the master
copy of the document is not in any of the user servers
In this case, the SE complex service consists in the remote editing of one or more documents by several
users in an interactive and synchronous way, without any intermediate CSS, so all users
intercommunicate between themselves.
One one-to-several association (one MCS channel) is established between all users. No CSS exists. The
role of moderator, i.e. the user responsible for assigning the SE token during the SE session, needs to be
agreed.
The SE complex service is based on the following basic services:
- manipulation;
- token-interchange;
- retrieval (optional);
- storing (optional).
The manipulation basic service is used to manipulate the document remotely and to send updates to other
users. The purpose of the SE token is to know which user is in turn to access and manipulate a
document. The token-interchange basic service is used to interchange the SE token. The retrieval basic
service may be used for the IDS phase. The storing basic service may be used for the FDS phase.

Page 16
ETS 300 498-2: April 1998
4.3 Joint document Presentation/Viewing (PV)
The PV complex services category consists of the remote presentation or joint viewing of a document,
where a user (the presenter) presents the content of a document to other users (the viewers).
The basic principles which constitute the PV complex services are:
- several pre-determined users co-operate to jointly present/view one or more pre-determined
documents. Every user has a full copy of the document(s);
- one user will initiate the PV session. This user is called the initiator;
- optionally, the initiator, or another user, may take the role of moderator of the PV session. The
moderator is in charge of distributing the PV token, introduced below, if any;
- the user who presents (at a given time) the content of a document is called presenter;
- users who do not present (at a given time) are called viewers;
- the presenter communicates to all viewers;
- users may establish several one-to-one associations or one one-to-several association;
- if one-to-one associations are used, several one-to-one associations need to be established in
order to allow for communication between all users through a CSS (see subclause 4.2.1);
- MCS may be used. Then, the establishment of one one-to-several association (one MCS channel)
is enough (see subclause 4.2.1);
- GCC may also be used (see subclause 4.2.1);
- before presentation starts, an IDS phase is necessary, where all users get, if not yet available, the
document(s) which are subject to the PV session;
- when a presenter points to a document fragment, this operation is sent to all viewers;
- a PV token may exist. Only the owner of the PV token can present a document. The moderator
controls the PV token and distributes it according to requests of viewers. The moderator can be the
initiator, a pre-defined specific user, the user holding the PV token (i. e. the moderator role is
changing during the PV session).
The PV complex services are classified according to the number of users who can present a document to
the other users, the two following cases are considered:
- PV1, i.e. a Joint document Presentation/viewing with 1 presenter;
- PVn, i.e. a Joint document Presentation/viewing with n presenters.
For each of these PV complex services, the following subclauses give a description and some service
construction rules, that highlight the basic services on which the complex service is founded and how
these basic services are combined together. Figures 3 and 4 are used for this purpose. Let n be the
number of users participating in a PV session, n > 1.
4.3.1 Joint document Presentation/viewing with 1 presenter (PV1)
4.3.1.1 Description
The PV1 complex service consists of the remote presentation or joint viewing of one or more documents,
where one user (the presenter) presents the content and structure of a document to the other users (the
viewers).
No PV token is needed.
Page 17
ETS 300 498-2: April 1998
4.3.1.2 Service construction rules
Figure 3 gives an overview of the PV1 complex service.
Client 1
Client 2
Server 1
Server 2
Presenter
Viewer 1
Client 3
... Server 3
Viewer 2
Legend:
Pointing (n = 2) or
Multi-pointing (n > 2)
...
Master copy of the document
Client n
Optional local copy of the document
Server n
Viewer n-1
Figure 3: Joint document Presentation/Viewing with 1 presenter (PV1),when the master copy of
the document is on the presenter's server
The PV1 complex service is based on the following basic services:
- pointing (if there is only one viewer) or multi-pointing (if there are more than one viewer);
- retrieval (optional).
The pointing or multi-pointing basic services are used because the presenter needs to identify document
fragments to one or several viewers, respectively. The retrieval basic service may be used for the IDS
phase.
4.3.2 Joint document Presentation/viewing with n presenters (PVn)
4.3.2.1 Description
The PVn complex service consists of the remote presentation or joint viewing of one or more documents,
where several users (the presenters) present the content of a document to the other users (the viewers).
In the PVn complex service, all users are provided with the ability to present the content of a document to
the other users, but at a given time only one user presents while the others view.

Page 18
ETS 300 498-2: April 1998
Most of the characteristics of the PV1 complex service are still valid. The main differences of the PV1
complex service are:
- more than one user may present;
- a PV token is needed to control who is presenting.
4.3.2.2 Service construction rules
Figure 4 gives an overview of the PVn complex service.
Client 1
Client 2
Server 1
Server 2
Viewer n-1
Viewer 1
Client 3
Server 3
Legend:
Viewer 2
PV token
...
Pointing (n = 2) or
Multi-pointing (n > 2)
Master copy of the document
Client n
Optional local copy of the document
Server n
Presenter
Figure 4: Joint document Presentation/Viewing with n presenters (PVn),when the master copy of
the document is in one of the user servers
The PVn complex service is based on the following basic services:
- pointing (if there is only one viewer) or multi-pointing (if there are more than one viewer);
- token-interchange;
- retrieval (optional).
The pointing or multi-pointing basic services are used because the presenter needs to identify document
fragments to one or several viewers, respectively. The purpose of the PV token is to know which user is
next in line to present the document. The token-interchange basic service is used to interchange the PV
token. The retrieval basic service may be used for the IDS phase.

Page 19
ETS 300 498-2: April 1998
5 Document aspects concerning the SE and PV complex services
In clause 6, part 1 of this ETS, document aspects of the basic services are specified. The ODA standards
and recommendations are considered as the method for representing and interchanging documents.
This part specifies another document aspect, i.e. the use of non-ODA documents.
5.1 Non-ODA documents
CSs specified in this part of the ETS shall be applicable to non-ODA documents.
There are two cases of handling documents:
- handling of full documents: in this case, since the operations are independent from the document
structure, all basic and Complex Services shall apply to both ODA documents and non-ODA
documents;
- handling of document fragments: in this case, a method to identify document fragments is needed
in order to apply basic and CSs to non-ODA documents.
NOTE: It is outside the scope of this ETS to specify such an identification mechanism. The
European Workshop for Open Systems (EWOS), that is planned to be replaced by the
ISSS (Information Society Standardization System), a CEN division, in September
1997, is working on the definition of a Generic Abstract Interface (GAI) allowing
manipulation of any kind of document.
In case of working on non-ODA documents, the document format shall be specified following the rules
given in subclauses 7.1.5, 7.3.2 and annex A. More information is given in subclause B.1.3 of annex B.
6 Communication aspects concerning the SE and PV complex services
In addition to the communication modules described in clause 7 of ETS 300 498-1 [1], the following
communication modules are needed to specify document communication complex services:
- combined DTAM-DM and DTAM-TK (DTAM-DM/TK);
- Multipoint Communication Service (MCS);
- Generic Conference Control (GCC).
6.1 Combined DTAM-DM and DTAM-TK (DTAM-DM/TK)
6.1.1 Description
The DTAM-DM communication module is described in subclause 7.4 of ETS 300 498-1 [1]. The DTAM-
TK communication module is described in subclause 7.5 of ETS 300 498-1 [1].
In addition to this, a combined DTAM-DM/DTAM-TK communication module exists, that allows a
symmetric communication for remote document manipulation of documents, combined with a token
interchange capability in order to synchronize the communicating entities.
All the features of DTAM-DM and DTAM-TK apply.
6.1.2 Services, protocols and profiles
The DTAM-DM symmetric abstract services are contained in the DTAM-DM-SYM application service
element. The DTAM-TK abstract services are contained in the DTAM-TK application service element.
Both application service elements and their combined use are specified in
ITU-T Recommendation T.435 [8].
The combined DTAM-DM/DTAM-TK protocol is specified in ITU-T Recommendation T.436 [9]. This
protocol makes use of the Association Control Service Element (ACSE), the Remote Operations Service
Element (ROSE) and the presentation service.

Page 20
ETS 300 498-2: April 1998
The profiles AOD11, AOD12 and AOD13, as specified in ETS 300 498-1 [1], subclause 7.4.2 also apply to
this communication module.
The basicReadOnlyLevel is one of the manipulation levels which can be indicated in the arguments of the
abstract DTAM bind operation, as specified in ITU-T Recommendation T.435 [8], subclause 8.1.
6.1.3 Use for document communication
DTAM-DM/TK is used for the remote interactive symmetric manipulation of documents where a token is
needed to synchronize communicating entities.
6.2 Multipoint Communication Service (MCS)
6.2.1 Description
Multipoint Communication Service (MCS) provides a general multipoint connection-oriented data service.
It collects point-to-point transport connections and combines them to form a multipoint domain. Within that
domain, a large number of logical channels can provide one-to-one, one-to-many and many-to-one data
delivery. Nodes within an MCS doma
...