WO 99139285
`
`PC'I'lUS99!0l988
`
`The memory unit 22 also includes a gateway editor 210, by which means the user
`
`determines the rules governing the interaction of a given gateway 210 with the registers 120 of
`
`transient containers 100, governing transiting containers upon ingress and egress, and
`
`governing the interactive behavior of containers within the container to which that gateway is
`
`attached.
`
`The memory unit 22 also includes databases 900, by which means the analysis engine
`
`400, the execution engine 500, the gateways 100, the editors 110, 125, 210, 510, 610, 710, and
`
`the search interface 300, store information for later use.
`
`The memory unit 22 present invention also includes a search engine 320 by which
`
`means the user is able to locate containers 100 and, referring now to Fig. 4, containerized
`
`elements 01.
`
`The memory unit 22 present invention also includes an engine editor 510, by which
`
`means the user establishes the rules and operating procedures for the analysis engine 400 and
`
`the execution engine 500.
`
`The memory unit 22 present invention also includes a reporting means editor 610, by
`
`which means the user establishes the rules and schedule under which the information collected
`
`by gateways 200 firorn transient containers 100 will be sent to the analysis engine 400.
`
`The memory unit 22 present invention also includes a collection means editor 710, by
`
`which means the user establishes the rules and schedule under which the analysis engine 400
`
`will gathers the information collected by gateways 200 from transient containers 100.
`
`The memory unit 22 present invention also includes screen interfaces (GU1’s) 936,
`
`specifically designed to simplify and enhance the operations of the container editor 110, the
`
`gateway editor 210, and the Search interface 300.
`
`The present invention also includes a menu or button access 937, by which a user
`
`utilizing any generic computer program may access the system 10 or the container editor 110
`
`from a menu selection(s) or button(s) within that program.
`
`IO
`
`15
`
`20
`
`25
`
`The present invention also includes a computer, media or publishing network 201,
`
`comprising computers, digital devices and digital media 202 and a communication device 26,
`
`within which the components enumerated in Fig. 2 A interact, compiling, analyzing, and
`
`30
`
`altering containers 100 and the network Zfllaccording to information gathered ii-orn container
`
`registers 120.
`
`14
`
`SUBSTI
`
`SHEET ‘RULE 26
`etltloners Twit er, Inc. anciYe|p Inc. - Exhibit 1008 - Page 481
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:20)
`
`

`
`WO 99139285
`
`PCTfUS99!0l9B8
`
`The memory unit 22 also includes one or more computers 202, by which means the
`
`components of Fig 1 sustain the operations described in Fig. 2 A.
`
`The memory unit 22 also includes flat or relational databases 900, used where, and as
`
`required. Databases are used to store search phrases, search templates, system history for the
`
`analysis engine and execution engine, container levels and container, sites and digital
`
`elements, or any and all storage required to operate the system.
`
`Referring now to FIG. 2 B, a drawing of a computer network 201 as a system 10,
`
`showing a possible placement of nested containers 100, computer servers, gateways 200, on
`
`the sites described below. (Note: Fig. 2 B utilizes in parts the same numbering scheme as Fig.
`
`13 A, 13 B, 13 C, 13 D and as Fig. 2 A.)
`
`In FIG. 2 B various exemplary sites are shown, any
`
`or all of which might
`
`interact dynamically within the system.
`
`Site 1 shows a single
`
`workstation with a container and gateway connected to an Intranet.
`
`.(Individual containers
`
`may be a floppy or CD-Rom to be downloaded or inserted.) Site 2 shows a server with a
`
`gateway in relationship to various containers.. Site 3 shows an Internet web page with a
`
`container residing on it. Site 4 shows a personal computer with containers and a gateway
`
`connected to the Internet. Site 5 shows a configuration of multiple servers and containers on a
`
`Wide Area Network" Site 6 shows a workstations with a gateway and containers within a
`
`container connected to a Wide Area Network. Site 7 shows an independent gateway, capable
`
`of acting as a data collection and data reporting site as it gathers data from the registers of
`
`transiting containers, and as an agent of the execution engine as it alters the registers of
`
`transient containers. A container 100 contains the code to enable it to interact with the
`
`components enumerated in 2A, and to reconstruct itself internally and manage itself on the
`
`network 201. The code resides in and with the container in its registers and gateway
`
`definitions and controls- Additional system code resides in all sites to manage the individual
`
`and collective operation and oversight of the components enumerated in 2.4., with the specific
`
`components distributed amongst the sites according to the requirements of optimization.
`
`Referring now to Fig. 2 B 1 various exemplary sites are shown as described above in
`
`Fig. 2 B, with the addition of possible location of one or more gateway storage 205 locations.
`
`10
`
`15
`
`20
`
`Referring now to Figures 2 C through 2 H, various exemplary sites with one or more of
`
`30
`
`the logical components of the system 10 in relationship are shown. Site 1 comprises an
`
`interactive information container 100, a container editor 110, container registers _ 120, a
`
`15
`
`SUBSTITUTE SHEET_ {RULE 26
`_
`_
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:21)
`Petitioners Twit er, Inc. an Yelp Inc. - Exhibit 1008 - Page 482
`
`

`
`W0 9959285
`
`PCTIU S99.~“0 l 988
`
`container register editor I25, system-wide hierarchical container gateways 200, gateway
`
`storage 205, gateway editors 210, engine editors 510, a search interface 300. search engine
`
`320, analysis engine 400, execution engine 500, a data reporting means 600, a data reporting
`
`means editor 610, a data collection means 700, a data collection means editor 710, and
`
`databases 900, all residing on data storage means 20, utilizing the memory unit to function 22,
`
`operating on communications network 12 with a communication device 26.
`
`Site 2 comprises an interactive information container
`
`100, a container editor 110,
`
`container registers 120, a container register editor 125, system-wide hierarchical container
`
`gateways 200, gateway storage 205, gateway editors 210, engine editors 510, search engine
`
`320, analysis engine 400, execution engine 500, a data reporting means 600, a data reporting
`
`means editor 610, a data collection means 700, a data collection means editor 710, and
`
`databases 900, all residing on data storage means 20, utilizing the memory unit to function 22,
`
`operating on communications network 12. with a communication device 26.
`
`Site 3 comprises an interactive information container 100, a container editor 110,
`
`container registers 120, a container register editor 125, hierarchical container gateways 200,
`
`gateway storage 205, gateway editors 210, and databases 900, all residing on data storage
`
`means 20, utilizing the memory unit to fitnction 22, operating on communications network 12
`
`with a communication device 26.
`
`Site 4 comprises an interactive information container 100, a container editor I10,
`
`container registers 120, a container register editor 125, hierarchical container gateways 200,
`
`gateway storage 205, gateway editors 210, a search interface 300, and databases 900, all
`
`residing on data storage means 20, utilizing the memory unit to function 22, operating on
`
`communications network 12 with a communication device 26.
`
`Site 5 comprises an interactive information container 100, container registers 120, a
`
`container register editor 125, hierarchical container gateways 200, gateway storage 205, and
`
`databases 900, all residing on data storage means 20, accessed and utilized by non-resident
`
`memory unit 22, operating on communications network 12 with a communication device 26.
`
`Site 6 includes an independent analysis engine 400, execution engine 500, data
`
`10
`
`15
`
`20
`
`25
`
`collection means 700, and data reporting means 600 gateway editors 210, engine editors 510,
`
`30
`
`a data reporting means editor 610, a data collccti on means 700, a data collection means editor
`
`I6
`
`SUBSTI I U I E
`T RUL
`Pet|t|oSnle{EE|'wit er, Inc?
`Yelp Inc. - Exhibit 1008 - Page 483
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:22)
`
`

`
`WO 99339285
`
`PCT/US 9910 l 988
`
`710, and databases 900, all residing on data storage means 20, utilizing the memory unit to
`
`function 22, operating on communications network 12 with a communication device 26.
`
`Referring now to FIG. 3 A and FIG. 3 B, a block diagram of several nested information
`
`containers is shown, including examples of elements, e.g., code 1100, text 1200, audio 1300,
`
`video 1400, photograph 1500, graphic images 1600, and examples of possible container level
`
`classifications in increasing size, e.g., element 10900000, document 10800000, database
`
`10700000, warehouse 10600000, domain l0500000,a.nd continuing increasingly larger on Fig
`
`3 (B), subject 10400000,
`
`field 10300000, master
`
`field 10200000,
`
`species 10100000.
`
`Containers may be infinitely nested and assigned any ciass, super class or sub class scheme
`
`and description by the creator of the container to govern nesting within that container.
`
`In
`
`addition to digital elements, containers may also include system process and components,
`
`including containerization itself.
`
`Referring now to FIG. 3 C, a block diagram of an information container system is
`
`shown,
`
`listing, without any relationship indicated, some of the possible system components
`
`and processes, or sets thereof, that may be encapsulated as elements 01 in an information
`
`container 100. An information container 100 may include one or more of the following: any
`unique, container 100, gateway 200, output device 16, input device 24, output device process
`
`160, input device process 240, data storage device 20, data storage device process 2000,
`
`processor 18, bus 12, content 01, search process 02,
`
`interface 04, memory unit 22,
`
`communication device 26, search interface 300, search process 98, network 201, class of
`
`device, process or content 999, class of process at any unique class of device 990, process at
`
`any unique device 99, editor 110, 125, 210, 510, 610, 710, engine 320, 400, 500,
`
`containerization process 1098, or process 08.
`
`Any container may include (n) other containers, to infinity. The use of value evolving
`
`container registers 120 in conjunction with gateways 200, data reporting modules 600, data
`
`coliection modules 700, the analysis engine 400, and the execution engine 500 provides the
`
`information container 100 with extensive knowledge of the use, operation of its internal
`
`contents, prior to, during and after those contents’ residence within that container 100, and
`
`10
`
`I5
`
`20
`
`25
`
`extensive knowledge of the use, operation and contents of the system 10 external to itseif, and
`
`30
`
`aliows the container 100 to establish and evolve its own identity and course of interaction on
`
`the system 10. Further, containers 100, as logical enclosures, can exist and ‘operate
`17
`
`SUBSTITUTE, SHEET RULE 26)
`_
`_
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:23)
`Petitioners Twlt er, Inc. and Yelp Inc. - Exhlbll 1008 - Page 484
`
`

`
`WO 99139285
`
`PCTM39910! 988
`
`independent of their digital contents, whether encapsulating audio, video, text, graphic, or
`
`other.
`
`Referring now to FIG. 4, a block diagram of an infonnation container 100 is shown-
`
`The information container 100 is a logically defined data enclosure which encapsulates any
`
`element, digital segment (text, graphic, photograph, audio, video, or other), set of digital
`
`segments as described above with reference to FIG. 3 (C), any system component or process,
`
`or other containers or sets of containers. The container 100 comprises the containerized
`
`elements 01, registers 120 and a gateway 200.
`
`Registers 120 appended to an information container 110 are unique in that they operate
`
`independently of the encapsulated contents, providing rules of interaction, history of
`
`interaction,
`
`identity and interactive life to that container 100 through the duration of its
`
`existence on a network 201, without requiring reference to, or interaction with, its specific
`
`contents. They enable a container 100 to establish an identity independent of its contents.
`
`Additionally, registers 120 are unique in that their internal values evolve through interaction
`
`with other containers 100, gateways 200, the analysis engine 400, the execution engine 500,
`
`and the choices made by the users in the search interface 300, the container editor 110, the
`
`register editor 125, the gateway editor 210, the engine editor 510- Registers 120 are also
`
`unique in that they can interact with any register of a similar definition on any container 100
`
`residing on the network 201, independent of that container’s contents. Registers 120, once
`
`constructed, may be copied and appended to other containers 100 with their internal values
`
`reset,
`
`to form new containers. Register values, when collected at gateways 200 and made
`
`available to the analysis engine 400 through the data collection means 700 and the data
`
`reporting means 600, provide an entirely new layer of network observation and analysis and
`
`operational control through the execution engine 500. Registers 120 accomplish not only a
`
`real time information about
`
`information system, but also a real
`
`time information about
`
`information usage on a network. Further, because the user base of a network determines
`
`usage, the system 10,
`
`in gathering information about information usage,
`
`is observing the
`
`choices of the human mind. When these choices are submitted to the analysis of a rules-based
`
`10
`
`15
`
`20
`
`25
`
`or other analysis engine 400, the system 10 becomes capable of becoming progressively more
`
`30
`
`responsive to the need of the user base, in effect, learning to become more usefiil by utilizing
`
`the execution engine 500 to create system-wide changes by altering the rules of gateway. 200
`
`18
`
`SUBSTI'I'UTE_SHEET_{RULE 26)
`_
`_
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:24)
`Petitioners TWI ter, Inc. and Yelp Inc. - Exhlbll 1008 - Page 485
`
`

`
`W0 9959285
`
`PC'I'fl.lS99I{l'l 988
`
`interaction and thereby altering the registers 120 of transient containers 100 and establishing a
`
`complete evolutionary cycle of enhanced utility.
`
`Further, in establishing the pre-defined registers as described in the following four
`
`paragraphs, the following unique aspects of information about information are utilized for the
`
`first time: 1) the dynamic governance of information according to its utility through time, in
`
`active, passive and neutral aspects, as explained below; 2) the dynamic governance of
`
`information according to its utility through space in active, passive and neutral aspects, as
`
`explained below; 3) the dynamic governance of information according to its ownership, as
`
`explained below; 4) the dynamic governance of information according to its unique history of
`
`interaction as an identity on a network, as explained below; 5) the dynamic governance of
`
`information according to the history of the system on which it exists, as explained below; 6)
`
`the dynamic governance of information according to established rules of interaction, in active,
`
`passive and neutral aspects, as explained below; 7) the dynamic governance of information
`according to the profile of its creator, as explained below;
`8) the dynamic governance of
`
`information according to the value established by its ongoing usage, as explained below; 9) the
`
`dynamic governance of information according to it distributed ownership, as explained below;
`
`10) the dynamic governance of information according to what class of information it might be
`incorporated into, and according to what class of information container it might incorporate,
`
`as explained below;
`
`ll) the dynamic governance of information according to self-reporting,
`
`10
`
`15
`
`20
`
`as explained below-
`
`Referring now to Fig 4, registers 120 may be (1) pre-defined, (2) created by the user or
`
`acquired by the user, or (3) system-defined or system-created. Pre-defined registers 120 are
`
`those immediately available for selection by the user within a given container editor as part of
`
`25
`
`30
`
`that container editor,
`
`in order that the user may append any of those registers 120 to a
`
`container 100 and define values for those registers 120 where required. Registers 120 created
`
`by the user are those conceived and created by a specific user or user group and made
`
`immediately available for selection by the user or user group in conjunction with any of a wide
`
`number of container editors, in order that the user may append any of those registers 120 to a
`
`container 100 and define values for those registers 120 where required. Registers 120 acquired
`
`by the user are those registers existing networlc—wide 20], created by the user base, that might
`
`be located and acquired by the user in order that the user may append any of those registers
`
`l9
`
`SUBSTITUTE SHEET {IRULE 263
`_
`_
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:25)
`Petitioners TWI er, Inc. an Yelp Inc. - EXh|b|l1008 - Page 486
`
`

`
`WO 99139285
`
`PC'I'lUS99I01988
`
`120 to a container 100 and define values for those registers 120 where required. System-
`
`defined registers are those registers whose values are set andfor controlled by the system 10.
`
`System—created registers are those registers created by the system 10.
`
`Registers 120 are user or user-base created or system-created values or ranges made
`
`available by the system 10 to attach to a unique container, and hold system-set, user-set, or
`
`system-evolved values. Values may be numeric, may describe domains of time or space, or
`
`may provide information about the container 100, the user, or the system 10. Registers 120
`
`may be active, passive or interactive and may evolve with system use. Pre-defined registers
`
`include, but are not limited to, system history 110000, container history 101000, active time
`
`102000, passive time 103000, neutral
`
`time 104000, active space 111000, passive space
`
`112000, neutral space 113000, containment 105000, inclusion 106000, identity 114000, value
`
`115000, ownership 107000, ownership addresses 116000, proportionate ownership 117000,
`
`creator profile 108000, receptivity 118000, influence 119000, points 109000, others 120000,
`
`reporting 121000, neutrality 122000, acquire 123000,
`
`create 124000, content title 125000,
`
`content key phrase(s) 126000, and content description 127000, security 12800, and parent
`
`rules 129000.
`
`Pre-defined registers comprise an historical container register 101000,
`
`logging the
`
`history of the interaction of that container 100 with other containers, events and processes on
`the network 201, an historical system register 110000, logging the history of pertinent critical
`
`and processes on the network, a point register 109000 accumulating points based upon a
`
`hierarchically rated history
`
`of usage, an identity register 114000 maintaining a unique
`
`network wide identification and access location for a given container specifying a unique time
`
`and place of origin and original
`
`residence, a proportionate ownership register 117000
`
`maintaining a record of ownership percentage and economic values, and others 120000.
`
`User-defined registers include a report register 121000 setting trigger levels for report
`
`sequences, content determination and delivery target, three time registers, consisting of a
`
`range, map, graph, list, curve or other designating time relevance, 102000 assigning the time
`
`characteristics by which that container will act upon another container or process, 103000
`
`10
`
`15
`
`20
`
`25
`
`assigning the time characteristics by which that container be acted upon by another container
`
`30
`
`or process, and 104000 assigning the time characteristics by which that container will interact
`
`with another container or process,
`
`three space registers, consisting of a range, map, graph, list,
`
`20
`
`SUBSTI
`
`ESHEET RULE 26)
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:26)
`etltloners TWI ter, Inc. and Yelp Inc. - Exhibit 1008 - Page 487
`
`

`
`WO 99139285
`
`PCTill S9910] 988
`
`curve or other designating the domain and determinants of space relevance, 1 11000 assigning
`
`the space characteristics by which that content will act upon another container or process,
`
`112000 assigning the space, characteristics by which that content wiil be acted upon by
`
`another container or process, and 113000 assigning the space characteristics by which that
`
`container will
`
`interact with another container or process, a domain of influence register
`
`1 19000, determining the set, class and range of containers upon which that container will act, a
`
`domain of receptivity register 118000, determining the set, class and range of containers
`
`allowed to act upon that container, a domain of neutrality register 122000, determining the set,
`
`class and range of containers with which that container will interact, a domain of containment
`
`register 105000, determining the set, class and range of con_tainers which that container may
`
`logically encompass, a domain of inclusion 106000 register, determining the set, class and
`
`range of containers by which that container might be encapsulated, an ownership register
`
`107000, recording the original ownership of that containers, a creator profile register 108000,
`
`describing the creator or creators of that container, an ownership address register 116000,
`
`maintaining the address of the creator or creators of that container, a value register 115000,
`
`assigning a monetary or credit value to that container, other registers 120000 created by users
`
`or the system, a reporting register 121000, determining the content, scheduling and recipients
`
`of information about that container, a neutrality register 122000, an acquire register 123000,
`
`enabling the user to search and utilize other registers residing on the network, a create register
`
`124000, enabling the user to constmct a new register, a content title register 125000, naming
`
`the contents of the container,
`
`a content key register, 126000,
`
`identifying the container
`
`contents with a key phrase generated by the user andfor the system based upon successful
`
`usage of that phrase in conjunction with the utilization of the information within that container
`
`100, a content description register 127000, identifying the container contents with additional
`
`description, a security register 128000, controlling container security, and a parent container
`
`register 129000, storing the rules governing container interaction as dictated by the parent
`
`(encapsulating) container.
`
`The container also includes a gateway 200 and gateway storage 205.
`
`10
`
`15
`
`20
`
`25
`
`Gateways 200 are logically defined passageways residing both on containers 100 and
`
`30
`
`independently in the system 10. Gateways 200 govern the interactions of containers 100
`
`2!
`
`S
`
`SU3 THU telisitgiiiefiris
`Yelp Inc. - Exhibit 1008 - Page 488
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:27)
`
`

`
`W0 99/39285
`
`PCI'!US99l0l988
`
`encapsulated within their domain by reading and storing register 120 information of containers
`
`entering and exiting that container 100.
`
`The present invention also includes container gateway storage 205. Gateway storage
`
`205 stores infonnation regarding the residence, absence,
`
`transience, and alteration of
`
`encapsulated and encapsulating containers 100, and their attached registers 120, holding the
`data collected from registers 120 of transient containers 100 in order to make it available ii: the
`
`data collection means 700 and the data reporting means 600, and storing the rules governing
`
`the operations of its particular gateway 20!).
`
`Referring now to FIG. 5, a flow chart of the preferred method for creating a container
`
`10
`
`100.is shown.
`
`Input is received from the user selecting a container level through use of a drop-down
`
`menu 10100. A menu of all possible container classes within the subset and superset scheme
`
`of multiple hierarchically nested containers, i.e.; element, document, file, database, warehouse,
`
`domain, and more, is displayed on the output device 10200.
`
`Input is received from the user
`
`15
`
`selecting a class 10300.
`
`A graphic representation of a container in that class, with registers common to all
`
`containers as well as registers unique to its class is displayed 10301.
`
`Input is received from the user choosing to “create” 10400, “edit" 10500, or “locate"
`
`10600.
`
`20
`
`When the input of “create" 10400 is received from the user, a container template in that
`
`class appears 10410.
`
`Input from the user is then received adding or selecting a register 10540
`
`to append to that container template. When input is received Erorri the user adding a register, a
`
`list of registers that might be added to that class of container is made available to select 10550.
`
`Input is received from the user selecting a register 10560 and editing it 10570. The menu
`
`25
`
`returns to “add or select" 10540.
`
`If the input of “locate" 10600 is received fiorn the user, the system prompts the user to
`
`enter the identity of the container or class of containers 10605. The system locates the
`
`container-(s) 10610. Input is received from the user selecting a container 10620. The system
`
`prompts the user for a security code for permission to access the container for template use, or
`
`30
`
`to alter its registers, or to alter its content 10630. . Input is received from the user entering a
`
`name and password providing access to one of the security levels 10640.
`
`Input is received
`
`22
`
`SUBSTII U lE_SI-IE T_¥RULE 263
`_
`_
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:27)(cid:28)
`Petitioners WI ter, Inc. an Yelp Inc. - Exhibit 1008 - Page 489
`
`

`
`WO 99239285
`
`PCTIU599!01988
`
`from the user editing the container accordingly by transition to step 10500 and performing the
`
`steps for editing.
`
`If the input of “edit“ 10500 is received, a list of containers available to edit at that level
`
`is shown 10510.
`
`Input is received from the user selecting a container 10520. That container
`
`appears, available to edit 10530. Input is received fi'om the user selecting “add” or “select"
`
`registers 10540 by the user clicking on the graphically depicted register, or from a drop down
`
`menu. input is received from the user selecting the register to edit 10560. Input is received
`
`from the user selecting “modify” or “delete" for that register 10565. If input is received from
`
`the user to “delete," that register is severed from the container. If input is received from the
`
`user to “modify”, the register editor 10570 screen appropriate to that register appears, i.e., an
`
`x—y type graph to define a curve of relevant active time, in which the user manipulates the x-y
`
`termini, scale and curve, or a global map in which Input is received from the user selecting the
`
`locale of active space, whether zip code, city, county, state, country, continent, plant or other.
`
`When input is received from the user saving the definition, the screen returns to the main
`
`container screen to make another selection available. . Input is received from the user defining
`
`as many registers as he chooses. One of the registers may be named "new register.” Input is
`
`received from the user selecting the new register, and if chosen by the user, defining a wholly
`
`unique and new kind of register by the user entering input into the register editor 125.
`
`When the input is received from the user choosing to add a register, a list of registers
`
`that might be added to that class of container are made available to select 10550. Input is
`
`received from the user selecting a register 10560 and editing it 10570. The menu returns to
`
`“add or select” 10540, and in turn to Input — Select Container.
`
`Input may then be received fi'om the user choosing to add, modify, or delete the
`
`container contents 10700. Once the registers are defined, input is received from the user
`
`indicating completion and the interface reverts to the container editor. When input is received
`
`from the user choosing "select component" (to select the component to containerize) from the
`
`main menu bar 10700, a window appears allowing the user to select any file, component, or
`
`other container. If for example, the user were creating a warehouse container, and wishes to
`
`incorporate several databases into that container, input would then be received from the user
`
`selecting "database." The program would prompt the user for the location (directory) of that
`database or container.
`If the requested selection is not containerized, input may
`be
`23
`
`l0
`
`15
`
`20
`
`25
`
`30
`
`SUBSTITUTE SHEET {RULE 26)
`_
`_
`(cid:51)(cid:72)