Browse Prior Art Database

Generic Verb Definition for OAGIS Message Structure Disclosure Number: IPCOM000130390D
Original Publication Date: 2005-Oct-21
Included in the Prior Art Database: 2005-Oct-21
Document File: 4 page(s) / 42K

Publishing Venue



An XML schema definition specifies a generic verb structure that includes all attributes and elements of all verbs of the Open Applications Group Integration Specification (OAGIS).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 29% of the total text.

Page 1 of 4


YOR820050557 Derek S Jennings/Watson/IBM David D Chen, Noel Luddy, Patrick Rooney, Pankaj Sinha

Generic Verb Definition for OAGIS Message Structure

An XML schema definition is disclosed that specifies a generic verb structure for the Open Applications Group Integration Specification (OAGIS). OAGIS, which is developed by the Open Application Group (see for details), specifies a structure for XML business messages (Business Object Documents or BODs) between business entities and applications. The XML messages are constructed using an ApplicationArea and DataArea.

The ApplicationArea contains descriptive information that is generic for all messages, as well as information about applications that send a message. The DataArea contains information which is specific to the business interactions. The DataArea consists of a "Verb", which contains the message "action" and related attributes for the message, and a "Noun", which contains the business domain data for the message.

This structure of Verb and Noun promotes consistency within messages, and maximizes the reuse of each building block used to construct a message, which shortens the development cycle and learning curve required to create messaging solutions. For instance, consider a PurchaseOrder, which is a commonly used message in eCommerce transactions. The PurchaseOrder message has typical operations ("Actions") that are performed on it such as "Process", "Get", "Show", and "Acknowledge" to name a few.

OAGIS currently defines each Verb operation as a separate XML element, which requires a separate message to be created for each Operation. That is, although ProcessPurchaseOrder and ShowPurchaseOrder share the common noun "PurchaseOrder", they are two different XML message schemas required to implement the typical business transaction. Problems with this approach are: - For a business interaction that requires two schemas, two separate mapping specifications that map the business data for an application to its verb specific XML schema definitions have to be developed. - When generating Java code, each schema represents a separate group of code, (e.g., Java package). For the request and response message pattern (typical in Web Services), data has to be moved from one package to the other, which increases development activities, and runtime cost. - When a new "operation" is required for business needs, a new BOD schema has to be constructed , and a new mapping exercise has to be conducted, which is very time consuming.

Thus, there is a need to maintain a common Verb-Noun structure in messages, while avoiding the need to develop separate schemas for each business message. To do this requires that the "Operation" information for the message be moved out of the XML element definition.

This disclosure maintains the OAGIS Verb-Noun structure and defines a generic XML Verb eleme...