Additional SOA Patterns –Supporting Composition Controllers - Applied SOA Patterns on the Oracle Platform - page 554

We believe that even if oversimplified, this complex business case is descriptive enough
to understand the 3D nature of complex business events. Every business object such as a
consolidated Voyage Schedule can only be seen in the following scenarios:
• In the context of other supporting business objects, such as ports, port calls and
their purposes, vessels, and crew
• With an object's historical retrospective (history of the port calls, crew shifts, and
so on)
• It can also be seen as an unbounded set of uncorrelated object data streams re-
gistered by event interceptors
In this matrix, we have the following properties of parameterized events, which comprise
the Object Context XSD part:
• Stage : This is the historical indicator on the time axis for the object entity. The-
oretically, it can be endless, but at present, DB practice can have new and old val-
ues.
• ParameterName : This is how a parameter is identified as an object's property.
• Value : This is the parameter's actual value.