Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/451—Execution arrangements for user interfaces
• • G—PHYSICS
  • G10—MUSICAL INSTRUMENTS; ACOUSTICS
  • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
  • G10L15/00—Speech recognition
  • G10L15/26—Speech to text systems

Definitions

• the present invention relates generally to the field of computing systems.
• the present invention relates to computing systems that can mimic human data manipulation.
• the present invention relates to an Any-to-Any computing system that can simulate human-type information processing and enables natural language communication with the computing system.
• a One-To-Many machine is defined as "a machine in which one assembled structure has a fixed relationship to one or more assembled structures, in a manner that is intrinsically hierarchical and is intrinsically limited.” In software today, this fixed relationship is normally a programmer-created relationship that the user cannot change.
• An Any-to-Any computing machine that can be configured to simulate human-type information processing.
• An Any-to- Any machine is defined as "a machine in which any component or assembly of components can be related to any number of any component or assembly of components in a manner that is not intrinsically hierarchical and is intrinsically unlimited.” More particularly in relation to a computing machine, it is defined as "a computing machine in which any number of any component or assembly of components, can be related to any number of any component or assembly of components, in a manner that is not intrinsically hierarchical and is intrinsically unlimited.”
• the Any-to-Any machine is described in relation to data, which is defined to include user data, machine data, and software.
• the definition of the machine can be further refined and stated as "a computing machine in which any number of any data component or assembly of data components, can be related to any number of any data component or assembly of components, in a manner that is not intrinsically hierarchical and is intrinsically unlimited.”
• the principles and underlying methods of the Any-to-Any machine can be extended to apply equally well to the construction of hardware. If so applied, the machine can produce considerable additional benefits due to the fact that the hardware, and the software, and the human are then all operating on the same basic Any-to-Any machine principles.
• the ease of use and power and hence usefulness of the Any-to-Any computing machine derive from the fact that the human user handles data (often as represented by words) on Any-to-Any principles.
• the difficulty of use of state of the art software derives from the fact that it is built on one-to-many machine principles, which are in deep and fundamental conflict with human Any-to-Any data handling methods.
• the Any-to-Any computing machine breaks all data and software entries down into indivisible, re-useable components, including data concerning the structure in which the machine itself is constructed (such as a database), and stores each component in a separate record and then, through various mechanisms, relates the components to one another by type. That is, each data component has an unambiguous meaning that cannot be further broken down without losing the entirety of its meaning.
• each software component performs a single function that cannot be further broken down without losing the entirety of its useful functionality.
• This decomposition then allows any type of data component type or any type of data assembly to be "paralleled” or specifically associated with one or more software components or software component assemblies configured to handle its associated data component type or assembly type. This also allows any data or software component to be correlated with any other data or software component without necessarily involving a third component in the correlation. As a result, a single instance of each data and software component or component assembly may be independently and directly accessed for use in or by multiple software modules and this access can occur in either a hierarchical or a non-hierarchical manner. This avoids redundancy in the computing system and simplifies troubleshooting, maintenance, and upgrades.
• the Any-to-Any computing machine typically stores data and software code in a Data Relation Table that includes a Data Classification structure that serves as a universal interface for all data and software components stored in the database.
• the Data Relation Table mechanism which is essentially an assembly plan for the assembly of data components and the further assembly of previously assembled structures, is analogous to the assembly plan for a car or airplane. Such vehicles are built from single-function individual components such as screws and bolts and nuts.
• any one word is at minimum an assembly of the word itself, and the (invisible) concept(s) or meaning(s) that go along with it.
• this word when transmitted, is essentially an assembly consisting of a single word (fax) plus more than a dozen components of the individual meanings of the word.
• the data assemblies received from the user or elsewhere first need to be disassembled, and then stored in component form, sorting each component in such a manner as to indicate its type (for example in Data Class record types which are analogous to physical component bins, with the difference that they store types of components).
• data - such as words and their meanings
• this typing is not done based on classically-used mechanisms such as grammar, syntax or probabilities, but based on meaning or function. Because words are then related by their meaning - as opposed to their grammatical classification - differences, similarities and identities of meaning can be found and used, regardless of the grammatical classification of particular words.
• One desirable principle in constructing an Any-to-Any machine, in accordance with the Component Principle, is the absence of as many as possible programmer-created fixed relationships (such as are current in the state of the art) between any one data component or component assembly and another. Ideally, this should be as near complete as possible and preferable for the application concerned. For example, in conventional databases, a programmer often ascribes a field name (a label) to a given field in the database, another name to that field in the user interface using that database, and then that name or label may be displayed on the screen and another name cannot be displayed on the screen without also changing the first name.
• a field name a label
• any field can be given any label, and individual users can label a given type of data in any manner that happens to suit them, or data can be re-labeled in other languages simply by selecting a different language of record to use for a given output.
• One importance of this is that users are individuals, and terms and displays that are convenient to one person are incomprehensible to another, yet existing One-to-Many software construction methods make it extremely difficult to change these, difficult to change them on the fly and difficult to change the manner and labeling of the output depending on the person who is looking at the data.
• An element of ease of use that is enabled by the invention is the ability to show any data in any fashion, with the consequence that the input and the output of any data can adapt (if suitable mechanisms exist) or be adapted to each individual user.
• the application of the Component Principle to separating the displayed field name from the database field name, and further, to completely separating the software mechanisms that manipulate data from the mechanisms that output the results of the manipulation has the effect of enabling any database field to be re-labeled as often as required for different purposes, different types of data as well as for different users. Enabling this field re-labeling in a database field has the additional benefit of turning a single-use database into a potentially universal database that is intrinsically capable of recording any data - and this facilitates the acceptance of data from a human. Additionally, the ability to record any data enables all data to be recorded in a single standard format.
• the Component Principle (in which parts of any data are disassembled into types of parts to the extent that further disassembly loses the entirety of the original meaning or function, and then stored for subsequent re-use) is the enabling method that enables an Any- to-Any machine to be built. In any Any-to-Any machine, the Component Principle is also applied to software.
• software which is conventionally constructed as a large lump, is disassembled (or written as) fields and records that either contain the actual software itself, or Numbers Concept Language (described below) references to it, or references to other records, or references to disk files, as the requirement may be and as the limitations of the medium in which the Data Relation Table may permit.
• the Component Principle is equally applied to the construction of the different types of things that are usually collectively named software.
• 'software' in an Any-to-Any machine is applied by applying the Component Principle and disassembling it into its various types of thing, each of which is recorded in its own Data Relation Table record type.
• Examples of such software record types are Execution records - the only types of record that contain actual code (or references to code) in their fields - Label records containing records, Condition records containing conditions upon which the code is to act, Prompt records for in prompting the user, Help records containing help, and so on.
• modules When acting together, such different records types are referred to as a module, and generally, the code in a single field, as well as the values for the same field in a Label or Prompt record, all apply to the same field, a method that is referred to as 'field parallel' construction.
• a unique and powerful benefit of this method is derived by using a specific sub-type of Condition Record referred to as an 'If Not Found' condition record.
• a record contains, in its data field, a specific condition and in the Administration Field termed a 'Director Field' can contain, or point to one or more records that state what to do if the condition/s contained in the If Not Found Condition record are matched.
• a Field Parallel Director record type can be used as a matched pair with an If Not Found Condition record, in which the fields of the Director Record either contain logic or instructions or point to records that do.
• This mechanism has the unique benefit of having the effect of welding any number of machines built on Any-to-Any similarly implanted, to act as a transparent whole, both in terms of the data they contain, and in terms of the abilities of their software modules.
• Applying the Component Principle method to both data and to software produces the unique and novel benefit that where any particular type of data (i.e. component or component assembly) exists, it can be precisely and exactly paralleled by a software component or components, or by a software component assembly or software component assemblies of different types, that are hence able to perform a precise transformation on any data type, i.e., where a particular type of data assembly exists, a particular software assembly can be built to handle that data assembly.
• a further teaching of the Any-to-Any machine construction is that software Components are almost entirely built to handle types of data and almost never to handle specific instances of data. For example, a single piece of logic in a field that is able to split an email address into its component parts (of user name and domain name) is not written to split an email address (an instance) but is written to split any value into its component parts. What that logic is to split, and what it is to use as a basis for the split, and where it is to put the results, are all specified by additional records (or field values in specific record types). Consequently, only one piece of actual code is now required to split anything. A further and uniquely beneficial consequence is that a great deal of manipulation can be handled by generic logic of this type.
• the Data Classification structure also includes and helps to define a Numbers Concept Language that uniquely identifies specific components for specific meanings of language (or other) terms that might otherwise be ambiguous, or contain more than one component meaning or use.
• the Numbers Concept Language also uniquely identifies specific components for all software components and component assemblies.
• the Data Classification structure can cooperate with a language processing system that translates natural language (or other languages, if desired) into Numbers Concept Language records for entry into the Data Relation Table. This provides the Any-to-Any computing machine with the ability to use natural language to communicate with a user, and to understand and execute natural language commands.
• Any-to-Any computing machine can be made to communicate in a human-like natural language discourse, and (*because all languages are handled on the basis of Components) can also communicate in machine languages and can also be made to translate accurately between human languages, between machine languages and between human and machine languages.
• the Data Relation Table structure of the Any-to-Any computing machine lends itself to a "field parallel" method of creating relationships between table records and/or between field values or combinations of field values.
• the same field in multiple records can correspond to the same Data Class of the Data Classification structure.
• This allows a software Numbers Concept Language identifier to be entered into a particular field for the purpose of identifying software code for operating on a data entry located in the same field on a corresponding data record.
• each data component is typically related to one or more first software components for manipulating that data component, and to one or more second software components for inputting and/or outputting that data record.
• multiple software-type records may be used to define a software module.
• This basic structure allows the Any-to-Any machine to be implemented in any combination of hardware and software, and can be configured control and operate hardware and software that is not built using the Any-to-Any design concepts.
• the field parallel principle enables the data in the fields of a record or records to be processed individually, to be processed in any order, and to be processed either individually, or on a massively parallel basis with all fields being processed simultaneously.
• An desirable operating principle of the software of an Any-to-Any machine is that a human who has caused something to be done (for example by ordering the Any-to-Any machine to perform an order) cannot refer to the order itself, or the result of the execution of the order, other than by using terms contained in the original order, or by using terms that, via a Concept Hierarchy, refer to some of the terms contained in the original order, or, to the circumstances surrounding the performance of the order itself, such as the time of day at which the order was given.
• the Data Relation Table permits both the order itself and the circumstances surrounding the creation of that order, to be recorded in one or more Data Relation Table records.
• the human manner of referring to a previous order, or to the results of the execution of an order is implemented in an Any-to-Any machine in terms of certain specific operating principles, as follows (but can equally be implemented in conventional software with beneficial results).
• One of these principles is that each and every human order is always recorded, and recorded in as much detail as is available.
• Another principle is that the Data Relation Table records containing previously given orders and the results of the execution of the order, are preferably never over-written, but only copied and then changed after copying, because overwriting (or erasing) a previous record renders that item unrecoverable in the state in which it previously existed and in which it may be required to be specified as part of specifying a further activity. For example, if the following order is given "send an Email to the guy to whom I sent the letter I printed last week on the ABC printer" cannot be executed if it was not recorded that the letter concerned was printed on the printer the user specified.
• Still another operating principle is that if excessive records result from the practice of not over-writing or erasing records, then such excessive records are firstly archived and later removed using a 'detail deterioration algorithm' following a principle termed the 'unlimited principle.
• the Unlimited Principle is stated as "the software may not limit the human in any manner in which he does not limit himself.” For example, while a human may remember what he ate for lunch the previous day, he will not normally either remember what he had for lunch 14167 days ago, nor will he have the slightest interest in recovering that data.
• the "Importance" Administration field, and the “Importance” record type enable types of data to be graded, a grading that the deterioration algorithm can eventually use to remove records of no further interest.
• a further principle is that the previous principle, in which records are not normally erased or over-written, means that the resulting Data Relation Table forms a time track - a continuous record of past events in time order, from latest backwards.
• each Data Relation Table record can contain one or more fields for Life, Time, Space, Energy and Matter. Using different values in these five categories, it proves possible, with various methods to record any data whatsoever.
• a field can either contain a value for a concept or combination of concepts, or, point to another record and consequently, the value of each particular field can actually be specified by a further record, and the value of each field of that further record can themselves be specified in a further record.
• any given concept can either be specified as a field, or by a record of that type, or both, and one can point to the other.
• a further desirable principle of the Any-to-Any machine, and a principle that is applicable to the construction of the storage medium and the Find Modules using it, and one that also dramatically improves the speed and accuracy of searching in conventional computing machines is the Co-reducing Concept Principle.
• This principle is also a key element in enabling an Any-to-Any machine to function at all.
• the Co-Reducing Concept Principle may be stated as "a human specifies something by continuing to add concepts each of which excludes all other concepts, until such time as the concepts now specified are unique (i.e. are the one thing or group of things he wishes to specify) and explicitly exclude all other concepts.” Note that the order in which the concepts are supplied is immaterial to the resulting concept that is specified, (but may not be immaterial to the further concepts that are supplied afterwards).
• a further principle of key importance to enable an Any-to-Any machine to function usefully is that when, in human interaction, a specification given to another human is thought to be unique but is not, the listener continues to prompt the speaker for further concepts until such time as the resulting specification is unique. For example, a boss may say to a secretary "call New York” and the secretary might reply 'Who in New York - there are only x million people in New York?" The boss might clarify "clients" and the secretary might prompt "Which ones? We have about 1 ,000." The boss might add another concept: "Mine (i.e.
• This interaction of the Co-Reducing Concept Principle with another is termed the 'Co-Reducing Concept Prompt', and is triggered by a mismatch between the Co-Reducing Principle specification and the results produced by it.
• This mechanism may be implemented between the Any-to-Any machine and its users, and can also be implemented between Any- to-Any machines themselves, enabling them to interact constructively.
• the above concepts and principles may be achieved through a universal database structure. This structure implements a semantic network and an optional Concept Hierarchy wherein each concept is uniquely identified by a number or numbers i.e., each concept is assigned a number in a Numbers Concept Language.
• Each concept or concept assembly (representing a data item) in the database may have semantic network links to all other data items that reference or are related to that data item or are referenced by the data item, where the links represent a type of relationship that is identified by a concept.
• the Numbers Concept Language may be used throughout the Any-to-Any machine, with the exception of the field/s used to record actual words and phrases in a particular language. Nevertheless, a simpler and more limited but still extremely useful Any- to-Any machine has been built successfully using words themselves, without translating them into Numbers Concept Language, an Any-to-Any machine has been built that uses both methods simultaneously. In simpler ⁇ applications, a full Numbers Concept Language implementation can be overkill.)
• the present invention includes a computing system that may be stored on any type of computer storage medium, and may be expressed in software, hardware, or a combination of software and hardware.
• the invention includes a computer-executable method defined by instructions that may be stored as software or implemented through computing hardware, or a combination of software or hardware computer storage media.
• the computer executable instructions expressed within the software and/or hardware define a computing system that stores data having an original meaning by disassembling the data into data components, the further disassembly of which would cause the loss of substantially all of the original meaning.
• the computing system then stores each data component independently.
• software having a required function may be stored by creating the software as a number of software components, the further disassembly of which would cause the loss of substantially all of the required function.
• the computing system then stores each software component independently.
• the computing system typically classifies the data components into data component types, and creates one or more software components or assemblies of software components that are configured to perform an operation on an associated data component type. Likewise, the computing system may also classify assemblies of the data components into data component assembly types, and create one or more software components that are configured to perform an operation on an associated data component assembly type.
• the computing system defines a data classification interface including a set of semantic data classes for categorizing data items.
• the computing system also defines a set of records including fields configured for containing numerical indicators corresponding to the data items. These numerical indicators are defined within a numbers concept language dictionary in which each numerical indicator is uniquely associated with a base data item. This allows the computing system to correlate the semantic data classes with the fields of the records to associate a particular numerical indicator located in a particular field of a record with an associated data class.
• the computing system then stores the data components as records expressed in the data structure, and the software components may also be stored as records expressed in the data relation structure.
• one or more data components containing numerical identifiers in a particular field, and one or more software components containing numerical identifiers in the same field identify software components that are configured to operate the data components.
• the computing system may also be configured to receive a natural language block and convert the natural language block into one or more records expressed in the data relation structure. These records are then stored in the data relation structure. The computing system may then identify one or more fields of these records containing numerical identifiers, identify one or more software components configured to operate on data components having numerical identifiers in those fields, and call those software components to operate on the data components.
• the computing system may be configured to include an order execution system that is operable for receiving data inputs and performing operations in response to the data inputs.
• This order execution system defines a data relation structure that includes a data classification interface that defines a set of semantic data classes for categorizing data and software items. This set of data classes is said to be "semantic" because each data class connotes a particular meaning for a data item assigned to the class.
• the order execution system also includes a set of records defining fields configured for containing numerical indicators corresponding to the data items. These numerical indicators are typically defined within a numbers concept language dictionary in which each numerical indicator is uniquely associated with a base data item.
• the data relation structure correlates the semantic data classes of the data classification interface with the fields of the records to accommodate the association of a particular numerical indicator in a particular field of a record to connote a data component that identifies an unambiguous meaning for the data item.
• the order execution system typically contains many data blocks, such as commands, queries, or other data inputs received from a user or other computing system.
• Each data block has an original meaning and is disassembled into data components, the further disassembly of which would cause the loss of substantially all of the original meaning.
• Each data component is then stored independently as a record expressed in the data relation structure.
• software having a required function may be constructed from a number of software components, the further disassembly of which would cause the loss of substantially all of the required function.
• each software component may be stored independently as a record expressed in the data relation structure.
• the data relation structure may be functionally configured as a data relation table or as a semantic network.
• the data classes of the data classification interface are typically grouped into a set of semantic data categories selected from the group of categories including administration, life, time, space, action, and matter.
• the records expressed in the data relation structure are typically selected from a group of record types including data records, condition records, code records, prompt records, label records, help records, and other types of records.
• a group of contiguous code records expressed in the data relation structure define a software module for performing a multi-step operation:
• data records containing numerical identifiers in a particular field, and one or more code records containing numerical identifiers in that same field may identify software that is configured to operate on the data records.
• the computing system may also include an interface control system operable for receiving a natural language block, and a language processing system that typically receives the natural language block from the interface control system.
• the language- processing system then converts the natural language block into one or more records expressed in the data relation structure and connoting a unique meaning ascribed to the natural language block, and passes the records to the order execution system.
• the order execution system may be configured to receive the corresponding records from the language processing system, and determine whether the corresponding records define an unambiguous command. The order execution system may then execute the command if the corresponding records defines an unambiguous command. Alternatively, the order execution system may cause the interface control system to prompt the user for additional information if the corresponding records does not define an unambiguous command.
• FIG. 1 is a functional block diagram of an Any-to-Any computing machine including an interface control system and an order execution system.
• FIG. 2 is a functional block diagram of an Any-to-Any computing machine including an interface control system, a language processing system, and an order execution system.
• FIG. 3 is a functional block diagram of items contained in an order execution system for use in an Any-to-Any computing machine, which items may be stored in the form of a Data Relation Table.
• FIG. 4 is a functional block diagram of items contained in a language processing system for use in an Any-to-Any computing machine.
• FIG. 5 is a diagram illustrating a Numbers Concept Language dictionary for use in an Any-to-Any computing machine.
• FIG. 6 is a diagram illustrating a logics table for use in an Any-to-Any computing machine.
• FIG. 7 is a diagram illustrating the use of data/software parallel n-tuplet in a Data Relation Table for use in an Any-to-Any computing machine.
• FIG. 8 is a diagram illustrating the structure of a Data Relation Table for use in an
• FIG. 9 is a logic flow diagram illustrating a process for responding to natural language commands in an Any-to-Any computing system that includes a language processing system.
• FIG. 10 is a logic flow diagram for a language processing system in an Any-to-Any computing system.
• FIG. 11 is a logic flow diagram illustrating a process for responding to natural language commands in an Any-to-Any computing system that does not include a language processing system.
• FIG. 12 is a diagram illustrating an implantation of the Numbers Concept Language table for defining concepts and Data Class Table physical storage.
• FIG. 13 is a diagram illustrating a translation table containing forward references to string values in a string table illustrated in FIG. 16.
• FIG. 14 is a diagram illustrating the Data Relation Table Label, Prompt, Query and Help record sub-types.
• FIG. 15 is a diagram illustrating the Data Class Table Records-DATA containing the
• FIG. 16 is a diagram illustrating a portion of a Data Class String Table containing string values in English Concept Language with associated converted Numbers Concept Language values.
• FIG. 17 is a diagram illustrating a portion of a Java Class Table containing a reference to the byte codes for the associated concepts.
• FIG. 18 is a diagram illustrating the Co-Reducing Concept principle.
• FIGS. 19A-19H are diagrams listing the generic field names and data categories used in one embodiment of the present invention.
• FIG. 1 is a functional block diagram of an Any-to-Any computing machine 10 that may be accessed by a user 12 (The user can be an actual person, or the same or another Any-to-Any machine acting as a user).
• the Any-to-Any computing machine 10 includes an interface control system 14 and an order execution system 16.
• the Any-to-Any computing machine 10 does not include a language processing system capable of interpreting natural language text.
• the interface control system 14 is configured to receive structured data inputs that are, by their structured nature, unambiguous.
• structured inputs typically include buttons, selection lists, check boxes, text boxes and similar items and can include structured data of any type.
• An example of the interface control system 14 is described in the commonly-owned co-pending United States Patent Application No. entitled, "Graphical User Interface” and filed on November 13, 2000, and which is incorporated by reference into this specification.
• the order execution system 16 receives these structured inputs and determines whether a complete instruction has been communicated. If not, the order execution system 16 returns a prompt for additional information to the interface control system 14, which presents the prompt to the user.
• This prompt may be presented to the user either visually, on a screen, or by any other method such as text-to-speech, or to another Any-to-Any machine by an inter-machine communication channel. This process repeats as preferable until the order execution system 16 has received a complete instruction, which it then implements.
• An desirable feature of this system lies in the structure and operation of the order execution system 16, which implements the Any-to-Any computing structure in the form of one or more Date Relation Tables. This type of table is described is greater detail below with reference to FIGS. 7 and 8.
• FIG. 2 is a functional block diagram of an Any-to-Any any computing machine 10' that includes a language processing system 18 in addition to the interface control system 14 and an order execution system 16 described above.
• the language processing system 18 allows the user 12 to communicate with the system 10 using unstructured, natural language input.
• the language processing system 18 converts ordinary natural language text into Numbers Concept Language that the order execution system 16 can understand and respond to in an appropriate manner.
• FIG. 3 is a functional block diagram of items contained in the order execution system 16. These items include software components 20 that are expressed as records in a Data Relation Table 17. Each software component performs a single function on a single data component or component assembly, and cannot be further broken down without losing its functionality. In other words, each different type of thing that is normally collectively referred to as "software” is broken down into constituent components, such as the code itself, external conditions, prompts, labels, help, field names and so forth and the code itself is broken down to the extent that it is capable of performing a single action on a single type of data component. Each software component is then stored separately, which - together with communication methods between software components - allows each software component to be accessed and used independently of the other software components. This allows any data or software component or component assembly to be correlated with any data component or component assembly or software component or component assembly without necessarily involving a third component in the correlation.
• any one software component or component assembly can output its results to any combination of other manipulation modules (with no visual or other output at all) and/or to any of many alternative output component assemblies.
• any output to a peripheral device - such as a screen or printer is treated wholly as being an output-time spatial assembly of data. For example 'a letter' in an Any to Any machine is recorded as component assemblies, which are simply arranged with specific spatial relationships on the screen, a spatial relationship of data that the user recognizes as being 'a letter'.
• This Any-to- Any interface methodology results in an ability to create relationships wholly through spatial relationships as output time. For example, if the individual components 'Mr.', 'John' and 'Brown' are each displayed in their own borderless field on the screen (termed an 'Active Element') and if these fields are arranged consecutively so that they are seen as "Mr. John Brown", the user will understand this is the name of a person. However, if these data components are differently displayed in different parts of the screen - for example 'Brown' is displayed next to fields that state 'is a good person', the user will understand 'Brown is a good person.' However, only one recording of 'Brown' is required to do this.
• a further advantage of this Any-to-Any output method that is enabled by the Component Principle of software storage is that if it is required to 'put' a photograph (for example) 'into' a letter, no complex linking method is required to do so, and instead, the field of the record containing the photograph is simply displayed with a specific spatial relationship to the remainder of the data that is the letter.
• a further advantage of this methodology is that no change is required to either the underlying data manipulation logic, or to the code controlling the display of an item in order to cause the visual display (or any output) to behave in totally different manners.
• an Interface Behavior record for one user can cause a particular display module to output needed prompts to a user one at a time ('spoon-feed interface') in a manner suitable for a novice, while, another Behavior record (related to another and skilled user, causes the very same display module to display all needed prompts and known values simultaneously.
• no new manipulation logic, or output logics is required - the only change required is to change a single Interface behavior record that in effects, gives the display module different instructions, on a field by field basis, as to what to do.
• the Data Relation Table 17 also includes data components 22. Each data component has an unambiguous meaning that cannot be further broken down without losing the entirety of its meaning. These two types of components 20 and 22 form the building blocks from which matching and parallel data and software assemblies of higher complexity may be assembled.
• any data or software component or component assembly may be correlated with any other data or software component or component assembly without necessarily involving a third component in the correlation.
• This is the basic concept underlying the Any-to-Any computing machine.
• Another characteristic resulting from the component-level data and software storage approach is that a single instance of each data and software component or component assembly may be independently and directly accessed or referenced in a non-hierarchical manner for use independently of any other, for example in creating multiple software modules. This avoids redundancy in the computing system and simplifies troubleshooting, maintenance, and upgrades.
• the component principle of data and software storage and manipulation also enables any data component or assembly to be accessed and manipulated independently of any other data component or assembly.
• This Component Principle also enables data components and assemblies to be manipulated by software components and assemblies in a parallel data/software structure, in which particular data component or assemblies are associated with particular software components or assemblies that are configured to manipulate their associated data components or assemblies. Further, the Component Principle of storage is also the key principle that enables an Any-to-Any machine to be unlimited (other than physical limits that may.
• each telephone number is recorded in a separate record, and if the display Interface is also constructed on Any-to-Any machine principles, and if software modules are suitably constructed, then, is it possible for a user to have no phone numbers recorded or displaying, or a thousand phone numbers recorded for him, each of which (using remaining Data Relation Table fields and if preferable other record pointed to from those fields) can state the times and locations and conditions under which it is operative.
• a single software component is recorded in a Data Relation Table Record, it is possible to use the record itself, or other records pointed to from the base record, to specify an infinity of data about that component, and to control its operation - or non-operation - infinitely finely.
• the Data Relation Table 17 may also include a Concept Hierarchy table 24, which is typically stored as an assembly of Data Relation Table records.
• the Concept Hierarchy table 24 contains a listing of known relationships between or among data components and/or assemblies in the system's library and is a table to which users can add in an unlimited manner.
• the Concept Hierarchy table 24 indicates that an "apple” is a member of the class known as "fruit," and a "dog” is a member of the class known as "animal,” and so forth.
• the Concept Hierarchy mechanism is also used for many forms of grouping in the Any- to-Any machine, such as for grouping any one document or item into an unlimited number of groups. Additionally, other record types enable the user to state anything he should wish about any one or more junior- senior relationships.
• the construction of the all hierarchy mechanisms is such the membership of an item in any hierarchy does not preclude that same item (as opposed to a copy of the that item) being included in any other hierarchy and further, allows any hierarchy to be accessed directly at any level without going through the entirety of the hierarchy. Membership in multiple hierarchies does not require multiple copies and also allows reciprocal hierarchies - if A is accessed B can be seen as (one of) its juniors while if B is accessed, A can be seen as its junior, again without requiring any copies of the items concerned, with the result that items viewed are always up to date. Recording these relationships allows the machine 10 to identify these relationships when they occur in natural language constructs.
• the Concept Hierarchy table 24 assists the machine 10 in determining that the terms “dog” and “animal” both refer to the same thing.
• the Concept Hierarchy table also enables the Any-to-Any machine 10 to perform a function known as "return nearest truth.” For example, the machine may respond to the question, “did Joe go to New York by train?” with “no, but he did go Chicago by plane.” Similarly, the machine may respond to the subsequent question, “did he go yesterday?” with “no, but he is going tomorrow.”
• the Data Relation Table 17 also includes a Data Classification interface 26, which is used to differentiate between different meanings for the same term, and also to define a Numbers Concept Language for uniquely identifying each component meaning for a language construct having multiple possible meanings.
• the Data Classification interface 26 serves as a universal yet variable interface for all of the records stored in the Data Relation Table 17 and hence, relates data to the software that manipulates that data type. That is, a particular interface typically operates with all Data Relation Table tables or records containing data of a particular type, and could include a particular application or span many applications, yet may be specifically assembled for a particular application.
• the records in the Data Relation Table 17, in turn, can be correlated into higher-level software and data structures to create software modules, databases, spreadsheets, and any previously-unknown type of data item.
• the Data Classification interface 26 effectively serves as a universal interface for all of the software modules and data structures implemented within the Data Relation Table 17.
• the Data Classification interface 26 also contains and communicates both with the visual or other output interfaces and with the language processing system 18, which converts natural language input into Numbers Concept Language records that can be entered into the Data Relation Table 17 by way of the classification interface.
• software modules and data structures implemented within the Data Relation Table 17 can have the ability to receive and process natural language input, as well as machine languages and virtually any other type of input.
• the Data Relation Table 17 also includes a logics table 28, which correlates software components with number concepts language identifiers, i.e., numbers that correspond to predefined components. This can be used to allow the Numbers Concept Language identifiers, rather than the software code itself, to be entered into the Data Relation Table 17.
• each specific meaning of a word is stored as one or more Numbers Concept Language identifiers in the Data Relation Table 17.
• the Data Relation Table 17 also includes record correlations 30, which are implemented through several features. First, multiple components may be stored in different Data Classes of the same record in the Data Relation Table 17 to indicate that these components have a combined meaning (in the case of non-software data) or a combined function (in the case of software-type records) in that record.
• the term "faxed” can be said to be comprised of four different components, one of which is the word itself, one that means “an action,” another that means “to send by facsimile,” and third that means “in past time.” All four of these components stored in the same record connotes the meaning of the term “faxed.” However, the part of the meaning of "faxed” that is “an action” is typically defined by storing the Numbers Concept Language identifier for the term "to send by facsimile” in a Data Relation Table field dedicated to storing types of actions.
• a further type of record correlation is known as "field parallelism," in which multiple components are stored in the same field of different records.
• field parallelism in which multiple components are stored in the same field of different records.
• a data record has a particular component entry in a particular field
• a software record may have an entry in the same field.
• the fact that a particular software assembly applies to particular type of data assembly and vice versa can be stated by a wide variety of mechanisms, including Administration fields used in a particular manner, and records of specific types that state this, but when field parallelism in use, the Software module/s concerned are so constructed that the Field Logic in a given field is able to handle and in nearly all cases only handles data components or component assemblies in its same-number field.
• a third major type of record correlation may be implemented through administration fields defined within the Data Classification interface 26.
• Administration Fields are used to control the data and to enable specific relationships between records and record types and also between data and/or software users to be recorded and used.
• any other type of parallelism can be configured into the Data Relation Table structure, in which data and associated software parallel each other through the presence of their Numbers Concept Language indicators in the same field (e.g., column) of the Data Relation Table 17.
• An desirable benefit of the use of field parallelism is that it provides an orderly framework in which a programmer can work and enable him to track and follow relationships that can become potentially extremely complex.
• field parallelism is used in the construction of the Any-to-Any machine, the database need not store empty fields and thereby improves search space and reduces storage space. FIG.
• NCL Numbers Concept Language
• the grammar stripping module 32 removes the application of grammatical features to effectively decompress the natural language communication. For example, the term “faxed” can be decompressed into “action, fax in past time,” the term “Joe's” can be decompressed to "belonging to first name, Joe,” and so forth.
• the grammar stripping module 32 also decompresses the effect of operator words (words that have both a meaning and perform an operation on their own or other words or groups of words) such as "and", "on”, "of”, as well as the pronouns, and other pointing, linking words, suffixes, and prefixes.
• the resulting decompressed language can then be processed by the language rule base 36.
• the grammar formatting module 34 uses a different rule base to perform compression on NCL records and turn them into grammatically correct readable language.
• the language rule base 36 includes a set of rules that are used to identify and remove higher-level compressions, and also to identify which of the candidate meanings for a particular term is indicated in a particular natural language construction.
• the term "fax” can mean the "act of sending by fax,” the "fax machine,” the "document sent by fax,” or the "document received by fax.
• the rule base 36 For each candidate meaning, the rule base 36 identifies other elements in the language construction that should be present to justify that particular meaning and such a rule is termed a Requirement Rule .
• the rule base 36 does this for each term in a block of natural language, and then identifies a set of meanings that simultaneously satisfies the requirements for all the meanings. This method of determining meanings has the benefit of finding when a given thought - as transmitted by words - is in fact complete and stands on its own, and can therefore be processed.
• the rule base 36 can be optimized by ordering the meanings in a priority order based on frequency of occurrence in the language of interest (as determined in advance and typically stated in the record encountered), and then goes through the permutations and combinations of meanings in decreasing priority order until it finds a set of meanings that simultaneously satisfies the requirements for all the meanings.
• the NCL dictionary 38 converts the block into an NCL record for entry into the Data Relation Table 17.
• FIG. 5 is a diagram illustrating the structure of the NCL dictionary 38 in greater detail.
• the single term 42 "fax" in the language construct 40 "fax Joe about bananas” will be used to illustrate the operation and structure of the NCL dictionary 38. All terms are translated into NCL format for entry into the Data Relation Table 17 in a similar manner.
• the NCL dictionary 38 includes a number of columns that define a Data Classification interface 26, each of which is a Data Class. It should be noted that this is the same Data Classification interface used by the Data Relation Table 17, so that NCL records created for the NCL dictionary 38 can be readily entered into the Data Relation Table 17, and data records in the Data Relation Table can likewise be translated back into words using the NCL dictionary 38.
• the Data Classification interface 26 includes five data categories 44: life, time, space, action, and matter.
• the Data Relation Table 17 includes a sixth data category, administration, which is used for record manipulation and, by using different combinations of numbers in various fields, can also act to define higher level data and software assemblies.
• Each data category in turn, is broken down into dozens of Data Classes, each containing types of meanings, that can be used to distinguish between the candidate meanings of various terms.
• a set of 80 or so Data Classes for the English language had been shown to provide an acceptable performance for the system 10 in prototype embodiments used for typical office administrative tasks.
• an appropriate set of Data Classes may vary from system to system depending on the functionality of the system and the vocabulary of the users. For example, an Any-to-Any computing machine is used for scientific research and a children's entertainment system will have significantly different sets of Data Classes.
• Each Data Class forms a column in the NCL dictionary 38, and each data component in the dictionary forms a row, which is referred to as a "record.”
• each Data Class is assigned a number. For example, the classes could be numbered left to right from one to 80. In the example shown in FIG. 5, only a very small subset of the Data Classes have been shown.
• one type of record in a first Data Relation Table can be conveniently converted into a different corresponding type of record in a second Data Relation Table.
• simple data such as a book or a Newspaper
• NCL Simple NCL
• This method is efficient provided that the storage medium such as the database described herein, stores both Data Relation Records and Continuous NCL in the same format, so that relationships of components can be found.
• the particular Data Classes shown in the NCL dictionary 38 have been included to illustrate the application of the NCL formulation to the term "fax” from the language construct ""fax Joe about bananas.”
• the Base Meaning of each term in the NCL dictionary 38 is assigned a unique number.
• the term “fax” is assigned the number "24”
• the term “in” is assigned the number "25”
• the term “past (time)” is assigned the number "26.”
• the Base Meaning of a term, to which the number of "24” is assigned in the case of the word "fax” is that Component part of the meaning of the word that is common to all the different individual meanings of the word.
• NCL Base Number Although each term is assigned a unique NCL Base Number, this does not yet connote that a given spelling of word has an unambiguous meaning because the same term can often have several different meanings in different language contexts. Each different meaning, therefore, is defined by its own assembly of NCL data Components, and a separate NCL record is used to represent each meaning of a given word, and the Base meaning is a common factor in each such record.
• this term can have four different meanings - all of which contain the Base meaning of "fax" - fax (the received document), fax (the original document), fax (the machine), and fax (the act of sending). These meanings are each defined by a separate Component assembly that is represented by a different record in the NCL dictionary 38. Specifically, the Component for fax (the act of sending) is defined by entering the NCL Base Number "24" for the term “fax” into the data field "32" for "type of action.” This indicates that the term "fax” for this particular Component assembly is a "type of action,” i.e., fax (the act of sending).
• the component for fax (the machine) is defined by entering the same NCL base number "24" for the term "fax” into the data field "33" for "type of machine.” This indicates that the term “fax” for this component is a "type of machine,” i.e., fax (the machine). This produces an NCL expression of "33.24” for this particular component - the first entry "33” indicates the field number, and the second entry "24” indicates the NCL base number.
• the components for fax are defined by entering the NCL base concept number "24" for the term "fax” into the Data Class field "43” for "type of machine.” This indicates that the term “fax” in this case is a "type of document,” i.e., fax (the document). This produces an NCL expression of "43.24” for this particular Component assembly.
• the Component assembly for fax (the received document) it is preferable to utilize two Components in a single record. Namely, the NCL base number "25" for the term “in” entered in field "31” for "direction of action,” and the NCL base number "24” for the term ' ax” entered in field "43” for “type of document.” This results in the NCL expression "31.25 & 43.24” for this particular meaning of the terms " received fax es.” (Note that the quantity of received fax(es) is not specified by the record of this example and a further NCL term in a Quantity field is required to state the number of fax documents received, and that number can of course be zero.
• faxed may be defined by the NCL base number "26" for the term
• Components may be combined in an NCL record to define multi-work constructs, such as phrases, sentences or other blocks of language.
• multi-work constructs such as phrases, sentences or other blocks of language.
• non- language data constructs such as numbers, software, parts of sound, parts or images, and so forth.
• FIG. 6 is a diagram illustrating the logics table 28 for use in the Any-to-Any computing machine 10
• the logics table performs the function of correlating specific chunks of software code with NCL numbers, so that the chunks of code can be conveniently indicated in an NCL record.
• the unique benefit of recording the code in this fashion is that, should the code have an error, it is only preferable to change the single and sole instance of the code itself, and no update is required to the (potentially) thousands of modules in which that code may be used.
• the second advantage is that when a programmer wishes to add functionality, most of the functionality he needs will already be present in the form of existing Logics that he can specify in his Modules, and he only needs to write the specific Logics needed to perform the data transformation that he wishes to perform, but which do not already exist. This substantially reduces construction time.
• the logics table 28 includes a first column for the record number - which also doubles as the NCL number assigned to the chunks of code, a second column for the name of the corresponding chunk of code (which is optimally record in the form of an NCL reference, thereby enabling a programmer to view the Logic name in his own language, if other languages are installed) and a third column either containing the code itself or a pointer to a memory location where the code may be found.
• the Logic Table can equally contained compiled code.
• a particular Data Relation Table type record may be used to store the logic (or a pointer to a memory location where the actual logic is stored), in which case one field may store the logic (or pointer), and the other fields of that record type may be used to store data associated with the logic, such operands, conditions under which the logic should be operational, and so forth.
• a single Component such as a Field Logic (a piece of code that performs one transformation on a data in its own field) either in a dedicated table (as in this example), or in an entire Data Relation Table record devoted to that type of data - in this case, the Field Logic Data type.
• Any table other than a Data Relation Table is simply a table consisting of truncated Data Relation Table records, and is an optimization that may cause problems in the future, as the remaining Data Relation Table fields are not available if required - as for example, to describe the logic, or for example, to state the conditions under which it is to act.
• a table other than a Data relation table and a data relation table are simply different forms of one another, with the table being considered and treated as a version of the data relation table that has been optimized for a specific purpose).
• FIG. 7 is a diagram illustrating the use of data/software parallel triplets in the Data Relation Table 17.
• Data/software parallel triplet 52a is such an example.
• a data record 1 may be entered for a first name in Data Classification Interface 26, and a field parallel code record 1A for manipulating the data record may follow.
• Execution Records to distinguish their content from 'code' as the word is normally used, where actual code, plus labels, prompts etc are all assembled in one lump and collectively termed 'code'.
• Each field of an Execution Record only contains the actual lines of code needed to perform the transformation, and does not contain the Labels, Prompts, Error messages etc that are commonly included in normal code.
• An entry of the NCL number 123 for the software code in the same field as the NCL number 57 in the data record indicates that the code is intended to operate on the data in the corresponding field of the previous record.
• the next record may then be another code record, such as an input/output record, for operating on the same data item.
• the entry of the NCL number 341 for the second software code in the same field as the NCL number 57 in the data record indicates that the code is intended to operate on or with the data in the corresponding field of the other records in triplet.
• This process may be continued for any number of correlated records, such as one defining the font for the data output, another defining a display location, another defining a color, another defining a condition for the field, another defining labels for the field, another defining a "help" display for the field, and so forth.
• a single code record may use multiple sets of such correlated records, depending on the particular user performing the action invoking the code record. For example, if labels and other display items are stored directly, (i.e., as text rather than in NCL format), then different records may be used to store similar display items in different spoken languages.
• a group of records that together, perform an operation on a particular type of user data record/s are termed a "module".
• the "field parallel” technique described above can have powerful results because it provides a method for the programmer to maintain order in potentially extremely complex relationships and makes data items "extractable” for display in any given user interface. It is also an desirable part of the non-intrinsically hierarchical nature of the Any-to-Any machine, as, together with the data relation table structure itself, it enables groups of dissimilar items to be accessed non-hierarchically, down to the single field level. This is because a particular data item is automatically correlated in the Data Relation Table 17 with the software records for manipulating and displaying that data item type. Thus, a user on a remote computer system can simply link to the appropriate field of the desired data record in the Data Relation Table 17, and the data can be easily displayed in its intended format by simply applying the corresponding software code records.
• FIG. 8 is a diagram illustrating the structure of the Data Relation Table 17 for use in the Any-to-Any computing machine 10.
• the Data Relation Table 17 uses the same Data Classification interface 26 described previously with reference to the NCL dictionary 38, except that the Data Relation Table includes an additional "administration" data category. This provides the Data Relation Table 17 with a fixed number of columns that also define an interface for communicating with the language processing system 18, which, like the interface output logic, is also stored in the Data Relation Table itself.
• the Data Relation Table 17 may also contain a virtually unlimited number of records 50a-n. Each record contains one or more Components 56, which include a specific NCL base number in a specific field corresponding to a specific Data Class.
• FIG. 9 is a logic flow diagram 100 illustrating a process for responding to natural language commands in the Any-to-Any computing machine 10.
• the startup modules cause the interface control system 14, which is also assembled in the Data Relation Table, to initiate a display.
• step 102 is followed by step 104, in which the interface control system 14 identifies the user of the system, typically by receiving an entry in a text box or by receiving input from a biometric identification device controlled by the Any-to-Any machine 10.
• step 106 in which the user entry is checked against an authorized user table to determine whether the current user is a new user.
• step 108 the interface control system 14 activates new user registration modules that request various information of the new user, such as the user's experience level, view preferences, and the like.
• step 108 and the "NO" branch from step 106 are followed by step 110, in which the interface control system 14 identifies the user for the purpose of selecting and invoking a user interface type that is appropriate for the current user and for the circumstances (depending on whether the user is communicating through a keyboard and screen, via telephone or email, or whether the user is in fact another similar Any-to-Any machine).
• Step 110 is followed by step 112, in which the interface control system 14 selects and invokes a user interface type for the current user. Upon displaying the user interface type, the interface control system 14 is ready to receive a natural language block from the user at step 116. Thus, step 112 is followed by step 114, in which the interface control system 14 receives a natural language block from the user.
• Step 112 is followed by routine 114, in which the language block parses the command received from the user and converts the command to Numbers Concept Language (NCL).
• NCL Numbers Concept Language
• Routine 116 is followed by step 118, in which the NCL record/s representing the converted command are passed to step 118 and the order execution system 16.
• the command is matched to a software module and the corresponding module is activated.
• Step 118 is followed by step 120, in which the order execution system 16 analyzes the command to determine whether the user's command defines a complete and executable statement.
• step 122 in which the order execution system 16 causes the interface control system 14 to prompt the user for additional information.
• step 122 is followed by step 114, in which the interface control system 14 again receives a natural language block (this time in response to the prompt) and passes the block on to the language processing system 18 at routine 116.
• commands can be received from either natural language entry or from entries made into specific fields on the screen directly). Again, the command is checked to determine if the user's command is a complete and executable statement. This process continues through this loop until the user command is a complete and executable statement.
• step 120 is followed by step 124, in which the order execution system 16 executes the command.
• step 124 is followed by step 126, in which the order execution system 16 causes the interface control system 14 to display the result of the order execution.
• step 126 is followed by the "CONTINUE" step, at which point the Any-to-Any machine 10 may receive another command or perform any other function for which it is configured. With suitable Modules, the Any-to-Any machine can process simultaneous commands from different users and sources.
• FIG. 10 this logic flow diagram corresponds to step 116 shown in FIG. 9, and illustrates a language processing system in an Any-to-Any computing system 10.
• FIG. 10 begins following step 114 shown in FIG. 9.
• step 202 the language processing system 18 receives a natural language order from interface control system 14.
• step 202 is followed by step 204, in which the language block is decompressed. This includes the process of "grammar stripping" to interpret and remove certain language constructs and conventions, all of which act as successive compressions, embedded within the block.
• step 204 is followed by step 206, in which the language processing system 18 obtains a first language term from the block.
• step 206 is followed by step 208, in which the language processing system 18 retrieves all candidate records (i.e., all records corresponding to possible meanings for the term) for the current term.
• step 208 is followed by step 210, in which the language processing system 18 checks the language block to determine whether another term remains in the block.
• the "YES" branch loops back to step 206, and the language processing system 18 obtains the next term and then retrieves its candidate records. This process continues to loop through steps 206, 208 and 210 until no additional language terms remain in the language block.
• step 212 in which language processing system 18 applies the language rule base 36 to select the candidate record that corresponds to the correct meaning for each term in the block.
• the rule base 36 orders the candidate records for each term In the block in a priority order based on frequency of occurrence in the language of interest (as determined in advance and typically stated in the record encountered), and then goes through the permutations and combinations of meanings for the terms in the block in decreasing priority order until it finds a set of meanings that simultaneously satisfies the meaning requirements for all the terms in the block.
• Step 112 is followed by step 214, in which all of the selected records for the block are combined into a unitary database record for the block.
• step 214 is followed by step 216, in which the language processing system 18 passes the unitary database record for the block to the order execution system 16.
• step 216 is followed by the "CONTINUE step, which returns to step 118 shown in FIG. 9.
• FIG. 11 is a logic flow diagram 250 illustrating a process for responding to natural language commands in an Any-to-Any computing system 10 that does not include a language processing system 18.
• This type of system includes, as previously described, initializing the display, identifying the user and displaying a particular view, i.e. interface type, for the specified user.
• this system receives a structured command from the interface control system 14 at step 252.
• This structured command is usually in the form of an interface Active Element that is labeled with the name of a Module (such as ⁇ -MaiP and activates the module concerned.
• the module uses its Condition records to determine whether the received command defines a complete and executable statement.
• step 258 in which the interface control system 14 prompts the user for additional information.
• routine 250 loops back to step 252, in which the interface control system 14 again receives a structured command from the user and passes command. This process continues through this loop until the user command is a complete and executable statement.
• step 260 in which the order execution system 16 executes the command.
• Step 260 is followed by the "CONTINUE" step, at which point the Any-to-Any machine 10 may receive another command or perform any other function for which it is configured.
• Any-to-Any computing system Although a broad description of the structure and operation of the Any-to-Any computing system has been provided above, it should be understood that specific embodiments designed for specific applications may have remarkably different structures that nonetheless follow the teachings and methods of the Any-to-Any machine, a machine type which is made possible by the application of the Component Principle to the subject of computing.
• a typical database structure for use in a Any-to-Any system configured to perform typical office functions, such as storing and retrieving documents, sending faxes, and so forth, is described below.
• the preferred structural setup of the database for this particular application is that of a modified semantic network.
• the database need not be implemented as a modified semantic network, it may be advantageous to structure it as such because the modified semantic network structure provides data representation flexibility, eliminates the wastage and bloat of flat tables, efficiently supports the Co-Reducing Concepts Search mechanism, and is fairly economical in terms of space and speed.
• Figures 12-18 illustrate examples of representative portions of the database structures of this embodiment of the present invention because each of these structures could contain potentially trillions of records.
• FIG. 12 is a diagram illustrating a portion of a NCL (Numbers Concept Language) Table 300 containing some of the various Concepts of the database.
• This table is labeled Table #1 and simply lists all Data Relation Table Concepts 302 that are known to the database.
• the Data Relation Table (DRT) Concepts i.e. NCL Table records
• the DRT Concepts comprise the NCL Table for the database system, where the NCL Table defines the Concepts that may possibly be used as Fields (including record types) by Tables, and not the physical layout of a particular Table.
• any single concept in the database may be considered as a specific Field type. Since every Concept may be considered as a logical type with its own logical instances (records), any data item represented by such values may be considered to be a multi-dimensional coordinate location in a multi-dimensional 'space' of interrelated concepts. Since the number of Concepts is intrinsically unlimited, and the number of instances (records) is intrinsically unlimited, the conceptual space is infinite. Thus, the meaning of a data item is captured by this conceptual mapping. Each Concept is a separate record. Each of these Concepts may be used in the construction of a Data Relation Table Record, but not all Concepts are necessarily used in each record.
• each record type is designated by a Data Relation Record Type, which is itself just another Concept in the NCL Table, but a record type is not restricted to any particular set of Concepts.
• Each Concept is numbered and is referred to in all other tables by its Concept number (logical table number) and its record number.
• the NCL Table 300 has six fields, a record number/logical table number field 304, a physical table number field 306, a table format number field 308, a table name field 310, a forward reference sequence field 312, and a backward reference sequence field 314.
• the record number/logical table number field 304 serves as the unique Concept Number of a specific Concept in Numbers Concept Language.
• the physical table number field 306 points to the table where data for this concept is found.
• the table format number field 308 is a reference to the structure of the physical table referenced in the physical table number field 306. Note that the table format number 308 could be stored as part of the physical table itself, but may be stored in the NCL Table as an optimization.
• Table name field 310 is a forward reference to the physical-storage data-type for the particular Concept represented. Note that this forward reference may be used to a record in the String table designating a Java class name for primitive values, and an "empty reference" (all zeros) for non-primitive values.
• Forward pointer sequence 312 references the Concepts used in the definition of the Concept for this record, and backward pointer sequence 314 references the Concepts which use this Concept in their definition. Both the forward pointers and backward pointers serve as the links in the semantic network. Note that these links include the Concept designating the relationship type covering the link, and as such carry semantic value.
• the pointers are a 3-part number such as '6.1.23" where the first number is the concept number in NCL Table 300, the second number is the type identification number (type id number, i.e., the logical table number, which is also a Concept number in NCL Table 300), and the third number is the record number in the physical table used by the Concept that the type id number references.
• the three-part references embody a representation for the most basic of structural relationships, as "uses/is-used-by" link in the semantic network. So, in relation to the forward and backward pointer sequences of NCL Table 300, the forward pointer sequence indicates that the concept is the junior concept, i.e. the 'child,' of a more senior concept, i.e.
• each three-part pointer carries conceptual relationship type information, this representation may be applied to any kind of relationship, including but not limited to: definitions (as in the NCL Table 300), containment or composition, similarity/difference, inheritance, taxonomic relationships, etc.
• FIG. 13 is an illustration of a Translation Table 330 of the present invention. This table is labeled Table #2.
• Translation Table 330 contains the NCL translation of the concepts into the Natural Language word by referring to the Strings Table for the name of the concept. The English equivalent of the concept is given in parenthesis and is only provided for clarity and for ease of understanding the various concepts of the present invention.
• Translation Table 330 has four fields, a record number field 332, a concept number field 334 where concept number field 334 tracks its equivalent in the record number/logical table number field 304 of the NCL Table 300 of FIG. 1 , a language number field 336, and a forward reference field 338.
• record #22 indicates that it is a 'Matter' concept. It is in the uppermost level in the
• 'Matter' Category (See record #22 in FIG. 2) because it does not contain a forward reference pointer in the forward reference sequence field 312.
• Record #23 is the Time' concept and it is also in the uppermost level in the Time' Category.
• Record #24 represents the 'Present Time' concept and has a forward pointer sequence value of '6.1.23.
• the '6' refers to record #6 in NCL Table 300.
• the matching record in the Translation Table indicates that this field type is a concept.
• the second number, number '1 ,' refers to the record number in the NCL Table 300.
• the second number indicates it is a NCL type and that the physical table number in the physical table number field 306 used to locate the record number (the third number in the 3-part forward reference sequence) is Table #1 (NCL Table 300).
• the third number identifies the record number in the referenced physical table determined by the second number.
• number '23' points to record #23 in Table #1 (NCL Table 300).
• record #23 is the Time' Category.
• record #24 ('Present Time') in NCL Table 300 is a junior concept, i.e. a 'child,' of the Time' concept.
• the backward pointer sequence field 314 is similar to forward pointer sequence field 312, except that the backward pointers in this case point to the junior concepts, i.e. the 'children,' to which the current field is a senior concept, i.e. a 'parent.' Note that in this example the notion of 'senior' or 'parent' simply means the concept that uses another concept in its definition, while the notion of 'junior' or 'child' simply means the concept that is used by another concept's definition.
• Data Types are also included in NCL Table 300. Illustrative examples of such type concepts are record numbers 3-17, etc.
• a Data Relation Table Record's data record may be associated with a Java Class via the Translation Table 330, using language number zero (0), which denotes the internal language of the system.
• the database should 'know' how to store, search, and retrieve primitive data values such as Strings, Integers, Dates, et al.
• a few Java Classes are known to the database as primitive Data Class Tables, and are used for the storing of values of the corresponding type.
• the database should be able to store and retrieve executable code for Logics, which may be implemented as Java Classes. If a Java Class represents a native data structure, then the Java class should provide (or inherit) two functions, one to read an object's data from a Data Relation Record, and another to write an object's data to a Data Relation Record. In this manner, the details of the structure and implementation of the database are completely hidden from the Logics and other Java code.
• a DRT Record class which has a type# + record# Reference is defined as a persistent identifier for the DRT Record, and which stores a sparse map of key + value pairs of the fields and values actually used, where the key for the map is a NCL Concept Number denoting the conceptual Field for the value, and where the value may be any Java object, including primitive types, data structure classes, References to DRT Records, and also DRT Record objects.
• the database appears to read and write native Java objects, including DRT Record objects.
• the type# from the DRT Record's Reference is used to retrieve the Java class name by asking the database for the name of the concept denoted by the type# in the internal language (language zero, representing NCL itself).
• the concept number used as a field label is exchanged for the name of the concept in the internal language (language zero, representing NCL itself) to get the Java object field name. This information is sufficient for Java to reconstruct retrieved native Java objects. Note that the database remains unaware of any specific Java classes beyond the aforementioned few primitive data types.
• Data Relation Table-LPQH 350 has a record number field 352, a DRT forward reference field 354, a sub-type field 356, a language number field 358, and Fields forward reference sequence field 360.
• the Data Relation Table- LPQH 350 may also have a backward reference sequence field (not shown), which works in the normal manner. Because DRT forward reference field 354 is a forward pointer, it has the 3-part reference sequence discussed above.
• the first digit references the concept number in NCL Table 300
• the second number references the type number (in this case it is a sub-type)
• the third number references the record number in Table #4.
• the language number field number indicates the language being used. In this case, the number '1' means it is the English language.
• the Fields forward reference sequence field 360 references the fields in the String Table as the labels that are associated with the particular data record.
• the Data Relation Table-LPQH 350 may also have a User Number forward reference field (not shown) to 'mark' it as preferred by a specific User, as well as other administrative fields, as desired.
• a DRT Record can be used to create Assemblies of any number of fields.
• the same mechanism can also be used to create assemblies of any number of Record Types, thus eliminating the need for a separate Assembly Table mechanism described later and in the priority document.
• New Concept Fields are added to a Record Type later, they may go at the end of the Field sequence in the Data Relation Table Records-DATA; in fact, if updating of existing records were allowed, any field could be added to any record at any time. This provides a way to augment existing types and add new Concept Fields to NCL Table 300 without ever having to restructure existing records or tables.
• a Data Relation Record can specify other Record Types in the NCL Table Concept Fields in its reference sequence, effectively creating an assembly of other record types.
• a Data Relation Record can specify individual Data Records instead of NCL Table Concept Fields in its forward reference sequence, thus creating an assembly of individual records (also called a 'singleton object' or 'singleton class').
• This kind of assembly is not much use as a template for specifying multiple data records, as all such data records would contain exactly the same data, but it is useful for modeling complex constructions and assemblies of data which comprise a higher-order data item, such as a letter, spreadsheet, or other complex document.
• a Data Record might specify a Date field, a specific User's address record (which is an assembly as usual), a specific Greeting data record (such as "Dear Sir"), another Data Record Type (concept) for a text assembly (described below), a specific Signature record (also a text assembly), and a data record for a digitized signature.
• a Data Record might specify a Date field, a specific User's address record (which is an assembly as usual), a specific Greeting data record (such as "Dear Sir"), another Data Record Type (concept) for a text assembly (described below), a specific Signature record (also a text assembly), and a data record for a digitized signature.
• a specific User's address record which is an assembly as usual
• a specific Greeting data record such as "Dear Sir”
• a specific Signature record also a text assembly
• a data record for a digitized signature This would
• the Data Record Type for the text assembly may combine pre-existing text data records with Name Field references to affect a 'boilerplate' for the body of the Form Letter. Instances of this new template or type would then ask the user (or other input source) to fill in the Name Field value(s) in order to complete the data-value mapping for the new data record, thus easily creating form letters that differ only in the name listed in the body text.
• every NCL Table Concept Field may have its own Data Class Value Table 370 illustrated in FIG. 15 as the Data Relation Table Records-DATA.
• Each Concept that may have multiple values may have a Data Class Value Table, but such a table need not contain only values of one concept.
• the tendency is to store Data Class Values with similar structure and size in the same physical table in order to speed access and reduce storage overhead, but from a logical-model viewpoint every Data Class Value Table is independent.
• all Data Class Values could be stored in a single table (such as the DRT Records-DATA Table 370); in which primitive data values types such as String and Date are separated into separate tables for more optimal indexing and searching.
• the data item referenced also stores a 'back-pointer' directed typed relationship in the References back reference sequence field 376.
• a 'dependency trailer' that is merely a sequence or list of the Concept number, type ID number and record number of the record number field in the table for which it is referenced as a value.
• Such 'dependency trailers' are referred to as back reference sequences; the two terms are interchangeable.
• the Fields forward reference sequence field 374 stores the forward pointers to all values referenced by the data item.
• the collection of dependency relationships comprises the semantic network for the database, and provides direct access paths precisely equivalent to indexing every field in every record
• FIG. 16 illustrates a portion of a Data Class String Table 380 for String values where each unique string value is stored only once, and all field values set to a certain string value simply reference the string table number and the record number of the string desired.
• Table 380 simply holds primitive String values for use by other DRT Records.
• Table 380 has a record number field 382, a Field Value field 384 and a back reference sequence field 386.
• the back reference sequence points to all the records which use this particular String as a value in some field, regardless of what kind of record it is, or which field it is used in.
• Each back reference is a series of three numbers previously mentioned.
• the first points to the logical table number 302 in NCL Table 300, which designates the concept.
• the second number points to the record number in NCL Table 300, which indicates how the particular data value is used, i.e. the type id, and also designates the physical table used by that particular logical table number.
• the third number represents the record number in the physical table used by the logical table number (type id) designated by the second number reference.
• the Data Class String Table 380 may have a forward reference sequence (not shown) if desired.
• the back reference sequence pointers for record number 112 (me@home.net) in String Table 350 are 31.29.4 and 31.29.12.
• the first number "31" in each sequence number refers to the logical table number/record number in the NCL Table 300 in FIG. 12 and the related record number in Translation Table 330 in FIG. 13. Referring to logical table number "31" indicates that this data item is the concept 'email_address.' The second number "29” indicates that this data item is an eb.
• Email. Email__Address type This indicates that the string is an email address type of data.
• This data type references physical table #4, the Data Relation Table Records- DATA 370 in FIG. 15.
• Table 370 (DRT Records-DATA)
• the third numbers of the back reference sequence pointers are "4" and "12." These refer to the corresponding record numbers in Table 370.
• the Fields forward reference sequence 374 for records #4 and #12 point forward to the same data item that references these data records, i.e. the "me@home.net” string value in String Table 380 in FIG. 16.
• the References backward reference sequence 376 for records #4 and #12 point back to two different concepts, 33.32.3 and 34.32.9.
• ellipses 410, 420, 430, and 440 represent the concepts that are themselves represented (and transmitted between humans) by the words 'MY' 412, 'New York' 422, 'Client' 432 and 'Friends' 442.
• the word 'MY' 422 the listener will understand that this word refers to all things that belong in some manner to the speaker - his car, his house, his wife, etc., and, excludes all and every other concept to which 'my' does not apply.
• the transmission of each word is a continuing exclusion process, diametrically opposite to the inclusion or amplification or elaboration process that is often taught in the state of the art and in various linguistic disciplines.
• the concept transmitted 440 encompasses anyone and everyone in the world to which the word 'friend can be applied and excludes all other concepts. Since there are 6 billion people in the world, and most of them may be supposed to know more than one person to whom the word 'FRIENDS' 442 could be applied, the concept 440 transmitted by uttering the word 'FRIENDS' 442 on its own is enormous.
• This mismatch triggers the searching module to issue a Prompt derived from an associated Prompt record such as "which ones?" thereby applying the Co-reducing Concept Principle.
• the principle can be further applied by displaying the resulting matches as well as prompting for further concepts. This enables interactive searching to occur.
• this kind of query can easily propagate to more abstract concepts by way of the optional Concept Hierarchy to cover more conceptual ground such as 'large', 'furry', and 'omnivorous.'
• This mechanism enables a computer to Return Nearest Truth, a term applied to the mechanisms that emulate the human practice that, when a given query is not true, the human may usefully return the nearest information that is true.
• one human may query another "did Joe go to New York by plane?" and receive the reply "No, he went to San Francisco by train.”
• the terms "New York” and “San Francisco” are both related to one another as they are both juniors of one of the Space Data Category Concept Hierarchies - they are both 'within' the concept of USA.
• Co-Reducing Concept principle to any existing Internet search engine with dramatic results.
• the Co-Reducing Concept Principle is applied by continuing to clearly prompt the user for further concepts and then existing search engine logics uses these to eliminate those records that do not match all the concepts now being supplied.
• the process can be continued indefinitely, and thereby, a user can narrow down hundreds of thousands of hits to the two or three he requires, and without requiring any knowledge of understanding of Boolean operators, or of how to construct complex advanced searches.
• this method from the Any-to-Any machine can solve the considerable problem in the state of the art, that 70% of websites are not listed on any search engines at all.
• this query mechanism not only supports incremental searching, i.e. "dynamic searching,” by simply intersecting the dependency trailer sets one at a time and displaying the intermediate results, but the dependency trailer sets can also be pre-filtered using the relationship types. Further, the sets may be combined using any valid set operators such as union or difference, and not just intersection.
• FIGS. 19A-H these figures illustrate the various generic field names and data categories described in the present invention.
• Data category field 502 contains the various indications of the six major categories previously described, i.e. Life, Time, Space, Action (Energy), Matter, and Administration.
• Field number field 504 contains the assigned field numbers for each generic field name.
• Generic field name field 506 references the name of the particular field associated with a particular record number in the record number field 504.
• Information field 508 contains a brief description of the particular fields represented by the field names in the field name field 506.
• Examples field 510 contains short examples of the type of data that is associated with the field number 504. A majority of these field names and modules are more clearly described in the remainder of this detailed description.
• Human language can be turned into a Concept Language if the original language is considered to be, and is treated as a lossy compression data transmission system.
• the first step is to transform - in any convenient fashion - any words in the language that do not have unique meanings, into symbols (such as words or numbers), or combinations of symbols each of which do have unique meanings.
• symbols such as words or numbers
• Concept Language The main requirements for a Concept Language are essentially (but not wholly) a language for use in a computer where:
• a CONCEPT LANGUAGE is an invented term and is further defined as: 'A language in which each individual unique and whole concept or whole meaning is represented by its own unique Concept Symbol, or by its own unique combination of Concept Symbols.'
• a single CONCEPT SYMBOL is defined as 'a single and unique symbol, different from any other symbol, which represents a single, and whole, and unique thought or idea.
• a Concept Symbol in more detail, in the English Language, some words meet the requirement for a Concept Symbol.
• the concept that is conveyed by the symbol '1' is unique.
• the symbol '1 ' has only one, unique concept or meaning attached to it.
• the concept of '1' is not identical to the concept of '1.1', and it is not identical to the concept of 'almost 1', and it is not identical to the concept of a 'car'.
• '1 ' is not identical to any other symbol, and the concept associated with it is not identical to any other concept.
• the symbol '1' qualifies as a single Concept Symbol.
• the word "banana” does not qualify as a Concept Symbol because it has several meanings: 1) 'this is a banana', (a fruit). 2) 'He is a banana' (type of person). 3) The shoots of the young banana are eaten as a delicate vegetable (a plant) 4) shades of banana and cream (a color).
• banana can be used in a Concept Language if each unique meaning is identified "by a unique symbol or combination of symbols”. This can be done by designating the respective meanings as 'bananal” banana2" banana3" and "banana4" for example.
• a Concept Language formed in this manner using words from a language such as English is referred to as an "X Language Concept Language" - for example, as in this case - 'ENGLISH CONCEPT LANGUAGE.'
• a CONCEPT STATEMENT is defined as a series of Concept Symbols together, with or without spaces between them that are joined in some recognizable manner.
• the programmer can be successful - provided he de-compresses the transmission first.
• the world of modems consists of not just one modem language - one set of protocols and compression methods, but of several hundred sets corresponding to the several hundred languages in the world.
• one community of modems can not talk directly to any other group of modems but needs translation routines that translate, not the original data, but can only access the compressed data.
• This Any-to-Any machine then, is a set of methods to take any such human compressed transmission - a spoken language - and convert it to a Concept Language, which is a computer manipulable form of its original meaning.
• Any-to-Any machine is described as a series of methods by which a particular form of compression in use in a particular language can be detected and eliminated, in the process of translating the human language into any convenient Concept Language Once a language is viewed as a compressed transmission medium, any language can be translated into Concept Language.
• De-Compression method 1 relate new data to previous data . If one person asks another Tell me everything you know about bananas' the resulting reply may occupy a minute of talking, or several hours of talking if the person is an expert on bananas. Clearly, in that person's mind, the single word 'bananas' has a concrete relationship to a very considerable body of knowledge. The situation is similar to looking up the word "banana' in an encyclopedia, and there, directly related to the word 'banana' by physical position on the page, are many lines of description concerning 'banana'. Simply saying to someone the one word 'banana' and then asking that person, 'when I said 'banana' what did you think of?' will also demonstrate the existence of this relationship.
• the word 'banana' can be viewed as an extremely compressed form of the person's banana-knowledge package, exactly as the title of a book is a compressed reference to the book itself. Saying only the words The Bible' to someone, and asking them what came to their mind shows the relationship that exists in their mind between the book title and the body of knowledge that is the book itself.
• the single word 'banana' is a symbol that actually refers to, and is a compressed form of all memorized knowledge of banana.
• Cat' is a compressed form, and refers to all memorized knowledge about cat.
• 'John Brown' is a compressed form of, and refers to all memorized knowledge about John Brown - as this conversational example shows: Person 1 : 'John Brown went on holiday.'
• Treating language transmission as compressed data that should be decompressing the data - in this case by recording the relationship of the symbol to the data - enables the computer to copy one of the human data handling methods.
• the Data Relation Table as previously escribed, enables the relationships of new and old knowledge to be related togetyher and to be found as required, and once found, to be used as needed.
• a query phrased as "tell me everything you know about George Brown” will elicit everything known about that individual.
• De-Compression Method 2 relate each meaning of a word to its definition: Consider now a further applied to single word compression: Person 1 to Person 2: 'Oh!' Person 3 to Person 2: 'So you spoke to Person 1. What happened?'
• the "Definition" field OR record type, in a Data Relation Table (if used) provides a method for doing this.
• the record that contains the Concept Language statement for a particular meaning of a single word can either point to, or be treated as paried with, a record or series of records that is the definition of that word. Consequently, when necessary, the recorded definition of a word can be used to 5) De-Compression Method 3 - Concept Heirarchies.
• That relationship between the word 'train' and the word 'fly' is not stated anywhere in the above conversation.
• a review of the definitions of the word 'fly' shows they do not usually contain 'train' or any variants of the word 'train'. Yet a relationship should exist or otherwise Person 2 would not have replied 'He flew' but would have replied 'What do you mean by 'train' to New York?.' Further, there is no reference text that can be referred to that says: " 'train' and 'fly' are related". However, if a data relationship that exists for people is not also enabled for a computer, that computer will not 'understand'.
• Amethod for detecting Concept Heirarchies in a language concerning actions is as follows:
• Matter Data Category Table When looking for concept heirarchies, it is useful to ralize that each data Category has its own type of Concept Hierarchy.
• Space Data Heirarchies are within one another - New York is within USA. Matter data categories are types of things.
• a Chair is a type of furniture. When the meaning of "New York” is a thing, it is in the Concept Heirarchy of types of things - it is a member of the type of thing which is a city. When it is being used with a meaning of a Space, it is within a Space Concept Heirarchy, where one thing space is physically within another.)
• the word 'do' is the word most commonly used to query for the concept of any action of any kind: "what does a fax actually do?" 'What is the weather doing?' 'When are you going to do that?'
• the word 'do' effectively covers every single type of Action that can exist. However, the word 'move' covers only a portion of all the actions covered by 'do'.
• Other categories of 'do' exist besides the 'move' category - for example, the 'think' category, containing words such as 'think' 'suppose' 'wish' and so on.
• a Concept Hierarchy is established by checking if there are other similar concepts to the concept in question, and if so, checking if those similar concepts are covered by a word that expresses the concept of the group to which they may both belong. If such a word does exist, that word is the concept of the senior group in their hierarchy and the concepts of the words in question belong to that group.
• the type of questions that can assist with this are A) 'is this word a type of something? And B) Are there other types of this? 6) Each Meaning has its own Concept Hierarchy
• banana' has at least four meaning as previously described. Each meaning has its own Concept Hierarchy.
• 'Banana' as yellow color includes 'color' and 'yellow' in its Concept Hierarchy. For example: 'Is it yellow?' 'Yes, it's a kind of banana color.
• ' 'Banana' as a fruit includes 'fruit' in its Concept Hierarchy. For example: 'Do you have any fruit?' "Yes I've got some bananas.'
• the second compression is the end-coding '-ed'.
• '-ed' actually codes a second concept into the word, a concept that can expressed as 'completed' or 'time past'. This is itself a Compression, being properly tralsated into Concept Language as "Time & past time' (Time Concept Heirarchies are withing' one another. Wednesday is 'within' 'a week'. Time is also a continuous stream - and this is represented in the Data Relation Table, as a Data Relation Table is a continuous record of all events).
• the three concepts in the one word are completely different concepts - one is a concept of any action, one is concept of a particular type of machine action, and the last is a concept of time.
• the fact of the match causes execution of the matched software module to occur - which, for example, sends the file to a print module.
• the computer prints the letter. Changes the record from 'do & print & scheduled & letter' to 'do & print & completed. & letter'. Person to Computer: 'What have you done?
• Decompressing a word into individual concepts that are stated in a Concept Language in the Data Relation Table is one method used to enable a computer to answer questions such as those in the above example.
• invitation invitingly, invitational, invitationally, invitee, inviter, invite, invited, inviting, invitationable, invitationableness, uninvite, uninviting, uninvitingly, uninvitable, univitableness, de-invite, de-invitational, re-invite, re-inviter, re-invitee, re-invited, re- inviting, dis-invited, de-inviting, non-invitingly, non-invitable, non-invitableness, non- invitably, unre-invitable, and so on.
• Boss to secretary at a later date 'who have we invited to the party?' Secretary to Boss: 'Joe, George....'
• the word beginnings such as 'un', 're', 'non', endings such as 'able' 'ableness' and so on are considered by the to be compression codes of different types.
• Some codes are function • codes such as 'able' as in 'invitable', which can be decompressed to: 'do & invite & possible 'Invitingly' can be decompressed to 'do & invite & time now & quality', '-ly' is a function code, coding the word as the quality of an Action, re-invited can be decompressed to 'do & invite & time past & repeat' 're-' is a function code, coding for the concept of word for 'repeat action' re-invitedly can be decompressed to 'do & invite & time past & repeat & quality'
• Some compression codes for existence for example the 'less' in 'invitationless' (as in '
• Compression Codes are used in the Languasge Processing code in the form of rules.
• Word to which "ly” is added is a quality and applies to the nearest word of action to be found.
• Appplying the rule will, in each case detect the work 'invitingly' as being a the quality of the action of looking and enable the Concept to be correctly recorded as a Quality (rather than as a thing or as an action) in the Data Relation Table. Due to the presence of the Number Concept Language number for the Base Concept of 'invite', in both the above examples, a computer query " Did he invite Jill? Will return the answer of "true" or 'yes".
• the coding is not or attached to the word itself - i.e. the word is coded by different types of codes that are found elsewhere in the text that in the word itself.
• the word 'stop' is an order.
• the word 'stop' is a location. All other words in these two examples are the same, and in the same order.
• the meaning of 'stop' to be used is coded by the position of the word itself.
• Rule 1 If 1 ) 'stop' is the first, or 2) 'stop' is the only word and 3) if it is part of an order addressed to the computer, then (it is an order to stop the current action) decompress to: Computer & do & stop & time - now & current action. (The omission of the name of the person addressed - or in this example, the name of the computer addressed is a lossy compression confined in the word "stop' when used as a first word) Rule 2: If 1) 'stop' is the last word in a Statement, but 2) not the only word, and if 3) it is part of an order addressed to the computer, then (the word is a location reference) de-compress to:
• the meaning of a word in Concept Language does not necessarily have to be represented ONLY by a Concept Symbol, but can be represented by the action performed by a rule, or by a Concept Symbol or Symbols, or a combination of any of these.
• a software module should exist that is able to actually do that action and that single action only.
• a software module called 'Stopcheck' is called, whose function would be to check if 'item X' can be stopped.
• Modules to perform specific actions can not require opening a multi-megabyte software package, but should be instantly and quickly accessible, execute, and terminate. (The non-hierarchical manner in which Software Modules are record in the Data Relation Table allows this). 12) De-Compression Method 6 - Relative Proximity Compression Coding - Enabling a Computer to Determine from the Context which Meaning of a word to applies.
• Relative Proximity Compression Coding decompression enables a computer to determine the meaning of a word to be used based on contexts. Where a great distance in terms of number of words separates the word in question and the words that code its meaning requires creating the rule in a suitable fashion to account for this. Where a word meaning can be changed by context - the word 'roam' for example - suitable Encironment Concept Coding Decompression Rules determine whether the subject under discussion is telephone or people and hence which meaning is in use, and hence, which Concept Symbol to assign.
• 'Compression Operator Words' are defined as 'words that, while they may also have a meaning, are also code words that carry information selecting or affecting the meaning of other words or groups of words.
• the word is a compression operator - it codes concept package end and concept package beginning without using any additional symbol to do so. But the word 'and' also performs a second compression operation. 'I want to go to town, and buy a banana', decompresses to: "I want to go to town" "I want to buy a banana"
• the language processor finding the word "AND” calls code that does the following:
• Compressor Symbol- it operates on the word it is attached to and adds a separate concept of 'quantity of 2+' to the word it is attached to.
• the trailing 's' does not operate on the word it is attached to but on surrounding words - 'the dog's collar is red' - the trailing 's' operates on the word 'collar'. It is then acting as a Compression Operator, in that it is a compression that operates on or has an effect on a word or words other than the word to which it is attached.
• the 'dog' concept preceding 'are' can be either singular or plural, hence the word are .
• Neither the trailing 's', nor the word 'are' are redundant, each of them performs a function.
• Joe Blow is an investment banker Joe Blow has an old office. Joe Blow has a new office The distance between the old office and the new office is two miles
• Any-to-Any machine method that enables a computer to Decompress Structural Compression is also the method that solves the following requirement for an Understanding Computer.
• Location 'I will go to 'to' selects the Location meaning of 'go' hence location now required. 'I will go to town 'town' satisfied 'will' and 'go' but requires something about 'town' - satisfied by 'to'
• 'and' in the Any-to-Any machine is classed as a Operator Word and one of its operations is - in the particular case of the above example - is to state that the previous Statement is complete. If the person in the above example had said: 'I will go to and' these words do not 'make sense' and prompt the query "you will go to where?? The requirement for a Location has not been satisfied, although 'and' operates to state the words so far received are complete.
• associated software receives 'statement complete because of the rule activated by the word 'and'. However, the Requirement Rules are not satisfied, and hence, software treats the words so far received as incomplete. Software can identify the missing data as a Location and can now query for the missing location: 'you will go where??'
• Any-to-Any machine method applies in the simpler domain of computer control.
• the Requirement Rule of the word 'print' requires something to print. If the user issues a command 'Hey computer, I want printed OK?' The requirement of the word 'print' to have an identified item to print is not met by the words received that the user has stated he considers complete by using the word 'OK'. The Statement is incomplete and the part that is incomplete is the Requirement Rule of 'print' for something to print.
• This method of the Any-to-Any machine enables a computer to detect when it has received words that do not 'make sense' in human terms and also enables a computer to detect why it does not 'make sense'.
• the fact that the computer can detect what it is about the words received that do not 'make sense' enables the computer to take appropriate corrective action. (This method does not enable a computer to have 'judgement'. It simply enables a computer to copy the way a human handles the words).
• a human rarely uses probabilities in determining a word meaning and then only when there is no other way. Even so, if the execution is desirable, he will rarely execute based on a probability. A human prefers to query the uncertainty and attempt to clarify it (or if that is not possible, not to act at all).
• the Complete Statement method has the additional benefit of enabling one of the steps required for a computer to lean. Firstly, learning obviously can not occur in the absence of memory. 18) The Nature of Memory Requirement for Learning to Occur
• a person's first question on encountering a new object is invariably 'what does it do?' or an alternative phrasing such as 'what is that thing for?' - the first thing the person wants to know is what are the capacities of the object.
• a child asking: 'What is that daddy?' That a saw, Johnny.' 'What's it for?' 'It's for cutting wood, Johnny.' The child stores this data for subsequent use.
• the associated software records the new relationship also.
• the first requirement for learning is that previous known data is recorded.
• the Complete Statement method by detecting things that 'do not make sense' detects that there is something to learn, and this something is either an error in data so far received, or new data unknown to the computer.
• the Complete Statement method enables the computer to alert the user to the fact that the data it has received 'does not make sense', and why. The user, just as he does in life, with other people, will supply the correction or the missing data.
• the following illustrates this further in a business environment using the word 'roam'.
• the computer may have recorded only one meaning for 'roam' as 'aimless movement'.
• the computer receives the statement "my telephone is roaming'. Part of the Requirement
• Rule for 'roaming' will be that it requires an object that is capable of moving unassisted, but the telephone is recorded as only being able to move when assisted.
• the user's statement is not a Complete Statement because the Requirement Rule for the word 'roam' is not satisfied.
• the Complete Statement method enables a computer to detect when a received statement is incorrect, or when existing definitions are incorrect or missing further word meanings. The fact of this detection enables software routines to issue a query such as 'Can telephone's roam?' The user will reply 'yes'
• a desirable aspect of the associated software using the Concept Language is that - in order to act in a human manner - it needs to be able to lay a task aside and pick it up later, and suiteable scheduling modules can do this.
• the associated software needs to be able to lay aside processing a text into Concept Language and complete it at a later time.
• most general-purpose computer processors are idle 99% of the time. Text is seldom required again immediately after it is entered. Therefore, the software using the Concept Language can utilize the ability to lay aside tasks and processor time that is not used in the state of the art, to process text into Concept Language format without irritating the user with delays on more urgent tasks.
• the software that implements a Concept language should be adapted to the easy addition and change of rules (The Data REIation Table is so adaptable).
• a single computer can hardly be pre-loaded with all knowledge there is on everything, and hence every computer that understands should have the capacity to learn.
• a 'capacity to learn' is not something nebulous, but simply a capacity to record new word definitions and new rules in memory, and use the new rules, together with the pre-existing rules, and pre-existing data, for future computation.
• a computer that understands is effectively a computer that copies human methods of data handling. Therefore, human methods for handling data should be observed before they can be copied.
• Human methods for handling data can be implemented in a computer if language is treated as a lossy, multiple compression data transmission system. Language can further be treated as a system in which the De-compression required is entirely rule- based, and the inter-acting complex of De-compression rules apply to each different word, as well as to blocks of words.
• the first objective of decompression procedures is that each unique meaning is related to a unique symbol or a unique combination of unique symbols. The unique symbol or combination of symbols can then be related to a unique execution, and hence, the unique execution is related to a unique meaning.
• the first requirement in order to begin decompression is the creation of a Concept Language, in which each symbol is unique and has a unique meaning associated with it.
• the second object of decompression is that the decompressed form of the word enables software to maintain the same relationships between words that a human maintains.
• Decompression rules have as their object enabling software to copy human data handling and are therefore detected and isolated by simple empirical observation of the way humans use each word under a selection of different circumstances. When doing this, punctuation that is not evident in the spoken word should be ignored.
• the resulting Concept Language statements can be then recorded in such a manner that each unique execution to be done by the software can be related to its own unique statement.
• the computer can be ordered in Normal Language. Whether or not the computer can then perform the ordered execution depends on whether or not a unit of software - called a Software Module' - exists to perform the execution that was ordered.
• the process of de-compressing a language is itself an execution procedure and has certain specific memory requirements for the associated software system.
• two types of memory can be considered to exist: • 'Content Related Memory' is defined as memory to do with the content of a thing.
• An example applying to a computer would be the content of a letter or a book - the actual text.
• An example applying to a person could be the exact wording of the exact phrase he spoke at 9.31 am 613 days ago, or what he had for dinner 1129 days previously.
• • 'Execution Related Memory' is defined as memory that is able to be associated with execution.
• An example in the case of human would be that he remembers that 'he telephoned Joe last week about the banana shipment'. He remembers that plate glass windows should not be walked through. (Words italicized to emphasize the execution- related aspect of the memory). These memories are execution-related. (A human does aiso have Content Related Memory). Computers have fantastic Content Related Memory. If a computer has had recorded on its disks the entire Library of Congress it can return every single word, in the correct sequence without a single comma out of place. However, humans have comparatively poor Content Related Memory.
• de-compression of language requires Execution Related Memory, and can not be performed properly if such memory is not easily accessible.
• the final benefit is that using this Any-to-Any machine, the user no longer should learn the computer. Instead, the computer learns him.
• Each Concept Symbol composing the Concept Language may have only one meaning
• Each individual meaning that can exist in the spoken language to be translated into Concept Language are represented by only by one unique Concept Symbol or by only one Concept Symbol combination in the Concept Language.
• Concepts expressed in the Concept Language are related to one another in the same manner that a human relates those concepts, or can be so related by associated software.
• a Concept Language exists, and the rules for translating between it and one spoken language - such as English - also exist, then the Any-to-Any machines can use it to make two different levels of an 'Understanding Computer': 1) Concept Language can be used to control the functioning of a computer based onm a user's Normal Language input. While total control of the computer with Natural Language is then possible, this does necessarily mean that the computer can answer questions on the data it contains. Content - such as the content of a letter or a book - can still be recorded in the computer in Normal Language - the same manner it is recorded today.
• the computer can be ordered in Normal Language to perform any manipulation of which the computer's software is capable, and will do this successfully. But it will not be able to answer questions on content recorded in Normal Language. 2)
• this Any-to-Any machine is to translate all data entered into the computer into Concept Language before recording it - for example, all documents, all letters, all reports, all spreadsheets, and all data base contents etc. In this case, the Any-to-Any machine enables a computer to answer questions on the data it contains.
• Each spoken language requires the Any-to-Any machine's methods to be applied in a different manner to convert that spoken language into a given Concept Language.
• Each spoken language requires the Any-to-Any machine's methods to be applied in a different manner to convert a Concept Language into that particular spoken language. Conversions between the English language and a Concept Language that are devised per the Any-to-Any machine's methods will not all work for another language, which will require other conversions to be devised using the Any-to-Any machine's methods.
• Any-to-Any machine does not take a conventional view of language - conventional views have so far failed to produce computers that understand. It has already been mentioned that the Any-to-Any machine ignores most punctuation and the subject of grammar, because grammar classifies and describes word functions, and does not assist with interpreting meanings.
• the Any-to-Any machine is a series of methods for classifying and otherwise handling the meanings of the words in a given spoken language, such that applying the methods of the Any-to-Any machine, enables a person suitably qualified in a specific language to create a Concept Language that can then be used to control a computer.
• a Concept Language has several requirements it needs to fulfill in order to be useful in controlling the functioning of an Understanding Computer.
• One of the first and most obvious of these requirements, and an area of problems in the state of the art, is the subject of identifying documents or items that software is required to manipulate.
• the computer can not understand the human's specification for a specific item, and the human can not remember the software's specification for a specific item. Consequently, the identification of items to be manipulated by software is an aspects of the human-computer interaction problem that a Concept Language should take into account. It should be able to receive human item specifications and issue something to the computer's software that enables that software to identify the item concerned:
• any software is essentially 'Perform action 'A' on item "X."
• a small piece of software could easily be written that would perform action 'A' - for example, print any item.
• the human can not remember any of the ways that software uses to specify an exact item such as a letter.
• the software can not understand any of the ways a human uses to specify a unique item.
• a small software module called 'Print' could be written easily, and could be coupled to and launched by a human saying 'Print (item specification) X'. But there is no point in doing this, because the software cannot identify exactly which item the human is referring to when he gives his specification for X.
• an item - such as a letter - can not be identified, unless the specification that may be used to identify it in the future is recorded in the first place. It is only possible to identify (and thereafter, retrieve) a letter specified by a statement such as "get me the letter from Joe' if it was recorded in the first place that the letter came from Joe.
• software can not identify an item from a human specification, unless the software has recorded in relation to that item anything and everything that could be part of a human's specification for that item. Consequently, the first requirement is to identify what type of data a human does and does not use when specifying items on which he wants an action performed by software.
• a specification that a human issues with the intention of identifying the exact item he wants is termed a 'Unique Data Specification.
• the human issues a Unique Data Specification with the purpose of exactly identifying a specific item or item and that item or items alone, while excluding all others that he does not want. He expects that the specification he issues will identify the exact, unique item he wants, and will also exclude all other items that he does not want. If a boss says to his secretary 'Get me the letter Joe sent from Chicago about Bananas' he says so expecting that his Unique Data Specification will pick out the one item he wants, from the tens or hundreds of thousands of items to which his secretary has access. He considers his Unique Data Specification will identify a unique item.
• a 'Unique' Data specification is unique not in the sense that it unique means 'one' item, but 'unique' in the sense that only specific items - the ones he requires - will meet the specification, hence the items are unique in that no other items meet that specification.
• the word 'Data' is used in the broadest sense. Not everything the human wants to identify is necessarily a document. He may want to identify a person's address, or a printer or some other peripheral. The term 'Unique Data Specification' covers identifying all of these).
• the more precise definition of the problem preventing software from recording data that could be used in a human's Unique Data Specification is that the types of data a human uses in Unique Data Specification need to be identified so that they can be recorded and used. But even before identifying the types of data to be required, it is first desirable to invent a system to copy the way a human uses data to specify something. Only then is it possible to identify the types of data needing to be recorded and make arrangements to record them.
• Boss to Secretary Get me the letter.
• Boss to Secretary The one I sent to Joe.
• Boss to Secretary The one about bananas.
• Boss to Secretary The one he sent me when I was in Boston. Secretary to Boss: Oh that one. OK, I'll get it.
• the first Data Specification "get me the letter', used the word 'letter' - word that means 'one letter.'
• the Data Specification resulted in a data mismatch - 'the' has a meaning of 'one' in this instance, and this mismatched with secretaries recording, namely that she has many letters filed, not just one.
• the data mismatch lead to the query ('which ones?'), and when queried, the boss added a two more concepts to his data Specification 'sent to' and 'Joe'.
• his Data Specification was still not unique - several letters met those criteria, and a mismatch between his specification and that the letters the secretary knew to exist, and this caused a further query 'Which one?
• the Co-Reducing Concept Method enables a computer to copy the way a human uses a Unique Data Specification.
• the Co-reducing Concept Method has the effect of enabling software to ensure that it has sufficient different types of data available, so that a computer has adequate data with which to match any Unique Data Specification it is given in order to locate the required item. (Associated software (for example, the Data REIation Table) should provide for a) Detecting data mismatch between the Unique Data Specification and the data found in response to the Unique Data Specification.
• a word is effectively a name, a label, for the concept that is its meaning.
• the word 'banana' (with the meaning of the name of a fruit - there are other meanings also) is an example.
• banana(m) is labeled with the word 'banana'.
• the words 'New York' are a label for a specific package of meaning New York(m).
• 'My' is a word that conveys the concept of 'everything belonging to me.' It is not limited in any way. Anything that is the speaker's, is included and falls under the word 'my'. Everything that does not belong to the speaker, is excluded and does not fall within the meaning of the word 'my.'
• a Concept that has not been labeled with a specific word is described in language either by: 1 ) Giving it a name (which may then be called a 'word' if it applies to a frequently occurring phenomenon or a 'name' if it applies to only one of something or a to a specific group of something), or by:
• An item is specified by adding any one word to any other word, with the corresponding result that the Concept encompassed by each word is co-reduced to that part of the Concept of each that is common to the other.
• the processes is continued by adding any other word - and hence its corresponding Concept - to the pre-existing words - and hence Concepts.
• Each new word that is added further reduces the Concepts encompassed by the previous words to that part of the Concept of each of the words that is common to all of them.
• the process is continued until the part of the Concept common to all words present is the Concept that the person wishes to state.
• This Co-Reducing Concept Method is used in the Any-to-Any machine, in combination with previously mentioned Concept Hierarchies, to identify the types of data that need to be recorded in order to ensure a human's Unique data Specification can be met - if implemented in the appropriate software.
• the Any-to-Any machine views words as labels that humans ascribe to things.
• the word 'banana' can be considered a label for a person's knowledge about 'banana.' Humans assign labels to anything and everything.
• the Any-to-Any machine views a spoken language as a means of communication, consisting of labels for:
• a language is a means of communication consisting of labels for:
• Time, Space, Energy Matter can be added the category of 'Life' as word to label the aspects of a human being that can be recorded in a computer (Names, Emotions, Qualities, Reasons). This gives a final list of the categories of Meaning Words that can be recorded in a computer: Life, Time, Space (Location), Energy (Action), and Matter. These five Divisions of data, when used for recording in a computer, are termed 'Data Categories.'
• Data Categories are an invented method that is used to classify and manipulate the meanings of words.
• Phenomenon 1 The single, individual Concept Symbols in a Data Class each label a single meaning, and therefore, can not conflict with one another, and are therefore Unique. Because of this phenomenon, a selection of Data Class values from different Data Classes constitutes a unique statement. Therefore, adding sufficient Data Class values to one another, can constitute a unique specification for anything. For example, a concept exists to which the name 'chair' is given. No other concept whatsoever is the same as the concept of 'chair'. Every other concept is different to the concept of 'chair'.
• Phenomenon 2 Queries can only be answered with a value from their own Data Category.
• each query can be answered with absolutely any value from its own Data Category but can not be answered with any value from any other
• Phenomenon 3 Data Categories can be sub-divided into Data Classes that display the same behavioral phenomena as Data Classes:
• humans also query by Sub-categories of these Data Categories. For example, a human will query 'What furniture is in the room?' The word 'furniture' covers is a sub-division of the Data Category of Matter, i.e. a Data Class, and the Data Class of furniture includes - chairs, tables and so on. Exactly as for Data Categories, when a human issues a query for something from a specific Data Class, he expects to be given an item from that Data Class and not from another one.
• this database has data such as the above recorded in it for all documents produced by all the members of a large company.
• search will be a long one as there may be hundreds of thousands of letters going back many years.
• search begins by searching all files in the computer for the content of 'banana', the search will return, as it does in the state of the art, a list that is impossibly long and therefore useless, as well as taking an inordinate time to execute.
• the search is executed in the order of the Data Class Functional Hierarchy, i.e. from outside inwards - the two Life Data Categories first- the search is being conducted on the smallest number of potential matches and is therefore as rapid as possible.
• the search begins with items contain both the Boss and Joe, of which there will be relatively few. Those items concerning both of them the Boss was in Boston will be fewer still. The number of items the Boss sent to Joe at that time are unlikely to exceed a small number.
• the very last step, per the Data Class Functional Hierarchy will be to search the content of the remaining few items for the one containing the content of 'banana' - using state of the art content search technology.
• the information or data required, then, to locate specificJtems can, in theory, be entered at the time of their creation into Data Classes represented as fields in a database. Additionally, Data Classes exhibit certain phenomena that enables an item to be found based on a human Unique Data Specification and found rapidly. The remaining requirement is to identify the Data Classes that are need to be used, and the values in those classes that need to be recorded, and these depend in part on the applications to be used and hence, the items that will need to be located.
• Data Categories do not change, Data Classes are not a fixed rigid list, but are added or subtracted depending entirely on the intended application. There is little point in having a Data Class for water pump controller names if the Data Classes are to be used in an office application, and equally little point in having a Data Class for printer names in an application controlling water pumps in a power station. Hence, the exact selection of Data Classes depends on the application to be controlled, and hence, the vocabulary to be used, as follows:
• Any spoken Language consists of a quantity of words used by most people speaking the language natively and these can be called 'General Use Words'. Every language then has various blocks of words that are used in specific activities, such as accounting or astronomy, that can be termed 'Specialist Use Words'. Hence the actual words that need to be translated into a Concept Language includes the General Use Words and may also include Specialist Use Words depending entirely on the application with which the Concept Language is to be used.
• the first step in incorporating Data Categories, Classes and Sub-Classed into a Concept Language is to identify the separate and different Data Classes that exist for the intended application.
• this method creates a limited Concept Language that is capable of being used to control a computer in most cases, but will not take account of different phrasings used to say the same thing, nor will it enable a computer to answer questions on stored content.
• the main benefit of this method is that it creates a mechanism to exactly identify documents and peripherals. Such identification can then be related to and used with software modules such as 'Print X' previously described, provided the user uses the specific word 'Print' or whatever synonyms the programmer has provided for 'Print'.
• This method produces a major benefit by itself as it solves one of the major problems that exist in the state of the art - the increasing and major difficulty of locating the right document in a computer, especially as these increase in number.
• the more thorough method is to use the method of Concept Hierarchies because the Concept Hierarchy Method identifies all Data Classes anywhere in the entire spoken language being converted into a Concept Language. Because the Concept Hierarchy Method can be used with the entire language, as opposed to just those parts of the language used in document identification, the Concept Hierarchy Method enables all Meaning Words in the whole spoken language to be classified into Data Classes and Data sub-Classes as part of the translation process into Concept language.
• the additional benefit of this method is that when all data in a computer can then be stored in Concept Language form, enabling the computer to answer questions on the data it contains.
• a word's Concept Hierarchy can not be found mechanically by software but should be found manually by observation and analysis of the word's use in practice.
• One method for doing this is:
• a Data Class is a group of words or items that have the same senior in a Concept Hierarchy.
• the words 'fly' 'bus' 'car' are used in with the meaning of actions, not the meaning of the physical objects.
• Their Concept Hierarchies are: do & move & travel & fly do & move & travel & bus do & move & travel & car
• the words 'fly' 'bus' 'car' (as actions) are values in (members of) the Data Class named 'travel'. Travel' is itself one value in the data Class of 'Move' -other members might be 'slide' 'skate' and so on.
• an application to be programmed can be extremely limited, and not require an extensive language review in order to identify the possible Concept Hierarchies and hence Data Classes.
• the application to be programmed might be to enable Normal Language control of a telephone with a limited memory.
• what the telephone can do is extremely limited, and hence the number of possible instructions is limited also. Consequently, the Concept Language required is consequently small, and the possible Concept Hierarchies and Data Classes are very few.
• the Any-to-Any machine includes a simplified method for detecting Concept Hierarchies and hence Data Classes, consisting of 1) Make a list of the instructions the physical architecture can execute, and add to that, the list of instructions the software is required to execute (within the capability of the hardware).
• Step 1) Begin (with the Energy Data Category) and ask 'what can this computer do?
• Three of the answers might be:
• Step 4 Use what has so far been discovered and questions (as given previously to work out Concept Hierarchies) to work out the Concept Hierarchy and Data Classes for items on the two lists.
• Every Unique Data Specification will consist of one or more values from one or more the Data Classes. If software searches recorded Data Class values to find the Data Class values in the Unique Data Specification, and treats these values on the Co-Reducing Concept Method, then the correct item will be found and incorrect items will be excluded.
• the Any-to-Any machine methods of Data Classes and Concept Hierarchies produces specific benefits, two of which are:
• Every individual Concept Symbol used as a component of Concept Language may itself not contain more than one, single meaning.
• a Concept Language consisting entirely of numbers - called a Number Concept Language is much faster for a computer to manipulate than a language consisting of word, and is therefore the most desirable type of Concept Language, and the one that should actually be used by associated software, but 2) Such a number language is virtually incomprehensible for a human. If a spoken language is transformed directly into a Number Concept Language, it is very difficult to compare meanings and symbols assigned to them.
• a Number Concept Language is also much more compressed than a Concept Language that is created using existing words in a language, and this makes it even more difficult for a human to understand.
• Steps to Create a Language X Concept Language The following steps presented in the order of the sequence that can be used to create a Concept Language. However, the steps may have to be done several times, as the result of one step affects the work that was done on a previous step. Equally, as a person progresses with the steps, the depth of understanding of how the language is working in the light of the teachings of the Any-to-Any machine increases, requiring previous steps to be redone. The Steps are complete when it is found that no further conflicts exist between the results of one step and those of another step.
• Step 1 Select a vocabulary suitable to the intended application for the Concept Language
• Step 2 Divide the words of the vocabulary into Meaning Words and Operator Words, using the methods to be described. This division is useful as the two types of words are treated differently by the Any-to-Any machine.
• Step 3 For each Meaning Word that takes multiple forms, isolate each individual Base Concept.
• a 'Base Concept' is defined as 'that part of the overall meaning of a word that does not change, despite different suffixes or prefixes or forms of the word. For example, the word 'invite' takes multiple forms - invite, invitation, inviting, invitational and so on. (Operator words do not take multiple forms and this is one of the indicators of an Operator Word).
• Step 4 Make a full list of all prefixes and suffixes existing in the language
• prefixes and suffixes are a mixture of Operators acting as a compression code on their own word, Meaning Words that have their own meaning, and some are both Operators and have a meaning.
• the major types are:
• Time Operators are compression codes for time, '-ed' on a word of Action for example, adds concept of 'past time' to a word, and that past time then operates with the word it is attached to with the Co-Reducing Concept Method.
• prefix and suffix additions occur more frequently in the spoken language than in even the largest dictionaries and the only way to find all possible combinations is to test each word with all combinations of prefix and suffix.
• prefixes and suffixes are used ad-hoc to create words that are clear to the listener, and therefore, should be clear to an understanding computer, but are not found in any dictionary.
• Dictionaries inevitably record the words that both existed and were accepted by the authors as existing and as being acceptable, some time prior to the date of printing.
• dictionaries are to some extent historical, while a computer should operate in present time. Also it is not the place of a computer to dictate acceptable grammar and word usage, but the place of the computer to understand, if at all possible, what the user means.
• each combination should be checked for prefix and suffix additions that result in the word having a special meaning that is not simply the meanings of the prefix or suffix and the Base Concept combined.
• assign a Concept Statement to the word as per the instructions for doing this assign a Concept Statement to the word as per the instructions for doing this.
• An example of such a word is 'unprintable' which has three meanings that are not found in the Base Concept of 'print' 1) 'can not be printed' 2) 'not fit to be printed' with a conation of rude or obscene 3) trousers.
• Combinations should each be tested for their ability to combine further such as 'unre-printableness - a word than can be understood but that can not be found in a dictionary.
• Step 6 Assign Concept Symbol or Concept Statement Concept Symbols or Concept Statements are assigned to each meaning of each word, and each Variant, at the same time assigning Concept Hierarchies to each word as it tested. Do this by following the methods described in detail to do this.
• the first objective of a Concept Language is to convert each word that has more than one meaning under any circumstances that are likely to be encountered, into a form such that:
• Each different meaning of a word has its own Concept Symbol or Concept Statement (a combination of Concept Symbols). For example, the word 'worked' decompresses to 'work' & 'past time'. It Concept Statement
• Step 7 Create Concept Language Definitions.
• the next step is to define each word, using the Concept Symbols that have been created in the previous steps.
• a full definition of a word will be found to consist of the existing Concept Statement plus entries in other Data Categories than the Data Category of the word.
• the meaning of the word 'roam' as used in telephones is distinguished from all other meanings of the word, by the fact that it applies to telephones, as opposed to the other meanings, all of which apply to a person or thing that has the ability to move.
• Operator Compression Coding can act to select different meanings of a word - as in the example of the word 'dogs' given in the summary.
• Proximity Coding is defined as 'something outside the Statement where the word occurs, codes the meaning of the word to be used.' This is the case with the word 'roam' as used in connection with telephones, where the mention of 'telephone' - or some equivalent of telephone such as 'mobile' - may occur at a considerable physical distance in the text from the use of the word roam. It is a fundamental teaching of the Any-to-Any machine that software can identify the specific meaning of a word in use, provided that there is a rule that software can use to detect which meaning to use. It is a further teaching that a rule can be created provided there is at least one characteristic of the meaning that is detectable.
• Emotional content Some words contain an emotional concept as part of their meaning and if the Data Class of Emotion is used, the Concept Statement can include the appropriate Concept Symbol for the emotional concept of the word in that use. This lays the groundwork to enable a computer to give emotionally appropriate responses to statements addressed by the user to the computer. For example, if the user says "Damn you!' to the computer, part of those words is a concept of emotion - anger.
• Step 10 Create and Test Meaning Detection Rules.
• Meaning Detection Rules are partly composed of rules applying to individual words, and partly of Operator Rules. These rules interact, and because of this their effect rapidly become extremely complex, and in order to be sure they are correct, their affect should be tested on a wide variety of texts, preferably using software designed for the purpose, and individual rules adjusted as desired.
• Step 11 Create Operator Rules
• Operator Rules are the rules concerning Operation Words. They first of all detect which 'meaning' of the Operator Word to use. In the case of the Operator Word, the 'meaning' is at least partly an operation that is performed on another word or words, and enables those other words to be correctly translated into Concept language. In the same manner as every meaning of a meaning Word should be found, so should every 'meaning' - every operation - of an Operator Word be found. If the operator word only performs operations and has no other meanings, then each meaning requires at least one rule to detect that that meaning is in use, and another to perform the operation that is that meaning. If an Operator word also has a meaning like that of a Meaning Word, then that meaning is handled as for the Meaning of a
• Step 12 Translate Phrases and Colloquialisms into Concept Language. At this point, each separate meaning of the words to be used in the Concept
• Step 13 Create Concept Language Output Phrasing Rules
• Control only computer Requires a limited Concept Language built from a vocabulary based on the actions that the machine is required to control, plus small General Use Words vocabulary, as described earlier for a telephone.
• the vocabulary and hence the Concept language is set by the actions of which the machine or computer itself is capable.
• This level of Understanding Computer can be controlled using Normal Language, but all its responses should be prerecorded, and it's searches for Content will be no more accurate than now exists in the state of the art. It can however identify items accurately, but the style of the content search used as part of the identification will be no better than the state of the art.
• This computer can accept orders in any machine-readable format such as keyboard, Mouse, Touch-screen, Voice (if Voice Recognition software is installed) e-mail, fax (if Optical Character Recognition is installed) or by telephone (if Telephone Voice Recognition Software is installed).
• Compression Rules are the rules that turn Concept Language Statements back into compressed, spoken or written language X.
• Step 14 Create Compression Rules.
• Compression rules reverse the effect of the different types of De-Compression described above, and enable the computer to translate data in Concept Language format into normal spoken language and supply this to output mechanisms such as screen, printer, text to speech etc.
• the Compression Rules can turn Concept Language held in the computer back into the same language X in which the data was entered, nothing stops the recorded Concept Language being processed with the Concept Language and Compression Rules of Language Y.
• the input can be in one language, or many languages, and the output in one language or in many languages, provided the
• Step 15 Create a Number Concept Language - apply the Unlimited Principle
• a useful method for creating a Numbers Concept Language is to use a Compound Number, in which specific positions in the number refer to one thing, while other positions in the number refer to something else. For example, supposing that a number is twenty digits long. The first digit can be the number of the Data Category, the next three digits are the number of a Data Class, and so on. 36) The Unlimited Principle
• a computer within the limits of the capacities of its hardware, should never limit a user in a manner that he does not limit himself.
• a 'Last Number' is defined as the highest possible number in a number series. For example, the Last Number in a series of two digits is the number '99' or in a series of three digits is '999'. This Last Number may never be used in a Numbers Language, as it is reserved for associated software to use as an alert that a number series is full and a new series, joined to the old series, should be begun in some manner.
• Step 16 Create a Number Concept Language - Assign numbers to Concept Symbols and Statements.
• Concept Hierarchies are assigned numbers with a particular method that facilitates processing them.
• a Concept Hierarchy for a given word consists of several words in Language X Concept language. For example, the word 'fly', as given in previous examples, has the Concept Language statement of:
• the query translates into Number Concept Language as 'What did Joe 4?', and any value in the Data Class that begins with 4 is an acceptable answer. If the user asks, 'how did Joe travel?' this translates to 'How did Joe 4 44 199?' and any value in the Data Class that begins with 4 44 199 is acceptable.
• Step 17 Creating a Concept Language. Format of Concept Language
• the Data Class Format Output Method is useful method to output Concept language to enable a computer to select documents or peripherals based on a human's Unique Data Specification.
• a single document (or peripheral) can have a large number of values from different Data Classes associated with it.
• Software can generally perform simultaneous searches on several fields at once, but can not usually perform several searches on a single field simultaneously.
• a userful method is to record all Data Class values that are available for each computer event in a database field of their own. Then, a simultaneous selection of a number of values from different Data Classes can be used to identify the document. This is possible provided that the document content itself (which is anyway Data Class itself) is either recorded in its own field in the same record, or, a disk reference to it is in the field for the 'Content' Data Class.
• Concept Language output in Data Class Format for common office applications can use between two and three hundred Data Classes.
• the decision on what Data Classes to include as separate fields, and which to code into the logic is a question of optimization for the particular application. If two Data Classes are recorded in one Data Relation Table field - for example by coding them with a single digit distinguishing the two, this can lead to a single field needing to be queried twice. It can also lead to a pair of Data Relation Table Records being required to record a single event. Hence, deciding whether to apportion the designation of a particular Data Class to a Data Relation table Field, or to the recording and query logic is a question of optimization for the individual application.
• the Concept Language output is natively coded for its Data Class, and the associated logic programmer can use this coding in the manner he feels is most suitable.
• Free Form Output Method Enabling a Computer to Answer Questions about Recorded Text Data Class Format output efficient output for locating items, but is relatively inefficient for large blocks of text where each sentence or phrase does not contain values from many different Data Classes. For example, every computer event has a Time value from the Time Data category, and that Time should be recorded as it may be part of a reference to an item. People frequently use time as a reference 'The thing I printed after I sent an e-mail to Joe' One item - the e-mail sent to Joe
• the Free Form Output Method for Concept Language can be a more efficient method to output Concept Language and enable an Understanding Computer to query accurately large blocks of text.
• the text to be recorded is converted to Concept Language and then stored in a block in whatever sequence it is produced by the translation process.
• Joe 112313 (number for the word 'Joe' in the first name Data Class.
• the leading number '1' codes for the first, 'Life' Data Category, and 11 codes for the first Data Class in that category, i.e., the First Name data Class. 3213 is the number assigned to the first name Joe. If 'Joe' were in this instance a
• the user wants one meaning, specifies it with words that have multiple meanings, and consequently and inevitably, receives back every item that has any of the multiple meanings of the words he uses.
• the benefit of the Any-to-Any machine's method is what the user says is translated into a string that contains only the meaning he wants, and this string is used to search text that is in a format where every meaning is represented by only one string. Consequently, the query string, with its single meaning, can be 100% matched with every occurrence of that exact string (with only one meaning) in the recorded text. Consequently, the search finds the meaning he wants, no matter the original words used to phrase it.
• a user's multiword query - a sentence for example - has only one meaning for him, but several meanings for the computer, and hence produces several results, not the one result he wants.
• the user's multi-word query with one meaning is transformed into a Concept Language text with only one meaning. That meaning is defined by the Co- Reducing Concept Method of the various Concept Symbols in the Concept Language query text.
• a Concept Language Query running against a Concept Language text is actually querying with symbols AB (that have a meaning XY for the user) to locate symbols AB (that represent the meaning of XY for the user).
• Free Form Concept language output is desirable to enable a computer is to answer questions on stored text, and also to be enable a computer to perform operations reliably based on stored multi-line, multi-page and multi-format texts.
• the order 'send this e-mail to everyone who contacted us saying they thought our new Model X is great' is an example of an execution that is based on the content of stored texts.
• Such text would need to be storied in Free Form Concept Language in order to be sure of correctly executing an order requiring a search of text for meanings, as opposed to a state of the art search for multi-meaning words.
• Image Concept Language is a key enablement for a robot to act on human instructions
• Any-to-Any machine can also be used to enable a computer to handle data other than words, for example, images such as photographs or maps.
• Any image can be described in words, and some software exists and other software can be written quite easily that automatically describes the components of any image in words.
• the words used can be translated automatically into Concept Language by associated software, and then if suitably recorded, for example in Data Class Output Format Method, the words become a reference to the image.
• Data Class Output Format includes provision for all five data Categories (Life, Time, Space, Energy and Matter) and a Data Relation Table relates these to one another for each object, or event. Consequently, Concept Language is the key element enabling a computer to manipulate images and movements based on a user's instruction. If these technologies are united, a command such as 'get me the milk from the refrigerator' becomes possible.
• the refrigerator' has a Concept Language equivalent. That Concept Language equivalent can be matched to an image and the coordinates of that image - the coordinates of the refrigerator - recorded in the 'Space' Data Category of a suitable Data Relation Table.
• the computer is provided with a means of localizing itself - such as a form of GPS, or reference coordinates within a building, then calculating the motor inputs required to make the two coordinates coincide - to get the computer to move to the refrigerator is relatively mundane programming. Identifying a door handle, or making movements to open a door, are simple extensions of the same principles. But none of this can be enabled usefully, in the absence of the ability enabled by Concept Language, to relate directly, a user's words with an image.
• a Concept Language can be related to images through the intermediate stage of words, or can be enabled to translated directly to a Numbers Concept Language. In this manner, Image X is Number Concept Language 5414, and 5514 can be output either as a word "refrigerator' or as an image.
• images can also be created, combined, transformed and otherwise manipulated using Normal Language words.
• a computer is then enabled to perform commands, such as the following,: 'Make me a photograph of a garden, with a swimming pool in it. Make the swimming pool wider, and make the water blue. Empty the swimming pool.'
• the Concept Language definition of a word - for example 'Table' - will be the Concept Language equivalent of a definition such as 'a table is a flat surface that etc'
• This definition can be expressed as a Data Relation Table record or records. If the definition is sufficiently precise, a computer provided with visual imaging equipment can continually run the physical specifications of perceived images against the Data Relation Table records that define objects, and, if enabled for speech, thereby describe what it sees using normal spoken language. Equally, it can localize itself in a building by comparing the identified objects, to Data Relation table records for the Location of such objects. Hence, it can move around, knowing all the time where it is, by reference partly to where it was, and partly to the objects now visible.
• a Concept Language that relates Concept Symbols to images following the teachings and methods of this Any-to-Any machine is termed an Image Concept Language.
• Audio Concept Language that relates Concept Symbols to sounds is termed an Audio Concept Language.
• Non-sense essentially defines as specifying something that can not be done, or data mismatches - for example when the user specifies one item but the logic finds several. Part of the enablement to check whether something 'makes sense' is built into a Concept language with its use of the Complete Statement Method, and the CanDoCan't method - the name for the method used to record what an object can and can not do.
• Step 1 Select a Suitable Vocabulary
• a vocabulary can be selected as described previously for simple applications, by reviewing what the application will have to do and selecting a vocabulary based on that. Even so a considerable number of General Use Words are required. Alternately, large numbers of texts on a subject can be taken, and software used to remove all duplicate words. The result constitutes a vocabulary for the subject concerned, and this method is useful for specialized vocabularies for specialized subjects. Further, software can be used to remove all words that already exist in another generalized vocabulary, leaving only the words needing to be added to make the specialized vocabulary.
• a useful method for selecting a General Use vocabulary is to begin with a large dictionary, preferably in electronic form, and place this in a database, where it can be manipulated.
• Selecting the vocabulary to use is then a mechanical process of going down the list of words one by one and marking those to be used. Words not included at this time can be added later.
• Step 2 Divide the vocabulary into Meaning Words and Operator Words If the vocabulary has been placed in a database Meaning Words can be found by asking a series of questions of each word: Data Category Life:
• This example also demonstrates the Any-to-Any machine's teaching that a language can be made usable by a computer if it viewed as compression.
• the reality is that when a person says 'I print the letter' there is a something in the sentence - other than the word
• 'print' itself - that is stating that 'print' is an action not a thing. That something is a detectable characteristic and any detectable characteristic can form the basis for a rule that software can use to determine which meaning is in use.
• Step 2 Divide the vocabulary into Meaning Words and Operator Words - Inter- relationships of Data Categories, Compression Coding of Space/Matter Data Categories
• a further source of confusion when attempting to assign words to Data Categories is provided by the inter-relationships of Data Categories.
• the physical universe consists of Matter, Energy, Space and Time, and together with this is the category of Life, and it is a curious phenomena that all words other than Operator Words will fit into one or more of these categories. As stated previously the behavior of those words that are to do with the physical universe mimics the behavior of the physical universe itself.
• a prime example of this phenomenon is that words with a meaning of Matter are often used as words with a meaning of the Space Category - Location. For example 'go to the house', 'go to the chair' 'move over to the wall.' Houses, chairs and walls are definitely matter. The physical space in which they exist is a location, just as an address is a location. The location of the house chair or wall can be fixed on a map. A chair exists and it can occupy an unlimited number of locations.
• 'chair' in the words: 'go to the chair' is 'go to the (location of) the chair' but the word 'chair' does not always mean 'location of the chair'. If a person says 'Put the chair in the garbage dump' he does not mean 'put the location of the chair in the garbage dump.' Locations are coordinates in space and are not movable. A given space is there no matter what names it may be given, no matter what that space contains, that space is there and remains there.
• Any word - and a name is just a special type of word - is treated by the Any-to-Any machine method as a compressed form of its definition and this is equally true of a location Name.
• a Location name - such as 'Klein & Pinch' or 'the house' - should be treated by a computer as a compressed form of the actual location coordinates
• 'banana' is a name - a compressed reference - for 'a long tropical fruit which....'
• the functional relationship that is evident in the way the human handles location data is expressed in the Concept Hierarchy for a word with a location meaning.
• Step 2 Divide the vocabulary into Meaning Words and Operator Words - Interrelationships of Data Categories, Interaction of Time/Energy Data Categories.
• the Any-to-Any machine has a number of teachings concerning the interaction of words with meanings concerning the Time and Energy Data Categories, as follows: 44) Time / Action Compression
• Actions Energies
• Words having a meaning expressing some kind of Action are time coded, but words for all other Data Categories are not time coded..
• the word 'walk' has a form 'walked'. From the viewpoint of Grammar, the addition of the ending '-ed' turns 'walk' into 'past tense'. Per the teaching of the Any-to-Any machine, there is no change to the meaning of 'walk' there is addition to the meaning of walk - another meaning is added.
• the '-ed' that is added is treated as a compression code (compression in that it is shorter than the text it replaced) that adds the meaning 'past time' to the prior meaning of 'walk'.
• '-ed' is a compression code replacement for 'past time' to give: Walk & past time
• the Location Data Category does not take time codes. There is no suffix or prefix that can be added to an address name or any part of an address that makes the word into address & past time. Similarly, words with meanings that label Matter objects do not take time codes. There is no prefix or suffix that can be added to a word for a Matter object to make it into thing & past time.
• the word 'book' can not take a form - bookque for example - that means 'book used to exist'. It is possible to say 'booked' - 'I was booked' but, again, 'book' in that meaning is an action and hence takes a time coding. But 'book' as thing can not take a time coding in the English Language.
• Time Data Category past time. & Action Data Category Concept Hierarchy - do & move & travel & walk.
• 'Stop' is considered by Grammar to be the present tense, whereas in fact it is often future.
• the meaning of 'stop' is future (immediate future) - the action of 'stop' can not begin until a time later than the time the order has finished being given.
• the version of 'stop' that is coded for the Time Data category value of 'Now' - is 'stopping' - the action of 'stop' is occurring now.
• '-ing' is a Time Compression Code, coding the word to which it is attached for Time now'.
• the absence of a time code in the word 'stop' is itself a Time Compression Code for 'time future' when the meaning of 'stop' is 'stop' as an order.
• Action word - word with a meaning that expresses an action - can be coded for twenty-seven different time Viewpoints.
• a list of these and examples of each is attached as Appendix **. In each case, however the time is coded, it is part of the Concept Statement of the word concerned.
• This teaching of the Any-to-Any machine is contrary to that of the state of the art, but is desirable for the proper functioning of computer control using Normal Language.
• Stop schedule action for earliest possible stop, unless further time schedule specification received, in which case, execute as per that schedule. If the software now receives 'Stop printing in 5 minutes', schedule stop time is set to 5 minutes. The action of the 'stop' software is not changed. If the user says ' Stop printing 5 minutes after I say so', the action of the 'stop' software module is not changed in any way.
• the scheduler Module sets the time to execute as 'l say so & 5 minutes.' Effectively, because the programmer understands from the outset that the word 'stop' applies to the future, the software arrangements to handle the exact conditions or time of the future stopping become relatively simple.
• Actions are related by Time. Certain phenomena of the behavior of language are matters that can only be taken care of by the software that uses the Concept Language. One of these is the relationship between words for things, acting as words for Locations, part of which should be taken care of by querying software.
• Time used to relate different Actions to one another is a further example and in this case, the phenomenon needs to be handled wholly in software. While the following teachings does not affect the creation of a Concept Language, the person creating or translating into such a language needs to understand the mechanism that software will apply to Concept Statements created in the Concept Language. A person creating or translating into a
• Time Value X the Time value for 'Joe Cancelled his order.
• the two actions are related by the common time of their occurrence.
• That condition can be any combination of anything in any data category from existing data or future data or any combination of both:
• Actions that are related by common times are themselves Actions of the time 'Existing' as an Action, and one of the 'existings' is itself a time.
• all Actions should have provision for recording the time at which they are to be done. This time should be able to set to the time of another action, and the existence of that other action should be able to be tested. (The Data REIation Table provides for this).
• any one execution should be able to be coupled with any data on which it ought to be able to act, in any combination that can be executed.
• state of the art software the example above would require executions to done by 1) Word processing software 4) Contact software for fax number, 2) Fax software 3) e-mail software 4) Spreadsheet software and so on.
• the software to orchestrate just the combination and sequences of software actions in the above example would be complex, let alone orchestrating other possible combinations of executions and specifications of items on which to perform executions.
• state of the art software resulting from state of the art software writing philosophy, is too inflexible to accommodate flexibility human requirements. Unless it is improved the enablements of this Any-to-Any machine will enable a computer to understand every order, and perform none of them. .
• the Data REIation Table extends Concept Language expands the Command definition of each action word for which a software module exists to execute that action. This expansion of the definition is partly in the form of an additional Data Relation Table record that states the required condition for a module to operate.
• Step 2 Divide the vocabulary into Meaning Words and Operator Words - Base Concepts A useful method of doing this is to be begin by isolating and marking those words that take a variety of forms while still retaining something of the same meaning. Such words are called 'Base Concept Words' because they all have a Base Concept defined as follows: 48) Enabling a Computer to Respond to Queries in a Human Manner. The Base Concept Method In the English language, nearly every single word can take a large number of forms.
• Jack has an invitational attitude to Jill 4. Jack looked at Jill invitationally
• Jack said 'Jill's un-invitableness is such that..
• Jack sent a deinvitational letter to Jill 19- Jack, re-invite Jill
• a 'Base Concept' is defined as: That part of the meaning of a word (which takes multiple forms) that is common to all of the forms.'
• Base Concepts have only one meaning, and do not have any relationship of any kind with Grammar, or any classification of words in grammar and are not verbs, adjectives or any other part of speech.
• the Concept Symbol of a Base Concept is wholly and only a unique symbol for 'that part of the meaning of a word (which takes multiple forms) that is common to all of the forms.' In the case of 'Base Concept Concept Symbol 'invite' this meaning could be defined as 'ask & courteous' on the Co-Reducing Concept Method (see later description for the Any-to-Any machine's method for defining Concept Symbols).
• a useful method to enable Base Concepts to be manipulated is as follows: 1) Each word in the vocabulary is reviewed to find those words that take multiple forms, while still retaining a Base Concept.
• Each Base Concept is assigned a Concept Symbol.
• the Concept Symbol assigned to the Base Concept of all the above forms of invite is 'invite'.
• the Base Concept Concept Symbol 'invite' is simply a convenient way of enabling the Base
• a 'Complete Statement' is defined firstly as 'a statement
• Punctuation can not be used as a detection tool for a human's consideration of completeness of a statement, as punctuation more or less does not exist in the spoken word. For example, some words can be written and appear as: 'He said, "I will go to the house tomorrow.” But when these words are spoken in a complete monotone with equal pauses between words: 'he.. said..i.. will..go.. to..the..house.. tomorrow' they are still completely understandable. In this example, punctuation is not an element that defines whether the statement is complete or not.
• Pauses between spoken words also do not indicate whether a person considers a statement complete. When words are written, they may appear as "I am angry. Jill, is difficult. I shall fire her". When these words are spoken, they can be spoken in a monotone with equal length pauses between words, and still be correctly understood: 'I.. am..angry..jill.. is.. difficult.. i. shall..fire..her'. Pauses (represented by the symbol 'J ') can even be placed in the most unlikely places and the sense is still retained: 'I..am ⁇ angry..jill. ⁇ is.. difficult... i ⁇ shalLfire ⁇ her'.
• a problem does not occur if a statement is a Complete Statement and is detected to be complete from the words used themselves. However, a user may issue a statement that is not complete, and indicate that it is complete when it is not. Part of the computer definition of a 'Complete Statement' was that it is a statement that the humans 'considers to be complete.' A Human may say, 'I am angry Jill is. that's all' The words 'that's all.' state that the user is finished, and therefore - it can be assumed he considers that what he has said is complete. However, the statement is an Incomplete Statement, and the fact that is not complete should be able to be detected by software. The words 'the blue house' is not a normally a Complete Statement.
• software In order for a correction to be made, such as prompting the user to complete the missing data date or resolve the conflict, software needs a method to detect the nature of the omitted data or the nature of the data conflict.
• the software can detect that the complete statement received is in fact executable a statement.
• a Command can be a Complete Statement such as "print spreadsheet X' can not be executed until 'spreadsheet X' is identified for the software module that is to the printing. Thus, requirements for execution are in addition to any requirements for a user's statement to be considered complete.
• the software can detect why it is not executable.
• human behavior when encountering an order that can not be executed (in the cooperative spirit that a person would expect from his computer) is normally to tell the person why it can not be done.
• An understanding computer should therefore also be able to detect why an order can not be executed, so that either the computer itself, or the human, can take corrective action. Note that the computer can not take any corrective action until it can detect the exact nature of the error - and that involves detecting when a statement is not executable.
• a computer given an order to send a fax to someone for which it has no fax number, can check the conditions required for sending a fax. It can find that one of the recorded conditions is the existence of a fax number, together with the information that fax numbers are found in Location X, and the right one is chosen with procedure Y. Executing this and finding no fax number, the error handling procedure incorporated in the Execution Module can launch a user prompt or other procedure to obtain the missing fax number.
• Condition Rules have the added benefit of providing the basis - (2) above - for comparison with a statement of an Executable Statement (1) to detect if a Complete Statement is an Executable Statement (3).
• Base Concepts and other Meaning Words have Concept Condition Rules Taking the Base Concept [invite] as an example, it is clear that a Bare Meaning has certain requirements that need to be met in order for the word to be intelligible. These requirements can be found by the Any-to-Any machine method of testing the word in various uses and viewing the results in the light of the Any-to-Any machine's teachings. Once found, these requirements can then be expressed as rules, as in the following example concerning the Base Concept [invite].
• the Concept Condition Rule Method creates computer - executable statements that software can test to see if are satisfied or not. Using Concept Condition Rules, enables software to test and find whether the input is a Complete Statement or an Incomplete Statement and if incomplete, why it is incomplete. This ability on based on the Any-to-Any machine's further definition and final definitive definition of a Complete Statement, as follows: A statement is a Complete Statement when the words in a statement satisfy all the Concept Condition Rules of all the words in the statement. A statement is an Incomplete Statement, when the words in a statement do not satisfy all the Concept Condition Rules of all the words in the statement. This can be illustrated as follows. Several words in a statement can have Concept
• One word - termed for this example ' a type 1 word' - can have a rule that "a type 4 word is required'.
• the type 4 word can have a rule 'a type 1 word is required'. If the statement contains a type 1 word and a type 4 word, both Concept Condition Rules of both words will be satisfied and the statement will be a Complete Statement. If the user enters only a type 1 word, or only a type 4 word, that word's Concept Condition Rule is not satisfied, and the statement is an Incomplete Statement. The reason that the statement is an Incomplete Statement is apparent in the unsatisfied Concept Condition Rule (and hence can be used to generate an appropriate prompt or corrective action).
• the lines headed at the left 'Jack' and 'Jill' are supposed to be entries in a database.
• the database is supposed to contain two sets of Data Categories as mirror images of one another - one for the 'Cause Side' and one for the Effect Side', and these Data Categories are represented by database fields. These database fields have been named in the table for the purposes of this illustration with the Data Category names (but may not necessarily be so named in an actual application.
• the word in the first column - 'Jack', 'Jill' - shows the word in question, and the remaining columns represent the database fields, and show where the word would be entered in the Data Base.
• a record in which data is recorded - such as the words 'Jack' or Jill' - is termed a 'Data Record'.
• the words 'Jack' and 'Jill' are shown as occupying two lines and hence two records, but this is done only for clarity - there is no reason both words can not be entered in the correct fields in a single record.
• the first line, containing the word 'Jack' shows that the word 'Jack' falls into the Life Data Category on the Cause Side.
• the last line, containing the word 'Jill' shows that the word also falls into the Data Category of Life but on the Effect Side. Meaning Rules take care of detecting the case or Effect assignment to the words 'Jack', 'Jill'
• the middle row - containing the Base Concept [invite] in the left-most column represents a type of database record termed a 'Concept Condition Record' that is recorded in the same or another database that is similarly organized to the one containing the words 'Jack' and 'Jill'.
• the Concept Condition Rule for [invite] is expressed in the Concept Condition Record in terms of the Data Category fields that are required or not.
• the words 'Required Alternative' in each field of the Cause Side represent a suitable database expression with the meaning that any value of entry in at least one of these fields on the Cause Side are required.
• the words 'Required Alternative (Able to Move)' and 'Required Alternative' shown in fields on the Effect Side of the same line represent the fact that the same Concept Condition Rule also requires either an entry in the Matter Data Category or the Life Data Category.
• the words 'Able to move) further represent a database expression signifying that if there is an entry in this field, that entry value should have associated with it a Concept Symbol signifying that the object it represents has the capacity to move.
• Condition Record is satisfied by the presence of the word 'Jack' in the Life Category of the Cause side of the Data Record and by the word 'Jill' in the Effect side of the Data Record. But supposing that the statement entered was 'Jack invites', and nothing more, the requirement of the Condition Record on the Effect Side would not be met.
• a value would be returned that would enable a prompt to be created such as: 'Requires the name of a person or an object that is able to move'. More colloquially this prompt could be expressed as 'Who or what did he invite?'
• this method of the Any-to-Any machine provides the basis to enable a computer to determine whether entered data 'makes sense' and if not, why it does not 'make sense'. Less colloquially, the method enables software to determine whether entered data is a Complete Statement or not, and if not, why the Statement is incomplete, thereby fulfilling Understanding Computer Requirements (1) and (2) previously stated.
• a Data Class value 'Able to Move' as used in the Concept Condition Record described above, is implemented on the following broad outlines, using 'boat' as an example - a boat being a thing capable of movement:
• the Effect Side Matter data Category Condition Record contains one number - for example the number '2' that query logic interprets as 'A value in this field is one of the alternatives that is required'. Additionally the same field contains the number '4451' which query logic interprets as 'If there is any value in this field, query its Concept Statement to determine if it contains '4451 '. If it does contain 4451 , return 'True' else return 'False'.'
• the Data Relation Table then records the Concept Symbol for the Base Concept in a separate field termed a 'Base Concept Field' in the same record as the rest of the data.
• the Data Relation Table logic includes this field in queries conducted to answer user queries. In this manner - referring to the above example - a search for what did Joe 'do?' will find both [send] and [invite], and as usual, return the lowest (most detailed) value i.e. 'invite' Joe. Since the record will include a record of the Time and that Time will be earlier than now, the time is past time, and hence the logic adds the past time code of '-ed' and returns 'invited Joe.'
• Such a computer intrinsically requires senior, controlling software, that controls the computer as a whole, including controlling other software that actually performs the executions ordered by the user
• a Concept Language should be constructed bearing in mind not only the words in its vocabulary, but bearing in mind, and providing for the words that will inevitably be added by the user. Most applications will result in the user adding word to the Concept Language vocabulary - words for names of things and actions, the words for names of people and the words and numbers for addresses, telephone numbers etc.
• the Data Category of Space can be confusing, and the general tendency in the state of the art is either to ignore it, or to include into it things that do not belong in it. For example most computers have some provision to record the Life Category - people's names for example. Computers usually record Time in a limited manner - for example, the Time a file is last saved. Icons and Menus are, in a manner, recordings of the Energy Data Category - actions. Space however, it only really seen in a computer in terms of Disk Partitions, and otherwise, is more or less ignored.
• Coordinates can be used to record spaces and shapes - Names of spaces - for example, "New York' is name for a space as well as a name for a particular collection of material things.
• a Space is defined by four or more coordinate sets where at least one coordinate is not the same in all coordinate sets.
• a Space intrinsically contains an infinity of areas.
• An Area is defined by three or more sets of coordinates where one of the coordinates in the coordinate sets is the same for all the coordinate sets.
• An Area intrinsically contains an infinity of lines
• a Line is defined by two or more sets of coordinates (each which consists of three coordinates) where two of the coordinates are the same for all coordinate sets.
• a Curve is a special type of lines.
• a Curve is defined by more that two sets of coordinates where one of the coordinates are the same for all coordinate sets and another changes by a constant value in relation to its distance from the set of coordinates at either end of the curve. Any type of line intrinsically contains an infinity of points.
• a Point is defined by three coordinates.
• a Coordinate Pattern is defined as any number of sets of coordinates that are each separated from one another by distances, where those distances bear a fixed proportion to one another.
• the space occupied by any Matter can be defined in terms of a Coordinate Pattern.
• An Object When an object is defined in terms of the Space it occupies, it is defined as a Coordinate Pattern whose orientation with respect to gravity falls within specified limits.
• the direction of Gravity is a fundamental orienting factory in all verbal expressions of movement.
• An 'address' as referred to in everyday conversation is in reality an assembly of completely dissimilar data, which is often referred to as a block, and, in the state of the art, is usually treated by software as a single data type when it is not.
• most computers in the state of the art treating 'addresses' as a data type, give the data type a matching software type.
• This software type - contact software - deals with addresses only and will not process other data such as texts for letters or accounts data - both of which need addresses also.
• the least of the negative results of this error is that software with complex and difficult to use mechanisms is required to move address data where it is needed.
• the following is an example of an address Mr. Joe Blow, Ph.D. Director of Thought, Marketing Department
• Joe Blow Name of a person and while he may be addresses this way at his work address he may be addressed differently where he may prefer to be called 'Joey' or some nickname
• Joe is Director of Thought - but only at this location. He may have a number of other titles also. Chairman of the Lyons Club, President of the Gold Club and potentially, dozens of others. Marketing Department A Group Name
• the Bronx A Location Name New York City A Location Name New York State A Location Name USA A Location Name 291118 This is also set of coordinates and is effectively a number that is a name for an area. It is extremely desirable that in creating a Concept Language, the types of data and the kinds of word that, when used together, are labeled 'an address' are correctly assigned to correct Data Categories and handled accordingly to the requirements of each Data Category. If they are not, it becomes virtually difficult to create an Understanding Computer. The reason for this is as follows:
• a computer within the limits of the capacities of its hardware, should never limit a user in a manner that he does not limit himself.
• 'addresses For example a single person may have many locations at which he is from time to time - one or more work places, one or more homes, places where he does sports, and so on. Each of these places has its own coordinates - its own street address.
• this single person is related to many documents in his computer - either by the fact that he created them, or by the face that he received them.
• a human As far as a human is concerned, he is related to both his documents and his locations, but he is neither of these things. He is not a document and he is not a location.
• the only representation of that person in the computer is his address record - if he even has an address record for himself, which is not certain.
• the address record creates a fixed relationship between the representation of the person in the computer - his name - and one location.
• software in the state of the art offers up to three possible addresses: 'Home' 'Business' and 'Other.' If an attempt is made to create a Computer that Understands with software such as this, which violates the Unlimited Principle, the attempt will fail, as follows.
• Language is itself can be described as any-to-any data transmission system. Any word can be related to any other word within the limits of functionality and agreements (grammar). For example the following words can be used (related) together, and might be in a science function story: The invisible thinking car' The singing non-existent house'.
• the Co-reducing Concept Method is one application of the Any-to-Any Principle.
• a person can relate Any greeting to Any name. He can relate Any name to Any

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• Human Computer Interaction (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Stored Programmes (AREA)
• Processing Or Creating Images (AREA)
• User Interface Of Digital Computer (AREA)
• Digital Computer Display Output (AREA)
• Devices For Executing Special Programs (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=22596510

Family Applications (2)

Family Applications Before (1)

Country Status (9)

Families Citing this family (35)

Family Cites Families (4)

• 2000
  • 2000-11-13 JP JP2001536684A patent/JP2003514300A/ja active Pending
  • 2000-11-13 WO PCT/US2000/031351 patent/WO2001035217A2/en not_active Application Discontinuation
  • 2000-11-13 CA CA002360067A patent/CA2360067A1/en not_active Abandoned
  • 2000-11-13 CA CA002359997A patent/CA2359997A1/en not_active Abandoned
  • 2000-11-13 RU RU2001122576/09A patent/RU2001122576A/ru not_active Application Discontinuation
  • 2000-11-13 JP JP2001536685A patent/JP2003529818A/ja active Pending
  • 2000-11-13 AU AU16062/01A patent/AU1606201A/en not_active Abandoned
  • 2000-11-13 RU RU2001122574/09A patent/RU2001122574A/ru not_active Application Discontinuation
  • 2000-11-13 WO PCT/US2000/031231 patent/WO2001035216A2/en not_active Application Discontinuation
  • 2000-11-13 AU AU16113/01A patent/AU1611301A/en not_active Abandoned
  • 2000-11-13 EP EP00978675A patent/EP1259880A2/en not_active Withdrawn
  • 2000-11-13 NZ NZ512939A patent/NZ512939A/en unknown
  • 2000-11-13 EP EP00978614A patent/EP1247174A2/en not_active Withdrawn
  • 2000-11-13 IL IL14431900A patent/IL144319A0/xx unknown
  • 2000-11-13 IL IL14431400A patent/IL144314A0/xx unknown
• 2001
  • 2001-08-08 ZA ZA200106526A patent/ZA200106526B/en unknown

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events