Method for providing a summary of data
Abstract
A method for providing a summary of data relating to a merger or acquisition via an interface to a database comprises identifying a plurality of issues relating to a merger or acquisition, determining a plurality of milestones associated with the merger or acquisition, identifying a plurality of projects corresponding to the merger or acquisition, gauging a progress of the projects in terms of a plurality of criterion and outputting the issues, the milestones, and the gauged progress of the projects.

Term
Term ended
Projected expiry passed 22 November 2020, 5.8 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
13 claims: 3 independent, 10 dependent
- 1A method for providing a summary of data relating to a merger or acquisition via an interface to a database, comprising the steps of:(a) identifying a plurality of issues relating to a merger or acquisition;(b) determining a plurality of milestones associated with the merger or acquisition. (c) identifying a plurality of projects corresponding to the merger or acquisition;(d) gauging a progress of the projects in terms of a plurality of criterion;and (e) outputting the issues, the milestones, and the gauged progress of the projects.
- 7A system for providing a summary of data relating to a merger or acquisition via an interface to a database, comprising:(a) logic that identifies a plurality of issues relating to a merger or acquisition;(b) logic that determines a plurality of milestones associated with the merger or acquisition;(c) logic that identifies a plurality of projects corresponding to the merger or acquisition;(d) logic that gauges a progress of the projects in terms of a plurality of criterion;and (e) logic that outputs the issues, the milestones, and the gauged progress of the projects.
Independent claims3
101 paragraphs, as filed
Field of Invention
0001The present invention relates to browsing data using a data browser and more particularly pertains to facilitating the navigation of application specific data with a data browser using a plurality of links.
Background of the Invention
0002In the past, instructional databases have been commonly used to provide users with a plethora of information. Such information may be used to execute various tasks or enable the users to accomplish a goal. Often, such instructional databases may be stored on a centralized server and provide access to a plurality of client computers via a network. In some instances, such network is the Internet in which case the database is accessed via a web site.
0003Such prior art instructional databases, however, often utilize a conventional hypertext system which makes it particularly difficult to navigate the information in a progression that the original designers intended without sacrificing the ability of the user to freely navigate the information. Further, none of such prior art instructional databases allow an effective exchange of ideas in order to achieve a goal at hand.
0004Still yet another feature that the prior art instructional databases lack is the ability to track a progression of an effort to achieve an intended goal. Finally, the prior art instructional databases have never been used to facilitate a merger and acquisition situation.
Summary of Invention
0005A system, method, and article of manufacture are provided for facilitating the navigation of application specific data on a data page, i.e. web page, during use of a data browser, i.e. Netscape, MS Explorer, etc. Included on the data page are a plurality of links each corresponding to data. In use, the data may be retrieved upon selection of the corresponding link. To facilitate the navigation of the data, the links are displayed each as a component of an indicia such as a pointer or chevron to imply a relationship between the data.
0006In one embodiment of the present invention, the aforementioned relationship is a progressional relationship and the indicia implies a direction of progressional movement through the data. In order to imply direction, the indicia may take the form of a chevron or any other type of pointer that implies direction. As an option, each of the components of indicia may also be shaped as a chevron.
0007In yet another embodiment of the present invention, a currently selected link is visually differentiated with respect to the remaining links. This may be accomplished by highlighting a currently selected link. Further, the links may be continuously displayed with the data in order to continuously imply the progressional relationship and a current location among the data.
Description of Drawings
0008The foregoing and other objects, aspects and advantages are better understood from the following detailed description of a preferred embodiment of the invention with reference to the drawings, in which: <ul id="ul0001" list-style="none"><li><figref idref="f0001"><b>Figure 1</b></figref> is a schematic diagram of the present invention;</li><li><figref idref="f0002"><b>Figure 2</b></figref> is an illustration of a Navigation Chevron in accordance with one embodiment of the present invention;</li><li><figref idref="f0003"><b>Figure 3</b></figref> is an illustration of a knowledge database topic page in accordance with one embodiment of the present invention;</li><li><figref idref="f0004"><b>Figure 4</b></figref> is an illustration showing the use of nested Navigation Chevrons in accordance with one embodiment;</li><li><figref idref="f0005"><b>Figure 5</b></figref> is a block diagram of a Discussion Database in accordance with one embodiment of the present invention; and</li><li><figref idref="f0006"><b>Figure 6</b></figref> is an illustration of a Discussion Database Interface Page in accordance with one embodiment of the present invention.</li></ul>
Detailed Description
0009In accordance with at least one embodiment of the present invention, a single entry point is provided for merger/acquisition participants to access related information and deliverables utilizing Intranet technology. Entry may be accomplished using a hardware implementation such as is illustrated in <figref idref="f0001">Figure 1</figref>. Further, various functional and user interface features of the present invention may be enabled using software programming, i.e. object oriented programming (OOP).
Hardware Overview
0010A representative hardware environment of a preferred embodiment of the present invention is depicted in <figref idref="f0001">Figure 1</figref>, which illustrates a typical hardware configuration of a workstation having a central processing unit <b>110</b>, such as a microprocessor, and a number of other units interconnected via a system bus <b>112</b>. The workstation shown in <figref idref="f0001">Figure <b>1</b></figref> includes Random Access Memory (RAM) <b>114</b>, Read Only Memory (ROM) <b>116</b>, an I/O adapter <b>118</b> for connecting peripheral devices such as disk storage units <b>120</b> to the bus <b>112</b>, a user interface adapter <b>122</b> for connecting a keyboard <b>124</b>, a mouse <b>126</b>, a speaker <b>128</b>, a microphone <b>132</b>, and/or other user interface devices such as a touch screen (not shown) to the bus <b>112</b>, communication adapter <b>134</b> for connecting the workstation to a communication network (e.g., a data processing network) and a display adapter <b>136</b> for connecting the bus <b>112</b> to a display device <b>138</b>. The workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system.
Software Overview
0011Object oriented programming (OOP) has become increasingly used to develop complex applications. As OOP moves toward the mainstream of software design and development, various software solutions require adaptation to make use of the benefits of OOP. A need exists for the principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided.
0012OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.
0013In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each other's capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed.
0014OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition-relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects.
0015OOP also allows creation of an object that "depends from" another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine "depends from" the object representing the piston engine. The relationship between these objects is called inheritance.
0016When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with them (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a programmer would call the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects.
0017With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, the logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows: <ul id="ul0002" list-style="bullet" compact="compact"><li>Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system.</li><li>Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.</li><li>An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities.</li><li>An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.</li></ul>
0018With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future.
0019If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built objects.
0020This process closely resembles complex machinery being built out of assemblies and subassemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increase in the speed of its development.
0021Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems-programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal.
0022The benefits of object classes can be summarized, as follows: <ul id="ul0003" list-style="bullet" compact="compact"><li>Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems.</li><li>Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.</li><li>Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch.</li><li>Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways.</li><li>Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them.</li><li>Libraries of reusable classes are useful in many situations, but they also have some limitations. For example:</li></ul><ul id="ul0004" list-style="bullet" compact="compact"><li>Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes.</li><li>Flow of control. A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects.</li><li>Duplication of effort. Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way. Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should.</li></ul>
0023Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers.
0024Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others. In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.
0025The development of graphical user interfaces began to turn this procedural programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still "sits on top of" the system.
0026Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making all these things work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application.
0027Application frameworks reduce the total amount of code that a programmer has to write from scratch. However, because the framework is really a generic application that displays windows; supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure).
0028A programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems.
0029Thus, as is explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain: It typically includes objects that provide default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times.
0030There are three main differences between frameworks and class libraries: <ul id="ul0005" list-style="bullet" compact="compact"><li>Behavior versus protocol. Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides.</li><li>Call versus override. With a class library, the code the programmer instantiates objects and calls their member functions. It's possible'to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together.</li><li>Implementation versus design. With class libraries, programmers reuse only implementations, whereas with frameworks, they reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems.</li></ul>
0031Thus, through the development of frameworks for solutions to various problems and programming tasks, significant reductions in the design and development effort for software can be achieved. A preferred embodiment of the invention utilizes HyperText Markup Language (HTML) to implement documents on the Internet together with a general-purpose secure communication protocol for a transport medium between the client and a company. HTTP or other protocols could be readily substituted for HTML without undue experimentation. Information on these products is available in <nplcit id="ncit0001" npl-type="s"><text>T. Berners-Lee, D. Connoly, "RFC 1866: Hypertext Markup Language - 2.0" (Nov. 1995</text></nplcit>); and <nplcit id="ncit0002" npl-type="s"><text>R. Fielding, H, Frystyk, T. Berners-Lee, J. Gettys and J.C. Mogul, "Hypertext Transfer Protocol - HTTP/1.1: HTTP Working Group Internet Draft" (May 2, 1996</text></nplcit>). HTML is a simple data format used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML has been in use by the World-Wide Web global information initiative since 1990. HTML is an application of ISO Standard 8879; 1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML).
0032To date, Web development tools have been limited in their ability to create dynamic Web applications which span from client to server and interoperate with existing computing resources. Until recently, HTML has been the dominant technology used in development of Web-based solutions. However, HTML has proven to be inadequate in the following areas: <ul id="ul0006" list-style="bullet" compact="compact"><li>Poor performance;</li><li>Restricted user interface capabilities;</li><li>Can only produce static Web pages;</li><li>Lack of interoperability with existing applications and data; and</li><li>Inability to scale.</li></ul>
0033Sun Microsystem's Java language solves many of the client-side problems by: <ul id="ul0007" list-style="bullet" compact="compact"><li>Improving performance on the client side;</li><li>Enabling the creation of dynamic, real-time Web applications; and</li><li>Providing the ability to create a wide variety of user interface components.</li></ul>
0034With Java, developers can create robust User Interface (UI) components. Custom "widgets" (e.g., real-time stock tickers, animated icons, etc.) can be created, and client-side performance is improved. Unlike HTML, Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance. Dynamic, real-time Web pages can be created. Using the above-mentioned custom UI components, dynamic Web pages can also be created.
0035Sun's Java language has emerged as an industry-recognized language for "programming the Internet." Sun defines Java as "a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language. Java supports programming for the Internet in the form of platform-independent Java applets." Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add "interactive content" to Web documents (e.g., simple animations, page adornments, basic games, etc.). Applets execute within a Java-compatible browser (e.g., Netscape Navigator) by copying code from the server to client. From a language standpoint, Java's core feature set is based on C++. Sun's Java literature states that Java is basically, "C++ with extensions from Objective C for more dynamic method resolution."
0036Another technology that provides similar function to JAVA is provided by Microsoft and ActiveX Technologies, to give developers and Web designers wherewithal to build dynamic content for the Internet and personal computers. ActiveX includes tools for developing animation, 3-D virtual reality, video and other multimedia content. The tools use Internet standards, work on multiple platforms, and are being supported by over 100 companies. The group's building blocks are called ActiveX Controls, which are fast components that enable developers to embed parts of software in hypertext markup language (HTML) pages. ActiveX Controls work with a variety of programming languages including Microsoft Visual C++, Borland Delphi, Microsoft Visual Basic programming system and, in the future, Microsoft's development tool for Java, code named "Jakarta." ActiveX Technologies also includes ActiveX Server Framework, allowing developers to create server applications. One of ordinary skill in the art readily recognizes that ActiveX could be substituted for JAVA without undue experimentation to practice the invention.
Merger and Acquisition Engine System Overview
0037The Merger and Acquisition (M&A) Engine provides knowledge management and delivery capabilities to facilitate the learning and execution of merger-related work. In one embodiment, this is accomplished by storing the M&A Engine on a centralized server which may be accessed over a network, i.e. the Internet, via a web site using a hardware implementation set forth hereinabove and shown in <figref idref="f0001">Figure 1</figref>.
0038During operation, the M&A Engine facilitates user work, manages and delivers reusable knowledge, improves the ability to manage change resulting from mergers and acquisitions, and expedites the learning process for new merger resources. The M&A Engine streamlines communication between merger participants, and assists in the consolidation of projects. The M&A Engine can also be used as a marketing tool. In addition, the M&A Engine promotes standardization of processes that are applicable to individual areas such as status reporting, business case development, and budget and benefits monitoring.
0039Using the M&A Engine, productivity is improved during the transition by increased communication. Merger/acquisition participants are given a common entry point to effectively access information and deliverables, leverage existing knowledge, contribute knowledge, conduct informal conversations, document meeting outcomes and issues, etc.
0040The M&A Engine improves documentation and outcomes by providing users access to the entire history of an on-line discussion. This functionality improves the understanding of issues and/or topics, e.g. conversion schedule, DARTs, etc., as well as what decisions or progress has been made towards a resolution. The M&A Engine improves issue resolution during the transition by utilizing discussion databases to submit and/or answer issues, questions, topics, etc. This gives key stakeholders an improved understanding of the most current status of key deliverables.
0041The M&A Engine's streamlined communication throughout the transition yields benefits such as: <ul id="ul0008" list-style="bullet" compact="compact"><li>Improved creativity through more frequent communication with subject matter experts and on-line brainstorming sessions or idea sharing;</li><li>Reduced project completion cycles due to increased communication and collaboration of ideas, e.g. sharing of best practices, discussion databases, etc.;</li><li>Reduced costs due to fewer printed pages to distribute mass communications, e.g. administrative memos, phone directories, newsletters, etc., and key deliverables by providing information on-line; and</li><li>Reduced telephone, video conferencing, and travel costs, as users are able to conduct "virtual meetings" via the M&A Engine discussion databases.</li></ul>
0042The M&A Engine supports standardization of consolidation activities and deliverables. Users are consistently guided through the steps to complete merger/acquisition activities, and are provided samples and templates to facilitate the completion of deliverables associated with those activities. The M&A Engine also develops and retains institutional knowledge related to consolidation, thus reducing costs related to training and use of outside consultants.
0043The M&A Engine also supports the evolution of process-driven methods for the transition by utilizing the Intranet as its delivery vehicle. Through the M&A Engine, users are able to "drill-down" from a merger activity to specific task packages and deliverables. This capability improves the understanding throughout the organization of the complete range of activities that are involved with the consolidation of two or more organizations.
0044One embodiment of the M&A Engine includes a plurality of features for accomplishing the foregoing goals. For example, the present invention includes Navigation Chevron, a Discussion Database, a Discussion Database Interface Page, a 30/60/90 Plan, and a Merger Site Map. The Navigation Chevron is used to navigate the user through the M&A Engine environment. The Discussion Database is used to discuss concepts and serve as an audit trial of topics. The Discussion Database Interface Page describes the various discussion groups available to the user, and subscribes the user to individual discussion groups when selected. The 30/60/90 Plan is used to account for all actions taken during the first 90 days of consolidation. Finally, the Merger Site Map tracks activities and duration of these activities throughout the consolidation.
Navigation Chevron
0045The Navigation Chevron of the present invention is a form of hypertext that facilitates the navigation of data during use of the M&A Engine. Hypertext systems are a class of complex information management systems. These systems allow people to create, annotate, link together, and share information from a variety of media such as text, graphics, audio, video, animation, and programs. They also provide flexible access to information by incorporating the notions of navigation, annotation, and tailored presentation.
0046Hypertext is defined as an approach to information management in which data is stored in a network of nodes connected by links. Nodes can contain text, graphics, audio, video as well as source code or other forms of data. Hypertext with multimedia is called "hypermedia". The utility of hypermedia lies in its ability to produce large, complex, richly connected, and cross-referenced bodies of information.
0047Outside the academic world, due to the implementation of hypertext-like features in products such as MS Windows Help, information systems professionals are of the opinion that hypertext is just another user interface approach. However, hypertext is a hybrid that spans across traditional boundaries. It is a database method providing a novel way of directly accessing and managing data. It is also a representation scheme, a kind of semantic network, which mixes informal textual material with more formal and mechanized processes. It is an interface modality that features link icons or markers that can be arbitrarily embedded with the contents and can be used for navigational purposes. In short, a hypertext system is a database system which provides a totally different and unique method of accessing information. Whereas traditional databases have some structure around them, a hypertext database has no regular structure. The user is free to explore and assimilate information in different ways.
0048A hypertext system is made of nodes, or concepts, and links, or relationships. A node usually represents a single concept or idea. It can contain text, graphics, animation, audio, video, images or programs. It can be typed and can include detail, proposition, collection, summary; observation, and issue, thereby carrying semantic information. Nodes are connected to other nodes by links. The node from which a link originates is called the reference and the node at which a link ends is called the referent. They are also referred to as anchors. The contents of a node are displayed by activating links.
0049Links connect related concepts or nodes. They can be bidirectional thus facilitating backward traversals. Links can also be typed, i.e. specification link, elaboration link, membership link, opposition link and others, specifying the nature of relationship. Links can be either referential for cross-referencing purposes or hierarchical for showing parent-child relationships. Activation of a link marker displays a node.
0050Hypertext parallels human cognition and facilitates exploration. People think in nonlinear chunks which they try to associate with each other, thus building a network of concepts. When a person reads a book, they go back and forth a number of times to refer to previously read material, to make notes, and to jump to topics using the table of contents or the index. When they set out to write a document, they first develop an outline of ideas. Then, a person brainstorms, writes down on paper, organizes, revises, reorganizes and repeats the cycle until they are satisfied with the outcome-a coherent document. In fact, people have been forced to adapt to traditional, linear text because of representation on paper.
0051In order to understand hypertext, it is very essential to understand how people read and write documents. Reading and writing models have been developed by cognitive psychologists that can be used to understand non-linear thinking by human beings.
0052The theory of semiotics or the study of symbols shows that the understanding of knowledge ' takes place at four levels: lexical, syntactic, semantic and pragmatic. At the lexical level, the user determines the definition for each word encountered. At the syntactic level, the subject, action and object of a sentence are determined. The meaning of a sentence is determined at the semantic level. The pragmatic interpretation of text depends on the integration of semantic meaning of text with the reader's knowledge of self and of the world.
0053While reading text, people proceed from a lexical level to the syntactic level, to the semantic and to the pragmatic levels in that order. All these levels interact continuously and they cannot be truly separated. The reader might have to have knowledge of the world in order to understand the meaning of a word. The correct syntactic and semantic interpretation of text may depend on the reader's knowledge of the world. Hence, though readers may proceed from words to sentences, to paragraphs and to the overall document, the progress is more forward and backward.
0054A mental representation of the meaning of text is then constructed which is in the form of propositions or relationships. While reading text, readers establish local coherence in short-term memory-small scale inferences from few small units of information, i.e. relationships between words, sentences and so on. The reader makes preliminary hypotheses based on titles, words, propositions, and knowledge about the real world. A reading control system retrieves knowledge from the real world, present in long-term memory, in order to filter out information present in short-term memory. These hypotheses are refined as the reading of the text proceeds, with the reading control system being invoked continuously. These propositions are combined into larger structures, also called global. This hypothesized macroproposition or superstructure is used to understand the overall content of the text. The construction of a coherent mental representation has important consequences for navigation. In addition to generating forward references, we accumulate cues for backward navigation.
0055The reading control system uses the spreading activation model to access propositions or concepts. In semantic memory, each concept is connected to a number of other concepts. Activating one concept activates its adjacent concepts which in turn activate their adjacent concepts. Thus, activation spreads through the memory structure, determining what is to be added and what is to be removed from the interpretation of text. This process continues until further activation of adjacent propositions does not change the propositions used to interpret the text. That is, spreading activation decreases over time and semantic distance.
0056Writing is constrained by goal and audience. The author is guided by a goal but constrained by what the audience is prepared to accept. Different people approach writing in different ways. Some are good at making an outline first and then brainstorming. Some do the opposite. An expert author would always keep the reading model in mind so that the writing clearly reaches the target audience.
0057Writing involves the following three phases: exploring, organizing, and encoding. In the Cognitive Framework for Written Communication, Smith et al. call these three phases prewriting, organizing, and writing.
0058Exploring or pre-writing is the process of brainstorming and taking unstructured notes. The writer retrieves potential content from long-term memory or external sources, considers possible relations among ideas, groups related ideas and constructs small hierarchical structures. Thus, the product of exploration is a network or directed graph of ideas.
0059Organizing is the process of putting these notes or ideas in order, in the form of an outline or a hierarchy. This process involves abstract construction that involves perceiving subordinate/superordinate relations, comparing abstractions, sequencing, proportion, and balance. Thus, the product of organization is a hierarchy of related concepts.
0060Encoding or writing is the final phase of completing the document. The primary task is translating the abstractions of content and the relations of a hierarchical structure into a sequence of words, sentences, paragraphs, sections, chapters, and illustrations. The structure of the encoded text is linear and represents a path through the hierarchy. Reading employs processes in the reverse order. That is, a linear sequence of words is transformed into a hierarchy which is later integrated into a network in long-term memory.
0061The writing model can be extended by considering unstructured and structured representation at each phase. Whereas an unstructured item is isolated, a structured item shows coherence. Exploring can be split into unstructured brainstorming followed by structured note-taking.
0062Organizing can be classified as unstructured argumentation where relationships are established between ideas and structured organization of notes where notes are grouped together to make coherent sense. Encoding has an unstructured phase of linear planning which involves viewing groups of notes as sequences and a structured phase of drafting and revising in order to produce a final document which is a linear sequence of notes.
0063Just as the reader of a linear document constructs a local and global mental representation of the document, the author of a linear document uses cues both at the local and at the global levels, dividing the document into chapters, sections, paragraphs, sentences, words etc. This facilitates comprehension and navigation.
0064Thus, both reading and writing processes emphasize a lot on the non-linear nature of thinking, a natural process in human beings. Human cognition is essentially organized as a semantic network in which concepts are linked together by associations. Hypertext systems try to exploit this basic nature of cognition.
0065One aspect of the present invention utilizes a unique hypertext feature, a Navigation Chevron <b>200</b>, to navigate the user through the data in the M&A engine environment. <figref idref="f0002">Figure <b>2</b></figref> is an illustration of the Navigation Chevron <b>200</b>. The Navigation Chevron <b>200</b> is generally shaped as an indicia similar to a pointer, and may be arranged in any orientation, such as horizontally, diagonally, or vertically.
0066The Navigation Chevron <b>200</b> is made up of components, or discrete phase chevrons <b>202</b>, which are generally shaped similar to the Navigation Chevron <b>200</b>. Displayed on each discrete phase chevron <b>202</b> is an indication of the topic relating to that particular discrete phase chevron <b>202</b>. The indication may be a color, or some other identifying mark. A preferred indication is the title or general description of the topic area related to the particular discrete phase chevron <b>202</b>. The description allows the user to easily determine which discrete phase chevron <b>202</b> relates to the particular topic needed to complete a particular task.
0067The Navigation Chevron <b>200</b> is used to navigate a database of knowledge utilizing a progression of ideas or phases. Each idea or phase of the knowledge database is represented by a discrete phase chevron <b>202</b> in the Navigation Chevron <b>200</b>. The discrete phase chevrons <b>202</b> are organized in a logical progression of the topics covered by the Navigation Chevron's <b>200</b> related knowledge database.
0068The topic pages in the related knowledge database generally include a Navigation Chevron <b>200</b> as part of their display. The Navigation Chevron <b>200</b> may be located anywhere on the display, preferably away from the data provided by the knowledge database, such as at the top or to the side of the display. In addition, the Navigation Chevron 200 may be of any size. A preferred embodiment uses an initially large Navigation Chevron <b>200</b>. However, with each subsequent progression, the Navigation Chevron <b>200</b> becomes smaller in size. Note <figref idref="f0004">Figure <b>4</b></figref><b>.</b>
0069<figref idref="f0003">Figure <b>3</b></figref> is an illustration of a knowledge database topic page <b>300</b>. The knowledge database topic page <b>300</b> includes a Navigation Chevron <b>200</b> having discrete phase chevrons <b>202.</b> The discrete phase chevron <b>202</b> that is related to the current knowledge database topic page <b>300</b> is highlighted.
0070As the user decides on an area of knowledge to explore, the user picks a discrete phase chevron <b>202</b> utilizing a computer input device, such as the mouse <b>126</b>. Once a discrete phase chevron 202 is chosen, the related knowledge database topic page <b>300</b> is displayed along with a Navigation Chevron <b>200</b> including a highlighted discrete phase chevron <b>202</b> related to the current knowledge database topic page <b>300</b>. The Navigation Chevron <b>200</b> thus allows the user to navigate an extensive knowledge database in an easy and intuitive manner.
0071The user is able to explore the knowledge database in the order presented on the Navigation Chevron <b>200</b>, or in an order more pertinent to the task at hand. By selecting the topic to explore in the Navigation Chevron <b>200</b> the user can go directly to the topic needed for a particular task. In addition, the Navigation Chevron <b>200</b> allows the user to visualize the knowledge database as a whole, and determine how the current knowledge database topic page <b>300</b> relates to other topics in the knowledge database. As such, the Navigation Chevron <b>200</b> indicates a relationship, i.e. progression or sequence, that is inherently not present in conventional hypertext systems.
0072Navigation Chevrons <b>200</b> may be nested, allowing a more detailed navigation through a knowledge database. <figref idref="f0004">Figure 4</figref> is an illustration showing the use of nested Navigation Chevrons <b>200, 402</b>, and <b>406</b>. In this embodiment, a large Navigation Chevron <b>200</b> is used to allow access to broad topic areas covered by discrete phase chevrons <b>202</b>. Each topic covered by a discrete phase chevron <b>202</b> has a further Navigation Chevron <b>402</b> related to the particular broad topic covered by the discrete phase chevron <b>202.</b> The Navigation Chevron <b>402</b> includes further discrete phase chevrons <b>404</b> which relate to more detailed information associated with the broad topic of the discrete phase chevron <b>202.</b> The nesting of Navigation Chevrons <b>200</b> may continue, including further nested Navigation Chevrons <b>406</b>, as much as needed to allow easier navigation of a large knowledge databases. As discussed above, the nested Navigation Chevrons <b>200</b> allow the user to visualize the knowledge database as a whole, and determine how a knowledge database topic page <b>300</b> relates to the knowledge database as a whole.
0073It should be noted that Navigation Chevrons <b>200</b> may be employed to navigate data within any type of database including, but not limited to the M&A Engine. Below is an html code segment for displaying and using a Navigation Chevron <b>200</b>: <pre listing-type="program-listing"> <tr align="left" valign="top"> <td><b><img ismap usemap="#ChevronMap4" border="0" height="54" src="'images/MainChevron.gif" width="456"></b></td> </tr> <map name="ChevronMap4"> <area shape="poly" coords="347,0,435,1,454,25,435,53,347,53,365,28,345,0" href="Post- integration.htm"> <area shape="poly" coords="258,0,343,0,361,27,345,53,256,52,271,23,259,0" href="Consolid.htm"> <area shape="poly" coords="171,0,255,0,271,25,253,52,173,52,188,26,173,2" href="AssessAndStabiliz.htm"> <area shape="poly" coords="91,0,168,0,186,26,173,49,89,52,105,27,89,2" href="Organize.htm"> <area shape="poly" coords="1,0,88,0,101,23,88,51,5,51,17,27,3,0" href="MergerEng_Main.htm"> </map> <map name="MapFeed"> <area shape="rect" coords="2,0,173,120" href="feedback.htm"> </map></pre>
Discussion Database
0074Bulletin board systems, or BBS's, refer to computer systems equipped with one or more modems or other means of network access that serves as an information and message-passing center for remote users. Often BBS's are focused on special interests, such as science fiction, movies, Windows software, or Macintosh systems, and can have free or fee-based access, or a combination. Users dial into a BBS with their modems and post messages to other BBS users in special areas devoted to a particular topic, in a manner reminiscent to posting notes on a cork bulletin board. Many BBS's also allow users to chat online with other users, send e-mail, download and upload files that include freeware and shareware software, and access the Internet. Many software and hardware companies run proprietary BBS's for customers that includes sales information, technical support, and software upgrades and patches.
0075In other words, a BBS acts as a storage facility, where people calling from their computers can post or receive messages and send or receive program files. A BBS is usually subdivided by topics so that users with similar interests can send information to other users of similar interests. These related groups of messages are referred to as topics, message areas, forum(s), or conferences, i.e. a particular BBS may contain numerous related groups of messages such as on the subjects of travel, sports, stamp collecting, etc.
0076BBS's are distinguishable from electronic mail in that BBS's are used for posting messages of a particular group of computer users who have similar interests, but these posted messages are not ordinarily addressed to any particular user. BBS's are also used by some computer users who wish just to read posted messages and other information, without having to post a reply message. For example, a person in Columbus, Ohio, who is preparing for a vacation, may access a BBS on travel through his home computer and post a message asking for the best places to go skiing in the United States. Other network users with an interest in travel may read the message from the person from Columbus, and then reply with their opinion about where the best place is for skiing. There are thousands of BBS's available to computer network users on a wide variety of subject areas.
0077Another component of the M&A Engine of the present invention is the Discussion Database. The Discussion Database, in some limited respects, is similar to a BBS in that it is a repository of knowledge on various topics compiled from the input of various users of the Discussion Database. <figref idref="f0005">Figure <b>5</b></figref> is a block diagram of a Discussion Database <b>500</b> in accordance with one embodiment of the present invention.
0078A Discussion Database <b>500</b> includes a broad topic field <b>502</b> having Discussion Groups <b>504</b> relating to specific subject areas of the broad topic <b>502</b>. The Discussion Groups <b>504</b> include User Posts <b>506</b> which are documents contributed by users of the Discussion Database <b>500</b>. Preferably, the User Posts <b>506</b> are contributed by users of the particular broad topic field <b>502</b>, and most preferably, the User Posts <b>506</b> are contributed by users of the particular discussion group in which the User Post <b>506</b> is located. Generally, many broad topic fields <b>502</b> are used to create the Discussion Database <b>500</b> to increase ease of navigation. Typically, the more broad topic fields 502 that are used to create the Discussion Database <b>500</b>, the easier it is for a user to find the particular Discussion Group <b>502</b> related to the information they need. However, a broad topic field <b>502</b> may itself be a Discussion Group <b>504</b>, and thus contain User Posts <b>506</b>.
0079Utilizing the broad topic fields <b>502</b>, users locate an area of knowledge they need. As discussed above, within each broad topic field <b>502</b> are related Discussion Groups <b>504</b>. The Discussion Groups <b>504</b> are further refinements of the broad topic field <b>502</b> to which they relate. Users search through a list of Discussion Groups <b>504</b> within the broad topic field <b>502</b> to determine which Discussion Group <b>504</b> most closely relates to the information they need. Once a Discussion Group <b>504</b> is found relating to the information needed, the user searches through a list of User Posts <b>506</b> located in the chosen Discussion Group <b>504</b>.
0080In addition to obtaining information from the User Posts <b>506</b> previously located in the Discussion Group <b>504</b>, users may contribute their own documents to the Discussion Group <b>504</b>, thereby increasing the knowledge base available in the Discussion Database <b>500</b>. To contribute documents, users select the document they want to contribute and inform the system utilizing the Discussion Database Interface Page, discussed below. The system then adds the document to the list of available documents contained in the Discussion Group <b>504</b> and makes the corresponding document available to other users of the Discussion Database <b>500.</b>
0081The Discussion Database <b>500</b> is a dynamic continuously growing entity. The more the Discussion Database <b>500</b> is used, the more it grows. The Discussion Database <b>500</b> as a whole increases as users continue to contribute documents relating to the various Discussion Groups <b>504</b>. For example, in <figref idref="f0005">Figure 5</figref>, Joe decides he needs information about transition management projects on mergers of Nuclear Reactor companies. Joe first searches a list of broad topic fields <b>502</b> and determines that the Transition Management topic is the best topic to search in more detail. He then searches through a list of Discussion Groups <b>504</b> associated with the Transition Management topic field <b>502</b>, and determines that TMGT Special Projects Discussion Group <b>504</b> is the most closely related to the information he needs. Joe then reads through the User Post <b>506</b> contained in the TMGT Special Projects Discussion Group <b>504</b> and finds the information he needs. Joe then decides to contribute a document he wrote concerning other TMGT Special Projects, and proceeds to post it to the system. In the end, a user acquired the knowledge he needed, and as a result, the Discussion Database <b>500</b> increased its available knowledge base. Thus, it can be seen that the use of a continuously growing knowledge database dramatically increases productivity and organizational knowledge without having to continuously rely on outside sources.
Discussion Database Interface Page
0082The Discussion Database Interface Page describes the various Discussion Groups which are available to the user of the M&A Engine of the present invention. The Discussion Database Interface Page also subscribes the user to the individual Discussion Groups <b>504</b> used most often by the user.
0083<figref idref="f0006">Figure 6</figref> is an illustration of a Discussion Database Interface Page <b>600.</b> The Discussion Database Interface Page <b>600</b> includes a Discussion Group List <b>602</b> having a list of broad topic fields <b>502</b> and Discussion Groups <b>504</b>. As discussed above, a broad topic field <b>502</b> may itself be a Discussion Group <b>504</b>.
0084Each Discussion Group <b>504</b> has a Description <b>604</b> associated with it. Each Description <b>604</b> includes a string of descriptive data, or summary, of what type of information is contained in the related Discussion Group <b>504</b>. The Description <b>604</b> is preferably kept short to decrease the overall size of the Discussion Group List <b>602</b>. However, the Description <b>604</b> may be as long as needed to adequately inform users as to the contents of a particular Discussion Group 504.
0085By describing the categories of information within the Discussion Groups <b>504</b>, a user may effectively select the categories on the Discussion Database Interface Page <b>600</b> which are most relevant. As an option, the aforementioned string of descriptive data may constitute a link to the data. Also, a user may subscribe and access the categories of data by executing only one user action, namely clicking on the appropriate Discussion Groups <b>504</b> on the Discussion Database Interface Page <b>600</b>.
0086As such, the Discussion Database Interface Page <b>600</b> is utilized by the user to subscribe to and access individual Discussion Groups <b>504</b>. When a user wishes to join a Discussion Group <b>504,</b> the user selects the appropriate Discussion Group <b>504</b> from the Discussion Group List <b>602</b>. The corresponding Discussion Group <b>504</b> is then added to the Discussion Groups <b>504</b> the user can utilize. By subscribing only to Discussion Groups <b>504</b> pertinent to the particular user's interest and needs, the user can more quickly obtain needed information. Since the number of Discussion Groups <b>504</b> subscribed to by a particular user is generally much less than the total number of Discussion Groups <b>504</b> available, the user does not need to search through a large list of Discussion Groups <b>504</b> every time he or she needs information. Instead, the user selects only those Discussion Groups <b>504</b> that he or she will need most often. Thereafter, when the user desires information, he or she will generally only need to search through the Discussion Groups <b>504</b> the user has subscribed to. Thus, the search time is drastically reduced after the first use of the system.
0087The use of the Discussion Database <b>500</b> in combination with the Discussion Database Interface Page <b>600</b> creates a wealth of information useful for the entire organization utilizing the system. The Discussion Database <b>500</b> contains not only information provided by the organization that sets up the Discussion Database <b>500</b>, but also information provided by users of the system. The Discussion Database coupled with the Discussion Database Interface Page <b>600</b> creates a "living library" which grows with each use, and grows with the knowledge of its users. As users acquire more knowledge from experience and other outside sources, they transfer that knowledge to the Discussion Database 500 utilizing the Discussion Database Interface Page <b>600</b>. The transfer of knowledge to the Discussion Database <b>500</b> increases the knowledge contained in the Discussion Database 500, and helps keep the information contained in the Discussion Database <b>500</b> updated as new developments arise in various fields.
0088It should be noted that the Discussion Database Interface Page <b>600</b> may be employed to provide effective access to any type of database including, but not limited to, the database associated with the M&A Engine. Below is a code segment for creating a Discussion Database Interface Page <b>600</b>: <img file="EP1986112A1_D0001.tif" /><img file="EP1986112A1_D0002.tif" /><img file="EP1986112A1_D0003.tif" /><img file="EP1986112A1_D0004.tif" /><img file="EP1986112A1_D0005.tif" /><img file="EP1986112A1_D0006.tif" /><img file="EP1986112A1_D0007.tif" /><img file="EP1986112A1_D0008.tif" /><img file="EP1986112A1_D0009.tif" /><img file="EP1986112A1_D0010.tif" /><img file="EP1986112A1_D0011.tif" />
0089Although only a few embodiments of the present invention have been described in detail herein, it should be understood that the present invention may be embodied in many other specific forms without departing from the spirit or scope of the invention. Therefore, the present examples and embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope of the appended claims,
0090This application is a divisional application of European patent application no. <patcit id="pcit0001" dnum="EP08153773A"><text>08 153 773.0</text></patcit> (the "parent application"), also published under no. <patcit id="pcit0002" dnum="EP1939769A"><text>EP 1 939 769</text></patcit>, which in turn is a divisional application of European patent application no.: <patcit id="pcit0003" dnum="EP00986233A"><text>00 986 233.5</text></patcit>, also published under no. <patcit id="pcit0004" dnum="EP1275060A"><text>EP 1 275 060</text></patcit>. The original claims of this application, also repeated in the parent application, are repeated below in the present specification and form part of the content of this divisional application as filed. <ol id="ol0001" ol-style=""><li>1. A method for facilitating the navigation of data comprising the steps of: <ol id="ol0002" compact="compact" ol-style=""><li>(a) providing a plurality of links each corresponding to data;</li><li>(b) retrieving the data upon selection of the corresponding link; and</li><li>(c) displaying the links each as a component of an indicia to imply a relationship between the data.</li></ol></li><li>2. The method as set forth in claim 1, wherein the relationship is a progressional relationship.</li><li>3. The method as set forth in claim 1, wherein the relationship is a sequential relationship.</li><li>4. The method as set forth in claim 1, wherein the indicia implies a direction.</li><li>5. The method as set forth in claim 4, wherein the indicia is a pointer.</li><li>6. The method as set forth in claim 5, wherein the indicia is a chevron.</li><li>7. The method as set forth in claim 1, wherein a currently selected link is visually differentiated with respect to the remaining links.</li><li>8. The method as set forth in claim 1, wherein each component has a shape substantially similar to that of the indicia.</li><li>9. The method as set forth in claim 1, wherein the links are continuously displayed with the data to continuously imply the relationship.</li><li>10. A system for facilitating the navigation of data comprising: <ol id="ol0003" compact="compact" ol-style=""><li>(a) memory for storing a plurality of data pages;</li><li>(b) a display for depicting a plurality of links each corresponding to one of the data pages, the links each displayed as a component of an indicia to imply a relationship between the data pages; and</li><li>(c) an input.device for retrieving the data pages upon selection of the corresponding link.</li></ol></li><li>11. The system as set forth in claim 10, wherein the relationship is a progressional relationship.</li><li>12. The system as set forth in claim 10, wherein the relationship is a sequential relationship.</li><li>13. The system as set forth in claim 10, wherein the indicia implies a direction.</li><li>14. The system as set forth in claim 13, wherein the indicia is a pointer.</li><li>15. The system as set forth in claim 14, wherein the indicia is a chevron.</li><li>16. The system as set forth in claim 10, wherein a currently selected link is visually differentiated with respect to the remaining links.</li><li>17. The system as set forth in claim 10, wherein each component has a shape substantially similar to that of the indicia.</li><li>18. The system as set forth in claim 10, wherein the links are continuously displayed with the data pages to continuously imply the relationship.</li><li>19. A computer program embodied on a computer-readable medium for facilitating the navigation of data comprising: <ol id="ol0004" compact="compact" ol-style=""><li>(a) a code segment that provides a plurality of links each corresponding to data;</li><li>(b) a code segment that retrieves the data upon selection of the corresponding link; and</li><li>(c) a code segment that displays the links each as a component of an indicia to imply a relationship between the data.</li></ol></li><li>20. The computer program as set forth in claim 19, wherein the relationship is a progressional relationship.</li><li>21. A method for providing effective access to data comprising the steps of: <ol id="ol0005" compact="compact" ol-style=""><li>(a) receiving data from multiple users in a plurality of categories;</li><li>(b) providing access to the data via an interface that lists the categories;</li><li>(c) subscribing to the categories of data upon the selection thereof; and</li><li>(d) describing the categories on the interface.</li></ol></li><li>22. The method as set forth in claim 21, wherein the data includes information related to merger and acquisition.</li><li>23. The method as set forth in claim 21, wherein the categories are listed in a hierarchy.</li><li>24. The method as set forth in claim 23, wherein the categories include a plurality of broad topics and a plurality of specific topics wherein each specific topic is encompassed by at least one of the broad topics.</li><li>25. The method as set forth in claim 21, wherein the categories are described by an accompanying string of descriptive data.</li><li>26. The method as set forth in claim 21, wherein the categories are described by a string of descriptive data that constitutes a link to the data.</li><li>27. The method as set forth in claim 21, further comprising the step of subscribing to and accessing the categories of data in response to a single user action.</li><li>28. A system for providing effective access to data comprising: <ol id="ol0006" compact="compact" ol-style=""><li>(a) memory for storing data from multiple users in a plurality of categories;</li><li>(b) a display for depicting an interface with a list of the categories thereon, the categories being described on the interface; and</li><li>(c) a user input device for subscribing to the categories of data upon the selection thereof.</li></ol></li><li>29. The system as set forth in claim 28, wherein the data includes information related to merger and acquisition.</li><li>30. The system as set forth in claim 28, wherein the categories are listed in a hierarchy.</li><li>31. The system as set forth in claim 30, wherein the categories include a plurality of broad topics and a plurality of specific topics wherein each specific topic is encompassed by at least one of the broad topics.</li><li>32. The system as set forth in claim 28, wherein the categories are described by an accompanying string of descriptive data.</li><li>33. The system as set forth in claim 28, wherein the categories are described by a string of descriptive data that constitutes a link to the data.</li><li>34. The system as set forth in claim 28, wherein the system is adapted for subscribing to and accessing the categories of data in response to a single user action.</li><li>35. A computer program embodied on a computer-readable medium for providing effective access to data comprising: <ol id="ol0007" compact="compact" ol-style=""><li>(a) a code segment that receives data from multiple users in a plurality of categories;</li><li>(b) a code segment that provides access to the data via an interface that lists the categories;</li><li>(c) a code segment that subscribes to the categories of data upon the selection thereof; and</li><li>(d) a code segment that displays a description of the categories on the interface.</li></ol></li><li>36. The computer program as set forth in claim 35, wherein the data includes information related to merger and acquisition.</li><li>37. The computer program as set forth in claim 35, wherein the categories are listed in a hierarchy.</li><li>38. The computer program as set forth in claim 37, wherein the categories include a plurality of broad topics and a plurality of specific topics wherein each specific topic is encompassed by at least one of the broad topics.</li><li>39. The computer program as set forth in claim 35, wherein the categories are described by an accompanying string of descriptive data.</li><li>40. The computer program as set forth in claim 35, wherein the categories are described by a string of descriptive data that constitutes a link to the data.</li><li>41. A method for effectively collecting and disseminating information comprising the steps of: <ol id="ol0008" compact="compact" ol-style=""><li>(a) receiving data from multiple users in a plurality of categories;</li><li>(b) providing access to the data via an interface that lists the categories; and</li><li>(c) subscribing and accessing the categories of data in response to one user action.</li></ol></li><li>42. The method as set forth in claim 41, wherein the data includes information related to merger and acquisition.</li><li>43. The method as set forth in claim 41, wherein the categories are listed in hierarchy.</li><li>44. The method as set forth in claim 43, wherein the categories include a plurality of broad topics and a plurality of specific topics each encompassed by at least one of the broad topics.</li><li>45. The method as set forth in claim 41, further comprising the step of describing the categories on the interface.</li><li>46. The method as set forth in claim 45, wherein the categories are described by an accompanying string of descriptive data.</li><li>47. The method as set forth in claim 45, wherein the categories are described by a string of descriptive data that constitutes a link to the data.</li><li>48. A system for effectively collecting and disseminating information comprising: <ol id="ol0009" compact="compact" ol-style=""><li>(a) memory for storing data from multiple users in a plurality of categories;</li><li>(b) a display for depicting an interface with a list of categories of data thereon; and</li><li>(c) a user input device for subscribing to the categories and accessing the categories in response to one user action.</li></ol></li><li>49. The system as set forth in claim 48, wherein the data includes information related to merger and acquisition.</li><li>50. The system as set forth in claim 48, wherein the categories are listed in hierarchy.</li><li>51. The system as set forth in claim 50, wherein the categories include a plurality of broad topics and a plurality of specific topics each encompassed by at least one of the broad topics.</li><li>52. The system as set forth in claim 48, further comprising a description of the categories on the interface.</li><li>53. The system as set forth in claim 52, wherein the categories are described by an accompanying string of descriptive data.</li><li>54. The system as set forth in claim 52, wherein the categories are described by a string of descriptive data that constitutes a link to the data.</li><li>55. A computer program embodied on a computer-readable medium for effectively collecting and disseminating information comprising: <ol id="ol0010" compact="compact" ol-style=""><li>(a) a code segment that receives data from multiple users in a plurality of categories;</li><li>(b) a code segment that provides access to the data via an interface that lists the categories; and</li><li>(c) a code segment that subscribes and accesses the categories of data in response to one user action.</li></ol></li><li>56. The computer program as set forth in claim 55, wherein the data includes information related to merger and acquisition.</li><li>57. The computer program as set forth in claim 55, wherein the categories are listed in hierarchy.</li><li>58. The computer program as set forth in claim 57, wherein the categories include a plurality of broad topics and a plurality of specific topics each encompassed by at least one of the broad topics.</li><li>59. The computer program as set forth in claim 55, further comprising a description of the categories on the interface.</li><li>60. The computer program as set forth in claim 59, wherein the categories are described by - an accompanying string of descriptive data.</li></ol>
18 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP0986233A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1275060A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1939769A2 | Cites | European Patent Office (EPO) | Applicant |
| The technical aspects identified in the present application (Art. 92 EPC) are considered part of common general knowledge. Due to their notoriety no documentary evidence is found to be required. For further details see the accompanying Opinion and the reference below. | Non-patent | – | Search report |
| T. BERNERS-LEE; D. CONNOLY, RFC 1866: HYPERTEXT MARKUP LANGUAGE - 2.0, November 1995 (1995-11-01) | Non-patent | – | Applicant |
| R. FIELDING ET AL., HYPERTEXT TRANSFER PROTOCOL -- HTTP/1.1: HTTP WORKING GROUP INTEMET DRAFT, 2 May 1996 (1996-05-02) | Non-patent | – | Applicant |
12 members in 4 offices
Priority claims18
| Document | Office | Kind | Date |
|---|---|---|---|
| 44794199 | United States of America | A | |
| 44862499 | United States of America | A | |
| 44942199 | United States of America | A | |
| 447941 | United States of America | – | |
| 448624 | United States of America | – | |
| 449421 | United States of America | – | |
| 08153773 | European Patent Office (EPO) | A | |
| 00986233 | European Patent Office (EPO) | A | |
| EP20080153773 | – | – | – |
| EP20000986233 | – | – | – |
| US19990447941 | – | – | – |
| US19990448624 | – | – | – |
| US19990449421 | – | – | – |
| 08153773 | – | – | – |
| 00986233 | – | – | – |
| 447941 | – | – | – |
| 448624 | – | – | – |
| 449421 | – | – | – |
Members12
| Document | Office | Kind | |
|---|---|---|---|
| WO0139047A2 | World Intellectual Property Organization (WIPO) | A2 | |
| AU2251101A | Australia | A | |
| WO0139047A9 | World Intellectual Property Organization (WIPO) | A9 | |
| EP1275060A2 | European Patent Office (EPO) | A2 | |
| US6571235B1 | United States of America | B1 | |
| US6671692B1 | United States of America | B1 | |
| US6671693B1 | United States of America | B1 | |
| WO0139047A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP1939769A2 | European Patent Office (EPO) | A2 | |
| EP1939769A3 | European Patent Office (EPO) | A3 | |
| EP1986111A1 | European Patent Office (EPO) | A1 | |
| EP1986112A1This record | European Patent Office (EPO) | A1 |
8 legal events, as 2 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Designated country de not longer valid8566 | 8566 | DE | |
| Application deemed to be withdrawnWithdrawn18D | 18D | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWNSTAA | STAA | EP | |
| Designation fees paidAKX | AKX | EP | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1986112
- Publication, DOCDB
- 1986112
- Publication, EPODOC
- EP1986112
- Application
- 8162533
- Application, DOCDB
- 08162533
- Application, EPODOC
- EP20080162533
Titles3
- German
- Bereitstellungverfahren einer Datenzusammenfassung
- English
- Method for providing a summary of data
- French
- Procédé de mobilisation d'un resumé de données
Classification
- CPC, 2
- G06F17/30873
- G06F16/954
- IPC, 1
- G06F17 30
Designated states20
- Contracting states, 20
- Austria
- Belgium
- Switzerland
- Cyprus
- Germany
- Denmark
- Spain
- Finland
- France
- United Kingdom
- Greece
- Ireland
- Italy
- Liechtenstein
- Luxembourg
- Monaco
- Netherlands (Kingdom of the)
- Portugal
- Sweden
- Türkiye