Patent Application
20150149470
The present disclosure relates to the field of computers, and specifically to the use of computers in managing data. Still more particularly, the present disclosure relates to sorting and categorizing data.
Data are values of variables, which typically belong to a set of items. Examples of data include numbers and characters, which may describe a quantity or quality of a subject. Other data can be processed to generate a picture or other depiction of the subject. Data management is the development and execution of architectures, policies, practices and procedures that manage the data lifecycle needs of an enterprise. Examples of data management include storing data in a manner that allows for efficient future data retrieval of the stored data.
A processor-implemented method, system, and/or computer program product defines multiple context-based conformed dimensional data gravity wells on a context-based conformed dimensional data gravity wells membrane. Conformed dimensional objects and synthetic context-based objects are parsed into n-tuples. A virtual mass of each parsed object is calculated, in order to define a shape of the multiple context-based conformed dimensional data gravity wells that are created when data objects that are pulled into each of the context-based conformed dimensional data gravity well frameworks on a context-based conformed dimensional gravity wells membrane.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
With reference now to the figures, and in particular to
Exemplary computer 102 includes a processor 104 that is coupled to a system bus 106. Processor 104 may utilize one or more processors, each of which has one or more processor cores. A video adapter 108, which drives/supports a display 110, is also coupled to system bus 106. System bus 106 is coupled via a bus bridge 112 to an input/output (I/O) bus 114. An I/O interface 116 is coupled to I/O bus 114. I/O interface 116 affords communication with various I/O devices, including a keyboard 118, a mouse 120, a media tray 122 (which may include storage devices such as CD-ROM drives, multi-media interfaces, etc.), a printer 124, and external USB port(s) 126. While the format of the ports connected to I/O interface 116 may be any known to those skilled in the art of computer architecture, in one embodiment some or all of these ports are universal serial bus (USB) ports.
As depicted, computer 102 is able to communicate with a software deploying server 150, using a network interface 130. Network interface 130 is a hardware network interface, such as a network interface card (NIC), etc. Network 128 may be an external network such as the Internet, or an internal network such as an Ethernet or a virtual private network (VPN).
A hard drive interface 132 is also coupled to system bus 106. Hard drive interface 132 interfaces with a hard drive 134. In one embodiment, hard drive 134 populates a system memory 136, which is also coupled to system bus 106. System memory is defined as a lowest level of volatile memory in computer 102. This volatile memory includes additional higher levels of volatile memory (not shown), including, but not limited to, cache memory, registers and buffers. Data that populates system memory 136 includes computer 102's operating system (OS) 138 and application programs 144.
OS 138 includes a shell 140, for providing transparent user access to resources such as application programs 144. Generally, shell 140 is a program that provides an interpreter and an interface between the user and the operating system. More specifically, shell 140 executes commands that are entered into a command line user interface or from a file. Thus, shell 140, also called a command processor, is generally the highest level of the operating system software hierarchy and serves as a command interpreter. The shell provides a system prompt, interprets commands entered by keyboard, mouse, or other user input media, and sends the interpreted command(s) to the appropriate lower levels of the operating system (e.g., a kernel 142) for processing. Note that while shell 140 is a text-based, line-oriented user interface, the present invention will equally well support other user interface modes, such as graphical, voice, gestural, etc.
As depicted, OS 138 also includes kernel 142, which includes lower levels of functionality for OS 138, including providing essential services required by other parts of OS 138 and application programs 144, including memory management, process and task management, disk management, and mouse and keyboard management.
Application programs 144 include a renderer, shown in exemplary manner as a browser 146. Browser 146 includes program modules and instructions enabling a world wide web (WWW) client (i.e., computer 102) to send and receive network messages to the Internet using hypertext transfer protocol (HTTP) messaging, thus enabling communication with software deploying server 150 and other computer systems.
Application programs 144 in computer 102's system memory (as well as software deploying server 150's system memory) also include a context-based conformed dimensional data gravity well logic (CBCDDGWL) 148. CBCDDGWL 148 includes code for implementing the processes described below, including those described in
Note that the hardware elements depicted in computer 102 are not intended to be exhaustive, but rather are representative to highlight essential components required by the present invention. For instance, computer 102 may include alternate memory storage devices such as magnetic cassettes, digital versatile disks (DVDs), Bernoulli cartridges, and the like. These and other variations are intended to be within the spirit and scope of the present invention.
With reference now to
Within system 200 is a synthetic context-based object database 202, which contains multiple synthetic context-based objects 204a-204n (thus indicating an “n” quantity of objects, where “n” is an integer). Each of the synthetic context-based objects 204a-204n is defined by at least one non-contextual data object and at least one context object. That is, at least one non-contextual data object is associated with at least one context object to define one or more of the synthetic context-based objects 204a-204n. The non-contextual data object ambiguously relates to multiple subject-matters, and the context object provides a context that identifies a specific subject-matter, from the multiple subject-matters, of the non-contextual data object.
Note that the non-contextual data objects contain data that has no meaning in and of itself. That is, the data in the context objects are not merely attributes or descriptors of the data/objects described by the non-contextual data objects. Rather, the context objects provide additional information about the non-contextual data objects in order to give these non-contextual data objects meaning. Thus, the context objects do not merely describe something, but rather they define what something is. Without the context objects, the non-contextual data objects contain data that is meaningless; with the context objects, the non-contextual data objects become meaningful.
For example, assume that a non-contextual data object database 206 includes multiple non-contextual data objects 208r-208t (thus indicating a “t” quantity of objects, where “t” is an integer). However, data within each of these non-contextual data objects 208r-208t by itself is ambiguous, since it has no context. That is, the data within each of the non-contextual data objects 208r-208t is data that, standing alone, has no meaning, and thus is ambiguous with regards to its subject-matter. In order to give the data within each of the non-contextual data objects 208r-208t meaning, they are given context, which is provided by data contained within one or more of the context objects 210x-210z (thus indicating a “z” quantity of objects, where “z” is an integer) stored within a context object database 212. For example, if a pointer 214a points the non-contextual data object 208r to the synthetic context-based object 204a, while a pointer 216a points the context object 210x to the synthetic context-based object 204a, thus associating the non-contextual data object 208r and the context object 210x with the synthetic context-based object 204a (e.g., storing or otherwise associating the data within the non-contextual data object 208r and the context object 210x in the synthetic context-based object 204a), the data within the non-contextual data object 208r now has been given unambiguous meaning by the data within the context object 210x. This contextual meaning is thus stored within (or otherwise associated with) the synthetic context-based object 204a.
Similarly, if a pointer 214b associates data within the non-contextual data object 208s with the synthetic context-based object 204b, while the pointer 216c associates data within the context object 210z with the synthetic context-based object 204b, then the data within the non-contextual data object 208s is now given meaning by the data in the context object 210z. This contextual meaning is thus stored within (or otherwise associated with) the synthetic context-based object 204b.
Note that more than one context object can give meaning to a particular non-contextual data object. For example, both context object 210x and context object 210y can point to the synthetic context-based object 204a, thus providing compound context meaning to the non-contextual data object 208r shown in
Note also that while the pointers 214a-214b and 216a-216c are logically shown pointing toward one or more of the synthetic context-based objects 204a-204n, in one embodiment the synthetic context-based objects 204a-204n actually point to the non-contextual data objects 208r-208t and the context objects 210x-210z. That is, in one embodiment the synthetic context-based objects 204a-204n locate the non-contextual data objects 208r-208t and the context objects 210x-210z through the use of the pointers 214a-214b and 216a-216c.
Consider now an exemplary case depicted in
In the example shown in
Associated with the synthetic context-based object 304b is a context object 310z, which provides the context/datum of “music” to the term “rock” provided by the non-contextual data object 308r. Thus, the synthetic context-based object 304a defines “rock” as that which is related to the subject-matter “geology”, including minerals and/or gemstones, while synthetic context-based object 304b defines “rock” as that which is related to the subject-matter “entertainment”, including music.
In one embodiment, the data within a non-contextual data object is even more meaningless if it is merely a combination of numbers and/or letters. For example, consider the data “104-106” contained within a non-contextual data object 408r depicted in
In the example shown in
Associated with the synthetic context-based object 404b is a context object 410y, which provides the context data of “degrees on the Fahrenheit scale” and “human” to the term/values “104-106” provided by the non-contextual data object 408r. Thus, the synthetic context-based object 404b now defines term/values “104-106” as that which is related to the subject matter of “human fever”. Similarly, associated with the synthetic context-based object 404n is a context object 410z, which provides the context data of “atmospheres” to the term/values “104-106” provided by the non-contextual data object 408r. In this case, the generator of the synthetic context-based object database 202 determines that high numbers of atmospheres are used to define deep ocean pressures. Thus, the synthetic context-based object 404n now defines term/values “104-106” as that which is related to the subject matter of “deep oceanography”.
In one embodiment, the non-contextual data object may provide enough self-context to identify what the datum is, but not what it means and/or is used for. For example, consider the datum “statin” contained within the non-contextual data object 508r shown in
Associated with the synthetic context-based object 504b is a context object 510y, which provides the context/datum of “antioxidant” to the term “statin” provided by the non-contextual data object 508r. That is, a statin has properties both as a cholesterol reducer as well as an antioxidant. Thus, a statin can be considered in the context of reducing cholesterol (i.e., as described by the subject-matter of synthetic context-based object 504a), or it may be considered in the context of being an antioxidant (i.e., as related to the subject-matter of synthetic context-based object 504b). Similarly, a statin can also be an anti-inflammatory medicine. Thus, associated with the synthetic context-based object 504n is the context object 510z, which provides the context data of “anti-inflammatory medication” to the term “statin” provided by the non-contextual data object 508r. This combination identifies the subject-matter of the synthetic context-based object 504n as “tissue inflammation”.
With reference now to
Within system 600 is a conformed dimensional object database 602, which contains multiple conformed dimensional objects 604a-604n (thus indicating an “n” quantity of objects, where “n” is an integer). Each of the conformed dimensional objects 604a-604n is defined by at least one non-dimensional data object and at least one dimension object. That is, at least one non-dimensional data object is associated with at least one dimension object to define one or more of the conformed dimensional objects 604a-604n. The non-dimensional data object is merely a value/number, and has no dimensions (e.g., meters, product units, kilograms, etc.).
For example, assume that a non-dimensional data object database 606 includes multiple non-dimensional data objects 608r-608t (thus indicating a “t” quantity of objects, where “t” is an integer). However, data within each of these non-dimensional data objects 608r-608t by itself is meaningless, since it has no dimensions. That is, the data within each of the non-dimensional data objects 608r-608t is data that, standing alone, has no meaning, since it could be describing a number of inches, a number of feet, a number of meters, etc. (i.e., it is dimensional-less). In order to give the data within each of the non-dimensional data objects 608r-608t dimensional meaning, they are given dimension, which is provided by data contained within one or more of the dimension objects 610x-610z (thus indicating a “z” quantity of objects, where “z” is an integer) stored within a dimension object database 612. For example, if a pointer 614a points the non-dimensional data object 608r to the conformed dimensional object 604a, while a pointer 616a points the dimension object 610x to the conformed dimensional object 604a, thus associating the non-dimensional data object 608r and the dimension object 610x with the conformed dimensional object 604a (e.g., storing or otherwise associating the data within the non-dimensional data object 608r and the dimension object 610x in the conformed dimensional object 604a), the data within the non-dimensional data object 608r now has been given a label/dimension. This dimensional label/meaning is thus stored within (or otherwise associated with) the conformed dimensional object 604a.
Similarly, if a pointer 614b associates data within the non-dimensional data object 608s with the conformed dimensional object 604b, while the pointer 616c associates data within the dimension object 610z with the conformed dimensional object 604b, then the data within the non-dimensional data object 608s is now given a dimension/label by the data in the dimension object 610z. This dimensional meaning is thus stored within (or otherwise associated with) the conformed dimensional object 604b.
Note that more than one dimension object can give meaning to a particular non-dimensional data object. For example, both dimension object 610x and dimension object 610y can point to the conformed dimensional object 604a, thus providing compound dimensional meaning to the non-dimensional data object 608r shown in
Note also that while the pointers 614a-614b and 616a-616c are logically shown pointing toward one or more of the conformed dimensional objects 604a-604n, in one embodiment the conformed dimensional objects 604a-604n actually point to the non-dimensional data objects 608r-608t and the dimension objects 610x-610z. That is, in one embodiment the conformed dimensional objects 604a-604n locate the non-dimensional data objects 608r-608t and the dimension objects 610x-610z through the use of the pointers 614a-614b and 616a-616c.
With reference now to
In order to properly utilize the synthetic context-based objects 706, a synthetic context-based object parsing logic 708 parses the synthetic context-based objects 706 into parsed synthetic context-based objects 710. These parsed synthetic context-based objects 710 make up an n-tuple (i.e., an ordered list of “n” descriptive elements (where “n” is an integer)) that describe each of the synthetic context-based objects 706. In one embodiment, this n-tuple includes a pointer (e.g., a locating pathway) to the non-contextual data object in the synthetic context-based object. This pointer may be to a storage location (e.g., a universal resource locator (URL) address at which the non-contextual data object is stored), such that the synthetic context-based objects 706 must be generated, or the pointer may be local (such that the synthetic context-based objects 706 exist locally as part of a streaming data packet, etc.). In one embodiment, the n-tuple also includes a probability value that a non-contextual data object has been associated with a correct context object. That is, a correct context object may or may not be associated with a particular non-contextual data object. For example, the non-contextual data object may be incomplete (i.e., a fragment, a corrupted version, etc.) version of the actual non-contextual data. As such, a “guess” must be made to determine which context data should be associated with that corrupted non-contextual data. In this example, assume that the corrupted non-contextual data object contains the value “3.13”, and that the data is related to areas of circles. If the value of the non-contextual data object had been “3.14159”, then there is a high probability (e.g., is predetermined to have a 99% probability) that the context of this data object is the ratio of a circle's area divided by that circle's radius-squared (i.e., is “pi”). However, a predetermination may be made, based on probability calculations such as those using a Bayesian probability formula, that the likelihood of “3.13” being the ratio of a circle's area divided by that circle's radius-squared is only 85%.
In one embodiment, one of the parameters/values from the n-tuple is a weighting factor of importance of the synthetic context-based object. In one embodiment, this weighting factor is how “important” this particular synthetic context-based object is to an enterprise's project. For example, assume that an enterprise project is to track sales of a particular product at a particular store. If the synthetic context-based object contains information regarding an average sale price of units of a particular product sold at this particular store during a particular time period, then this synthetic context-based object is given (either manually or by an algorithm) an “importance” rating of 95 out of 100. However, if the synthetic context-based object describes whether the items are “red” or “blue” in color, such information is deemed less important (e.g., is given an “importance” rating of 30 out of 100). Note that an algorithm to determine (and/or predetermine) these importance ratings can utilize flags, metadata, etc. to determine the importance of the synthetic context-based objects. For example, assume that a particular synthetic context-based object has a flag indicating that it describes an average price for products sold at a particular store on a particular day. Assume further that a software program for an enterprise project to track such products also has this flag. Thus, if the two flags match, then a high level of importance (e.g., over 95 on a scale of 100) is assigned to synthetic context-based objects that have this flag.
The parsed synthetic context-based objects 710 are then sent to a context-based conformed dimensional data gravity wells membrane 712. The context-based conformed dimensional data gravity wells membrane 712 is a virtual mathematical membrane that is capable of supporting multiple context-based conformed dimensional data gravity wells. That is, the context-based conformed dimensional data gravity wells membrane 712 is a mathematical framework that is part of a program such as CBCDDGWL 148 shown in
With reference now to
In order to properly utilize the conformed dimensional objects 806, a conformed dimensional object parsing logic 808 parses the conformed dimensional objects 806 into parsed conformed dimensional objects 810. These parsed conformed dimensional objects 810 make up an n-tuple (i.e., an ordered list of “n” descriptive elements (where “n” is an integer)) that describe each of the conformed dimensional objects 806. In one embodiment, this n-tuple includes a pointer (e.g., a locating pathway) to the non-dimensional data object in the conformed dimensional object. This pointer may be to a storage location (e.g., a universal resource locator (URL) address at which the non-dimensional data object is stored), such that the conformed dimensional objects 806 must be generated, or the pointer may be local (such that the conformed dimensional objects 806 exist locally as part of a streaming data packet, etc.). In one embodiment, the n-tuple also includes a probability value that a non-dimensional data object has been associated with a correct dimension object. That is, a correct dimension object may or may not be associated with a particular non-dimensional data object. For example, the non-dimensional data object may be incomplete (i.e., a fragment, a corrupted version, etc.) version of the actual non-dimensional data. As such, a “guess” must be made to determine which dimension data should be associated with that corrupted non-dimensional data. In this example, assume that the corrupted non-dimensional data object contains the value “3.13”, and that the data is related to areas of circles. If the value of the non-dimensional data object had been “3.14159”, then there is a high probability (e.g., is predetermined to have a 99% probability) that this data object is the ratio of a circle's area divided by that circle's radius-squared (i.e., is “pi”). However, a predetermination may be made, based on probability calculations such as those using a Bayesian probability formula, that the likelihood of “3.13” being the ratio of a circle's area divided by that circle's radius-squared is only 85%.
In one embodiment, one of the parameters/values from the n-tuple is a weighting factor of importance of the conformed dimensional object. In one embodiment, this weighting factor is how “important” this particular conformed dimensional object is to an enterprise's project. For example, assume that an enterprise project is to track sales of a particular product at a particular store. If the conformed dimensional object contains information regarding how many units of this particular product have been sold at this store during a particular time period, then this conformed dimensional object is given (either manually or by an algorithm) an “importance” rating of 95 out of 100. However, if the conformed dimensional object describes whether the items are being paid for with cash or credit cards, such information is deemed less important (e.g., is given an “importance” rating of 30 out of 100). Note that an algorithm to determine (and/or predetermine) these importance ratings can utilize flags, metadata, etc. to determine the importance of the conformed dimensional objects. For example, assume that a particular conformed dimensional object has a flag indicating that it describes a quantity of products sold at a particular store on a particular day. Assume further that a software program for an enterprise project to track such products also has this flag. Thus, if the two flags match, then a high level of importance (e.g., over 95 on a scale of 100) is assigned to conformed dimensional objects that have this flag.
The parsed conformed dimensional objects 810 are then sent to the context-based conformed dimensional data gravity wells membrane 712, which is described above as depicted in
Note that context-based conformed dimensional data gravity well framework 902 is not yet populated with any parsed objects, and thus is not yet a context-based conformed dimensional data gravity well. However, context-based conformed dimensional data gravity well framework 906 is populated with parsed objects 908, which are synthetic context-based objects and/or conformed dimensional objects, and thus has been transformed into a context-based conformed dimensional data gravity well 910. This transformation occurred when context-based conformed dimensional data gravity well framework 906, which contains (i.e., logically includes and/or points to) a non-contextual data object 904b, a context object 912b, and a dimension object 913b, one or more of which is part of each of the captured parsed objects 908 was populated with one or more parsed objects. As stated above, each of the captured parsed objects 908 may be either a synthetic context-based object or a conformed dimensional object.
Note that parsed objects 901 are streaming in real-time from a data source across the context-based conformed dimensional data gravity wells membrane 712. If a particular parsed object is never pulled into any of the context-based conformed dimensional data gravity wells on the context-based conformed dimensional data gravity wells membrane 712, then that particular parsed object simply continues to stream to another destination, and does not affect the size and/or location of any of the context-based conformed dimensional data gravity wells.
Consider now context-based conformed dimensional data gravity well 916. Note that context-based conformed dimensional data gravity well 916 includes two dimension objects 913c-913d as well as two context objects 912c-912d and a non-contextual data object 904c. The presence of dimension objects 913c-913d and context objects 912c-912d (which in one embodiment are graphically depicted on the walls of the context-based conformed dimensional data gravity well 916) causes objects such as parsed object 914b (which in one embodiment contains both dimension objects 913c and 913d and/or both context objects 912c-912d and/or non-contextual data object 904c) to be pulled into context-based conformed dimensional data gravity well 916. Note further that context-based conformed dimensional data gravity well 916 is depicted as being larger than context-based conformed dimensional data gravity well 910 or context-based conformed dimensional data gravity well 920, since there are more objects (918) in context-based conformed dimensional data gravity well 916 than there are in these other context-based conformed dimensional data gravity wells. That is, it is the quantity of objects that have been pulled into a particular context-based conformed dimensional data gravity well that determines the size and shape of that particular context-based conformed dimensional data gravity well. The fact that context-based conformed dimensional data gravity well 916 has two dimension objects 912c-912d and two context objects 912c-912d, while context-based conformed dimensional data gravity wells 910/920 have only one dimension object 913b/913e and one context object 912b/912e, has no bearing on the size of the context-based conformed dimensional data gravity wells 910/920. Rather, the size and shape of the context-based conformed dimensional data gravity wells 910/916/920 in this embodiment is based solely on the quantity of parsed objects that are pulled in.
Note that, in one embodiment, the context-based conformed dimensional data gravity wells depicted in
In one embodiment, the context-based conformed dimensional data gravity well frameworks and/or context-based conformed dimensional data gravity wells described in
With reference now to
As depicted in block 1008, the processor parses each of the streaming objects into an n-tuple. For the conformed dimensional objects, each n-tuple comprises a pointer to one of the non-dimensional data objects, a probability that a non-dimensional data object has been associated with a correct dimension object, and a weighting factor of importance of the conformed dimensional object. For the synthetic context-based objects, each n-tuple comprises a pointer to one of the non-contextual data objects, a probability that a non-contextual data object has been associated with a correct context object, and a weighting factor of importance of the synthetic context-based object. In one embodiment, the n-tuple also includes a probability that a particular object is uncorrupted. For example, if it is determined that a particular object is a fragment of an original object (e.g., by comparing the length, format, and other features of that object with known lengths, formats, and other features of data/objects coming from the same data/object source as that particular object), then a probability can be assessed as to whether that particular object is corrupted. For example, if a particular data object from “Source A” is 32 characters long, while a typical (e.g., 90% of the data objects from Source A) data object from Source A is 30 characters long, then it is likely (e.g., 80% probable) that this particular data object has been corrupted with additional data. Similarly, if a particular data object from Source A is 22 characters long, while a typical (e.g., 99% of the data objects from Source A) data object from Source A is 30 characters long, then it is likely (e.g., 99% probable) that this particular data object has been corrupted by having certain bits truncated/removed.
With respect to block 1010, the processor calculates a virtual mass of each of the parsed objects. In one embodiment, the virtual mass of the parsed object is derived by calculating the virtual mass of a parsed synthetic context-based object by using the formula Pc(C)×Wtd(S), where Pc(C) is the probability that the non-contextual data object has been associated with the correct context object, and where Wtd(S) is the weighting factor of importance of the synthetic context-based object; and by calculating the virtual mass of a parsed conformed dimensional object by using the formula Pd(C)×Wtd(S), where Pd(C) is the probability that 1) said one of the non-dimensional data objects has been associated with the correct dimensional label, 2) said one of the non-dimensional data objects is uncorrupted, and 3) said one of the non-dimensional data objects has come from a data source whose data has been predetermined to be appropriate for storage in a particular context-based conformed dimensional data gravity well; and where Wtd(S) is the weighting factor of importance of the conformed dimensional object. The probabilities of 1) and 2) occurring are discussed above. The probability of 3) occurring can be predetermined by assigning one or more flags or other markers to each of the context-based conformed dimensional data gravity wells. For example, assume that these flags/markers identify five characteristics (e.g., length of the data, format of the data, time/date of when the data is generated, how frequently identical data is generated, and a source type (e.g., point of sales stations, stored databases, websites, etc.) of the data) of data that will be accepted in a particular context-based conformed dimensional data gravity well. If a certain non-dimensional data object has four of these flags/markers (e.g., as part of its n-tuple), then there may be a 90% probability that this non-dimensional data object is appropriate for storage within the particular context-based conformed dimensional data gravity well that has the five flags/markers. However, if a certain non-dimensional data object has only three of these flags/markers (e.g., as part of its n-tuple), then there may be only a 50% probability that this non-dimensional data object is appropriate for storage within that same particular context-based conformed dimensional data gravity well.
Continuing with the overall formula P(C)×Wt(S), Wt(S) is the weighting factor of importance of the conformed dimensional object. As described herein, in one embodiment the weighting factor of importance of the conformed dimensional object is based on how important the conformed dimensional object is to a particular project.
As described in block 1012, the processor creates multiple context-based conformed dimensional data gravity well frameworks on a context-based conformed dimensional data gravity wells membrane. Each of the multiple context-based conformed dimensional data gravity well frameworks comprises at least one dimension object, at least one non-contextual data object, and at least one context object. As described herein, the context-based conformed dimensional data gravity wells membrane is a virtual mathematical membrane that is capable of supporting multiple context-based conformed dimensional data gravity wells.
As described in block 1014, multiple parsed objects are then transmitted to the context-based conformed dimensional data gravity wells membrane. That is, these parsed objects are then transmitted to an algorithmic environment in which the logic-enabled context-based conformed dimensional data gravity well frameworks exist. These context-based conformed dimensional data gravity well frameworks are algorithmically generated based on their ability to attract specific objects. As described in block 1016, this pulling/attraction enables the processor to define multiple context-based conformed dimensional data gravity wells according to the virtual mass of multiple parsed objects that are pulled into each of the context-based conformed dimensional data gravity well frameworks. As described herein, each of the multiple parsed objects is pulled into a particular context-based conformed dimensional data gravity well in response to values from its n-tuple matching at least one dimensional object, at least one non-contextual data object, at least one context object, and/or other probability factors described herein, that is part of the particular context-based conformed dimensional data gravity well.
In one embodiment, the generated context-based conformed dimensional data gravity wells are presented on a display according to a combined virtual mass of the multiple parsed objects that populate each context-based conformed dimensional data gravity well. That is, a first context-based conformed dimensional data gravity well that holds a more virtually massive combination of parsed objects than a second context-based conformed dimensional data gravity well will be larger, and thus is visually depicted on a display as extending farther away from the context-based conformed dimensional data gravity wells membrane than the second context-based conformed dimensional data gravity well.
In one embodiment, the construction of the context-based conformed dimensional data gravity wells is temporally dynamic. That is, in this embodiment, the processor determines an age (i.e., how “stale” or “old”) each of the multiple parsed objects that have been pulled into the particular context-based conformed dimensional data gravity well is. Based on the age of each of these objects, the processor removes, from the particular context-based conformed dimensional data gravity well that holds a stale object, any parsed object that is older than a predetermined age.
In one embodiment, a likelihood that a particular object is pulled into an appropriate context-based conformed dimensional data gravity well is performed using a Bayesian probability formula. That is, an appropriate context-based conformed dimensional data gravity well is defined as a context-based conformed dimensional data gravity well whose framework includes at least one non-contextual data object, at least one context object, and/or at least one dimension object found in a parsed object that is pulled into that particular (appropriate) context-based conformed dimensional data gravity well.
For example, in order to determine a likelihood that a particular object is pulled into an appropriate context-based conformed dimensional data gravity well, assume that A represents the event that a particular object is a good populator of a particular context-based conformed dimensional data gravity well, and B represents the event that the particular object has a predefined amount of conformed dimension/context objects applied to its data object. This results in the Bayesian probability formula of:
where:
P(A|B) is the probability that a particular data object will be an appropriate populator of a particular context-based conformed dimensional data gravity well (A) given that (I) a predefined amount of conformed dimension/context objects are applied to the data object in a context-based or conformed dimensional object (B);
P(B|A) is the probability that the predefined amount of context-based or conformed dimensional objects are applied to the data object in the context-based or conformed dimensional object (B) given that (I) the data object is assigned to the particular context-based conformed dimensional data gravity well (A);
P(A) is the probability that the particular object will be the appropriate populator of the particular context-based conformed dimensional data gravity well regardless of any other information; and
P(B) is the probability that the particular object will have the predefined amount of conformed context/dimension objects regardless of any other information.
For example, assume that nine out of ten of the data objects that populate a particular context-based conformed dimensional data gravity well have the predefined amount (e.g., 80%) of the context/dimension objects that are on the sides of the particular context-based conformed dimensional data gravity well. Thus, P(B|A)=9/10=0.90. Assume also that the odds that any data object will be an appropriate populator of a particular context-based conformed dimensional data gravity well, regardless of any other information (P(A)), is 0.20, and that the probability that any data object will have the predefined amount of conformed context/dimension objects regardless of any other information (P(B)) is 0.25. The probability that any one data object will be a good populator of a particular context-based conformed dimensional data gravity well (based on these parameters) is 72%:
However, if nine out of ten of the conformed dimensional objects that populate a particular context-based conformed dimensional data gravity well still have the predefined amount (e.g., 80%) of the context/dimension objects that are on the sides of the particular context-based conformed dimensional data gravity well (P(B|A)=9/10=0.90), but now the odds that any data object will be an appropriate populator of a particular context-based conformed dimensional data gravity well, regardless of any other information (P(A)), is 25%, and the probability that any data object will have the predefined amount of conformed context/dimension objects regardless of any other information (P(B)) is now 23%, then the probability that any one data object will be a good populator of a particular context-based conformed dimensional data gravity well (based on these new parameters) is 98%:
The process depicted in
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of various embodiments of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the present invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present invention. The embodiment was chosen and described in order to best explain the principles of the present invention and the practical application, and to enable others of ordinary skill in the art to understand the present invention for various embodiments with various modifications as are suited to the particular use contemplated.
Note further that any methods described in the present disclosure may be implemented through the use of a VHDL (VHSIC Hardware Description Language) program and a VHDL chip. VHDL is an exemplary design-entry language for Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), and other similar electronic devices. Thus, any software-implemented method described herein may be emulated by a hardware-based VHDL program, which is then applied to a VHDL chip, such as a FPGA.
Having thus described embodiments of the present invention of the present application in detail and by reference to illustrative embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the present invention defined in the appended claims.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13733052 | Jan 2013 | US |
| Child | 14607468 | US |
