Patent Publication Number: US-2011078085-A1

Title: System and method for real estate business collaboration and knowledge acquisition and sharing

Description:
PRIORITY CLAIM AND RELATED APPLICATION 
     This application claims domestic priority under 35 U.S.C. §119(e) from prior U.S. provisional application Ser. No. 60/933,914, entitled “System and Method For Real Estate Analysis and Investment”, which was filed on Jun. 7, 2007 naming Gregory R. Clement as inventor, the entire disclosure of which is hereby incorporated by reference for all purposes as if fully set forth herein. 
    
    
     BACKGROUND OF THE INVENTION  
     1. Field of Invention 
     This invention relates generally to data processing and more specifically to providing data processing tools and environment that enables collaborative real estate knowledge acquisition and investment. 
     2. Description of Background Art 
     While investing in real estate remains a useful mechanism for building wealth, it also presents unique challenges. Home buyers and sellers, for example, are confronted with a variety of unfamiliar tasks that may further be objectively and subjectively oriented. Home buyers, however, enjoy a fixed goal of buying or selling their part-time or full-time dwelling. Real-estate investors, on the other hand, may be confronted by an even wider range of short and long term tasks that may encompass a wide range of investment goals, rendering real estate investing difficult for even the expert, let alone the novice investor. Unfortunately, few useful resources exist for addressing the challenges facing home buyers and sellers, or further, real-estate investors. 
     Conventional real-estate resources such as books, videos, seminars, call centers and other so-called “real estate courses” proliferate. However, these typically present only an author&#39;s recreation of “what worked” for that author. Moreover, these tend to include only specially selected “instructions” designed as much to espouse the value and infallibility of the author&#39;s perspective as to provide any practical assistance. 
     Newspapers and brokerage houses also provide print media relating to real estate. These, however, typically provide little more than listings of homes for sale by the property owner or a commission-based agent, i.e., managed exclusively by a particular broker or brokerage house, or by multiple brokers or brokerage houses under a multiple listing agreement. While the Sunday Real Estate section of a newspaper or brokerage literature may also provide other ads, local sales figures, articles or other somewhat generic information, these do little to assist persons with the actual buying and selling of real estate. 
     Some computer-based real estate resources also exist. However, most provide merely the same, primarily individual home buyer or seller support as their print counterparts. Online services provided by newspaper publishers, for example, tend to offer such listings, but do so in a generic, boolean search format. (See, for example, http://www.nytimes.com/page/realestate/). Online services provided by brokerage houses also provide primarily boolean searchable “home for sale” listings, albeit often over a broader region than newspapers (e.g., statewide or nationally), and both newspaper publishers and brokerage houses may list sales for commercial real estate as well. 
     Some brokerage houses (e.g., http://www.remax.com/) may also provide similar boolean searching in which a user may purportedly enter search terms for: “regional home prices”, “recent sale prices”, basic “school information”, “neighborhood data”, home sale price trends, etc, and further listing services are also available via the MLS multiple listing service listings, http://www.mls.com/. (The MLS listing service, for example, provides (to brokers only) agent and foreclosure listings, as well as a publicly accessible mortgage calculator, basic bank loan rates, generalized value of a home according to sales of similar home configurations in the area, a glossary and online real estate courses.) While providing some potentially useful informational material, however, the information provided does little to assist persons in the actual buying and selling of real estate. 
     A few so-called real estate applications are also purported to be becoming available. Some provide generic closing, and other forms, while others purport to support some buying or selling processes. However, the former fail to provide concrete assistance in the actual buying or selling of real estate, while the latter are apparently derived from general purpose business applications. As such, these tend to suffer the same difficulty of use, critical missing pieces, erroneous or inexact presumptions, and so on, as encountered with other examples that perpetuate the re-use of generic, general purpose business application components for addressing only certain aspects of complex processes. 
     In addition to the above-mentioned deficiencies, conventional real estate offerings fail to provide an environment that facilitates the singular or particularly ongoing purchase or sale of real estate, let alone the “deal-independent” accumulation of knowledge or coordinating or optimizing the handling of transactions that may be conducted in conjunction with one or more real estate deals. Conventional offerings also fail to consider, let alone facilitate, such aspects as planning, maintenance, upgrading, value optimization, timing or other concerns of investors and other persons involved in real estate purchasing and/or selling. Conventional real estate offerings further fail to enable sellers, investor buyers or investor sellers to coordinate or collaborate with each other or with related third parties, exploit one another&#39;s knowledge or transactional resources, provide reliable documentation, or minimize the time/effort required to actually conduct transactions, among other deficiencies. 
     Accordingly, there is a need for systems and methods that provide for conducting or otherwise facilitating real estate business, collaboration and knowledge accumulation sharing. 
     SUMMARY OF EMBODIMENTS OF THE INVENTION 
     Embodiments of the present invention include processing tools, resources and environment components that may be utilized alone or in combination for conducting or otherwise facilitating real estate business, collaboration and knowledge accumulation sharing, thereby enabling conventional difficulties to be avoided or further advantages to be achieved. 
     Embodiments of the invention provide for buying and selling real estate in a manner that may depart from the conventional single-match model. Much like buying or selling the family home, the conventional model requires a single user, working alone, to essentially conduct a repetitive cycle of separate tasks in which the user: purchases a single property, then searches for a buyer who may be interested in purchasing that particular property and then sells the property to the newly discovered buyer. Each real estate deal, for all practical purposes, begins completely anew with the purchase of each new property (e.g., find the new property, then begin a new search for a new buyer that may be interested in purchasing the new property, and so on). 
     While embodiments of the invention may support a single-match model (if desired in a particular instance), they also enable users to more optimally conduct potential or actual real estate deals, as well as included or otherwise related transactions or transaction aspects that may advance the real estate deals. Various embodiments enable users to conduct such deals, transactions or transaction aspects successively or concurrently as may be desired at any particular time. Embodiments also enable users to accumulate or share knowledge prior to or otherwise independently of a particular deal, transaction or transaction aspect in which such knowledge may be further utilized. Embodiments also enable the users to individually, coordinatingly or collaboratively conduct the same or different potential or actual deals, transactions or transaction aspects while: assuming the same or different roles, interacting according to the (typically advancing) status of other parties or assistance of third parties; accumulating, fully or partially sharing or utilizing pools of leads, prospects, other contacts, experience, tools or other knowledge; forming authoritative or self-authenticating transaction documentation, creating or utilizing modifiably reusable/adaptable tool automation, consulting with virtual advisors, party identification, user/knowledge linking, and so on, among other combinable aspects. 
     Users may, in various embodiments, include one or more of independent or affiliated buyers; sellers; buyer investors; seller investors; investor, owner/occupier, agent and other intermediaries; and users that may perform more than one role in the same or different actual or potential real estate deals, transactions or transaction aspects. Users may also, in various embodiments, include, for example, full access, limited access and guest access users. 
     In one embodiment, a real estate business, collaboration and knowledge acquisition sharing system (“real estate business system”) includes a real estate business application hosted by a central server, and one or more user systems that are couple-able to the central server for invoking features of the real estate business application. The real estate business application provides, within a multiple-focus timeline environment, a compliment of operational real estate transaction tools that may be invoked by respective system users to individually, coordinatingly or collaboratively: accumulate a knowledge base including user-specific and shared real estate business contact, property, experience and other conduct real estate business data; evaluate/conduct one or more real estate business deals; and utilize portions of the knowledge base or further data to conduct transactions or transaction aspects corresponding to the real estate business deals. 
     The multiple-focus timeline environment in one embodiment provides a split timeline-based presentation of a portion of the operational tools and knowledge base that are available to the user, and at least one persistable transaction attribute. A deal-&amp;-transaction timeline provides user access to or presentation of real-estate business transaction tools or stored user/shared data according to an optimized progression of transactions/transaction aspects in advancing a real estate deal and a user/other party role in conjunction with the real estate deal or deals. A further transaction-&amp;-aspect timeline provides user access to or presentation of real estate business transaction tools or stored user/shared data according to an optimized progression of transaction aspects of a current transaction. Each timeline may further correspond with one or more users, deals, transactions or transaction aspects. The embodiment may also persist one or more transaction attributes within the transaction-&amp;-aspect timeline or in a further presentation. Such attributes may, for example, include a particular contact, property and/or other knowledge that may be needed for or the current focus of a transaction or transaction aspect. A further embodiment provides for modifying the environment (e.g., one or both timelines) to indicate or further conduct processing according to a status or advancing status of one or more other persons with which a user is interacting (e.g., lead, prospect, party to an actual/potential deal, and so on). 
     In another embodiment, the real estate transaction tools comprise resource utilization advisors including a deal advisor, short sales advisor, and project resource allocation estimator. The resource utilization advisors respectively provide for conducting scenario analysis, comparison, advancement evaluation and customizable reporting relating respectively to: potential, actual or alternative deals, transactions or transaction aspects, short sales viability, and allocation of cost or other resources relating to renovation and/or other investment of user and/or other party resources. The advisors may, for example, utilize user data input or statistical models, as well as other accumulated knowledge base data corresponding to a same or different deal, transaction or transaction aspect of the same or a different user. 
     A further embodiment provides suitability matching tools. These provide for determining transaction-utilization transaction attributes (“transaction attributes”) corresponding to transaction data that may be utilized in determining applicability of acquired data in conjunction with current or future actual and/or potential deals, transactions or transaction aspects. The embodiment further provides for responding to user invocation in conjunction with such deals, transactions or transaction aspects by determining a corresponding subset of the data, according to such attributes or further criteria. For example, a transaction matching tool provides for associating actual and/or potential buyers with transaction attributes indicating their areas of preference, proximity, resource availability, deal/transaction history, likely follow through or other indicators of suitability or comparative suitability in conjunction with a (typically future) actual or potential purchase or sale of a property. The transaction matching tool further provides, in conjunction with a (typically future) availability of one or more properties for purchase or sale, for determining one or more of those sellers or buyers that may be interested or should be considered (or the nature/extent of such interest/consideration) as potential purchasers of the properties. In another embodiment, potential buyers may include one or both of disclosed buyers (whom the user may identify) and blind or “community matching” buyers (that one or more other users or the system may indicate exist without requiring that they reveal corresponding contact information). Matching tools may also operate in conjunction with other persons, properties or other roles in conjunction with a particular deal, transaction or transaction aspect. 
     Yet another embodiment includes guest linking and lead development tools. Guest linking tools enable a user to permit selectively limited access by third parties to the user&#39;s data. Such access may, for example, be limited to one or more particular deals, transactions or transaction aspects with which the third party is or otherwise may participate. Lead development tools provide for determining a pattern of communication with non-user sellers or other transaction parties that is more likely to generate interest or responsiveness in the parties, for compiling communication information and for initiating such communication with the parties. Such tools may also provide for determining a current status of such operation or responsiveness of one or more of such parties or classification(s) of such parties, among other aspects. 
     Among other embodiments, one particular embodiment provides for conducting team-based real estate business. For example, the embodiment provides for one user assigning one or more tasks (e.g., management or other interactions or interaction aspects), to various team members or third parties, and further provides for presenting to a corresponding team member or third party only applicable information or tasks. 
     These provisions together with the various ancillary provisions and features which will become apparent to those artisans possessing skill in the art as the following description proceeds are attained by devices, assemblies, systems and methods of embodiments of the present invention, various embodiments thereof being shown with reference to the accompanying drawings, by way of example only, wherein: 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1   a  is a flow diagram illustrating a real estate business, collaboration and knowledge acquisition sharing system (“real estate business management system”) according to an embodiment of the invention; 
         FIG. 1   b  is a flow diagram illustrating a further real estate business management system according to an embodiment of the invention; 
         FIG. 2  is a flow diagram illustrating a real estate knowledge base and associations of data therein according to an embodiment of the invention; 
         FIG. 3   a  is a flow diagram illustrating a split dual timeline, transaction based data persistence and independent share-able data accumulation operations of a real estate management system and real estate management system interface (“REM interface”) according to an embodiment of the invention; 
         FIG. 3   b  is a flow diagram illustrating how the REM interface operations of  FIG. 3   a  may be extended to the real estate business management system and REM interface by way of one or more further integral transaction or transaction aspect advancement sub-timelines in accordance with user selection or advancement of a potential or actual real estate deal; 
         FIG. 4-FIG .  70  illustrate various visual and textual presentations, user interactions and system responses thereto of the interface and operational features of the real estate business, collaboration and knowledge acquisition sharing system. 
       
         FIG. 71A-D 
       
       
         FIG. 72A-C 
       
       and 
         FIG. 73A-D  show diagrams illustrating embodiments that may comprise one or more of the components of the estate business, collaboration and knowledge acquisition sharing system according to any of the embodiments of the invention. 
         FIG. 74A-B  is a diagram illustrating a computing system embodiment that may comprise one or more of the components according to any of the embodiments of the invention. 
     
    
    
     DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS 
     In the description herein for embodiments of the present invention, numerous specific details are provided, such as examples of components and/or methods, to provide a thorough understanding of embodiments of the present invention. One skilled in the relevant art will recognize, however, that an embodiment of the invention may be practiced without one or more of the specific details, or with other apparatus, systems, assemblies, methods, components, materials, parts, or the like or some combination. In other instances, well-known structures, materials or operations are not specifically shown or described in detail to avoid obscuring aspects of embodiments of the present invention. 
     Turning now to  FIG. 1A , there is seen a real estate business, collaboration and knowledge acquisition sharing system (“real estate business system”) according to an embodiment of the invention. Real estate business system  100   a  broadly provides for responding to one or more users or groups of users by managing or otherwise conducting real estate business transactions or transaction aspects that may currently or subsequently correspond to one or more potential or actual real estate deals or groups of real estates deals. In this manner, system  100   a  provides for advancing toward completion the respective real estate deals or groups of real estate deals or indicating that completion of such deals or groups of deals should be avoided. 
     System  100   a  also provides for accumulating a knowledge base of real estate business data that may include data that is independent of a current real estate deal. The accumulated data may therefore be automatically or manually utilized by system  100   a  or a user respectively in conjunction with a current real estate transaction or transaction aspect. Such data may also be similarly utilized in one or more other real estate transactions or transaction aspects, if the data is-be determined to be applicable to such transactions or transaction aspects in a given instance. Such transactions or transaction aspects may further correspond with a current real estate deal or one or more other real estate deals or groups thereof, or with the same or different users, if the data is determined to be applicable to such users/deals. System  100   a  provides for conducting these or other real estate business/knowledge base operations in an individual or coordinated or combined (“collaborative”) manner in conjunction with system  100   a  member users, other users or other participants that may correspond to one or more of real estate business transactions, transaction aspects or deals. 
     A real estate deal may, for example, include potential or actual purchasing, selling, renting, converting, updating or other disposition of property, or some combination. A potential deal, transaction or transaction aspect, for purposes of the present example, includes a deal, transaction or transaction aspect in which one or more participants has not been advanced to a status of an actual deal participant or “party”. (A participant in this case may, for example, include a lead or prospect, whether or not he/she is aware of such participation.) A potential deal, transaction or transaction aspect may also transition from potential to actual in conjunction with sufficiently advancing a status of one or more potential deal participants, whether or not a deal is actually consummated. Users may, for example, include one or more of full or limited purpose users, “guest users”, intermediary or “community” users, third parties and so on, or groups (e.g., a “team” or “community”) thereof A participant may, for example, include a person that is determined by a user or system  100   a  to be related to a particular transaction, transaction aspect or deal even if, as is typically the case, the participant never becomes a user or is unaware of his/her participation. Participants may also be associated with a participant type (“role”) or other transaction attributes corresponding to such transaction, transaction aspect or deal (e.g., see below). Real estate business knowledge base data may, for example, include one or more of potential or actual seller, buyer, property, contact, statistical or other user or shared real estate business data that may be stored, determined, presented or otherwise provided (e.g., in a fully presented or lesser disclosed or “blind” manner) by the real estate business system. 
     The illustrated embodiment also provides for implementing system  100   a  in a membership-based manner. That is, system  100   a  provides for receiving authorization from a person for enrolling at least that person under a service agreement as a full or partial use member, for utilizing selected ones or all of the system  100   a  real estate business management and data acquisition features. In another guest-enabled embodiment, system  100   a  may also provide for receiving authorization from the person to also enroll one or more other persons as “guests” of the member, whereby system  100   a  may respond to the guest, according to also received user selection, by presenting, modifying or saving user-selected data types of data corresponding to selected deals, transactions or transaction aspects that are associated with the user or that the guest may enter. In a further session sharing embodiment, system  100   a  may also provide for receiving authorization from a member to also present, to a third party remote user, a presentation that system  100   a  presents to the member, or further, to also respond to third party remote user invocation, according to received member selection, by one or more of receiving data, implementing data modification, saving, and so on. (In a more specific embodiment enabling greater third party access than presentation, the embodiment also provides for resolving competing or conflicting user input according to member priority, received member-designated priority or some other suitable conflict resolution mechanism.) 
     In yet another embodiment, system  100   a  may also receive authorization from the person to participate in community private data sharing. In this embodiment, system  100   a  may: (1) make available, to the member, selectable acquired private data portions or detail hiding indicators of acquired private data portions of one or more other members that are also enrolled in community private data sharing; or (2) make available, to other members that are also enrolled in community private data sharing, selectable acquired private data portions or detail hiding indicators of acquired private data portions of the member. Each of the above member enrollments may, for example, be provided by system  100   a  as a paid service, e.g., a membership Web site), and may system  100   a  may provide for billing or managing billing of a member. (For clarity sake, the terms “member” will be included in the term “user” unless specifically indicated or the context clearly dictates otherwise, such that a user may but need not be subject to a membership arrangement. The term “third party user” will further be used to refer to a guest, session sharing or other third party other than a full or limited purpose user that may access the system, and may include a “non-member user” where a membership arrangement may be imposed.) 
     Note that the term “or” as used herein is intended to include “and/or” unless otherwise indicated or unless the context clearly dictates otherwise. The term “portion” as used herein is further intended to include “in whole or contiguous or non-contiguous part”, which part may include zero or more portion members, unless otherwise indicated or unless the context clearly dictates otherwise. The terms “multiple” or “multi” as used herein are intended to include “two or more” unless otherwise indicated or the context clearly indicates otherwise. The term “multimedia” is intended to include one or more media types, streams, portions, and so on, or some combination thereof unless the context clearly indicates otherwise. The term “information” is further intended to include data, executable code or both unless otherwise indicated or the context clearly indicates otherwise. 
     As shown in the  FIG. 1A  example, system  100   a  comprises at least intermittently communicatingly couplable components including real estate business management system  101 , network  102 , and one or more of each of: user devices  103   a - c,  data acquisition points  105 , external data sources  106  and data presentation nodes  107 . (System  100   a  may also operate in conjunction with one or more additional static or reconfigurable networks, other connections or various network security mechanisms, e.g., as are generally indicated by network  102   a  and firewall  108  respectively, in accordance with the requirements of a particular embodiment. System  100   a  also includes server  108  and system administration engine  109 . 
     Real estate business management system  101  (also referred to herein as “REM system”) provides for responding to user or remote device invocation, via user devices  103   a - c  or via other system  100   a  components, by conducting real estate business and data acquisition sharing operations corresponding to such invocation. REM system  101  may conduct such operations alone or may further invoke operabilities of such devices or other components in conjunction with providing such operations, or in providing a corresponding response, for example, as is discussed in greater detail below. REM system  101  may, for example, also provide for inter-operating with data acquisition nodes  105 , external data sources  106  or presentation nodes  107 . 
     Exemplary REM system  101  is implemented in a more centralized manner, operating as a hosted application hosted by a server  108 . Server  108  may, for example, include a conventional Web server or other application server, and the REM system may include a World-Wide-Web based application (or other remote application) operating at a Web site that may also be hosted by server  108  or some other server (not shown). 
     REM system  101 , in this example, also provides for generating Web pages that, together with various real estate, data acquisition and interface features provided by REM system  101 , forms a real estate business, collaboration and knowledge acquisition sharing environment. The environment may also include extension applications provided by data acquisition nodes  105 , external data sources  106  and data presentation nodes  107 , which may also be implemented as hosted applications hosted by one or more of the same or different Web servers and delivered to devices  103   a - c  or further user devices, kiosks, and so on (not shown) in the form of Web pages. These or other “extension applications” that may be utilized may also communicate more directly with REM system  101 , for example, as is discussed in greater detail below. 
     The above Web-based software implementation example will be presumed for the remainder of the discussion unless otherwise indicated or the context clearly indicates otherwise, so that aspects of the invention may be better understood. It will be appreciated by those skilled in the art, however, that various other mechanisms may also be utilized. For example, the exemplary implementation avoids installing operational code on a user device and provides “always available” online access to REM system  101  by most stationary or mobile network-ready user devices having a direct or indirect connection to the Internet. Other implementations may, however, also be used. For example, Local application software or other operational code may also be loaded onto a user device. Applets, servelets or other mobally executable code may also be utilized, or an implementation may utilize one or more of user devices, application/web servers, load balancing, generic or specialized hardware, add-ons, extensions, various mobile devices/peripherals, integrated/combined devices, peer-to-peer networking, and so on, many of which are well known in the related arts. These or other alternatives may, for example, be implemented in an otherwise conventional manner for implementing various other applications or portions thereof, in accordance with the requirements of a particular application. 
     Continuing now with  FIG. 1A , transfers among various system  100   a  components may be conducted in an otherwise conventional manner for generally supporting Web-based or otherwise remote applications. For example, REM system  100   a  may generate (i.e., or retrieve from corresponding storage) a Web page. The Web page may, for example, include XML or other suitable protocol or protocol variants for transferring to a user a Web page including a currently presented or “current” interface portion or other applicable code or data (“information”). Server  108  may further transfer such information via network  102  to one or more corresponding user devices  104   a - c,  e.g., using TCP/IP or other suitable protocols. 
     A transmission client (e.g., Web browser) that is hosted by or executed at the client (e.g., transmission client  131 ) may present the Web page to a user, which user may review the presented information and may further respond by invoking command options, entering or modifying data and so on, as provided by one or more corresponding ones of the received interface portions. The transmission client may further transmit information corresponding to the user response via network  102  to REM system  101 . Data acquisition nodes  105 , external data sources  106  and data presentation nodes  107  may also transfer information to/from respective user devices in a similar manner when inter-operating remotely with a user. Data acquisition nodes  105 , external data sources  106  and data presentation nodes  107  (“expansion nodes”) may further utilize conventional or other suitable transfer mechanisms, e.g., HTTP, SOAP, and so on, to transfer information to/from REM system  101  (e.g., including acquired data, external data or presentation information respectively). 
     As shown in  FIG. 1A , REM system  101  comprises at least intermittently communicatingly coupled components including real estate business management engine (“REM Engine)  111  and real estate business management knowledge base (“REM KB”)  112 . Real estate business management engine (“RBM engine”)  111  further includes communication engine  111   a,  knowledge base controller  111   b,  REM interface engine  111   c,  deal engine  111   d,  transaction/task engine  111   e,  virtual business advisor  111   f,  user/community suitability matching and linking engine  111   g,  transmission sequence engine  111   h,  interactive forms engine  111   j,  team assignment and reporting engine  111   k,  guest engine  111   m,  party status engine  111   n  and security engine  111   o.  REM system  101  may also include other components, e.g., as indicated by engine  111   p.    
     Communication and control engine (“communication engine”)  111   a  operates largely as an REM engine communication manager and controller. Communication engine  111   a  provides for receiving control/data information from other system  100   a  components, decoding, converting or formatting such received information as needed and to a form suitable for use by corresponding system  101  components, and invoking other engine  101  components that may correspond to the received information. Communication engine  111   a  also provides for coding, converting or formatting information received from other engine  101  components (as needed and to a form suitable for use by other system  100   a  components) and initiating transfer of such “generated information”, via server  108 , to corresponding ones of the other system  100   a  components. (It will be appreciated that encoding/decoding of information may be utilized in conjunction with more secure implementations, and any suitable encoding/decoding may be conducted, many of which are well known in the art.) In accordance with the above Web page implementation, for example, communication engine  111   a  provides for packaging and un-packaging information packets that may be transferred to and from REM system  101  in accordance with XML or one or more other protocols that may be utilized; communication engine  111   a  may provide for implementing suitable protocols for packaging and un-packaging information that may be transferred in a more direct manner to and from system  100   a  components other than user devices  103   a - c.    
     Knowledge base controller  111   b  broadly provides for responding to communication engine  111   a  or other REM engine  101  components by storing and retrieving knowledge base data to and from shared real estate management knowledge base (“KB”)  112 . In one embodiment, KB  112  provides a database management system (“DBMS”), for example, as produced by Oracle Corporation of Foster City, Calif. and various others. In this embodiment, KB controller  111   b  provides for interfacing with the DBMS for initiating data storage, retrieval, modification and manipulation operations (e.g., modify/delete data, query, sort, filter, extract, and so on). KB controller  111   b  similarly provides for storing, retrieving, modifying and manipulating real estate management information, other user/other participant information (e.g., organization, team, type, status, priority, preference, and so on) and system  100   a  operational information (e.g., interface, transaction attributes, and so on) in conjunction with KB  112 . 
     Those skilled in the art will appreciate that a wide variety of database or non-database mechanisms may be used, including but not limited to one or more of flat file, relational, object-oriented, multi-tenant or other databases, lists, tables, n-dimensional arrays, and so on. Suitable well known and emerging database or other storage configurations supporting various fixed or customizable schema may also be used, for example, main tables, support table, key fields, metadata, and so on, and will likely vary and are commonly implemented in accordance with the requirements of a particular embodiment. Examples of data types, code and data, and associations thereof corresponding to various real estate business management and knowledge base acquisition embodiments are, however, discussed in greater detail below. (Note that, while the discussion that follows may refer to KB controller operations as simply “storing”; it will be appreciated that KB controller operation may nevertheless also include storage, retrieval, modification, manipulation or other operations as well.) 
     KB controller  111   b  may generally provide for storing such information in an otherwise conventional manner for storing, in a database, multiple party and multiple relationship information. The illustrated embodiment of  FIG. 1A , for example, provides for the implementing the above discussed membership-based or other user-based RE business management and data acquisition. In this embodiment, KB controller  111   b  stores user information corresponding to member users in user data storage  112   a,  and information corresponding to third party users (here, non-member user data) in third party data storage  112   b.    
     Member user data may, for example, include membership agreement, payment, security information (e.g., username, password, encryption keys, remote access authorization, user device support, payment/customer support information, organization or business management team information, and so on). Member user data may also include system  101  administration information (e.g., as authorized by engine  109 ) for determining enrollment authorization and permissions for guest, session sharing or other third party user access, as well as for participation in submitting to or sharing community or other information sharing, or use of system  101  extensions, such as data acquisition nodes  105 , external data sources  106 , data presentation nodes  107 , and so on. KB controller  112   b  may further store, in third party data storage  112   b,  third party user access information (username, password, organization, team, etc., e.g. as with each member), contact information, global third party access privileges (e.g., whether guest or other access is available to a particular third party, type(s) of information that may be accessed, and the types of presentation, modification or other privileges that a user has determined are applicable to a particular third party, and so on. 
     KB controller  111   b  further stores, in data storage  112   c - e,  buyer data, seller data and property data respectively that may correspond to one or more members. As shown, KB controller  111   b  also provides for associating each of buyer data for each buyer, seller data for each seller and property data for each property with a corresponding member, one or more persons in a member&#39;s organization or on a member&#39;s team, applicable guest/session sharing third party or community member, as well as any applicable third party participant, deal, transaction, transaction aspect, transaction attributes, a time/date stamp and so on. (In various embodiments, for example, stored information may also be associated with other information that may be of interest to a user and ascertainable by controller  111   b  using prior stored information, system  100   a  accessible information or below-discussed custom field entries. Such information may, for example, include but is not limited to user device or node location, device/device resource identification, primary/secondary purpose of a trip, meeting or other contact or attempted contact, and so on. 
     It will become apparent as the discussion progresses that the storing of buyer, seller and property data may be conducted independently of a particular deal, transaction or transaction aspect, and further independently of other buyer, seller and property data. For example, members need not respond to a property becoming available by then attempting to locate a buyer for the property, or similarly attempt to create a deal in a strictly sequential manner. Rather, each member may instead seize available opportunities to accumulate buyer, seller or property “inventory”, and thereby create a share-able inventory or pool of available resources that the member may utilize to further expand his inventory, share or initiate, transact or conclude a deal as the opportunity arises. Moreover, while KB controller  111   b  may associate a portion of such data with a particular deal, transaction or transaction aspect (e.g., one or more potential or actual buyers, sellers or property), the data also remains independently available. A corresponding member may therefore further exploit such data for accumulating more such data (e.g., by contacting one or more of accumulated buyers/sellers, marketing one or more properties, and so on), sharing such data with a member community or others, or for use in conjunction with other deals, transactions or transaction aspects to which controller  111   b  may also associate such data. Such data utilization may also be extended by system  100   a  operation to a member providing or receiving community data, sharing a session, employing guests, utilizing other member contacts, and so on, among other system  100   a  features. 
     KB controller  111   b  also stores deal, transaction and transaction aspect data in storage  112   f  and operational data in operational data storage  112   g.  Deal, transaction and transaction aspect data may, for example, include forms, marketing, notes, calendaring, tasks, documentation, buyer, seller and property details, assignment of status in a deal, transaction or transaction aspect, or tasks to the member or one or more other persons on a member&#39;s team (that may also be members), third parties or community members, and so on that are not stored as member, third party, buyer, seller or property data, and that do not comprise operational data. 
     As with buyer, seller and property data, KB controller  111   b  may associate deal, transaction and transaction aspect data with one or more of corresponding member, guest, session sharing or other third parties, or may associate such data with community sharing or surrounding conditions; also as with buyer, seller or property data, KB controller  111   b  may also associate general “handling”, particular assignments of deal, transaction, transaction aspect portions or portions of other tasks (e.g., custom field data or other features that may not be otherwise directly supported by system  101 ) or access, modification or addition to such data by various member or non-member participants. Deal/transaction data may also include user preferences for conducting deal, transaction or transaction aspect portions (including any further task portions) or any further operational characteristics (e.g., stored in storage  112   g ), and which KB controller  111   b  may associate with a particular member, team, non-member participant, and so on, or one or more particular features. KB controller  111   b  may, for example, determine/conduct these or other associations automatically, e.g., according to responsible user operation, user preference, other criteria, according to user determination/selection or some combination thereof. 
     Operational data stored in operational data storage  112   g  may, for example, include code and data information for implementing, testing, maintaining, updating, administering, simulating or emulating REM engine  111 , REM KB  112 , or further, data acquisition nodes  105 , external data sources  106  and data presentation nodes  107 . Such data may, for example, include without limitation, the REM system/engine interface, protocol handling, tools, security, administration or other features (e.g., see below). 
       FIG. 2  illustrates, in greater detail, a further data storage embodiment that may be implemented for each full or limited system  100   a  user. In this embodiment, KB controller  111   b  provides for associating buyer, seller, property or other (e.g., shared) data that may be accumulated by the user to be associated with that user, and further with a participant type, status and other information. Note that the illustrated configuration shows data storage for only a single user. Such a configuration may be duplicated for other users, and may similarly provide for storing buyer, seller and property data corresponding to each of the other users. (Data that is initially unknown may, for example, be populated with null or other default data, and data storing and association may again be conducted by KB controller  111   b  of  FIG. 1A .) 
     As shown in  FIG. 2 , and with further reference to  FIG. 1A , knowledge base  200  may comprise various associations of knowledge base data. Knowledge base data includes user participant data (“user data”)  201  corresponding to a particular user, and data associated with user data  201 . Such associated data includes accumulated buyer data or seller data  202 ,  203  (if any) that is associated with accumulated buyers or sellers (if any), accumulated property data corresponding to property of the user (“user property data”)  201   a - b  (if any) and any accumulated property data corresponding to the accumulated buyers and sellers (“buyer property data” or “seller property data” respectively)  202   a - b,    203   a - b.  As shown, accumulated user property data  201   a - b  is associated with the user participant (“user”) and user data  201 , while accumulated buyer or seller data  202   a - b,    203   a - b  is associated with corresponding buyer and seller participants and data, and may, in various embodiments, also be associated with the user and user data. Knowledge base  200  also comprises a shared knowledge base  206  including system, community or other data, portions of which may also be associated with user data  201  or other knowledge base  200  data. 
     User data  201  includes user status/tracking data  211 , deal, transaction or transaction aspect data  212 , status and assignment data  213 , special data processing aspect data  214  and administration and tracking data  215 . As will be further discussed with reference to REM interface  111   c  ( FIG. 1A ), user data may include user status information  211  that may, for example, include calendar, notes, tasks, contacts and announcement data and parameters. As with other user data, KB controller  111   b  ( FIG. 1A ) may associate each status information entry that corresponds with a particular deal, transaction or transaction aspect with the corresponding deal, transaction or transaction aspect. Thus, for example, KB controller  111   b  may associate particular user calendar entries, notes, tasks, status/task assignments, contacts and announcements with the particular deal, transaction or transaction to which they pertain. 
     KB controller  111   b  may also store association of each of such data, according to corresponding parameters, with a particular user, entry/modifying participant, time/date stamp, access privileges, user preferences, user selectable guest, session sharing third party, availability to the community, location, device and security (e.g., guest or session sharing presentation, entry, modification; user location, device, use or other conditions, use of cryptography, and so on.), among other data associations. KB controller  111   b  may further provide for responding to REM interface engine  111   c  or other engine  111  components ( FIG. 1A ) by retrieving such information, for presentation, processing or other purposes, according to one or more of such data, parameters or associations. In accordance with one embodiment, however, at least those notes that have been entered and that pertain to a particular deal, transaction or transaction aspect may be rendered unalterable once entered; in accordance with another embodiment, all notes that have been accepted for storage are rendered unalterable, thereby enabling such notes to be utilized as self-authenticating notes. 
     Various embodiments may also provide for storing multiple types of user information, and may do so in accordance with integrated or separated constructs. One embodiment, for example, provides for storing various types of user information (e.g., real estate management, personal, other projects/tasks, and so on) as corresponding to a single integrated calendar or collection of notes, tasks, contacts, announcements, and so on. In this embodiment, KB controller  111   b  may automatically determine and associate with such data an information type; controller  111   b  may determine such type, for example, according to a context or condition at the time of entry or use (e.g., while handling a personal project). In another embodiment, a user may determine and enter or select such type, which controller  111   b  may in either case associate with corresponding data. In other embodiments, KB controller  111   b  may create a new construct for each new data type corresponding to the context or user determination, or the user may initiate or confirm such creation. Other examples will also become apparent to those skilled in the art in view of the discussion herein. 
     User information  201  also includes deal, transaction and transaction aspect data  212 , as well as parameters according to which such information may be generated, stored, retrieved, modified, manipulated or presented. As with user status/tracking data  211 , KB controller  111   b  may store associations with such data including user selectable parameters (“transaction attributes”). Transaction attributes may, for example, include but are not limited to assignment, status or access parameters through which a system  101  may determine a user or other participant status in conducting, assignment or read, write or modification access to one or more particular deals, transactions or transaction aspects. Such attributes may be applicable to all or particular data types or data thereof (e.g., user-determined range of calendar dates, notes, notes including particular references or terms, tasks corresponding to a particular user, contacts corresponding to RE business management, one or more particular deals, transactions or transaction aspects or of a particular type, and so on, or some combination). 
     Various embodiments may further provide such parameters for such conducting, assignment or access by a user organization, a user team or one or more members thereof, guest access, session sharing, community sharing, and so on, which parameters are indicated respectively as assignable tasks (of status/tracking data  211 ) organization/team status/assignment data  213  and guest/session and community data (of administration/tracking data  215 ). In various embodiments, such parameters may be provided as globally applicable or according to data type, deal, transaction, transaction aspect, data type, user, other participant, group or some combination. Thus, for example, KB controller  111   b  may provide for enabling or disabling task status/assignments or guest, session sharing or community privileges globally (to all users or other participants), respecting a particular deal, transaction or transaction aspect, notes or personal contacts, a fired employee, a now excluded or “dropped” participant, a subcontracting group, and so on, or some combination. 
     Of the remaining illustrated user data  201 , organization/team data of status/assignment  213  may further store member (e.g., employee) information of an organization to which the user may be an agent or an indicator of such data as may be separately stored (e.g., a remote organization chart or directory). In other embodiments, status/assignment data  213  may also store user type or status of the user, user&#39;s organization or team or members thereof, which data (or parameters corresponding thereto) may be associated with one or more deals, transactions transaction aspects or properties. In this instance, status may, for example, correspond with one or more of team leaders, coordinators, task assignors/assignees, and so on as may correspond to all deals, transactions or transaction aspects, or one or more particular deals, transactions or transaction aspects or groups thereof. User type, as with other participant types, may correspond with a buyer or seller or other type of person when participating in the disposition of a subject property. In other embodiments, user type may also correspond to real estate product/service providers or others, among other combinable alternatives. 
     Note that while system  101  may often automatically determine a user type, for example, as corresponding to a particular other participant (e.g., user buyer if the other participant is a seller or user seller if the other participant is likely a buyer), this may not always be the case. For example, a user may assume a potential or actual role of contractor for all or part of a renovation or update, or the user may desire and system  101  may provide for comparing a valuations or other characteristics that may comprise outcomes of the user potentially or actually assuming the role of different participant types in conjunction with the same or different deals, transactions or transaction aspects, or with respect to various properties or in conjunction with different product/service vendors. In such cases, system  101  enables a user to determine/select his or others&#39; participant type/status. Various such embodiments may not only provide for such “what if” comparisons, but also for modifying data input, processing or various other system  101  features in accordance with a particular user participant type or parameters corresponding thereto. 
     Custom forms, automated marketing scheduling, match/link and other processing and custom fields store data/parameters that applicable to such features, which features are discussed in greater detail below. Administrative/tracking data  215  may, in various embodiments, apply to a user, or further, a guest, session sharing participant or other participant. Administrative tracking data  215  may, for example, include user name, identifier, contact, other information and parameters, access privileges and parameters (e.g., including system  101  permissions, usernames and passwords for a user and any corresponding further participants), system  101  operational preferences and parameters, the above-discussed guest/session and community data, and preferences and security data and parameters (e.g., sharing privileges, encryption, and so on or some combination). Other user data or some combination may also be utilized in accordance with the requirements of a particular embodiment. 
     KB controller  111   b  also provides for storing and associating with a user corresponding buyer and seller information that may be accumulated by the user (e.g., directly or indirectly via system  101  features or via guests, session sharing or the community). In the present embodiment, buyer or seller data  202  may include substantially the same set of data types. These include participant type  202 , participant status  222 , deal/transaction status  223 , legal, financial or confidential details  224 , participant deal (or other) history data  225 , participant history status data  226 , business/organization data  227 , agency data  228 , communication data  229  and access data  230 . 
     Participant type  221  indicates a classification of the participant in conjunction with a deal, transaction or transaction aspect. In one embodiment, participant type  221  indicates whether the participant is a buyer or seller, while in other embodiments, participant type may include further predetermined or other classifications as well (e.g., renter, owner, occupier, lessor/lessee, contractor, other product/service provider, non-guest agent, and so on, or other participant types may also be utilized in accordance with a particular implementation). As with a user, such data may be associated with all or particular deals, transactions, transaction aspects, properties, or various other transaction attributes. 
     Buyer or seller data may also include participant status information  222 . In the present embodiment, KB controller  111   b  may store status information including at least three basic participant status types to which a participant may be advanced by a user: a lead, prospect or party to a deal. Without intended to be limited to a particular definition, leads may include participants of which a user (or assigned other person authorized by a user) may become aware but may not yet have contacted or may not have accumulated sufficient basic information to determine that the participant should be advanced or to actually advance the participant to prospect status, and who the user has determined are not yet parties to a deal. Prospects may include participants who have been contacted or for whom at least sufficient basic information has been accumulated, who are not yet parties to either any deal or a current deal. Parties to a deal may include those participants for whom a deal has been initiated and not yet concluded. (It will, however, be appreciated that other participant status alternatives may also be utilized in accordance with the requirements of a particular implementation.) 
     While participant status is typically assigned by user advancement (e.g., see above and below), KB controller  111   b  may also store parameters according to which deal engine  111   d,  transaction/task engine  111   d  or other system  101  components ( FIG. 1A ) may automatically advance or assign participant status. Such status assigning/advancing parameters may, for example, include assigning/advancing participant status: as a party to a deal responsive to determining that the participant has become associated with a deal, as a prospect or party to a deal responsive to accumulation, excuse or null entry of a predetermined amount or particular participant information corresponding to a lead, participant or party to a deal, as a prospect or party to a deal responsive to determining that a particular contact has been made or notated in a note that corresponds with a deal, and so on, among other combinable criteria. 
     KB controller  111   b  may store participant status data as participant status indicators indicating that one or more statuses are applicable to the participant. Typically, lead status may exist only until a corresponding participant is advanced to prospect. However, a participant may retain prospect status generally, even though the participant may be advanced to “party to a deal” status in conjunction with one or more potential or actual deals or groups of deals (e.g., by a user selection via an REB interface control provided by REB interface engine  111   c  of  FIG. 1A  or automatically by system  101 ). As will be discussed, KB controller  111   b  responds to advancement of a non-user participant (or user) by modifying the tools, data, or other interface portion presentation accordingly. Such interface modifying may, for example, include hiding or presenting such aspects, presenting such aspects in a particular manner, and so on. (Various interface embodiments may, for example, provide for presenting visual, audio or other sensory or media components in a configuration or presentation that distinguishes completed or other aspects that likely will be merely presented from incomplete, not yet presented or other aspects that may require modification, and so on. One embodiment, for example, implements such interfacing in a manner that corresponds to a dual-timeline/persistence interface model that is discussed in greater detail below). 
     Buyer or seller data  202  may also include deal/transaction data  223 . In this embodiment, such data may include status qualifying transaction attributes, such as indicating tasks that may be assigned or otherwise assumed by a participant, planned or critical time for completion. (Time for completion may, for example, include user entered or system  101  generated times according to which a deal, transaction or transaction aspect may be impacted or one or more users/ participants should be sent predetermined type, content or content criteria of phone, email, instant message, fax or other alert indicator, and so on.) Status qualifying attributes may also include, value/priority of a participant action/inaction or completion of the task, response to a lead, prospect or other contact or marketing campaign (e.g., see below), incompleteness, type(s) or nature (e.g., potential impact, priority and so on) of lack of completion of one or more deals, transactions or transaction aspects, and so on, among other combinable alternatives. 
     Buyer or seller data may also include legal, financial or other information  224  that may include confidential user information (“confidential user information”), or may include history information corresponding to a deal, transaction or transaction aspect  225  or participant status  226 . Confidential user information may, for example, include user information (e.g., user name, social security number, account numbers, aliases, username, and so on), well as general or specific assets, liabilities, credit report or other information that may impact extension of credit or other user/other person or organization resources to the participant, or still other information that may impact dealing with the participant or the absolute/comparative desirability of doing so (e.g., as compared to one or more other participants or potential participant deals). 
     Deal history information  225  may, for example, include indicators or other accumulated information accumulated by or for use by the user that may relate to prior dealings with the participant by the user or others. Such information may vary widely and may, for example, include indicators, other data or parameters for the user/system  101  determining the participant&#39;s manner of dealing, mode of dealing or prior dealings. Manner of dealing may, for example, include objective or subjective assessment of absolute or conditional likeability, fairness, responsiveness, openness to alternatives, reaction or other response to general or particular time, event or other conditions, and so on. Mode of dealing may, for example, include telephone, email, instant messaging, fax, video, graphics, speech recognition/synthetic speech, messages, in person meetings, and so on. Prior dealings may, for example, include indicators, data or parameters for determining the occurrence, types, events, results or other aspects of prior dealings with the participant by the user or others. As with other accumulated user, participant or property information, deal history information  225  may, for example, be retrieved by KB controller  111   b  for use by suitability matching/linking engine  111   g,  other engine  111  components or still other system  100   a  components ( FIG. 1A ) for conducting their respective real estate management or knowledge acquisition aspects or for presenting such raw or processed data or indicators thereof to a user for use in the conducting of deal/transaction viability, likely difficulty, prioritization, value, conditions or other real estate management or knowledge acquisition aspects. 
     Participant history status information  226  may, for example, include data or parameters for indicating a user dealing status (e.g., current engagement in real estate business), financial position or properties held, disposition to engaging in RE business management generally “the right deal” (e.g., seller, buyer, property, terms, conditions and so on) or with the user, user organization, team, team member(s), and so on. Participant history status information  226  may also include last contact with the participant or last update of participant information, as well as an assigned priority, value of conducting real estate business with the participant, and so on. 
     Of the remaining knowledge base data of the illustrated example, administrative/tracking data  227  includes identification and relationship information corresponding to a user organization, its employees, and so on, as well as a group or team and the status with which members may conduct real estate business (generally or with respect to a particular deal, transaction or transaction aspect. Agency data  228  includes intra or extra organization or team agents or organizations with which the participant does or tends to conduct real estate business, their role in conducting such business or conditions under which an agent or agents should be contacted, and system access that may be made available to such agents. (Similar information may also be stored with respect to administrative/tracking data. Communication data  229  includes available communication mechanisms and corresponding contact information corresponding to the participant, organization, group or agents. Finally, access data  230  includes guest, session sharing and community data and parameters that may be allocated or provided to the participant or his co-participants (e.g., organization, group or agents) and the respective limitations of such access, e.g., as was already discussed above. Those skilled in the art will appreciate that other participant data or parameters may also be utilized in accordance with the requirements of a particular implementation. 
     Property data  201   a - b,    202   a - b  and  203   a - b  includes data and parameters corresponding to the user and one or more accumulated participants respectively and is associated with respective ones of the aforementioned user and accumulated participant data and parameters. In this embodiment, property data and parameters may be substantially the same for users and various accumulated seller and buyer participants. More specifically, property data may correspond with a property that is held by a user or other participant seller or that is requested or otherwise determined to be preferred by a user or other participant buyer (e.g., according to stored results of personal knowledge, participant interview/submission and so on). 
     Each of property data  201   a - b,    202   a - b  and  203   a - b  includes property type data, location data, disposition data, ownership type data, property characteristic data, property condition data, property renovation/updating data and so on. Property type data indicates a type of property, for example, single or multiple family home, n-unit office building, n-unit condominium, leased land, and so on. Property location data indicates aspects of the property relating to its location, for example, end unit, region, neighborhood, district, proximity to schools, shopping transportation, airport, industry, zoning, and so on. Property disposition data indicates others&#39; held or “preferred” legal or other interest in the property (e.g., own, subject to lien by x-organization, repossessed/status, short sale opportunity, and so on). Ownership types indicates the participant&#39;s held or “preferred” or others&#39; ownership interest in the property, for example, as owner, occupier, having n-renters of m rental units at x dollars per month, and so on. Property characteristics data includes data describing the property held or “preferred”, for example, including number of bed, bath or other rooms, construction, dimensions, exterior space, lot size, accoutrements, and so on. 
     Property condition data includes indicators of the condition of the property, for example, including damage, work needed generally, in accordance with the location or market, or according to other predetermined criteria for evaluating a condition of a property or portions thereof. Property renovation/updating data indicates renovation or updating that may be needed and not yet described, completed or scheduled, as well as progress or other information relating to the setting up or conducting of renovation or updating, and so on. Those skilled in the art will appreciate that other property data or parameters may also be utilized in accordance with the requirements of a particular implementation. Property data may also be utilized in presentation or other manners as, for example, have already been discussed with reference to user or participant data and parameters. 
     It should also be noted that knowledge base data  112  or  200  data/parameters are not limited to textural data and any or all may also include images, audio, video, fly thru or other animation, and so on, as will be further discussed herein or otherwise in accordance with the requirements of a particular implementation. 
     Returning now to  FIG. 1A , REM interface engine  111   c , along with the above discussed- knowledge base and other REM system components, provides a real estate business environment within which one or more users may individually or collaboratively conduct real estate business management and share-able real estate business knowledge base accumulation. REM interface engine  111   c  provides for generating at least a current REM interface portion of an REM interface, for populating the interface portion with currently applicable data, if any, and for causing the interface portion to be transferred to one or more corresponding user devices, e.g., user devices  104   a - c.  REM interface engine  111   c  also provides for receiving, from a user device, responsive data entry, tool invocation or other user interaction with a current REM interface portion, transferring corresponding invocation or data information to communication engine  111   a,  and, if applicable, (e.g., to the received user interaction information), receiving REM interface data/parameters from other system  101  components and generating an REM interface portion corresponding with the user interaction information and the data and parameters. REM interface engine  111   c  also provides for interfacing with and causing data to be received from or transferred to data acquisition nodes,  105 , external data sources  106  and data presentation nodes  107 . 
     In one embodiment, the REM interface includes a group of Web pages that may include text, audio, graphics, video or other multimedia components. Those skilled in the art will appreciate that that REM interface engine  111   c  may generate the Web pages by constructing one or more of the pages in substantially real time or on demand, or the Web pages or portions thereof may be predetermined (other than the data with which they may be populated) and engine  111   c  may conduct the generating by integrating such portions. 
     It will become apparent, however, that the latter case of integrating predetermined interface portions may deviate substantially from conventional interfacing. For example, REM interface engine  111   c  may generate an interface or interface portion that may correspond with one or more of users and other participants, participant types, statuses, a deal, transaction or transaction aspect and advancement of a deal, transaction or transaction aspect, among other transaction attributes. 
     RE Interface engine  111   c  in one embodiment receives such attributes from one or more of communication controller  111   a  (e.g., as user interaction data received via a user device), and deal engine  111   d  or transaction engine  111   e  (e.g., as knowledge base data, i.e., or attributes, that one or both of engines  111   d - e  may invoke KB controller  111   b  to retrieve from REM KB  112 . Thus, not only may the user advances or be advanced by system  100   a  through a potential/actual deal (e.g., via pre-deal, intra-deal, inter-deal or knowledge base transactions or transaction aspects) without requiring user selection of independently operable generic tools. (Rather, interface engine  111   e  provides interface portions corresponding to and anticipating such advancement, thereby enabling the user to avoid having to locate and utilize tools within a remote or temporary popup interface menu or remote toolbar while advancing a particular actual/potential deal.) Interface engine  111   e  in one embodiment also generates an REM interface portion in which tools for advancing or responsive to an advanced potential/actual deal integrate non-obtrusively (with respect to a user workspace) with an already presented existing interface. The embodiment further provides for automatically providing new interface portions or RE management processing (e.g., according to such data or transaction attributes) that correspond with advancing an actual/potential deal, transaction or transaction aspect and that were not previously presented to the user. Moreover, RE interface engine  111   e  provides for presenting the interface portion or tools for invoking RE management processing in which deal or transaction processing are presentable independently and without obscuring the corresponding transaction aspect processing that may be concurrently conducted, an example of which is discussed below, beginning with reference to  FIG. 3A . 
     REM interface engine  111   a  further provides for populating the interface with data corresponding with deal, transaction or transaction aspects received from suitability matching/linking engine  111   f  or information received from other of engines  111   b - o.  The generation of the current interface portion may be conducted in an otherwise conventional or other suitable manner, and may utilize one or more of extensible markup language variants (e.g., XML) or other suitable page creation constructs that may further include application program interface or API commands for invoking application programs or APIs  103   a  that may reside on the user device. 
       FIGS. 3A through 3B , with further reference to  FIG. 1A  illustrate how REM interface engine  111   a  provides a hierarchical workflow based REM interface that may include singular or multiple split timelines or “workflows” and persist-able transaction aspect advancement or target data. By doing so, engine  111   a  thereby enables one or more users or other participants to be more optimally guided through a more efficient conducting of real estate business management and share-able independent knowledge base accumulation (i.e., and utilization).  FIGS. 4 through 70  further illustrate the exemplary REM interface in greater detail, as well as examples of system  100   a  operational components (“features” or “REM tools”) that may be accessible to users by interacting with the REM interface.  FIGS. 4 through 70  also provide a “walk through” of various visual and primarily textual presentations, user interactions and system  100   a  responses thereto of the interface and operational features. (It will be appreciated, however, that a resulting REM interface is not limited to any particular manner of interaction or media. Rather, various REM interface embodiments may employ mouse, keyboard, speech, biometrics, signal, actuator, controller or substantially any other interaction mechanism, and may provide for the use of text, graphics, audio, speech, video, animation or substantially any other type of multimedia presentation or interaction, in accordance with the requirements of a particular implementation.) 
       FIGS. 3A through 3B , for example, illustrate an REM interface embodiment  300   a - 300   b  that may be generated by REM interface engine  111   a.  For consistency sake, REM interface  300   a  is again implemented as a group of Web pages that may be presented by Mozilla Firefox, Microsoft Internet Explorer or substantially any other conventional or other Web browser, e.g., Web client  201   a,  Web client enabled application portion or additions, extensions or enhancements thereto (hereinafter collectively referred to as simply a “browser”). Applicable real estate data and the now well known Web browser menus/toolbar options  301   b  and status bar  301   c  have, however, been removed so as not to obscure aspects of the invention.  FIG. 3   a  more specifically illustrates an example of a hierarchical split-timeline REM interface configuration  300   a,  while  FIG. 3   b  illustrates a further secondary hierarchical split timeline interface configuration  300   b  that may also be included in an REM interface generated by REM interface engine  111   a  of  FIG. 1A . (For purposes of the REM interface discussion, the term “interface” will refer collectively to a more complete interface that may include multiple presentations, e.g., screens or Web pages, as well as one or more individual “pages” or “screens” of the REM interface.) 
     As shown in  FIG. 3A , interface  300   a  comprises, in addition to the above-noted browser features  301   a - b,  visually presented interface components including main menu  302  and workspace  303 - 306 . Main menu  302  provides a vertically stacked menu structure of menu options and sub-menu options (indicated by right facing arrows). Unlike conventional menus that are typically organized as encapsulated generic groupings tool functions, however, main menu  302  is organized according to managing real estate business, corresponding workflow and a third party participant type, here, sellers  331  and buyers  332 . A further “team” menu  333  also provides, in a workflow based manner, for conducting tasks relating to managing a user team, and an “administration” menu  334  provides for conducting such administrative tasks as setting up an account for an organization or agents thereof on REM system  101 , and entering users. All information entered via invocation of main menu  302  or further interaction with REM interface  300   a,  according to one embodiment, is stored by KB controller  111   b  in a REM KB, e.g.  112  or  200  of  FIGS. 1A-1B  and  2  respectively. (Administration information is, for example, stored as administration/tracking data, and so on, as was already discussed. Note that a “task” may generally include an assigned or otherwise assumed activity of initiating, conducting, completing or otherwise managing a deal, transaction or transaction aspect, which task may also include accumulating knowledge base data or parameters.) 
     Seller menu  331  provides for conducting real estate management and knowledge accumulation corresponding to third party participant status and may, for example, include prospects, leads and parties to a deal or “case”. While the aforementioned status advancing order may, for example, include leads, then prospects and then cases, sellers menu  331  ordering instead corresponds with system  100   a  providing for independent and concurrent efforts, in addition to managing development of leads and ongoing deals, to accumulate an inventory or pool of re-usable prospects with which new or further deals may be generated. 
     Buyers menu  332  provides for conducting real estate management and knowledge base accumulation corresponding to third party participants whose subtype may, for example, include a preference for retail property, lease options, rental property (“landlord”) or property purchased for rehabilitation and resale or “rehabber”. (Such data may also be stored in a corresponding knowledge base, e.g., REM KB  112  of  FIGS. 1A-1B  or REM KB  200  of  FIG. 2 , as a property data property preference that may be associated with a corresponding participant.) Buyers may also, in various embodiments, be classified according to their status as a lead, prospect or party to a deal. 
     Team menu  333  is arranged according to tasks that an individual user or user conducting real estate business management/knowledge accumulation as part of a team may focus on at any given point. As shown, such tasks may, for example, respectively include reviewing, working with or otherwise managing contacts, documents, particular transactions or transaction aspects that may also be specially indicated as tasks, World-Wide-Web hyperlinks or correspondences of system  101  data, studying (“the classroom”) and conducting system  100   a  user discussion (“forum”). 
     The REM interface  300   a  workspace  303 - 306 , ignoring search field  306  for now, is divided into multiple (here, two) independently operable but advancement-coordinate-able regions: deal-and-transaction timeline region (“deal region”)  303   a  and transaction-and-transaction-aspect (“task”) timeline region  304   a.  Each of regions  303   a  and  304   a  is further divided into a variable number of workflow regions that are designated by region selection handles depicted as “tabs”  303   b,    304   b,  and at least one work area  303   c,    304   d.  Search field  306 , provides for user-initiated simple or complex searches of all or portions of workspace  303 - 306 , REM KB  112  ( FIG. 1A ), or further, extra-workspace sources including, for example, the community of users or non-user participants, data acquisition nodes  105 , external data sources  107 , data presentation nodes  107  ( FIG. 1A ), network resources including but not limited to the Internet, and so on, or some combination. Searches may be more generic or may be more limited, for example, according to any one or more of: user, participant, document, deal, transaction, type, status, interface portion, conditions, other KB parameters, contextual delimeters, and so on. See, for example, the above REM KB discussion. 
     Interface  300   a  provides for presenting regions  303   a  and  304   a  as hierarchically based multiple independent workflows or timelines, or further, for persisting within the interface  300   a  presentation essential information relating to currently conducted management of a current deal, transaction or transaction aspect or knowledge base accumulation. In one embodiment, for example, REM interface engine  111   c  generates timeline regions  303   a,    304   a  and workflow regions  303   b,    304   b  and tool or feature components to be presented within such regions as corresponding with current transaction parameters including a currently selected non-user participant type, and further, the current third party participant status or sub-type. REM interface engine  111   c  in the present embodiment conducts such generation regardless of whether a particular third party participant is currently selected or even yet known, so long as such parameters may be ascertained, e.g., through user selection or system  101  reference to REM KB or other determination. 
       FIG. 8 , for example, illustrates how REM interface engine  111   c  responds to user selection of a “seller lead” by generating task timeline region  801   a  and deal timeline region  801   b,  and inserting, within each timeline region, workflow regions  802   a  and  802   b  respectively. REM interface engine further populates workflow regions  802   a  and  802   b  with interface components  803   a  and applicable data, if any, corresponding to the seller type and lead status, or further, to one or more particular sellers or properties. (In this example, the task timeline workflow regions include owner information, property information and mortgage information, while the deal timeline workflow regions include notes, tasks, documents and links. Interface components for workflow region  802   a  include portions of a data entry form for accumulating basic seller lead related information or “owner information” including identification of the property, owner information, contact information and miscellaneous other information; REM interface engine  111   c  also populates deal timeline region. The selected document workspace region of deal timeline workspace regions  802   b  is populated as blank, since there is no document management associated with the user selection, at least at this point in managing the illustrated seller as a lead. 
     Returning to  FIG. 3A  with further reference to  FIG. 8 , REM interface engine  111   c  also generates workflow regions according to a timeline or workflow associated with the current participant type and status. In this example, the workflow is applicable to both of the inserted workspace regions and the ordering of the workspace regions. REM interface engine  111   c,  for example, inserts additional ones of deal timeline workspace regions  304   b  as corresponding to the workflow associated with the type and current participant status, or more specifically, the advancing of the current participant&#39;s status. (Stated alternatively, engine  111   c  renders certain workspace regions unavailable unless a current participant has advanced or is otherwise associated with a corresponding participant status.) 
     Specifically, REM interface engine  111   c  always presents notes region  341  and, in accordance with the general applicability and importance of note taking, always placed such region first (i.e., leftmost of tabs  304   b ). REM interface engine  111   c  adds, to the right of tab  304   c,  seller leads workflow regions  342  as corresponding to the participant type and status of “seller” and “lead”, workflow regions  343  as corresponding to “seller” and “prospect” and workflow regions  344 - 346  as corresponding to “seller” and “party to a deal” respectively. 
     REM interface engine  111   c  further adds workflow regions within such workflow region groups according to a workflow ordering with which a user will likely at least initially utilize each successive workflow region, e.g., an order in which seller information is typically more optimally obtained. While in the present embodiment the workspace region, interface components and ordering thereof are predetermined (e.g., and stored in REM KB  112 ), it will be appreciated that other embodiments may also provide for imposing one or more component or data content/ordering variations according to user preferences, system  101  monitoring of actual use and determination therefrom of general, initial contact, type, use, location, meeting, call or other context, per session or other user workflow or workflow or other tendency, and so on or some combination. (See, for example,  FIGS. 6-9 ,  18 - 26  and  28 - 40 , which also illustrate examples of interface components corresponding to each of the respective groups of workspace regions.) 
     Continuing with  FIG. 3B , REM interface engine  111   c  also conducts such workflow based interface generation with regard to sub-workspace regions, which engine  111   c  also automatically generates and inserts according to the split timeline configuration. In this embodiment, for example, REM interface engine  111   c  responds to a current third party participant type and status of “seller” and “lead” by generating and inserting, into task timeline region  303   a,  sub-workspace regions  303   d  including subject property  371 , and owner information, contact information and other information  372 . Engine  111   c  further generates and inserts, into deal timeline region  304   a,  sub-workspace regions  304   e  including mortgages  381 , and liens, comparables or “comps, short sale and paperwork  382 . Engine  111   c  may also inserts corresponding interface control components, including but not limited to inserting save button  383  as interface component  304   f.    
     REM interface engine  111   c  further conducts such workflow based interface generation such that any two or more timeline regions and workflow regions may operate in an yet coordinated manner that may further persist selected data. That is, an interface portion presented in timeline region  303   a  or modification or replacement of region  303   a  may occur without impacting the interface portion presented by timeline region  304   a  and visa versa. However, engine  111   c  also generates coordinated sets of workspace regions and sub-regions such that user workflow may be co-supported by the interface presented by such regions and sub-regions.  FIG. 20 , for example, illustrates one embodiment in which the interface portion  2001   e  presented by timeline region  2001   a  may vary according to user or system  101  selection of workspace regions  2001   b  without obscuring or otherwise impacting the interface portion  2002   f  presented by timeline region  2002   a  via selection of workspace regions  2002   b  and visa versa. Moreover, at least a portion (and typically all) of workspace regions  2001   b,    2002   b  and sub-regions  2001   c,    2002   d  are generated by engine  111   c  in a coordinated manner, such that the information presented is co-supportive, and in a manner that may persist selected data. 
     Thus, for example, responsive to a user initiating an assumed a task of contacting a seller prospect (as evidenced by the addition of seller prospect tabs  2002   c ) regarding information not yet collected from the seller, REM interface engine  111   c  may present the user with the illustrated interface and with contact form  2001   e  automatically selected. The user may review deal or transaction data corresponding to which the seller corresponds in workspace regions  2002   b  or sub-regions  2002   d  before, during or following the call without affecting form  2001   e,  which regions and sub-regions are coordinated with regions  2001   b  and subregions  2001   c,  and which regions and sub-regions are easily reviewable due to their timeline or workflow ordering. The seller&#39;s identification and other information also remains presented. Returning to  FIG. 1A , REM interface engine  111   c  also persists selectable data, which engine  111   c  has automatically selected (e.g., as a default) as including identification of the seller called by the user as the owner-occupier of the property and having the name Barbara Moore. Therefore, the user may also be presented with a persisted reminder as to such identification, even though the user may also browse workspace regions  2001   b  or workspace sub-regions  2001   c  other than form  2001   d.    
     (It will be appreciated persistable data is not limited to participant identification or persisting of selected data in only a timeline “region bar”. Rather, the particular data may be determined by a user or automatically by system  101  as corresponding, for example, to a default data type, a data type that corresponds with a currently selected workspace region or group of workspace regions, context, deal, transaction or transaction aspect, and so on, in accordance with the requirements of a particular implementation. Visual perisitable data may also be inserted in other portions of a presented interface or other mechanisms may also be used, e.g., pop-up, mouse-over or other actuation, speech, and so on.) 
     TEAM—generated in an inter-screen workflow supporting manner 
     Main screen 
     Assignment—manager, assignee 
     Other interface characteristics—listview versus timeline or workflow view 
     Returning again to  FIG. 1A , deal engine  111   d  and transaction/task engine  111   e  provide for responding to communication controller  111   a  by controlling REM system  101  operation corresponding to potential and actual deals (or “cases”) and to transactions, transaction aspects and tasks respectively. More specifically, deal engine  111   d  provides for responding to REB interface engine  111   c  requests (via controller  111   a ) for deal status information or data by invoking KB controller  111   b  to retrieve such data from REM KB  112  and transferred data to REB interface controller  111   b.  Deal engine  111   d  also provides for initiating KB controller  111   b  for storing such data as may result from user interaction, e.g., utilizing a deal workspace region ( FIG. 3   a -b), and for initiating system  101  components corresponding to a deal or team operation (e.g., components  111   f  and  111   k - n ) and returning resulting data to KB controller  111   b  for storage or REB interface engine  111   b  for use in generating an REB interface portion. Deal engine  111   d  further provides for invoking and receiving responses from transaction engine  111   e  corresponding to transactions, transaction aspects and designated tasks that may be utilized in providing responses to invocation respecting deals. 
     Transaction/task engine (“transaction engine”)  111   e  operates in substantially the same manner as deal engine  111   d,  but with regard to transactions, transaction aspects and designated tasks, and responsive to deal engine  111   d  operation. More specifically, transaction engine  111   d  provides for responding to REB interface engine  111   c  requests (via controller  111   a  and deal engine  111   d ) for transaction, transaction aspect and task status information or data by invoking KB controller  111   b  to retrieve such data from REM KB  112  and transfers such data to deal engine  111   d.  Transaction engine  111   e  also provides for initiating KB controller  111   b  for storing such data as may result from user interaction, e.g., utilizing a deal/transaction or transaction/task workspace region ( FIG. 3   a - b ), and for initiating system  101  components corresponding to a deal or team operation (e.g., components  111   g - j ) and returning resulting data to KB controller  111   b  for storage or REB interface engine  111   b  (via deal engine  111   d ) for use in generating an REB interface portion. In accordance with such an arrangement of deal engine  111   d  and transaction engine  111   e,  deal engine may determine control, status or data corresponding to a deal. Deal engine may also delegate those aspects that may correspond with an underlying transaction, transaction aspect or designated task to transaction engine  111   e  and delegate those aspects that correspond with a component processing to a corresponding (deal level) component. Deal engine may also incorporate transaction, transaction or task results received from transaction engine  111   e  or such other system  101  components in forming a response to the deal engine invocation. 
       FIG. 71A-D ,  FIG. 72A-C , and  FIG. 73A-D  are flow diagrams illustrating embodiments that may comprise one or more of the components of the estate business, collaboration and knowledge acquisition sharing system according to any of the embodiments of the invention. 
       FIGS. 71A-D  will now be described.  FIG. 71A  begins at start point  7100   a.  Accumulate, at a server, a knowledge base of real estate information corresponding to users, properties, real estate buyers and real estate sellers (e.g. independently of a real estate transaction (stage  7102 ). Receive, from a remote user device, user information, the user information including identifying information identifying a target property and a target real estate transaction (e.g. the ‘RE’ transaction) (stage  7104 ). Store at least a portion of the user information in the knowledge base, enabling use of the info in conjunction with other forms/transactions (stage  7106 ). Determine, by the server, a base document corresponding to the real estate transaction (e.g. stored by the remote server or received from the user) (stage  7108 ). Generate, by the server, a resulting document that integrates the user information (stage  7110 ). 
     Continuing with  FIG. 71B , if the stored ‘RE’ information is used (decision point  7112 ), then determine a subset of the accumulated ‘RE’ information corresponding to the user and the target transaction (stage  7114 ), and integrate the subset of the accumulated ‘RE’ information into the resulting document to form an integrated document (stage  7116 ). Whether using stored ‘RE’ information or not, then initiating, by the server, execution of a document manipulating program by the user device (e.g. use API to launch a word processing program on the user device) (stage  7118 ). Initiate, by the server, loading of at least one of the resulting documents and the integrated document by the computer program (stage  7120 ). Initiate, by the server, processing of at least one of the resulting documents and the integrated document by the computer program (stage  7122 ). 
     Continuing with  FIG. 71C , at point  7100   b,  modify, by the user using the computer program, the at least one resulting document or integrated document to form a modified document (and transferring the modified document to the server) (stage  7132 ). Receive, at the server, the modified document (stage  7134 ). Parse, at the server, the modified document to determine whether at least one of the base document and the subset of the accumulated ‘RE’ info have been modified (stage  7136 ). If the information has been modified (decision point  7138 ), update, at the server, the knowledge base of real estate information according to the modified subset of accumulated ‘RE’ information (stage  7140 ). Associate, at the server, the copy of the base document with an indicator indicating the user (stage  7142 ). 
     Continuing with  FIG. 71D , if the base document has been modified (decision point  7144 ), then store, at the server, a copy of the base document according to the base document modifications (stage  7146 ), and associate, at the server, the copy of the base document with an indicator indicating the user (stage  7148 ). 
       FIGS. 72A-C  will now be described.  FIG. 72A  begins at start point  7200   a  with determining average costs for conducting specific updates to a generalized sampling of properties (stage  7202 ). Determining average cost deviations of the average costs for the conducting of specific updates according to an accumulated knowledge base of property information of properties (e.g. location of property) (stage  7204 ). Receiving, from a user, update indicators that applicable ones of types and repetitions of updates may be conducted on areas of target property (e.g. to features located in or relating to specific areas of a home or home layout to place the home in an at, below or above market value or other specified condition) (stage  7206 ). Receiving, from a user, one or more cost difference indicators indicating cost differences between the average costs or average cost deviations and update costs applicable to the user, if any (stage  7208 ). 
     Continuing with  FIG. 72B , if there are not differences (decision point  7210 ), then the following stages are performed. Determining a cost estimate for conducting updates corresponding to the user according to a user selection of at least one of the average costs, average cost deviations and cost difference indicators (stage  7212 ). Generating a project estimation report corresponding to the cost estimate and transferring the cost estimate report to a user device (e.g. to a remote user device) (stage  7214 ). Storing cost estimate indicators indicating the cost estimate and an association of the cost estimate with the user (stage  7216 ). Determining one or more ‘RE’ transactions associated with the user (stage  7218 ). Associate the cost estimate indicators with the ‘RE’ transactions (stage  7220 ). Applying the cost estimate to a viability, cost or profit analysis, (or further, negotiation or other subsequent transaction) of the user if the user conducts such analysis (e.g. deal filter, profit analyzer) (stage  7222 ). 
     If there are differences (decision point  7210 ), then the stages in  FIG. 72C  are performed, as identified at point  7200   b.  Determine at least one reliability indicator indicating a reliability of the cost difference indicators (e.g. according to a rating of user reliability, user cost reliability history, applicable user experience, contractor or other product/service provider data, market variation/fluctuations, a consensus, significant number or other predetermined acceptability measure of other users, search data, etc. (stage  7232 ). If the analysis indicates sufficient reliability (decision point  7234 ), then compare the cost difference indicators with classification indicators to determine if the cost difference indicators correspond with average cost estimate or average cost deviation error, location variation or price fluctuation (e.g. by comparing with information utilized in forming reliability indicator (stage  7236 ). Update at least one of the average cost estimate, average cost deviation or a price fluctuation estimate according to the determining of block  7136  (stage  7238 ). Determine whether other users may have been or may be impacted by the update, and notifying one or more of the other users as to the update or providing opportunity for updating of resultant data produced using a corresponding one or more of the average cost estimate or deviation (stage  7240 ). 
       FIGS. 73A-73C  will now be discussed.  FIG. 73A  begins at start point  7300   a.  Receiving, from a plurality of users, third party participant data corresponding with the disposition of property corresponding to the respective third party participants (e.g. buyer, seller and property data of actual or potential buyers or sellers of real estate in which the buyers and/or sellers may include one or more of leads and prospects) (stage  7302 ). Receiving, from third party participants or other non-users, third party participant data corresponding with the disposition of property corresponding to respective ones of the third party participants (e.g. from actual or potential buyers, sellers, agents, brokers, etc.) (stage  7304 ). Associating the received data with corresponding ones of the plurality of users (stage  7306 ). Associating the received data with transaction attributes corresponding to real estate transaction data characteristics (stage  7308 ). Accumulating the data and associations in a knowledge base (e.g. storing the data and associations in a real estate business management knowledge base corresponding to a REM system (stage  7310 ). 
     Turning now to  FIG. 73B , receiving, from at least one current user of the plurality of users and subsequent to the receiving of the data, a transaction request corresponding to an actual or potential real estate deal, the request corresponding to one or more transaction attributes (stage  7312 ). Comparing the transaction attributes of the request with at least a portion of the accumulated data (or association) corresponding to the current user to determine third party participants corresponding to the request (e.g. selecting at least partially matching stored buyers that may be or become interested in purchasing a property of a current user having a property to sell or at least partially matching stored sellers that may be or become interested in selling a property of interest to a current user interested in purchasing such a property (stage  7314 ). Filtering or prioritizing the third party participants (according to predetermined criteria), such that a prioritized or filtered subset of the corresponding third party participants includes at least one of: third party participants that more closely correspond with the request and third party participants that whose data or para indicate that they will more likely or more readily consummate a corresponding real estate deal (stage  7316 ). 
     Turning now to  FIG. 73C , receiving a participation request from at least a subset of the users to share, with other users, at least a portion of third participant data (or parameters) of third party participants corresponding to the respective users in the subset of users (stage  7320 ). Comparing the transaction attributes of the transaction request with at least a portion of the accumulated data (or association) corresponding to the subset of sharing users to determine third party participants corresponding to the transaction request (stage  7322 ). Filtering or prioritizing the corresponding shared third party participants, such that a prioritized or filtered subset of the corresponding shared third party participants correspond with the request and third party participants that whose data or para indicate that they will more likely or more easily consummate a corresponding real estate deal (stage  7324 ). 
     Turning now to  FIG. 73D , filtering or prioritizing the corresponding third party participants and shared third party participants, such that a prioritized or filtered subset of the corresponding third party participants and shared third party participants includes at least one of: third party participants that more closely correspond with the request and third party participants that whose data or para indicate that they will more likely or more readily consummate a corresponding real estate deal (stage  7326 ). Compiling the shared third party participant data to at least one of: remove third party participant identification information identifying at least a subset of the shared third party participants, and to summarize the corresponding third party participant data (stage  7328 ). Associating, with the compiled third party participant data to form associated third party participant data, at least one of: user information of respective corresponding users, and contact information for contacting the respective corresponding users (stage  7330 ). Presenting, to the current user, at least a portion of the third party participant data resulting from the comparing of block ______ and the associated third party participant data (stage  7332 ). 
     The  FIG. 74A-B  flow diagram illustrates a computing system embodiment that may comprise one or more of the components of  FIG. 1A  through  FIG. 1B . While other alternatives may be utilized or some combination, it will be presumed for clarity sake that components of systems  100   a  through  100   b  and elsewhere herein are implemented in hardware, software or some combination by one or more computing systems consistent therewith, unless otherwise indicated or the context clearly indicates otherwise. 
     Computing system  7400  comprises components coupled via one or more communication channels (e.g. bus  7401 ) including one or more general or special purpose processors  7402 , such as a Pentium®, Centrino®, Power PC®, digital signal processor (“DSP”), and so on. System  7400  components also include one or more input devices  7403  (such as a mouse, keyboard, microphone, pen, and so on), and one or more output devices  7404 , such as a suitable display, speakers, actuators, and so on, in accordance with a particular application. 
     System  7400  also includes a computer readable storage media reader  7405  coupled to a computer readable storage medium  7406 , such as a storage/memory device or fixed, removable or stand alone storage/memory media; such devices or media are further indicated separately as storage  7408  and memory  7409 , which may include hard disk variants, floppy/compact disk variants, digital versatile disk (“DVD”) variants, smart cards, partially or fully hardened removable media, read only memory, random access memory, cache memory, battery backed memory, flash memory, and so on, in accordance with the requirements of a particular implementation. One or more suitable communication interfaces  7407  may also be included, such as a modem, DSL, infrared, RF or other suitable transceiver, and so on for providing inter-device communication directly or via one or more suitable private or public networks or other components that may include but are not limited to those already discussed. 
     Working memory  7410  further includes operating system (“OS”)  7411 , and may include one or more of the remaining illustrated components in accordance with one or more of a particular device, examples provided herein for illustrative purposes, or the requirements of a particular application. REM engine components  7412  may, for example, include one or more real estate business management systems and REM KB  7413  may include a shared real estate business management knowledge base, e.g., as discussed with reference to  FIG. 1A-B . Data acquisition node engine  7414 , external data source node acquisition engine  7415 , data presentation node engine  7416  may, for example, respectively include: a data collection program for receiving buyer or seller participant-submitted data (e.g., from a web site or call center); transfer, search, smart agent or spider program for accumulating non participant statistics, participant credit scores or records, or other data according to which real estate transactions may be conducted; and a Web site setup and transfer program for creating, populating or maintaining a user Website (e.g., for marketing a property for sale). Telecomm communication engine  7417  and telecomm message engine  7418  respectively provide for conducting Web-based, plain old telephone system, cellular or other communications in conjunction with an REM system. System administration engine  7419  provides for conducting administration of Real estate management system  101  components. Working memory of one or more processing systems may also include other program(s)  7415 , including any add-on or other code, which may similarly be stored or loaded therein during use. 
     The particular OS may vary in accordance with a particular device, features or other aspects in accordance with a particular application, e.g., using Windows, WindowsCE, Mac, Linux, Unix, a proprietary OS, and so on. Various programming languages or other tools may also be utilized, such as those compatible with C variants (e.g., C++, C#), the Java 2 Platform, Enterprise Edition (“J2EE”) or other programming languages. Such working memory components may, for example, include one or more of applications, add-ons, applets, servlets, custom software and so on for implementing functionality including, but not limited to, the examples discussed elsewhere herein. Other programs  7415  may, for example, include one or more of security, compression, synchronization, backup systems, groupware, networking, or browsing code, assessment delivery/conducting code for receiving or responding to resulting items or other information, and so on, including but not limited to those discussed elsewhere herein. 
     When implemented in software, one or more of system  100   a  through  100   b  or other components may be communicated transitionally or more persistently from local or remote storage to memory (SRAM, cache memory, etc.) for execution, or another suitable mechanism may be utilized, and one or more component portions may be implemented in compiled or interpretive form. Input, intermediate or resulting data or functional elements may further reside more transitionally or more persistently in a storage media, cache or other volatile or non-volatile memory, (e.g., storage device  7408  or memory  7409 ) in accordance with the requirements of a particular implementation. 
     Reference throughout this specification to “one embodiment”, “an embodiment”, or “a specific embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention and not necessarily in all embodiments. Thus, respective appearances of the phrases “in one embodiment”, “in an embodiment”, or “in a specific embodiment” in various places throughout this specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics of any specific embodiment of the present invention may be combined in any suitable manner with one or more other embodiments. It is to be understood that other variations and modifications of the embodiments of the present invention described and illustrated herein are possible in light of the teachings herein and are to be considered as part of the spirit and scope of the present invention. 
     Further, at least some of the components of an embodiment of the invention may be implemented by using a programmed general purpose digital computer, by using application specific integrated circuits, programmable logic devices, or field programmable gate arrays, or by using a network of interconnected components and circuits. Connections may be wired, wireless, by modem, and the like. 
     It will also be appreciated that one or more of the elements depicted in the drawings/figures may also be implemented in a more separated or integrated manner, or even removed or rendered as inoperable in certain cases, as is useful in accordance with a particular application. It is also within the spirit and scope of the present invention to implement a program or code that can be stored in a machine-readable medium to permit a computer to perform any of the methods described above. 
     Additionally, any signal arrows in the drawings/Figures should be considered only as exemplary, and not limiting, unless otherwise specifically noted. Furthermore, the term “or” as used herein is generally intended to mean “and/or” unless otherwise indicated. Combinations of components or steps will also be considered as being noted, where terminology is foreseen as rendering the ability to separate or combine is unclear. As used in the description herein and throughout the claims that follow, “a”, “an”, and “the” includes plural references unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise. 
     The foregoing description of illustrated embodiments of the present invention, including what is described in the Abstract, if any, is not intended to be exhaustive or to limit the invention to the precise forms disclosed herein. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes only, various equivalent modifications are possible within the spirit and scope of the present invention, as those skilled in the relevant art will recognize and appreciate. As indicated, these modifications may be made to the present invention in light of the foregoing description of illustrated embodiments of the present invention and are to be included within the spirit and scope of the present invention. 
     Thus, while the present invention has been described herein with reference to particular embodiments thereof, a latitude of modification, various changes and substitutions are intended in the foregoing disclosures, and it will be appreciated that in some instances some features of embodiments of the invention will be employed without a corresponding use of other features without departing from the scope and spirit of the invention as set forth. Therefore, many modifications may be made to adapt a particular situation or material to the essential scope and spirit of the present invention. It is intended that the invention not be limited to the particular terms used in following claims, if any, and/or to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include any and all embodiments and equivalents falling within the spirit and scope of the invention.