Abstract:
PROBLEM TO BE SOLVED: To provide a build function of a componentized workflow model. SOLUTION: Each step of a workflow is modeled as an activity having metadata describing modes of the workflow in designing, at compilation, and at execution. A user selects the activity for generating a workflow via a user interface or an application programming interface to arrange the same. The metadata associated with each activity in the workflow is collected to create permanent expression of the workflow. The user extends the workflow model by authoring a custom activity. The workflow can be executed by compilation. COPYRIGHT: (C)2006,JPO&NCIPI
Abstract:
PROBLEM TO BE SOLVED: To provide a user interface for building a work flow model made into components. SOLUTION: Each step of a work flow is modeled as activity having metadata describing various states in designing work flow steps, various states in compiling and various states in executing. A user selects the activity for creating a work flow via the user interface and arranges it. The metadata associated to the respective activity in the work flow are collected and a permanent expression of the work flow is created. The user expands the work flow model by authoring custom activity. COPYRIGHT: (C)2006,JPO&NCIPI
Abstract:
A unified data access mechanism can provide transparent access to data that is either stored locally or remotely. Application programs can direct data requests and data modifications to this singular component without foreknowledge of where the data is stored. The unified data access mechanism can work in concert with a synchronization mechanism that can maintain data synchronization between local data and remote data. Requested or modified data can be identified as stored locally or remotely based on the namespace of the data. If the data is stored remotely, the user credentials associated with the user's process space within which the application program is executing can be utilized to identify, and then provide, relevant authentication information to the remote data store, should it be required.
Abstract:
In scenarios involving a data set accessible through a protocol, operations sets may be formulated for performing various operations on the data set, and may be expressed as resource scripts according to a scripting language. However, such resource scripts may be difficult to design due to the complicated aspects of the interaction, such as asynchrony, network transport, the syntax of the scripting language, and the details of the protocol. A design environment may be devised to facilitate designers in generating resource scripts, e.g., through the manipulation of visual elements. The design environment may abstract the lower-level working details of the resource scripts, and may allow designers to focus on the logical designing of the operations set. The design environment may then automatically generate the resource script from the operations set in accordance with the constraints of the script language and the protocol.
Abstract:
An apparatus and method provide a companion application via a companion application corresponding to a host window provided by a host application, the companion window providing information or metadata descriptive of data in the host window. The host application and companion applications may be separate applications such that the host application is unaware of the companion application. The companion application may hook into the host application (e.g., via an application programming interface) and may monitor host application activities and/or data. Based on identification of data or events in the host application, the companion application may obtain information characterizing or providing a context for data provided by the host application. The host window and companion window may be attached to each other, the host window providing host application data and the companion window providing data describing the host application data.