Browse Prior Art Database

Generalized Protocol Boundary for DOCUMENT Interchange

IP.com Disclosure Number: IPCOM000062096D
Original Publication Date: 1986-Oct-01
Included in the Prior Art Database: 2005-Mar-09
Document File: 4 page(s) / 51K

Publishing Venue

IBM

Related People

Singh, HS: AUTHOR

Abstract

The protocol boundary is described in terms of a set of functions and verbs that request Document Interchange (DIA) to perform services. The description is presented from the application or transaction programmer's view of the DIA protocol boundary. The verbs (for a given function) provide a semantic definition of the way application transaction programs interact with the DIA services. The definition utilizes a syntax to facilitate its description. The products do not have to provide an interface that exactly matches this syntax. However, they must support the semantics of the definition. An overview of the DIA verbs in terms of their functions is first described. These verbs can be classified into four distinct functions. 1.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 38% of the total text.

Page 1 of 4

Generalized Protocol Boundary for DOCUMENT Interchange

The protocol boundary is described in terms of a set of functions and verbs that request Document Interchange (DIA) to perform services. The description is presented from the application or transaction programmer's view of the DIA protocol boundary. The verbs (for a given function) provide a semantic definition of the way application transaction programs interact with the DIA services. The definition utilizes a syntax to facilitate its description. The products do not have to provide an interface that exactly matches this syntax. However, they must support the semantics of the definition. An overview of the DIA verbs in terms of their functions is first described. These verbs can be classified into four distinct functions. 1. SESSION CONTROL FUNCTIONS DIA Session Services are used to establish, maintain, and terminate DIA sessions. The summary of these functions is: The SIGN_ON function is used to establish a DIA session, negotiate the DIA functions that can be performed in that session, and enable the DIA processes to validate each other's authority to exchange information. The SIGN_OFF function terminates the DIA session. The SET_CONTROL_VALUE function provides the ability for one DIA process to establish, change, or delete the value associated with a control variable that is defined at the receiving DIA process, e.g., a password. 2. DOCUMENT DISTRIBUTION SERVICE FUNCTIONS The Document Distribution Services deliver information, such as messages or documents, within an office systems network. The information can be distributed directly between two nodes; Source Node (SN) or Recipient Node (RN), or through an office systems node (OSN) for subsequent delivery. The summary of these functions is: The CANCEL_DISTRIBUTION function cancels distribution status information or cancels the delivery of distributed documents or messages. This function is described in detail later. The DELIVER function is used to directly transport documents and/or messages between source and recipient nodes. The LIST function requests delivery of a list of documents and/or messages queued for delivery at an OSN or status for previous request. The OBTAIN function requests delivery of one or more documents and/or messages scheduled for delivery to the requestor. The PROCESS_BIT_STRING function allows an OSN to interpret a bit- stream representation to a DIA function request and perform the requested operation. The REQUEST_DISTRIBUTION function transports documents and/or messages from a Source Node (SN) to an OSN for distribution to the specified Recipient Nodes (RN). 3. DOCUMENT LIBRARY SERVICES FUNCTIONS The Document Library Services provide for maintaining user documents in a document library. The summary for these functions is as follows: The DELETE function permanently removes access to the identified document. The FILE1 function preserves the identified document in the library for an authorized docume...