Browse Prior Art Database

Generalized Protocol Boundary Syntax for End User and Application Interfaces

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

Publishing Venue

IBM

Related People

Singh, HS: AUTHOR

Abstract

A protocol boundary syntax is described in terms of functions and verbs that request to perform services. The description is presented from the application, end user, and application transaction programmer's view of the protocol boundary. The syntax provides the verbs (for a given function) a semantic definition of the way users interact for requested services. The definition utilizes a syntax to facilitate the description. The protocol boundary or Application Interface (API) is a means for end users or transaction applications to request information from the system. A common and generalized protocol boundary permits all classes of users and applications to interface and request higher levels of service/function in programming/systems environment.

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 28% of the total text.

Page 1 of 5

Generalized Protocol Boundary Syntax for End User and Application Interfaces

A protocol boundary syntax is described in terms of functions and verbs that request to perform services. The description is presented from the application, end user, and application transaction programmer's view of the protocol boundary. The syntax provides the verbs (for a given function) a semantic definition of the way users interact for requested services. The definition utilizes a syntax to facilitate the description. The protocol boundary or Application Interface (API) is a means for end users or transaction applications to request information from the system. A common and generalized protocol boundary permits all classes of users and applications to interface and request higher levels of service/function in programming/systems environment. The user/application normally make requests from the system in terms of verbs/commands. Therefore, a protocol boundary is a series of verbs/commands. This protocol boundary syntax describes a generalized format to represent each verb's function, syntactic format, and parameters. The syntax scheme is able to present all parameters and values that can be coded on the verb. This syntax scheme allows not only the selection of parameters and their values, but also establishes the relationship that one verb has with other verbs. The verb syntax is presented in the syntax diagram for the verb, as shown in the figure on the preceding page.

The syntax diagram shows all parameters and values that are valid for the verb. The parameters are divided into two groups: those that must be coded (required), and those that need not be coded (optional). Heavy branch lines (double lines) are used to indicate default values on optional parameters, which are used by the system for uncoded parameters. The parameters without heavy branch (double) lines have no defaults and are required. Each parameter is described in the same order as shown in the syntax diagram. If a parameter has more than one value, the values are described in the same order as shown. The default value, if there is one, is always first and is shown as an underlined heading at the beginning of the text that describes the value. The description of each parameter contains what the parameter means and what it specifies. The dependent relationship this parameter has with other parameters in the verb is also described. When the parameter has more than one value, the information that applies to the parameter as a whole is covered. The specific information for each of the values is described after the name of each value. Syntax diagrams show all the parameters and values for each verb. Each syntax diagram specifies the parameters and the choice of values for each parameter. The required parameters do not have default values. A default value is assumed (heavy branch lines) for each uncoded parameter, for most verbs. For each parameter that can have a repetition of values, the...