Abstract: Operationalizing a goal includes receiving the goal and execution rules associated with the goal, where one or more execution rules correspond to an execution system operable to initiate execution of the execution rules. The goal is represented in a representation language that includes a set of operations. An operation of the set of operations is applied to the goal to partition the goal into subgoals. For each subgoal, an operation of the set of operations is applied to the subgoal to derive and configure one or more execution rules associated with the subgoal. The goals, the applied operations, the subgoals, and the execution rules are recorded as operationalized knowledge to operationalize the goal.

Abstract: The present invention extends to methods, systems, and computer program products for allowing a computer system user to extend the functionality of a data-centric software application. The method includes instantiating the data-centric software application, where the data-centric application has portions of business logic categorized and associated with items of data-centric application functionality defined in a schema. The method includes receiving customization input to customize at least one of the portions of business logic. The method includes formulating a representative model corresponding to at least one of the portions of customized business logic. The method includes applying the representative model to the schema to generate a customized schema that extends the business logic of the data-centric software application.

Abstract: Validating executable data for interactions among a plurality of process artifacts at design time. A data context is created to include the plurality of process artifacts. The data context carries interaction rules among the plurality of process artifacts. The executable data from a data source is associated with the plurality of process artifacts in the created data context. A subset of the interaction rules is selected corresponding to at least one of the plurality of process artifacts. The associated executable data is validated when the associated executable data is in accordance with the selected subset of the interaction rules.

Abstract: A meta-model representing a business process. Operative expressions are defined for identifying the business process. The business process includes a plurality of activity sequences. Metadata is collected associated with the defined operative expressions. The collected metadata is formatted according to a schema. The meta-model representing the business process is provided to a user as a function of the formatted metadata and the defined operative expressions such that the user can interact with the business process using the defined operative expressions.

Abstract: Semantic rich objects for a dynamic user experience. One or more actions in the process are represented by semantic rich objects (SROs) for exposing functionality of the process. Each of the SROs includes metadata associated with an action and an execution environment therefor. In response to an interactive gesture from a user selecting at least one of the SROs to perform a desired action in the process, metadata is extracted from the selected SROs to determine whether the desired action is available in the execution environment of the process.

Abstract: Establishing relationships between one or more entities of a first application and one or more entities of a second application using metadata. At least one entity of the second application is identified for establishing a relationship with at least one entity of the first application. Metadata from the second application is received at the first application. The metadata includes information associated with the identified entity of the second application. An expression is generated, based on the metadata, specifying a relationship between the entity of the first application with the identified entity of the second application.

Abstract: Identifying a transaction from a real time event stream having latency. A method of the invention receives events from the real time event stream where events define a plurality of transactions to be identified. Each of the transactions includes a first event and a second event; the first event has a first latency relative to the real time event stream and the second event has a second latency relative to the real time event stream. The first event is identified from the received real time event stream, and a time is record when the first event is received. The method determines a time period during which the second event occurs as a function of the first latency, the recorded time of the first event, and the second latency. The transaction having the first and second events is identified based on the determined time period of the second event.

Abstract: System and method for identifying a pattern. A method of the invention compiles a pattern description where the pattern description defines a series of a first event and a second event relating to the first event. The first event is received and includes a type parameter data, a time parameter data, and a substance parameter data. A system of the invention includes a script component for associating or attaching a first script to the first event. The first script defines the type, time, and substance parameters of the second event as a function of the parameters of the first event according to the pattern description. A pattern recognition engine executes the attached first script and the executed script identifies the second event and thereby identifies the pattern.

Abstract: An application entity may be created and defined by a user at an application. Related service entities managed by different service applications may be matched and consolidated. The application entity may be associated with one or more related service entities. Metadata corresponding to the associated service entities may be provided to the application. Such metadata may enable the associated service entities to be managed from within the application.

Abstract: An application entity may be created and defined by a user at an application. Related service entities managed by different service applications may be matched and consolidated. The application entity may be associated with one or more related service entities. Metadata corresponding to the associated service entities may be provided to the application. Such metadata may enable the associated service entities to be managed from within the application.

Abstract: Workflows can be used, created, modified and saved from within the user's working environment. Workflow can be initiated by selecting actions from a menu or workflow can be triggered by actions of users. A workflow, including an in progress workflow, can be dynamically modified, for example, to fix a process that has gone awry, to change the workflow to accommodate a changing situation, or the like. An existing workflow saved as a practice may be reused or modified. A composition system builds workflows by combining workflow units within limitations imposed by a constraint system. A constraint system accesses information stored in a knowledge base to restrict the actions an initiator of an action can initiate within a particular context in the workflow or in the environment in which the workflow operates, the targets the initiator can assign a task to, and the resources with which the initiator can associated a task.

Abstract: Operationalizing a goal includes receiving the goal and execution rules associated with the goal, where one or more execution rules correspond to an execution system operable to initiate execution of the execution rules. The goal is represented in a representation language that includes a set of operations. An operation of the set of operations is applied to the goal to partition the goal into subgoals. For each subgoal, an operation of the set of operations is applied to the subgoal to derive and configure one or more execution rules associated with the subgoal. The goals, the applied operations, the subgoals, and the execution rules are recorded as operationalized knowledge to operationalize the goal.

Abstract: Information, or data, among applications in multiple diverse computer systems is represented in a uniform way allowing the data to be easily manipulated, navigated and modified. Each piece of information is stored as a uniquely identifiable object instance of one of multiple uniquely identifiable object classes that are themselves instances of a Root class. Two object instances can be linked by a uniquely identifiable two-way navigable link of a particular links class. Each link of a links class is constrained to linking object instances of either one or two different object classes. Each link also has a corresponding object instance such that the object class of the corresponding object instance is the links class, and the unique identifier of the object instance is the same in value as the unique identifier of the link.

Abstract: Information, or data, among applications in multiple diverse computer systems is represented in a uniform way allowing the data to be easily manipulated, navigated and modified. Each piece of information is stored as a uniquely identifiable object instance of one of multiple uniquely identifiable object classes that are themselves instances of a Root class. Two object instances can be linked by a uniquely identifiable two-way navigable link of a particular links class. Each link of a links class is constrained to linking object instances of either one or two different object classes. Each link also has a corresponding object instance such that the object class of the corresponding object instance is the links class, and the unique identifier of the object instance is the same in value as the unique identifier of the link.