ETSI ETS 300 498-1 ed.1 (1996-07)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Odprta arhitektura dokumentov (ODA) – Komunikacijske storitve ODA – 1. del: Osnovne storitveOpen Document Architecture (ODA); ODA communication services; Part 1: Basic services35.240.20Uporabniške rešitve IT pri pisarniškem deluIT applications in office workICS:Ta slovenski standard je istoveten z:ETS 300 498-1 Edition 1SIST ETS 300 498-1 E1:2003en01-december-2003SIST ETS 300 498-1 E1:2003SLOVENSKI
STANDARD
EUROPEANETS 300 498-1TELECOMMUNICATIONJuly 1996STANDARDSource: ETSI TC-TEReference: DE/TE-02022ICS:33.020Key words:ODA, DTAM, DFROpen Document Architecture (ODA);ODA communication services;Part 1: Basic servicesETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST ETS 300 498-1 E1:2003

Page 2ETS 300 498-1: July 1996Whilst 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.SIST ETS 300 498-1 E1:2003

Page 3ETS 300 498-1: July 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.113.1Definitions.113.2Abbreviations.124Introduction to document communication basic services.134.1Basic services that can be stand-alone services.144.1.1SToRing basic service (STR).144.1.1.1Description.144.1.1.2Examples of concrete applications.144.1.2DiSTribution basic service (DST).144.1.2.1Description.144.1.2.2Examples of concrete applications.144.1.3ReTRieval basic service (RTR).144.1.3.1Description.144.1.3.2Examples of concrete applications.144.1.4Storing-And-Retrieval basic service (SAR).144.1.4.1Description.144.1.4.2Examples of concrete applications.154.1.5MaNiPulation basic service (MNP).154.1.5.1Description.154.1.5.2Examples of concrete applications.154.2Basic services that cannot be stand-alone services.154.2.1PoiNTing basic service (PNT).154.2.1.1Description.154.2.1.2Examples of concrete applications.154.2.2Multi-PoinTing basic service (MPT).154.2.2.1Description.154.2.2.2Examples of concrete applications.164.2.3ToKen-Interchange basic service (TKI).164.2.3.1Description.164.2.3.2Examples of concrete applications.164.3Classification of basic services.165Introduction to document communication complex services.175.1Asynchronous document production.175.1.1Description.175.1.2Service construction rules.175.1.3Example of concrete applications.185.2Sequential document production.185.2.1Description.185.2.2Service construction rules.195.2.2.1Local manipulation of the document.195.2.2.2Remote manipulation of the document on different stores.205.2.2.3Remote manipulation of the document on a central store.215.2.3Examples of concrete applications.215.3Joint synchronous editing.225.3.1Description.225.3.2Service construction rules.225.3.3Example of concrete applications.235.4Joint document presentation/viewing.235.4.1Description.23SIST ETS 300 498-1 E1:2003

Page 4ETS 300 498-1: July 19965.4.2Service construction rules.235.4.2.1Only one user can present.235.4.2.2All users can present.245.4.3Example of concrete applications.256Document aspects.256.1Introduction.256.2ODA DAPs.256.2.1DAPs for document processing applications.266.2.2DAPs for image applications.266.3Use of ODA DAPs.267Communication aspects.277.1Introduction.277.2Document Filing and Retrieval (DFR).287.2.1Description.287.2.2Services, protocols and profiles.287.2.3Use for document communication.297.3Document Transfer And Manipulation - Bulk Transfer - Normal Mode (DTAM-BT-NM).297.3.1Description.297.3.2Services, protocols and profiles.297.3.3Use for document communication.297.4Document Transfer And Manipulation - Document Manipulation (DTAM-DM).297.4.1Description.297.4.2Services, protocols and profiles.297.4.3Use for document communication.317.5Document Transfer And Manipulation - Token Exchange (DTAM-TK).317.5.1Description.317.5.2Services, protocols and profiles.317.5.3Use for document communication.317.6Combined use of DFR and DTAM-DM (DFR/DTAM-DM).317.6.1Description.317.6.2Services, protocols and profiles.317.6.3Use for document communication.327.7Message Handling Systems (MHS).327.7.1Description.327.7.2Services, protocols and profiles.327.7.3Use for document communication.338Components and design rules for basic services.338.1Definition of document related service attributes.348.1.1The service attribute "document location".348.1.2The service attribute "document copies".358.1.3The service attribute "document access rights".358.1.4The service attribute "store access rights".368.1.5The service attribute "document format".368.1.6The service attribute "functionality level".378.2Definition of communication related service attributes.388.2.1The service attribute "number of communicating entities".388.2.2The service attribute "communication type".388.2.3The service attribute "communication module".398.3Rules for the formal definition of basic services.398.3.1Rules and notation for the assignment of values to the document relatedservice attributes.408.3.2Rules and notation for the assignment of values to the communicationrelated service attributes.418.3.3Rules and notation for the selection of the communication modules.418.3.4Application rules.429Formal definition of document communication basic services.439.1Storing basic service.439.1.1Document related service attributes.439.1.2Communication related service attributes.43SIST ETS 300 498-1 E1:2003

Page 5ETS 300 498-1: July 19969.1.3Selection of communication modules.449.1.4Application rules.449.1.4.1Application rules when using DFR.449.1.4.2Application rules when using DTAM-BT-NM.459.1.4.3Application rules when using MHS.459.2Distribution basic service.459.2.1Document related service attributes.459.2.2Communication related service attributes.459.2.3Selection of communication modules.469.2.4Application rules.479.2.4.1Application rules when using DFR.479.2.4.2Application rules when using DTAM-BT-NM.479.2.4.3Application rules when using MHS.489.3Retrieval basic service.489.3.1Document related service attributes.489.3.2Communication related service attributes.489.3.3Selection of communication modules.499.3.4Application rules.509.3.4.1Application rules when using DFR.509.3.4.2Application rules when using DTAM-DM.509.3.4.3Application rules when using DFR in combination withDTAM-DM.519.3.4.4Application rules when using MHS.519.4Storing-and-Retrieval basic service.529.4.1Document related service attributes.529.4.2Communication related service attributes.539.4.3Selection of communication modules.539.4.4Application rules.549.4.4.1Application rules when using DFR.549.4.4.2Application rules when using DTAM-DM.549.4.4.3Application rules when using DFR in combination withDTAM-DM.559.4.4.4Application rules when using MHS.569.5Manipulation basic service.569.5.1Document related service attributes.569.5.2Communication related service attributes.579.5.3Relationship to communication modules.579.5.4Application rules.589.5.4.1Application rules when using DFR.589.5.4.2Application rules when using DTAM-DM.589.5.4.3Application rules when using DFR in combination withDTAM-DM.599.5.4.4Application rules when using MHS.609.6Pointing basic service.609.6.1Document related service attributes.609.6.2Communication related service attributes.619.6.3Selection of communication modules.619.6.4Application rules.629.6.4.1Application rules when using DTAM-DM.629.7Multi-pointing basic service.629.7.1Document related service attributes.629.7.2Communication related service attributes.639.7.3Selection of communication modules.639.7.4Application rules.649.7.4.1Application rules when using DTAM-DM.649.8Token-interchange basic service.649.8.1Document related service attributes.659.8.2Communication related service attributes.659.8.3Selection of communication modules.659.8.4Application rules.669.8.4.1Application rules when using DTAM-TK.66Annex A (informative):Use of further communication modules.67SIST ETS 300 498-1 E1:2003

Page 6ETS 300 498-1: July 1996A.1Document Transfer And Manipulation - Bulk Transfer - Transparent Mode (DTAM-BT-TM).67A.1.1Description.67A.1.2Services, protocols and profiles.67A.1.3Use for document communication.68A.2Facsimile group 3 (FAX3).68A.2.1Description.68A.2.2Services, protocols and profiles.68A.2.3Use for document communication.68A.3EuroFile Transfer (EFT).69A.3.1Description.69A.3.2Services, protocols and profiles.69A.3.3Use for document communication.69A.4File Transfer, Access and Manipulation (FTAM).69A.4.1Description.69A.4.2Services, protocols and profiles.70A.4.3Use for document communication.70A.5Facsimile group 4 (FAX4) application.70A.5.1Description.70A.5.2Services, protocols and profiles.70A.5.3Use for document communication.71A.6Binary File Transfer (BFT) application.71A.6.1Description.71A.6.2Services, protocols and profiles.71A.6.3Use for document communication.71Annex B (informative):Implementation guidelines.73B.1General implementation guidelines.73B.1.1Amount of information to be transferred.73B.1.2Mapping of DFR access rights to access rights of this ETS.73B.1.3Quality of Service (QoS).74B.1.4Security.75B.2Specific implementation hints for the storing basic service.75B.3Specific implementation hints for the distribution basic service.76B.4Specific implementation hints for the retrieval basic service.76B.5Specific implementation hints for the storing-and-retrieval basic service.77B.6Specific implementation hints for the manipulation basic service.77B.7Specific implementation hints for the pointing basic service.77B.8Specific implementation hints for the multi-pointing basic service.77B.9Specific implementation hints for the token-interchange basic service.77Annex C (informative):Bibliography.78C.1Document architectures.78C.2Communication architectures.78History.81SIST ETS 300 498-1 E1:2003

Page 7ETS 300 498-1: July 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Terminal Equipment (TE)Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS specifies document communication services, based on Open Document Architecture (ODA)documents, to be provided on top of existing base standards or profiles, giving constraints on them andrules on how to use and combine them.This first Part of the ETS specifies basic services. Complex services, founded on basic services, will bespecified in Part 2 to this ETS (currently under development).ETSI Technical Report (ETR) 081 has been taken into consideration as one of the sources for this ETS.The purpose of ETR 081 was to define the scope and priorities for the initialization of standardization inthe area of ODA communication applications.Transposition datesDate of adoption of this ETS:17 May 1996Date of latest announcement of this ETS (doa):30 September 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 March 1997Date of withdrawal of any conflicting National Standard (dow):31 March 1997SIST ETS 300 498-1 E1:2003

Page 8ETS 300 498-1: July 1996Blank pageSIST ETS 300 498-1 E1:2003

Page 9ETS 300 498-1: July 19961ScopeThe Open Document Architecture (ODA) base standard and associated profiles specify the means torepresent and interchange complex documents.Communication base standards and associated profiles, specifying interchange, remote manipulation andmanagement of documents at the application layer of the Open Systems Interconnection (OSI) referencemodel, have also been specified, as Document Transfer And Manipulation (DTAM) and Document Filingand Retrieval (DFR).Standardizing document communication services will help implementors and service providers to extendthe use and acceptance of these services in Europe. Furthermore, the standardization of documentcommunication service profiles will facilitate interworking.This ETS specifies ODA document communication services to be provided on top of existing basestandards or profiles, giving constraints on them and rules on how to use and combine them.This first Part of the ETS specifies basic services, such as storing-and-retrieval or manipulation. Complexservices, such as asynchronous document production or joint document presentation, will be founded onbasic services, and will specified in a future ETS. Some of these complex services are introduced in thisPart of this ETS, in order to more clearly understand the complex services that could be built on top of thebasic ones.2Normative referencesPart 1 of this ETS incorporates by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to Part 1 of this ETS only when incorporated in it by amendment or revision. For undated referencesthe latest edition of the publication referred to applies.[1]ISO/IEC 8613-1 (1994) / ITU-T Recommendation T.411 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 1: Introduction and general principles".[2]ISO/IEC 8613-2 (1994) / ITU-T Recommendation T.412 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 2: Document structures".[3]ISO/IEC 8613-3 (1994) / ITU-T Recommendation T.413 (1994): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 3: Abstract interface for the manipulation of ODA documents".[4]ISO/IEC 8613-4 (1994) / ITU-T Recommendation T.414 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 4: Document profile".[5]ISO/IEC 8613-5 (1994) / ITU-T Recommendation T.415 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 5: Open Document Interchange Format (ODIF)".[6]ISO/IEC 8613-6 (1994) / ITU-T Recommendation T.416 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 6: Character content architectures".[7]ISO/IEC 8613-7 (1994) / ITU-T Recommendation T.417 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 7: Raster graphics content architectures".[8]ISO/IEC 8613-8 (1994) / ITU-T Recommendation T.418 (1993): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 8: Geometric graphics content architectures".SIST ETS 300 498-1 E1:2003

Page 10ETS 300 498-1: July 1996[9]ISO/IEC 8613-12 (1994) / ITU-T Recommendation T.422 (1994): "Informationtechnology - Open Document Architecture (ODA) and interchange format -Part 12: Identification of document fragments".[10]ISO/IEC ISP 10610-1 (1993): "Information technology - Internationalstandardized profile FOD11 - Open document format: Simple documentstructure - Character content architecture only - Part 1: Document ApplicationProfile (DAP)".[11]ISO/IEC ISP 11181-1 (1993): "Information technology - Internationalstandardized profile FOD26 - Open document format: Enhanced documentstructure - Character, raster graphics and geometric graphics contentarchitectures - Part 1: Document Application Profile (DAP)".[12]ISO/IEC ISP 11182-1 (1993): "Information technology - Internationalstandardized profile FOD36 - Open document format: Extended documentstructure - Character, raster graphics and geometric graphics contentarchitectures - Part 1: Document Application Profile (DAP)".[13]ISO/IEC 10166-1 (1991): "Information technology - Text and office systems -Document Filing and Retrieval (DFR) - Part 1: Abstract service definition andprocedures".[14]ISO/IEC 10166-1 (1991) / Cor. 1 and Cor. 2 (1994): "Information technology -Text and office systems - Document Filing and Retrieval (DFR) - Part 1:Abstract service definition and procedures - Technical corrigendum 1 andTechnical corrigendum 2".[15]ISO/IEC 10166-2 (1991): "Information technology - Text and office systems -Document Filing and Retrieval (DFR) - Part 2: Protocol specification".[16]ISO/IEC ISP 12069: "Information technology - International standardized profilesADFnn - Document Filing and Retrieval - Parts 1 to 3".[17]CCITT Recommendation T.522 (1991): "Communication application profile BT1for document bulk transfer".[18]ITU-T Recommendation T.435 (1994): "Document Transfer And Manipulation(DTAM) - Services and protocols - Abstract service definition and procedures forconfirmed document manipulation".[19]ITU-T Recommendation T.436 (1994): "Document Transfer And Manipulation(DTAM) - Services and protocols - Protocol specifications for confirmeddocument manipulation".[20]ISO/IEC 10021 (1990): "Information processing systems - Text communication -Message Oriented Text Interchange Systems (MOTIS)".[21]ISO/IEC ISP 10611, Parts 1 to 5 (1994): "Information technology - Internationalstandardized profiles - Application profiles for Message Handling (MH) -Common messaging - Part 1: MHS service support (AMH1n); Part 2:Specification of ROSE, RTSE, ACSE, presentation and session protocols foruse by MHS (AMH1n); Part 3: AMH11 - Message transfer (P1); Part 4: AMH12 -MTS access (P3); Part 5: AMH13 - MS access (P7)".[22]ISO/IEC ISP 12062, Parts 1 to 5 (1994): "Information technology - Internationalstandardized profiles - Application profiles for Message Handling (MH) -Interpersonal messaging - Part 1: IPM MHS service support; Part 2: AMH21 -IPM content; Part 3: AMH22 - IPM requirements for message transfer (P1);Part 4: AMH23 - IPM requirements for MTS access (P3); Part 5: AMH24 - IPMrequirements for enhanced MS access (P7)".SIST ETS 300 498-1 E1:2003

Page 11ETS 300 498-1: July 19963Definitions and abbreviations3.1DefinitionsFor the purposes of this Part of this ETS, all the definitions in the references given in clause 2 aboveapply. However, in addition, the following definitions, in the context of this ETS, apply:basic service: A fundamental service which can be a stand-alone service or part of more complexservices.client: A communicating entity requesting services provided by a server.communication application: All means and procedures to enable remote access, management andmanipulation of information by a communicating entity, and to perform the transfer of information andoperations between communicating entities. These may include remote access, management andmanipulation of document stores, documents inside document stores and document fragments insidedocuments. A communication application uses communication modules to transfer information andoperations.communicating entity: An entity which performs a communication application with the goal ofcommunicating information and operations to or from a remote communicating entity, using acommunication link. A communicating entity may be a human, hardware or software.communication link: A connection between two communicating entities.communication module: A standardized set of operations and protocols that belong to the applicationlayer.complex service: A service which can be founded on basic services, providing an enhanced task of adocument communication application.document: An ODA document.document fragment: An ODA document fragment.document store: A storage capacity with well-defined structure intended to contain documents.full document: A complete document which does not constitute a part of another document.server: A communicating entity which provides services for other communicating entities. A server maypossess and administer a document store.service: A well-defined task of a document communication application.set of document fragments: One or more document fragments.set of full documents: One or more full document.user: A human communicating entity.SIST ETS 300 498-1 E1:2003

Page 12ETS 300 498-1: July 19963.2AbbreviationsFor the purposes of this Part of this ETS, the following abbreviations apply:ACSEAssociation Control Service ElementADFApplication profile for DFRAFTApplication profile for FTAMHApplication profile for MHSAODApplication profile for ODAASEApplication Service ElementATSAbstract Test SuiteBFTBinary File TransferBSBasic ServiceBTBulk TransferCAPCommunication Application ProfileCCITTConsultative Committee on International Telegraphy and TelephonyDAPDocument Application ProfileDFRDocument Filing and RetrievalDMDocument ManipulationDOAMDistributed Office Applications ModelDSTDiSTribution basic serviceDTAMDocument Transfer And ManipulationDTAM-BT-NMDocument Transfer And Manipulation - Bulk Transfer - Normal ModeDTAM-BT-TMDocument Transfer And Manipulation - Bulk Transfer - Transparent ModeDTAM-DMDocument Transfer And Manipulation - Document ManipulationDTAM-TKDocument Transfer And Manipulation - ToKen interchangeECMError Correction ModeEFTEuroFile TransferFAX3Facsimile group 3FAX4Facsimile group 4FODInterchange Format and representation profile for ODAFODAFormal specification of ODAFTFile TransferFTAMFile Transfer, Access and ManipulationIPMInterPersonal MessagingISDNIntegrated Services Digital NetworkISPInternational Standardized ProfileISRImplementation Support RequirementsMHSMessage Handling SystemMNPMaNiPulation basic serviceMPTMulti-PoinTing basic serviceMSMessage StoreMTSMessage Transfer SystemN/ANot ApplicableNMNormal ModeODAOpen Document ArchitectureOSIOpen System InterconnectionPNTPoiNTing basic serviceQoSQuality of ServiceROAReferenced Object AccessROSERemote Operations Service ElementRTRReTRieval basic serviceRTSEReliable Transfer Service ElementSARStoring-And-Retrieval basic serviceSEService ElementSTRSToRing basic serviceTCTechnical CommitteeTETerminal EquipmentTKToKen exchangeTKIToKen-Interchange basic serviceTMTransparent ModeSIST ETS 300 498-1 E1:2003

Page 13ETS 300 498-1: July 19964Introduction to document communication basic servicesThis ETS specifies services for document communication. Some of them are considered as basicservices. More complex services, to be specified in a further ETS, are defined in terms of the basic ones.In this ETS, a methodology for the specification of services is defined (see clause 8). However, it is onlyapplied to basic services (see clause 9), while complex services are only introduced (see clause 5).Basic services use existing document and communication base standards and profiles.Two groups of basic services are considered:-basic services that, apart from being used for specifying complex services, can be implemented asstand-alone services, and then provided to users;-basic services that can only be used for specifying complex services.A number is assigned to each Basic Service (BS).The basic services that belong to the first group are:-storing (BS 1);-distribution (BS 2);-retrieval (BS 3);-storing-and-retrieval (BS 4);-manipulation (BS 5).Storing and distribution basic services apply to full documents only, while retrieval, storing-and-retrievaland manipulation basic services apply to full documents and to document fragments.The basic services that belong to the second group are:-pointing (BS 6);-multi-pointing (BS 7);-token-interchange (BS 8).Pointing and multi-pointing basic services only apply to document fragments, while the Token-Interchangebasic service (TKI) is independent of documents.There are some subset relationships between some of the basic services, but a complete hierarchybetween them does not exist. The relationships are:-storing is a subset of distribution;-storing is a subset of storing-and-retrieval;-retrieval is a subset of storing-and-retrieval;-storing-and-retrieval is a subset of manipulation;-pointing is a subset of multi-pointing.Basic services are introduced in the following subclauses with a description and some examples. Then, aclassification is given in subclause 4.3.SIST ETS 300 498-1 E1:2003

Page 14ETS 300 498-1: July 19964.1Basic services that can be stand-alone services4.1.1SToRing basic service (STR)4.1.1.1DescriptionThe STR basic service provides for storing one or more full documents from a communicating entity(sender) to a remote document store (recipient). The sender is provided with the ability to store (create)new documents at the recipient's communicating entity, but cannot read, delete or modify already storeddocuments. Before storing, the documents are located in the sender's local store. This service does notcover the case where both the sender and the recipient are different from the requesting communicatingentity (third party transfer).4.1.1.2Examples of concrete applicationsExamples of concrete applications are:-transfer of documents to a remote system;-a remote storage service, where users store documents in a common remote server.4.1.2DiSTribution basic service (DST)4.1.2.1DescriptionThe DST basic service provides for distribution of one or more full documents from a communicatingentity (sender) to several remote document stores (recipients). This service is a generalization of thestoring service in the case of more than one recipient.4.1.2.2Examples of concrete applicationsExamples of concrete applications are:-document distribution service;-distribution of electronic newsletters to registered subscribers.4.1.3ReTRieval basic service (RTR)4.1.3.1DescriptionThe RTR basic service provides for searching and retrieval, from a remote document store, of one ormore full documents or document fragments.4.1.3.2Examples of concrete applicationsExamples of concrete applications are:-read-only document server;-system for remote consultation of documents.4.1.4Storing-And-Retrieval basic service (SAR)4.1.4.1DescriptionThe SAR basic service provides for both storing, into a remote document store, and retrieval, from aremote document store, of one or more full documents or document fragments. Stored documents ordocument fragments shall not be overwritten.Searching for one or more documents or document fragments is also provided by this service.SIST ETS 300 498-1 E1:2003

Page 15ETS 300 498-1: July 1996This service is a superset of the retrieval basic service and of the storing basic service. However, it is notthe joining of storing and retrieval basic services, since storing only applies to full documents, and storing-and-retrieval applies both to full documents and to document fragments.4.1.4.2Examples of concrete applicationsExamples of concrete applications are:-storing and retrieval in a document server;-joint composition of documents, where users are not allowed to modify existing text.4.1.5MaNiPulation basic service (MNP)4.1.5.1DescriptionWith the MNP basic service, one communicating entity (client) accesses remotely to anothercommunicating entity (the document store, or server) in order to manipulate one or more documents ordocument fragments.Manipulation includes searching and reading operations, such as those provided by the retrieval basicservice.4.1.5.2Examples of concrete applicationsExamples of concrete applications are:-remote document editing;-document reading, or browsing, to make comments on content.4.2Basic services that cannot be stand-alone services4.2.1PoiNTing basic service (PNT)4.2.1.1DescriptionThe PNT basic service provides for a communicating entity to identify (to point to) a document fragmentinside a document at a remote communicating entity.4.2.1.2Examples of concrete applicationsExamples of concrete applications are:-to build a complex service such as joint viewing of documents, where one user presents documentsto another user;-to provide the facility for two users to interchange views on documents; for example one usershows, to the remote user, specific parts of a document.4.2.2Multi-PoinTing basic service (MPT)4.2.2.1DescriptionThe MPT basic service provides for a communicating entity to identify (to point to) a document fragmentinside a document in several remote communicating entities.SIST ETS 300 498-1 E1:2003

Page 16ETS 300 498-1: July 19964.2.2.2Examples of concrete applicationsExamples of concrete applications are:-to build a complex service such as joint viewing of documents, where one user presents documentsto several other users;-to provide a complex service such as joint editing of documents by several users, where, beforemodifications, affected document fragments are shown and discussed (for example by associatedtelephone conversation).4.2.3ToKen-Interchange basic service (TKI)4.2.3.1DescriptionThe TKI basic service provides for application token interchange between two communicating entities.The token indicates which communicating entity has the turn to perform further operations.4.2.3.2Examples of concrete applicationsExamples of concrete applications are:-to build a complex service, such as two users jointly editing a document in an interactive way, wherethe token is used to interchange the turn between users;-to build a complex service, such as work flow guided document production, where a token is usedto inform users about their turn to work on the document (for example, a travel order).4.3Classification of basic servicesTable 1 classifies the basic services taking into account:-services that can be implemented as stand-alone services;-services working on full documents and/or document fragments; a third case is servicesindependent of documents;-type of operations provided:-reading: information is only searched and retrieved;-adding: information is added to the documents or to the document store;-modifying: information in the documents or document store is modified;-one communicating entity associated to another communicating entity or one communicating entityassociated to several communicating entities.The following abbreviations for the basic services are used in table 1:-SToRing:STR
...