ISO/IEC 10021-1:1990/Amd 1:1994
(Amendment)Information technology — Text Communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 1: System and Service Overview — Amendment 1: Message Store Extensions
Information technology — Text Communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 1: System and Service Overview — Amendment 1: Message Store Extensions
Replaces text in clauses 7.1; 7.4; 8.5; 18; 19.6; 19.7; 19.9. Append text in annexes B and C.
Technologies de l'information — Communication de texte — Systèmes d'échange de texte en mode message (MOTIS) — Partie 1: Présentation générale du système et des services — Amendement 1: Extensions de dépôt de message
General Information
Relations
Standards Content (Sample)
ISO/IEC
INTERNATIONAL
10021-1
STANDARD
First edition
1990-12-01
AMENDMENT 1
1994-12-01
Information technology - Text Communication -
Message-Oriented Text Interchange Systems
(MOTIS) -
Part 1:
System and Service Overview
AMENDMENT 1: Message Store Extensions
Technologies de I ’information - Communication de texte - Systemes d ’kchange
de texte en mode message (MOTIS) -
Partie 7: Prksentation g&krale du systhme et des services
AMENDEMENT 7: Extensions de d&p& de message
Reference number
ISO/IEC IOOZI-1:1990/Amd.1:1994(E)
---------------------- Page: 1 ----------------------
ISO/IEC 10021-1:199O/Amd.l:1994(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the Inter-
national 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, ISO/IEC JTC 1. Draft International Standards adopted by the
joint technical committee are circulated to national bodies for voting. Publication
as an International Standard requires approval by at least 75 % of the national
bodies casting a vote.
Amendment 1 to International Standard ISOLIEC 10021- 1: 1990 was prepared by
Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee 18, Document processing and related communication.
o ISO/IEC 1994
All rights reserved. Unless otherwise specified, 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
ii
---------------------- Page: 2 ----------------------
ISO/IEC 10021~1:1990/Amd.l:1994(E)
Text Communication -
Information technology -
Message-Oriented Text Interchange Systems (MOTIS) -
Part 1:
System and Service Overview
AMENDMENT 1: Message Store Extensions
0 Introduction
This cikzuse provides an introduction to this amendment. The text in this clause is not intended for inclusion in ISOIIEC
10021-1.
The elements of Service provided by the Message Store Abstract-Service defined in CCI ’IT Rec. X.413 (1992) I ISO/IEC
10021-1:1990 are limited to the storage of delivered messages and their subsequent retrieval by the MS-User. This document
proposes extensions to the elements of Service offered by the general Message Store and the IPMS Message Store to equip
them to satisfy a broader range of Service requirements. These include the Provision of services for the storage of submitted
messages, the correlation of replies and IPNs, the modification by the MS-User of certain attributes of stored messages, and
the logging of Submission and delivery operations.
71 0 Description of the MHS Model
In existing clause 7.1, repliwe the second last Paragraph with the following:
The message store (MS) is an optional general purpose capability of MHS that acts as an intermediary between the UA and
the MTA. The MS is depicted in the MHS Functional Model as shown in Figure 1. The MS is a functional entity whose
primary purpose is to store delivered, and, optionally, submitted messages and permit their retrieval by the MS-User @JA).
The MS also allows for Submission from, and alerting to the MS-User.
74 l The Message Store
Replace existing clause 7.4 (up to 7.4.1) with the following:
Remote UAs tan be implemented on a wide variety of equipment, including personal Computers of varying capabilities. The
MS Service tan complement a remote UA by providing continuously available storage and delivery Services on behalf of a
User, for example.
One MS acts on behalf of only one User, i.e. it does not provide a common or shared MS capability to severd wem. See also
PRMD 3 of Figure 5.
The MS will store delivered messages and reports. As an Option it may also store submitted messages, submitted probes, and
draft messages. The MS may also keep a history of messages by storing extracts of previously and currently stored messages
in logs. Messages may be grouped in a user-defined and potentially hierarchical structure.
1
---------------------- Page: 3 ----------------------
ISO/IEC 10021~1:1990 / Amd.l:1994 (E)
The MS retrieval capability provides users who subscribe to an MS with basic message retrieval capabilities potentially
applicable to all information held by the MS. Figure 6 Shows the delivery, and subsequent retrieval of messages that are
delivered to an MS, and the Submission of messages via the MS.
/
Retrieval Delivery
,
MS-User ’ MS MTS
r
t \
MS Submission
Submission
Figure 6 - Submission and Delivery with an MS
When a user subscribes to an MS, all messages destined for the user are delivered to the MS only. The MS-User, if on line,
may receive Alerts that announce the delivery of certain messages to the MS. Messages delivered to an MS arc considered
delivered from the MTS perspective.
The basic MS is independent of application specific Services (see 8.7) and may store messages with all types of content, the
type of content being dependent on the type of Service. However, it may provide additional capabilities depending on the
type of content.
When an MS-user submits a message, the MS conveys the Submission request to the MTS and reports the outcome retumed
by the MTS to the MS-User. If requested by the MS-User, the MS may expand the message by forwarding parts of delivered
or submitted messages that are currently stored in the MS before conveying the Submission to the MTS. The MS may also
store a copy of the message submitted to the MTS if the Submission is successful. The MS service allows the User to transfer
a message to the MS for storage as a draft message. The draft message may subsequently be retrieved, or the MS may
include its body-Parts in a message submitted to the MTS when requested in a message submitted by the MS-User.
The MS-User may be provided with the capability to request the MS Service to forward selected messages automatically
upon delivery. The MS may also provide automatic deletion of messages after a User specified period of time, or when the
message expires, or when the message is rendered obsolete by another message.
The MS may automatically attach information to a previously submitted message concerning its delivery or non-delivery.
The MS may also generate content-specific notifications, acknowledging receipt or acceptance when requested by the User or
when the User has retrieved the message.
The elements of Service describing the features of the MS are defined in Annex B and classified in clause 19. Users are
provided with the capability based on various criteria, to get counts and lists of messages, to fetch messages, and to delete
messages, currently held in the MS.
Figure 6A depicts a simplified model of the information types stored in the MS, and the functions the MS fulfils.
The scope of the MS Services defined in CCITT Rec. F.400 (1988) and (1992) I ISO/IEC 10021-1: 1990 was mainly limited
to the storage of delivered messages and reports and their subsequent retrieval by the MS-User. The 1994 Version of this part
of ISO/IEC 10021 defines new extensions to provide a broader range of Service facilities. These enhanced facilities
particularly apply in those environments where the MS is used as a personal data base to store, retrieve, modify, and classify
a user ’s messages, often with frequent and lang-lasting interaction between the MS-User and MS. Examples of such
environments might be found in local area networks, or in environments where the User employs different User Agent
implementations at different locations to access one MS. In other environments where the MS is used mainly as a temporary
storage System, to take delivery of messages and reports and provide for their retrieval by infrequent and short-lasting
interactions, these enhanced facilities may not be required. In this latter case, some enhanced facilities may be provided
locally by the MS-User itself.
Consequently, the basic and essential optional requirements defined for the MS in this this part of ISO/IEC 10021 arc the
same as those defined in Versions published Prior to 1994.
---------------------- Page: 4 ----------------------
ISODEC 1002Llt1990 / Amd.lr1994 (E)
Insert a new Figure 6A:
Ml ’SPorts
Dellvery Submission
Administration
7
I
t
I
:
I - !
Timer
I
I
0
MS-Fundions
I
0
------------------
4
MS-Parts
Administrution MS-Submission
Retrieval
Zl
Submission to the MTS
@ Fetch, List and Summarlze
@
@ Modify message attributes @ Submkslon to the MTS
and Delete with incorporation of parts
of stored messages
0 Register-MS
@ Draft storage
Figure 6A - Message Store Functional Model
85 0 Message Store
Replace the last sentence of 8.5 with the following:
The user may submit messages through the MS, and retrieve messages that have been either delivered to the MS, or
submitted by the User.
---------------------- Page: 5 ----------------------
ISO/IEC 10021-1:1990 / Amd.l:1994 (E)
18
Purpose
Replace the last Paragraph of clause 18 (Vable 3 lists all the elements of service ”) with the following:
Table 3 lists all the Elements of Service available in MHS, Shows what Services they are associated with of the presently
defined Services, MT Service, IPM Service, PD Service, and MS Service, and gives the corresponding reference number to
the definition in Annex B. Elements of Service relevant to the IPM Message Store are marked on both the IPM and MS
columns.
In the following two amendments, the “Xir in each row is placed in the VPMrr and “M;Stt columns as indicated.
MT IPM PD MS
In Table 3, replace the existing row ending with “B.83” with the following:
Auto-forwarding of IP-messages
X X B.83
Add the following rows to Table 3, preserving alphabe& Order:
Auto-acknowledgement of IP-messages
X X B.96
Auto- action Log
X B.97
Auto-assignment of Annotations
X B.98
Auto-assignment of Group Names
X B.99
Auto-assignment of Storage Period
X
B.100
Auto-correlation of IP-messages
X X
B.101
Auto-correlation of IP-notifications
X X
B.102
Auto-correlation of Reports
X
B.103
Auto-deletion after S torage Period
X
B.104
Auto-discarding of IP-messages
X X
B.105
Delivery Log
X B.106
IP-message Action Status X
X B.107
Storage of Draft Messages
X B.108
S torage on Submission
X B.109
S torage Period Assignment
X B.l10
S tored Message Annotation
X B.lll
Stored Message Grouping
X B.112
Submission Log
X B.113
Submission of IP-messages Incorporating Stored Messages X
X B.114
19.6
Base Message Store
Replace the last sentence of the first Paragraph in 19.6 with the following:
When an MS is provided, each Element of Service shown in Table 8 shall be supported for every type of message (delivered-
message, submission-log, draft-messages etc.) stored in the MS to which that Element of Service is applicable.
---------------------- Page: 6 ----------------------
ISODEC 10021-lt1990 / Amd.l:1994 (E)
19.7 MS Optional User Facilities
Replace existing Table 9 with the following:
Table 9 - MS Optional User Facilities
Annex B
Elements of Service Classification Reference
Auto-action Log A B.97
A
Auto-assignment of Annotations B.98
A B.99
Auto-assignment of Group Names
Auto-assignment of S torage Period A B.100
A
Auto-correlation of Reports B.103
A B.104
Auto-deletion after S torage Period
A B.106
Delivery Log
A B.108
Storage of Draft Messages
A B.109
S torage on Submission
A
Storage Period Assignment B.l10
Stored Message Alert A B.82
S tored Message Annotation A B.llll
Stored Message Grouping A B.112
Submission Log A B.113
19.9 IPM Service Optional User Facilities
Insert the following rows in Table 11, preserving alphabetic Order:
A
Storage of Draft Messages B.108
N/A
S torage on Submission A B.109
N/A
Storage Period Assignment A B.l10
N/A
A B.111
S tored Message Annotation
N/A
S tored Message Grouping A B.112
N/A
Submission of IP-messages Incorporating Stored Messages N/A A B.114
In Table 12, repluce the existing row ending with “B.83 tt with the following:
Auto-forwarding of IP-messages A B.83
Insert the following rows in Table 12, preserving alphabetic Order:
Auto-acknowledgement of IP-messages A B.96
Auto-ac tion Log A B.97
Auto-assignment of Annotations A B.98
Auto-assignment of Group Names A B.99
Auto-assignment of S torage Period A B.100
Auto-correlation of IP-messages A
B.lO1
Auto-correlation of IP-notifications A
B.102
Auto-correlation of Reports A B.103
Auto-deletion after S torage Period A B.104
Auto-discarding of IP-messages A B.105
Delivery Log A B.106
IP-message Action Status A B.107
Submission Log A B.113
---------------------- Page: 7 ----------------------
ISO/IEC 10021-1:1990 / Amdkl994 (E)
Annex B
Definitions of Elements of Service
In Annex B, append the following to the NOTE:
This element of Service was not defined in Versions of this part of ISO/IEC 10021 published Prior to 1994.
(1994)
In Annex B, replace clause B.83 with the following:
B.83 Auto-forwarding of IP-messages IPM MS
This element of Service enables an MS-User to instruct the MS to auto-forward selected P-messages that are delivered to it.
The MS-User may specify through registration several sets of criteria Chosen from the attributes available in the MS, and IP-
messages meeting each set of criteria will be auto-forwarded to one or more users or DLs. If requested by the message
originator, a non-receipt notification is generated indicating that the IP-message was auto-forwarded, even if the MS retains
a copy of the forwarded message. For each set of selection criteria, a body part may be specified, to be included as a ‘cover-
note’ with each auto-forwarded P-message.
NOTE - In Versions of this put of ISO/IEC 10021 bl’ h d
pu is e Prior to 1994, this element of Service was named Stored
Message Auto-forward, and classified as a general MS optional User facility; it has since been classified 8s IPM-specific.
In Annex B, insert the following sentence @er the Jirst sentence of clkwse B.84:
Subject to subscription, deletion may be restricted to messages meeting certain criteria, e.g., messages stored for longer than
an agreed period of time.
In Annex B (as modified by Technical Corrigendum 1), replace clause B.4n with the folIowing:
B.4n MS Register
MS
This element of service enables an MS-User register items of information
with the MS in to modify
aspects of its behaviour, such as:
1. the Performance of automatic actions;
2. the default set of information retrieved when using the Stored Message Fetthing and Stored Message Listing
elements of Service. One set of information may be registered per UA employed by the User;
3. the credentials used by the Message Store to authenticate the MS-User.
If a User employs more than one UA implementation, then as a subscription Option the MS may store a separate set of
registration information for each UA. The User may retrieve the registered information from the MS.
NOTE - The capability to store separate Sets of registration infoxmation and to retrieve registered information was not defined in Versions of this
part of ISO/IEC 10021 published Prior to 1994.
Insert the following clauses (B.96 - B.114) at the end of Annex B:
B.96 Auto-acknowledgement of IP-messages
IPM MS (1994)
This element of Service enables an MS-user
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.