Abstract: A method and system for storing complex graph data. The graph data is represented by triples, quadruples, quintuples, etc. In order to speed up storage and retrieval of graph data, the data is stored in a form of triples, quadruples, quintuples, etc. in a B-tree. The B-trees are data structures that allow operations on dynamic data sets. The operations can be search, search for minimum and maximum values, insert, delete, reference to parent or child directory. The tree can be used as a dictionary or as a prioritized chain. The speed of tree operations is proportional to the height. The data is read as blocks from the same location. If a tree node is moved to an operational memory, an allocated memory block is moved and the operation executes very fast.

Abstract: A method, system and computer product for a Smart-Bricks Information System (IS), which solves the problems of lack of adaptability and lack of flexibility of information systems. In order to provide adaptability and flexibility of the IS, the enterprise's information space is divided into a plurality of universal micro-blocks—Smart-Bricks micro-systems. The Smart-Bricks IS implements the following: contains all necessary and sufficient system parts for the functioning of each micro-system (data, code, interface); self-assembles into “instantaneous info-conglomerates”-Smart-Bricks Instant Performances (SBIP); and runs under control of the Ontological Model of an enterprise subject area, which is adaptable to the changing conditions of a given subject area.

Abstract: A method for auto-generation of tags and retrieval of data form a graph-based database. A triplestore is a purpose-built database for the storage and retrieval of triples, a triple being a data entity (also known as a statement) composed of Subject-Predicate-Object. A triplestore is optimized for the storage and retrieval of triples. A query language is used for accessing to triples stored in the triplestore. A search items need to be tagged for search and retrieval. The number of tags increases as the amount of data increases. Stored data changes over time, so the old tags are deleted or replaced by the new tags. A large number of new tags must be created. The tags (i.e., autotags) are created automatically to facilitate efficient data retrieval from the triplestore.

Abstract: A system for synchronizing Custom Objects between an application and an External server includes an application interfacing to a server for synchronizing standard objects supported by the application; a plurality of Custom Objects stored on the External server, wherein the Custom Objects are not supported by the application, the application interfacing to the External server for synchronizing Custom Objects; the application storing a plurality of standard objects. The standard objects are converted to Custom Objects types supported by the Custom Object manager. The application includes a Custom Object manager for managing the Custom Objects. At least one of the Custom Object type has a workflow. The Custom Objects include a discussion with a hierarchy of comments.

Abstract: A computer-implemented method of processing business data, the method including storing data in SPO (subject-predicate-object) format in multiple databases; using a storage layer to connect to the multiple databases and maintaining a record of which data is stored in which database, the data comprising rules and axioms, the axioms representing user data; the rules and the axioms stored in the SPO format; at least one ontology representing a union of at least some rules and axioms that represent a particular data interpretation; a storage layer that permits working with data stored in different databases simultaneously and permits a user to use data from several storages simultaneously; transforming the user data based on context provided by a business application that works with specific objects and ontologies, the context being defined by a particular ontology; performing operations on the data based on triggers specified by the rules; generating new data in the same context; processing requests from a busin

Abstract: A method and system for storing complex graph data. The graph data is represented by triples, quadruples, quintuples, etc. In order to speed up storage and retrieval of graph data, the data is stored in a form of triples, quadruples, quintuples, etc. in a B-tree. The B-trees are data structures that allow operations on dynamic data sets. The operations can be search, search for minimum and maximum values, insert, delete, reference to parent or child directory. The tree can be used as a dictionary or as a prioritized chain. The speed of tree operations is proportional to the height. The data is read as blocks from the same location. If a tree node is moved to an operational memory, an allocated memory block is moved and the operation executes very fast.

Abstract: A method for data synchronization is provided. Custom Objects are stored in MICROSOFT Outlook as Outlook items. Two continual processes check if there are changes in the Outlook Items and whether these changes are saved on the hard drive. MICROSOFT Storage Items are used to store information about fields of Outlook items that have been changed and fields of Outlook items that have been saved to the hard drive. Then, information about both changed and saved fields is sent to an external server. Subsequently, notifications about successful saving of the fields on the external server are received. The information about the fields changed on the external server is received, as well. The fields changed on the external server are saved to the Outlook items. Thus, two-way synchronization between Outlook and the external server is achieved.

Abstract: A computer-implemented method of processing business data, the method including storing data in SPO (subject-predicate-object) format in multiple databases; using a storage layer to connect to the multiple databases and maintaining a record of which data is stored in which database, the data comprising rules and axioms, the axioms representing user data; the rules and the axioms stored in the SPO format; at least one ontology representing a union of at least some rules and axioms that represent a particular data interpretation; a storage layer that permits working with data stored in different databases simultaneously and permits a user to use data from several storages simultaneously; transforming the user data based on context provided by a business application that works with specific objects and ontologies, the context being defined by a particular ontology; performing operations on the data based on triggers specified by the rules; generating new data in the same context; processing requests from a busin