Abstract: One or more data items of one or more types are received, wherein each data item is associated with one or more attributes, and wherein each attribute is associated with an attribute name and an attribute value. A key is calculated for each attribute, and a determination as to whether the key is located in a dictionary is made. The key is added to the dictionary based on the determination along with an attribute description, and a determination of a number of occurrences of one of the one or more items to the number of all the one or more items in a set is made. Based on this number of occurrences attributes are classified as either mandatory, expected or optional in the generated template for the corresponding info item type.

Abstract: A computer-implemented information system involves data objects stored in the database with characteristics of such data objects defined at a design time. The system is able to associate customized data object events with at least some of the data objects subsequent to the design time to define subscriber objects. Data objects which are publisher objects are determined based on the events. In one implementation, the information system includes a messaging manager, with a message broker and an event controller associated therewith.

Abstract: Monitor services deployable on device networks may be implemented using a modular approach, in which a core monitor service is mapped to one or more devices included in, or associated with, the device networks. Additional monitoring-related functionality may be provided to such devices using plug-ins, add-on services or service components, or other service modules, which interact with the core monitor service. The core monitor service(s) and any monitor service modules may be mapped, to specific ones of the devices, based on, for example, requirements of other services and/or relevant device metadata (e.g., capabilities) of the devices. In additional or alternative implementations, various protocols may be used to register new devices and deployed monitor service(s) with the distributed monitoring service(s) in a fast, secure, energy-efficient, and reliable manner, even as devices join or leave the device network(s).

Abstract: Monitor services deployable on device networks may be implemented using a modular approach, in which a core monitor service is mapped to one or more devices included in, or associated with, the device networks. Additional monitoring-related functionality may be provided to such devices using plug-ins, add-on services or service components, or other service modules, which interact with the core monitor service. The core monitor service(s) and any monitor service modules may be mapped, to specific ones of the devices, based on, for example, requirements of other services and/or relevant device metadata (e.g., capabilities) of the devices. In additional or alternative implementations, various protocols may be used to register new devices and deployed monitor service(s) with the distributed monitoring service(s) in a fast, secure, energy-efficient, and reliable manner, even as devices join or leave the device network(s).

Abstract: A service repository is used to store at least one service in association with service metadata describing service requirements of the service. The service repository also may store one or more platform-specific service executables. A service mapper is used to determine device metadata associated with each of a plurality of devices, where the device metadata provides device characteristics of the devices. The service mapper may thus map the service to a selected device of the plurality of devices for deployment thereon, based on a matching of corresponding elements of the service requirements and the device characteristics. The service mapper also may re-map the service between devices to maintain a quality and reliability of the service.

Abstract: Monitor services deployable on device networks may be implemented using a modular approach, in which a core monitor service is mapped to one or more devices included in, or associated with, the device networks. Additional monitoring-related functionality may be provided to such devices using plug-ins, add-on services or service components, or other service modules, which interact with the core monitor service. The core monitor service(s) and any monitor service modules may be mapped, to specific ones of the devices, based on, for example, requirements of other services and/or relevant device metadata (e.g., capabilities) of the devices. In additional or alternative implementations, various protocols may be used to register new devices and deployed monitor service(s) with the distributed monitoring service(s) in a fast, secure, energy-efficient, and reliable manner, even as devices join or leave the device network(s).

Abstract: One or more operations are defined to be used against a repository of one or more items. One or more associations between each of the one or more items are also defined. A classification is associated with the one or more operations for an execution environment within a transformation graph, wherein the classification defines whether the operation can be executed in parallel or not in parallel with other operations. The operations are processed based on the classification.

Abstract: A first request to access a first set of items is received, wherein each item is associated with one or more properties. A second request to access a second set of items is also received. A determination is made as to whether items from the first set are in the second set of items, and the sets are divided into one or more subsets based on the determining. Each of the one or more subsets is assigned to a respective thread, and the respective thread of the subset that does not contain items in the second request is processed. This way, individual subsets (i.e. data partitions) can be processed by multiple threads in parallel without having to synchronize them.

Abstract: A service repository is used to store at least one service in association with service metadata describing service requirements of the service. The service repository also may store one or more platform-specific service executables. A service mapper is used to determine device metadata associated with each of a plurality of devices, where the device metadata provides device characteristics of the devices. The service mapper may thus map the service to a selected device of the plurality of devices for deployment thereon, based on a matching of corresponding elements of the service requirements and the device characteristics. The service mapper also may re-map the service between devices to maintain a quality and reliability of the service.

Abstract: In some implementations, a method includes receiving a first data set that is stored using a first format, generating an info item based on the first data set, the info item representing an entity extracted from the first, data set, generating a delta item based on the first data set, the delta item including a reference to the into item and defining a context-based modification of the info item, generating a second data set in a second format comprising the into item and the delta item, and storing the second data set to the computer-readable storage medium.

Abstract: A service repository is used to store at least one service in association with service metadata describing service requirements of the service. The service repository also may store one or more platform-specific service executables. A service mapper is used to determine device metadata associated with each of a plurality of devices, where the device metadata provides device characteristics of the devices. The service mapper may thus map the service to a selected device of the plurality of devices for deployment thereon, based on a matching of corresponding elements of the service requirements and the device characteristics. The service mapper also may re-map the service between devices to maintain a quality and reliability of the service.

Abstract: Systems, methods and computer program products, implementing techniques for automatic data acquisition and the real-time display of automatically acquired data. A system implementing the techniques includes one or more automatic data acquisition devices that emit data; and a data integration system that receives data from the automatic data acquisition devices and processes the data. The data integration system includes a display system for displaying the data to a user. The display system is operable to generate a graphical display and to update the graphical display automatically and only when new data from the automatic data acquisition devices is available. The display system is operable to update only affected parts of the graphical display but not necessarily the entire display.

Abstract: A service repository is used to store at least one service in association with service metadata describing service requirements of the service. The service repository also may store one or more platform-specific service executables. A service mapper is used to determine device metadata associated with each of a plurality of devices, where the device metadata provides device characteristics of the devices. The service mapper may thus map the service to a selected device of the plurality of devices for deployment thereon, based on a matching of corresponding elements of the service requirements and the device characteristics. The service mapper also may re-map the service between devices to maintain a quality and reliability of the service.

Abstract: Modeling a component-based application includes modeling communication capabilities of components of the application, modeling a plan for interlinking components of the application, modeling communications capabilities of a compound component composed of a plurality of constituent components, and determining if interlinked components are compatible to communicate validly in the application.

Abstract: In one embodiment the present invention includes a plurality of processes for storing data. The processes may include identifiers for specifying other processes representing other resources. In one embodiment, the processes store link types for specifying a relationship type between the resource represented by the process and other resources represented by other processes. Processes may represent data elements and the links may represent relationships between the data. Queries may be conducted across the data in parallel by sending messages to the processes. In one embodiment, the processes represent RDF subjects and RDF objects, and the links represent RDF predicates. Queries for RDF data satisfying predefined criteria or relationships can be performed in parallel by executing processes at the same time on different threads on one or more CPUs.

Abstract: Among other disclosed subject matter, a computer program product is tangibly embodied in a computer-readable storage medium and includes instructions that when executed by a processor perform a method for recording information about an item. The method includes assigning a unique identifier to an item in a repository, the item supporting versioning and being subject to a data model having no predefined schema for items. The method includes associating a first attribute with the unique identifier, the first attribute being part of the item and being configured for modification. The method includes associating the first attribute with a version number, wherein the versioning is supported without recording in the repository a time period when the first attribute is valid.

Abstract: One or more data items of one or more types are received, wherein each data item is associated with one or more attributes, and wherein each attribute is associated with an attribute name and an attribute value. A key is calculated for each attribute, and a determination as to whether the key is located in a dictionary is made. The key is added to the dictionary based on the determination along with an attribute description, and a determination of a number of occurrences of one of the one or more items to the number of all the one or more items in a set is made. Based on this number of occurrences attributes are classified as either mandatory, expected or optional in the generated template for the corresponding info item type.

Abstract: A first request to access a first set of items is received, wherein each item is associated with one or more properties. A second request to access a second set of items is also received. A determination is made as to whether items from the first set are in the second set of items, and the sets are divided into one or more subsets based on the determining. Each of the one or more subsets is assigned to a respective thread, and the respective thread of the subset that does not contain items in the second request is processed. This way, individual subsets (i.e. data partitions) can be processed by multiple threads in parallel without having to synchronize them.

Abstract: One or more operations are defined to be used against a repository of one or more items. One or more associations between each of the one or more items are also defined. A classification is associated with the one or more operations for an execution environment within a transformation graph, wherein the classification defines whether the operation can be executed in parallel or not in parallel with other operations. The operations are processed based on the classification.

Abstract: A modeling tool may be configured to generate a diagrammatic representation of a service-based process, expressed using a diagrammatic modeling language. A model converter may be configured to convert the diagrammatic representation into a formal model of the service-based process, and a model verifier configured to apply constraints to the formal model to verify an operation of the service-based process and output a verified formal model. A code generator may be configured to generate executable code therefrom for executing the service-based process therewith.