OAGIS Approach to Reusable XML Nouns and Verbs

The Open Applications Group Integration Specification (OAGIS) employs a standardized messaging architecture based on Business Object Documents (BODs) to facilitate enterprise application integration. At the core of this approach is the separation of business actions (Verbs) from business data (Nouns), enabling organizations to build highly modular, consistent, and reusable XML message schemas across diverse business domains.

The Business Object Document (BOD) Architecture

In OAGIS, communication between disparate systems is structured around the Business Object Document. Every BOD functions as a standardized business envelope composed of two primary XML elements: * The Control Area (Verb): Defines the operational intent and processing instructions. * The Data Area (Noun): Contains the core business payload and contextual data.

This decoupled architecture forms a Verb + Noun messaging pattern, creating specific operations like ProcessPurchaseOrder, SyncItemMaster, or GetInventoryBalance.

Reusable Verbs (Actions)

OAGIS verbs define standardized actions that can be applied generically across multiple business contexts. Instead of designing custom transaction semantics for each unique document type, developers use a shared library of XML verbs.

Verbs fall into distinct interaction patterns: * Request/Response: Get and Show (queries), Process and Acknowledge (transactional commands). * Publish/Subscribe: Sync (synchronizing state across systems) and Notify (event-driven broadcasts). * Lifecycle Management: Cancel, Change, and Confirm.

Because the syntax and behavior of a verb like Sync remain identical whether applied to a customer record or a ledger entry, systems can reuse processing logic, error-handling routines, and transport workflows across integrations.

Reusable Nouns (Business Payloads)

Nouns represent canonical business entities, such as Invoice, PurchaseOrder, Employee, or BillOfMaterials. OAGIS designs nouns using standardized, common data types and modular components (Core Component Technical Specification / CCTS framework).

A noun is constructed from reusable subcomponents: * Headers: High-level metadata common to the entire business object (e.g., PurchaseOrderHeader). * Lines: Specific repeating transaction units (e.g., PurchaseOrderLine). * Standard Elements: Uniform definitions for ubiquitous data, such as addresses, party identifiers, currency codes, and timestamps.

By establishing a unified definition for a noun, OAGIS ensures that the same data structure is utilized regardless of the verb acting upon it. A PurchaseOrder structure remains constant whether it is being created (Process), updated (Change), or retrieved (Get).

Benefits of the Noun-Verb Approach

• Reduced Complexity: Decoupling action from data minimizes the number of unique schemas required to support enterprise workflows.
• Consistent Governance: Shared data elements and verbs enforce semantic consistency across disparate software applications (ERP, CRM, SCM).
• Maintainability and Extensibility: Schema updates to a noun immediately propagate across all associated actions, and organizations can extend nouns using standard user-extension areas without breaking the core verb logic.