Process and framework for facilitating information sharing using a distributed hypergraph
A knowledge model “overlay” for organizing and analyzing large, dynamic data volumes is implemented as a hypergraph that manifests as a result of a distributed theory-driven data source transformation process. This process maps exponentially growing data into an asymptotically limited information space. Within this space, real-world entities (e.g. people, computers, cities, Earth) and their complex interdependencies (e.g. social networks, connectivity, causal relationships) are represented as attributed hypergraph elements (i.e. both hypervertices and hyperedges). Attributes are represented as state vectors affixed to any hypergraph element. Transformation of source system data into this overlay structure is accomplished with minimal data movement and replication using a universal “pointer” like mechanism that is managed in a decentralized fashion by the respective transformation components. Access to the knowledge overlay is performed via a hypergraph communication protocol encapsulated within a common hypergraph API and accompanying hypergraph toolkit.
1. A process for accessing data in a distributed knowledge hypergraph, the process comprising:
submitting, by a first client device, a first request for data graphed as an element in a distributed knowledge hypergraph, wherein the first request is submitted via a common hypergraph application programming interface;
receiving, by a first hypergraph server, the first request from the first client device and determining by the first hypergraph server a reference for a location of the element, wherein the reference for the location of the data includes identification of a second hypergraph server;
messaging the second hypergraph server by the first hypergraph server in a peer-to-peer communication using a defined hypergraph transfer protocol (HGTP) based on the reference of the location of the data, wherein the message includes a request for the data and a location of the first hypergraph server;
receiving at the first hypergraph server from the second hypergraph server, the data in a return peer-to-peer communication using the defined hypergraph transfer protocol (HGTP); and
providing the data to the first client device from the first hypergraph server in a response to the first request via the common hypergraph application programming interface.
2. The process according to claim 1 , wherein determining by the first hypergraph server a reference for a location of the data includes determining embedded routing information from a universally unique identifier (UUID) assigned to the element.
3. A process for requesting information from a distributed knowledge graph, the process comprising:
formulating, at a first adapter, a query directed to a first hypergraph element of the distributed knowledge graph using a common hypergraph application programming interface for processing by a first hypergraph server associated with the first adapter, the first hypergraph server being programmed to receive queries in a format of the common hypergraph application programming interface and further being programmed to communicate with other hypergraph servers using a defined hypergraph transfer protocol (HGTP);
packaging, by the first hypergraph server, the query into a HGTP query message and forwarding the query message to a second hypergraph server in accordance with first location instructions for the first hypergraph element at a second adapter;
receiving, by the first hypergraph server, an HGTP results message from the second hypergraph server, formatting results from the HGTP results message in the format of the common hypergraph application programming interface and forwarding the formatted results to the first adapter.
4. The process according to claim 3 , wherein the query includes a request for attributes associated with the first hypergraph element.
5. The process according to claim 4 , wherein formulating the query includes providing a universally unique identifier (UUID) for first hypergraph element.
6. The process according to claim 5 , wherein formulating the query includes providing a universally unique identifier (UUID), an identifier of the method and parameters of the method for first hypergraph element.
7. The process according to claim 3 , wherein forwarding the packaged query message includes determining, by the first hypergraph server, the first location instructions for the first hypergraph element using the received UUID.
8. The process according to 3 , wherein the packaged query message includes location instructions for the first adapter.