PATENT ABSTRACT
A method, system, and apparatus for identifying, describing, integrating, and discovering information events with the unique feature of applicability to and extensibility across event states irrespective of function and or embodiment in one system with one approach, one infrastructure, one architecture, one method, and one principled basis, comprising: a self-mint method for self-service identity; an information architecture; a method to organize everything; a scalable business process for integrating data from different tables and/or from different systems into one combined system; a programming process and language, operating system architecture, and modeling medium; and a search engine and directory to make it all accessible; altogether comprising an infrastructure for a network system.

PATENT DESCRIPTION
This is a Continuation of application Ser. No. 10/231,085 filed Aug. 29, 2002; Examiner Alford Kindred; A/U 2163. 
   CROSS-REFERENCE TO RELATED APPLICATIONS 
   This application is entitled to the benefit of Provisional Patent Application Ser. No. 60/315,923, filed 31 AUGUST 2001. 

   STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT 
   Not Applicable. 
   INCORPORATION-BY-REFERENCE OF MATERIALS SUBMITTED ON A COMPACT DISC 
   Prototype requested by Examiner submitted on electronic media (USB thumb drive) on Oct. 27, 2006. 
   BACKGROUND OF THE INVENTION 
   Field of Invention
         Table of Contents   Field   Scope and Definition of Everything   Validation Context   Official Context   Structural Context   Information Infrastructure Context   Telecommunications Infrastructure   Network Context   Communications Infrastructure Context   Technical Context   Application Context   Privacy Context   Principles Applied Practically   Greater Utility   Alignment With Analog Original   Integrated End-To-End Solution       

   FIELD 
   The broad field of invention is event identity, where everything is defined as an event. The general field is identity as applied in the context of symbolic representation of resources in a global network of information and communication systems. The more specific field is identity as a control element in lists, tables, and relational database systems, and as essential network information infrastructure. The present invention is a Model of Everything according to  FIG. 1 . 
   The current reference architecture imposes structural constraints that both preclude accurate depiction of our global civilization in all its complex and interrelated assertions of identity and property ownership, and undermine foundational tenets of democracy by limiting individual access and participation in the electronic economy. At best, work-arounds are expensive and marginally effective. At worst, they compromise personal freedom to self-represent. 
   The essential ingredient for survival in the electronic economy is identity. The problem is, you don&#39;t own yours. You can&#39;t. The architecture that defines your access says so. 
   Unitary Technology stipulates one information infrastructure that corrects fundamental errors in construction and brings the existing IT architecture into correspondence with its analog ideal. Unitary Reference Architecture redefines electronic participation with self-service single sign-on identity, enabling direct access by all users for all uses. 
   Scope and Definition of Everything 
   What&#39;s in everything? What are the main parts of reality? Mathematicians, biologists, cosmologists, philosophers, theologians, and everyday persons have been asking and answering these questions as long as we&#39;ve been communicating. The answers are as diverse as the populations served by explanation. 
   Everything is at once very specific and very general. Information granularity, where the range could be anywhere from atoms to planets, is integral to definition. In the extreme abstract, the word everything is all in one, and a singularity, all of one. A table with one listing named “Everything” is a List of |EVERYTHING|. So is a table listing every molecular constituent of every cell of every person, place, and thing on the planet.
         Everything 2      1 a: all that exists; 1 b: all that relates to the subject   2: all that is important   3: all sorts of other things—used to indicate related but unspecified events, facts, or conditions   All 2      1 a: the whole amount or quantity of; 1 b: as much as possible   2: every member or individual component of   3: the whole number or sum of   4: every   Reality 7      1: the quality or state of being real   2a (1): a real event, entity, or state of affairs
           (2): the totality of real things and   
           2b something that is neither derivative nor dependent but exists necessarily—in reality: in actual fact       

   Reality is everything real. Real is what&#39;s known and agreed to. The public domain represents the record of what&#39;s known and agreed to. Assertions are claims made by people about themselves and their property. “Facts” are claims authenticated by credible witness. Ideas, discoveries, theories, principles, and other non-objective things in |EVERYTHING|, as well as real and personal property, are circumscribed by agreements about ownership in the form of authenticated claims by authenticated maker-owners. Individuals and businesses voluntarily record claims of ownership because that&#39;s the information they want people to know. 
   Thus, the terms reality, everything real, and |EVERYTHING|, for the purposes of a Model of Everything, are defined as the sum total of all the agreements we have about it. The scope of a Model of Everything is bounded by the evolving analog agreements that comprise our social, economic, and political compacts captured in proceedings, publications, libraries, journals, files, folders, computers, and media, all over the world. 
   UR-URL Combination Identity-Identifier-Addressing-Indexing Method, identified by the name Unitary Reference Architecture and the acronym identifier URA, and sometimes, just plain Unitary Architecture, is a form of Universal Resource Identifier (URI) of particular identification code nomenclature and syntax. “Reference architecture” is the term that names the function URA performs in its capacity as the cohering basis of one referential system of unique event addresses. Unitary declares the present claim to novelty, as unique from all predecessors, which are not. 
   The unitary analog “whole system” is comprised of authenticated claims about property ownership by legal entities with identity, captured as records of transactions with unique identifier codes in tables and files all over the world. This is the historical record of everything real. This is the scope of the present invention, which usefully identifies, differentiates, and correlates identity for all events, including all property “objects” and all ownership “assertions,” with one common reference architecture. Other methods are limited to identifying many events. 
   Unitary Reference Architecture is at the same time a combination identity-identifier-addressing-indexing method and a new IT architecture for the current generation of information networks. Additionally, it is a next generation unitary programming syntax method and means for Model Driven Architecture, which is itself the next generation of Object Oriented Programming. Plus, it is a future generation representational medium for depicting, manipulating, directing, sequencing, synthesizing and controlling information events in digital environments. 
   It will be made apparent that the present invention meets widespread demand for a comprehensive solution to long-standing problems considered unsolvable by experts who have tried and failed. It also reveals and remedies an unrecognized defect, and provides both the desired end and unexpected collateral benefits across the whole domain of information systems and application subsystems that use and depend on identity for essential operations. 
   Validation Context 
   Government is in business to standardize and manage whole-population-scale social interactions that create and maintain civil society. States issue fictitious names; local property offices authenticate and legally validate real estate transactions. Authentication is the step of matching evidences. Validation means, “to agree, too,” and they show concurrence by adding new records of transactions to the lists of records they already have in their files and databases. They issue an identification number that links your artifact and their file. This is its identifier. 
   Official analog systems have both hard copies of artifacts and master lists, as well as computer database tables of the important information in some standard order that matches the paper form filled out. The identifier in the table matches the number in the paper file system. They reference each other. The identifier is reference architecture. The act of issuing an identification code is called “minting” and firms that issue identifiers are commonly called “mints.” 
   The minting agency is also responsible for maintaining security of the data. These are public records. Security generally means making sure they don&#39;t get lost or corrupted, in this case. Permanence is the main objective, so precautions are taken to protect both the files and the computer records. Keeping the information secret is not an issue and these offices make money selling information to anyone who wants copies. That&#39;s what public information is intended to be for. Other agencies have information that is not public, like the IRS. They have rules for what they can share and what they cannot. 
   In the real world, privacy is a design criterion that shapes political means for collective individual purpose. In the web world, privacy is a product feature defined by permissions and authorities that serve the mint. 
   Official Context 
   Governments are not the only source of official identity. We have an analog vendor system of authentication that runs in parallel and is governed by the same rules. Notary Publics are vendors. Hospital vendors witness and authenticate births and validate certificates. Title company vendors validate real property transfers after authenticating identity of the property, as well as buyer and seller. Contracts and sales receipts are examples of analog evidence that validate the terms of transactions between people. But until makers agree to publish jointly owned contractual details, information is private. 
   The common threat to privacy posed by vendor authentication and maintenance of transaction records is the loophole that lets vendor mints publish, or make known to others, details of transaction record information without the consent of the other maker. The causal vulnerability is transaction records of records on the Internet only have one maker—the mint. The mint is the maker, and minting is like breathing life into the transaction, which becomes a virtual object with identity and descriptive properties, chiefly, the person and their personal information about the goods and services purchased. 
   This is a key point. The virtual system is not a system of ownership; it&#39;s a system of transaction records. What&#39;s distributed is not information about makers; it&#39;s information about transactions, which is the thing the mint owns. 
   This results from the original definitions and specifications in the information architecture of the whole system, and dates back to the computer&#39;s evolution from calculating machine to desktop sensation with the first widely used spreadsheet programs. Financial purposes, which represent operations as event transactions, are the basis of information architecture: the unitary term is a transaction that has a unique identifier as a property that differentiates it from all the other transactions. Everything is a transaction with properties. 
   Structural Context 
   What&#39;s information architecture?
         “At its most basic, information architecture is the construction of a structure or the organization of information. In a library, for example, information architecture is a combination of the catalog system and the physical design of the building that holds the books. On the Web, information architecture is a combination of organizing a site&#39;s content into categories and creating an interface to support those categories.” 3          

   Here&#39;s another definition from experts Lou Rosenfeld and Peter Morville from Argus Associates:
         “Information architecture involves the design of organization, labeling, navigation, and searching systems to help people find and manage information more successfully.” 4          

   Information architecture is another term for identity addressing and indexing method. 
   According to Webster, a system is “a regularly interacting or interdependent group of items forming a unified whole.” 5  In practice, “The System” is the set of regularly interacting and interdependent federal, state, regional and local agreements we call our civil society. It&#39;s formalized as rules—laws, contracts, ordinances, covenants, norms, agreements, principles, values—the definitions about how we interact as economic beings. 
   The rules we share are the reference architecture of society. These agreements are captured in various analog media as files, records, microfiche, documents, books, text, graphics, and various lists and tables. 
   Information Infrastructure Context 
   What&#39;s a global network of information systems? The phrase is often used casually to refer to something so big that we don&#39;t stop to think about what it is. It&#39;s the evolving and expanding virtualized embodiment of our analog distributed system of records of agreements, electronically captured as computerized records of real transaction artifacts. The electronic version is called the Internet, the World Wide Web, or just the Web, and E-Commerce, as well as global network of information systems, and a few more variations. 
   Telecommunications Infrastructure 
   
       
       
         
           A related system is the global network of telecommunication systems. It&#39;s comprised of: 
           1. The sum total of all the communication devices (phones, faxes, computers, personal digital assistants [PDA&#39;s], radios, television, and so forth); 
           2. The sum total of all the various copper wires, optical cable, satellites, microwave, bandwidth, and other media; 
           3. The sum total of all the statements of information reference architecture agreements that control the parameters for how devices and media exchange information. 
         
       
     
  
   Together, they comprise the global network of info-telecommunication systems. This virtual network itself is now synonymous with the all-encompassing terms “the net,” “global infrastructure,” and “global system.” 
   Network Context 
   The network is not dependent on device or medium of transmission. At the top of the tree, the whole system level, it depends on and revolves around rules about data formats and instruction sequences. The reference architecture of the world&#39;s info-telecom system is phone numbers and Internet addresses. A phone number is a telecommunication address that refers to person or business entity. An Internet address, for a website or email, is a digital address that likewise refers to a person or business entity. 
   Network information architecture is not a thing; it is a set of rules about the structure of a network system, which is also not a thing, but a set of agreements about regularly interacting or interdependent items in a whole. In the case of communication, the agreements are about sequences of symbols (numbers) and instructions. 
   The whole point of having a system in the first place is to find others and their property, intellectual and otherwise. The system constant is entity ownership, not device and not medium. When new devices are introduced, they conform to the international standards, not vice versa. 
   Information architecture sets the basic terms of a whole system. The unitary element that coheres the analog original real global network of information systems is event ownership identity as symbolized by numbers that correlate two event objects—people and/or their artifacts. The unitary element that coheres its digital counterpart, the electronic network, is transaction identity. This is a vital point of disparity between current embodiment prior arts and the present invention. 
   Communications Infrastructure Context 
   The global telephony network system is based on the agreement we&#39;ll all use country and area codes and prefixes and extensions. The Internet system is based on using said global agreements, plus the further agreement we&#39;ll use domain names and IP addresses and certain kinds of negotiation sequences and routing instructions to establish connections, accomplished with a hierarchical arrangement of registries and service providers. It&#39;s all spelled out in International Assigned Numbers Authority (IANA) documents. 6    
   “The Transmission Control Protocol/Internet Protocol (TCP/IP) suite, originally developed by the United States Department of Defense, is the set of logical connections used by the Internet, the worldwide consortium of computer networks. TCP/IP, based on peer-to-peer application software, creates a connection between any two computers using standard telephone access rules.” 7    
   These are the numbers and names in the master system that correspond to the reference architecture stipulated as unique number strings called Internet Protocol addresses. IP addresses are written as four sets of numbers separated by periods; for example, 204.171.64.2. This identifier is used to locate (discover) a resource. The infrastructure of the global network of information systems is not the artifacts, not the content—not the resources. It&#39;s the rules about how to discover resources and access content. Information on the Internet is the product of the businesses that own it, not a function of the overall network system. Web pages are the destination. The infrastructure is the set of conventions that govern interaction utility and operation—the agreements that define the network relationships and how information is exchanged—the highway. 
   Technical Context 
   List and database size is limited by the quantity of available variables within the ID numbering system&#39;s nomenclature. What makes a bunch of data “a system” is that it has at least one thing in common and at least one thing that&#39;s different. One way you keep track is by numbering the things, which meets the condition for difference. There can&#39;t be two with the same ID number. If you have one list with a number method, say one through ten, and another list with an alpha method, ordered A to Z, and combine them, it&#39;s OK as long as all the identifiers are unique. It&#39;s still a system, if the two lists have something else in common, maybe the purpose or owner or anything. Having a field for unique identifiers in the first place can be the thing the two systems have in common. The only mandatory field in a table is the identifier. 
   The unique identifier is usually the first column in a relational table or spreadsheet. Off the shelf programs like Excel and Lotus 1-2-3 have reference architecture that stipulates numbered rows and alpha columns with unique identifiers for each cell made up of the reference coordinates as a code: A1, B2 . . . conveniently built into the page for at-a-glance orientation. Having addresses for all the cells means you can do things with individual data, as well as with groups, or columns and rows of data. This kind of organization is the foundation of information science because pretty much all of the information in the world is part of some kind of list or table in some kind of file. 
   The easiest way to combine information in two old different systems is to make a new bigger file with both. This is called merging and the technical term is data integration. Regardless of whether your purpose is to upgrade old internal systems or to communicate with new external systems, if you want to integrate data, you have to design a new identifier code that will ensure all the individual items in all the tables have unique identity in one combined system. Common fields, like name and address, are rarely unique. 
   Interoperability is facilitated by common identity nomenclature. If you agree up front about the architecture, you don&#39;t have costly conversion projects every time you add another partner. Identity is particularly important to the businesses at the end of the supply chain that interfaces directly with end customers because consumers are not things. In the new web services business model, identity is applied to both things and people. It&#39;s easy to visualize companies trading information about orders, but when the information is about people, it&#39;s a different story. 
   Application Context 
   Identity management refers to the practice of designing codes and access rules, assigning identifiers, and maintaining a master control system to ensure uniqueness across the entire system, which establishes a platform for integration. The bigger the system or combination of systems, the greater quantity of identifiers is needed. In addition to aligning formats for supply-chain integration, companies are also organizing their intellectual property assets into accessible compendiums called knowledge bases. Plus, vast quantities of market transactions are created every day that have to be maintained for years for legal purposes. All these transaction records feed a huge cottage industry that archives them. All of the transactions and all of the entities require identifiers. 
   Privacy Context 
   Where the customer is business and the things identified are tangible personal property, there are few design constraints for the numbering method. But where the customer is an individual, what&#39;s identified is intangible real property—identity is “real” but it isn&#39;t a “thing.” It&#39;s an assertion or claim of ownership. We have special requirements for authenticating whether or not a person is who they say they are. In commercial contexts, this is a critical component of a valid contract. Citizens have artifacts they produce to verify or corroborate claims, like original property deeds, marriage licenses and stock certificates. These are maintained and shared by people themselves when they need to validate their own identity or the identity of their property. We have strict definitions about what&#39;s original and what&#39;s a copy. There are procedures for knowing the difference. A certified or notarized official transcript copy has more authority than a simple declaration on a napkin. Witnesses add another layer of validation. 
   The bottom line is in the analog world, individuals have access to both the means and the methods for self-representation as independent individual citizens. The mechanics of identity administration are well known; rights and obligations are precisely stipulated with rules everyone can follow. Authentication and permissions are self-published by affirmation and verified by simple user-initiated procedures with owner-driven tools. 
   In the digital world, an individual cannot self-represent on the Internet without paying a vendor for the privilege of agreeing with him who he is. Because the vendor has no way of knowing for a fact, they have to figure out ways to simulate official imprimatur. The method used is to make vendor mints caretakers of private information. In the new digital embodiment, vendors represent individuals. Vendors protect individual privacy. Vendors are responsible for authentication and vendors own the resultant identifiers. This is convenient for the vendors, but to the user, it&#39;s a layer of manipulation control between private ownership and property. It is necessary because it&#39;s designed into the virtual system that way.  FIGS. 54-61  illustrate these process elements. 
   Principles Applied Practically 
   Unitary Technology resolves duality by a shift in premise. The essential common unit of commerce is not the transaction but the identity. Transaction is a state of event. Event identity is the unitary term. On a systemic level, this new view of an old principle correctly reframes transaction event identity—as well as the record and artifacts that represent it—as respectively real and personal property of the maker. This is a subtle but important distinction between a system of records of claims about individuals, to a system of records of claims made by individuals about themselves. The maker is not a descriptive element owned by a transaction with identity. Individuals with identity make transactions. This is true in real life, but not in it&#39;s virtualization. 
   Greater Utility 
   Unitary Reference Architecture may be minted by multiple mints independently of one another, and requires no central authority. It applies to entities, as well as property; objects as well as assertions about objects. It&#39;s infinitely scalable, infinitely extensible, universal, persistent, primitive, and reductive to useful field length. It puts ownership and control of identity, and its representation, where it belongs—with makers. Person entity makers. Business entity makers. 
   Alignment with Analog Original 
   In the real world, private information is owned by private entities. The System is of and about individual ownership. Having a maker or owner is the source of identity. The record of civilization is charted in official claims of origination. We have institutionalized mechanisms for establishing authenticity, one of the purposes government serves. This critical step is missing in current electronic models that apply entity status and standing to define virtual transaction artifacts that own people as data. 
   Instatement is the process of formalizing makers&#39; claims—what makes a thing an “entity” in organized societies, and what makes a business a legal “person” with standing for ownership. Ownership is central to Western socio-political and economic democracies. In the real world, only “real” person entities can own things; artifacts cannot. In the real world, we have a one citizen one vote one identity rule, but not on the Internet where anonymity is the root of all spam. The processes and rules used to instate entities in the virtual economy need to match real world laws and legal practices. The digital embodiment of our analog “system” needs to match the original analog version it duplicates. The Internet does not. It is a system of intermediary ownership. Unitary Reference Architecture corrects this fundamental misconstruction by providing method and means for direct participation and private ownership of digital identity and identifiers. 
   Integrated End-to-End Solution 
   Unitary Technology delivers an end-to-end architecture for identifying, owning, naming, differentiating, representing, describing, depicting, illustrating, modeling, simulating, synthesizing, replicating, relating, connecting, associating, combining, merging, integrating, unifying, organizing, classifying, indexing, locating, addressing, positioning, routing, maintaining, storing, retrieving, finding, sharing, improving, sequencing, instructing, operating, manipulating, and controlling information events with one approach, one infrastructure, one architecture, one method, and one principled basis—a singular solution. 
   DESCRIPTION OF RELATED ART 
   Table of Contents
         Prior Art Overview   State-Of-The-Art Technology   Federated Identity   Digital Earth   Current Context   Replication Error In Premise   Replication Error in Purpose   Universal Resource Identifiers   Critical Distinction   Competitive Context   Vendor War Drives Implementation   Systemic Propagation   Commonality With Prior Art Forms       

   Combination of Prior Art Forms
         Unitary Distinction       

   PRIOR ART OVERVIEW 
   The differences between the present invention and prior art lie in simple scope, as well as specific application. At one end of the spectrum, Digital Earth 16  is cited as a massive global initiative to create a digital linked network of terrestrial data using digital mapping and locating technologies (GPS/Global Positioning System geospatial reference coordinates) to represent the earth&#39;s geographical features. Their scope includes the spectrum of very large (oceans and continents) to very small (media rich descriptive meta data attached to a narrowly circumscribed area) phenomena. Digital Earth represents objects in a distributed network of servers with multiple addressing methods. 
   The Universal Semantic World Wide Web 17  is a requirements description of an ideal web representation of assertions about objects and events in a distributed network of servers with multiple ontological indexing methods. The present invention is one method that both addresses and indexes and applies to both objects and assertions about objects. UR-URL combines the content vision of the first with the access vision of the second. 
   At the other end, Pullen&#39;s “Integrated field modeling system,” 18  is cited as an example that takes digital mapping to the micro level. She uses fixed coordinate mathematics in a computer-based method for modeling and replicating phenomena through atomic and molecular dynamics. 
   There are many instances of prior art similar to Pullen that apply to modeling, communication, encryption, synthesis, data manipulation, routing, and identifiers in general for addressing and indexing systems using various properties alone and in combination. Each specifies a scope of less than |EVERYTHING|. The present invention replaces and subsumes them all. Chumbley 19  is an example of a similar approach with expectations limited to locating some things in some systems. 
   In the middle are the many and varied commercial, political and personal uses of identity as represented by information-technology industry leaders affiliated for the purpose of federated identity. UR-URL may be distinguished from all prior art in that UR-URL has the unique feature that it incorporates and extends the utility of each technology severally, and in any and all of multiple combinations. 
   State-Of-The-Art Technology 
   The state-of-the-art is set by Microsoft, Sun Microsystems, Hewlett-Packard, and IBM, Oracle, ATT, American Express, Bank of America, and three hundred other well-known corporate multinationals who&#39;ve aggregated in two camps to promote identity solutions. MS, HP and IBM form the core of UDDI, the consortium that uses Microsoft products and vendor standards. The Liberty Alliance is a collaboration of businesses that use Sun&#39;s Java products and vendor standards. The Liberty Alliance Project and UDDI share common motive, method, and means that transcend minor differences in application—which largely amount to yet another layer of intermediary vendors and redirects that subject shared information about customers to increased risk across many business partners. 
   Digital Earth 
   On the surface, Digital Earth 22  and the present invention&#39;s “one universal Model of Everything” sound similar. The differences will be made apparent. The following description and objectives have been abstracted from the reference documents found on their website. The present invention may be specifically differentiated from Digital Earth in the following regard.
         Begin excerpt:   What Is Digital Earth?   Society has gathered an enormous amount of digital information about the Earth and its inhabitants. This digital information consists of everything from satellite photographs that detail cities and farm fields to databases containing information on transportation, commerce, population, crime, food production, history, and much more. The scale ranges from global to local—from humanity to the individual. This information that is stored around the world is not easily accessible or easily utilized in conjunction with other types of data . . . . Recognizing this challenge the National Digital Earth Initiative was created to enable and facilitate the evolution of Digital Earth, a digital representation of the planet that will allow people to explore and interact with vast amounts of natural and cultural information . . . . A primary goal of Digital Earth is to unlock the world&#39;s knowledge by simplifying access to georeferenced information, which is information that relates to a particular spot or area of the earth. The Digital Earth Vision is to provide Interoperability of geo-referenced digital resources. For additional information see the national web page.   End excerpt       

   The inventor points out the defined scope of less than everything. Digital Earth claims to represent physical data referenced to geo-coordinates. UR-URL has a larger scope that extends to noumena, or non-physical data.
         Begin excerpt cite continues:   Introduction and Scope   The types of georeferenced information that Digital Earth will make accessible include earth imagery, digital elevation models, land usage, gridded geophysical parameters, vector maps, and location-specific cultural and historical information. The information may be relevant to the Earth&#39;s surface, interior, atmosphere, or near-space environment, as long as it can be related to a coordinate system centered on the planet.   End excerpt       

   The inventor points out this further definition of information about physical phenomena.
         Begin excerpt cite continues:   Interoperability Issues   Among the outstanding interoperability issues are the following:   1. Implementation specs for coverages, advanced geometry   2. Identity, relationships, topology   3. Niche data modeling concepts needed for advanced services; data types required by service I/O   4. Internationalization, i.e., appreciation of cultural and linguistic diversity   Introduction and Scope   Digital Earth focuses on geodata and geoprocessing resources that are network accessible. Mere presence on a network, however, is not sufficient to make such resources easy to find and access. Digital spatial data and metadata are represented in many forms and stored in diverse and often very distributed systems. These aspects, combined with the sheer volume and diversity of resource types, demand common standards to support effective discovery mechanisms. Such discovery standards must support not only text search and matching for bibliographic metadata, but search of more complex characteristics such as geometries, date ranges, and taxonomies . . . . The Content Standard for Digital Geospatial Metadata does not specify the means by which geospatial metadata is organized in a computer system or in a data transfer, nor the means by which this information is transmitted, communicated, or presented to the user.   End excerpt       

   The inventor points out that UR-URL does specify the means by which Geospatial metadata is organized in a computer system and in a data transfer and the means by which this information is transmitted, communicated, and presented to the user.
         Begin excerpt cite continues:   Value Added Service Enablers   Value-added service enablers provide geospatial information products, niche applications and enabling services for integrators and service providers. We will see a proliferation of vendors who convert commodity data into information products packaged for particular market segments or individual users. Similarly, service enablers/providers will produce myriad geo-intelligent services for consumer, business and government clients.   End excerpt.       

   The inventor points out that UR-URL is specifically intended to be such a vendor of geo-intelligent services for consumer, business and government clients.
         Begin excerpt cite continues:   Vicinity.com is a good example of a company that adds value to technology and data to provide a service to its customers, mostly Web site owners who want to provide their customers with information about locations of, for example, stores and customer service centers.   Integrators   Integrators provide integrated solutions, custom applications and professional services for service providers and end users.   Service providers   Service provides offer final products or services to the end customer.   The Internet is providing many new opportunities for companies to provide services and information products as opposed to providing systems and data. Most Web sites currently offer only the passive documents that HTML is designed to provide. The next big phase in the evolution of the Web will involve automatic invocation of services that are distributed over the Net. Service usage will be paid for by license, by subscription, by timed metering, or on a pay-per-use basis. Abundant bandwidth and E-commerce tools that automatically manage innumerable transactions per day will support a rich market in online services.   The end customer   The end customer in the geospatial value chain might be a consumer or someone in a government agency or business. The products and services delivered to the end customer will almost always pass through or depend on multiple industry players who depend on interoperable geospatial technologies. These end products and services will sometimes be entirely spatial information, but more often they will be “hybrid” in nature, only partly geospatial. The Web&#39;s advance is regrettably creating a “swarm” of network-resident geospatial data and geoprocessing services. Currently there are many web-based mapping sites, but almost none interoperate.   New Markets   New markets will open as geoprocessing enters mainstream IT and as the new Net and object-centric geospatial infrastructure fleshes out and matures.   Consumers   The geospatial industry has served mainly a set of users trained in managing complex geodata management problems. These users, working in the traditional GIS and remote sensing application markets, will benefit from network-based geoprocessing, and they will grow in number, but a much larger population of less skilled users will begin to benefit as well. Looking forward a few years, it is likely that people&#39;s information appliances will include “personal spatial assistance services” that will maintain the individual&#39;s information context and connection (personal logical network) as the individual moves through space, bridging media and modality, mapping electronic locations of devices (addresses) to their physical locations; using concepts of “reach space,” “co-location,” and “near-by.” Mobile, location aware, Internet-connected devices will use their location awareness to maintain and optimize their Internet connections and also to deliver a variety of consumer services.   End excerpt.       

   The inventor points out that UR-URL provides such a method to control individual identity elements as an individual or thing moves through space.
         Begin excerpt:   Here are some of the ways in which consumer markets can make or are making use of geospatial data and geoprocessing, particularly in an environment of wireless, spatially aware devices:   1. E-commerce. Location-sensitive shopping agents.   2. Entertainment. Virtual travel—visit places without being there.   3. Travel/tourism. Downloadable applets for the mobile tourist.   4. Emergency road services, 911 emergency response systems.   5. Personal safety/security, health monitoring   6. Cell phone or car mayday button.   7. Security monitoring and intrusion response.   8. Special wayfinding for elderly and disabled.   9. Child, pet, and car position reporting devices.   10. Businesses E-commerce. A transaction-intensive company storefront shows the location of nearest customer service centers for their products.   11. Supply Chains. A large manufacturing company updates their centralized, mainframe-based supply chain management system by adding mid-tier geospatially-enabled “servlets” and secure Web applications for its offices, suppliers and distributors scattered around the globe.   12. Customer Support. Customer service representatives assist customers over the Net and coordinate with field technicians via mobile, position-aware PDAs.   13. Enterprise Resource Planning Systems. A company&#39;s distributed decision support capability is crucial to timely and effective operations; geospatial decision aids offer a new dimension to the decision process.   14. Targeted advertising and marketing. A large consumer products firm is getting poor investment returns on its advertising and marketing; it turns to the Net and uses geo-intelligent agents to more effectively target its prospects.   15. Planning, Operations and Maintenance for spatially-dependent industries like transportation, telecommunications, agriculture, natural resource exploitation, water and power distribution. A field operations support system ties mobile field personnel to the dispatch center; geospatial objects offer descriptive portrayals of field activities   16. Packaging/Shipping/Distribution. Delivery personnel for a shipping company start their days at the distribution center by downloading applet-based manifests for the day&#39;s run.   17. Finance/Banking. Investment analysts at a major bank use geo-intelligent agents to scan market databases and report on global market trends.   18. Insurance. A progressive insurance company moves to integrate spatially-oriented insurability factors into their new dynamic rate-determination system.   19. Health care. Outpatients with telemetering sensors and GPS can immediately tell health care professionals and family the health status and location of patients.   20. Spatially-enabled buyer&#39;s guides for small businesses provided by service providers.   21. Advertising and marketing. Spatially-enabled yellow pages populated by value-added service enablers and provided by Web portal service providers.   22. Lead generation. Spatially-enabled software agents scour the Net for business opportunities.   23. Travel. On-line automated travel agents employing spatial capabilities become readily available to assist in finding and booking low-cost travel.   24. Networking. A small business uses geo-intelligent agents to find local subcontractors for a bid it is preparing.   25. Real estate. On-line real estate listing services built by integrators for service brokerages, with the data produced by value added service enablers.   26. Precision agriculture. Network-available geospatial services provide farmers with biweekly crop health and status reports.   End excerpt.       

   The inventor points out that these multiple uses are all enabled by UR-URL.
         Begin excerpt cite continues:   Governments   The role of government in Digital Earth is explicitly not to build a monolithic system in which all geodata can be housed and distributed. Rather, government—especially at the US Federal level—will encourage industry, academia and government researchers to develop technologies, standards, services and software that enable the Digital Earth vision of seamless and intuitive access to georeferenced information. Here are some of the ways in which governments will make use of geospatial data and geoprocessing in an open distributed processing environment:
           1. Emergency management and response. Disaster mobile operations management systems include distributed geoprocessing capabilities for real-time decision support and distributed, collaborative relief operations.   2. Resource management. A large federal agency with scarce, distributed resources upgrades their management system to allow collaborative resource management tasking on the Web, using, for example, geospatial applets.   3. Defense and intelligence. The U.S. Army adds modules to a distributed war gaming system that makes it easier to change geographic simulation spaces using a new high-performance geospatial information appliance.   4. Environment Management. Remote spatially-sensitive sensors are incorporated into a monitoring system to assist in time-critical remediation efforts.   5. Transportation. Geospatial software objects/applets with traffic and weather information are dispatched regularly to mobile units   6. Census. New Web census reporting services to the public, government and business.   7. Mapping. Digital Earth mapping plans for the United Nations: cooperating governments and enterprises around the globe should use the DERM in their planning, and require standards-conformant geodata and geoprocessing software.   8. Public Safety. Police use distributed geospatial objects to offer field personnel critical, real-time decision support and distributed, collaborative operations.   9. Municipal information services. A progressive municipality might offer new Web services to homes and businesses for “Dig Safe.”   10. Education. A new earth studies course is offered globally to demonstrate the viability of distance learning to remote areas.   11. Research. Digital Earth research occurring in universities around the globe results in hundreds of new applications for spatially-oriented problems.   
           End excerpt.       

   The inventor points out that UR-URL is especially valuable for government purposes where a unique identification and addressing method are required. It has easily recognizable symbology, while providing value-neutral content. The address references incept location and time, but no other demographically sensitive data may be derived from the identification schema alone. Governments require such terms.
         Begin excerpt cite continues:   What is Clearinghouse?   A fundamental goal of Clearinghouse is to provide access to digital spatial data through metadata. The Clearinghouse functions as a detailed catalog service with support for links to spatial data and browse graphics. It is not the intent of the FGDC to create a centralized data system or index but to facilitate distributed search against multiple, current stores of spatial metadata and data on the Internet.   End excerpt.       

   The inventor points out that it is the intent of UR-URL to create a centralized data system and index, and to facilitate distributed search.
         Begin excerpt cite continues:   Address Content Standard.   Within this scope, addresses are broadly defined as locators to places where a person or organization may reside or receive communications, but excluding electronic communications . . . . Addresses are a key part of most data sets involving people and organizations as well as their activities, and many agencies maintain data keyed to addresses. There is a proliferation of agency address standards which have been developed in response to specific agency needs. By their very nature, these existing agency address standards present conflicting guidelines for creating and maintaining addresses and address lists. Existing agency address standards do not provide common semantic definitions which may be used by the myriad of organizations wishing to successfully exchange address data. Given the enormous expense of collecting, maintaining, and using address data, there is a need for an FGDC address content standard to improve the sharing and exchange of address data amongst Federal, state, and local governments and other interested participants. End excerpt.       

   The inventor points out that UR-URL does provide a common semantic definition, which may be used by the myriad of organizations wishing to successfully exchange address data.
         Begin excerpt cite continues:   Digital Earth infrastructure, .geo domain   Yvan Leclerc, SRI International   Infrastructure Requirements: Open   1. Anybody should be able to add metadata (use digital signatures for authentication)   2. Any type of georeferenced object   3. Cameras, vacation pictures of Yosemite, cars, buildings, avatars, cell phones, aerial/satellite images, classroom geography projects, . . . .   Infrastructure: .geo domain   1. Use DNS to encode latitude/longitude for any element in a hierarchical n-tree.   2. minutes.degrees.tendegrees.geo   3. e.g. 37e47n.1e5n.10e20n.geo   Using DNS to Index Geographic Data   The infrastructure we propose to meet the goals of scalability without undue burdens on any single server is based on a hierarchy of Web servers. Each server in this hierarchical organization has a DNS name that represents a given geographic area of the earth, called a cell. The server is responsible for all metadata about data that lies within this area and has a footprint within a limited range. It is also responsible for providing DNS service to those servers corresponding to smaller cells within its own cell, and these servers are responsible in turn for correspondingly more detailed information about their smaller cells . . . . By limiting the area and range of details in this way, each server becomes responsible for only a tiny fraction of all of the metadata available around the globe. Furthermore, by using DNS names that represent the geographic service area of the server, clients can immediately determine which server to query without the need for a global name server . . . . The servers in our infrastructure are arranged hierarchically in the form of a rectangular n-tree. At the base of the n-tree is the top-level domain name .geo. We are currently proposing a hierarchy of the form minutes.degrees.tendegrees.geo, though this may change if more levels of the hierarchy are deemed necessary. Copyright©2000 SRI International.   End excerpt.       

   The inventor points out the primary difference between this schema based on DNS and other schemas based on other formats for geocoordinates is that UR-URL uses spacetime referential geotemporal coordinates, and does not require the hierarchical DNS-like array of intermediaries.
         Begin excerpt cite continues:   Digital Earth implementation poses many technical challenges. Data management is a key concern . . . and it becomes obvious that simply storing, indexing, and retrieving the data will be a formidable problem . . . . Clearly no single organization will have the resources to administer the entire Digital Earth. This implies a distributed framework, with high speed networks to route data from repositories to processing centers and on to end users . . . . Digital Earth is a concept for unifying many different views of the Earth, the creatures which inhabit it, and the natural and cultural environments in which they live. Although many potential components of a Digital Earth exist now, the framework and technologies needed to tie them together have yet to be defined. Nonetheless, a consensus is developing that such a framework is useful, even necessary, and it seems almost inevitable that one or more “Digital Earth&#39;s will emerge within the next few years.   End excerpt.       

   The inventor points out that the present invention is an example of an emergent “Digital Earth,” and the framework that ties it together is Unitary Reference Architecture. 
   Current Context 
   Individuals Affirm Identity. Anyone can walk into a library and, upon minimal verification of their assertion of identity, get a library card with an identifier that let&#39;s him check out a book. The library is under no illusion that they can sell their list of users&#39; names and addresses to publishing houses that want to market to people who like to read. Identity and identifiers, as well as any other information about a person, belongs to the person, not to a service provider. 
   Official Records Corroborate Affirmations. Minting has the effect of establishing a symbolic identity by formalizing referential relationship between a resource event (you) and an identifier. The government, as the first really big mint, or promulgator of identity-related management control systems, established strict policies about how information about citizens could be obtained, authenticated, stored, used and shared—or not. 
   Replication Error in Premise 
   With democracy stalled at the Web access starting gate, our ability to assert dissention is regulated by the folks who make the rules. Rules we don&#39;t really even know about. There is a fundamental flaw in the basic reference architecture that defines the Internet system itself. It&#39;s built on an inadvertent misapplication of transaction identity rules to people identity requirements. This is bad business practice and about to get worse. 
   The first generation analog original is a brick and mortar system of ownership of stuff by people, and the second-generation paper system is a copy of the original as official transaction records. The new web services version is a third generation copy of a copy of the system. 
   It&#39;s intentionally designed to be a system of records that represent transactions that represent a system of ownership. It is not a system of entity ownership. It&#39;s a system of transactions records about transactions about ownership. The important thing is the transaction, not the person. The transaction has identity and people are just details. The biggest difference in this bizarro-world version is who owns the right to represent identity. In the analog world, individuals own identity and identifiers. In the digital world, mints own both. Owning and controlling customer identity is the key to profitability in the Internet economy. 
   Replication Error in Purpose 
   “There is a war brewing over the future of the Internet . . . and to the victor will go an online business that is far bigger and richer than anything either company has seen to date. The battleground is none other than control over your digital identity—your name, your credit card number, your e-mail address, your calendar, your music, your photos, your shopping habits. Control those on behalf of the consumer, and it&#39;s over.” 13    
   Identity providers are co-opting identity on purpose. 
   Universal Resource Identifiers 
   According to the inventors of the Internet,
         “The Web would be impossible without some form of global identifier. The most fundamental specification of Web architecture, while one of the simpler, is that of the Universal Resource Identifier, or URI. URIs may refer to documents, resources, to people, and indirectly to anything. The principle that anything, absolutely anything, “on the Web” should be identified distinctly by an otherwise opaque string of characters is core to the universality. An identifier is an object that can act as a reference to something that has identity. In the case of URI, the object is a sequence of characters with a restricted syntax. Having identified a resource, a system may perform a variety of operations on the resource, as might be characterized by such words as ‘access’, ‘update’, ‘replace’, or ‘find attributes’.“ 14  Tim Berners-Lee, “Web Architecture From 50,000 Feet,” The Fundamentals: The Universal Web.       

   According to the World Wide Web Consortium&#39;s (W3C) “Principles of URI/ID Design,” 8  the key features of an ideal Universal Resource Identifier (URI) are Uniqueness, Universality, Persistence, Scalability, Evolvability, Opacity, No Side-effects, Global uniqueness, Optional sameness, Fully Non-dereferenceable, Infinite number of referential mints, Myriad interchangeable code variations within same referential system. 
   The present invention meets these criteria. Furthermore, it demonstrates W3C ideal design principles, which are Simplicity, Modular Design, Tolerance, Decentralization, Test of Independent Invention, and Principle of Least Power. The present invention represents the ideal universal resource identifier method as envisioned and defined by the framers. No known method can. These criteria are viewed as a wish list, not an expectation. The current embodiment does not meet this specification. Moreover, it&#39;s commonly acknowledged as inadequate for the expanding needs of our growing electronic infrastructure. 
   Critical Distinction 
   In the original specification that defines the Internet, distinction is made between identity and identifier, but not between people-identifier and data-identifier. It was logical to extend old pre-Internet rules for electronic data to all resources, including people. Therein lies a paradox in terms. People are human resources in everyday usage. And in an intranet, human resources are resource objects. But on the Internet, users are not employees, they&#39;re voters. The public at large is not a corporate data pool. This is a largely unrecognized difference that matters a lot—literally the difference between ownership and subjugation—that&#39;s defined into the architecture. 
   In the real world, people with identity make transactions with identifiers. In the digital world, transactions with identity own people with identifiers. On top of that contradiction, the label “User ID” compounds confusion and ultimates in common substitution of the term “identity” for “identifier.” Altogether, we end up with a double-reverse back flip mutation of the intents and purposes of both terms. You can&#39;t mint identity; you can only mint identifiers. And only owners have the right to claim names. Because identity providers assert does not make it so. 
   Competitive Context 
   Functional Limits Drive Design Specification. It&#39;s the current prevailing wisdom that there&#39;s no such thing as a universal persistent unlimited method for self-service single sign-on identity. It&#39;s just simply not possible. They assume the natural limits of the copy world and apply them as constraints. In computerized relational database management, identifiers are typically codes and algorithms that use permutations to generate large quantities of unique strings. Identifiers are lumped with other math-based computer functions, and the only absolute requirement is that there be uniqueness. This mindset of identity as a data field belonging to a transaction informs their approach to formulating identity methods, which are not for data, but people too. Instead of designing a new system for people, they upgraded an old system of transactions. It serves business purposes and that&#39;s enough. 
   Vendor War Drives Implementation 
   The solutions big business offers are arrayed against the backdrop of competition. What&#39;s at stake is the very future of one or more proprietary technologies. The key players are Microsoft and Sun Microsystems.
         “Microsoft, in fact, has a new mission, and it is called .Net. At its simplest, .Net is an attempt to shift Microsoft&#39;s business from selling software to renting out a vast array of Web-based business and consumer services, such as Passport and Hailstorm. It&#39;s the latest manifestation of Bill Gates&#39;s determination to increase the percentage of Microsoft&#39;s revenues that come from recurring fees, as opposed to one-time sales of software.   The technological goal of .Net is to plow through the competing standards and other roadblocks and create a Web where it&#39;s far easier for servers to swap information and provide services on the fly. Microsoft believes the Internet is entering a new age of distributed computing, and Net&#39;s job is to ensure Microsoft&#39;s dominance in this new age.” 13 Ibid  
 
Systemic Propagation
       

   Citizen users are not objects owned by enterprises. The new industry-giant identity partnerships blur lines between inter-intra-extra-nets, which makes single sign-on more than a matter of better business as usual. When technical difficulties define public policy by default, it&#39;s personal. Self-representation isn&#39;t a privilege we need interveners to grant and manage. It&#39;s not even a right that laws originate, much less a performance criterion that products enforce. Self-representation is the fundamental and irrepressible expression of being as economic necessity. Without it, the individual has nothing. This is what the current embodiment holds for the future. 
   Existing architectural constraints, combined with aggressive competitive market practices, are driving definition of digital access. This is the current state of applied prior art in the field of identity. 
   Commonality with Prior Art Forms 
   UR-URL, as an identity addressing and indexing method, may be compared to other addressing and indexing methods in the context of the technologies that utilize addressing and indexing methods. High order categories of use include but are not limited to:
         1. Classification systems and architectures,   2. Routing communications, as in telephone and data transmission,   3. Manipulating images, as in photographs and other representations,   4. Locating points or objects in space, as in navigation and traffic control,   5. Deconstruction and replication of objects, as in cloning and synthesis,   6. Nanotechnology applications, as in simulation and control of miniature machine agents, biologic agents, information agents, and,   7. Data integration, as in primary key differentiation and control of multiple elements in one system.       

   A unique identification address (primary key) for each element in a set or system is mandatory in each instance and application type listed above, and in fact the existence of such unique identification field is the mechanism that enables them. The current embodiment is many identification code methods in each category of use. The present invention applies to each current embodiment and to all uses where differentiation of many elements in one set is necessary to achieve political, social and/or economic objectives. 
   Combination of Prior Art Forms 
   The present invention&#39;s business methodology proposes one uniform identification numbering/classification method for all commercial identification applications and purposes. The same method also applies to governance and social uses. Examples of concurrent public purposes that could be served include but are not limited to:
         1. Use UR-URL for taxation, social security and employment records   2. Use UR-URL for voting and direct participation processes   3. Use UR-URL for ethnicity-bias-free demographic data keyed to geography and age   4. Use UR-URL for random selection processes grouped in various configurations   5. Use UR-URL for security processes and marks of authentication   6. Use UR-URL to record official legislative, judicial and regulatory effectivities   7. Use UR-URL for military, anti-terrorist and national security purposes   8. Use UR-URL for global wireless data and voice communications       

   Beyond these uses, additional uses are illustrated in  FIGS. 81-92  Homepage Views as sample applications, and functional groupings of applications are described in Alternate Embodiment section. It is the intent of this patent application to stipulate |ALL| uses by way of categories of extant practical applications identical in regards except as refer to identification, to which the present method employs to advantage in each case and all cases. 
   Unitary Distinction 
   The present invention has the singular characteristic that it applies to and uniquely identifies all users and governs all uses. Prior art methods apply to many users and many uses, some digital, some analog, some things, but not |EVERYTHING|. 
   BRIEF SUMMARY OF THE INVENTION 
   Table of Contents
         Marketplace of Identified Ownership Events   UR-URL Code Structure   Present Assertions   Key Ideas   Terms   Unitary Ontology   Differentiation   Independent Minting   Coordinate System Equivalence   Universal Information Architecture   Summary of Differences
           1. Better Design Approach   2. Greater Combination of Elements   3. Modification To Standard Term   4. Broader Application   5. Different Scope   6. Different Design Criteria   7. Superior Design Principles   
           Unitary Advantages
 
Marketplace of Identified Ownership Events
       

   In a nutshell, a Model of Everything is made up of: a universal information architecture, a method for self-minted self-service identity, a scalable business process for integrating data from different tables and/or from different systems into one combined system, a method to organize everything, and a search engine and directory to make it all accessible. There&#39;s also a programming process and language, a modeling medium, and a number of interesting applications that in further combination provide a new roadmap, a new on-ramp, and a new routing mechanism for commuters on the information super-highway. 
   Where other addressing methods are designed for property and used by vendors to identify people, URA is a tool designed for people to identify themselves in the economy. The rules that formalize systems as architecture need to be consistent with the principles of democracy they simulate. URA is. Existing current embodiment prior arts are not. 
   UR-URL Code Structure 
   The optimum code structure for a Model of Everything is indicated by the intersection of Information Science and the Theory of Relativity, and usefully applies and extends Conservation Laws. Because no two things can occupy the same space at the same time, referential space-time geo-coordinates are natural and “real” identification numbers. Everything and everyone has an incept XTZT/Gt. That is, no two people are born in the same bed at the same time. Each event has a unique set of longitude, latitude, elevation and time designations that are fixed according to an established referential system. This applies to all events in all time: entities and property, as well as the transactions that formalize agreements about them, and as such, defines and constitutes unitary identity information system reference architecture. The application of the fact that assertion of incept ownership is the unifying property for all things and ideas is unique to the present invention. 
   Present Assertions 
   
       
       
         
           I. The “gt” in XYZT/gt represents a quantitative adjustment for curvature of space where it matters and can be measured. 
           II. The relativistic view of gravity as the “rate of change of intersection between events” may be represented as the summation of changes in relative links in a database of everything, be they objective or assertive. That is, gt stands for change in relation—both spatial and temporal, quantity and quality. 
           III. Everything&#39;s connected to everything by URA. It integrates and differentiates and demonstrates the fundamental theorem of calculus. XYZT/gt is the unifying field in a database of everything and XYZT/gt is the unifying property in spacetime. Agreement is the unifying force. 
           IV. Matter is finite. Relation is not. Conservation Laws hold for objects, but not events, which use the same objects over and over in ever-new assertions of identity by owners, makers, and discoverers. 
           V. The unification set |         | is the one and only unitary event system object—a finite and expanding model of spacetime. |         | is the largest set: |         | 0 =S∀(x)=1ΛC 0 ≧1□C 0 ≦|         | 0  
 
Key Ideas
 
           1. An event is something that happens, a system of objects in relation. 
           2. An information object is something that happens in an information system, a virtual event artifact. 
           3. A virtual event artifact, also called an entity, is a copy or representation of a real object, artifact, or idea. 
           4. An event object is a system of related object constituents and properties. 
           5. An event system is a system of related event objects, also called event system object. 
           6. Events come in two sizes: all in one, and one in all. 
           7. Events come in two varieties: the first now, or incept, and other nows, or updates. 
           8. Event objects don&#39;t have identity until origination conditions are claimed and named by makers, owners, and discoverers. 
           9. Events are undifferentiable continuums brought to a standstill by common assertion of relation at time certain. 
           10. Time is not a force. Agreement about it is. 
           11. Time is a variable in all force equations. Consensus about what time is and how it&#39;s measured “makes” time a unifying constraint. 
           12. Everything is relative. 
           13. Everything is by agreement
 
Terms
 
           Event: “Something that happens; occurrence; a noteworthy happening; a social occasion or activity. The fundamental entity of observed physical reality represented by a point designated by three coordinates of place and one of time in the space-time continuum postulated by the theory of relativity.” 2 Ibid    
           Relativistically speaking, everything is an event. Everything is an object and everything is a system. Event objects are systems. Event systems are objects. It&#39;s not complicated, it&#39;s synthesized to highest broadest commonality. The unitary in Unitary Technology means one. Sameness is simple. And cost effective. 
           An event object is one thing, an entity, all in one—made up of parts and pieces with properties, attributes, and relations that hold it together—a system of constituents in a same-place/same-time condition. An event system is one thing too, a group, one in all—made up of two or more objects related by common property or purpose. 
           An event object is the smallest system. An event system is a combination of any two or more event objects and/or systems. An event system is defined as the relation between two or more objects or assertions with one property in common (the reason the objects or assertions regularly interact, or the purpose that unifies the objects as one “whole” group), and one property that&#39;s unique (a way to tell “items” apart in a “group”). 
           A list is defined as a system. A table is defined as a system. A database is defined as a system. A program is defined as a system. A computer is defined as a system. A network (intra-inter-extra) is a system. A global network of information and telecommunication and transportation systems is a system. A potted plant, a family, a discipline, a science, a language, a culture, a project, an ecology—all are systems. 
           All common groupings of items at all levels of scope, granularity, and purpose are defined individually and severally as “event systems” as would be generalized by everyday persons who interact with them.
 
Unitary time certain is defined as incept or origination date and time, as asserted by maker. All objects and assertions are presumed to have incept, which is a unique unifying event property that resolves space and time and upon which rests the capacity for representation of everything in one system and all systems in one system.
 
         
       
     
  
   The term “Object of Everything” defines a “whole system event object” and refers to the collection of all the individual constituents in any one object as a system or any one system of objects, at any specified level of granular representation. “Everything” is a extensible term, in that combining “every-things” from any two or more individual system databases as whole “objects of everything” results in a new Object of Everything and a new combined whole-system object. Systems may be thus represented individually and aggregated modularly. 
   Private and public system objects may be integrated, federated, and accumulated. The unitary event is the original assertion of incept identity—self-minting—the act of establishment that coheres civil society. The unitary system event and largest object—the present invention—is a Model of Everything. 
   Unitary Ontology 
   Unitary ontology is fundamental technology. The following logical statement stipulates one super-ordinate unitary ontolological architecture. Basis: Everything is an event. Objects are events. Assertions are events. 
                                                           0. ALL EVENTS - EVERYTHING            1.0. EVENT ASSERTIONS   1.1. EVENT OBJECTS            1.0.0. PRINCIPLE   1.0.1. TRANSACTION   1.1.0. PERSON   1.1.1. PROPERTY                    
The terms Event Assertion and Event Object are defined as inclusive of and synonymous with generally held top-level divisions of everything, i.e.: physical or non-physical, tangible or intangible, matter or mind, thing or concept, object or subject, property or agreement, phenomena or noumena, and so forth. All other ontologies are by this definition Derivative Ontologies.
 
   All existing ontologies, taxonomies, and classification systems fall within their respective domains as either Event Assertions or Event Objects. Unitary Ontological Reference Architecture does not attempt to specify variety or number of referential systems. Indeed, the function of unitary ontology is to establish an all-inclusive framework within which any number of classification systems and parameters may be employed. 
   The secondary purpose of establishing one unitary ontological reference architecture is to usefully and universally categorize the domain [EVERYTHING] so as to make information accessible. The primary purpose of Unitary Ontological Reference Architecture is to show conclusive evidence that the domain [EVERYTHING], as defined herein, and claimed by the present invention, is indeed inclusive of everything. No other method claims all events, which if you agree with Einstein, is everything. No other method claims all objects and all assertions, which is everything if you use common non-relativistic definitions. Details of Unitary Ontology Architecture are depicted in the several views of the drawings. 
   Differentiation 
   Traditional object oriented approaches begin with objects as entities that own properties, relations, and participation in events. Objects are accumulated in functional databases where difference—more apparent than commonality—drives an army of upgrade licenses marching side by side. The inventory control system has one kind of information, the human resource system another, which may or may not match the resource pool in the scheduling system, and there are often legacy data pockets that don&#39;t match anything. 
   In contrast, Unitary Technology starts with relativity and an event orientation. Everything is an event. Events are entities that own objects. And makers own events and artifacts. The event of object, what&#39;s being recorded in the list, is either original incept of the aggregation of constituents, the preliminary definition in the system, or update—a change to any aspect of original condition. 
   Independent Minting 
   With Unitary Technology, each system (internal and external) may be treated as a subsystem to the whole with addresses relative to any point and scale. Reuse and integration are easy. Systems using different references are easily converted to equivalency. Owners mint identifiers. Identifiers correspond to real objects, assertions, and artifacts, actual times and places. People have options in minting their identifiers. There are only two criteria: you own the event and can prove it with a link to a real authority that has a real instantiating artifact. For example, your birth certificate references both the hospital location and your parent&#39;s home address; you could choose either. The title to your home references both your identity and the property, so you could choose that UR-URL for a communication address. What matters is there&#39;s a trail to formal authentication and accountability. 
   Coordinate System Equivalence 
   Longitude, latitude, and elevation coordinates come in different varieties. E-Gov will likely apply some standard georeferencing convention for official use. Conversion formats and formulas will be bundled as plug-ins. It won&#39;t matter which standard references or syntax are used within any given system, what will matter is real-time agreement to protocols when two systems exchange data. 
   Universal Information Architecture 
   One information architecture doesn&#39;t mean all the information in the universe is contained in one place, on one server, of one type, in one language, or one database. It means all the information everywhere can have the same basic set of terms, the same system of identifiers, the same organizing basis, and the same classification conventions so all the information and communication events can be sensibly integrated for fast access by both users and agents, internally and with partners. Plus, common terms simplify multi-dimensional analysis across disparate data sets. 
   Summary of Differences 
   1. Better Design Approach 
   
       
       
         
           Where the current embodiment is the result of bottoms up requirements generation, adaptation, manipulation and formulation beginning with the problems working toward solutions—from some things to many things, the present invention was discovered and applications found afterward—starting with |EVERYTHING| and working top down, as illustrated in  FIGS. 1-6 .
 
2. Greater Combination of Elements
 
           The inventor combined Einstein&#39;s generally known ideas about relativity with other generally known ideas about organizing and accessing information systems with computers and search engines. The inventor discerned that, in table identifier terms, Einstein&#39;s spacetime event coordinates do indeed represent the unified field, the one place where everything is different but joined all in one time and place. With real incept specified, it&#39;s all time. Einstein defined and then discussed this property as it applies to location of and perspective from moving bodies. His purpose was to circumscribe and delimit the term so he could then define relative differences between points and moving bodies. It was not to generate addresses for event records in tables. Einstein did not have a computer. There was no practical example in nature for him to observe, test, and confirm his theory. UR-URL provides one common table field and one common nomenclature to describe the one thing that everything has in common-incept. The field that unifies, but differentiates is XYZT/gt/incept. It&#39;s already a unique name, if you stipulate both location and time in terms of referential relationship and ownership. Ownership is the key to differentiating many claims sharing one event identity.
 
3. Modification To Standard Term
 
           Minkowski defined the general term XYZT as a four-dimensional event vector comprised of three standard spatial components plus time. Einstein extended the conceptual model and terms to describe a universe of event objects correlated by measurable dimensional proximity to all other events. Unitary Technology adopts Einstein&#39;s theory of measurement and further acknowledges the role of gravitational influence by specifying the term XYZT/gt where Gt represents a quantitative adjustment for curvature in space when determining event locations as referential addresses. The factor Gt only applies where it can be measured, which now is in pretty gross terms over long distances. GPS technologies are improving our acuity, able to isolate smaller and smaller frames from satellites in space. In the future, our measuring tools will be even better and in nano-environments, little differences matter a lot. For most things, relative XYZT is sufficient to the purpose of uniqueness.
 
4. Broader Application
 
           The inventor therefore claims to uniquely apply Einstein&#39;s principles of relativity, in combination with computer and information science, to meet and conjoin the goals of Digital Earth, the Liberty Alliance Project, UDDI, and E-Government enterprise architecture and other public purposes with the present invention.
 
5. Different Scope
 
           Digital Earth uses specific referential geographical coordinates to define matter that you can see. Pullen uses non-specific referential spatial coordinates to define matter that you cannot see. The present invention uses specific referential geographical and temporal incept ownership coordinates to define matter that you can see and matter that you cannot see. The present invention combines the features and utilities of all identifier methods, regardless of object conditions, states, attributes, and/or properties. And none of the modeling methods that use coordinates stipulate the unifying property of incept ownership XYZT/gt. Where Digital Earth and Pullen are limited in scope and vision to physical characteristics and/or geographical features, UR-URL has no such limitations. UR-URL applies to not only geographical features (physical) but also the all-inclusive domain of events, defined herein to be incept instances of recordable information. In simple terms, “everything” was usefully classified as an event by Albert Einstein.
 
6. Different Design Criteria
 
           The inventor concludes that while Digital Earth and UR-URL have similar objectives and some common target data sets, they are not the same. UR-URL is exactly what the framers expected would evolve but could not specify. As such, it demonstrates non-obviousness.
 
7. Superior Design Principles
 
           Where Microsoft and the Liberty Alliance use standard algorithm principles to identify business entities and property, the present invention uses higher super-ordinate principles of physics to identify business entities and property, people entities and property, plus all other things and events.
 
Unitary Advantage
 
         
       
     
  
   Unitary Technology culminates the drive for information on demand with a blueprint for the ultimate resource—the present invention—one referential system and Model of Everything. A Model of Everything is a very big idea. Unitary Technology makes it not only possible, but also practical. 

   
     BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS 
     List of Figures 
     View I 
     Identity of Everything—Zero Dimension 
       FIG. 1  Everything 
       FIG. 2  Construction of Everything 
       FIG. 3  Deconstruction of Everything 
       FIG. 4  Dimension of Everything 
       FIG. 5  Extent of Everything 
       FIG. 6  Description of Everything 
       FIG. 7  Unitary Reference Architecture Components 
       FIG. 8  Alignment of Scope and Components 
       FIG. 9  Relation of Scope and Components 
       FIG. 10  Everything Components 
       FIG. 11  Unitary Reference Architecture Components 
       FIG. 12  UR-URL Identifier Method Components 
     View II 
     List of Everything—One Dimension 
       FIG. 13  List of Everything Components 
       FIG. 14  List View 
       FIG. 15  List With Prior Art Reference Architecture 
       FIG. 16  List With Unitary Reference Architecture 
     View III 
     Table of Everything—Two Dimensions 
       FIG. 17  Table of Everything Components 
       FIG. 18  Table View 
       FIG. 19  Table With Prior Art Reference Architecture 
       FIG. 20  Table With Unitary Reference Architecture 
       FIG. 21  Top-Level Ontology 
       FIG. 22  Event Ontology 
       FIG. 23  Relative Event Ontology 
       FIG. 24  Entity Ontology 
       FIG. 25  Object Ontology 
       FIG. 26  Ontology of Origination 
       FIG. 27  Ontology of Dimension 
       FIG. 28  Ontological Integration 
       FIG. 29  Dimensional Integration 
       FIG. 30  Alignment Between Primitive Terms 
       FIG. 31  Matrix of Ontological Terms 
       FIG. 32  Ontology of Everything 
       FIG. 33  Table With Unitary Resource Description Framework (RDF) 
       FIG. 34  Table With Extended Unitary Resource Description Framework (RDF) 
       FIG. 35  Table With Simple Unitary Resource Description Framework (RDF) 
       FIG. 36  Table With Unitary Reference Architecture, Ontology, (RDF), Hardware and Software 
     View IV 
     Database of Everything—Three Dimensions 
       FIG. 37  Database of Everything Components 
       FIG. 38  Database View 
       FIG. 39  Database With Prior Art Reference Architecture 
       FIG. 40  Database With Unitary Reference Architecture 
       FIG. 41  Database With Unitary Reference Architecture, Hardware and Software 
     View V 
     Platform for Everything—Four Dimensions 
       FIG. 42  Platform for Everything Components 
       FIG. 43  Platform View 
       FIG. 44  Identity Expressions 
       FIG. 45  Logical Expressions 
       FIG. 46  Correspondence Between Expressions 
       FIG. 47  Description Expressions 
       FIG. 48  Programmatic Expressions 
       FIG. 49  Diagrammatic Expressions 
       FIG. 50  Menu Expressions 
       FIG. 51  Prior Art Menu Synthesis and Simplification 
       FIG. 52  Simplified Menu Expressions 
       FIG. 53  Unitary Platform 
       FIG. 54  Current Embodiment Access Process 
       FIG. 55  Web Services Vendor Mint Access Process 
       FIG. 56  Worst Case Future Vendor Mint Access Process 
       FIG. 57  Present Invention Access Process 
       FIG. 58  Access Process Comparison 
       FIG. 59  Direct Ownership Process Components 
       FIG. 60  Intermediary Ownership Process Components 
       FIG. 61  Ownership Process Components Comparison 
     View VI 
     Web Portal to Everything—All Dimensions 
       FIG. 62  Web Portal to Everything Components 
       FIG. 63  Web Portal View 
       FIG. 64  Unitary Web Portal 
       FIG. 65  Sample Web Portal to Everything Page 1 
       FIG. 66  Sample Record  1   
       FIG. 67  Sample Record  2   
       FIG. 68  Sample Record  3   
       FIG. 69  Sample Record  4   
       FIG. 70  Sample Record  5   
       FIG. 71  Sample Record  6   
       FIG. 72  Sample Record  7   
       FIG. 73  Sample Record  8   
       FIG. 74  Sample Record  9   
       FIG. 75  Sample Record  10   
       FIG. 76  Sample Records Summarized 
       FIG. 77  Sample Web Portal to Everything Page 2 
       FIG. 78  Enterprise Record Examples 
       FIG. 79  Enterprise Record Example Detail 
       FIG. 80  Present Invention Part List Example 
       FIG. 81  Homepage  1   
       FIG. 82  Homepage  2   
       FIG. 83  Homepage  3   
       FIG. 84  Homepage  4   
       FIG. 85  Homepage  5   
       FIG. 86  Homepage  6   
       FIG. 87  Homepage  7   
       FIG. 88  Homepage  8   
       FIG. 89  Homepage  9   
       FIG. 90  Homepage  10   
       FIG. 91  Homepage  11   
       FIG. 92  Homepage  12   
       FIG. 93  Alignment Between Components and Component Parts of Unitary Reference Architecture 
       FIG. 94  Alignment Between Parts and Part Numbers of Unitary Reference Architecture 
       FIG. 95  Model of Everything Apparatus 
       FIG. 96  Preferred Embodiment 
   

   LIST OF TABLES 
   Table 1 Alignment Between Dimensional Views, Figures, Parts, and Numbering Nomenclature 
   Table 2 Sample Event Function Set Options 
   Table 3 MS Office Product Main Menu Examples—One Hundred and Two Objects 
   Table 4 Main Menu Synthesis—Twenty-Five Objects 
   Table 5 Sample Unitary Main Menu Optional Arrangements 
   Table 6 Unitary Terms of Description 
   The present invention is an information Model of Everything  1000 . Drawings illustrate the deconstruction of the conceptual singularity “everything” through successive dimensional views of components and parts in order to demonstrate claims to universality: “infinitely extensible” and “universally applicable” and “everything in one system and all systems in one system”—that “everything” really is |EVERYTHING|. Universality is made apparent in figures which define what everything is, and show that everything: 
   1. can be scientifically identified, differentiated, and integrated with UR-URL Identifier Method  101   
   2. can be versionalized by dimension with Unitary Infrastructure  200   
   3. can be grouped and classified with Unitary Ontology Architecture  300   
   4. can be scientifically described with six universal terms of Unitary Resource Description Framework  400   
   5. can be operationalized with Unitary Process Architecture  500   
   6. can be packaged and delivered with Unitary Apparatus  600   
   At one end of the spectrum, everything is one thing—one whole. At the other, everything is an exponentially huge quantity of particles in various arrangements and versions. There are many ways to systematize everything, and many ways to order explanations and images. To establish and maintain coherence throughout the many figures necessary for as large a subject as |EVERYTHING|, drawings are grouped in six dimensional views. Six high-level components shown in  FIG. 1  correlate by dimension as listed in Table 1. Sub-part numbers correlate to components and are, with a few exceptions, coded with the view identity (1, 2, 3, 4, 5, or 6) as the last digit of the part number. 
   
     
       
             
           
             
             
             
             
             
           
         
             
               TABLE 1 
             
           
           
             
                 
             
             
               Alignment Between Dimensional Views, Figures, Parts, and Numbering Nomenclature 
             
           
        
         
             
               FIGURE # 
               DIMENSIONAL VIEW 
               COMPONENT 
               PART # 
               SUB-PART # 
             
             
                 
             
             
               FIGS. 1-12 
               0-D Identity 
               Unitary Reference Architecture 
               100 
               100&#39;s 
             
             
               FIGS. 13-16 
               1-D Information 
               Unitary Infrastructure 
               200 
               200&#39;s 
             
             
               FIGS. 17-36 
               2-D Object 
               Unitary Ontology Architecture 
               300 
               300&#39;s 
             
             
               FIGS. 37-41 
               3-D System 
               Unitary RDF 
               400 
               400&#39;s 
             
             
               FIGS. 42-61 
               4-D Process 
               Unitary Process Architecture 
               500 
               500&#39;s 
             
             
               FIGS. 62-92 
               All-D Unification 
               Unitary Apparatus 
               600 
               600&#39;s 
             
             
                 
             
           
        
       
     
   
   The final four figures show additional big-picture views of the whole organizational structure.  FIG. 93  Alignment Between Component Parts of Unitary Reference Architecture shows “parts added” with each successive higher order component;  FIG. 94  Alignment Between Part Numbers of Unitary Reference Architecture, shows relationships between sub-structures;  FIG. 95  Model of Everything Apparatus Reference shows all the apparatus parts in one drawing; and  FIG. 96  Preferred Embodiment presents the preferred embodiment and preferred illustration of the present invention, Model of Everything  1000 . 
   I Identity of Everything View—Zero Dimension 
   FIG.  1  Everything 
   Everything, also referred to in absolute brackets |EVERYTHING|, is not a part or a component. Everything is the analog original that Model of Everything  1000  is a model “of”. 
   Model of Everything  1000  has foundation in Principle 1.1, a term which stands for the principle of unity on which the present invention rests, and the principles combined to make the present invention. Old analog principles of relativity are combined with old and new principles of information science and applied in a new context of event identity architecture. Resultant is further combined with old analog principles of private ownership and old principles of citizenship in a new universal identity architecture—the present invention—method, means, and apparatus for identifying, describing, and locating information events and information resources, with the unique feature of universal extensibility across the domain of |EVERYTHING|, defined on Page 4 and again as follows:
         Everything 2      1a: all that exists   1b: all that relates to the subject   2: every member or individual component of   3: the whole number or sum of   All 2      1a: the whole amount or quantity of   1b: as much as possible   2: every member or individual component of   3: the whole number or sum of   4: every   Reality 2      1: the quality or state of being real   2a (1): a real event, entity, or state of affairs
           (2): the totality of real things and   
           2b something that is neither derivative nor dependent but exists necessarily—in reality: in actual fact   Model 1      2: copy, image   4: a miniature representation of something; also: a pattern of something to be made;   7: archetype;       

   10b: a type or design of product;
         12: a system of postulates, data, and inferences presented as a mathematical description of an entity or state of affairs.       

   Per above definitions, the present invention&#39;s Model of Everything  1000  is at the same time a “copy” of our analog system, a “miniature” digitized information version of analog known reality, a “pattern” to build modular integrateable systems, a technology “product”, and “a system of postulates, data, and inferences presented as a mathematical description of [everything],” where the term “mathematical description” in elemental form is comprised of a reference number (a unique identifier) and name (alpha and/or numeric identity characters/symbols) for each thing. 
   |EVERYTHING| is taken to mean everything known, specifically all known reality as captured in analog and digital event records in a distributed network of information system resources maintained in various storage media worldwide. The present invention&#39;s identifier method, UR-URL  101 , is based on the discovery that relative referential geotemporal coordinates, applied as unique identifiers to incept events in a system of ownership that corresponds with analog principles of private ownership and citizenship, make possible the construction of a Model of Everything  1000 . As detailed in other sections of the present specification, relative referential geotemporal coordinates may be infinitely extended; relative referential geotemporal coordinates may be associated with objective things; and, relative referential geotemporal coordinates may be associated with maker-owner-discoverers at event incept. What&#39;s yet to demonstrate is that “everything”=|EVERYTHING|—which will be made apparent in figures. 
   Figures are best understood as a multi-assembly bill of materials. Components, sub-components, and parts are arranged in tree-form and read as “goes into” charts—what&#39;s below “goes into” what&#39;s above. Conversely, what&#39;s above is “made up of” what&#39;s below. 
     FIG. 1  Everything depicts the structure of |EVERYTHING| as high-level components of the present invention, Model of Everything With UR-URL Combination Identity, Identifier, Addressing, and Indexing Method, Means, and Apparatus  1000 , also referred to in embodiment Model of Everything  1000 . 
     FIG. 1  provides a reference map for the overall architecture of Model of Everything  1000 . Model of Everything  1000  is made up of six components: Unitary Reference Architecture  100 , Unitary Infrastructure  200 , Unitary Ontology Architecture  300 , Unitary Resource Description Framework (RDF)  400 , Unitary Process Architecture  500 , and Unitary Apparatus  600 . Components with sub-components and parts are individually discussed in figures that follow. 
   FIG.  2  Construction of Everything 
     FIG. 2  depicts Levels of Abstraction  202 . 2 , which is a sub-component of Dimension  202 —shown as a component of Unitary Infrastructure  200  in  FIG. 1 . Parts of Levels of Abstraction  202 . 2  are conceptual dimensions of everything;
           202 . 2 . 1  Explication     202 . 2 . 2  Aggregation     202 . 2 . 3  Organization     406 . 3  Integration     202 . 2 . 4  Synthesis     202 . 2 . 5  Resolution     202 . 2 . 6  Unification       
   To understand what anything is made of, Levels of Abstraction  201 . 2  provide iterative process steps which may be employed top-down or bottoms up, or from any level up or down. By starting with a whole, and using a top-down approach, successive divisions lead to enumeration of individual elements. 
   Conversely, starting with individual elements and a bottoms-up approach, systems are created through successive combinations until the final duality is resolved, and the whole circumscribed. 
   FIG.  3  Deconstruction of Everything 
   Levels of Abstraction  202 . 2  are used to think about what |EVERYTHING| is made of. It would be very difficult to start at the bottom and list everything without thinking in kinds. It would be impossible to know if each thing was represented without using kinds, but it would also be very difficult to list every kind without thinking in systems. And still, there is no assurance that one system or another has not been omitted altogether, so a top-down approach is used to deconstruct everything. 
   Starting at the top, the question is, what is the system identity of the model? What is the “original” a system “of”? According to Relativity  302  everything is an Event  301 . 2 , and each thing is an Event  3012 . Model of Everything  1000  is a model of All Events  201 . 6  in everything. 
   The next question is, what are labels for the top two or three main groupings in everything, such that there are no elements not in a grouping? Animal-vegetable-mineral is a common way people think about everything. More common is physical-abstract, which takes into account the domain of ideas. 
     FIG. 3  depicts everything as a continuum with All Events  201 . 6  in the center at the Integration  406 . 3  dimensional level. All Events  201 . 6  represents intersection of physical and abstract, with Mountains of Matter  201 . 1 . 7  at one extreme on top of Icebergs of Ideas  201 . 1 . 8  at the other. Everything known is a lot of things and a lot of information. But everything known is either physical or abstract and nothing known is not physical or abstract. At this first stage of deconstruction, the objective version of the model includes everything. 
   FIG.  4  Dimension of Everything 
   Then, Levels of Abstraction  202 . 2  are also used to think about what Mountains of Matter  201 . 1 . 7  and Icebergs of ideas  201 . 1 . 8  are made up of. Mountains of Matter  201 . 1 . 7 , taken as a whole, comprise Object of Everything  201 . 1 . 6 . That is all of physical reality. 
   What are labels for the top groupings in physical reality? Physical reality is organized in systems, and systems of systems. Domain Objects  201 . 1 . 5  is an inclusive term for “systems of systems” and Event System Object  201 . 1 . 4  is a label that applies to systems, which are collections of things or ideas cohered by common group label. 
   Everything could be divided into successive domain slices, but at this stage of deconstruction the names and knowledge arenas don&#39;t matter. What&#39;s needed now are terms that generalize the “kinds” of objects that form each level&#39;s divisions of everything. Event Domain Objects  201 . 1 . 5  and Event System Objects  201 . 1 . 4  apply. 
   At the center, the Integration  406 . 3  level, is the analog state of material embodiment of wholes in relative motion, each an Event  301 . 2  and altogether All Events  201 . 6 , comprising the entire complement of singular things and their organized aggregations of parts, pieces, and properties, which are represented as Event Objects  201 . 1 . 3 , and their descriptive Event Information  202 . 1 . 2 . The original relation of event object and event information is established when owners make claims that define the identity of each thing with symbols—name and unique Event Identities  201 . 1 . 1 .  FIG. 4  depicts seven universal dimensions of embodiment in Layers of Objects  201 . 1 ;
           201 . 1 . 1  Event Identities     201 . 1 . 2  Event Information     201 . 1 . 3  Event Objects     201 . 6  Events     201 . 1 . 4  Event System Objects     201 . 1 . 5  Event Domain Objects     201 . 1 . 6  Object of Everything       

   Each thing in both physical and abstract dimensions is an Event  301 . 2  in All Events  201 . 6 . Event forms represented in Model of Everything  1000  include embodiments that range from physical to abstract. At this second stage of deconstruction, the dimensional version of the model includes everything. 
   FIG.  5  Extent of Everything 
   By considering the dimensions of everything, the extent of everything may be circumscribed as scope elements shown in  FIG. 5 . Scope of Everything  201 , which consolidates dimensional terms into one set of six dimensioned levels of reality which collectively represent everything as inclusive ranges of conceptual description.
           201 . 1  All Identities     201 . 2  All Information     201 . 3  All Objects     201 . 4  All Systems     201 . 5  All Domains     201 . 6  All Events       

   In other words, every individual thing known to man could be listed as an identity, as information, as object, as system, as domain, or as event. And correlatively, there is no thing known to man or that will be known that doesn&#39;t fit under at least one of these umbrella terms. Thus, the scope of the present invention is Unitary Scope  201 , all inclusive of everything, and at this stage of deconstruction, the subjective version of the model includes everything. 
   FIG.  6  Description of Everything 
   Scope of Everything  201  labels may be further correlated with socio-political-cultural dimension as conceptual infrastructure terms as articulated in  FIG. 6 . The institutions of everything are; 
   
     
       
             
             
           
         
             
                 
             
           
           
             
               Information Reference Architecture 200.1: 
               encompasses principles of information structure, organization, 
             
             
                 
               definition of identities and constituents. 
             
             
               Civil Infrastructure 200.2: 
               encompasses principles of democracy, self-representation, 
             
             
                 
               ownership, rules, values, norms, principles and processes of 
             
             
                 
               citizenship, including original instantiation and current 
             
             
                 
               authentication. 
             
             
               Information Infrastructure 200.3: 
               encompasses language, classification, representation, media, 
             
             
                 
               devices, hardware and software. 
             
             
               Physical Infrastructure 200.4: 
               encompasses all people, property, events, places, ideas, artifacts, 
             
             
                 
               objects, assertions; everything. 
             
             
               Process Infrastructure 200.5: 
               encompasses natural systems, man-made systems, business 
             
             
                 
               methodologies, programmatic structures, functions, and tools, 
             
             
                 
               production systems, delivery systems, supply chain networks, 
             
             
                 
               media, devices, hardware and software. 
             
             
               Economic Infrastructure 200.6: 
               encompasses principles of economics, exchange systems, metrics, 
             
             
                 
               markets, financials, communication, systems, the Internet, the 
             
             
                 
               telephone system, media, devices, hardware and software. 
             
             
                 
             
           
        
       
     
   
   Infrastructure  200  components are inclusive of abstract principles and conventions that people around the world use to define semantic systems, to communicate with one another, to make and use things, and to participate in both the community and marketplace. Through multiple versions that articulate and circumscribe deeper and wider definitions, the model continues to apply to and include everything. 
   FIG.  7  Unitary Reference Architecture Components 
     FIG. 7  depicts the high-level components of Model of Everything  1000  with Unitary Reference Architecture  100 , which constitute a copy, pattern, image to be made, miniature representation, and mathematical description of analog |EVERYTHING| including all events  201 . 6 , all event domains  201 . 5 , all event systems  201 . 4 , all event objects  201 . 3 , all event information  201 . 2 , and event identities  201 . 1 . The components that make up Unitary Reference Architecture  100  are; 
   UR-URL Identifier Method  101   
   List of Everything  102   
   Table of Everything  103   
   Database of Everything  104   
   Platform for Everything  105   
   Web Portal to Everything  106   
   FIG.  8  Alignment of Scope and Components 
     FIG. 8  shows the alignment between Model of Everything  1000  components and Scope of Everything  201  elements derived according to Levels of Abstraction  202 . 2  and Layers of Objects  202 . 1 . Everything in Scope of Everything  201  is modeled in Model of Everything  1000 . 
   FIG.  9  Relation of Scope and Components 
     FIG. 9  shows Scope of Everything  201  elements from top to bottom going into Model of Everything  1000 , which is constructed from bottom to top, built on Unitary Reference Architecture  100 . 
   Unitary Infrastructure  200  components are the underlying structural members that support the overall architecture of everything. Dimensions are “rebar” that keep columns of part numbers in straight order within states. Scopes are “cross-beams” that span and connect columns to cohere components and parts across the continuum of states. 
   FIG.  10  Everything Components 
   Model of Everything  1000  components are modeled after and represent components and dimensions of everything. Model of Everything  1000  is made up of Unitary Reference Architecture  100 , Unitary Infrastructure  200 , Unitary Ontology Architecture  300 , Unitary Resource Description Framework  400 , Unitary Process  500 , and Unitary Apparatus  600 . 
   FIG.  11  Unitary Reference Architecture Components 
   Unitary Reference Architecture (URA)  100  is made up of UR-URL Identifier Method  101 , List of Everything  102 , Table of Everything  103 , Database of Everything  104 , Platform for Everything  105 , and Web Portal to Everything  105 . 
   FIG.  12  UR-URL Identifier Method Components 
   UR-URL Identifier Method  101 , also referred to as Unitary Identity Architecture and Unitary Identity, is made up of UR-URL  101 . 1 , Name  101 . 2 , Owner  101 . 3 , Authority  101 . 4 , Keywords  101 . 5 , and Path  101 . 6 . 
   UR-URL  101 . 1  is made up of unique relative referential geotemporal incept coordinates XYZT/GT asserted by makers. Correlated terms include but are not limited to: UR-URL Real Identifier  101 . 1 . 1 , XYZT/GT Incept  101 . 1 . 2 , XYZT/GT Now  101 . 1 . 3 , XYZT/GT Extension  101 . 1 . 4 , Other Extension  101 . 1 . 5 , Other Address  101 . 1 . 6 , and Other ID  101 . 1 . 7 . 
   UR-URL  101 . 1  establishes a direct association by owner-maker between real identity and real identifiers coincident with event time and location. The form of address a particular event takes, be it coordinate or postal or other, is immaterial to the fact of specificity of a distinct location in spacetime that may be converted to numerous equivalent formats. What makes the identifier work universally for everything and everyone everywhere in all time isn&#39;t simply location, as in common navigation systems, and it isn&#39;t simply time, as in common date/time stamping, and it isn&#39;t simply the combination of location and date/time. What makes UR-URL  101 . 1  work universally is the combination of location/date/time with assertion of incept identity ownership in a system of legally authenticated claims—exactly what the public domain is in analog. We could not have democracy if vendors owned citizens&#39; legal identities, yet we continue to evolve the Internet—a system of artificial identities—as though it could and will be a substitute for real analog establishments and institutions. It can&#39;t. The present invention can. 
   Point of clarification: UR-URL will work as an identifier for everything anytime anywhere in any given system, even without the principle of incept ownership or other components of Unitary Reference Architecture  100 . But the only way to make one universal system of |EVERYTHING| is with Unitary Reference Architecture which employs universal principles of private ownership and citizenship used by people and governments around the world. Officially authenticated privately controlled event identity ownership is the key to utility as one universal system of information addresses in one Model of Everything  1000 . 
   Furthermore, any prior art identifier method may be used modularly with Unitary Reference Architecture  100  components—List, Table, Database, Platform, Web Portal, Ontology, RDF—in place of UR-URLs to build a “Model of Something”. However, the resultant model can represent only a portion of |EVERYTHING| insofar as prior art identifier methods are finite combinations and can only identify as many things in |EVERYTHING | as code structure permits. 
   Name  101 . 2  is made up of alpha-numeric characters and/or symbols as asserted by makers. Correlated terms include but are not limited to: Claimed Identity Name  101 . 2 . 1 , Real Name  101 . 2 . 2 , Real Identity  101 . 2 . 3 , Named Identity  101 . 2 . 4 , Title  101 . 2 . 5 , Term  101 . 2 . 6 , Other Designation  101 . 2 . 7 . 
   Owner  101 . 3  is made up of the legal name of the entity asserting a claim to ownership of person, property, or idea. Correlated terms include but are not limited to: Claim Maker Owner  101 . 3 . 1 , Functional Owner  101 . 3 . 2 , Maker  101 . 3 . 3 , Inventor  101 . 3 . 4 , Discoverer  101 . 3 . 5 , Parent  101 . 3 . 6 , and Legal Agent  101 . 3 . 7 . 
   Authority  101 . 4  is made up of the legal name of the entity or instrument corroborating or authorizing the claim and instantiating the entity, i.e. Department of Vital Statistics authenticates and records births instantiating person entities as citizens; contract documents authorize expenditure of enterprise resources and instantiate production processes. Correlated terms include but are not limited to: Official Incept Authentication  101 . 4 . 1 , Official Authentication  101 . 4 . 2 , Official Anytime Authentication  101 . 4 . 3 , Maker Affidavit Authentication  101 . 4 . 4 , Witness Affidavit Authentication  101 . 4 . 5 , Other Legal Authentication  101 . 4 . 6 . The vital step of official authentication is missing in the current embodiment and prior art embodiments with vendor authentication. 
   Keywords  101 . 5  is made up of links to related things and ideas. Keywords  101 . 5  can be anything, including but not limited to specific individual terms concatenated in UR-URL  101 . 1 &#39;s XYZT/GT method: Coordinate Values  101 . 5 . 1 , Point of Origin  101 . 5 . 2 , Differential Quantity  101 . 5 . 3 , Latitude  101 . 5 . 4 , Longitude  101 . 5 . 5 , Elevation  101 . 5 . 6 , Time  101 . 5 . 7 , GT  101 . 5 . 8 , Other Legal Designation  101 . 5 . 9 . 
   Path  101 . 6  is made up of links to the system or parent that has conventions, protocols, and references that govern the thing or idea. The path for an information resource might be the owner&#39;s website. The path for a work center resource might be to its parent department. At a minimum, terms of reference must be specified. Correlated terms that clarify address nomenclature include but are not limited to: Referential System  106 . 1 , Parent System  106 . 2 , GPS  106 . 3 , Geo.Domain  106 . 4 , USGS  106 . 5 , Metes and Bounds  106 . 6 , Others  106 . 7 . 
   II List of Everything View—One Dimension 
   FIG.  13  List of Everything Components 
   List of Everything  102  is made up of UR-URL  101 , Tabular Architecture Rows and Columns  600 . 11 , and Infinite Range With Infinite UR-URL Identifier Method Scope  600 . 13 . 
   FIG.  14  List View 
     FIG. 14  illustrates a common list form apparatus with Tabular Architecture Rows and Columns  600 . 11 . 
   FIG.  15  List With Prior Art Reference Architecture 
     FIG. 15  illustrates a common list form with prior art reference architecture comprising an ID Number  101 . 1 . 7  which is not infinitely extensible and which does not apply to everything, depicted as Finite Range With Finite Identifier Scope  600 . 16 . Every element within a system must have a unique identifier. Size of system is limited by available combinations generated by the identifier method&#39;s code syntax. GUID has 41 characters which yields over 3E+49, or, 33,452,526,613,163,800,000,000,000,000,000,000,000,000,000,000,000 unique identifiers. That looks like a lot of identifiers, but it&#39;s still a finite number and not remotely enough for everything. 
   FIG.  16  List with Unitary Reference Architecture 
     FIG. 16  illustrates List of Everything  102 , and contrasts prior art identifier methods&#39; finite range depicted in  FIG. 15  with UR-URL Identifier Method  101  and its Infinite Range With Infinite UR-URL Identifier Method  600 . 13 . This is a fundamental distinction between the present invention and prior art lists: the capacity to enumerate everything. 
   List of Everything  102  is the most elementary expression of everything in apparatus, consisting of one infinitely extensible column containing just UR-URL  101 . 1  identifiers which define a field in “spacetime” and relate point addresses with Event Potential  302 . 7  identity. An example is List of Everything  102  with the system identity “navigation instructions” comprising a single column of executable identifiers where both locations within the defined field where the object of the instructions is scheduled to be and the time it&#39;s supposed to be there are contained in the object&#39;s UR-URL Identifier  101 . 1 . The thing, the place, the time, and sequence of events are simultaneously represented as “a path” of successive UR-URLs  101 . 1 . 
   More commonly, List of Everything would contain columns for UR-URL Identifier  101 . 1  and Name  101 . 2 , a simple binary pair. In general terms of tabular architecture, each data column represents a property or dimension held in common by all information events recorded in rows. The unique identifier column is mandatory, and not counted as a dimension. Therefore, List of Everything  102  with sequential UR-URLs  101 . 1  is apparatus in zero dimension. List of Everything  102  with UR-URL  101 . 2  and Name  101 . 2  has one dimension—Name  101 . 2 , the identity dimension, and is apparatus in one dimension. 
   III Table of Everything View—Two Dimensions 
   FIG.  17  Table of Everything Components 
   Table of Everything  103  is made up of UR-URL Identifier Method  101 , List of Everything  102 , Infinite range With Infinite UR-URL Identifier Method Scope  600 . 13 , Unitary Ontology Architecture  300 , Unitary Resource Description Framework (RDF)  400 , Commercial Off The Shelf (COTS) or Open Source Computer System  600 . 1 , Tabular Architecture Columns and Rows  600 . 11 , COTS or Open Source Spreadsheet Software With Search and Hyperlinks  600 . 5 , Variable Columns  600 . 17 , Event Data  600 . 2 . These ten parts are common where Table of Everything  103  is a component. 
   FIG.  18  Table View 
     FIG. 17  illustrates a common table form apparatus with Tabular Architecture Rows and Columns  600 . 11  and Variable Columns  600 . 17 . 
   FIG.  19  Table with Prior Art Reference Architecture 
     FIG. 19  illustrates a common table form apparatus with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , and prior art reference architecture comprising an ID Number  101 . 1 . 7  which is not infinitely extensible and which does not apply to everything, depicted as Finite Range With Finite Identifier Scope  600 . 16 . 
   FIG.  20  Table with Unitary Reference Architecture 
     FIG. 29  illustrates a table with Tabular Architecture Rows and Columns  600 . 11  and Variable Columns  600 . 17 , with Unitary Reference Architecture&#39;s UR-URL  101 , and contrasts prior art identifier methods&#39; finite range with UR-URL  101  and its Infinite Range With Infinite UR-URL Identifier Method  600 . 13 . This is a fundamental distinction between the present invention and prior art tables: the capacity to enumerate everything. 
   FIG.  21  Top-Level Ontology 
   Things in reality come in wholes and are described in terms of features and attributes, which are arranged in systems—systems of systems. A model of what exists in a system is called an ontology. The word traditionally refers to the study of existence—everything—the nature of being. Simply put, technology-wise, an ontology is the map of “kinds” in the whole system |ANYTHING|. It stipulates conceptual linkage between and across subsystems and components, and shows how everything in scope is connected and organized. Node/category names represent a particular dimension, nature, or essential property shared by sets within the system. Irreducible common denominators are called primitives or universal types. 
   Broadly speaking, ontologies tell the computer how to “know” what something “is” by suggesting associations and patterns between kinds and types so “likeness” can be reduced to math, which is the language computers speak. A computer thinks by reading lists really fast. Just as it&#39;s easier for people to find a book in the library by using the subject and author guides, so classification makes computer processing faster and more efficient. Search engines use this basic principle to measure keyword related value equivalence to rank results. On a deeper level, ontologies provide a logical basis for relating semantic concepts with programming rules so software agents can more closely simulate human reasoning processes. 
   Developing an ontology includes: 29    
   Defining the scope of constituency, what it&#39;s an ontology of; 
   Grouping the constituents in classes and subclasses; 
   Ordering the classes and subclasses in a hierarchy of categories; 
   Defining roles and properties of classes; 
   Specifying values for instances of properties. 
   When the categories and types are defined, you can create a knowledge base by listing individual elements and using the classification terms to label, organize, and cross-reference at every level of description. 
   Popular enterprise programs are based on tables and requests. Requests are operations performed on a specific dataset drawn from one or more tables. Each row in a human resource database represents a person, aka resource event object. The columns have field category names like job title, departmental assignment, pay grade, skill classification, home address and phone, and each object has specific values in its row for each of the types of information. Similarly, an inventory control database lists products, equipment, tools, materials, and other corporate assets along with descriptive fields such as capacity, location, quantity, and cost. Software operations select and manipulate these various “kinds” of data for display in reports and graphics. 
   Individual values have particular syntax that matters. If one company uses the name format “Last, First, Middle” and partners use “First Middle Last” it takes an extra step (and extra cost) to convert one or the other to match. Agreement up front—first and foremost, on the identifier method, and second, on the “pick-list” for keyword categories and types—facilitates integration. An event ontology standardizes the “kinds” and resource description framework (RDF) simplifies consistent application. Unitary Reference Architecture  100 , Unitary Ontology  300  and Unitary RDF  400  establish a common basis for common purpose. 
   Object oriented systems and their ontologies start out by dividing everything into “physical” or “abstract” groupings as the first level duality of entity condition. Unitary Ontology Architecture  300  clarifies the term “abstract” by making explicit the fact that ideas, as well as their electronic replicas, are created, discovered, and made “legally real” by human articulation, application, authentication, agreement, and public recording of artifact. In the real world, there is a significant difference between an original and a copy. 
   The largest set is not all objects or all entities. It is All Events  201 . 6 , unified, integrated, and differentiated. Everything is an Event  301 . 2 . Event condition is either Object  301 . 3  or Assertion  301 . 4 . An assertion is a claim by a maker about their person, property, principle, or transaction—the four states of event, or, event “embodiments”. Assertions are abstract ideas made concrete through declaration (a claim by one person), contract (a claim made by two or more people), or collective agreement (a statement of principle; a law, which is either theoretical or statutory; or a primitive, an elemental force or singular essence). Transaction is the assertion of performance. 
   The terms Event  301 . 2 , Object  301 . 3 , and Assertion  301 . 4  are universal, comprehensive in their plurality and singular in their extremity. Upon deconstruction, each has multiple terms of inference. Event Object  301 . 3  and Event Assertion  301 . 4  were defined on Page 47 inclusively as synonymous with generally held top-level divisions of everything, i.e. physical or non-physical, tangible or intangible, matter or mind, thing or concept, object or subject, property or agreement, etc. 
   Conditional duality is resolved by symmetry in that Event Objects  301 . 3  and Event Assertions  301 . 4  about object constituents and relations share the same identifiers and makers. 
   Unitary Top-Level Ontology  301 . 1  is made up of Events  301 . 2 . Events  301 . 2  are made up of Objects  301 . 3  and Assertions  301 . 4 . Objects are either Person  301 . 5  or Property  301 . 6 , and Assertions  301 . 4  are either Principle  301 . 7  or Transaction  301 . 8 . Everything is an Event  301 . 2 , and nothing that exists is not either Person  301 . 5 , Property  301 . 6 , Principle  301 . 7  or Transaction  301 . 8 . The model continues to apply and extend to everything. 
   FIG.  22  Event Ontology 
   Unitary Ontology  301  depicted in  FIG. 22  is derived using Levels of Abstraction  201 . 2  in a process of deconstruction. Unitary Ontology  301  includes and expands Unitary Top-Level Ontology  301 . 1 . The Primitive Entity  300 . 1  for the whole ontology, what the ontology is a system “of”, is Event  301 . 2 . An ontology of |EVERYTHING| is necessarily an event ontology. 
   The Condition  403 . 5  of an Event  301 . 2  is either Object  301 . 3  or Assertion  301 . 4 . The States  404 . 5  of Events  301 . 2 —the embodiments—are Person  301 . 5 , Property  301 . 6 , Principle  301 . 7 , and Transaction  301 . 8 . Classes  407 . 5  and Sub-Classes  300 . 2  would fit as nodes under States  404 . 5  in a larger-sized ontology map, but have been presented in tabular form to fit on one page. 
   Persons  301 . 5  are either Real  301 . 9  or Fictitious  301 . 10 . Real Persons  301 . 9  are of age and/or competent to make contracts or not, represented by Sui Juris  301 . 9 . 1  and Non-Sui Juris  301 . 9 . 2  sub-class primitives. Fictitious Persons  301 . 10  are legal entities that are not real persons, and are represented by For Profit  301 . 10 . 1  and Non-Profit  301 . 10 . 2  sub-class primitives. 
   Property  301 . 6  is Real  301 . 11 , Personal  301 . 12 , Intellectual  301 . 13 , and Public  301 . 14 . Real Property  301 . 11  is represented by Land  301 . 11 . 1  and Rights  301 . 11 . 2  sub-class primitives. Personal Property  301 . 12  is represented by Tangible  301 . 12 . 1  and Intangible  301 . 12 . 2  sub-class primitives. Intellectual Property  301 . 13  is represented by Instrument  301 . 13 . 1  and Information  301 . 13 . 2  sub-class primitives. Public Property  301 . 14  is represented by Environment  301 . 14 . 1  and Emblem  301 . 14 . 2  sub-class primitives. 
   Principle  301 . 7  is Primitive  301 . 15 , Law  301 . 16 , or Standard  301 . 17 . Primitive  301 . 15  is represented by Singularity  301 . 15 . 1  and Force  301 . 15 . 2  sub-class primitives. Law  301 . 16  is represented by Statutory  301 . 16 . 1  and Theoretical  301 . 16 . 2  sub-class primitives. Standard  301 . 17  is represented by Definition  301 . 17 . 1  and Convention  301 . 17 . 2  sub-class primitives. 
   Transaction  301 . 8  is Claim  301 . 18 , Function  301 . 19 , or Action  301 . 20 . Claim  301 . 18  is represented by Contract  301 . 18 . 1  and Declaration  301 . 18 . 2  sub-class primitives. Function  301 . 19  is represented by Operation  301 . 19 . 1  and Office  301 . 19 . 2  sub-class primitives. Action  301 . 20  is represented by Act  301 . 20 . 1  and Obligation  301 . 20 . 2  sub-class primitives. 
   Prior art ontologies&#39; top-level system identity is most often “entity” so the ontology is a system of “entities” and everything within the system is an instance of “entity”. The computer world is object-oriented, based on the principles of information systems. Digitization is an abstraction itself. The computer world begins an entire dimension away from real. In digital terms, an object is an entity and a person is an object. Not so in the real world and not so at the higher level of Unitary Ontology, which is based on the higher combination of the principles of information systems and the principles of private ownership and citizenship and the principles of relativity. 
   The present invention must necessarily begin at the higher level, “event”. Everything is really an event. Everything is not really an entity. By moving up a level of abstraction, Unitary Ontology  301  comes into the real world and provides superordinate primitive terms for the real-world dimension of formal instantiation of entity that is integral to real identity—to citizenship, participation in the economy, self-representation. 
   In the real world, a baby is not a citizen—not a real entity with legal status—until incept (birth) is claimed by makers (parents), authenticated by witness (usually the hospital) and officially recorded in the public rolls. In the top-levels of description of everything, the terms “condition” and “state” and “class” correspond to legal definitions of rights and responsibilities. This vital first instantiation step in the information life-cycle of the real world is missing in object ontologies and in prior art identification and description schemas. Unitary Ontology  301  is an ontology of everything in the real world and in the information world. 
   FIG.  23  Relative Event Ontology 
   The Statement of Principle  302 . 8  and design specification for a whole-system information model are derived from the following excerpt from Einstein&#39;s Theory of Relativity 24 :
         “Every description of the scene of an event or of the position of an object in space is based on the specification of the point on a rigid body (body of reference) with which that event or object coincides. This applies not only to scientific description, but also to everyday life.”
 
The present invention interprets this statement to mean every event description has six basic elements:
   1. Point  302 . 2  (the actual thing, or entity that “has” the objects in relation);   2. Reference-Body  302 . 6  (the standard, or “known” point of origin to measure “from,” the governing constraints);   3. Observer  302 . 3  (everything is relative to the observer);   4. Position  302 . 1  (the mathematical coordinates of the point&#39;s location relative to the reference body);   5. Scene  302 . 5  (objects and assertions about object constituents and relations);   6. Specification  302 . 4  (explicit or detailed statement of legal particulars).       

   These groupings are herein considered primitives, or elementary classes in an ontological framework. Things and ideas—entities, objects and artifacts, real and virtual, animate and inanimate—have all six event elements; Scene  302 . 5  is all inclusive of event constituents  405 , resources  407 , and relations  408 . 
   Event Potential  302 . 7  represents that state of being between conception and actualization, and all that exists are points without description—available UR-URL  101 . 1  identity-identifier-addresses without objects. In order for UR-URL  101 . 1  or any identifiers to be associated with points/objects, there have to be the other four elements. There has to be a position, which is a coordinate differential in three vector dimensions—latitude, longitude, and elevation; there has to be a reference-body to measure the coordinates “from”; there has to be an entity doing the measuring and naming; and the measurer-namer has to “specify” details of event properties. 
   Fewer than six terms may be used to describe |EVERYTHING| where two or more terms are identical, such as in a private system where owner, authority, and user are one and the same entity, and in cases where it is not necessary to repeat parameters set at the system level, such as path where all objects in a system share the same path. 
   Relative Ontology  302  depicts the universal generic structure of an event system. Relative Ontology  302  terms circumscribe the entire range of “kinds” of information all event objects and all event systems are comprised “of” and forms the principled premise for Unitary Resource Description Framework  400 . 
   FIG.  24  Entity Ontology 
   Top-Level Ontology  303 , detailed in John F. Sowa&#39;s  2000  book, “Knowledge Representation,” 30  defines categories, subcategories, types, and subtypes for entity objects and processes in a hierarchical construct with no redundancy. Category names are designed to be used as unique type labels in predicate calculus and are “[ . . . ] defined in terms of the role and the relation Has.” 30  This is machine-readable logic built into the words. The specification is available for download and the intent is for businesses to use these labels for classifying information assets. When they do, everything will match from the inside out. Entity Ontology  303  primitive terms are:
           303 . 1  Term.Entity ( )=T.     303 . 2  Term. T  ( ).     303 . 3  Term.independent (I).     303 . 4  Term.Relative (R).     303 . 5  Term.Mediating (M).     303 . 6  Term.Physical (P).     303 . 7  Term.Abstract (A).     303 . 8  Term.Actuality (IP)=Independent∩Physical.     303 . 9  Term.Form (IA)=Abstract∩Independent.     303 . 10  Term.Prehension     303 . 11  Term.Proposition (RA).     303 . 12  Term.Nexus (MP)=Physical∩Mediating.     303 . 13  Term.Intention (MA)=Abstract∩Mediating.     303 . 14  Term.Continuant (C).     303 . 15  Term.Occurrent (O).     303 . 16  Term.Object (IPC)=Actuality∩Continuant.     303 . 17  Term.Process (IPO)=Actuality∩Occurrent.     303 . 18  Term.Schema (IAC)=Form∩Continuant.     303 . 19  Term.Script (IAO)=Form∩Occurrent.     303 . 20  Term.Juncture (RPC)=Prehension∩Continuant.     303 . 21  Term.Participation (RPO)=Prehension∩Occurrent.     303 . 22  Term.Description (RAC)=Proposition∩Continuant.     303 . 23  Term.History (RAO)=Proposition∩Occurrent.     303 . 24  Term.Structure (MPC)=Nexus∩Continuant.     303 . 25  Term.Situation (MPO)=Nexus∩Occurrent.     303 . 26  Term.Reason (MAC)=Intention∩Continuant.     303 . 27  Term.Purpose (MAO)=Intention∩Occurrent.     303 . 28  Term.Absurdity (IRMPACO)=⊥.     303 . 29  Term.Intermediate Category     303 . 30  Central Category       

   FIG.  25  Object Ontology 
   The IEEE 31  Suggested Upper Merged Ontology (SUMO)  304 , a proposed open standard ontological framework and the collaborative result of some of the best thinkers in the Internet world, is shown in part in  FIG. 25 . It is linked to Sowa&#39;s Top-Level Ontology  303 , subordinate in position, and picks up with object ontology where Sowa&#39;s entity ontology leaves off. 
   Sevcenko&#39;s 32  free online SUMO Browser  304  offers SUMO Term Search  304 . 1  and displays derivative concepts in easy-to-read tree diagrams shown as SUMO Search Results  304 . 2 , permitting quick selection of lowest common terms. All the average everyday person needs to know is where to find them. Additionally, John Sowa&#39;s website 30  has extensive documentation about concepts, design principles, and, particularly helpful, detailed explanations of the math. Copies of relevant portions are included with cited reference volumes. 
   It would be impossible herein to do justice to Sowa&#39;s sophisticated and elegant approach to knowledge representation, and if what you want is interoperability, this system has widespread support. Custom codes can be incorporated and it&#39;s built for expansion, extensible to any level of detail, metatag and beyond. However, any and all categories and types can be “had” in a Model of Everything  1000 . The intent of Unitary Ontology  301  is to stipulate an all-inclusive instantiating construct within which any number of classification systems may be usefully employed. Unitary Ontology provides primitive designations for legitimizing condition, class, state, and form. For categories and types, the Sowa Top-Level Ontology  303  and IEEE Suggested Upper Merged Ontology  304  represent industry best practices and provide primitive category labels for entities and objects, both physical and abstract, from planets to quantum theory. 
   FIG.  26  Ontology of Origination 
   Unitary Ontology Architecture  300  must extend to all aspects and dimensions of being or it wouldn&#39;t be |EVERYTHING|. This necessitates incorporating provision for belief systems, which are entered as assertions by makers. Ontology of Being  305  shows Eddy&#39;s construct 33 , Infinite Mind and Its Infinite Manifestation, represented by synonymous primitives: Principle  305 . 1 , Mind  305 . 2 , Soul  305 . 3 , Spirit  305 . 4 , Life  305 . 5 , Truth  305 . 6 , Love  305 . 7 , and further described as All Knowing  305 . 8 , All Acting  305 . 9 , All Seeing  305 . 10 , All Being  305 . 11 , All Wise  305 . 12 , All Loving  305 . 13 , Eternal  305 . 14 , All Substance  305 . 15 , Intelligence  306 . 16 . These terms represent the constituents and relations of being. Ontology of Being  305  provides neutral and flexible primitive classification labels that bridge the space between seen and unseen, what we can touch and what we believe. 
   FIG.  27  Ontology of Dimension 
   Young&#39;s construct 34 , Ontology of Dimension—Four Levels of Reality  306 , divides everything into four dimensions: I. Purpose  306 . 1 , II. Value  306 . 2 , III. Concept  306 . 3 , and IV. Matter  306 . 4 . 
   FIG.  28  Ontological Integration 
   The composite in  FIG. 37 , Integrated Ontology  307 , aligns primitive sections from four separate sources. Alone, each depicts the author&#39;s complete view of everything in reality. The superordinate level inclusively represents the nature of being and progress as defined by Eddy  305 . Unitary Identity Architecture  101  precedes Relative Ontology  302  illustrated in the next section, and Unitary Ontology  301  in the middle. The next latticework is a rendering of the Sowa Top-Level Ontology  303  for all-purpose object entity description. SUMO  306  and expanding derivatives are referenced but not shown. Sowa/SUMO are together considered one ontology. Each node has a word that signifies an extensible high-order category/type/subtype. 
   In addition to establishing legitimacy corresponding to analog instantiation, artifacts, and instruments, the further purpose of Unitary Ontology  301  is to provide evidence that the domain |EVERYTHING|, as defined herein, and claimed by the present invention, is indeed inclusive and extends to everything known. No other method claims all events, which if you agree with Einstein, is everything. No other method claims all objects and all assertions, which is everything if you use common non-relativistic definitions. Together, these four unique and complementary ontologies comprise an all-encompassing set of general summary-level category codes/labels for our many diverse claims and agreements about individual and collective human experience. 
   The components of Integrated Ontology  307  are Ontology of Being  305 , Relative Ontology  302 , Unitary Ontology  301 , Entity Ontology  303 , Object Ontology  304 , and Unitary Reference Architecture  100 . 
   FIG.  29  Dimensional Integration 
   Young&#39;s Ontology of Dimension  306  is overlaid Integrated Ontology  307  to create Dimensioned Integrated Ontology  308 . There is alignment between constructs, which indicates model coherence at fundamental levels. 
   FIG.  30  Alignment Between Primitive Terms 
   The present invention, Model of Everything With UR-URL Identity, Identifier, Addressing, and Indexing Method, Means, and Apparatus, can identify, address, index and integrate in an information table every molecular constituent of every cell of every person, place, and thing on the planet. The present invention can also include every idea ever claimed by anyone in all time. In terms of detail, how much is enough and how much is too much? 
   Enough is a function of purpose. Too much has consequences for privacy. The burning question today, in terms of the Internet and web service, is, “What kinds of information are needed to describe things well enough for discovery?” “Well enough” depends on who&#39;s looking and what&#39;s being described. Business needs to align transaction data formats for supply chain partnership automation. When it&#39;s business being described, “well” is a matter of common interest in specific fields and codes. But when it&#39;s people, “enough” more often than not means nothing at all. We&#39;d just as soon nobody knew anything about us. The fact of the matter remains, the end product of industry efforts to standardize the “kinds” of information they exchange will be a set of basic templates that specify how information about private citizens is collected and used. The kinds matter a lot. 
   Privacy isn&#39;t about “trust providers” protecting private information; it&#39;s about their not owning and controlling it in the first place. We should be asking, “What are the critical kinds of information we want vendors to share with each other about us and our property?” The kinds have both legal and personal ramifications. For this reason, and because quantity doesn&#39;t mean quality, just higher cost and longer wait times, Unitary Technology reframes the inquiry to, “How little is adequate?” 
   All information winds up in tables with columns and rows, so the answer boils down to the labels that should be in the columns—labels that, in order to be universal, have to apply to and describe each thing in |EVERYTHING| in sufficient detail so as to differentiate it from everything else. “Resource Description Framework” refers to the particular selection of terms as column labels in the Tabular Architecture Rows and Columns  600 . 11  “columns”. 
   Alignment between standard primitive ontological constructs in Resource Description Synthesis  409  suggests common column label RDF requirements for event description and discovery. Relative Ontology&#39;s  302  six components map to our analog  413  minimum terms for valid contract, the norm for authenticating identity of person and property. There is commonality with John F. Sowa&#39;s Top-Level Categories  303 , and there&#39;s a parallel with standard programming n-tuple logic  411 . In aggregation, they point to six basic ingredients in all event objects—URA Terms 101. 
   Relative Ontology  302  primitives are: Position  302 . 1 , Point  302 . 2 , Observer  302 . 3 , Specification  302 . 4 , Scene  302 . 5 , and Reference-Body  302 . 6 . Analog primitives are Address, Name, Maker(s), Contract/Artifact, Claim(s), and Witness  101 . 4 . 5 . Sowa primitives are Proposition  303 . 11  Actuality  303 . 8 , Prehension  303 . 10 , Intention  303 . 13 , Nexus  303 . 12 , and Form  303 . 9 . Logic  411  primitives are ID  101 . 1 . 7 , Bearer  411 . 1 , Normative Agent  411 . 2 , Condition of Obligation  411 . 3 , Obligation  411 . 4 , and Sanction  411 . 5 . ERP  412  primitives are ID  101 . 1 . 7 , Name  101 . 2 , Functional Owner  101 . 3 . 2 , Work Order/Statement of Work  412 . 1 , Resources  405  and Relations  408 , and System  406 . 
   Considered in concert, like terms from the several ontologies are synthesized conceptually in Unitary Resource Description RDF Array  400 : Identifier  401 , Identity  402 , Origin  403 , Agreement  404 , Constituents  405 , and System  406 . Then, RDF Array  400  terms are reduced to simplest common user-friendly Unitary Reference Architecture  101  terms: UR-URL  101 . 1 , Name  101 . 2 , Owner  101 . 3 , Authority  101 . 4 , Keyword  101 . 5 , and Path  101 . 6 . 
   The answer to the question, what kinds of information are needed to describe things well enough for discovery, is, not much—six things, as indicated by Relative Ontology  302  and transformed to common terms Unitary RDF  400  in Resource Description Synthesis  409 . However, subdividing constituent into keyword profile, and activity more closely matches enterprise planning. 
   The sum total of enterprise assets is a list of resources—things. The objective of business is to leverage human capital assets with intellectual property assets in combination with real and personal property assets following policy, procedure, and process assets to make other things that are worth more in combination than alone. 
   Business has resources  407 . Business has activity  408 . 1 . Activity  408 . 1  is the assertion of relation between resources. Activity  408 . 1  is an event  301 . 2  and a system  406  and an object  301 . 5  with incept and constituents relating. Just another line item in an enterprise model of Model of Everything  1000 . Resources  407  are resources  407 , regardless of state  404 . 5 . They all have the same basic kinds of descriptive elements. Differences are all situational. That is, event conditions differ, but when all&#39;s said and done, each thing is a system and is in a system. All event objects  201 . 1 . 3  and event systems  201 . 1 . 4  share six common primitive terms. 
   Keyword  101 . 5  is a more common term than Constituent  405 , and can refer to anything, including Profile  407  and Activity  408 . 1 . They can all be in the same column, but it&#39;s useful to see three groupings. What business needs is a list of resources with common RDF in a table that can be queried—an enterprise Table of Everything  103 . 
   FIG.  31  Matrix of Ontological Terms 
   Synthesis of ontological constructs produced RDF Array  400 , which is further considered in Resource Description Matrix  410 , where the terms of Unitary Resource Description Framework  400  are arrayed in five cross-sections that bring out particular facets of application as high-order ontological primitive labels for the many dimensions of |EVERYTHING|: Expression  400 . 5 , Aspect  400 . 4 , Purpose  400 . 3 , Set  400 . 2 , and Logic: Has  400 . 1 . 
   
     
       
             
             
           
         
             
                 
             
           
           
             
               The Expressions 400.5 of Unitary RDF 400 are: 
               Address 401.5, Element 402.5, Condition 403.5, State 404.5, 
             
             
                 
               Category 405.5, Domain 406.5, Class 407.5, Union 408.5. 
             
             
               The Aspects 400.4 of Unitary RDF 400 are: 
               Uniqueness 401.4, Representation 402.4, Inception 403.4, 
             
             
                 
               Legitimacy 404.4, Composition 405.4, Orientation 406.4, 
             
             
                 
               Eligibility 407.4, Context 408.4. 
             
             
               The Purposes 400.3 of Unitary RDF 400 are: 
               Differentiation 401.3, Designation 402.3, Ownership 403.3, 
             
             
                 
               Instantiation 404.3, Classification 405.3, Integration 406.3, 
             
             
                 
               Utilization 407.3, Operation 408.3. 
             
             
               The Sets 400.2 of Unitary RDF 400 are: 
               Record 401.2, Register 402.2, Ontology 403.2, Concordance 
             
             
                 
               404.2, Taxonomy 405.2, Architecture 406.2, Pool 407.2, 
             
             
                 
               Model 408.2. 
             
             
               The Logic: Has 400.1 with Unitary RDF 400: 
               Has UR-URL 401.1, Has Name 402.1, Has Owner 403.1, Has 
             
             
                 
               Authority 404.1, Has Keyword 405.1, Has Path 406.1, Has 
             
             
                 
               Profile 407.1, Has Activity 408.1. 
             
             
                 
             
           
        
       
     
   
   FIG.  32  Ontology of Everything 
   Unitary Integrated Ontology  309  arrays Unitary RDF  400  terms and Expressions  400 . 5  against the combined components of Integrated Ontology  307  to illustrate top-to-bottom applicability from the highest order abstract concepts and event incept origination and instantiation all the way through entity categories to object forms, both physical and abstract. There is a primitive for everything and no thing exists that has no primitive. Unitary Integrated Ontology  309  is an ontology of |EVERYTHING| and demonstrates universal inclusion. 
   Asterisks note supplementary headers that align with titles and add symmetry and coherence to the illustration. Every effort was made to ensure no terms overlap between ontologies, and that unitary terms correspond with commonly accepted legal definitions. The intent and design of Unitary Ontology Architecture  300  is that the final construct have no redundancy, and as depicted herein, labels are unique across the ontologies integrated. 
   FIG.  33  Table with Unitary Resource Description Framework (RDF) 
     FIG. 32  illustrates a table with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , Infinite Range With Infinite UR-URL Identifier Method  600 . 13 , and List of Everything  102 , with Unitary Resource Description Framework  400  in six terms of UR-URL Identifier Method  101 : UR-URL  101 . 1 , Name  101 . 2 , Owner  101 . 3 , Authority  101 . 4 , Keyword  101 . 5 , and Path  101 . 6 , as might be used in a public domain context. 
   FIG.  34  Table with Extended Unitary Resource Description Framework (RDF) 
     FIG. 34  illustrates a table with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , Infinite Range With Infinite UR-URL Identifier Method  600 . 13 , List of Everything  102 , with extended Unitary Resource Description Framework  400  in eight terms of UR-URL Identifier Method  101 : UR-URL  101 . 1 , Name  101 . 2 , Owner  101 . 3 , Authority  101 . 4 , Keyword  101 . 5 , Path  101 . 6 , Profile  101 . 7 , and Activity  101 . 8 , as might be used in an enterprise context. 
   FIG.  35  Table with Simple Unitary Resource Description Framework (RDF) 
     FIG. 35  illustrates a table with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , Infinite Range With Infinite UR-URL Identifier Method  600 . 13 , and List of Everything  102 , with Simple Unitary Resource Description Framework  400  in four terms of UR-URL Identifier Method  101 : Name  101 . 2 , Keyword  101 . 5 , and Path  101 . 6 , as might be used in a private context where owner and authority are one and the same as the user and it is not necessary to duplicate entries. 
   FIG.  36  Table with Unitary Reference Architecture, Ontology, (RDF), Hardware and Software 
     FIG. 36  illustrates Table of Everything  103  with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , Infinite Range With Infinite UR-URL Identifier Method Scope  600 . 13 , List of Everything  102 , Unitary Ontology Architecture  300 , Unitary Resource Description Framework  400 , UR-URL Identifier Method  101 , COTS or Open Source Computer System  600 . 1 , COTS or Open Source Spreadsheet Software With Search and Hyperlinks  600 . 5 , and Event Data  600 . 2 , altogether comprising Table of Everything  103 . Table of Everything  103  is apparatus in two-dimensions. 
   While Model of Everything  1000  may be constructed using old-fashioned analog media, the addition of COTS or Open Source Spreadsheet Software With Search and Hyperlinks  600 . 5  expands the utility of Table of Everything  103 . The following definitions of the term “table” explain additional functionality: 
   Tables as features offered by application programs 28  
         Traditionally, the most familiar media for creating and storing tables have been pen and paper. Given the proliferation of computers at home and in the workplace, computer representations of “paper tables” have become widespread. Common software applications give users the possibility of generating, manipulating, and editing both table data and table formats with ease. Such applications include: word processing applications; Desktop publishing software; spreadsheet applications; presentation software; and tables specified in HTML or another markup language.       

   Tables as techniques used in programming computers 28  
         Data tables are used extensively in computers, in forms as diverse as equal-sized and consecutive blocks of memory locations, on one hand, and “scatter-storage” schemes relying on what are more conventionally known as hash functions, on another. Each is a distinct data structure in computer science.       

   Spreadsheet 28  
         A spreadsheet is a rectangular table (or grid) of information       

   Table of Everything  103  may be created in common commercial spreadsheet programs such as Excel and Lotus 1-2-3. Each row of Table of Everything  103  contains a record for one thing, and columns contain terms for each thing according to the column labels. Terms are also “things” with their own records, which are connected by hyperlink. Thus, every term in every column represents either a value or a link to that term&#39;s identity record in Table of Everything  103 . 
   IV Database of Everything View  3   
   FIG.  37  Database of Everything Components 
   The components of Database of Everything  104  are: UR-URL Identifier method  101 , Table of Everything  103 , Variable Relational Tables  600 . 15 , COTS or Open Source Computer System  600 . 1 , COTS or Open Source Database Software  600 . 6 , Infinite Integration With UR-URL Identifier Method Scope  600 . 12 . Database of Everything  104  contains Table of Everything  103 , but individual Table of Everything  103  parts included are not called individually. 
   FIG.  38  Database View 
     FIG. 38  illustrates a common database form apparatus with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , and Variable Relational Tables  600 . 15 . 
   FIG.  39  Database with Prior Art Reference Architecture 
     FIG. 39  illustrates a common database form apparatus with Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , Variable Relational Tables  600 . 15 , with prior art reference architecture comprising an ID Number  101 . 1 . 7  which is not infinitely extensible and which does not apply to everything, depicted as Finite Range With Finite Identifier Scope  600 . 16 , and which is not infinitely integrateable, depicted as Finite Integration With Finite Identifier Scope  600 . 14 . 
   FIG.  40  Database with Unitary Reference Architecture 
     FIG. 40  illustrates a common database form apparatus with List of Everything  102 , Table of Everything  103 , Unitary Ontology Architecture  300 , Unitary RDF  400 , Tabular Architecture Rows and Columns  600 . 11 , Variable Columns  600 . 17 , Variable Relational Tables  600 . 15 , with Unitary Reference Architecture&#39;s UR-URL  101 , and contrasts prior art identifier methods&#39; finite range with UR-URL  101  and its Infinite Range With Infinite UR-URL Identifier Method  600 . 13  and Infinite Integration With UR-URL Identifier Method  600 . 12 . This is a fundamental distinction between the present invention and prior art databases: the capacity to enumerate everything. A database with Unitary Reference Architecture  100  is a Database of Everything  104 . 
   FIG.  41  Database with Unitary Reference Architecture, Hardware and Software 
     FIG. 41  illustrates Database of Everything  104  components depicted in  FIG. 40  with the addition of COTS or Open Source Computer System  600 . 1 , COTS or Open Source Database Software  600 . 6 , and Event Data  600 . 2 . Spreadsheet Software With Search and Hyperlinks  600 . 5  is also shown and may be used optionally instead of database software since, as described in the definitions below, works much the same way. 
   Row (database) 28  
         In the context of a relational database, a row represents a single, implicitly structured data item in a table. For example, in a table that represents companies, each row would represent a single company; in a table that represents the association of employees with departments, each row would associate one employee with one department.   The implicit structure of a row, and the meaning of the data values in a row, requires that the row be understood as providing a succession of data values, one in each column of the table. The row is then interpreted as a relation variable composed of a set of tuples, with each tuple consisting of the two items: the name of the relevant column and the value this row provides for that column.   Each column expects a data value of a particular type. For example, one column might require a unique identifier, another might require text representing a person&#39;s name, another might require an integer representing hourly pay in cents.       

   Column (database) 28  
         In the context of a relational database, a column of a table is a set of data values of a particular simple type, one for each row of the table. The columns provide the structure according to which the rows are composed. For example, a table that represents companies might have the following columns: ID (integer identifier, unique to each row); Name (text); Address line 1 (text); Address line 2 (text); City (integer identifier, drawn from a separate table of cities, from which any state or country information would be drawn); Postal code (text); Industry (integer identifier, drawn from a separate table of industries); etc. Each row would provide a data value for each column and would then be understood as a single structured data value, in this case representing a company. More formally, each row can be interpreted as a relative variable, composed of a set of tuples, with each tuple consisting of the two items: the name of the relevant column and the value this row provides for that column.       

   Database of Everything  104  is an apparatus with tabular architecture containing rows of object identity records with corresponding columns of universal Unitary RDF  400  data fields containing terms and values specific to each object and relative to the Unitary RDF  400 , and classified by Unitary Integrated Ontology  309 . Terms are also objects in selfsame Database of Everything  104  with original “term object” identity records that are also classified with primitive ontological terms drawn from Unitary Integrated Ontology  309 . 
   Database of Everything  104  may be created in common commercial spreadsheet and database programs such as Excel, Lotus 1-2-3, dBase, and Access. These programs have basic tabular architecture  600 . 11  and feature search, hotlink, and other programmatic functionality. Unitary RDF  400  terms in columns represent primitive identities with links to individual term identity records, thus a Database of Everything  104  in a spreadsheet/database program is a searchable inventory of information object identities corresponding to analog objects and assertions in one cross-referenced matrix of everything. Database of Everything  104  is apparatus in three dimensions. 
   V Platform for Everything View  4   
   View  4  presents Unitary Process Architecture  500  descriptions, beginning with examples of programmatic functionality, and concluding with process flow diagrams that illustrate application of Unitary Technology in the overall socio-political-economic context of access to information services and resources in the global electronic marketplace. 
   FIG.  42  Platform for Everything Components 
   Components of Platform for Everything  105  are: UR-URL Identifier Method  101 , Database of Everything  104 , Shell  600 . 4 , Unitary Shell  601 , COTS or Open Source Shell Software With Simple Tools  600 . 7 , COTS or Open Source Predicate Logic Software  600 . 8 . 
   FIG.  43  Platform View 
     FIG. 43  illustrates a common shell apparatus  600 . 4  with several shells open. Shells are convenient utility platforms that facilitate simple code writing with various popular COTS or Open Source scripting languages and object oriented approaches. A shell is a flexible and versatile canvas that when used in tandem with UR-URL Identifier Method  101  and Database of Everything  104 , along with Computer System  600 . 1 , COTS or Open Source Shell Software With Simple Tools  600 . 7 , and COTS or Open Source Predicate Logic Software  600 . 8 , becomes a powerful programmatic tool. Terms are defined: 
   Ontology 30  
         The subject of ontology is the study of the categories of things that exist or may exist in some domain. The product of such a study, called an ontology, is a catalog of the types of things that are assumed to exist in a domain of interest D from the perspective of a person who uses a language L for the purpose of talking about D. The types in the ontology represent the predicates, word senses, or concept and relation types of the language L when used to discuss topics in the domain D. An uninterpreted logic, such as predicate calculus, conceptual graphs, or KIF, is ontologically neutral. It imposes no constraints on the subject matter or the way the subject may be characterized.   By itself logic says nothing about anything but the combination of logic with an ontology provides a language that can express relationships about the entities in the domain of interest. [Emphasis added.]       

   N-tuple 28  
         In mathematics, a tuple is a finite sequence of objects (a list of a limited number of objects). (An infinite sequence is a family.) Tuples are used by mathematicians to describe mathematical objects that consist of certain components.       

   Usage in computer science 28  
         In computer science (especially in programming languages and database theory such as the relational model) a tuple is usually defined as a finite function that maps field names to a certain value. Its purpose is the same as in mathematics, namely to indicate that a certain entity or object consists of certain components and/or has certain properties. In programming languages tuples are used to form data structures.       

   Programming language is defined: 28  
         A programming language or computer language is a standardized communication technique for expressing instructions to a computer. It is a set of syntactic and semantic rules used to define computer programs. A language enables a programmer to precisely specify what data a computer will act upon, how these data will be stored/transmitted, and precisely what actions to take under various circumstances.       

   Spreadsheet programming 28  
         Just as the early programming languages were designed to generate spreadsheet printouts, programming techniques themselves have evolved to process tables (=spreadsheets=matrices) of data more efficiently in the computer itself. A spreadsheet program is designed to perform general computation tasks using spatial relationships rather than time as the primary organizing principle. Many programs designed to perform general computation use timing, the ordering of computational steps, as their primary way to organize a program.   In a spreadsheet, however, a set of cells is defined, with a spatial relation to one another. In the earliest spreadsheets, these arrangements were a simple two-dimensional grid. Over time, the model has been expanded to include a third dimension, and in some cases a series of named grids. The cells are functionally equivalent to variables in a sequential programming model. References between cells can take advantage of spatial concepts such as relative position and absolute position, as well as named locations, to make the spreadsheet formulas easier to understand and manage.   Many of the concepts common to sequential programming models have analogues in the spreadsheet world.       

   Basic 28  
         The idea behind object-oriented programming is that a computer program is composed of a collection of individual units, or objects, as opposed to a traditional view in which a program is little more than a list of instructions to the computer. Each object is capable of receiving messages, processing data, and sending messages to other objects. In this way, messages can be handled, as appropriate, by one chunk of code or by many in a seamless way.   In OOP, objects are simple, self contained and easily identifiable. This modularity allows the program parts to correspond to real aspects of the problem and thereby to model the real world. Object-oriented programming often begins from a written statement of the problem situation. Then by a process of inserting objects or variables for nouns, methods for verbs and attributes for adjectives, a good start is made on a framework for a program that models, and deals with, that situation.   According to the object-oriented principles, the verb is attached to the object and logic associated to the requirement is handled in the object. The paradigm of OOP is essentially not that of programming but one of design. A system is designed by defining the objects that will exist in that system, the code which actually does the work is irrelevant to the object, or the people using the object, due to encapsulation.       

   The architecture of Model of Everything  1000  facilitates easy use of basic object-oriented programming functionality, and is ideally suited for simple predicate logic tools and applications. In addition to internal cross-referencing by hotlink: 1) links from one object&#39;s value term to that term&#39;s identity object record, 2) links between terms and terms; 3) and links between objects and objects, there is also a built-in internal link through Unitary Integrated Ontology to predicate logic constructions. Logic provides the semantic basis, and UR-URL Identifiers  101 . 1  provide the terms inserted into logical forms as relation variables. 
   Database of Everything  104 , which “goes into” Platform for everything  105 , is a table with resources in rows and what they “have” in columns. Possession is the relation represented in a system of ownership, i.e. owner has object, object has keywords, resource has role. The symbol ∩ means “intersection” or “has.” 
   Table 2 shows sample “Has Category” fields that might be used in an enterprise information asset management event system database. Each superclass represents a union set [Identifier ∩ Set (Code, Value) (Code, Value) . . . ] where codes are class, category, and type labels drawn from the ontology and values are object-specific properties and attributes.
         Each record has a pair of values in each essential field, and as many other category/value pairs as desired.   Keyword, profile, and activity fields can have any combination of constituent codes and values (or one field vs. three).   Constraints and relationships are inherited from parent/path.   System and code definitions are listed objects with UR-URLs; codes link to definitions—everything&#39;s a link.   Objects are entities with constituents, and also constituents themselves in larger event system objects.   An activity is entered as a new event record that “has” resources in roles—people, property, and processes.   Updates are “has” functions that generate event links with new instances of codes and values for resources used.   Each resource has a UR-URL; old identifiers and codes are listed constituents.   Codes may be entered in series [Identifier ∩ (Code, Value, Value, Value . . . )].   Code pairs too [Identifier ∩ (Code, Value) (Code, Value)] and [Identifier ∩ (UR-URL,UR-URL) (UR-URL,UR-URL)].   Shorthand activity programming—use the schedule to embed due date/time right in planned activity identifiers.   Fields may contain any combinations of codes and values.   Codes link to code definitions, which are listed resources.   Values link to other listed resources or contain literal strings.       

   
     
       
             
           
             
             
             
             
             
             
             
             
           
         
             
               TABLE 2 
             
           
           
             
                 
             
             
               Sample Event Function Set Options 
             
           
        
         
             
               ∩ Name 
               ∩ Owner 
               ∩ Authority 
               ∩ Class 
               ∩ Constituent 
               ∩ Process 
               ∩ SysParent 
               ∩ UR-URL 
             
             
                 
             
             
               ∩ NameLast 
               ∩ OwnerLink 
               ∩ AuthorityLink 
               ∩ Form 
               ∩ Component 
               ∩ Obligation 
               ∩ SysChild 
               ∩ X-UR-URL 
             
             
               ∩ NameFirst 
               ∩ 
               ∩ State 
               ∩ Office 
               ∩ Feature 
               ∩ Role 
               ∩ SysReference 
               (Real Relative) or 
             
             
                 
               EntityCondition 
             
             
               ∩ 
                 
               ∩ Statement 
               ∩ Utility 
               ∩ Property 
               ∩ Relation 
                 
               (Referential-Ext) 
             
             
               NameMiddle 
             
             
               ∩ Symbol 
                 
                 
               ∩ Capacity 
               ∩ Attribute 
               ∩ Action 
                 
               ∩ InceptLocDateTime 
             
             
               ∩ Alias 
                 
                 
               ∩ AccessRule 
               ∩ Characteristic 
               ∩ Predicate 
                 
               ∩ NowLocDateTime 
             
             
               ∩ Icon 
                 
                 
               ∩ Performance 
               ∩ Quality 
               ∩ Operation 
                 
               ∩ PartNumber 
             
             
                 
                 
                 
               ∩ KeyCategory 
               ∩ Quantity 
               ∩ Argument 
                 
               ∩ ProductCode 
             
             
                 
                 
                 
                 
               ∩ Association 
               ∩ Predecessor 
                 
               ∩ Identifier 
             
             
                 
                 
                 
                 
               ∩ Possession 
               ∩ Successor 
                 
               ∩ Address 
             
             
                 
                 
                 
                 
               ∩ Image 
               ∩ Vector 
                 
               ∩ AddressCode 
             
             
                 
                 
                 
                 
               ∩ Graph 
               ∩ Function 
             
             
                 
             
           
        
       
     
   
   Furthermore, just as programmatic functionality accrues to a spreadsheet where “a set of cells is defined with a spatial relation to one another” (per definition of “Spreadsheet Programming”), so UR-URLs are defined not with just spatial relation within the tabular structure of the spreadsheet, but also ontological relation within the Unitary RDF  400  structure, and spatio-temporal relation within the UR-URL Identifier&#39;s  101 . 1  XYZT/GT structure itself. UR-URLs “are functionally equivalent to variables in a sequential programming model” and can be used as such. UR-URL Identifiers  101 . 1  serve as external executable hotlinks that can invoke identity object terms. 
   And, abstracting the definition of “programming language” as given, UR-URLs are a programming language. In a modular sub-version Model of Everything  1000  with the system identity “Software Authoring Program”, everything that software authoring program is “made of”, from the highest domain groupings to lowest granular object, has a record with six descriptive terms and UR-URL. 
   “Programming Language” is just one of the many domains of “Software Authoring Program” which is in the larger domain “Operating System”. Every term in the whole system has a record and UR-URL. Every “standardized communication technique for expressing instructions to a computer” has a record and UR-URL. Every “set of syntactic and semantic rules used to define computer programs” has a record and UR-URL. “Programmers can precisely specify what data a computer will act upon” by specifying UR-URLs for the “data”, UR-URLs for the “actions”, UR-URLs for the “storage and transmission rules”, UR-URLs for conditions that define “circumstances” and alternatives. Architects can also specify UR-URLs  101 . 1  for hard-drive addresses, real or referential. UR-URLs  101 . 1  provide an end-to-end architecture for Model of Everything  1000 . 
   Everything means |EVERYTHING| in whatever system is using the present invention. A dictionary is a comprehensive listing of original terms (system identity: term definitions) with descriptions, such that, in usage, when a term is specified the description is invoked, which lets us use words as a short-hand for meaning. Model of Everything  1000  is a comprehensive listing of original object records with descriptions that let us use UR-URLs as a short-hand for meaning in all kinds of forms, and formats, and sentences, and strings in programming tools that use relation variables. 
   In Model of everything  1000 , the identity-identifier, UR-URL  101 . 1 , is the platform for universal interoperability. 
   FIG.  44  Identity Expressions 
   Event Identity Forms  501  represent simple forms of expression that associate UR-URL Identifiers  101 . 1  with real identity. Makers record claims that link entity names with identifiers, as in Unitary Identity Statement  501 . 1  and they also record claims that link object names with identifiers, and object identifiers with object properties, as in  501 . 2 . Multiple assertions may be in one statement, as in Unitary Event Identity Statement  501 . 3 . 
   FIG.  45  Logical Expressions 
   Event Tuple Forms  502  represent simple forms of expression that associate subject, object, and predicate, where Tuple Statement  502 . 1  is a standard construction with prior art identifier and Unitary Tuple Statement  502 . 2  has the same semantic structure with UR-URL Identifiers  101 . 1 . A standard N-Tuple Statement  502 . 3  is likewise compared with Unitary N-Tuple Statement  502 . 4 . UR-URL Identifiers  101 . 1  may be used to represent terms in simple COTS or Open Source Predicate Logic Software  600 . 8  logical constructions. 
   FIG.  46  Correspondence Between Expressions 
   Event Statement Forms  503  illustrate correspondence between how English Language  503 . 2  terms used in logical constructs to represent the sentence “A cat is on a mat” in examples from Sowa&#39;s explanatory material and how UR-URL Identifiers  101 . 1  terms are used to represent the same sentence “A cat is on a mat.”  503 . 1  with the same notation and syntax, substituting UR-URL Identifiers  101 . 1  for the Event Objects  301 . 3  “cat” and “mat”, and the Event Assertion  301 . 4  “on”, which would correlate to identity objects in Model of Everything  1000 . 
   FIG.  47  Description Expressions 
   Event Description Forms  504  illustrate the use of simple logical constructions to enter object identity information in Model of Everything&#39;s  1000  tabular architectures  600 . 11 . 
   Single Entry  504 . 1  form associates resource object UR-URL  101 . 1  with properties and values entered by makers as Event Data  600 . 2  or selected from Unitary Integrated Ontology  309 , as indicated by the drop selection “Find Term” in both  504 . 1  and  504 . 2 . 
   Multiple Entries  504 . 2  form illustrates how resource object UR-URLs  101 . 1  may be associated with Unitary RDF terms and values in a compound statement. 
   FIG.  48  Programmatic Expressions 
   Programmatic Forms  505  illustrate three of numerous possible examples of programmatic expressions. Resource Planning  505 . 1  illustrates a typical Activity  101 . 8  Event Object  201 . 3  as would relate project terms in activity scheduling programs. The Activity  101 . 8  is the Event object  201 . 3  that “has” Resources  407 , Constituents  405 , Relations  408 , and Values-Event Data  600 . 2 . Just as Critical Path Method (CPM) Networks are constructed by associating these elements, so simple logical statements can associate elements. Elements&#39; UR-URL Identifiers  101 . 1  could be represented graphically as a CPM Network Diagram as shown in  FIG. 49 , CPM  506 . 2 . 
   Operations Sequencing  505 . 2  illustrates a typical “object has sequence of instructions” type of Event Object  201 . 3 , and Binary Pairs  505 . 3  illustrates the simple association of two UR-URL Identifiers  101 . 1 . 
   FIG.  49  Diagrammatic Expressions 
   Diagrammatic Forms  506  illustrate four of numerous possible examples of diagrammatic expressions that may be represented as logical statements or graphical elements, depending on what kinds of COTS and Open Source and other software programs and objects are employed. Spatial arrangements are facilitated by the relative referential geotemporal coordinate basis of UR-URL Identifiers  101 . 1 . 
   Tree  506 . 1  illustrates a typical hierarchical organization chart type arrangement; CPM  506 . 2  illustrates a network diagram with UR-URL Identifiers  101 . 1  as previously discussed. Cluster  506 . 3  illustrates a honey-combed representation of relation and/or sequence of UR-URL Identifiers  101 . 1 . Map  506 . 4  represents an object relationship diagram that maps links between UR-URLs  101 . 1 , such as are used in social network maps, mind maps, associative diagrams, and so forth. 
   FIG.  50  Menu Expressions 
   Menu Forms  507  is a rendering of a portion of the Microsoft Word file menu structure. Main menu bars with most frequently used operations grouped as sub-menus are common features of software programs in general. Typically, menus are represented as a series of drop-down boxes with exploding sub-lists of choices, as shown in Prior Art Menus  507 . 1 . 
   The same menu structure depicted in  507 . 1  is depicted in Prior Art Menu Expressions  507 . 2  as would be represented in a logical selection statement using UR-URLs, and where, in a Model of Everything  1000  with the system identity: MS Word, each menu, sub-menu, and code object are line items in the system&#39;s model of Database of Everything  104 . 
   FIG.  51  Prior Art Menu Synthesis and Simplification 
   MS directories are presented in a version of tree form  506 . 1  turned sideways that represent paths through the whole. This is a user-friendly way to present a big-picture view of relationships, and it is an intuitive way to organize information at the architectural level—particularly for MS programmers building on the original conceptual architecture of DOS. Plus, linear structures are well suited for computational efficiency. 
   But in order for trees to maintain relations down through the lowest levels of granularity, there is redundancy as seen in two instances of “Cancel [X on checkbox] in the third “Drop-Down Sub-Menus” column of Prior Art Menus  507 . 1 . “Cancel” is an “object” that is repeated many times in many of the MS Word menus. Redundancy is also apparent across entire complements of “suite” products, as illustrated in Menu Synthesis  506 . 
   Menu Synthesis  508  is made up of a table with menu objects grouped by program, Twelve Program Objects—One Hundred and Five menu Objects  508 . 2 , and a table with common menu objects each represented just once, One Platform—Twenty-Five menu Objects  508 . 2 . 
     508 . 1  is made up of a rough tally of menu objects from a twelve-program “premiere” collection of integrated programs that are discussed generically but which are based on the MS products used by the inventor to create, illustrate, and specify the present invention. Many comparable products with similar complements of redundant menu objects are available through COTS and Open Source sources. 
   Products shown in  508 . 1  are also shown in Table 3, and have instances of menu types listed. Uncommon menu types are shown in the shaded area. Common suite of products include: Web Browser  5082 . 1 , Mail Handler  508 . 2 . 2 , Word Processor  508 . 2 . 3 , Web Page Creation and Editing  508 . 2 . 4 , Spreadsheet  508 . 2 . 5 , Database  508 . 2 . 6 , Graphics  508 . 2 . 7 , Presentation  508 . 2 . 8 , Publishing  508 . 2 . 9 , Drawing  508 . 2 . 10 , Project Management  508 . 2 . 11 , and Directory  508 . 2 . 12 . 
   
     
       
             
           
             
             
             
             
             
             
             
             
             
             
             
             
           
         
             
               TABLE 3 
             
           
           
             
                 
             
             
               MS Office Product Main Menu Examples - One Hundred and Two Objects 
             
           
        
         
             
               WEB 
               MAIL 
               WP 
               HTM-ED 
               SS 
               DB 
               GRFX 
               PRES 
               PUB 
               PNT 
               PM 
               DIR 
             
             
                 
             
             
               File 
               File 
               File 
               File 
               File 
               File 
               File 
               File 
               File 
               File 
               File 
               File 
             
             
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
               Edit 
             
             
               View 
               View 
               View 
               View 
               View 
               View 
               View 
               View 
               View 
               View 
               View 
               View 
             
             
                 
                 
               Insert 
               Insert 
               Insert 
               Insert 
               Insert 
               Insert 
               Insert 
                 
               Insert 
             
             
                 
                 
               Format 
               Format 
               Format 
                 
               Format 
               Format 
               Format 
                 
               Format 
             
             
               Tools 
               Tools 
               Tools 
               Tools 
               Tools 
               Tools 
               Tools 
               Tools 
               Tools 
                 
               Tools 
               Tools 
             
             
               Favorites 
               Favorites 
               Table 
               Table 
               Data 
                 
               Effects 
               Slideshow 
               Table 
               Image 
               Project 
               Favorites 
             
             
               Search 
               Actions 
                 
               Frames 
                 
                 
               Arrange 
                 
               Arrange 
               Colors 
             
             
               Address 
               Contacts 
                 
                 
                 
                 
                 
                 
               Mailmerge 
             
             
               Links 
             
             
                 
                 
               Window 
               Window 
               Window 
               Window 
               Window 
               Window 
                 
                 
               Window 
             
             
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
               Help 
             
             
               IE Browser 
               Outlook 
               Word 
               FrontPage 
               Excel 
               Access 
               Photodraw 
               PowerPoint 
               Publisher 
               Paint 
               Project 
               WinExplorer 
             
             
                 
             
           
        
       
     
   
   Menus synthesized in  508 . 2  are shown in Table 4, and have each instance of menu type listed just once. Synthesized Main File Menu groupings are: File  508 . 1 . 1 , Edit  508 . 1 . 2 , View  508 . 1 . 3 , Insert  508 . 1 . 4 , Format  508 . 1 . 5 , Tools  508 . 1 . 6 , Table  508 . 1 . 7 , Data  508 . 1 . 8 , Function  508 . 1 . 9 , Window  508 . 1 . 10 , and Help  508 . 1 . 11 . 
   
     
       
             
           
             
             
             
             
             
             
             
             
             
             
             
           
         
             
               TABLE 4 
             
           
           
             
                 
             
             
               Main Menu Synthesis - Twenty-Five Objects 
             
           
        
         
             
               File 
               Edit 
               View 
               Insert 
               Format 
               Tools 
               Table 
               Data 
               Function 
               Window 
               Help 
             
             
                 
             
             
               Favorites 
                 
                 
                 
               Image 
                 
                 
                 
               Action 
               Arrange 
                 
             
             
               Search 
                 
                 
                 
               Colors 
                 
                 
                 
               Project 
               Frames 
             
             
               Address 
                 
                 
                 
               Effects 
                 
                 
                 
               Mailmerge 
             
             
               Links 
                 
                 
                 
                 
                 
                 
                 
               Slideshow 
             
             
                 
                 
                 
                 
                 
                 
                 
                 
               Contacts 
             
             
                 
             
           
        
       
     
   
   FIG.  52  Simplified Menu Expressions 
   Table 5 Sample Unitary Main Menu Optional Arrangements shows a minimalist configuration with the same synthesis of twenty-five unique objects shown in  FIG. 51 , but further simplified by grouping into four main menus. 
   
     
       
             
           
             
             
             
             
             
           
         
             
               TABLE 5 
             
           
           
             
                 
             
             
               Sample Unitary Main Menu Optional Arrangements 
             
           
        
         
             
                 
               File 
               Frame 
               Tool 
               Function 
             
             
                 
                 
             
             
                 
               File 
               Frame 
               Tool 
               Function 
             
             
                 
                 
               View 
               Edit 
               Action 
             
             
                 
                 
               Arrange 
               Table 
             
             
                 
                 
               Insert 
               Data 
             
             
                 
                 
               Format 
               Project 
             
             
                 
                 
               Image 
               Mailmerge 
             
             
                 
               Search 
               Colors 
               Slideshow 
             
             
                 
               Address 
               Effects 
               Contacts 
             
             
                 
               Links 
               Window 
               Favorites 
             
             
                 
                 
                 
               Help 
             
             
                 
                 
             
           
        
       
     
   
   When menus are constructed using logical statements to associate sub-menus and functions, statements may specify any menu object in any grouping. In macro, objects are groups of lines of code, that are grouped functionally, and grouped programmatically, and grouped systemically. There are hierarchical relationships between object functions, and some objects have other objects as constituents, i.e. a main menu “has” sub menus and a sub-menu “has” other sub-menus or programmatic objects. Each term at each level of granularity is represented in a model Model of Everything  1000  with system identity: premier software suite, and terms can be grouped into main menus and sub-menus that suit users. 
     FIG. 52  illustrates Simplified Menu Forms  509  as a logical selection statement for a model of Model of Everything  1000  with the system identity: premier software suite as would allow selection at the program object level with Program Objects  509 . 1 . 1 , the menu object level with Menu Objects  509 . 1 . 2 , and object level with Navigation Objects  509 . 1 . 3  or other objects. 
   Shell With Simplified Menu Forms  510  illustrates the application of unitary menu synthesis groupings to the selection of main file menus that may be associated with shells  600 . 4 . Simplified Menu Forms  509  and Shell with Simplified Menu Forms go into Unitary Shell  601 . Navigation Bar  600 . 3  and Access  600 . 19  are also illustrated as optional menu object elements. 
   FIG.  53  Unitary Platform 
   Platform for Everything  105  is made up of: UR-URL Identifier Method  101 , Database of Everything  104 , Unitary Shell  601 , COTS or Open Source Computer System  600 . 1 , COTS or Open Source Shell Software With Simple Tools  600 . 7 , COTS or Open Source Predicate Logic Software  600 . 8 . Spreadsheet  600 . 5  and/or Database  600 . 6  software may also be used and are shown. 
   Platform for Everything combines the universal utility of Unitary components and capacities with common programmatic forms and features in COTS and Open Source tools in one unitary interoperable platform of universal, persistent, infinitely extensible, identities. 
   In reality, real citizen identity is the platform for democracy. UR-URL Identifiers 101  are real identity identifiers that correlate real citizen identity with real referential incept ownership identity. Real identity is the platform. Platform for Everything  105  is apparatus in four dimensions. 
   FIG.  54  Current Embodiment Access Process 
   Thus far figures have traced the deconstruction and reconstruction of everything as apparatus in five dimensions—0D to 4D. Abstract information infrastructure and architectural contexts have been made concrete as components and parts of physical apparatus. Figures have shown how parts fit together and how parts work together to form one universal Model of Everything  1000 . Civil and economic dimensions have been considered mechanically. The following figures address the access process component of |EVERYTHING| which includes the politics of access and control, but without which, Model of Everything  1000  would not be |Everything|. The point of identifying, describing, and co-locating information resources is so people can find and use them. Access is pivotal. 
   Process flow diagrams that follow share common steps which, once described, are referred to by Part No. in subsequent diagrams, and not described again in detail. 
     FIG. 54  depicts the Current Embodiment Flow Diagram  511  which begins when people and things are instantiated at incept with Official Incept Authentication  101 . 4 . 1 . Real Names  101 . 2 . 2  are associated with real identity in “the system”. “The system” refers to that Western Democratic institution that comprises “We the people”, the body politic, where the individual elements in the system are Sui Juris  309 . 9 . 1  citizens or Non-Sui Juris  309 . 9 . 2  citizens with system identity: USA (or other country) which has sovereign interest in and responsibility for maintaining a public roll of authenticated citizen identities—Real Names  101 . 2 . 2 . 
   Sui Juris citizens may participate in the economy, may make contracts for goods and services, may vote, and may otherwise self-represent in the extended marketplace of country of origin. Armed with proof of identity—simple birth certificate and picture ID, a person can travel freely in country, get a drivers license, get a Social Security Number and get a job, open bank accounts, get utility service, phone service, television service, and service of all kinds. He can use public transportation, public libraries, and use public services. Identity in “the system” means access to critical public infrastructure owned in common by the citizenry, held in trust and managed for the people by the “current administration”. 
   Thus, people may contract with vendors to obtain access to the telephone system, access to cable systems, to banking systems, or other service systems, and particularly, access to the Internet. Vendors Mint Artificial Identifiers  500 . 2  after either No Authentication  500 . 3  or Authentication  500 . 4 , which assigns a User ID/Password  500 . 6 , that gives Access  600 . 19  to Vendor Service Providers  500 . 7 . 
   Layers  500 . 5  includes the growing number products and services from Authentication Schemas, and Authentication Products, to Privacy and Security Products and Certificates, Federation Partners, and Web Services. 
   Once access identity is established, and User ID/Password  500 . 6  formalized, users can access their accounts, buy, receive vendor service. In the case of the Internet, access is to the larger marketplace of Vendor Service Providers  600 . 7 . Part  600 . 7  signifies participation in the economy, which is the desired end step. 
   FIG.  55  Web Services Vendor Mint Access Process 
   The Internet is fast becoming the only system as more and more business is conducted electronically through ever widening arrays of devices and exponentially increasing volumes of transactions. Identity Federations afford business many interoperability benefits, including participation in one system of unique identifiers. Just as universal utility is achieved through UR-URL Identifiers  101 . 1  for everything, so business partnerships in supply chains achieve the same utility but on a smaller scale. 
   New Web Services Vendor Mint Model Flow Diagram  512  depicts instantiation  101 . 4  preceding identity  101 . 2 . 2  followed by Vendor Trust Provider  500 . 8 , such as Liberty Alliance and UDDI, which relies on Authentication By Vendor  500 . 4  and Layers  500 . 5  of authentication products and services, culminating in Vendor Mint Artificial Identifier  500 . 2  and Access  600 . 19 . 
   An important distinction of this flow process as compared to flow processes  511 ,  513 , and  514  is shown in the sub-loop through Vendor Authentication  500 . 4  and Vendor Anytime Authentication  500 . 9 . to Vendor Service Provider  500 . 7 . In the new federated web services model, vendor partners serve as Trust Providers and authenticate identities for their partners, supply chains, and customers. 
   Official Authentication  104 . 2  is missing. Moreover, the anytime authentication necessary to conduct online transactions bypasses the user altogether. 
   FIG.  56  Worst Case Future Vendor Mint Access Process 
   The only thing worse than vendor trust providers owning private identity is depicted in Worst Case Future Vendor Mint Model Flow Diagram  513 . Diagram  513  is identical to Diagram  512  as regards the flow from  101 . 4 . 1  to  101 . 2 . 2  to  500 . 8  to  500 . 2  to  600 . 19  to  500 . 7 . 
   As noted, the difference is in the sub-loop through Official Authentication  101 . 4 . 2  and Official Anytime Authentication  101 . 4 . 3 . The user is again bypassed, but this worst-case scenario shows vendors interacting directly with official authentication processes, positioning vendors squarely between citizens and their government. 
   FIG.  57  Present Invention Access Process 
   Present Invention Owner Self-Mint Flow Diagram  514  depicts instantiation  101 . 4  preceding identity  101 . 2 . 2  followed by Official Authentication  101 . 4 . 2  provided directly to the user-maker-owner making a claim to Mint Real Identifier  500 . 1  in Model of Everything&#39;s  1000  public domain. User-maker-owners may Access  600 . 19  the Internet and Vendor Service Providers  500 . 7 , as well as initiate Official Anytime Authentication  101 . 4 . 3  to vendors. 
   FIG.  58  Access Process Comparison 
     FIG. 56  shows all four flow process diagrams,  511 - 514  aligned for comparison. The distinction between authentication steps is significant. Without self-minting, the only choices are vendor mints or a national mint, owned and controlled by the government. Without the present invention, the worst is inevitable with vendors churning out privacy solutions as fast as government is automating vital public domains. 
   FIG.  59  Direct Ownership Process Components 
     FIG. 59  illustrates detail in Current Embodiment Flow Process  511 . 
   Our current analog system is a system based on Private Ownership  500 . 10  of Real Identity, Real Property, Personal Property, Tangible Property, Intangible Property, and Intellectual Property. 
   
     
       
             
             
           
         
             
                 
             
           
           
             
               500.11 
               We are owners in common with Public Infrastructure Ownership 500.11 of Public Property, 
             
             
                 
               including but not limited to Public Resources, Public Broadband, Public “Hot Spots”, Public 
             
             
                 
               Television Broadcast, Public Radio Broadcast, Public Library System, and Public Mail System. 
             
             
               500.12 
               We have Privately Owned Systems 500.12 including but not limited to Computers, Monitors, 
             
             
                 
               CPU/OSes, Storage Media, Peripherals, and Software Licenses that are our private property. 
             
             
               500.13 
               We also own Access Devices 500.13 such as Cell Phones, Landline Phone, Walkie-Talkie, 
             
             
                 
               Television, Radio, Ham Radio devices, Broadband devices, GPS Receivers, and Satellite Dishes. 
             
             
               500.14 
               We have service contracts with Access Vendors 500.14 including but not limited to Phone 
             
             
                 
               Company, Cable Company, Wireless Company, Cellular Company, Internet Company, Satellite 
             
             
                 
               Company, Digital Audio Company, GPS Company, Broadband Company, and Mail Delivery 
             
             
                 
               Company. 
             
             
               500.15 
               Vendors use customer identity as Access Means/Control 500.15 which takes various forms 
             
             
                 
               including but not limited to Phone Number, User/Account Number, Wireless Number, Cellular 
             
             
                 
               Number, User ID/Password, User Name/Account Number, User/Account Number, and 
             
             
                 
               Name/Account Number. 
             
             
               500.16 
               Users buy and own products, and rent access and services from multiple vendors in a competitive 
             
             
                 
               marketplace with individual Service Contracts 500.16 made between user-maker-owners and 
             
             
                 
               individual vendors for specific uses. 
             
             
                 
             
           
        
       
     
   
   FIG.  60  Intermediary Ownership Process Components 
   In the New Web Services Vendor Mint Model  512 , there is Vendor Infrastructure Ownership and Control  500 . 17  in Television, Radio, Broadband, Telephone, Internet, Cable, Optical Cable, Cellular, and Microwave. The new model relies on early obsolescence of vendor-dependent devices with vendor embedded controls and single-vendor operating instructions. The new model actively promotes Rented Hardware and Access Devices  500 . 18  including but not limited to Rented Access Hardware, Proprietary RF Receivers, Proprietary Cable Receivers, Proprietary Satellite Receivers, Proprietary Broadband Receivers, Proprietary Digital Audio Receivers, Proprietary GPS Receivers, Proprietary Data Receivers, Rented Identity, Rented Web Software Services Access, Rented Web Service Product Access, Rented Web Service Time Access, Rented Web Service Data Storage Access 
   The new Access Vendors  500 . 19  are Identity Federations, who use Federated Identity for Access Means and Control  500 . 20  that establish Vendor Control of Private Identity, Vendor Control of Private Information, Vendor Control of Private Devices, and Vendors Between Citizens and Government. In place of many service contracts with many vendors, the new model is Federated Web Services  500 . 21  and their product is Trust, embodied as Communication Services, Authentication Services, Privilege Management Services, Security Services, Application Services, Directory Services, Hosting Services, and Search Services, all in one Membership Contract and End User License Agreements (EULA&#39;s) with One-Sided and Hidden Terms and Conditions, and Personalization with User Profiling/Data Mining and Content Pre-Screening/Filtering. 
   FIG.  61  Ownership Process Components Comparison 
     FIG. 61  illustrates the differences between Owner System—Individual Ownership—Direct Access  515 , comprised of the Current Embodiment Flow Diagram  511  enhanced by the Present Invention Owner Self-Mint Flow Diagram  514 , and the New Web Services Vendor Mint Model Flow Diagram  512 . 
   The New Web Services Vendor Mint Model  512  is based on the unsupportable premise of vendor ownership of private identity, and, absent alternative, will place Middle-Men  500 . 24  between Citizen  500 . 22  and Government  500 . 23 , where the Present Invention Owner Mint Model  514  sustains and builds upon the fundamental covenant between Government  500 . 23  and Citizens  500 . 22 . 
   The current embodiment is a real world analog system based on private identity ownership. The Internet embodiment and its evolving new form, Federated Web Services  500 . 21 , replicates the real world as an electronic system based on vendor identity ownership. This is a hugely significant shift in premise. The resultant Vendor Mint Model  512  requires Layers  500 . 5  of authentication products and services to correct problems created by artificial identity in the first place. A system of artificial identities cannot sustain anything, much less everything. The electronic version of “The System” must be as real as its analog original. The economy depends on it. 
   The present invention corrects fundamental flaws in the current electronic embodiment by providing method, means, and apparatus based on private identity ownership, thus bringing the electronic replica into alignment with its analog original. 
   VI Web Portal to Everything View  5   
   FIG.  62  Web Portal to Everything Components 
   The components of Web Portal to Everything  106  are: UR-URL Identifier Method  101 , Platform for Everything  105  including all parts, Navigation Bar With Links  600 . 3 , COTS or Open Source Web Page Software  600 . 9 , COTS or Open Source Browser Software  600 . 10 , Frames With and Without Content  600 . 18 , and Access  600 . 19 . 
   FIG.  63  Web Portal View 
     FIG. 63  illustrates a common web portal form apparatus made up of COTS or Open Source Computer System  600 . 1 , Navigation Bar With Links  600 . 3 , COTS or Open Source Web Page Software  600 . 9 , COTS or Open Source Browser Software  600 . 10 , Frames With and Without Content  600 . 18 , and Access  600 . 19 . 
   FIG.  64  Unitary Web Portal 
   Web Portal to Everything  106  is made up of a common web portal form apparatus as shown in  FIG. 63 , and made up of  600 . 1 ,  600 . 3 ,  600 . 6 ,  600 . 9 ,  600 . 10 ,  600 . 18 , and  600 . 19 , plus Unitary components  101 ,  104 , and  105  which include Unitary Shell  601 , Unitary Ontology  300 , and Unitary RDF  400 , not called out separately in  FIG. 64 . 
   Web Portal to Everything  106  is depicted as a user view of computer monitor with Platform for Everything  105  open in the background to Database of Everything  104 , and with a Web Portal to Everything  106  browser frame open in the foreground. 
   Web Portal to Everything  106  embodies Model of Everything&#39;s  1000  cumulative aggregation of unitary components: Unitary Reference Architecture  100  with UR-URL Identifier Method  101 , List  102 , Table  103 , Database  104 , Platform  105 , and Web Portal  106  to Everything, including Unitary Ontology Architecture  300 , Unitary Resource Description Framework  400 , Unitary Process Architecture  500 , and Unitary Apparatus  600 . 
   Web Portal to Everything  106  is Model of Everything&#39;s  1000  electronic replica of our global network of information, transportation, and telecommunications systems—all systems in one system, replacing many systems of artificial access identifiers with one system of universal real identifiers minted by citizens, owned by citizens, controlled by citizens, authenticated as in analog by citizen&#39;s official channels, and used by citizens to identify person and property during the course of self-representation in democracy and participation in the economy. Web Portal to Everything  106  is apparatus in all dimensions. 
   FIG.  65  Sample Web Portal to Everything Page  1   
     FIG. 65  depicts a sample Web Portal to Everything  106  page made up of  600 . 1 ,  600 . 3 ,  600 . 6 ,  600 . 9 ,  600 . 10 ,  600 . 18 , and  600 . 19 ,  601 ,  101 , and  104  with Frame Contents  600 . 18  illustrating Database of Everything  104  as might be accessed by a user looking for information, information which in this and subsequent samples corresponds to examples given in the specification about homes in Podunk County. 
   FIG.  66  Sample Record  1   
     FIG. 66  illustrates a sample Model of Everything  1000  object record such as would correspond to an Official Record of Ownership  414 . 1 . 
   FIG.  67  Sample Record  2   
     FIG. 67  illustrates a sample Model of Everything  1000  object record such as would correspond to an Individual Public claim  414 . 2 . 
   FIG.  68  Sample Record  3   
     FIG. 68  illustrates a sample Model of Everything  1000  object record such as would correspond to a Vendor claim  414 . 3 . 
   FIG.  69  Sample Record  4   
     FIG. 69  illustrates a sample Model of Everything  1000  object record such as would correspond to an Individual Update Record  414 . 4 . 
   FIG.  70  Sample Record  5   
     FIG. 70  illustrates a sample Model of Everything  1000  object record such as would correspond to a Public Directory Record  414 . 5 . 
   FIG.  71  Sample Record  6   
     FIG. 71  illustrates a sample Model of Everything  1000  object record such as would correspond to an Original Incept claim  414 . 6 . 
   FIG.  72  Sample Record  7   
     FIG. 72  illustrates a sample Model of Everything  1000  object record such as would correspond to an Official US Census Record  414 . 7 . 
   FIG.  73  Sample Record  8   
     FIG. 73  illustrates a sample Model of Everything  1000  object record such as would correspond to a Personal Record  414 . 8 . 
   FIG.  74  Sample Record  9   
     FIG. 74  illustrates a sample Model of Everything  1000  object record such as would correspond to a Personal Homepage  414 . 9 . 
   FIG.  75  Sample Record  10   
     FIG. 75  illustrates a sample Model of Everything  1000  object record such as would correspond to search results for John Q. Public and 123 Palmy Way  414 . 10 . 
   FIG.  76  Sample Records Summarized 
     FIG. 76  depicts a summary of Sample  414  records illustrated in  FIGS. 6 through 75 , Parts  101 , and  414 . 1  through  414 . 9 , as might be represented in Unitary Reference Architecture  100  tabular apparatus forms. 
   FIG.  77  Sample Web Portal to Everything Page  2   
     FIG. 77  depicts a sample Web Portal to Everything  106  page made up of  600 . 1 ,  600 . 3 ,  600 . 5 ,  600 . 9 ,  600 . 10 ,  600 . 18 , and  600 . 19 ,  601 , and  101 , with Frame Contents  600 . 18  illustrating Table of Everything  103  as might be presented to as user as search results based on specification Samples  414  of records in Podunk County. 
   FIG.  78  Enterprise Record Examples 
     FIG. 78  depicts a summary of enterprise records as might be represented in Unitary Reference Architecture  100  tabular apparatus forms with UR-URL Identifiers  101  in a system that applies the principle of ownership in a business asset management context. Enterprise Summary Array  415  is made up of hierarchically related object records that represent hierarchical entity roles within an enterprise which “have” resources, relations, responsibilities, and other properties and values that each have identity object records in an enterprise model of Model of Everything  1000  and extended Unitary RDF  400 . 
   Enterprise Summary Array  415  is made up of object arrays corresponding to Company  415 . 1 , Component  415 . 2 , Division  415 . 3 , Department  415 . 4 , Work Center  415 . 6 , and Work Station  415 . 6 . 
   FIG.  79  Enterprise Record Example Detail 
     FIG. 79  depicts the same enterprise information as depicted in  FIG. 78 , but with more and or different detail. Model of Everything&#39;s  1000  dimensional construct supports any level of granularity, as illustrated by comparison of  FIGS. 78 and 79 . 
   Enterprise Detail Array  416  is made up of object arrays corresponding to Corporation  416 . 1 , Component  4162 , Division  416 . 3 , Department  416 . 4 , Work Center  416 . 5 , Work Station  416 . 6 , Resource  416 . 7 , Role  416 . 8 , and Process  416 . 9 . 
   FIG.  80  Present Invention Part List Example 
     FIG. 80  illustrates the present invention&#39;s parts list as might be represented in Unitary Reference Architecture  100  tabular apparatus forms with UR-URL Identifiers  101 . Part Number Array  417  shows correspondence between six terms required to describe parts and six terms of UR-URL Identifier Method. 
   Part Number Array  417  is made up of FIG. No/Path  417 . 6 , Part No./UR-URL  417 . 1 , FIG. Name/Owner  417 . 3 , Part Name/Name  417 . 2 , Sub-Parts/Keywords  417 . 5 , and Parent Component/Authority  417 . 4 . 
   FIGS.  81 - 92  Prototype Illustrated 
   The utility, practicality, and universality of the present invention may be most comprehensively illustrated in a prototype web portal. A model of records of claims of everything, including event objects and event assertions, could be made manifest in other media, and could be depicted with additional detail in both content and active object design. The UR-URL prototype is intended as an illustration only, simple and short, and as such is not intended to represent all possible illustrations. 
   The actual technical construction of the apparatus itself is elementary, compared to its principles of organization. It was designed only after the indexing and classification system had been developed. A model of everything is a lot of stuff to organize on a few pages. The ontology is the result of much consideration, and its simple framework is evident in the information groups and layouts. 
   The prototype UR-URL website apparatus was designed in 2001, in order to demonstrate functional utility. A second prototype front end was designed in March of 2002 in order to demonstrate commercial, social, and political utility. FIGS.  81 / 96  to  92 / 96  depict the original conceptual rendering. 
   Prototype Structure 
   There are four basic uses. The first is introductory, the second is registration, the third, search, and the fourth, commerce. Extensions org, net, and com are used as names that refer to said purposes within one whole unitary system, and are not separate domains. 
   FIG.  81  Homepage  1   
     FIG. 81 , Homepage  1 , represents the initial web portal user interface. The purpose of Homepage  1  is to provides links to direct visitors to frequently asked questions, and to promote applications partners. 
   FIG.  82  Homepage  2   
     FIG. 82 , Homepage  2 , represents an overview of the web portal and its services. 
   FIG.  83  Homepage  3   
     FIG. 83 , Homepage  3 , continues the representation of the utility and functions of the web portal and its services. 
   FIG.  84  Homepage  4   
     FIG. 84 , Homepage  4 , represents a high-level graphical map of the web portal architecture. 
   FIG.  85  Homepage  5   
     FIG. 85 , Homepage  5 , represents the inclusion of generic terms of use and various policy statements, but does not stipulate contract language in entirety. The purpose of Homepage  5  is to illustrate conformance to typical web portal features. Details of such policies are inconsequential to the utility of UR-URL Addressing and indexing method. 
   FIG.  86  Homepage  6   
     FIG. 86 , Homepage  6 , represents an introduction to the commercial utility of UR-URL, providing general information about how applications may be considered. Groupings are intended to illustrate broad categories of technical functions.
         1. “Official records” depicts UR-URL&#39;s utility as a compendium of record able public information and combines legal filings, product registration, birth and death recording, certifications and so forth into one system of official records of claims.   2. “Communications services” depicts UR-URL&#39;s utility as a compendium of global positioning and locating address protocols, and combines many address protocols for traffic control, voice and data telephony, and so forth into one system of addresses for routing communications and communications signals.   3. “Group services” depicts UR-URL&#39;s utility as a compendium of references, and combines directories, search engines, registries, cross-referenced multi-source personal profile data, and so forth into one system of addresses for correlation and integration by/with individual entities, groups, and/or their associated data.   4. “Data services” represents UR-URL&#39;s utility as an integration platform, and combines image mapping, synthesis, conversion, translation, correlation, projection, replication, reproduction, archival storage, and so forth into one system of unique control elements.       
   FIG.  87  Homepage  7   
     FIG. 87 , Homepage  7 , represents UR-URL&#39;s utility as a gateway for individual entities to connect with one another as well as to control how information about them is collected, stored, and disseminated. Homepage  7  depicts one future application that utilizes user-driven data mining and instant messaging technologies in real time, assigning addresses to information strings as specified by users for their own private information agent purposes. HomePage  7  does not stipulate all possible illustrations, rather is intended to show how technologies may be combined and integrated through the use of UR-URL addressing and indexing method. 
   FIG.  88  Homepage  8   
     FIG. 88 , Homepage  8 , represents the record registration function with classification options, and an automated form that shows relevant data fields and selections. 
   FIG.  89  Homepage  9   
     FIG. 89 , Homepage  9 , represents an overview of a typical search utility where public users may search the entire database. Sample pages are intended to illustrate general search functionality, and are not intended to stipulate all possible illustrations of search functionality. In the present illustration, anonymous searches are facilitated through the use of temporary UR-URL ID codes; simple and advanced search options enable selection specification. 
   FIG.  90  Homepage  10   
     FIG. 90 , Homepage  10 , continues the representation of a typical search function. 
   FIG.  91  Homepage  11   
     FIG. 91 , Homepage  11 , represents UR-URL&#39;s commercial utility where applications vendors&#39; products and services correlated to UR-URL are accessed by the public. 
   FIG.  92  Homepage  12   
     FIG. 92 , Homepage  12 , represents UR-URL&#39;s utility an illustration of the value equation derived from public-private partnership. UR-URL addressing and indexing properties have universal applicability and as such provide an ideal standard nomenclature for linking individuals and vendors with disparate systems and data. Users require unique identification and desire convenience; vendors must provide unique identification and UR-URL provides convenience. Increasing needs for interoperability at every level can be met through natural three-way demand/supply partnerships, such as those illustrated in  FIG. 92  Homepage  12 , that generate value all parties. Additional value derived from promotional placement of vendor applications partner links is illustrated. 
   FIG.  93  Alignment Between Components and Component Parts of Unitary Reference Architecture 
     FIG. 93  shows the progressive development of Unitary Reference Architecture  100  components, beginning with UR-URL Identifier Method  101 . 1 , which goes into List of Everything  102 , which goes into Table of everything  103 , which goes into Database of Everything  104  which goes into Platform for Everything  105  and Web Portal to Everything  106 . 
   FIG.  94  Alignment Between Parts and Part Numbers of Unitary Reference Architecture 
     FIG. 94  shows the relation between the Several Dimensional Views I-VI and the part number coding schema that correlates components and parts  1000 ,  100 ,  200 ,  201 ,  202 . 1 , and  201 . 2 . 
   FIG.  95  Model of Everything Apparatus 
     FIG. 95  illustrates the apparatus parts and part numbers used in descriptions and figures:
           600 . 1  COTS or Open Source Computer System     600 . 2  Event Data     600 . 3  Navigation Bar With Links     600 . 4  Shell     600 . 5  COTS or Open Source Spreadsheet Software With Search and Hyperlinks     600 . 6  COTS or Open Source Database Software     600 . 7  COTS or Open Source Shell Software With Simple Tools     600 . 8  COTS or Open Source Predicate Logic Software     600 . 9  COTS or Open Source Web Page Software     600 . 10  COTS or Open Source Browser Software     600 . 11  Tabular Architecture Rows and Columns     600 . 12  Infinite Integration With UR-URL Identifier Method Scope     600 . 13  Infinite Range With Infinite UR-URL Identifier Method Scope     600 . 14  Finite Integration With Finite Identifier Method Scope     600 . 15  Variable Relational Tables     600 . 16  Finite Range With Finite Identifier Method Scope     600 . 17  Variable Columns     600 . 18  Frames With and Without Content     600 . 19  Access     601  Unitary Shell       
   FIG.  96  Preferred Embodiment 
     FIG. 96  represents the preferred embodiment and preferred illustration view of the present invention, Model of Everything  1000 , with main components made up of Unitary Reference Architecture  100 —made up of UR-URL Identifier Method  101 , List of Everything  102 , Table of Everything  103 , Database of Everything  104 , Platform for Everything  105 , and Web Portal to Everything  106 —, Unitary Infrastructure  200 , Unitary Ontology Architecture  300 , Unitary Resource Description Framework (RDF)  400 , Unitary Process Architecture  500 , and Unitary Apparatus  600 . 
   LIST OF REFERENCE NUMERALS 
   
     
       
             
           
             
             
           
         
             
                 
             
             
               List of Reference Numerals 
             
           
        
         
             
               Part No. 
               Part 
             
             
                 
             
             
               1000 
               Model of Everything 
             
             
               100 
               Unitary Reference Architecture 
             
             
               1.1 
               Principle 
             
             
               101 
               UR-URL Identifier Method 
             
             
               101.1 
               UR-URL 
             
             
               100.1.1 
               UR-URL Real Identifier 
             
             
               100.1.2 
               XYZT/GT Incept 
             
             
               101.1.3 
               XYZT/GT Now 
             
             
               101.1.4 
               XYZT/GT Extension 
             
             
               101.1.5 
               Other Extension 
             
             
               101.1.6 
               Other Address 
             
             
               101.1.7 
               Other ID Number (ID) 
             
             
               101.2 
               Name 
             
             
               101.2.1 
               Claimed Identity Name 
             
             
               101.2.2 
               Real Name 
             
             
               101.2.3 
               Real Identity 
             
             
               101.2.4 
               Named Identity 
             
             
               101.2.5 
               Title 
             
             
               101.2.6 
               Term 
             
             
               101.2.7 
               Other Designation 
             
             
               101.3 
               Owner 
             
             
               101.3.1 
               Claim Maker Owner 
             
             
               101.3.2 
               Functional Owner 
             
             
               101.3.3 
               Maker 
             
             
               101.3.4 
               Inventor 
             
             
               101.3.5 
               Discoverer 
             
             
               101.3.6 
               Parent 
             
             
               101.3.7 
               Legal Agent 
             
             
               101.4. 
               Authority 
             
             
               101.4.1. 
               Official Incept Authentication 
             
             
               101.4.2 
               Official Authentication 
             
             
               101.4.3 
               Official Anytime Authentication 
             
             
               101.4.4 
               Maker Affidavit Authentication 
             
             
               101.4.5 
               Witness Affidavit Authentication 
             
             
               101.4.6 
               Other Legal Authentication 
             
             
               101.5. 
               Keywords 
             
             
               101.5.1 
               Coordinate Values 
             
             
               101.5.2 
               Point of Origin 
             
             
               101.5.3 
               Differential Quantity 
             
             
               101.5.4 
               Latitude 
             
             
               101.5.5 
               Longitude 
             
             
               101.5.6 
               Elevation 
             
             
               101.5.7 
               Date/Time 
             
             
               101.5.8 
               GT 
             
             
               101.5.9 
               Other Legal Designation 
             
             
               101.6 
               Path 
             
             
               101.6.1 
               Referential System 
             
             
               101.6.2 
               Parent System 
             
             
               101.6.3 
               GPS 
             
             
               101.6.4 
               Geo.Domain 
             
             
               101.6.5 
               USGS 
             
             
               101.6.6 
               Metes &amp; Bounds 
             
             
               101.6.7 
               Others 
             
             
               101.7 
               Profile 
             
             
               101.8 
               Activity 
             
             
               102 
               List of Everything 
             
             
               103 
               Table of Everything 
             
             
               104 
               Database of Everything 
             
             
               105 
               Platform for Everything 
             
             
               106 
               Web Portal of Everything 
             
             
               200 
               Unitary Infrastructure 
             
             
               200.1 
               Information Reference Architecture 
             
             
               200.2 
               Civil Infrastructure 
             
             
               200.3 
               Information Infrastructure 
             
             
               200.4 
               Physical Infrastructure 
             
             
               200.5 
               Process Infrastructure 
             
             
               200.6 
               Economic Infrastructure 
             
             
               201 
               Unitary Scope 
             
             
               201.1 
               All Identities 
             
             
               201.2 
               All Information 
             
             
               201.3 
               All Objects 
             
             
               201.4 
               All Systems 
             
             
               201.5 
               All Domains 
             
             
               201.6 
               All Events 
             
             
               202 
               Everything Dimensions 
             
             
               203 
               Layers of Objects 
             
             
               203.1 
               Event Identities 
             
             
               203.2 
               Event Information 
             
             
               203.3 
               Event Objects 
             
             
               203.4 
               Event System Objects 
             
             
               203.5 
               Event Sub-System Objects 
             
             
               203.6 
               Object of Everything 
             
             
               203.7 
               Icebergs of Ideas 
             
             
               203.8 
               Mountains of Matter 
             
             
               204 
               Levels of Abstraction 
             
             
               204.1 
               Explication 
             
             
               204.2 
               Aggregation 
             
             
               204.3 
               Organization 
             
             
               204.4 
               Synthesis 
             
             
               204.5 
               Resolution 
             
             
               204.6 
               Unification 
             
             
               300 
               Unitary Ontology Architecture 
             
             
               300.1 
               Term.Primitive Entity 
             
             
               300.2 
               Term.Sub-Class 
             
             
               300.3 
               Term.Type 
             
             
               300.4 
               Term.Field 
             
             
               300.5 
               Term.Unity 
             
             
               300.6 
               Term.One 
             
             
               300.7 
               Term.All 
             
             
               300.8 
               Term.All In All 
             
             
               301 
               Unitary Event Ontology 
             
             
               301.1 
               Unitary Top-Level Ontology 
             
             
               301.2 
               Event 
             
             
               301.2.1 
               Condition, Objects 
             
             
               301.2.2 
               Condition, Assertions 
             
             
               301.3 
               Objects 
             
             
               301.3.1 
               State.Person 
             
             
               301.3.2 
               State.Property 
             
             
               301.4 
               Assertions 
             
             
               301.4.1 
               State.Principle 
             
             
               301.4.2 
               State.Transaction 
             
             
               301.5 
               Person 
             
             
               301.5.1 
               Class.Real 
             
             
               301.5.2 
               Class.Fictitious 
             
             
               301.6 
               Property 
             
             
               301.6.1 
               Class.Real 
             
             
               301.6.2 
               Class.Personal 
             
             
               301.6.3 
               Class.Intellectual 
             
             
               301.6.4 
               Class.Public 
             
             
               301.7 
               Principle 
             
             
               301.7.1 
               Class.Primitive 
             
             
               301.7.2 
               Class.Law 
             
             
               301.7.3 
               Class.Standard 
             
             
               301.8 
               Transaction 
             
             
               301.8.1 
               Class.Claim 
             
             
               301.8.2 
               Class.Function 
             
             
               301.8.3 
               Class.Action 
             
             
               301.9 
               Person.Real 
             
             
               301.9.1 
               Sub-Class.Sui Juris 
             
             
               301.9.2 
               Sub-Class.Non-Sui Juris 
             
             
               301.10 
               Person.Fictitious 
             
             
               301.10.1 
               Sub-Class.For-Profit 
             
             
               301.10.2 
               Sub-Class.Nonprofit 
             
             
               301.11 
               Property.Real 
             
             
               301.11.1 
               Sub-Class.Land 
             
             
               301.11.2 
               Sub-Class.Rights 
             
             
               301.12 
               Property.Personal 
             
             
               301.12.1 
               Sub-Class.Tangible 
             
             
               301.12.2 
               Sub-Class.Intangible 
             
             
               301.13 
               Property.Intellectual 
             
             
               301.13.1 
               Sub-Class.Instrument 
             
             
               301.13.2 
               Sub-Class.Information 
             
             
               301.14 
               Property.Public 
             
             
               301.14.1 
               Sub-Class.Environment 
             
             
               301.14.2 
               Sub-Class.Emblem 
             
             
               301.15 
               Principle.Primitive 
             
             
               301.15.1 
               Sub-Class.Singularity 
             
             
               301.15.2 
               Sub-Class.Force 
             
             
               301.16 
               Principle.Law 
             
             
               301.16.1 
               Sub-Class.Theoretical 
             
             
               301.16.2 
               Sub-Class.Statutory 
             
             
               301.17 
               Principle.Standard 
             
             
               301.17.1 
               Sub-Class.Definition 
             
             
               301.17.2 
               Sub-Class.Convention 
             
             
               301.18 
               Transaction.Claim 
             
             
               301.18.1 
               Sub-Class.Statement 
             
             
               301.18.2 
               Sub-Class.Contract 
             
             
               301.19 
               Transaction.Function 
             
             
               301.19.1 
               Sub-Class.Operation 
             
             
               301.19.2 
               Sub-Class.Office 
             
             
               301.20 
               Transaction.Action 
             
             
               301.20.1 
               Sub-Class.Act 
             
             
               301.20.2 
               Sub-Class.Obligation 
             
             
               302 
               Relative Event Ontology 
             
             
               302.1 
               Primitive.Position 
             
             
               302.2 
               Primitive.Point 
             
             
               302.3 
               Primitive.Observer 
             
             
               302.4 
               Primitive.Specification 
             
             
               302.5 
               Primitive.Scene 
             
             
               302.6 
               Primitive.Reference-Body 
             
             
               302.7 
               Event Potential 
             
             
               302.8 
               Statement of Principle - C1920 Einstein 
             
             
               303 
               Entity Ontology - C2000 Sowa 
             
             
               303.1 
               Term.Entity ( ) =  τ . 
             
             
               303.2 
               Term. τ  ( ). 
             
             
               303.3 
               Term.Independent (I). 
             
             
               303.4 
               Term.Relative (R). 
             
             
               303.5 
               Term.Mediating (M). 
             
             
               303.6 
               Term.Physical (P). 
             
             
               303.7 
               Term.Abstract (A). 
             
             
               303.8 
               Term.Actuality (IP) = Independent∩Physical. 
             
             
               303.9 
               Term.Form (IA) = Abstract∩Independent. 
             
             
               303.10 
               Term.Prehension 
             
             
               303.11 
               Term.Proposition (RA). 
             
             
               303.12 
               Term.Nexus (MP) = Physical∩Mediating. 
             
             
               303.13 
               Term.Intention (MA) = Abstract∩Mediating. 
             
             
               303.14 
               Term.Continuant (C). 
             
             
               303.15 
               Term.Occurrent (O). 
             
             
               303.16 
               Term.Object (IPC) = Actuality∩Continuant. 
             
             
               303.17 
               Term.Process (IPO) = Actuality∩Occurrent. 
             
             
               303.18 
               Term.Schema (IAC) = Form∩Continuant. 
             
             
               303.19 
               Term.Script (IAO) = Form∩Occurrent. 
             
             
               303.20 
               Term.Juncture (RPC) = Prehension∩Continuant. 
             
             
               303.21 
               Term.Participation (RPO) = Prehension∩Occurrent. 
             
             
               303.22 
               Term.Description (RAC) = Proposition∩Continuant. 
             
             
               303.23 
               Term.History (RAO) = Proposition∩Occurrent. 
             
             
               303.24 
               Term.Structure (MPC) = Nexus∩Continuant. 
             
             
               303.25 
               Term.Situation (MPO) = Nexus∩Occurrent. 
             
             
               303.26 
               Term.Reason (MAC) = Intention∩Continuant. 
             
             
               303.27 
               Term.Purpose (MAO) = Intention∩Occurrent. 
             
             
               303.28 
               Term.Absurdity (IRMPACO) = ⊥. 
             
             
               303.29 
               Term.Intermediate Category 
             
             
               303.30 
               Central Category 
             
             
               304 
               Object Ontology - SUMO Browser C2001 IEEE 
             
             
               304.1 
               SUMO Term Search 
             
             
               304.2 
               SUMO Term Results 
             
             
               305 
               Ontology of Origination C1875 Eddy 
             
             
               305.1 
               Term.Principle 
             
             
               305.2 
               Term.Mind 
             
             
               305.3 
               Term.Soul 
             
             
               305.4 
               Term.Spirit 
             
             
               305.5 
               Term.Life 
             
             
               305.6 
               Term.Truth 
             
             
               305.7 
               Term.Love 
             
             
               305.8 
               Term.All Knowing 
             
             
               305.9 
               Term.All Acting 
             
             
               305.10 
               Term.All Seeing 
             
             
               305.11 
               Term.All Being 
             
             
               305.12 
               Term.All Wise 
             
             
               305.13 
               Term.All Loving 
             
             
               305.14 
               Term.All Eternal 
             
             
               305.15 
               Term.All Substance 
             
             
               305.16 
               Term.Intelligence 
             
             
               306 
               Ontology of Dimension 
             
             
               306.1 
               I Purpose 
             
             
               306.2 
               II Value 
             
             
               306.3 
               III Concept 
             
             
               306.4 
               IV Matter 
             
             
               307 
               Integrated Ontology 
             
             
               308 
               Dimensioned Integrated Ontology 
             
             
               309 
               Unitary Integrated Ontology 
             
             
               400 
               Unitary RDF Array 
             
             
               400.1 
               Logic: Has 
             
             
               400.2 
               Set 
             
             
               400.3 
               Purpose 
             
             
               400.4 
               Aspect 
             
             
               400.5 
               Expression 
             
             
               401 
               Identifier 
             
             
               401.1 
               Logic.Has UR-URL 
             
             
               401.2 
               Set.Record 
             
             
               401.3 
               Purpose.Differentiation 
             
             
               401.4 
               Aspect.Uniqueness 
             
             
               401.5 
               Expression.Address 
             
             
               402 
               Identity 
             
             
               402.1 
               Logic.Has Name 
             
             
               402.2 
               Set.Register 
             
             
               402.3 
               Purpose.Designation 
             
             
               402.4 
               Aspect.Representation 
             
             
               402.5 
               Expression.Element 
             
             
               403 
               Origin 
             
             
               403.1 
               Logic.Has Owner 
             
             
               403.2 
               Set.Ontology 
             
             
               403.3 
               Purpose.Ownership 
             
             
               403.4 
               Aspect.Inception 
             
             
               403.5 
               Expression.Condition 
             
             
               404 
               Agreement 
             
             
               404.1 
               Logic.Has Authority 
             
             
               404.2 
               Set.Concordance 
             
             
               404.3 
               Purpose.Instantiation 
             
             
               404.4 
               Aspect.Legitimacy 
             
             
               404.5 
               Expression.State 
             
             
               405 
               Constituent 
             
             
               405.1 
               Logic.Has Keyword 
             
             
               405.2 
               Set.Taxonomy 
             
             
               405.3 
               Purpose.Classification 
             
             
               405.4 
               Aspect.Composition 
             
             
               405.5 
               Expression.Category 
             
             
               406 
               System 
             
             
               406.1 
               Logic.Has Path 
             
             
               406.2 
               Set.Architecture 
             
             
               406.3 
               Purpose.Integration 
             
             
               406.4 
               Aspect.Orientation 
             
             
               406.5 
               Expression.Domain 
             
             
               407 
               Resource 
             
             
               407.1 
               LogicHas Profile 
             
             
               407.2 
               Set.Pool 
             
             
               407.3 
               Purpose.Utilization 
             
             
               407.4 
               Aspect.Eligibility 
             
             
               407.5 
               Expression.Class 
             
             
               408 
               Relation 
             
             
               408.1 
               Logic.Has Activity 
             
             
               408.2 
               Set.Model 
             
             
               408.3 
               Purpose.Operation 
             
             
               408.4 
               Aspect.Context 
             
             
               408.5 
               Expression.Union 
             
             
               409 
               Resource Description Matrix 
             
             
               410 
               Resource Description Synthesis 
             
             
               411 
               Logic 
             
             
               411.1 
               Bearer 
             
             
               411.2 
               Normative Agent 
             
             
               411.3 
               Condition of Obligation 
             
             
               411.4 
               Obligation 
             
             
               411.5 
               Sanction 
             
             
               412 
               ERP 
             
             
               412.1 
               Work Order/Scope of Work (SOW) 
             
             
               412.2 
               Constraints 
             
             
               413 
               Analog 
             
             
               414 
               Sample Records 
             
             
               414.1 
               Official Record of Ownership Sample 
             
             
               414.2 
               Individual Public Claim Record Sample 
             
             
               414.3 
               Vendor Claim Record Sample 
             
             
               414.4 
               Individual Update Record Sample 
             
             
               414.5 
               Public Directory Record Sample 
             
             
               414.6 
               Original Incept Record Sample 
             
             
               414.7 
               Government Record Sample 
             
             
               414.8 
               Personal Record Sample 
             
             
               414.9 
               Personal Homepage Record Sample 
             
             
               415 
               Enterprise Summary Array 
             
             
               415.1 
               Company Record 
             
             
               415.2 
               Component Record 
             
             
               415.3 
               Division Record 
             
             
               415.4 
               Department Record 
             
             
               415.5 
               Work Center Record 
             
             
               415.6 
               Work Station Record 
             
             
               416 
               Enterprise Detail Array 
             
             
               416.1 
               Company Record 
             
             
               416.2 
               Component Record 
             
             
               416.3 
               Division Record 
             
             
               416.4 
               Department Record 
             
             
               416.5 
               Work Center Record 
             
             
               416.6 
               Work Station Record 
             
             
               416.7 
               Resource Record 
             
             
               416.8 
               Role Record 
             
             
               416.9 
               Process Record 
             
             
               417 
               Part Number Array 
             
             
               417.1 
               Part Number—UR-URL 
             
             
               417.2 
               Part Name—Name 
             
             
               417.3 
               FIG Name—Owner 
             
             
               417.4 
               View Name—Authority 
             
             
               417.5 
               Sub-Parts—Keywords 
             
             
               417.6 
               FIG Number—Path 
             
             
               500 
               Unitary Processes Architecture 
             
             
               500.1 
               Mint Real Identifier 
             
             
               500.2 
               Vendor Mint Artificial Identifier 
             
             
               500.3 
               No Authentication 
             
             
               500.4 
               Authentication By Vendor 
             
             
               500.5 
               Vendor Layers Block 
             
             
                 
               Authentication Schemas 
             
             
                 
               Authentication Products 
             
             
                 
               Privacy Products 
             
             
                 
               Security Products 
             
             
                 
               Certificates 
             
             
                 
               Federations 
             
             
                 
               Web Services 
             
             
               500.6 
               User ID/Password 
             
             
               500.7 
               Vendor Service Provider 
             
             
               500.8 
               Vendor Trust Provider 
             
             
               500.9 
               Vendor Anytime Authentication 
             
             
               500.10 
               Private Ownership Block 
             
             
                 
               Real Identity 
             
             
                 
               Real Property 
             
             
                 
               Personal Property 
             
             
                 
               Tangible Property 
             
             
                 
               Intangible Property 
             
             
                 
               Intellectual Property 
             
             
               500.11 
               Public Infrastructure Ownership Block 
             
             
                 
               Public Resources 
             
             
                 
               Public Broadband 
             
             
                 
               Public “Hot Spots” 
             
             
                 
               Public TV Broadcast 
             
             
                 
               Public Radio Broadcast 
             
             
                 
               Public Library System 
             
             
                 
               Public Mail System 
             
             
               500.12 
               Owned Systems Block 
             
             
                 
               Computer 
             
             
                 
               Monitor 
             
             
                 
               CPU 
             
             
                 
               Storage 
             
             
                 
               Peripherals 
             
             
                 
               Software Licenses 
             
             
               500.13 
               Owned Access Devices Block 
             
             
                 
               Cell Phone 
             
             
                 
               Landline Phone 
             
             
                 
               Walkie-Talkie 
             
             
                 
               Television 
             
             
                 
               Radio 
             
             
                 
               Ham Radio 
             
             
                 
               Broadband Receiver 
             
             
                 
               GPS Reader 
             
             
                 
               Satellite Dish 
             
             
               500.14 
               Access Vendors Block 
             
             
                 
               Phone Company 
             
             
                 
               Cable Company 
             
             
                 
               Wireless Company 
             
             
                 
               Cellular Company 
             
             
                 
               Satellite Company 
             
             
                 
               Internet Company 
             
             
                 
               Digital Audio Company 
             
             
                 
               GPS Company 
             
             
                 
               Broadband Company 
             
             
                 
               Mail Delivery Company 
             
             
               500.15 
               Access Means Block 
             
             
                 
               Phone Number 
             
             
                 
               User Account 
             
             
                 
               Wireless Number 
             
             
                 
               Cellular Number 
             
             
                 
               User ID 
             
             
                 
               Name 
             
             
               500.16 
               Service Block 
             
             
                 
               Service Contracts 
             
             
               500.17 
               Vendor Infrastructure Ownerhsip Block 
             
             
                 
               Television 
             
             
                 
               Radio 
             
             
                 
               Broadband 
             
             
                 
               Telephone 
             
             
                 
               Internet 
             
             
                 
               Cable 
             
             
                 
               Optical Fibre 
             
             
                 
               Cellular 
             
             
                 
               Microwave 
             
             
                 
               Satellite 
             
             
               500.18 
               Rented.Proprietary Access Devices Block 
             
             
                 
               Rented Access Hardware 
             
             
                 
               Proprietary Cell Phone 
             
             
                 
               Proprietary RF Receiver 
             
             
                 
               Proprietary Cable Receiver 
             
             
                 
               Proprietary Satellite Receiver 
             
             
                 
               Proprietary Broadband Receiver 
             
             
                 
               Proprietary Digital Audio Receiver 
             
             
                 
               Proprietary GPS Receiver 
             
             
                 
               Proprietary Data Receiver 
             
             
                 
               Rented Identity 
             
             
                 
               Rented Web Software Services Access 
             
             
                 
               Rented Web Service Product Access 
             
             
                 
               Rented Web ServiceTime Access 
             
             
                 
               Rented Web Service Data Storage Access 
             
             
               500.19 
               Access Vendors Block 
             
             
                 
               Identity Federations 
             
             
               500.20 
               Access Means Block 
             
             
                 
               Federated Identity 
             
             
                 
               Vendor Control of Private Identity 
             
             
                 
               Vendor Control of Private Information 
             
             
                 
               Vendor Control of Private Devices 
             
             
                 
               Vendor Between Citizen and Govt 
             
             
               500.21 
               Federated Web Services Block 
             
             
                 
               Communication Services 
             
             
                 
               Authentication Services 
             
             
                 
               Privilege Management Services 
             
             
                 
               Security Services 
             
             
                 
               Application Services 
             
             
                 
               Directory Services 
             
             
                 
               Hosting Services 
             
             
                 
               Search Services 
             
             
                 
               Membership Contract 
             
             
                 
               End User License Agreement 
             
             
                 
               One-Sided Terms and Conditions 
             
             
                 
               Hidden Terms and Conditions 
             
             
                 
               Personalization 
             
             
                 
               Content Pre-Screening/Filtering 
             
             
                 
               User Profiling and Data Mining 
             
             
               500.22 
               Citizen 
             
             
               500.23 
               Government 
             
             
               500.24 
               Middle-Man 
             
             
               501 
               Forms 
             
             
               501.1 
               Identity Forms 
             
             
               501.2 
               Unitary Entity Identity Statement 
             
             
               501.3 
               Unitary Event Ownership Statements 
             
             
               501.4 
               Unitary Event Identity Statement 
             
             
               502 
               Tuple Forms 
             
             
               502.1 
               Tuple Statement 
             
             
               502.2 
               Unitary Tuple Statement 
             
             
               502.3 
               N-Tuple Statement 
             
             
               502.4 
               Unitary N-Tuple Statement 
             
             
               503 
               Event Statement Forms 
             
             
               503.1 
               Unitary Forms 
             
             
               503.2 
               English Language Forms 
             
             
               504 
               Event Description Forms 
             
             
               504.1 
               Single Entry 
             
             
               504.2 
               Multiple Entry 
             
             
               505 
               Programmatic Forms 
             
             
               505.1 
               Resource Planning 
             
             
               505.2 
               Operations Sequencing 
             
             
               505.3 
               Binary Pairs 
             
             
               506 
               Diagrammatic Forms 
             
             
               506.1 
               Tree Diagram 
             
             
               506.2 
               Critical Path Method Diagram (CPM) 
             
             
               506.3 
               Cluster Diagram 
             
             
               506.4 
               Map Diagram 
             
             
               507 
               Menu Forms 
             
             
               507.1 
               Prior Art Menus 
             
             
               507.2 
               Prior Art Menu Expressions 
             
             
               508 
               Menu Synthesis 
             
             
               508.1 
               Twelve Programs—105 Menu Objects 
             
             
               508.2 
               One Platform—25 Menu Objects 
             
             
               509 
               Simplified Menu Forms 
             
             
               509.1 
               Program Objects 
             
             
               509.2 
               Menu Objects 
             
             
               509.3 
               Navigation Objects 
             
             
               510 
               Shell With Simplified Menu Forms 
             
             
               511 
               Present Invention Owner Self-Mint Flow Diagram 
             
             
               512 
               Current Embodiment Flow Diagram 
             
             
               513 
               New Web Services Vendor Mint Model Flow Diagram 
             
             
               514 
               Worst Case Future Vendor Mint Model Flow Diagram 
             
             
               515 
               Owner System Individual Ownership Direct Access 
             
             
               516 
               Renter System-Vendor Ownership-Vendor Control 
             
             
               600 
               Unitary Apparatus 
             
             
               600.1 
               COTS or Open Source Computer System 
             
             
               600.2 
               Event Data 
             
             
               600.3 
               Navigation Bar With Links 
             
             
               600.4 
               Shell 
             
             
               600.5 
               COTS or Open Source Spreadsheet Software With 
             
             
                 
               Search and Hyperlinks 
             
             
               600.6 
               COTS or Open Source Database Software 
             
             
               600.7 
               COTS or Open Source Shell Software With Simple Tools 
             
             
               600.8 
               COTS or Open Source Predicate Logic Software 
             
             
               600.9 
               COTS or Open Source Web Page Software 
             
             
               600.10 
               COTS or Open Source Browser Software 
             
             
               600.11 
               Tabular Architecture Rows and Columns 
             
             
               600.12 
               Infinite Integration With UR-URL Identifier Method Scope 
             
             
               600.13 
               Infinite Range With Infinite UR-URL Identifier Method Scope 
             
             
               600.14 
               Finite Integration With Finite Identifier Method Scope 
             
             
               600.15 
               Variable Relational Tables 
             
             
               600.16 
               Finite Range With Finite Identifier Method Scope 
             
             
               600.17 
               Variable Columns 
             
             
               600.18 
               Frames With and Without Content 
             
             
               600.19 
               Access 
             
             
               601 
               Unitary Shell 
             
             
                 
             
           
        
       
     
   
   DETAILED DESCRIPTION OF THE INVENTION 
   Table of Contents
         Introduction
           Overview   Statements of Principles   Unitary Event Information Architecture   Overall Structure and Function   Unitary System Components   Example of Unitary Identity Applied   
           Operation—Main Embodiment
           How To Make A Model of Everything   How To Make A New Net With New Network Information Architecture   How To Make An Operating System Information Architecture   How To Make An Event Oriented Programming Language   
           Alternate Embodiments       

   INTRODUCTION 
   Overview 
   It isn&#39;t immediately obvious how an inventory control database and human resources database could have the same information structure as the financial transaction database and the document knowledge base. At the objective level these resources seem to be very different with widely differing properties and applications. But in abstraction everything in an information system—every file, every folder, every document, every record, every activity, every system, every object—every asset—is an event that can be listed and directorized with eight universal terms of description common to all resources ( FIG. 34 ). Integration and interoperability, both internally and with clients and partners, depends on such correspondence in data structures and formats. The defining criterion is ownership, the cohering basis is incept identity, and UR-URL relative referential geotemporal coordinates are universal resource identifiers for all users and all uses. Identity is the platform. 
   The same architecture works for personal and civic systems too, but with six terms ( FIG. 33 ). Value and distinction lie in breadth of public scope, not depth of private detail. The resultant directory looks like a big phone-book-like list of links to everything everyone needs to find in a simple table that everyone knows how to use. What you want is what you get 
   Statements of Principles 
   Unitary Technology—The Governing Principle
         “Every description of the scene of an event or of the position of an object in space is based on the specification of the point on a rigid body (body of reference) with which that event or object coincides. This applies not only to scientific description, but also to everyday life.” 24          

   Principle of Conservation; Conservation Laws applied and extended
         1. Principle: Law of Conservation of Matter   2. Principle: Law of Conservation of Energy   3. Principle: Law of Conservation of Charge   4. New: Law of Conservation of Ideas   5. New: Law of Conservation of Events In Spacetime       

   Unitary Reference Architecture—Evolution of Relational Database Principles applied
         1. Principle: Use unique identifiers.   2. General: Use symbolic codes applied uniquely as identifiers.   3. Specific: Use real identity properties as codes applied uniquely as identifiers.   4. Common: Use real plane coordinate location address properties as unique identifier codes.   5. Advanced: Use relative three-dimensional location addresses as unique identifier codes.   6. New: Use real relative four-dimensional incept location addresses as unique identifier codes.       

   Unitary Identity Reference Architecture 
                                                    One Term   URA = XYZT/gt/incept [EVERYTHING]        One Application:   Apply relative spacetime geo-temporal event incept           coordinates to information science as information           system identity primary key.        One System:   Model of Everything = XYZT/gt/incept [ALL]            Unitary Ontological Reference Architecture              One Identity   All Events [ALL]        One Condition   Events [EACH/EVERYTHING]           Event Assertions            Principle            Transaction           Event Objects            Person            Property                    
Premises
         1. The universe is infinite.   2. The universe is a closed system, that is, the set of constituents comprising the known universe is finite.   3. Conservation laws are adopted—the total amount of matter and energy in a closed-system remain constant.   4. The Law of Conservation of Ideas is defined as correlated.   5. Symmetry applies between objects and assertions that formalize agreements about objects.   6. The Law of Conservation of Spacetime is considered and initially defined as both finite and expanding.
 
Postulates
       
   1. Everything is an event. 
   2. Everything is connected to everything else. 
   3. Everything is by agreement. 
   4. The event is the unitary identity. 
   5. The unitary identity is the entity 
   6. The identity is the identifier in the Model of Everything. 
   7. The identity is the unitary reference architecture. 
   8. The unitary reference architecture is the network. 
   9. The unitary ontology is a symmetrical self-organizing system. 
   10. The unitary Principle is the Law of Conservation of Events in Spacetime. 
   Relativity and Information Science 
   Theory of Relativity
         1 Each point in spacetime is called an event. 23  
           1.1 Everything that is and that happens is an event with identity.   1.2 Event scenes are comprised of coincident objects and assertions.   1.3 An event description is an assertion of object relation within a referential system.   1.4 The term event is defined as a system of intersecting objects conjoined by common assertion of location relative to a point on a rigid referential body in space at a time certain.   
           2 Any object (such as the center of the solar system) is a suitable frame of reference; 23  
           2.1 The term object is defined as an occurrence of one or more points of conjoined artifact mass.   2.2 An object is a system of related object properties.   2.3 An object event is a system of related object assertions of object properties.   2.4 A system is an object of related object identities.   2.5 A system event is an assertion of relation of object identities.   
           3 And the motion of any object can be referred to that frame. 23  
           3.1 nternational Geotemporal Standard frames of reference.   3.2 Velocity=zero and distance=zero at relative event location at time certain.   3.3 Event object=XYZT/gt/now   3.4 Unitary event object=XYZT/gt/incept   
           4 Every particle or object in the universe is described by a so-called world line that describes its position in time and space. If two or more world lines intersect, an event or occurrence takes place; if the world line of a particle does not intersect any other world line, nothing has happened to it, and it is neither important nor meaningful to determine the location of the particle at any given instant. 23  
           4.1 The term event represents the same-place same-time intersection of world lines of objects, and is comprised of assertions of constituent properties of identified objects and their relation.   4.2 The term event object is defined as the aggregation of related object assertions, characterized as inclusive of the set of object properties whose intersection occasioned the event, which comprise said event&#39;s constituent properties, and which may or may not have further descriptive properties germane to the event.   4.3 The term event system is defined as the assertion of constituent event object identities and their relationship.   
           5 The “distance” or “interval” between any two events can be accurately described by means of a combination of space and time, but not by either of these separately. 23  
           5.1 The property that coheres event object and event assertion, and which constitutes event identity, is time and place, XYZT/gt.   5.2 The object relative spacetime address is the object identity. The object identity is the identifier.   5.3 The event assertion relative spacetime address is the event identity. The event identity is the event identifier.   5.4 Event object identity and event assertion identity originate when makers claim referential terms of incept.   5.5 Makers are entities, legal persons and groups, private or public.   5.6 XYZT/gt/now differentiates and unifies all objects in one space at one time.   5.7 Incept XYZT/gt/incept differentiates and unifies all objects in all time in one place—a Model of Everything.
 
Unitary Event Information Architecture
   
           1. Every event has identity.   2. Every event has origin.   3. Every event has agreement.   4. Every event has resources.   5. Every event has constituents.   6. Every event has relations.   7. Every event has systems.   8. Every event has identifiers.       

                                                         TABLE 6                   Unitary Terms of Description            ARRAY   IDENTIFIER   IDENTITY   ORIGIN   AGREEMENT   CONSTITUENT   SYSTEM   RESOURCE   RELATION               EXPRES-   Address   Element   Condition   State   Category   Domain   Class   Union       SION       ASPECT   Uniqueness   Representation   Inception   Legitimacy   Composition   Orientation   Eligibility   Context       PURPOSE   Differentiation   Designation   Ownership   Instantiation   Classification   Integration   Utilization   Operation       SET   Record   Register   Ontology   Concordance   Taxonomy   Architecture   Pool   Model       LOGIC   Has UR-URL   Has Name   Has Owner   Has Authority   Has Keyword   Has Path   Has Profile   Has Activity               Note:       Table 6 data is represented in FIG. 31 Matrix of Ontological Terms            
Overall Structure and Function
 
   Items  200 . 1 - 6  comprise components of a global network of information communication systems. The components of the present invention are identified as sub-components of Unitary Technology, the name that expresses the universal utility of the main embodiment, Unitary Reference Architecture  100 . Further sub-components  101  through  106  comprise alternate functional embodiments that extend its utility. Infrastructure Components are illustrated in  FIG. 6 . 
   Unitary System Components 
   
       
       
         
             200 . 6  Economic Infrastructure: Principles of economics, exchange systems, metrics, markets, financials, communication systems, the Internet, the telephone system, media, devices, hardware and software 
             200 . 5  Process Infrastructure: Business methodologies, production systems, delivery systems, supply chain networks, media, devices, hardware and software. 
             200 . 4  Physical Infrastructure: All people, all property; all places, ideas, artifacts, objects, assertions; everything. 
             200 . 3  Information Infrastructure: Language, classification, representation, media, devices, hardware and software. 
             200 . 2  Civil Infrastructure: Principles of democracy, self-representation, ownership, rules, values, norms. 
             200 . 1  Information Architecture: Unitary Reference Architecture Universal Resource Identifier (URI)
             100  Unitary Reference Architecture—URA Self-service single sign-on identity for all users and all uses.
               101 Event Identity Model—Unitary Identity Architecture (UR-URL Identifier Method)     102  Event Information Model—Unitary Event System (List of Everything)     103  Event Object Model—Unitary Event Field Modeling Method (Table of Everything)     104  Event System Model—Unitary Event Integration and Network Architecture (Database of Everything)     105  Event Process Model—Unitary Event Programming (Platform for Everything)     106  Unitary Event Model—(Web Portal to Everything)         
         
       
     
  
   Taken in aggregation, this high-level list of components is intended to represent the full spectrum of scientific principles and technology currently governing the interpretation and application of identity as essential information architecture. Each domain of systems uses identity for varying purposes and applications. Systems within each domain have different architectures. There&#39;s overlap, but more difference than commonality in the numbering schemas. URA unifies all schemas and purposes with one method. 
   Example of Unitary Identity Applied 
   One Entity&gt;Many Claims 
   One Claim&gt;Many Entities 
   Let&#39;s imagine a unitary system contains all the public property records for Podunk County. You want to use the system to find a house to buy. You go to the search utility, enter the location coordinates for the neighborhood in question, and the search results screen pops up. It lists all the houses by street and owner, either way, or by keywords in the description. Each home may have more than one listing, more than one database address primary URA ID key (UR-URL). 
   The county property records will all be owned by, and show as the maker, PDC. The link to more information directs the browser to the PDC homepage. The primary key for each property would have as the URA an XYZT that has the latitude, longitude and elevation as the first three sets of code variables, and then the date and time of sale as the last set. Because this is an official public record, the format for the digits might be fixed; a “standard” for all addresses would probably use the US Geological Survey (USGS) system. This URA and record might look like:
         THE OFFICIAL RECORD OF OWNERSHIP SAMPLE— FIG. 66 
           UR-URL NO2649095.WO8006333.E00040.10172000.133000   Name Record of single-family home ownership   Owner PoDunk County Tax-Collector   Authority Deed or Title Company; Has artifact   Keywords Instantiation Incept date/time/loc at closing; Has desc   Path Web: pdc.fl.gov/records/titles   
               

   The owner might also register the property in preparation for selling it. They want to be known as the owner, they want to be visible and locatable. So they register. The ID would be the same, because URA could use the standard format for the event object house. This is what would be same/different
         INDIVIDUAL PUBLIC CLAIM SAMPLE— FIG. 67 
           UR-URL NO2649095.WO8006333.E00040.10172000.133000   Name NO2649095.WO8006333.E00040.10172000.133000   Owner Public, John Q. and Public, Jane Q.   Authority Web: pdc.fl.gov/records/titles   Keywords Claim: Incept date/time/loc at closing; Has title, Joint   Path Web: jqpfamily/homepage   
               

   The real estate company might also register the same house on a commercial site. They don&#39;t want people to know who owns the house or where it is. They want the users to come to them. Their record would have a totally different initial URA based not on the piece of property, but based on the Real Estate Company&#39;s URA. They would not be registering the house as property, because they don&#39;t own it. They&#39;re registering the listing. The listing is their property and resides at their location in a file folder in the file room. The listing would look like this:
         VENDOR′S CLAIM SAMPLE— FIG. 68 
           UR-URL S12345675.W22222333.E00050.04012003.108300   Name Listing for single-family home   Owner Good Realty Company Inc   Authority Listing 3333-456   Keywords Fl pool home; gated community; water view; 3% to selling broker; 3br; 2ba; FR; Bonus rm; 3CGrg; owner will carry 2nd   Path Web: goodrealty.com/listings/homes/florida.htm   
               

   Part of the contract with the realtor might stipulate that John add the realtor&#39;s link to his own registration record, or he would maybe set a flag in his mailbox that “read” the email and if it matched the keywords “house” “for sale,” the email would go automatically (redirected) to the realtor and not John. Realtors don&#39;t like it when owners snag buyers directly. So John would go to the site, click on “Update record” and add the realtor&#39;s http to the LINK field. Now, John&#39;s personal record would look like:
         INDIVIDUAL UPDATE RECORD SAMPLE— FIG. 69 
           UR-URL NO2649095.WO8006333.E00040.04012003,108300 (? T)   Name NO2649095.WO8006333.E00040.10172000.133000   Owner Public, John Q.   Authority Web: pdc.fl.gov/records/titles   Keywords Now date/time/loc at record registration; Has agent, Good Realty   Path Web: goodrealty.com/listings/homes/florida.htm   
               

   Finally, the telephone company may also assign a URA “phone number” for the house. ATT “owns” the phone numbers now, they are the mint. They issue identifiers—phone numbers. Their method of formatting GPS signals might use an abbreviated system that&#39;s easier for users to remember. Instead of the whole standard longitude, they might use an alternate system like Geo Domain. It generalizes regions, like area codes, but they make sense to the location relative to the basic “standard.” Imagine date formats, you can use 04/02/02 or 02APR02 and they mean the same thing, they&#39;re just different formats. And you can change the format at a click, convert. This means they are the same but different. This one uses: “minutes.degrees.tendegrees.geo.” 
   Also, if it&#39;s a device, it may be fixed or mobile. The time signature is a constant string of location signals that correspond to where the device is. Technically, every minute (or billing increment) is a transaction at certain location. Transactions are grouped into units of “calls” between locations and numbers. So the phone company&#39;s internal database and directory record might look like this, if they used the Geo Domain method:
         PUBLIC DIRECTORY RECORD SAMPLE— FIG. 70 
           UR-URL 2e33n.5e5n.2e10n.37e47n.1e5n.10e20n.E00040.10172000.133000 (alternate referential format UR-URL)   Name John Q. Public   Owner Phone Co   Authority Web: pdc.fl.gov/records/titles (which references maker and location)   Keywords Web: jqpfamily.com/communication/access; Constraint, No solicitation   Path Web: phoneco.com (where this record is)   
               

   John Smith was originally registered as a dependent citizen entity at the time of his birth, which was witnessed by the hospital and authenticated by the local governmental agency that maintains vital statistics. His incept record would include standard information:
         ORIGINAL INCEPT CLAIM SAMPLE— FIG. 71 
           UR-URL S00236666.E55555555.E00010.08011951.233022   Name NameFirst, John, NameMiddle, Q., NameLast, Public   Owner Makers, Mary Q. Public nee Smith and Jack Q. Public   Authority Witness, Web: goodhospital.com/records/contact.htm   Keywords InceptLoc, S00236666.E55555555.E00010; Incept D/T 0.08011951.233022   Path Web: pdc.fl.gov/deptvitalstatistics/(where the authenticating artifact is)   
               

   John Smith is an “object” in the USGOV system. This could be his personal URA for everything, if he wants. It&#39;s linked to a county or hospital registration of live birth or personal affidavit that “authenticates” his existence. The rest of the government&#39;s internal database fields can be anything, but this would be the public record displayed. It simply acknowledges that John Smith is a person with a name and a link. It is the URA for everything official. 
   This is not a system anyone can see or get into. It is the USGOV and it is behind firewalls. The public part of the public record is the name and URA ID. The USGOV records and other regional public entities are also registered and listed in the pubic domain with the following kind of entry:
         US CENSUS RECORD SAMPLE— FIG. 72 
           UR-URL S00236666.E55555555.E00010.08011951.233022   Name John Q. Public   Owner US Census Bureau   Authority Web: pdc.fl.govideptvitalstatistics/(where the authenticating artifact is)   Keywords Has (name, relation, gender, DOB, Latino Y/N, race)   Path Web: us.gov/census/(where this record is)   
               

   John Smith can also register himself, and this main person entry is what he chooses to reveal to the world. The URA is public. The information associated with it is limited to what the maker wants to put in the public record. Most people like to be in the phone book. They want to be found. Registering your self as an entity is a prerequisite to registering your property, but ATT can register your phone number and name as part of a whole phone book of people&#39;s phone numbers and names because they “own” the mint and information in it. Users can request exclusion, just like with regular user-owned personal data today.
         PERSONAL RECORD SAMPLE— FIG. 73 
           UR-URL NO2649095.WO8006333.E00040.10172000.133000 (chooses home UR-URL)   Name John Q. Public   Owner John Q. Public   Authority Affidavit   Keywords No solicitation   Path None   
               

   Or John Smith might want to be found, so he might add to his record “Link” the device ID-phone number, or his homepage, or his business, whatever he wants. But just because the link is there and people can find his homepage, does not mean they can get into his personal private data behind that homepage. It might just have a “log on” screen for family members to see the photo&#39;s page, or a “sign-up here if you want me to receive your email” where he makes the people give HIM information before he&#39;ll accept the email. Whatever, this page is what he wants the world to see and know about him. His listing in might look like this:
         PERSONAL HOMEPAGE RECORD SAMPLE— FIG. 74 
           UR-URL NO2649095.WO8006333.E00040.10172000.133000 (chooses home UR-URL)   Name John Q. Public Homepage   Owner John Q. Public   Authority Affidavit   Keywords PMP, CPF, project management; Resume: Web: jqpfamily.com/resume.htm   Path Voice/data Web: jqpfamily.com/communication/access (his routing program)   
           SEARCH RESULTS SAMPLE— FIG. 75 
           If someone wanted to find John Smith&#39;s phone number, they could search on the name John Smith and the following results would be displayed:
               Search: John Q. Public
                   UR-URL NO2649095.WO8006333.E00040.10172000.133000   Homepage: Web: jqpfamily.com/login.htm   Phone Co: Web: phoneco.com/jqpfamily.com/login.htm   PDCFL: Web: pdc.fl.gov/records/titles.index.htm   
                   Search 123 Palmy Way, City of Warmtown, County of Po Dunk
                   UR-URL NO2649095.WO8006333.E00040.10172000.133000   PDCFL Web: pdc.fl.gov/records/titles.index.htm   Owner Web: jqpfamily.com/login.htm   Agent Web: goodrealty.com/listings/homes/florida.htm   
                   
               
               

   The beauty of a semantic web such as this is it anticipates the messy naturally evolving cross-referenced linkages across and between entities, domains, contexts, and applications around the world and in the universe at large. All exist harmoniously side-by-side in URA. At each location, unless you have the password and authorization to get in, you can&#39;t find out anything except his name and the URA number and the fact that he is listed as an element in each of these proprietary databases. If it is the ATT site, it would go right to the phone number URA and it would be displayed or say Unpublished, just like a paper phone book. If you went to the IRS site, it would not even let you search. If you go to county records homepage, you can search on name or URA of the property or the owner and get one record, the record you&#39;re looking for. 
   If they go to the realty website, there is only information about the house and the phone number of the real estate agent. If the searcher really wanted to, just like today, they could go to the county records and find the house, then go to the ATT site to find the phone number, or to the owner&#39;s site and find them or their agent. The point is to automate a public system, not make private systems public. 
   Information Architecture 
   An existing upgrade proposal for web infrastructure is the addressing method Geo Domain, which stipulates use of DNS to encode latitude/longitude for any element in a hierarchical n-tree. This is an alternate to the lon/lat architecture we use for navigation, and it has a different way of dividing up the grid: Geo.Domain Method:25 ibid Minutes.Degrees.Tendegrees.Geo, e.g, 37e47n.1e5n.10e20n.geo 
   Digital Earth and W3C suggest identification using geographical coordinates in an abbreviated format. Unitary Technology is capable of accommodating this and all GPS formats. It is anticipated that ultimately one standard format will be adopted worldwide for telephony, and this one seems to have the most flexibility. 
   The examples shown are not intended to specify formats or specific code variations for particular applications. Rather, they seek to illustrate the flexibility with which individuals can manage the way information about them is represented in the systems of those they chose to do business with. 
   Operation 
   Main Embodiment 
   Ordinary Everyday Person 
   The present invention assumes current technology as would be known to an everyday person of reasonable intelligence and education that has a library card, computer, surfs the web, and watches the Discovery Channel. Unitary Reference Architecture is fundamental technology. It&#39;s big but simple. 
   Assumptions 
   URA is an combination identity-identifier-addressing-indexing business method for information system integration and control, and is not dependent on medium, just like “information” isn&#39;t. It&#39;s harder to do this manually, even though you can. An ordinary everyday person would buy a personal computer, big or small, doesn&#39;t matter, and select an operating architecture—preferably one that&#39;s cheap or free like Unix or Linux, but Windows and Mac are OK too. 
   Common off the shelf components are assumed, so, it&#39;s reasonable to further assume no special understanding of computers or programming is necessary. The ordinary everyday person may know a little, or a lot, but whenever they hit a point where they need help, they get it, or hire a professional. Assumption of prior art functionality is captured in global terms and common narrative both for simplicity and because the present invention really is that simple. The way you do anything better, if it has to do with identity, is to take its old system of identifiers with limited intent, less capacity, and no universality, and instead use Unitary Reference Architecture and get unlimited unitary integration interoperability opportunities. 
   How to Make a Model of Everything 
   1. Reference Architecture 
   
       
       
         
           Take a piece of paper and draw six columns. Leave the first column blank.
 
2. Identity
 
           In the second column, list all the things you know about. That&#39;s all the people, all the places, all the stuff, and all the ideas. It doesn&#39;t matter if you get everything the first time, you can add more later. You have to do that anyway, as new stuff happens. For now, just list all the names of individual things you can think of. Identity means what it is, its name.
 
3. Owner
 
           In the third column, put the name of the person who owns each thing. Everything has an owner. People own themselves. Event ownership is what representation is all about. If it&#39;s a mountain or something you&#39;re not sure about, the country where it is probably owns it. Put them on the list. You can list great ideas using the inventors or discoverers as the owners. Everything known can be listed as an event. Even stuff that happens is owned by the people there. There would be lots of owners for the event “Super-Bowl.” You might want to have just “Super-Bowl Broadcast” which is probably owned by the television network. Same thing with stuff. For your first version, you should probably have a few big mountains rather than a million little molehills. Just a suggestion. It&#39;s still a Model of Everything, just bigger clumps. You can break out the detail later.
 
4. Authority
 
           In the fourth column, put the name of the instrument or agency that corroborates ownership. Just because someone claims ownership doesn&#39;t make it so. This could be a deed, or birth certificate, or contract, or the Department of Vital Statistics, or county that maintains property records.
 
5. Keywords
 
           In the fifth column, put some keywords and phrases that describe the thing. If you want, you can just copy other lists of things like dictionaries and atlases. If you&#39;re using a computer, you can load the words in the second column in the first place. Saves a lot of time listing basics. 
           Also in this column, if it&#39;s a thing, put the address where it is. If it&#39;s a person, put the address where s/he was born, and the date and time they were born (or, the date and time the thing was bought, or made, or began or was discovered)
 
6. Path
 
           In the sixth column, put the path or address of each thing&#39;s governing system, the system it&#39;s in—the source of applicable standards and protocols.
 
7. Unique Identifiers
 
           Now we get to the part where it&#39;s particularly helpful if your list is in a spreadsheet or relational database. You can do this manually, but it will take longer. Your list is probably pretty big. Look at a map or use a hand-held GPS navigation tool to find the locational coordinates that match the physical addresses in column five. You could do this part faster with software package, probably inexpensively. Put these coordinates in the first column, and put the name of the GPS system in column six. Then, convert the incept dates and times to number-strings, and put those new numbers at the tail end of the first numbers in the first column. Even though today&#39;s GPS isn&#39;t exact to millimeters, it doesn&#39;t matter. All you need to know is one exact reference. Everything else is an offset. Use a measuring tape if you have to. 
           This is the identity address, or “identifier” or ID—the UR-URL. This is important. People and things have real incept identity. The real identity address is used as the UR-URL identifier. Just don&#39;t call these numbers identity. They are identifiers. It&#39;s a legal thing. All identifiers in a system must be unique, and these are. We&#39;re using the real Unitary Reference Architecture as our database reference architecture. We all know the math, so uniqueness is naturally maintained without central mints. 
           Once we have UR-URLs for everything, we can do anything. Like make more lists of stuff in groups. But we can also do a whole lot more.
 
8. Cross-References
 
           Compare all the stuff&#39;s keywords in column five, and every time there&#39;s a match, put the UR-URL from column one of the thing that matches into the Keyword column. This will be lots of cross-references. The universe gets pretty messy after a while. So do databases. If the Keyword column gets too full, you can group them into some other columns.
 
9. Ontology
 
           If you have a classification system, you can use that with the keywords to organize stuff according to things like science or public records or things that are red. Whatever. But the organizing only comes when someone wants to find something specific. The rest of the time, this is just a list and the basic order in its raw form is location, based on the number order of the UR-URLs.
 
10. Universality
 
           If you want, you can put in some other columns, like maybe the code string that makes an elemental image or unitary waveform of the thing, but that would only be needed if you wanted to replicate it. That&#39;s not something you&#39;re probably going to do, so these few columns are pretty much all you need for a basic Model of Everything. You have all the stuff and all the people, and where there is ownership, a cross-link between their identifiers. 
           This is a Model of Everything. The reference architecture is the network. If anything new happens, it already has identity ready and waiting. Just use the identities as identifiers and add them in. That&#39;s all there is to it.
 
11. Product
 
           It&#39;s really just a big Model of Everything and who owns it and where it is, cross-referenced to everything else—one set of identifiers in one system that&#39;s already real, already verifiable, already a matter of public record. The thing that&#39;s new is who owns and controls access to the information. Here, like in life, makers do. Self-service identity makes digital self-representation possible.
 
How to Make a New Net with New Network Information Architecture
 
(1) Construct a model of |everything| ( 1000 ) by creating a unique ur-url real identity-identifier for each event according to the steps
 
           a) claim ownership of a real event as is common everyday practice in the public domain 
           b) identify the real event by name and/or symbols 
           c) claim a real address of said real event 
           d) claim a real event incept time of said real event 
           e) relate term symbol “t” to “time” as is everyday practice 
           f) relate the real event incept time value to symbol “t” 
           g) select any standard referential system and set of referential protocols from numerous standard referential systems commonly used with mathematical constructs and/or georeferencing applications 
           h) relate term symbols “x”, “y”, and “z” to three dimensional vector coordinates as is everyday practice 
           i) relate coordinate terms “x”, “y”, and “z” with terms “latitude”, “longitude”, and “elevation” respectively, as is everyday practice 
           j) apply selected standard protocols to determine real three-dimensional vector coordinate values of the real event address 
           k) associate said real event address values with real three-dimensional “xyz” vector coordinates corresponding to said real event address 
           l) concatenate values “x” and “y” and “z” and “t” corresponding to said real event address, resultant “xyzt” combination comprising the unique ur-url real identity-identifier, and 
           m) assign said unique ur-url real identity-identifier to said real event 
           n) claim relation of said unique ur-url real identity-identifier to said real event as is common in everyday identity instantiation practice in the public domain 
           o) secure official authentication as is common everyday practice 
           p) publish claim to ownership of event identity as is common everyday practice 
           q) repeat steps (a) through (q) for each event in all events.
 
(2) Construct a zero-dimensional model of |everything| ( 101 ) comprising constructing table apparatus with tabular architecture, column and rows, and making one column, and making an infinitely extensible number of rows, and cohering the infinitely extensible number of rows with one system of said unique ur-url real identity-identifiers according to the method and steps of (1), and placing one unique ur-url real identity-identifier for each event in all events, one per row in column one, such that each point of zero-dimension event potentiality in spacetime is represented by the particular ur-url with which it coincides.
 
(3) Construct a one-dimensional model of |everything| ( 102 ) according to the steps according to (2) with the addition of a second element comprising constructing a zero-dimensional model of |everything| according to the method and steps of (2), and making a second column, and listing in the second column names which represent identity of each real event claimed according to the method and steps of (1), and placing names one per row in correspondence with the particular ur-url real identity-identifier with which its claimed real address coincides, and continuing until each real named event is associated with the particular ur-url real identity-identifier with which it coincides according to the method and steps of (1).
 
(4) Construct a two-dimensional model of |everything| ( 103 ) according to the steps according to (3) with the addition of steps comprising employing commercial off the shelf or open source computer system, and using commercial off the shelf or open source spreadsheet software with search and hyperlink functionality, and making a one-dimensional model of everything according to the method and steps of (3) and adding columns, and assigning to additional columns, beyond ur-url column and name column, column field labels selected from the group consisting of owner, authority, keyword, path, profile, activity, and classifying named event properties with ontology terms, and describing named events by inserting particular values and properties in row cells corresponding to field labels for each named event, and creating hyperlinks between instances of particular events according to common everyday spreadsheet usage, and continuing until each named event is classified and/or described.
 
(5) Construct a three-dimensional model of |everything| ( 104 ) comprising the steps according to (4) with the addition of steps comprising employing commercial off the shelf or open source database software, and making a two-dimensional model of everything according to the method and steps of (4) and adding relational tables, and updating original real event records with new real-time event data, and using original claimed incept real xyz for each updated event, and using real event update activity real time as value related to “t”, and concatenating new xyzt real event real identity-identifier ur-url, and assigning the new xyzt real event real identity-identifier ur-url to real event update activities in corresponding relational tables, and integrating any and all relational tables that share same ur-url real identity-identifier terms.
 
(6) Construct a four-dimensional model of |everything| ( 105 ) comprising the steps according to (5) with the addition of steps comprising employing commercial off the shelf or open source shell software with simple tools, and employing commercial off the shelf or open source predicate logic software, and making a three-dimensional model according to the method and steps of (5) containing said named real events relating to original event term identities defined according to the method and steps of (1) and which identities were related to all other real event identities according to the method and steps of (2) and which were listed by said real identity name and said real ur-url real identity-identifier according to the method and steps of (3) and which were described and classified according to the method and steps of (4), and which were associated in relational tables according to the method and steps of (5), and employing said ur-url real identity-identifiers as relation variables in standard programmatic forms, and creating programmatic sentences by specifying “words” of consisting of said ur-url real identity-identifiers that refer to and invoke by hotlink original terms and definitions contained in corresponding real event records, and creating sentences in english or any language by specifying said ur-url real identity-identifiers that refer to and invoke by hotlink original english or other language terms and definitions in corresponding real event records, and drawing pictures with “palettes” of said ur-url real identifiers that refer to and invoke by hotlink original programmatic objects contained in corresponding real event records, and assigning said ur-url real identity-identifiers to real hard drive and operating system event addresses, and creating activity schedules by linking real named event&#39;s predecessor and successor ur-url real identity-identifiers.
 
(7) Construct an all-dimensional model of |everything| ( 106 ) comprising the steps according to (6) with the addition of steps comprising employing commercial off the shelf or open source web page software with simple tools, and employing commercial off the shelf or open source browser software, and applying laws, rules, norms, conventions, and legal requirements corresponding to everyday analog institutions and instantiation processes, and making a four-dimensional model according to the method and steps of (6), and employing simple web page software to create website page text and graphics, and employing simple browser software to access website page text and graphics, and recording owned property and identity ownership claims according to the method and steps of (1) for instantiating new real event identity, and operating a web portal front end to deliver access to everything by everyone, and employing said ur-url real identity-identifiers to full benefit in place of telephone communication identity addresses, and at the same time using said ur-url real identity-identifiers in place of Internet identity-identifiers, domain addresses, and internet protocol addresses, and at the same time employing said ur-url real identity-identifiers in place of vendor account identity-identifiers, and at the same time employing said ur-url real identity-identifiers for official governance and participation process identity-identifiers owned by private citizens, and at the same time employing said ur-url real identity-identifiers in any and all capacities and instances where identity-identifiers are employed, and achieving universal interoperability by means of shared said system of said ur-url real identity-identifiers applied in constructs of zero to all dimensional product versions of the present invention.
 
How to Make an Operating System Information Architecture
 
           1. Take a computer off the shelf 
           2. And some C++, or any semantic specification tool 
           3. Add URA 
           4. Assign identifiers to operating instructions the same way you do now 
           5. Assign identifiers to memory storage medium the same way you do now 
           6. Assign identifiers to data events the same way you do now, but use unitary event identifiers instead of other identifier methods, for everything in the whole system 
         
       
     
  
   By using the same system of identifiers you use for event object identifiers also for memory address identifiers, you could eliminate one whole extra term—probably not as much as a thirty percent overall reduction in memory, but every byte counts. In the old computer information architecture, if you use real physical location, all the identifiers would always be unique, but they&#39;d change every time you performed routine disk maintenance. You could maybe add a rule in the old reference architecture that kept track all the changes, but usually there&#39;s just another identifier. This way you always know what and where everything is. 
   But if your operating system information architecture uses the same URA referential method, code syntax, and nomenclature as the system of URA event objects, then the principle of symmetry would be invoked to the max. At its most primitive level, the system identifier is the object identifier is the object identity when object identifier used is its real microscopic location address in the computer. Now you have operating system information architecture. 
   How to Make an Event Oriented Programming Language 
   1. Take a box of Object Oriented Programming, and a box of Model Driven Architecture 
   2. Make a Model of Everything with the system identity: Event Object Oriented Programming 
   3. Construct programmatic instructional sequences by making mini-lists of executable identifiers. 
   Object Oriented Programming automates programming by clumping frequently used lists of instructions that do frequently needed operations into one reusable functional template or “object.” Single operation objects can be connected to other objects to make bigger objects. A program is a bunch of objects in a certain order. Model Driven Architecture means bigger clumps for more functionality at higher and broader levels. Event object orientation is the next higher level of combination, followed by system event object, and unitary object. URA completes the object orientation evolution. Everything&#39;s a system object—an operation is an event object, a process is an event object, resources are event objects, terms and protocols—all event objects in one system. 
   Unitary Reference Architecture provides one unitary system of identifiers for all event objects. Writing a program is as simple as linking identifiers when the object and its identity and its location and it&#39;s assertion of utility are all referentially embedded in the unique identifier primary key code. Real referential geo-temporal mathematical coordinates are conveniently grouped and inherently indexed. The time vector provides a handy way to assign duration and sequence. Event identity inheres force and field, process and content, object and assertion and it describes, locates, differentiates, integrates, orders, directs, mutes, and controls. Unitary programming tools and techniques also apply as method and means for simulation, replication, synthesis, and molecular models of systems of all sizes and complexities. A Model of Everything provides a larger construct for modeling event phenomena in whole-systems contexts. 
   Nanotechnology. 
   Reference architecture for a Model of Everything includes very small things too. The key aspect that makes this model not just bigger but dramatically different from the many partial models and modeling techniques used today is the fact that, with URA, event objects and event assertions share the same identity, and same identifier. This principle of symmetry between analog identity and digital identifier is especially useful in controlling nano-processes. 
   Broadly speaking, agents (miniature machine agents, biological agents, information agents) are controlled by software programs that consist of identified lines of code that first define the field and then establish the terms of relationship and interaction. Then, transactional instructions are applied to produce desired results. A typical transaction would consist of an identifier, an object name or description, and an operation, which itself consists of a process step and sequence or time. An operation might be as simple as “move object from one place to another in the system,” or as complex as a group of software or machine compound objects that execute additional operations with other objects in the system. 
   A Unitary simulation would similarly define the field and establish terms of relationship and interaction. Once all points are addressed, the whole set of operating instructions would consist of a series of object addresses alone, where the address is XYZT/gt and applies to both the point and the object that occupies it along it&#39;s path of interaction. Thus, the object and the place where it&#39;s supposed to be as well as the time it&#39;s supposed to be there are all in the identifier. This is about as efficient as code gets. It concurrently leverages signaling technology by using real identity addresses as communication identifiers, plus models can be easily linked and merged without quantity constraints imposed by standard addressing methods. With huge quantities of nano-objects, every character counts. Inherent extensibility facilitates aggregation of subsections which may be constructed independently and assembled modularly. 
   Alternate Embodiments 
   Grid Computing
         Unlimited grid addresses. Unlimited relative grid addresses.       

   Blade Technology
         IBM Blade technology specifies a “fabric” of I/O addresses; URA provides fabric grid addresses, and a method of referential relative addresses.       

   Virtual Storage Solutions
         Virtual storage theory links data stored in non-contiguous physical locations and simulates unitary configuration through address/ID code structure nomenclature. URAs addresses provide system unification at the identity level, making physical location constraints not only transparent but also meaningless. What coheres a system is its primary key identity definition.       

   Wireless Communication
         In the future, mobile communication from multiple devices will connect more of us, where hard-wired infrastructure now predominates. URA provides identity for the caller, for the device, and for the transaction, thereby extending mobile wireless data capabilities for transaction management. Furthermore, URA provides a multiple-option schema for alternate telephone numbers themselves.       

   Short Message Systems
         Theoretically, anyone could set up a COM business/phone company using their own URA identity addresses as phone numbers. This is more likely in the smaller domain of messaging, however, alternate national and global systems could be established.       

   Bar Code Adhesive Strips
         With URA, individuals as well as corporations can easily track their property items with mini-lo-jack strips. Examples: personal home inventory, children, eyeglasses, pets, anything that gets lost, slap a sticky-back beeping strip with programmable address options that signals directly to the main system exactly where each and every item may be found. When the “thing” is children (“jewelry” or “accessory” tags), a national public record domain becomes a vital resource.       

   Governance, Secure “Public ID” Structure
         URA is the only national ID schema that applies universally to all citizens of the world. It contains only demographically neutral information about claims to ownership specified voluntarily by makers.       

   Artificial Intelligence
         Memory is just a stored event description. URA integrates complex systems of assertions as easily as objects. The identifier&#39;s time/location simplifies both linear and non-linear dynamics of conceptual relationship.       

   Miscellaneous Representational Whole-System Applications
         Genetic Simulation/DNA Modeling Platform; Knowledge Base Management; Traffic Control; Directories/Registries, Inventory Systems; Emergency Healthcare Profiles, Cameras that capture grid addresses as real-time address identifiers with meta data.       

   Alternate Referential Addressing Method Embodiment
         As an alternate embodiment and addressing schema for assigning referential addresses associated with a single entity or event address, UR-URL uses a modified Sierpinski carpet algorithm. In this embodiment, individual unique ID&#39;s are assigned relative to an original unique ID, in a manner that corresponds to the standard “make hole” method, starting with a square, dividing it into a 3-by-3 grid, and removing the center square; then repeating the process for each remaining square.27.