US20100023500A1 - System and method for collecting, storing, managing and providing categorized information related to a document object - Google Patents
System and method for collecting, storing, managing and providing categorized information related to a document object Download PDFInfo
- Publication number
- US20100023500A1 US20100023500A1 US11/979,260 US97926007A US2010023500A1 US 20100023500 A1 US20100023500 A1 US 20100023500A1 US 97926007 A US97926007 A US 97926007A US 2010023500 A1 US2010023500 A1 US 2010023500A1
- Authority
- US
- United States
- Prior art keywords
- link
- document object
- attribute
- user
- relationship
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9558—Details of hyperlinks; Management of linked annotations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
Definitions
- the technical field is relating documents on computer networks and storing, indexing and presenting those relationships to network users.
- Computers are exceptional devices for storing, sorting and relating large amounts of information.
- Information is stored on computers and networked computing and storage devices as documents or objects, together referred to as document objects.
- document objects may contain any form of information, from text documents and articles, financial data, statistical information, electronic mail, images and photos, music, animation, and even motion pictures.
- the Internet as a network of interconnected networks, offers users access to an even broader collection of information—the Worldwide Web (the “Web”).
- Web Worldwide Web
- publishers offer information for educational, recreational, and commercial purposes.
- the Internet, and it's predominant Web form, is organized and accessed by assigning document objects an address, or Uniform Resource Locater (“URL”).
- URLs define the transfer protocol for and location of each individual document object on the Internet, or other network, including the Internetworking Protocol (“IP”) address of the host computer system of the document object.
- IP Internetworking Protocol
- Linkspace incorporate and provide many improvements on existing methods for publishing, distributing, relating and searching document objects on computer networks, including the Internet.
- Linkspace operates to provide many beneficial improvements in searching, identifying and publishing information over computer networks.
- Linkspace permits a user of a computer network or the Internet to establish relationships between document objects located on the network or the Internet. Those relationships may comprise link relationships and link references and are maintained by Linkspace in one or more link directories. The contents of link directories may be organized, categorized, sorted and filtered in groupings based on various criteria relating to, among other things, user interests and attributes, the types of document objects and the nature of the content of those document objects. Linkspace allows a network user to be presented with a selection of links to document objects related to the document object the user is currently accessing based upon the URL of the current document object, and link relationships created by the user and other users of the network stored in the link directories.
- a network user equipped with Linkspace When a network user equipped with Linkspace identifies and locates a first document object on the network that is of interest to her, she may initiate one method of the present invention to mark the location, through its URL, as a start point of a link relationship.
- she accesses a second document object on the network that she considers relevant to the first document object she initiates another step of one method of the invention to mark the second document object as an end point of the link relationship.
- the link relationship Upon marking the second document object as the end point, the link relationship is created and stored on a link directory selected to store similar link relationships.
- Linkspace consists primarily of a system and method for creating and publishing link relationships, a system and method for storing and managing link relationships in link directories, and a system and method for presenting a network user with links related by link relationships to the document object the user is currently accessing.
- a method for enabling users of a network to create, store, and provide access to relationships between document objects stored on the network may include the steps for allowing a user of the network to create a link relationship between a first document object and a second document object; for storing the link relationship in one or more link directories; and for providing all users of the network access to the link relationships stored in the one or more link directories based upon the document object currently accessed by the users.
- a system for establishing and providing access to relationships between document objects stored on a network wherein the relationship between a first document object and a second document object may be created by an individual user of the network and provided to other users of the network.
- the system may include one or more client devices that access document objects stored on the network and create link relationships between a first document object and a second document object; and one or more servers that store and filter the link relationships created by the client devices and transmit one or more link relationships and link references to the client devices.
- a computer readable medium on which is embedded a program.
- the embedded program comprises modules that execute the above method.
- FIG. 1 is a diagram showing a system according to one embodiment of the invention.
- FIG. 2 is a diagram showing a client device which is Linkspace-enabled and its interaction with other hardware and software;
- FIG. 3 a is a diagram showing the components of a server which is Linkspace-enabled and its interaction with other hardware and software;
- FIG. 3 b is a diagram showing more detail of one embodiment of a user data store from FIG. 3 a;
- FIG. 4 a is a diagram illustrating one embodiment of a link directory according to one embodiment of the invention.
- FIG. 4 b is a diagram illustrating another embodiment of a link directory according to one embodiment of the invention.
- FIG. 5 is a diagram showing one embodiment of the invention implemented on public, private or closed computer networks
- FIG. 6 is a flowchart illustrating a method according to one embodiment of the invention.
- FIG. 7 is a flowchart illustrating a method for, identifying link relationships between document objects according to one embodiment of the invention.
- FIG. 8 is a flowchart illustrating a method for publishing link relationships between document objects according to one embodiment of the invention.
- FIG. 9 is one example screen view of a user interface for a relate links dialog box according to one embodiment of the invention.
- FIG. 10 is an example of a screen view for a client user interface according to one embodiment of the invention.
- FIG. 1 shows one embodiment of a system 100 for collecting, storing, managing and providing to network users categorized information related to an open document object.
- a document object may contain any form of information, including text documents and articles, financial data, statistical information, electronic mail, images and photos, music, voice data, animation, and even motion pictures.
- the system 100 includes a network 10 , such as the Internet or other network of interconnected computers or a combination of networks and the Internet; one or more Linkspace-enabled client devices 20 ; one or more Linkspace-enabled servers 30 , one or more first document objects 40 ; one or more second document objects 50 ; one or more link references 42 and 52 , corresponding to the first document objects 40 and the second document objects 50 respectively; and one or more link relationships 45 .
- the system 100 may also include one or more links 41 and 51 pointing to the first document objects 40 and second document objects 50 respectively.
- the client devices 20 are preferably Linkspace-enabled.
- the client device 20 may comprise a computer or other digital information device running software enabled by the present invention to create, filter, sort and display the link references 42 , 52 , and the link relationships 45 .
- the server 30 may comprise a server computer or other digital information device running software enabling the present invention to store, index, search, filter, sort and transmit the link references 42 , 52 , and the link relationships 45 to client devices 20 .
- the server 30 further comprises one or more link directories 35 for storing and indexing information regarding the link relationships 45 and link references 42 and 52 developed by the client devices 20 with respect to the one or more first documents 40 and second documents 50 .
- the link reference 42 , 52 comprises a pointer to one document object 40 , 50 on the network 10 and attributes associated with that document object 40 , 50 .
- the link relationship 45 comprises two pointers, one each to the first document object 40 and to the second document object 50 , and attributes describing characteristics of the relationship between the two document objects 40 , 50 related by the link relationship 45 .
- the pointers included in a link relationship 45 may be comprised of pointers to a link reference 42 , 52 .
- the link relationship 45 establishes a meaningful relationship between two document objects 40 , 50 , whereas the locations of the document objects 40 , 50 may be maintained within the Linkspace system 100 by means of the link references 42 , 52 .
- the system 100 shown in FIG. 1 operates to create and store link relationships 45 .
- the system 100 creates and stores link relationships 45 between a first document object 40 and a second document object 50 , preferably on one or more servers 30 in one or more link directories 35 in the manner described as follows.
- the client device 20 is enabled by means of software or other devices to request, access and display document objects on the network 10 .
- the user of a client device 20 identifies one first document object 40 of interest to her that she wishes to associate with a second document object 50
- she utilizes the software running on the Linkspace-enabled client device 20 to create a link relationship 45 between the first document object 40 and the second document object 50 .
- This link relationship 45 is then stored on the server 30 in a link directory 35 .
- system 100 may operate to perform the functions described above, including the creation of link relationships 45 and link references 42 , 52 , the storing of link relationships 45 and link references 42 , 52 , and providing access to and retrieval of link relationships 45 and link references 42 , 52 , by means of automated procedures requiring little or no user interaction.
- the server 30 delivers to the client device 20 the link references 42 and the link relationships 45 , along with contextual information, or attributes, associated with the link references 42 and the link relationships 45 .
- the client device 20 displays to the user of the client device 20 the existence of a link relationship 45 between the first document object 40 being accessed by the client device 20 and the second document object 50 .
- Each link relationship 45 may also operate in the reverse direction.
- the server 30 transmits the link references 42 and the link relationships 45 , with contextual information, to the client device 20 .
- This enables display of the availability of the related first document object 40 to the user of the client device 20 with the context of the first document object 40 , and within the context of its relationship to the displayed second document object 50 .
- the system 100 is generally described as having enabling software resident on the client device 20 and on the server 30 , various other software configurations are possible, including having all of the software resident at either the server 30 (making the client device 20 essentially a “dumb terminal”) or at the client device 20 (making the client device 20 essentially perform server functions), or various software sharing arrangements.
- the client device 20 may include the one or more link directories 35 , a communications module (described later in reference to FIG. 3 a ), and a user data store that may maintain information regarding authorized users of the client device 20 (described later in reference to FIGS. 2 , 3 a , and 3 b ).
- FIG. 2 is a diagram showing an example of the components of a Linkspace-enabled client device 20 and its interaction with other software and hardware.
- the client device 20 preferably includes a rendering tool 210 , such as a web page browser like Microsoft® Internet Explorer, for rendering document objects located on the network 10 and displaying those document objects to users of the client device 20 ; a client tool 220 , for allowing the user of the client device 20 to create and access link relationships 45 between document objects; and a network access tool 240 , such as a TCP/IP stack or other interface, for allowing software modules on the client device 20 to connect to and communicate with other devices and document objects on the network 10 .
- the client device 20 operates primarily to create and present link relationships 45 to users.
- the rendering tool 210 may store a document object URL address 215 for referring to the document object currently being accessed and rendered by the rendering tool 210 .
- the rendering tool 210 may also include a Graphic User Interface (“GUI”) display 218 , or other type of display, for displaying the document objects accessed and rendered by the rendering tool 210 .
- GUI Graphic User Interface
- the client device 20 may include more than one rendering tool 210 enabling the user of the client device 20 to access multiple document objects.
- the client tool 220 may include a client GUI display 225 , or other display software and hardware, for displaying link references 42 , 52 and link relationships 45 to the user of the client device 20 .
- the displayed link references 42 , 52 and link relationships 45 would be those link references 42 , 52 and link relationships 45 relevant to the document object currently being rendered and displayed by the rendering tool 210 (as determined by the document object URL address 215 in the rendering tool 210 ).
- the client tool 220 may also include Linkspace user profile data 230 for storing information about the user of the client device 20 , the link directories 35 the user may have access to, and the attributes of link references 42 , 52 , and attributes of link relationships 45 that the user may be interested in.
- the Linkspace user profile data 230 may also or alternatively be stored on the one or more servers 30 , along with the Linkspace user profile data 230 of all other users of the system 100 .
- the client device 20 operates to create and present link relationships 45 to users of the client device 20 follows. While the network access tool 240 is active and placing the client device 20 in communication with the network 10 , the user enables the rendering tool 210 and the client tool 220 . The user may then request and access document objects stored on the network 10 by means of the rendering tool 210 . Through the GUI display 218 , the users enters or otherwise selects a document object URL address 215 associated with the first document object 40 of interest to the user. The client tool 220 connects to and uses the rendering tool 210 and accesses the document object URL address 215 associated with the first document object 40 .
- the client tool 220 then establishes contact with the server 30 and passes to the server 30 the stored document object URL address 215 associated with the first document object 40 , along with any relevant information that may come from the Linkspace user profile data 230 .
- the connection to the server 30 may be initiated through the network access tool 240 or by other means not utilizing the network access tool 240 .
- the Linkspace-enabled server 30 searches the link directories 35 for any URLs in the link references 42 , 52 matching, or similar to, the document object URL address 215 . After searching, the server 30 retrieves the one or more link relationships 45 that include the document object URL address 215 . Prior to searching, the URLs may be stripped of any information not relevant to the location of the document object 40 , 50 on the network 10 . Such information not relevant to the location of the document object 40 , 50 may include query strings or other data attached to URLs for tracking or other purposes.
- the server 30 determines the link references 42 , 52 which may be of interest to the user of the client device 20 by filtering the retrieved link references 42 , 52 using the Linkspace user profile data 230 and the attributes assigned to the link references 42 , 52 and to the link relationships 45 .
- the filtering of link references 42 , 52 and link relationships 45 may be accomplished by one of several methods of filtering data including matching, character and Boolean comparing, and other data comparison and filtering methods.
- the server 30 transmits to the client tool 220 the filtered link references 42 , 52 included in the one or more link relationships 45 .
- the client tool 220 presents the transmitted link references 42 , 52 within the context established by the link relationships 45 by means of the client GUI display 225 .
- the user of the client device 20 must select a first document object 40 to begin the link relationship, a second document object 50 to complete the link relationship 45 , and assign attributes to the link references 42 , 52 and the link relationship 45 between the two document objects 40 , 50 .
- the user interacts with the client GUI display 225 to activate a function of the client tool 220 to capture the document object URL address 215 associated with the first document object 40 .
- the user may interact with the GUI display 218 of the rendering tool 210 to request, access and display the second document object 50 .
- the user may then interact with the client GUI display 225 again to activate a further function of the client tool 220 to capture the document object URL address 215 associated with the second document object 50 , completing the selection of document objects 40 , 50 participating in the new link relationship 45 .
- attributes of the link references 42 , 52 and the new link relationship 45 may be assigned.
- the user may select or otherwise specify attributes associated with the link references 42 , 52 and link relationship 45 . These attributes aid in categorizing, sorting or filtering the link references 42 , 52 and the link relationship 45 in the link directories 35 for delivery to other client devices 20 .
- the attributes may be, for example, descriptive, temporal, spatial, or quantitative in nature, i.e., describe the link reference in terms of who or what, when, where, or how much.
- One such attribute (not shown) may be a plain language name for the link reference 42 , 52 , determined and entered by the user to describe the link reference in terms more useful to users of the system 100 than the document object URL address 215 .
- attributes may include description of the content of either of the document objects 40 , 50 related by the link relationship 45 , wherein that content may be described to include a product review, news article, product information page, competitor's product information, or product order forms, among other types of content.
- the client tool 220 connects to the server 30 to store the link references and the new link relationship 45 in the appropriate link directory 35 .
- the new link relationship 45 is then made available to other users.
- other client devices 20 who have access to the server 30 and are assigned access privileges on the link directory 35 in which the new link relationship 45 has been stored are given access to the new link relationship 45 .
- the user of the client device 20 determines that there is a relationship that is not already described by the transmitted link relationships 45 between the currently accessed document object 40 and a second document object 50 , the user may proceed to create and publish a new link relationship 45 between the first document object 40 (currently accessed and displayed by the rendering tool 210 ) and the second document object 50 . This may be accomplished without displaying the second document object 50 .
- FIG. 3 a is a diagram showing the components of the Linkspace-enabled server 30 and its interaction with other hardware and software.
- the server 30 includes a first link directory 35 , a user data store 370 , and a server manager 380 .
- the server 30 may also include a second link directory 310 and one or more Nth link directories 320 .
- the server manager 380 coordinates communications between the other components of the server 30 .
- the server manager 380 also coordinates communications with outside objects, including the one or more client devices 20 .
- the server manager 380 also performs the function of locating appropriate link directories 35 , 310 , 320 for the user to participate in based upon a document object presently displayed on the client device 20 .
- the user of the client device 20 may request that the server manager 380 look in all link directories 35 , 310 , 320 across the system 100 , regardless of whether the user has an affiliation with the specific link directory 35 , 310 , 320 (which may be set in the user's Linkspace user profile data 230 ), for the URL of the document object the user is currently accessing with the client device 20 .
- the user data store 370 stores identification and user profile data regarding users authorized to access the server 30 , which of the several link directories 35 , 310 , and 320 those users are permitted access to, and which attribute preferences the users have for each of the link directories 35 , 310 , 320 .
- portions of the information maintained in the user data store 370 may be stored in the link directories 35 , 310 , 320 .
- FIG. 3 a also shows one or more alternate Linkspace-enabled servers 350 that may reside on the network 10 .
- the one or more alternate servers 350 may be located off the network 10 but otherwise connected to or in communication with the client devices 20 and/or the first server 30 .
- One or more alternate link directories 360 may reside on the one or more alternate servers 350 .
- the one or more alternate servers 350 may include other elements duplicating the functions of the server manager 380 and user data store 370 , as well as additional link directories 310 and 320 .
- the existence of the alternate servers 350 provides for flexibility in the distribution of link directory data across several servers, redundancy and interoperability across multiple networks and/or sets of client devices 20 and users of the Linkspace system 100 .
- Each of the several link directories 35 , 310 , 320 or 360 may be associated with and store link references 42 , 52 and link relationships 45 .
- These link references 42 , 52 and link relationships 45 may have attributes matching categories defined by an authorized user designated to manage such link directories 35 , 310 , 320 or 360 .
- each link directory 35 , 310 , 320 or 360 may be considered to be a community of interest.
- the authorized user designated to manage such link directories 35 , 310 , 320 or 360 may also establish attributes by which to organize, sort and filter the link references and link relationships 45 . Attributes may describe the types and properties of the document objects 40 , 50 and the link relationships 45 . Any authorized user of the link directories 35 , 310 , 320 or 360 may then create and place link references and link relationships 45 in the link directories 35 , 310 , 320 or 360 and assign attributes to the link references and link relationships 45 .
- FIG. 3 a further illustrates the provision for a further link relationship 345 between the second document object 50 and a third document object 340 .
- the link relationship 345 may be created by an authorized user of one of the client devices 20 , just as the link relationship 45 between the first document object 40 and the second document object 50 was created.
- the link relationship 345 may be stored in a second link directory 310 , separated from the link relationship 45 stored in the first link directory 35 .
- the link relationships 45 and 345 may be considered to belong to differing communities of interest represented by the separate first link directory 35 and second link directory 310 .
- a user of a client device 20 who is currently viewing or otherwise accessing the second document object 50 will only be presented with the link relationship 345 if the user is an authorized user of, and thus in the user directory 370 list for, the second link directory 310 . Furthermore, a user of a client device 20 who is currently viewing or otherwise accessing the second document object 50 will only be presented with both the link relationship 45 and the link relationship 345 if the user is an authorized user of, and thus in the user directory 370 lists for, both the first link directory 35 and the second link directory 310 .
- a user of the Linkspace system may be or may apply to be an authorized user for any combination of or all of the link directories 35 , 310 , 320 , and 360 .
- FIG. 3 b is a diagram showing more detail of one embodiment of the user data store 370 from FIG. 3 a .
- the user data store 370 may include a user directory 372 , a user profile store 375 , and a user account store 378 .
- the user directory 372 includes one or more user data records 374 , typically one or more each for every authorized user of the servers 30 , 350 .
- the user data records 374 may include personal identifying data for an associated authorized user and data indicating the link directories 35 , 31 , 320 , 360 to which each user has access.
- the user profile store 375 includes one or more user profile records 330 , typically one or more each for every authorized user of the servers 30 , 350 .
- the user profile records 330 for each authorized user may further include one or more user profiles 332 .
- Each user profile 332 may contain data regarding specific, differing configurations of the user's personal, professional, geographic and other interests, and the servers 30 , link directories 35 , 310 , 320 , 360 , and attributes associated with those interests, as entered by the user or collected by the client tool 220 .
- the data in the user profile 332 may be used to determine what link directories 35 , 310 , 320 , 360 that the user may have engaged.
- the data in the user profile 332 may further determine what attributes of link references 42 , 52 , and of link relationships 45 , will be considered by the server 30 in returning the link references 42 , 52 and the link relationships 45 from the link directories 35 , 310 , 320 , 360 to the user's client device 20 .
- the user account store 378 includes one or more user account records 379 , usually one each for every authorized user of the servers 30 , 350 .
- the user account records 379 hold information regarding usage of the Linkspace system 100 by each authorized user.
- the information in the user account records 379 may include data on instances of the publication of link relationships 45 , and the transmissions of link relationships 45 and link references 42 , 52 based upon the document object displayed by the client tool 220 of each user.
- data regarding the document objects 40 , 50 , 340 requested and accessed by users of the system 100 is not recorded in the user account records 379 against the individual authorized user in order to maintain user privacy with regard to what document objects 40 , 50 , 340 each individual user may request or access.
- the server manager 380 When an authorized user of a client device 20 creates a link relationship 45 that is stored in one or more of the link directories 35 , 310 , 320 , 360 , the server manager 380 records in the user account record 379 (associated with the authorized user creating the link relationship 45 ) the activity of creating and storing a link relationship 45 .
- Each of the authorized users of the link directories 35 , 310 , 320 , 360 may be allowed to create link relationships 45 to be stored in one or more of the link directories 35 , 310 , 320 or 360 , to which that authorized user is permitted publication access.
- Each of the authorized users of each specific link directory 35 , 310 , 320 , 360 may also be allowed access for display those link relationships 45 stored in the specific link directory 35 , 310 , 320 , 360 that relate to the first document object 40 or second document object 50 that the user is currently viewing on the user's client device 20 .
- each of the elements of the server 30 , alternate server 350 , the client devices 20 , and the first, second and third document objects 40 , 50 , and 340 , along with the creation and presentation of the link relationships 45 and 345 may be illustrated by the application of the methods 600 , 700 , and 800 described below with reference to FIGS. 6 , 7 , and 8 .
- FIG. 4 a shows the general structure of one embodiment of the link directory 35 .
- This embodiment of the link directory 35 includes a link relationship table 420 .
- the link relationship table 420 comprises a list of link relationships 460 , 470 , 480 , 490 . These link relationships 460 , 470 , 480 , 490 correspond to the link relationships 45 , 345 created by users of the client device 20 as they are stored in the link directory 35 .
- the link relationship 460 comprises a field 462 containing a link reference 42 (L 1 ) including the URL address of the first document object 40 related by the link relationship 460 ; a field 463 containing a link reference 52 (L 2 ) including the URL address of the second document object 50 related by the link relationship 460 ; a set of link relationship attributes 465 ; and a directional indicator 466 showing the nature of the link relationship between the two document objects, either unidirectional or bi-directional.
- the link relationship 460 is shown with the directional indicator 466 specifying that the link relationship 460 is a unidirectional link relationship.
- Some or all of the list of link relationships 460 , 470 , 480 , 490 comprising the link relationship table 420 may, in one embodiment of the invention, be stored on the server 30 in the form of relational database records.
- the relational database record corresponding to the link relationship 460 may be comprised of one or more relational database fields corresponding to the field (L 1 ) 462 , field (L 2 ) 463 , link relationship attributes 465 , and directional indicator 466 .
- Each of the one or more relational database fields may be formatted and designated to store various forms of relational database data types.
- the relational database field corresponding to the field 462 may contain data specifying the appropriate URL as text or other format appropriate for the network upon which the invention may be implemented.
- the relational database field corresponding to the directional indicator 466 may be formatted as a simple flag (i.e., Boolean) data type such as True/False, Yes/No, or On/Off.
- the relational database field corresponding to the directional indicator 466 may be formatted as a type to allow entry of a value indicating whether the link relationship attribute 465 applies forward, backward or in both directions across the link relationship 460 .
- the link relationship attributes 465 may be represented by one or more relational database fields.
- the relational database fields comprising the link relationship attributes 465 may include a field of text data listing the assigned titles of the one or more specific link relationship attributes assigned to the link relationship 460 .
- the relational database fields comprising the link relationship attributes 465 may then also include one or more attribute value fields containing data formatted appropriately for the corresponding link relationship attribute listed in the above described field of text data.
- the plain language name link relationship attribute may have its corresponding value stored in a field formatted as text
- a zip code attribute may have its corresponding value stored in a field formatted as a 5 or 9 digit integer
- a date attribute may have its corresponding value stored in a field formatted in a date format.
- the relational database fields comprising the link relationship attributes 465 may utilize relational database key fields which point to additional database tables containing the records specifying each available type of link relationship attribute for the link relationship 460 and key fields which point to additional tables containing the values associated with each of link relationship attribute identified by a key.
- the link relationship 470 comprises a field 472 containing a link reference 42 (L 1 ) including the URL address of the first document object 40 related by the link relationship 470 ; a field 473 containing a third link reference (L 3 ) including the URL address of the third document object 340 related by the link relationship 470 ; a set of link relationship attributes 475 ; and a directional indicator 476 showing the nature of the link relationship between the two document objects, either unidirectional or bi-directional.
- the link relationship 470 is shown with the directional indicator 476 specifying that the link relationship 470 is a bi-directional link relationship.
- the link relationship 480 comprises a field 482 containing a link reference 52 (L 2 ) including the URL address of the second document object 50 related by the link relationship 480 ; a field 483 containing the third link reference (L 3 ) including the URL address of the third document object 340 related by the link relationship 480 ; a set of link relationship attributes 485 ; and a directional indicator 486 showing the nature of the link relationship between the two document objects, either unidirectional or bi-directional.
- the link relationship 480 is shown with the directional indicator 486 specifying that the link relationship 480 is a bi-directional link relationship.
- the link relationship 490 comprises a field 492 containing a link reference 52 (L 2 ) including the URL address of the second document object 50 related by the link relationship 490 ; a field 493 containing a link reference 42 (L 1 ) including the URL address of the first document object 40 related by the link relationship 490 ; a set of link relationship attributes 495 ; and a directional indicator 496 showing the nature of the link relationship between the two document objects, either directional or bi-directional.
- the link relationship 490 is shown with the directional indicator 496 specifying that the link relationship 490 is a unidirectional link relationship.
- the link relationship attributes 465 , 475 , 485 , 495 may include a plain language name (not shown) associated with each of the link references 42 , 52 participating in the respective link relationship 460 , 470 , 480 , 490 , as determined and entered by the user of the client tool 220 .
- the plain language name serves to describe the link reference 42 , 52 in terms better understood by the users of the system 100 than the URL associated with the link reference 42 , 52 .
- the link relationship attributes 465 , 475 , 485 , 495 serve to describe the link references 42 , 52 in terms useful to users of the system 100 , and to place the link references 42 , 52 in a context that may attract users to select the link references 42 , 52 .
- link relationship attributes 465 , 475 , 485 , 495 may include descriptions of the content of either of the document objects 40 , 50 related by the link relationship 460 , 470 , 480 , 490 , wherein that content may be described to include a product review, news article, product information page, competitor's product information, or product order forms, among other types of content.
- the link relationship 470 may have a value assigned to the directional indicator 476 specifying that the link relationship 470 is a bi-directional link relationship. This indicates that the link relationship attributes 475 apply to either of the two document objects ( 40 and 340 ) equally in the context of the link relationship 470 .
- the link relationship 460 may, on the other hand, have a value assigned to the direction indicator 466 specifying that the link relationship 460 is a unidirectional link relationship. This signifies that the link relationship attributes 465 apply in only one direction between the two document objects 40 and 50 represented in the fields 462 and 463 through the link references 42 and 52 respectively. In this instance, a link relationship will not be transmitted and presented to the user of the client device 20 when requested in the direction opposite to that specified by the direction indicator 466 . In the case of the link relationship 460 shown in FIG. 4 a , the attributes 465 apply only as the link relationship 460 is traversed from the first link reference 42 to the second link reference 52 , and not in the reverse direction.
- the link relationship 490 may have a value assigned to the direction indicator 496 specifying that the link relationship 490 is a unidirectional link relationship. This signifies that the link relationship attributes 495 apply in only one direction between the two document objects 50 and 40 represented in the fields 492 and 493 through the link references 52 and 42 respectively.
- the attributes 495 apply only as the link relationship 490 is traversed from the second link reference 52 to the first link reference 42 , and not in the reverse direction. In this instance, a link relationship will not be transmitted and presented to the user of the client device 20 when requested in the direction opposite to that specified by the direction indicator 496 .
- the direction indicator 466 of the link relationship 460 may comprise a plurality of directional indicator fields (not shown). Each directional indicator field may then correspond to one of the one or more link relationship attributes 465 and indicate whether the corresponding link relationship attribute 465 may apply in one direction or in both directions between the two document objects 40 and 50 represented in the fields 462 and 463 through the link references 42 and 52 respectively.
- the direction indicator 496 of the link relationship 490 may comprise a plurality of directional indicator fields (not shown). Each directional indicator field may then correspond to one of the one or more link relationship attributes 495 and indicate whether the corresponding link relationship attribute 495 may apply in one direction or in both directions between the two document objects 50 and 40 represented in the fields 492 and 493 through the link references 52 and 42 respectively.
- a similar arrangement may then be implemented for the remaining direction indicators 476 , 486 of the link relationships 470 , 480 .
- FIG. 4 b shows the general structure of another embodiment of the link directory 35 .
- This embodiment of the link directory 35 includes a document object table 410 , and a link relationship table 420 , as described above for FIG. 4 a.
- the document object table 410 comprises a set of link references 430 , 440 , 450 to document objects located on the network 10 to which the link directory 35 is connected.
- Each link reference 430 , 440 , 450 further comprises the URL 432 , 442 , or 452 of the respective document object 40 , 50 , 340 of interest; a set of document object attributes 435 , 445 , 455 associated with the URL 432 , 442 , 452 ; and a list 437 , 447 , 457 of pointers to any of the link relationships 460 , 470 , 480 , 490 by which the link references 430 , 440 , 450 may be connected to each other with context.
- link relationship 460 , 490 having the direction indicator 466 , 496 set to indicate that the link relationship 460 , 490 is unidirectional
- the link relationship 460 , 490 will be listed only in the list 437 , 447 , 457 of pointers for the link reference 430 , 440 , 450 that begins the unidirectional link relationship 460 , 490 .
- the link references 430 , 440 , and 450 in FIG. 4 b correspond to the link references 42 , 52 , and the third link reference (not shown), as described in FIGS. 1-4 a above, and which point to the URL addresses of the document objects 40 , 50 , and 340 respectively.
- the document object attributes 435 , 445 , 455 serve to describe the link references 430 , 440 , 450 in terms useful to users of the system 100 , and to place the link references 430 , 440 , 450 in a context that may attract users to select the link references 430 , 440 , 450 .
- the document object attributes 435 , 445 , 455 may include a plain language name that serves to describe the document object 40 , 50 , 340 in terms better understood by the users of the system 100 than the URLs associated with the link references 430 , 440 , 450 ; descriptions of the content of the document object 40 , 50 , 340 associated with link references 430 , 440 , 450 , wherein that content may be described to include a product review, news article, product information page, competitor's product information, or product order forms, among other types of content; and other descriptive characteristics associated with the document object 40 , 50 , 340 .
- the link references 430 , 440 , and 450 may be created and placed in the document object table 410 when a user of the client device 20 creates a link relationship 45 between a first document object 40 and a second document object 50 or a third document object 340 .
- the link relationship table 420 shown in FIG. 4 b comprises the same list of link relationships 460 , 470 , 480 , 490 , detailed above in FIG. 4 a .
- the link relationship 460 comprises a field 462 containing a pointer to the link reference 430 for the first document object 40 related by the link relationship 460 ; a field 463 containing a pointer to the link reference 440 for the second document object 50 related by the link relationship 460 ; the link relationship attributes 465 ; and the directional indicator 466 .
- FIG. 4 b the link relationship 460 comprises a field 462 containing a pointer to the link reference 430 for the first document object 40 related by the link relationship 460 ; a field 463 containing a pointer to the link reference 440 for the second document object 50 related by the link relationship 460 ; the link relationship attributes 465 ; and the directional indicator 466 .
- the link relationship 470 comprises a field 472 containing a pointer to the link reference 430 for the first document object 40 related by the link relationship 470 ; a field 473 containing a pointer to the link reference 450 for the third document object 340 related by the link relationship 470 ; the link relationship attributes 475 ; and the directional indicator 476 .
- link relationship 480 comprises a field 482 containing a pointer to the link reference 440 for the second document object 50 related by the link relationship 480 ; a field 483 containing a pointer to the link reference 450 for the third document object 340 related by the link relationship 480 ; the link relationship attributes 485 ; and the directional indicator 486 .
- the link relationship 490 comprises a field 492 containing a pointer to the link reference 440 for the second document object 50 related by the link relationship 490 ; a field 493 containing a pointer to the link reference 430 for the first document object 40 related by the link relationship 490 ; the link relationship attributes 495 ; and the directional indicator 496 .
- FIG. 5 illustrates one embodiment of the present invention in which the invention may operate on multiple networks of varying degrees of network security.
- the different networks on which the systems and methods of the present invention may be implemented include a public network such as the Internet 510 , a private network 520 that may be connected to the Internet 510 , and a closed network 530 that is secure and not accessible to users not connected to the closed network 530 .
- the closed network 530 is not connected to any public network such as the Internet 510 , and is not connected to another private network 520 .
- the public network or Internet 510 may have components connected to it that implement the present invention, including one or more Linkspace-enabled client users 511 , one or more link directories 512 , one or more Linkspace-hosted content units 513 , and one or more networked content units 514 .
- the link directories 512 described here are functionally equivalent to the link directories 35 , 310 , 320 , and 360 described above in connection with FIGS. 1 , 2 and 3 a .
- the Linkspace-hosted content units 513 comprise information storage devices connected to the network 510 that provide additional document object storage facilities to users of the Linkspace system 100 separate from the publicly or privately operated networked content units 514 .
- the networked content units 514 may include networked data servers or web servers.
- the Linkspace-hosted content units 513 are provided to accommodate the streamlined publication and/or distribution of content by users of the Linkspace system 100 .
- the client tool 220 may allow a user of the Linkspace system 100 to store document objects of his or her own creation through a simplified procedure, i.e., a publish document function enabled through the client GUI display 225 .
- the user of the client device 20 may select a document object 40 that she wishes to publish through the Linkspace-hosted content units 513 , or she may create a document object (not shown) using the rendering tool 210 or other document object creation tool.
- the user of the client device 20 selects the publish document function through the client GUI display 225 and selects the link directories 35 , 310 , 320 , 360 in which she wishes to create and publish new link relationships 45 , 345 referencing the user created or selected document object.
- the user of the client device 20 may then create and publish link relationships 45 , 345 referencing the user created or selected document object.
- the client tool 220 may automatically upload the user created or selected document object from the user's client device 20 , or from another location on the network, in this case the Internet 510 , and save it on the Linkspace-hosted content unit 513 .
- the client tool 220 may then publish the new link relationships 45 , 345 referencing the user created or selected document object to the appropriate link directory 35 , 310 , 320 , 360 , and then make the user created or selected document object available to other users of the Linkspace system 100 through the new link relationships 45 , 345 .
- the activity of publishing a user created or selected document object in this manner is also recorded in the appropriate user account record 379 for the user creating or selecting the document object to be published.
- the private network 520 may have connected to it components that implement the present invention, including one or more Linkspace-enabled client users 521 , one or more link directories 522 , one or more Linkspace-hosted content units 523 , and one or more networked content units 524 .
- the closed network 530 may have connected to it components that implement the present invention, including one or more Linkspace-enabled client users 531 , one or more link directories 532 , one or more Linkspace-hosted content units 533 , and one or more networked content units 534 .
- the private network 520 is shown connected to the public network or Internet 510 .
- This may allow Linkspace-enabled client users 521 connected to the private network 520 to also be permitted access to any of the one or more link directories 512 , Linkspace-hosted content units 513 , and networked content units 514 that are connected to the public network or Internet 510 .
- Linkspace-enabled client users 511 connected to the public network or Internet 510 that are not also among the group of authorized Linkspace-enabled client users 521 of the private network 520 , may not be permitted to access the one or more link directories 522 , Linkspace-hosted content units 523 , and networked content units 524 that are connected to the private network 520 .
- a Linkspace client user 531 connected to the closed network 530 may only be permitted access to the one or more link directories 532 , Linkspace-hosted content units 533 , and networked content units 534 that are connected to the closed network 530 .
- FIG. 6 is a flowchart showing the steps of a method 600 according to one embodiment of the present invention.
- the method 600 includes the steps of a first user (not shown) of a client device 20 locating a first document object 40 (step 610 ); the first user locating a second document object 50 (step 620 ); and the first user creating a link relationship 45 between the first document object 40 and the second document object 50 (step 630 ).
- the method 600 includes the additional steps of storing the link relationship 45 created by the first user in a link directory 35 (step 640 ); and providing access to the link directory 35 to a second user (not shown) of another client device 20 (step 650 ).
- the method 600 may include a step for providing authorized users of client devices 20 access to the link relationships 45 stored in link directories 35 , based upon the document object 40 currently accessed by the users on the users' client device 20 (step 660 ).
- FIG. 7 is a flowchart showing the steps of a method 700 for accessing and displaying link relationships and related document objects on a network according to one embodiment of the present invention.
- the method 700 initiates when a user of a client device 20 engages the rendering tool 210 to request, access and display a document object 40 (step 710 ).
- the user of the client device 20 then engages the client tool 220 and is authenticated by a server 30 (step 715 ).
- the user of the client device 20 selects a user profile 332 (step 717 ) that has been returned to the client device 20 upon authentication of the user by the server 30 in step 715 .
- the selected user profile 332 may be used to determine what attributes of the link relationships 45 will be applied to filter and sort the link references 430 , 440 , 450 and link relationships 460 , 470 , 480 returned by the server 30 .
- By filtering and sorting using attributes a manageable and meaningful group of relevant link references 430 , 440 , 450 may be displayed to the user based on the user's needs and interests.
- the steps 715 and 717 may occur before the step 710 .
- the user selects a client tool 220 function (step 720 ).
- the first function that the user may select is to enter a document object URL 215 into the rendering tool 210 , whereupon that document object URL 215 is captured by the client tool 220 and transmitted to the servers 30 (step 730 ).
- the activity of transmitting the document object URL 215 to the servers 30 by the client tool 220 may be recorded and stored in an appropriate location within the user data store 370 .
- the server 30 then processes the transmitted document object URL 215 across the various link directories 35 to which the user is authorized access.
- One method of processing by the server 30 is according to the following steps.
- the server 30 performs a search of the document object tables 410 of all link directories 35 to find all instances of the document object URL 215 (step 735 ).
- the server 30 searches the Link relationship tables 420 in the link directories 35 where the URL 215 was found.
- This search by the server 30 locates all link relationships 460 , 470 , 480 , 490 referencing the URL 215 as one of the pointers to link references 462 or 463 , 472 or 473 , 482 or 483 , 492 or 493 included in those link relationship 460 , 470 , 480 , 490 (step 740 ).
- the server 30 then accumulates all the URLs 432 , 442 , 452 related, through the link relationships 460 , 470 , 480 , 490 identified in step 740 , to the URL 215 .
- the server 30 also accumulates the document object attributes 435 , 445 , 455 associated with the identified URLs 432 , 442 , 452 and the link relationship attributes 465 , 475 , 485 , 495 associated with the link relationships 460 , 470 , 480 , 490 identified in step 740 (step 745 ).
- the accumulated URLs 432 , 442 , 452 are then filtered by link relationship attributes 465 , 475 , 485 , 495 (step 750 ), and then filtered again by document object attributes 435 , 445 , 455 (step 755 ).
- the accumulated URLs 432 , 442 , 452 may be filtered first by document object attributes 435 , 445 , 455 (step 755 ) and then by link relationship attributes 465 , 475 , 485 , 495 (step 750 ).
- the user profile 332 is applied to determine what link relationship attributes 465 , 475 , 485 , 495 , and document object attributes 435 , 445 , 455 to use in filtering the accumulated URLs 432 , 442 , 452 .
- the filtered URLs 432 , 442 , 452 are then sent back to the client device 20 that transmitted the URL 215 , along with the associated document object attributes 435 , 445 , 455 , and associated link relationship attributes 465 , 475 , 485 , 495 (step 760 ).
- the activity of transmitting the filtered URLs 432 , 442 , 452 , along with the associated document object attributes 435 , 445 , 455 , and associated link relationship attributes 465 , 475 , 485 , 495 , to the client device 20 may be recorded and stored in an appropriate location within the user data store 370 .
- the first filtering steps 750 , 755 may be performed by the client device 20 .
- the client tool 220 upon receiving the filtered URLs 432 , 442 , 452 from the server 30 , may further filter and sort the returned URLs 432 , 442 , 452 according to data stored in the selected user profile 332 (step 765 ). In this manner, the data in the user profile 332 may be applied to the filtered and sorted URLs 432 , 442 , 452 on either the server 30 or the client tool 20 .
- the filtered and sorted URLs 432 , 442 , 452 are then displayed to the user of the client device 20 by the client GUI display 225 and the client tool 220 alerts the user of the client device 20 to the availability of related links (in the form of the returned URLs 432 , 442 , 452 ) by means of an indicator in the client GUI display 225 (step 770 ).
- the method 700 then returns to step 720 to await further action by the user of the client device 20 .
- step 720 the user of the client device 20 selects one of the URL links 432 , 442 , 452 displayed by the Linkspace GUI display as being related by link relationships 460 , 470 , 480 , 490 to the presently accessed document object 40 with the URL 215 (step 780 )
- the rendering tool 210 accesses the new document object 50 associated with the selected URL and displays that document object 50 in the GUI display 218 of the rendering tool 210 (step 785 ).
- the new document object URL address 215 of the selected document object 50 is then passed on to the servers 30 (step 790 ) and the method 700 continues with step 735 , as above, using the URL 215 of the new document object 50 as the URL to search for.
- FIG. 8 is a flowchart showing the steps of a method 800 for creating and publishing link relationships according to one embodiment of the present invention.
- the method 800 initiates when a user of the client device 20 engages the client tool 220 and is authenticated by a server 30 (step 810 ).
- the user of the client device 20 may then select a publish link relationship function of the client tool 220 (step 815 ).
- the user of the client device 20 may then navigate, using the rendering tool 210 , to the first document object 40 of the new link relationship 45 that the user of the client device 20 wishes to create and publish.
- the user may then select a declare first link function of the client tool 220 (step 820 ).
- the user of the client device 20 may then navigate, again using the rendering tool 210 , to the second document object 50 that the user of the client device 20 wishes to associate by means of a link relationship 45 with the first document object 40 .
- the user can then select the declare second link function of the client tool 220 (step 825 ).
- the user of the client device 20 has now selected both ends of a link relationship 45 .
- the user of the client device 20 may then further assign link relationship attributes, such as those shown in FIG. 4 ( 465 , 475 , 485 , 495 ) to the link relationship 45 , along with assigning any document object attributes, such as those shown in FIG. 4 ( 435 , 445 , 455 ), to the first document object 40 and second document object 50 of the link relationship 45 (step 835 ).
- the user may then interact with a Linkspace GUI 225 button or element to complete the link relationship publish function (step 840 ).
- the URLs and document object attributes of the document objects 40 and 50 associated by the new link relationship 45 are stored in the document object table 410 in the selected link directory 35 (step 850 ). Additionally, the new link relationship 45 , along with the URL references to the first document object 40 and second document object 50 and the link relationship attributes, such as those shown in FIG. 4 ( 465 , 475 , 485 , 495 ), are stored in the link relationship table 420 in the selected link directory 35 (step 855 ).
- the method 800 for creating and publishing link relationships completes by recording the publishing activity to the user account record 379 associated with the user of the client device 20 for later tracking and billing purposes (step 880 ).
- FIG. 9 is an example of a user interface, more specifically, a screen view of a user interface for a relate links dialog box 900 , one element of the user interface of one embodiment of the invention.
- the relate links dialog box 900 is invoked when a user of the client tool 220 engages the publish link relationship function of the client tool 220 .
- the relate links dialog box 900 includes a drop down list 910 for selecting a community of interest, a user interface term referring to one of the one or more link directories 35 , and a checkbox 915 for indicating whether the link relationship 45 being created is to operate bi-directionally or unidirectionally. If the checkbox 915 is checked, then the link relationship 45 being created will only apply in one direction.
- the user has selected the community of interest (link directory 35 ) referred to as “Wireless Washington,” a link directory 35 storing link references 42 , 52 and link relationships 45 considered by their creators as relevant to wireless device users in the Washington, D.C. metropolitan area.
- the relate links dialog box 900 further includes a link-from section 920 , a link-to section 930 , a link relationship attributes display box 970 , a submit link relationship button 980 and a cancel button 985 .
- the submit link relationship button 980 is selected by the user when the user has selected and/or entered all information associated with the link references 42 , 52 and the link relationship 45 that the user wishes to publish.
- the client tool 220 closes the relate links dialog box 900 and transmits the information associated with the created link relationship 45 to one of the one or more servers 30 .
- the cancel button 985 may be selected by the user to abort the creation and publication of the link relationship 45 that the user initiated and to close the relate links dialog box 900 .
- the link-from section 920 may include a first document object URL 922 associated with the first document object 40 included in the link relationship 45 being created, where the first document object URL 922 was captured when the publish link relationship function was engaged; a first plain language name field 925 ; and a listing of first link reference attributes 940 and the attribute values 942 associated with those first link reference attributes 940 .
- the first document object URL 922 is the address of a first document object 40 that is a web page for a coffee and dessert shop.
- the first plain language name field 925 may be captured when the publish link relationship function was engaged and/or may be edited by the user creating the link relationship 45 .
- An exemplary first link reference attribute for food 945 and the value of specialty foods 947 assigned to the first link reference attribute 945 by the user creating the link relationship 45 , are also shown.
- the link-to section 930 similarly may include a second document object URL 932 associated with the second document object 50 included in the link relationship 45 being created, where the second document object URL 932 was captured when the publish link relationship function was engaged; a second plain language name field 935 ; and a listing of second link reference attributes 950 and the attribute values 952 associated with those second link reference attributes 950 .
- the second document object URL 932 is the address of a second document object 40 that is a web page for a “LinkSpace Restaurant” located in McLean, Virginia (a suburb of Washington).
- the second plain language name field 935 may be captured when the publish link relationship function was engaged and/or may be edited by the user creating the link relationship 45 .
- An exemplary second link reference attribute for location 955 and the value of address 995 assigned to the second link reference attribute 955 by the user creating the link relationship 45 , are also shown.
- a subordinate attribute for city 957 subordinate under the attribute for location 955 , and a value of address 995 along with the assigned value of McLean 958 for the subordinate attribute for city 957 , are also shown in the link-to section 930 .
- Further subordinate attributes may include a street 956 with a value 959 of 12345 Main Street.
- the link relationship attributes display box 970 includes a list of link relationship attributes 972 and a delete link relationship attribute button 975 .
- the link relationships 972 are formed by pairs of first link reference attributes 940 and second link reference attributes 950 that the user creating the link relationship 45 has selected to describe the nature of the link relationship 45 .
- These link relationship attributes 972 may form the link relationship attributes 465 , 475 , 485 , 495 described in FIG. 4 a .
- the delete link relationship attribute button 975 may be used to delete a selected link relationship attribute 972 displayed in the link relationship attributes display box 970 .
- the exemplary link relationship attribute 972 shown in FIG. 9 indicates that the user creating the link relationship 45 has declared that the city subordinate attribute 957 (one selected second link reference attribute 950 ) of the Linkspace Restaurant associated with the second document object 50 , having a value of McLean 958 , is related to the food attribute 945 (one selected first link reference attribute 940 ), having a value of specialty foods 947 , of the coffee shop associated with the first document object 40 .
- Linkspace Restaurant web page 9 is created and published, other users of Linkspace-enabled client devices 20 that request and/or access the Linkspace Restaurant web page may be presented with a link reference 42 , 52 pointing to the web page for the coffee and dessert shop, as illustrated in the link reference display window 1020 shown in FIG. 10 .
- the link relationship attribute 972 may be declared by the user performing a drag-and-drop operation wherein the link reference attribute 957 is dragged and dropped onto the link reference attribute 945 , creating the link relationship attribute 972 which relates the two document objects 40 , 50 by the association of the city subordinate attribute 957 to the food attribute 945 .
- the creation and selection of link relationship attributes 972 may be performed in a manner similar to that used in the link-to section 930 and link-from section 920 described above, utilizing a set of link relationship attribute types along with data input fields for entering or otherwise selecting values for those attributes.
- FIG. 10 is an example of a screen view for one embodiment of the client GUI display 225 for one embodiment of the invention, wherein the client GUI display 225 is integrated into the GUI display 218 of the rendering tool 210 .
- a client toolbar 1010 and a link reference display window 1020 together comprise the client GUI display 225 .
- a browser window 1030 displays the document object ( 40 , 50 ) being requested and accessed by the rendering tool 210 and having the document object URL address 215 displayed in an address bar field 1040 .
- the client toolbar 1010 includes a number of GUI buttons that initiate various functions of the client tool 220 .
- a client logon button 1050 initiates a connection between the client tool 220 and one or more servers 30 .
- a client logoff button 1055 ends a user session for the client tool 220 and disconnects the client tool 220 from the one or more servers 30 .
- a mark starting page button 1060 may be engaged to initiate the publish link relationship function of the client tool 220 by setting the currently displayed document object 40 shown in the browser window 1030 and referenced by the document object URL address 215 displayed in the address bar field 1040 as the first document object 40 in the link relationship 45 .
- a mark ending page button 1065 may be engaged to complete the selection of participating document objects 40 , 50 for the publish link relationship function of the client tool 220 .
- Engaging the mark ending page button 1065 sets the newly displayed document object 50 shown in the browser window 1030 and referenced by the document object URL address 215 displayed in the address bar field 1040 as the second document object 50 in the link relationship 45 , and opens a relate links dialogue box 900 (shown and described in FIG. 9 above) to allow the user of the client tool 220 to assign attributes to the link relationship 45 .
- the client toolbar 1010 also may include three icons that indicate the availability and type of link references 42 , 52 related to the document object 40 open in the browser window 1030 . These icons may include a publisher links indicator 1071 , a private links indicator 1072 , and a community links indicator 1073 .
- the link reference display window 1020 presents the user with a hierarchical listing of any link references 42 , 52 , delivered by the server 30 , that may be related to the document object 40 that is currently displayed in the browser window 1030 and has the document object URL address 215 shown in the address bar field 1040 .
- the link reference display window 1020 may be presented in a tabbed format, wherein each tab may contain a different set of link references 42 , 52 depending on the type of link reference and link relationship involved. In one embodiment of the invention, there may be three different tabs at the top of the link reference display window 1020 , each corresponding to one of the indicator icons ( 1071 , 1072 , 1073 ) in the client toolbar 1010 .
- the first tab may be a private links tab 1074 , corresponding to the private links indicator 1072 .
- the second tab may be a publisher links tab 1075 , corresponding to the publisher links indicator 1071 .
- the third tab may be a community links tab 1076 , corresponding to the community links indicator 1073 .
- the document object 40 displayed in the browser window 1030 in FIG. 10 is a representative web page, in this case for a restaurant named Linkspace.
- this page is displayed, and the client tool 220 is engaged, as indicated by the recessed display of the client logon button 1050 in the client toolbar 1010 , one or more of the indicator icons ( 1071 , 1072 , 1073 ) in the client toolbar 1010 will become highlighted if there are any link references 42 , 52 available of the corresponding type.
- the community links indicator 1073 is highlighted, while the publisher links indicator 1071 and the private links indicator 1072 are grayed out.
- the returned link references 42 , 52 are displayed in the link reference display window 1020 under the community links tab 1076 .
- the link references 42 , 52 are displayed in a hierarchical listing under affinity directory headings 1081 , 1082 .
- the affinity directory heading 1082 shown represents one community of interest, corresponding to one link directory 35 on a server 30 , maintaining one set of link relationships 45 and link references 42 , 52 , that may include the document object 40 displayed in the browser window 1030 .
- Each attribute folder 1091 , 1092 may contain a grouping of listed hyperlinks 1095 , 1096 drawn from the respective affinity directory heading 1082 and related to the document object 40 displayed in the browser window 1030 by a particular link relationship attribute 972 .
- affinity directory heading 1082 indicates a link directory 35 focusing on wireless devices in the Washington, D.C. area.
- attribute folder 1091 groups listed hyperlinks 1095 by the link relationship attribute 972 , further relating document objects 40 to specialty food document objects 50 .
- the listed hyperlink 1095 listed under the attribute folder 1091 , comprises the text of the plain language name attribute of a document object concerning coffee and dessert after dinner.
- the listed hyperlink 1095 displayed under the affinity directory heading 1082 and the attribute folder 1091 , represents a link reference 52 to a document object 50 that is related, as a document object of interest to wireless device users in the Washington area, and as a specialty food document object, to the document object 40 , the restaurant web page, displayed in the browser window 1030 .
- the attribute folder 1092 shown in the example in FIG. 10 groups listed hyperlinks 1096 by the link relationship attribute 972 further relating documents objects 40 to document objects 50 concerning the downtown area of the Washington, D.C. suburb of McLean.
- the listed hyperlink 1096 is to a LinkNexus document object for the city of McLean.
- a LinkNexus document object may comprise a listing of further link references 42 , 52 to document objects 40 , 50 relating to a particular subject.
- the LinkNexus document object indicated by the listed hyperlink 1096 may contain link references 42 , 52 concerning the suburban city of McLean.
- the listed hyperlink 1096 displayed under the affinity directory heading 1082 and the attribute folder 1092 , represents a link reference 52 to a document object 50 that is related, as a document object of interest to wireless device users in the Washington area, and as a link to content relevant to downtown McLean, to the document object 40 , the restaurant web page, displayed in the browser window 1030 .
- the affinity directory heading 1081 shown in the example in FIG. 10 indicates a community related to “Your Company,” the user's company.
- This affinity directory heading 1081 may contain link references 42 , 52 to document objects 40 , 50 maintained on the user's company's private network 520 , accessible to users within the company, but not to the general public, as shown and described in FIG. 5 .
- the steps of the methods 600 , 700 and 800 , and subsets of those steps or parts of the methods, may be implemented with hardware or by execution of programs, modules or scripts.
- the programs, modules or scripts may be stored or embodied on one or more computer readable mediums in a variety of formats, including source code, object code or executable code, among other formats.
- the computer readable mediums may include, for example, both storage devices and signals.
- Exemplary computer readable storage devices include conventional computer system RAM (random access memory), ROM (read only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), and magnetic or optical disks or tapes.
- Exemplary computer readable signals, whether modulated using a carrier or not, are signals that a computer system hosting or running the described methods can be configured to access, including signals downloaded through the Internet or other networks.
Abstract
Description
- This is a continuation application of Ser. No. 10/050,515, filed Jan. 18, 2002, entitled “A SYSTEM AND METHOD FOR COLLECTING, STORING, MANAGING AND PROVIDING CATEGORIZED INFORMATION RELATED TO A DOCUMENT OBJECT,” the subject matter of which is herein incorporated by reference in its entirety.
- The technical field is relating documents on computer networks and storing, indexing and presenting those relationships to network users.
- Networks connecting many computers offer users access to a wide variety of information. Computers are exceptional devices for storing, sorting and relating large amounts of information. Information is stored on computers and networked computing and storage devices as documents or objects, together referred to as document objects. Such document objects may contain any form of information, from text documents and articles, financial data, statistical information, electronic mail, images and photos, music, animation, and even motion pictures.
- The Internet, as a network of interconnected networks, offers users access to an even broader collection of information—the Worldwide Web (the “Web”). On the Web, publishers offer information for educational, recreational, and commercial purposes. The Internet, and it's predominant Web form, is organized and accessed by assigning document objects an address, or Uniform Resource Locater (“URL”). These URLs define the transfer protocol for and location of each individual document object on the Internet, or other network, including the Internetworking Protocol (“IP”) address of the host computer system of the document object.
- Users accessing computer networks and the Internet are generally required to perform their own searches across the networks for the information, stored as document objects, that they desire or need. As the amount of information available on computer networks, and on the Internet in particular, grows exponentially, existing search and information location techniques become increasingly less effective. Existing Internet search techniques often yield too many seemingly related references which are not, in fact, truly useful to the user. The usefulness of traditional Internet search and indexing systems is actually decreasing as the number of documents on the Internet explodes.
- Existing search, categorization, and retrieval techniques for document objects stored on computer networks, while generally executed at the high speeds of modern computer systems, are increasingly imprecise and often much too broad, as well as time and labor intensive, owing to the explosion of information being added to those networks.
- A need exists to enhance the network user's information browsing experience. A need exists to provide network users with information relevant to the individual document object they are accessing and provide that information in a context of value to them by relating the document object they are accessing to link references to other document objects within a specific context. Such other document objects may or may not be offered by the publisher of the document object currently accessed. A need exists to provide network users with information relevant to the specific information the user may be searching for and relevant to the user's immediate personal, professional, geographic and other interests.
- A need exists for entities or groups to be able to communicate information to their employees or members as those employees or members access document objects on a network, and to enable those employees or members to view content deemed important to the entities or groups. A need further exists for publishers of content on the Internet to be able to personalize content presented to Internet users without requiring the establishment of a personal relationship between the user and the content publisher. A need exists to enable the collection of the search experiences of a group of users and share that experience with other users of networked information devices.
- The systems, apparatus and methods of the present invention (hereinafter “Linkspace”) incorporate and provide many improvements on existing methods for publishing, distributing, relating and searching document objects on computer networks, including the Internet.
- Linkspace operates to provide many beneficial improvements in searching, identifying and publishing information over computer networks.
- Linkspace permits a user of a computer network or the Internet to establish relationships between document objects located on the network or the Internet. Those relationships may comprise link relationships and link references and are maintained by Linkspace in one or more link directories. The contents of link directories may be organized, categorized, sorted and filtered in groupings based on various criteria relating to, among other things, user interests and attributes, the types of document objects and the nature of the content of those document objects. Linkspace allows a network user to be presented with a selection of links to document objects related to the document object the user is currently accessing based upon the URL of the current document object, and link relationships created by the user and other users of the network stored in the link directories.
- When a network user equipped with Linkspace identifies and locates a first document object on the network that is of interest to her, she may initiate one method of the present invention to mark the location, through its URL, as a start point of a link relationship. When she accesses a second document object on the network that she considers relevant to the first document object, she initiates another step of one method of the invention to mark the second document object as an end point of the link relationship. Upon marking the second document object as the end point, the link relationship is created and stored on a link directory selected to store similar link relationships. When a second network user equipped with Linkspace, and with access to the link directory, accesses the first document object, he is then presented with a link to the second document object as a relevant document object that may be of interest to him. Likewise, if the second network user accesses the second document object, he may then be presented with a link to the first document object as a relevant document object that may be of interest to him.
- Linkspace consists primarily of a system and method for creating and publishing link relationships, a system and method for storing and managing link relationships in link directories, and a system and method for presenting a network user with links related by link relationships to the document object the user is currently accessing.
- In one respect what is described is a method for enabling users of a network to create, store, and provide access to relationships between document objects stored on the network. The method may include the steps for allowing a user of the network to create a link relationship between a first document object and a second document object; for storing the link relationship in one or more link directories; and for providing all users of the network access to the link relationships stored in the one or more link directories based upon the document object currently accessed by the users.
- In another respect what is described is a system for establishing and providing access to relationships between document objects stored on a network wherein the relationship between a first document object and a second document object may be created by an individual user of the network and provided to other users of the network. The system may include one or more client devices that access document objects stored on the network and create link relationships between a first document object and a second document object; and one or more servers that store and filter the link relationships created by the client devices and transmit one or more link relationships and link references to the client devices.
- In yet another respect, what is described is a computer readable medium on which is embedded a program. The embedded program comprises modules that execute the above method.
- Those skilled in the art will appreciate these and other advantages and benefits of various embodiments of the invention upon reading the following detailed description of a preferred embodiment with reference to the below-listed drawings.
- The detailed description will refer to the following drawings, wherein like numerals refer to like elements, and wherein:
-
FIG. 1 is a diagram showing a system according to one embodiment of the invention; -
FIG. 2 is a diagram showing a client device which is Linkspace-enabled and its interaction with other hardware and software; -
FIG. 3 a is a diagram showing the components of a server which is Linkspace-enabled and its interaction with other hardware and software; -
FIG. 3 b is a diagram showing more detail of one embodiment of a user data store fromFIG. 3 a; -
FIG. 4 a is a diagram illustrating one embodiment of a link directory according to one embodiment of the invention; -
FIG. 4 b is a diagram illustrating another embodiment of a link directory according to one embodiment of the invention; -
FIG. 5 is a diagram showing one embodiment of the invention implemented on public, private or closed computer networks; -
FIG. 6 is a flowchart illustrating a method according to one embodiment of the invention; -
FIG. 7 is a flowchart illustrating a method for, identifying link relationships between document objects according to one embodiment of the invention; -
FIG. 8 is a flowchart illustrating a method for publishing link relationships between document objects according to one embodiment of the invention; -
FIG. 9 is one example screen view of a user interface for a relate links dialog box according to one embodiment of the invention; and -
FIG. 10 is an example of a screen view for a client user interface according to one embodiment of the invention. -
FIG. 1 shows one embodiment of a system 100 for collecting, storing, managing and providing to network users categorized information related to an open document object. A document object may contain any form of information, including text documents and articles, financial data, statistical information, electronic mail, images and photos, music, voice data, animation, and even motion pictures. The system 100 includes anetwork 10, such as the Internet or other network of interconnected computers or a combination of networks and the Internet; one or more Linkspace-enabledclient devices 20; one or more Linkspace-enabledservers 30, one or morefirst document objects 40; one or moresecond document objects 50; one ormore link references first document objects 40 and thesecond document objects 50 respectively; and one ormore link relationships 45. The system 100 may also include one ormore links first document objects 40 andsecond document objects 50 respectively. Theclient devices 20, as well as theserver 30, are preferably Linkspace-enabled. Theclient device 20 may comprise a computer or other digital information device running software enabled by the present invention to create, filter, sort and display the link references 42, 52, and thelink relationships 45. Theserver 30 may comprise a server computer or other digital information device running software enabling the present invention to store, index, search, filter, sort and transmit the link references 42, 52, and thelink relationships 45 toclient devices 20. Theserver 30 further comprises one ormore link directories 35 for storing and indexing information regarding thelink relationships 45 and link references 42 and 52 developed by theclient devices 20 with respect to the one or morefirst documents 40 andsecond documents 50. - The
link reference document object network 10 and attributes associated with thatdocument object link relationship 45 comprises two pointers, one each to thefirst document object 40 and to thesecond document object 50, and attributes describing characteristics of the relationship between the two document objects 40, 50 related by thelink relationship 45. The pointers included in alink relationship 45 may be comprised of pointers to alink reference link relationship 45 establishes a meaningful relationship between two document objects 40, 50, whereas the locations of the document objects 40, 50 may be maintained within the Linkspace system 100 by means of the link references 42, 52. - The system 100 shown in
FIG. 1 operates to create andstore link relationships 45. The system 100 creates and stores linkrelationships 45 between afirst document object 40 and asecond document object 50, preferably on one ormore servers 30 in one ormore link directories 35 in the manner described as follows. Theclient device 20 is enabled by means of software or other devices to request, access and display document objects on thenetwork 10. When the user of aclient device 20 identifies onefirst document object 40 of interest to her that she wishes to associate with asecond document object 50, she utilizes the software running on the Linkspace-enabledclient device 20 to create alink relationship 45 between thefirst document object 40 and thesecond document object 50. Thislink relationship 45 is then stored on theserver 30 in alink directory 35. - In an alternate embodiment, the system 100 may operate to perform the functions described above, including the creation of
link relationships 45 and link references 42, 52, the storing oflink relationships 45 and link references 42, 52, and providing access to and retrieval oflink relationships 45 and link references 42, 52, by means of automated procedures requiring little or no user interaction. - When a
client device 20 later requests and accesses afirst document object 40 for which theserver 30 has stored an associatedlink relationship 45 in one ormore link directories 35, theserver 30 delivers to theclient device 20 the link references 42 and thelink relationships 45, along with contextual information, or attributes, associated with the link references 42 and thelink relationships 45. Theclient device 20 then displays to the user of theclient device 20 the existence of alink relationship 45 between thefirst document object 40 being accessed by theclient device 20 and thesecond document object 50. This enables the user of theclient device 20 to be made aware of thesecond document object 50, the context of thesecond document object 50, and the context of the relationship between thesecond document object 50 and thefirst document object 40 as that relationship may be of interest to the user of theclient device 20 while viewing thefirst document object 40. - Each
link relationship 45 may also operate in the reverse direction. In this manner, when a user of theclient device 20 is accessing thesecond document object 50 for which an associatedlink relationship 45 is stored in the one ormore link directories 35 on theserver 30, theserver 30 then transmits the link references 42 and thelink relationships 45, with contextual information, to theclient device 20. This enables display of the availability of the relatedfirst document object 40 to the user of theclient device 20 with the context of thefirst document object 40, and within the context of its relationship to the displayedsecond document object 50. - While the system 100 is generally described as having enabling software resident on the
client device 20 and on theserver 30, various other software configurations are possible, including having all of the software resident at either the server 30 (making theclient device 20 essentially a “dumb terminal”) or at the client device 20 (making theclient device 20 essentially perform server functions), or various software sharing arrangements. For example, theclient device 20 may include the one ormore link directories 35, a communications module (described later in reference toFIG. 3 a), and a user data store that may maintain information regarding authorized users of the client device 20 (described later in reference toFIGS. 2 , 3 a, and 3 b). -
FIG. 2 is a diagram showing an example of the components of a Linkspace-enabledclient device 20 and its interaction with other software and hardware. Theclient device 20 preferably includes arendering tool 210, such as a web page browser like Microsoft® Internet Explorer, for rendering document objects located on thenetwork 10 and displaying those document objects to users of theclient device 20; aclient tool 220, for allowing the user of theclient device 20 to create and accesslink relationships 45 between document objects; and anetwork access tool 240, such as a TCP/IP stack or other interface, for allowing software modules on theclient device 20 to connect to and communicate with other devices and document objects on thenetwork 10. Theclient device 20 operates primarily to create andpresent link relationships 45 to users. - The
rendering tool 210 may store a documentobject URL address 215 for referring to the document object currently being accessed and rendered by therendering tool 210. Therendering tool 210 may also include a Graphic User Interface (“GUI”)display 218, or other type of display, for displaying the document objects accessed and rendered by therendering tool 210. In alternate embodiments of the invention, theclient device 20 may include more than onerendering tool 210 enabling the user of theclient device 20 to access multiple document objects. - The
client tool 220 may include aclient GUI display 225, or other display software and hardware, for displaying link references 42, 52 andlink relationships 45 to the user of theclient device 20. Typically, the displayed link references 42, 52 andlink relationships 45 would be those link references 42, 52 andlink relationships 45 relevant to the document object currently being rendered and displayed by the rendering tool 210 (as determined by the documentobject URL address 215 in the rendering tool 210). Theclient tool 220 may also include Linkspaceuser profile data 230 for storing information about the user of theclient device 20, thelink directories 35 the user may have access to, and the attributes of link references 42, 52, and attributes oflink relationships 45 that the user may be interested in. The Linkspaceuser profile data 230 may also or alternatively be stored on the one ormore servers 30, along with the Linkspaceuser profile data 230 of all other users of the system 100. - An example of how the
client device 20 operates to create andpresent link relationships 45 to users of theclient device 20 follows. While thenetwork access tool 240 is active and placing theclient device 20 in communication with thenetwork 10, the user enables therendering tool 210 and theclient tool 220. The user may then request and access document objects stored on thenetwork 10 by means of therendering tool 210. Through theGUI display 218, the users enters or otherwise selects a documentobject URL address 215 associated with thefirst document object 40 of interest to the user. Theclient tool 220 connects to and uses therendering tool 210 and accesses the documentobject URL address 215 associated with thefirst document object 40. Theclient tool 220 then establishes contact with theserver 30 and passes to theserver 30 the stored documentobject URL address 215 associated with thefirst document object 40, along with any relevant information that may come from the Linkspaceuser profile data 230. The connection to theserver 30 may be initiated through thenetwork access tool 240 or by other means not utilizing thenetwork access tool 240. - The Linkspace-enabled
server 30 searches thelink directories 35 for any URLs in the link references 42, 52 matching, or similar to, the documentobject URL address 215. After searching, theserver 30 retrieves the one ormore link relationships 45 that include the documentobject URL address 215. Prior to searching, the URLs may be stripped of any information not relevant to the location of thedocument object network 10. Such information not relevant to the location of thedocument object - The
server 30 then determines the link references 42, 52 which may be of interest to the user of theclient device 20 by filtering the retrieved link references 42, 52 using the Linkspaceuser profile data 230 and the attributes assigned to the link references 42, 52 and to thelink relationships 45. The filtering of link references 42, 52 andlink relationships 45 may be accomplished by one of several methods of filtering data including matching, character and Boolean comparing, and other data comparison and filtering methods. Theserver 30 then transmits to theclient tool 220 the filtered link references 42, 52 included in the one ormore link relationships 45. Theclient tool 220 presents the transmitted link references 42, 52 within the context established by thelink relationships 45 by means of theclient GUI display 225. - To create a
new link relationship 45, the user of theclient device 20 must select afirst document object 40 to begin the link relationship, asecond document object 50 to complete thelink relationship 45, and assign attributes to the link references 42, 52 and thelink relationship 45 between the two document objects 40, 50. To select afirst document object 40 to begin thenew link relationship 45, the user interacts with theclient GUI display 225 to activate a function of theclient tool 220 to capture the documentobject URL address 215 associated with thefirst document object 40. To select asecond document object 50 to complete thenew link relationship 45, the user may interact with theGUI display 218 of therendering tool 210 to request, access and display thesecond document object 50. The user may then interact with theclient GUI display 225 again to activate a further function of theclient tool 220 to capture the documentobject URL address 215 associated with thesecond document object 50, completing the selection of document objects 40, 50 participating in thenew link relationship 45. Once the two document objects 40, 50 are established, attributes of the link references 42, 52 and thenew link relationship 45 may be assigned. - The user may select or otherwise specify attributes associated with the link references 42, 52 and
link relationship 45. These attributes aid in categorizing, sorting or filtering the link references 42, 52 and thelink relationship 45 in thelink directories 35 for delivery toother client devices 20. The attributes may be, for example, descriptive, temporal, spatial, or quantitative in nature, i.e., describe the link reference in terms of who or what, when, where, or how much. One such attribute (not shown) may be a plain language name for thelink reference object URL address 215. Other examples of attributes may include description of the content of either of the document objects 40, 50 related by thelink relationship 45, wherein that content may be described to include a product review, news article, product information page, competitor's product information, or product order forms, among other types of content. - Normally, upon completion of the endpoint capturing and attribute assignment functions, the
client tool 220 connects to theserver 30 to store the link references and thenew link relationship 45 in theappropriate link directory 35. Generally, thenew link relationship 45 is then made available to other users. Typically,other client devices 20 who have access to theserver 30 and are assigned access privileges on thelink directory 35 in which thenew link relationship 45 has been stored are given access to thenew link relationship 45. - Furthermore, if the user of the
client device 20 determines that there is a relationship that is not already described by the transmittedlink relationships 45 between the currently accesseddocument object 40 and asecond document object 50, the user may proceed to create and publish anew link relationship 45 between the first document object 40 (currently accessed and displayed by the rendering tool 210) and thesecond document object 50. This may be accomplished without displaying thesecond document object 50. -
FIG. 3 a is a diagram showing the components of the Linkspace-enabledserver 30 and its interaction with other hardware and software. Theserver 30 includes afirst link directory 35, a user data store 370, and aserver manager 380. Theserver 30 may also include asecond link directory 310 and one or moreNth link directories 320. Theserver manager 380 coordinates communications between the other components of theserver 30. Theserver manager 380 also coordinates communications with outside objects, including the one ormore client devices 20. Theserver manager 380 also performs the function of locatingappropriate link directories client device 20. The user of theclient device 20 may request that theserver manager 380 look in alllink directories specific link directory client device 20. The user data store 370 stores identification and user profile data regarding users authorized to access theserver 30, which of theseveral link directories link directories link directories -
FIG. 3 a also shows one or more alternate Linkspace-enabledservers 350 that may reside on thenetwork 10. In alternate embodiments of the system of the invention, the one or morealternate servers 350 may be located off thenetwork 10 but otherwise connected to or in communication with theclient devices 20 and/or thefirst server 30. One or morealternate link directories 360 may reside on the one or morealternate servers 350. The one or morealternate servers 350 may include other elements duplicating the functions of theserver manager 380 and user data store 370, as well asadditional link directories alternate servers 350 provides for flexibility in the distribution of link directory data across several servers, redundancy and interoperability across multiple networks and/or sets ofclient devices 20 and users of the Linkspace system 100. - Each of the
several link directories link relationships 45. These link references 42, 52 andlink relationships 45 may have attributes matching categories defined by an authorized user designated to managesuch link directories link directory such link directories relationships 45. Attributes may describe the types and properties of the document objects 40, 50 and thelink relationships 45. Any authorized user of thelink directories relationships 45 in thelink directories relationships 45. -
FIG. 3 a further illustrates the provision for afurther link relationship 345 between thesecond document object 50 and athird document object 340. Thelink relationship 345 may be created by an authorized user of one of theclient devices 20, just as thelink relationship 45 between thefirst document object 40 and thesecond document object 50 was created. Thelink relationship 345 may be stored in asecond link directory 310, separated from thelink relationship 45 stored in thefirst link directory 35. As such, thelink relationships first link directory 35 andsecond link directory 310. A user of aclient device 20 who is currently viewing or otherwise accessing thesecond document object 50 will only be presented with thelink relationship 345 if the user is an authorized user of, and thus in the user directory 370 list for, thesecond link directory 310. Furthermore, a user of aclient device 20 who is currently viewing or otherwise accessing thesecond document object 50 will only be presented with both thelink relationship 45 and thelink relationship 345 if the user is an authorized user of, and thus in the user directory 370 lists for, both thefirst link directory 35 and thesecond link directory 310. A user of the Linkspace system may be or may apply to be an authorized user for any combination of or all of thelink directories -
FIG. 3 b is a diagram showing more detail of one embodiment of the user data store 370 fromFIG. 3 a. The user data store 370 may include a user directory 372, a user profile store 375, and a user account store 378. - The user directory 372 includes one or more user data records 374, typically one or more each for every authorized user of the
servers link directories - The user profile store 375 includes one or more user profile records 330, typically one or more each for every authorized user of the
servers - Each user profile 332 may contain data regarding specific, differing configurations of the user's personal, professional, geographic and other interests, and the
servers 30,link directories client tool 220. The data in the user profile 332 may be used to determine whatlink directories link relationships 45, will be considered by theserver 30 in returning the link references 42, 52 and thelink relationships 45 from thelink directories client device 20. - The user account store 378 includes one or more user account records 379, usually one each for every authorized user of the
servers link relationships 45, and the transmissions oflink relationships 45 and link references 42, 52 based upon the document object displayed by theclient tool 220 of each user. In alternate embodiments of the invention, data regarding the document objects 40, 50, 340 requested and accessed by users of the system 100 is not recorded in the user account records 379 against the individual authorized user in order to maintain user privacy with regard to what document objects 40, 50, 340 each individual user may request or access. - When an authorized user of a
client device 20 creates alink relationship 45 that is stored in one or more of thelink directories server manager 380 records in the user account record 379 (associated with the authorized user creating the link relationship 45) the activity of creating and storing alink relationship 45. Each of the authorized users of thelink directories link relationships 45 to be stored in one or more of thelink directories specific link directory link relationships 45 stored in thespecific link directory first document object 40 orsecond document object 50 that the user is currently viewing on the user'sclient device 20. - The interaction of each of the elements of the
server 30,alternate server 350, theclient devices 20, and the first, second and third document objects 40, 50, and 340, along with the creation and presentation of thelink relationships methods FIGS. 6 , 7, and 8. -
FIG. 4 a shows the general structure of one embodiment of thelink directory 35. This embodiment of thelink directory 35 includes a link relationship table 420. - The link relationship table 420 comprises a list of
link relationships relationships link relationships client device 20 as they are stored in thelink directory 35. Thelink relationship 460 comprises afield 462 containing a link reference 42 (L1) including the URL address of thefirst document object 40 related by thelink relationship 460; afield 463 containing a link reference 52 (L2) including the URL address of thesecond document object 50 related by thelink relationship 460; a set of link relationship attributes 465; and adirectional indicator 466 showing the nature of the link relationship between the two document objects, either unidirectional or bi-directional. Thelink relationship 460 is shown with thedirectional indicator 466 specifying that thelink relationship 460 is a unidirectional link relationship. - Some or all of the list of
link relationships server 30 in the form of relational database records. The relational database record corresponding to thelink relationship 460 may be comprised of one or more relational database fields corresponding to the field (L1) 462, field (L2) 463, link relationship attributes 465, anddirectional indicator 466. Each of the one or more relational database fields may be formatted and designated to store various forms of relational database data types. In one embodiment of the invention, the relational database field corresponding to thefield 462, as well as the relational database field corresponding to thefield 463, may contain data specifying the appropriate URL as text or other format appropriate for the network upon which the invention may be implemented. In one embodiment of the invention, the relational database field corresponding to thedirectional indicator 466 may be formatted as a simple flag (i.e., Boolean) data type such as True/False, Yes/No, or On/Off. Alternatively, the relational database field corresponding to thedirectional indicator 466 may be formatted as a type to allow entry of a value indicating whether thelink relationship attribute 465 applies forward, backward or in both directions across thelink relationship 460. In one embodiment of the invention, the link relationship attributes 465 may be represented by one or more relational database fields. In this embodiment, the relational database fields comprising the link relationship attributes 465 may include a field of text data listing the assigned titles of the one or more specific link relationship attributes assigned to thelink relationship 460. The relational database fields comprising the link relationship attributes 465 may then also include one or more attribute value fields containing data formatted appropriately for the corresponding link relationship attribute listed in the above described field of text data. For example, the plain language name link relationship attribute may have its corresponding value stored in a field formatted as text, whereas a zip code attribute may have its corresponding value stored in a field formatted as a 5 or 9 digit integer, and a date attribute may have its corresponding value stored in a field formatted in a date format. In an alternative embodiment, the relational database fields comprising the link relationship attributes 465 may utilize relational database key fields which point to additional database tables containing the records specifying each available type of link relationship attribute for thelink relationship 460 and key fields which point to additional tables containing the values associated with each of link relationship attribute identified by a key. - As with the
link relationship 460, thelink relationship 470 comprises afield 472 containing a link reference 42 (L1) including the URL address of thefirst document object 40 related by thelink relationship 470; afield 473 containing a third link reference (L3) including the URL address of thethird document object 340 related by thelink relationship 470; a set of link relationship attributes 475; and adirectional indicator 476 showing the nature of the link relationship between the two document objects, either unidirectional or bi-directional. Thelink relationship 470 is shown with thedirectional indicator 476 specifying that thelink relationship 470 is a bi-directional link relationship. Thelink relationship 480 comprises afield 482 containing a link reference 52 (L2) including the URL address of thesecond document object 50 related by thelink relationship 480; afield 483 containing the third link reference (L3) including the URL address of thethird document object 340 related by thelink relationship 480; a set of link relationship attributes 485; and adirectional indicator 486 showing the nature of the link relationship between the two document objects, either unidirectional or bi-directional. Thelink relationship 480 is shown with thedirectional indicator 486 specifying that thelink relationship 480 is a bi-directional link relationship. - The
link relationship 490 comprises afield 492 containing a link reference 52 (L2) including the URL address of thesecond document object 50 related by thelink relationship 490; afield 493 containing a link reference 42 (L1) including the URL address of thefirst document object 40 related by thelink relationship 490; a set of link relationship attributes 495; and adirectional indicator 496 showing the nature of the link relationship between the two document objects, either directional or bi-directional. Thelink relationship 490 is shown with thedirectional indicator 496 specifying that thelink relationship 490 is a unidirectional link relationship. - The link relationship attributes 465, 475, 485, 495 may include a plain language name (not shown) associated with each of the link references 42, 52 participating in the
respective link relationship client tool 220. The plain language name serves to describe thelink reference link reference link relationship - The
link relationship 470 may have a value assigned to thedirectional indicator 476 specifying that thelink relationship 470 is a bi-directional link relationship. This indicates that the link relationship attributes 475 apply to either of the two document objects (40 and 340) equally in the context of thelink relationship 470. - The
link relationship 460 may, on the other hand, have a value assigned to thedirection indicator 466 specifying that thelink relationship 460 is a unidirectional link relationship. This signifies that the link relationship attributes 465 apply in only one direction between the two document objects 40 and 50 represented in thefields client device 20 when requested in the direction opposite to that specified by thedirection indicator 466. In the case of thelink relationship 460 shown inFIG. 4 a, theattributes 465 apply only as thelink relationship 460 is traversed from thefirst link reference 42 to thesecond link reference 52, and not in the reverse direction. In a similar manner, thelink relationship 490 may have a value assigned to thedirection indicator 496 specifying that thelink relationship 490 is a unidirectional link relationship. This signifies that the link relationship attributes 495 apply in only one direction between the two document objects 50 and 40 represented in thefields link relationship 490 shown inFIG. 4 a, theattributes 495 apply only as thelink relationship 490 is traversed from thesecond link reference 52 to thefirst link reference 42, and not in the reverse direction. In this instance, a link relationship will not be transmitted and presented to the user of theclient device 20 when requested in the direction opposite to that specified by thedirection indicator 496. - In an alternate embodiment, the
direction indicator 466 of thelink relationship 460 may comprise a plurality of directional indicator fields (not shown). Each directional indicator field may then correspond to one of the one or more link relationship attributes 465 and indicate whether the correspondinglink relationship attribute 465 may apply in one direction or in both directions between the two document objects 40 and 50 represented in thefields direction indicator 496 of thelink relationship 490 may comprise a plurality of directional indicator fields (not shown). Each directional indicator field may then correspond to one of the one or more link relationship attributes 495 and indicate whether the correspondinglink relationship attribute 495 may apply in one direction or in both directions between the two document objects 50 and 40 represented in thefields direction indicators link relationships -
FIG. 4 b shows the general structure of another embodiment of thelink directory 35. This embodiment of thelink directory 35 includes a document object table 410, and a link relationship table 420, as described above forFIG. 4 a. - The document object table 410 comprises a set of link references 430, 440, 450 to document objects located on the
network 10 to which thelink directory 35 is connected. Eachlink reference URL respective document object URL list link relationships link relationship direction indicator link relationship link relationship list link reference unidirectional link relationship FIG. 4 b correspond to the link references 42, 52, and the third link reference (not shown), as described inFIGS. 1-4 a above, and which point to the URL addresses of the document objects 40, 50, and 340 respectively. - The document object attributes 435, 445, 455 serve to describe the link references 430, 440, 450 in terms useful to users of the system 100, and to place the link references 430, 440, 450 in a context that may attract users to select the link references 430, 440, 450. The document object attributes 435, 445, 455 may include a plain language name that serves to describe the
document object document object link references document object - The link references 430, 440, and 450 may be created and placed in the document object table 410 when a user of the
client device 20 creates alink relationship 45 between afirst document object 40 and asecond document object 50 or athird document object 340. - The link relationship table 420 shown in
FIG. 4 b comprises the same list oflink relationships FIG. 4 a. InFIG. 4 b, thelink relationship 460 comprises afield 462 containing a pointer to thelink reference 430 for thefirst document object 40 related by thelink relationship 460; afield 463 containing a pointer to thelink reference 440 for thesecond document object 50 related by thelink relationship 460; the link relationship attributes 465; and thedirectional indicator 466. InFIG. 4 b, thelink relationship 470 comprises afield 472 containing a pointer to thelink reference 430 for thefirst document object 40 related by thelink relationship 470; afield 473 containing a pointer to thelink reference 450 for thethird document object 340 related by thelink relationship 470; the link relationship attributes 475; and thedirectional indicator 476. InFIG. 4 b,link relationship 480 comprises afield 482 containing a pointer to thelink reference 440 for thesecond document object 50 related by thelink relationship 480; afield 483 containing a pointer to thelink reference 450 for thethird document object 340 related by thelink relationship 480; the link relationship attributes 485; and thedirectional indicator 486. Likewise, inFIG. 4 b, thelink relationship 490 comprises afield 492 containing a pointer to thelink reference 440 for thesecond document object 50 related by thelink relationship 490; afield 493 containing a pointer to thelink reference 430 for thefirst document object 40 related by thelink relationship 490; the link relationship attributes 495; and thedirectional indicator 496. -
FIG. 5 illustrates one embodiment of the present invention in which the invention may operate on multiple networks of varying degrees of network security. The different networks on which the systems and methods of the present invention may be implemented include a public network such as theInternet 510, aprivate network 520 that may be connected to theInternet 510, and aclosed network 530 that is secure and not accessible to users not connected to theclosed network 530. Theclosed network 530 is not connected to any public network such as theInternet 510, and is not connected to anotherprivate network 520. - The public network or
Internet 510 may have components connected to it that implement the present invention, including one or more Linkspace-enabled client users 511, one ormore link directories 512, one or more Linkspace-hostedcontent units 513, and one or morenetworked content units 514. Thelink directories 512 described here are functionally equivalent to thelink directories FIGS. 1 , 2 and 3 a. The Linkspace-hostedcontent units 513 comprise information storage devices connected to thenetwork 510 that provide additional document object storage facilities to users of the Linkspace system 100 separate from the publicly or privately operatednetworked content units 514. Thenetworked content units 514 may include networked data servers or web servers. - The Linkspace-hosted
content units 513 are provided to accommodate the streamlined publication and/or distribution of content by users of the Linkspace system 100. Theclient tool 220 may allow a user of the Linkspace system 100 to store document objects of his or her own creation through a simplified procedure, i.e., a publish document function enabled through theclient GUI display 225. The user of theclient device 20 may select adocument object 40 that she wishes to publish through the Linkspace-hostedcontent units 513, or she may create a document object (not shown) using therendering tool 210 or other document object creation tool. The user of theclient device 20 then selects the publish document function through theclient GUI display 225 and selects thelink directories new link relationships client device 20 may then create and publishlink relationships client tool 220 may automatically upload the user created or selected document object from the user'sclient device 20, or from another location on the network, in this case theInternet 510, and save it on the Linkspace-hostedcontent unit 513. Theclient tool 220 may then publish thenew link relationships appropriate link directory new link relationships - Similarly, the
private network 520 may have connected to it components that implement the present invention, including one or more Linkspace-enabled client users 521, one ormore link directories 522, one or more Linkspace-hostedcontent units 523, and one or morenetworked content units 524. - Additionally, the
closed network 530 may have connected to it components that implement the present invention, including one or more Linkspace-enabled client users 531, one ormore link directories 532, one or more Linkspace-hostedcontent units 533, and one or morenetworked content units 534. - In
FIG. 5 , theprivate network 520 is shown connected to the public network orInternet 510. This may allow Linkspace-enabled client users 521 connected to theprivate network 520 to also be permitted access to any of the one ormore link directories 512, Linkspace-hostedcontent units 513, andnetworked content units 514 that are connected to the public network orInternet 510. However, Linkspace-enabled client users 511 connected to the public network orInternet 510 that are not also among the group of authorized Linkspace-enabled client users 521 of theprivate network 520, may not be permitted to access the one ormore link directories 522, Linkspace-hostedcontent units 523, andnetworked content units 524 that are connected to theprivate network 520. - A Linkspace client user 531 connected to the
closed network 530, and therefore not connected to either the public network orInternet 510 nor to theprivate network 520, may only be permitted access to the one ormore link directories 532, Linkspace-hostedcontent units 533, andnetworked content units 534 that are connected to theclosed network 530. -
FIG. 6 is a flowchart showing the steps of amethod 600 according to one embodiment of the present invention. Themethod 600 includes the steps of a first user (not shown) of aclient device 20 locating a first document object 40 (step 610); the first user locating a second document object 50 (step 620); and the first user creating alink relationship 45 between thefirst document object 40 and the second document object 50 (step 630). Themethod 600 includes the additional steps of storing thelink relationship 45 created by the first user in a link directory 35 (step 640); and providing access to thelink directory 35 to a second user (not shown) of another client device 20 (step 650). - The
method 600 may include a step for providing authorized users ofclient devices 20 access to thelink relationships 45 stored inlink directories 35, based upon thedocument object 40 currently accessed by the users on the users' client device 20 (step 660). -
FIG. 7 is a flowchart showing the steps of amethod 700 for accessing and displaying link relationships and related document objects on a network according to one embodiment of the present invention. Themethod 700 initiates when a user of aclient device 20 engages therendering tool 210 to request, access and display a document object 40 (step 710). The user of theclient device 20 then engages theclient tool 220 and is authenticated by a server 30 (step 715). The user of theclient device 20 then selects a user profile 332 (step 717) that has been returned to theclient device 20 upon authentication of the user by theserver 30 instep 715. The selected user profile 332 may be used to determine what attributes of thelink relationships 45 will be applied to filter and sort the link references 430, 440, 450 and linkrelationships server 30. By filtering and sorting using attributes, a manageable and meaningful group of relevant link references 430, 440, 450 may be displayed to the user based on the user's needs and interests. - In alternate embodiments of the
method 700, thesteps step 710. - With the user profile 332 selected and the
document object 40 displayed, the user then selects aclient tool 220 function (step 720). The first function that the user may select is to enter adocument object URL 215 into therendering tool 210, whereupon thatdocument object URL 215 is captured by theclient tool 220 and transmitted to the servers 30 (step 730). The activity of transmitting thedocument object URL 215 to theservers 30 by theclient tool 220 may be recorded and stored in an appropriate location within the user data store 370. - The
server 30 then processes the transmitteddocument object URL 215 across thevarious link directories 35 to which the user is authorized access. One method of processing by theserver 30 is according to the following steps. Theserver 30 performs a search of the document object tables 410 of alllink directories 35 to find all instances of the document object URL 215 (step 735). Theserver 30 then searches the Link relationship tables 420 in thelink directories 35 where theURL 215 was found. This search by theserver 30 locates alllink relationships URL 215 as one of the pointers to linkreferences link relationship server 30 then accumulates all theURLs link relationships step 740, to theURL 215. Theserver 30 also accumulates the document object attributes 435, 445, 455 associated with the identifiedURLs link relationships - The accumulated
URLs method 700, the accumulatedURLs URLs URLs client device 20 that transmitted theURL 215, along with the associated document object attributes 435, 445, 455, and associated link relationship attributes 465, 475, 485, 495 (step 760). The activity of transmitting the filteredURLs client device 20 may be recorded and stored in an appropriate location within the user data store 370. Alternatively, the first filtering steps 750, 755 may be performed by theclient device 20. - The
client tool 220, upon receiving the filteredURLs server 30, may further filter and sort the returnedURLs URLs server 30 or theclient tool 20. - The filtered and sorted
URLs client device 20 by theclient GUI display 225 and theclient tool 220 alerts the user of theclient device 20 to the availability of related links (in the form of the returnedURLs method 700 then returns to step 720 to await further action by the user of theclient device 20. - If, at
step 720, the user of theclient device 20 selects one of the URL links 432, 442, 452 displayed by the Linkspace GUI display as being related bylink relationships document object 40 with the URL 215 (step 780), therendering tool 210 then accesses thenew document object 50 associated with the selected URL and displays that documentobject 50 in theGUI display 218 of the rendering tool 210 (step 785). The new documentobject URL address 215 of the selecteddocument object 50 is then passed on to the servers 30 (step 790) and themethod 700 continues withstep 735, as above, using theURL 215 of thenew document object 50 as the URL to search for. -
FIG. 8 is a flowchart showing the steps of amethod 800 for creating and publishing link relationships according to one embodiment of the present invention. Themethod 800 initiates when a user of theclient device 20 engages theclient tool 220 and is authenticated by a server 30 (step 810). The user of theclient device 20 may then select a publish link relationship function of the client tool 220 (step 815). - The user of the
client device 20 may then navigate, using therendering tool 210, to thefirst document object 40 of thenew link relationship 45 that the user of theclient device 20 wishes to create and publish. The user may then select a declare first link function of the client tool 220 (step 820). The user of theclient device 20 may then navigate, again using therendering tool 210, to thesecond document object 50 that the user of theclient device 20 wishes to associate by means of alink relationship 45 with thefirst document object 40. The user can then select the declare second link function of the client tool 220 (step 825). The user of theclient device 20 has now selected both ends of alink relationship 45. - The user now may select which of the
link directories 35 in which the user wishes to publish the new link relationship 45 (step 830). The user of theclient device 20 may then further assign link relationship attributes, such as those shown inFIG. 4 (465, 475, 485, 495) to thelink relationship 45, along with assigning any document object attributes, such as those shown inFIG. 4 (435, 445, 455), to thefirst document object 40 andsecond document object 50 of the link relationship 45 (step 835). The user may then interact with aLinkspace GUI 225 button or element to complete the link relationship publish function (step 840). Upon completion of the link relationship publish function on the client device, the URLs and document object attributes of the document objects 40 and 50 associated by thenew link relationship 45 are stored in the document object table 410 in the selected link directory 35 (step 850). Additionally, thenew link relationship 45, along with the URL references to thefirst document object 40 andsecond document object 50 and the link relationship attributes, such as those shown inFIG. 4 (465, 475, 485, 495), are stored in the link relationship table 420 in the selected link directory 35 (step 855). Themethod 800 for creating and publishing link relationships completes by recording the publishing activity to the user account record 379 associated with the user of theclient device 20 for later tracking and billing purposes (step 880). -
FIG. 9 is an example of a user interface, more specifically, a screen view of a user interface for a relatelinks dialog box 900, one element of the user interface of one embodiment of the invention. The relatelinks dialog box 900 is invoked when a user of theclient tool 220 engages the publish link relationship function of theclient tool 220. In the embodiment shown inFIG. 9 , the relatelinks dialog box 900 includes a drop downlist 910 for selecting a community of interest, a user interface term referring to one of the one ormore link directories 35, and acheckbox 915 for indicating whether thelink relationship 45 being created is to operate bi-directionally or unidirectionally. If thecheckbox 915 is checked, then thelink relationship 45 being created will only apply in one direction. In the example illustrated inFIG. 9 , the user has selected the community of interest (link directory 35) referred to as “Wireless Washington,” alink directory 35 storing link references 42, 52 andlink relationships 45 considered by their creators as relevant to wireless device users in the Washington, D.C. metropolitan area. - The relate
links dialog box 900 further includes a link-fromsection 920, a link-tosection 930, a link relationship attributesdisplay box 970, a submit link relationship button 980 and a cancel button 985. The submit link relationship button 980 is selected by the user when the user has selected and/or entered all information associated with the link references 42, 52 and thelink relationship 45 that the user wishes to publish. Upon selection of the submit link relationship button 980, theclient tool 220 closes the relatelinks dialog box 900 and transmits the information associated with the createdlink relationship 45 to one of the one ormore servers 30. The cancel button 985 may be selected by the user to abort the creation and publication of thelink relationship 45 that the user initiated and to close the relatelinks dialog box 900. - In the embodiment shown in
FIG. 9 , the link-fromsection 920 may include a firstdocument object URL 922 associated with thefirst document object 40 included in thelink relationship 45 being created, where the firstdocument object URL 922 was captured when the publish link relationship function was engaged; a first plainlanguage name field 925; and a listing of first link reference attributes 940 and the attribute values 942 associated with those first link reference attributes 940. In the example illustrated byFIG. 9 , the firstdocument object URL 922 is the address of afirst document object 40 that is a web page for a coffee and dessert shop. The first plainlanguage name field 925 may be captured when the publish link relationship function was engaged and/or may be edited by the user creating thelink relationship 45. An exemplary first link reference attribute forfood 945, and the value ofspecialty foods 947 assigned to the firstlink reference attribute 945 by the user creating thelink relationship 45, are also shown. - The link-to
section 930 similarly may include a seconddocument object URL 932 associated with thesecond document object 50 included in thelink relationship 45 being created, where the seconddocument object URL 932 was captured when the publish link relationship function was engaged; a second plainlanguage name field 935; and a listing of second link reference attributes 950 and the attribute values 952 associated with those second link reference attributes 950. In the example illustrated byFIG. 9 , the seconddocument object URL 932 is the address of asecond document object 40 that is a web page for a “LinkSpace Restaurant” located in McLean, Virginia (a suburb of Washington). The second plainlanguage name field 935 may be captured when the publish link relationship function was engaged and/or may be edited by the user creating thelink relationship 45. An exemplary second link reference attribute forlocation 955, and the value ofaddress 995 assigned to the secondlink reference attribute 955 by the user creating thelink relationship 45, are also shown. In addition, in the example illustrated byFIG. 9 , a subordinate attribute forcity 957, subordinate under the attribute forlocation 955, and a value ofaddress 995 along with the assigned value ofMcLean 958 for the subordinate attribute forcity 957, are also shown in the link-tosection 930. Further subordinate attributes may include astreet 956 with avalue 959 of 12345 Main Street. - The link relationship attributes
display box 970, as shown for the embodiment illustrated byFIG. 9 , includes a list of link relationship attributes 972 and a delete linkrelationship attribute button 975. Thelink relationships 972 are formed by pairs of first link reference attributes 940 and second link reference attributes 950 that the user creating thelink relationship 45 has selected to describe the nature of thelink relationship 45. These link relationship attributes 972 may form the link relationship attributes 465, 475, 485, 495 described inFIG. 4 a. The delete linkrelationship attribute button 975 may be used to delete a selectedlink relationship attribute 972 displayed in the link relationship attributesdisplay box 970. - The exemplary
link relationship attribute 972 shown inFIG. 9 indicates that the user creating thelink relationship 45 has declared that the city subordinate attribute 957 (one selected second link reference attribute 950) of the Linkspace Restaurant associated with thesecond document object 50, having a value ofMcLean 958, is related to the food attribute 945 (one selected first link reference attribute 940), having a value ofspecialty foods 947, of the coffee shop associated with thefirst document object 40. As a result, once theexemplary link relationship 45 shown inFIG. 9 is created and published, other users of Linkspace-enabledclient devices 20 that request and/or access the Linkspace Restaurant web page may be presented with alink reference reference display window 1020 shown inFIG. 10 . - In one embodiment of the invention, the
link relationship attribute 972 may be declared by the user performing a drag-and-drop operation wherein thelink reference attribute 957 is dragged and dropped onto thelink reference attribute 945, creating thelink relationship attribute 972 which relates the two document objects 40, 50 by the association of the citysubordinate attribute 957 to thefood attribute 945. In an alternate embodiment, the creation and selection of link relationship attributes 972 may be performed in a manner similar to that used in the link-tosection 930 and link-fromsection 920 described above, utilizing a set of link relationship attribute types along with data input fields for entering or otherwise selecting values for those attributes. -
FIG. 10 is an example of a screen view for one embodiment of theclient GUI display 225 for one embodiment of the invention, wherein theclient GUI display 225 is integrated into theGUI display 218 of therendering tool 210. In the embodiment shown inFIG. 10 , aclient toolbar 1010 and a linkreference display window 1020 together comprise theclient GUI display 225. Abrowser window 1030 displays the document object (40, 50) being requested and accessed by therendering tool 210 and having the documentobject URL address 215 displayed in anaddress bar field 1040. - The
client toolbar 1010 includes a number of GUI buttons that initiate various functions of theclient tool 220. Aclient logon button 1050 initiates a connection between theclient tool 220 and one ormore servers 30. Aclient logoff button 1055 ends a user session for theclient tool 220 and disconnects theclient tool 220 from the one ormore servers 30. A mark startingpage button 1060 may be engaged to initiate the publish link relationship function of theclient tool 220 by setting the currently displayeddocument object 40 shown in thebrowser window 1030 and referenced by the documentobject URL address 215 displayed in theaddress bar field 1040 as thefirst document object 40 in thelink relationship 45. After the user navigates to asecond document object 50, a mark endingpage button 1065 may be engaged to complete the selection of participating document objects 40, 50 for the publish link relationship function of theclient tool 220. Engaging the mark endingpage button 1065 sets the newly displayeddocument object 50 shown in thebrowser window 1030 and referenced by the documentobject URL address 215 displayed in theaddress bar field 1040 as thesecond document object 50 in thelink relationship 45, and opens a relate links dialogue box 900 (shown and described inFIG. 9 above) to allow the user of theclient tool 220 to assign attributes to thelink relationship 45. - The
client toolbar 1010 also may include three icons that indicate the availability and type of link references 42, 52 related to thedocument object 40 open in thebrowser window 1030. These icons may include apublisher links indicator 1071, aprivate links indicator 1072, and a community linksindicator 1073. - The link
reference display window 1020 presents the user with a hierarchical listing of any link references 42, 52, delivered by theserver 30, that may be related to thedocument object 40 that is currently displayed in thebrowser window 1030 and has the documentobject URL address 215 shown in theaddress bar field 1040. The linkreference display window 1020 may be presented in a tabbed format, wherein each tab may contain a different set of link references 42, 52 depending on the type of link reference and link relationship involved. In one embodiment of the invention, there may be three different tabs at the top of the linkreference display window 1020, each corresponding to one of the indicator icons (1071, 1072, 1073) in theclient toolbar 1010. The first tab may be aprivate links tab 1074, corresponding to theprivate links indicator 1072. The second tab may be apublisher links tab 1075, corresponding to thepublisher links indicator 1071. The third tab may be acommunity links tab 1076, corresponding to thecommunity links indicator 1073. - The
document object 40 displayed in thebrowser window 1030 inFIG. 10 is a representative web page, in this case for a restaurant named Linkspace. When this page is displayed, and theclient tool 220 is engaged, as indicated by the recessed display of theclient logon button 1050 in theclient toolbar 1010, one or more of the indicator icons (1071, 1072, 1073) in theclient toolbar 1010 will become highlighted if there are any link references 42, 52 available of the corresponding type. - For example, as illustrated in
FIG. 10 , thecommunity links indicator 1073 is highlighted, while thepublisher links indicator 1071 and theprivate links indicator 1072 are grayed out. This indicates that theserver 30 has returned one or more link references 42, 52 that are categorized as community links and has not returned any link references 42, 52 categorized as publisher or private links. The returnedlink references reference display window 1020 under thecommunity links tab 1076. In this case, the link references 42, 52 are displayed in a hierarchical listing underaffinity directory headings link directory 35 on aserver 30, maintaining one set oflink relationships 45 and link references 42, 52, that may include thedocument object 40 displayed in thebrowser window 1030. In addition, under each affinity directory heading 1081, 1082, there may be displayed one ormore attribute folders attribute folder hyperlinks document object 40 displayed in thebrowser window 1030 by a particularlink relationship attribute 972. - In the example shown in
FIG. 10 , affinity directory heading 1082 indicates alink directory 35 focusing on wireless devices in the Washington, D.C. area. Also shown in the example inFIG. 10 , theattribute folder 1091 groups listedhyperlinks 1095 by thelink relationship attribute 972, further relating document objects 40 to specialty food document objects 50. The listedhyperlink 1095, listed under theattribute folder 1091, comprises the text of the plain language name attribute of a document object concerning coffee and dessert after dinner. In this manner, the listedhyperlink 1095, displayed under the affinity directory heading 1082 and theattribute folder 1091, represents alink reference 52 to adocument object 50 that is related, as a document object of interest to wireless device users in the Washington area, and as a specialty food document object, to thedocument object 40, the restaurant web page, displayed in thebrowser window 1030. - The
attribute folder 1092 shown in the example inFIG. 10 groups listedhyperlinks 1096 by thelink relationship attribute 972 further relating documents objects 40 to documentobjects 50 concerning the downtown area of the Washington, D.C. suburb of McLean. The listedhyperlink 1096 is to a LinkNexus document object for the city of McLean. A LinkNexus document object may comprise a listing of further link references 42, 52 to documentobjects FIG. 10 , the LinkNexus document object indicated by the listedhyperlink 1096 may contain link references 42, 52 concerning the suburban city of McLean. In this manner, the listedhyperlink 1096, displayed under the affinity directory heading 1082 and theattribute folder 1092, represents alink reference 52 to adocument object 50 that is related, as a document object of interest to wireless device users in the Washington area, and as a link to content relevant to downtown McLean, to thedocument object 40, the restaurant web page, displayed in thebrowser window 1030. - The affinity directory heading 1081 shown in the example in
FIG. 10 indicates a community related to “Your Company,” the user's company. This affinity directory heading 1081 may contain link references 42, 52 to documentobjects private network 520, accessible to users within the company, but not to the general public, as shown and described inFIG. 5 . - The steps of the
methods - The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. Those skilled in the art will recognize that many variations are possible within the spirit and scope of the invention as defined in the following claims, and their equivalents, in which all terms are to be understood in their broadest possible sense unless otherwise indicated.
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/979,260 US20100023500A1 (en) | 2001-03-07 | 2007-10-31 | System and method for collecting, storing, managing and providing categorized information related to a document object |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US27352001P | 2001-03-07 | 2001-03-07 | |
US28247001P | 2001-04-10 | 2001-04-10 | |
US10/050,515 US7386792B1 (en) | 2001-03-07 | 2002-01-18 | System and method for collecting, storing, managing and providing categorized information related to a document object |
US11/979,260 US20100023500A1 (en) | 2001-03-07 | 2007-10-31 | System and method for collecting, storing, managing and providing categorized information related to a document object |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/050,515 Continuation US7386792B1 (en) | 2001-03-07 | 2002-01-18 | System and method for collecting, storing, managing and providing categorized information related to a document object |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100023500A1 true US20100023500A1 (en) | 2010-01-28 |
Family
ID=37423361
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/050,515 Expired - Fee Related US7386792B1 (en) | 2001-03-07 | 2002-01-18 | System and method for collecting, storing, managing and providing categorized information related to a document object |
US10/090,739 Expired - Fee Related US7139974B1 (en) | 2001-03-07 | 2002-03-06 | Framework for managing document objects stored on a network |
US11/601,645 Expired - Fee Related US8515998B1 (en) | 2001-03-07 | 2006-11-20 | Framework for managing document objects stored on a network |
US11/979,260 Abandoned US20100023500A1 (en) | 2001-03-07 | 2007-10-31 | System and method for collecting, storing, managing and providing categorized information related to a document object |
US13/432,642 Expired - Fee Related US9128934B2 (en) | 2001-03-07 | 2012-03-28 | User interface for presenting and searching relationships between document objects located on a network |
US13/754,542 Expired - Fee Related US9047386B2 (en) | 2001-03-07 | 2013-01-30 | Creating a link relationship between document objects and storing in a link directory |
US14/015,782 Expired - Fee Related US9218431B2 (en) | 2001-03-07 | 2013-08-30 | System for linked and networked document objects |
US14/968,796 Abandoned US20160154878A1 (en) | 2001-03-07 | 2015-12-14 | System For Linked And Networked Document Objects |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/050,515 Expired - Fee Related US7386792B1 (en) | 2001-03-07 | 2002-01-18 | System and method for collecting, storing, managing and providing categorized information related to a document object |
US10/090,739 Expired - Fee Related US7139974B1 (en) | 2001-03-07 | 2002-03-06 | Framework for managing document objects stored on a network |
US11/601,645 Expired - Fee Related US8515998B1 (en) | 2001-03-07 | 2006-11-20 | Framework for managing document objects stored on a network |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/432,642 Expired - Fee Related US9128934B2 (en) | 2001-03-07 | 2012-03-28 | User interface for presenting and searching relationships between document objects located on a network |
US13/754,542 Expired - Fee Related US9047386B2 (en) | 2001-03-07 | 2013-01-30 | Creating a link relationship between document objects and storing in a link directory |
US14/015,782 Expired - Fee Related US9218431B2 (en) | 2001-03-07 | 2013-08-30 | System for linked and networked document objects |
US14/968,796 Abandoned US20160154878A1 (en) | 2001-03-07 | 2015-12-14 | System For Linked And Networked Document Objects |
Country Status (1)
Country | Link |
---|---|
US (8) | US7386792B1 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110035388A1 (en) * | 2008-01-02 | 2011-02-10 | Samsung Electronics Co., Ltd. | Method and apparatus for recommending information using a hybrid algorithm |
US20120159320A1 (en) * | 2008-03-07 | 2012-06-21 | Mathieu Audet | Method of managing attributes and system of managing same |
US20140173562A1 (en) * | 2012-12-17 | 2014-06-19 | Martina Rothley | Automatic Documentation Generator |
US9588646B2 (en) | 2011-02-01 | 2017-03-07 | 9224-5489 Quebec Inc. | Selection and operations on axes of computer-readable files and groups of axes thereof |
US9690460B2 (en) | 2007-08-22 | 2017-06-27 | 9224-5489 Quebec Inc. | Method and apparatus for identifying user-selectable elements having a commonality thereof |
US20170338693A1 (en) * | 2012-07-31 | 2017-11-23 | Causam Energy, Inc. | System, method, and apparatus for electric power grid and network management of grid elements |
US20170344045A1 (en) * | 2012-07-31 | 2017-11-30 | Causam Energy, Inc. | System, method, and data packets for messaging for electric power grid elements over a secure internet protocol network |
US10180773B2 (en) | 2012-06-12 | 2019-01-15 | 9224-5489 Quebec Inc. | Method of displaying axes in an axis-based interface |
US10289657B2 (en) | 2011-09-25 | 2019-05-14 | 9224-5489 Quebec Inc. | Method of retrieving information elements on an undisplayed portion of an axis of information elements |
US10430495B2 (en) | 2007-08-22 | 2019-10-01 | 9224-5489 Quebec Inc. | Timescales for axis of user-selectable elements |
US10671266B2 (en) | 2017-06-05 | 2020-06-02 | 9224-5489 Quebec Inc. | Method and apparatus of aligning information element axes |
US10845952B2 (en) | 2012-06-11 | 2020-11-24 | 9224-5489 Quebec Inc. | Method of abutting multiple sets of elements along an axis thereof |
Families Citing this family (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020002563A1 (en) * | 1999-08-23 | 2002-01-03 | Mary M. Bendik | Document management systems and methods |
US6427175B1 (en) * | 1999-09-24 | 2002-07-30 | Clickmarks, Inc | Method and apparatus for collaborative remote link management using sharable online bookmarks |
WO2003057648A2 (en) * | 2002-01-11 | 2003-07-17 | Enrico Maim | Methods and systems for searching and associating information resources such as web pages |
US10046244B2 (en) | 2002-06-14 | 2018-08-14 | Dizpersion Corporation | Method and system for operating and participating in fantasy leagues |
US7792827B2 (en) * | 2002-12-31 | 2010-09-07 | International Business Machines Corporation | Temporal link analysis of linked entities |
US20040237051A1 (en) * | 2003-05-23 | 2004-11-25 | Clauson Todd A. | Dynamic menu reordering |
US20070043766A1 (en) * | 2005-08-18 | 2007-02-22 | Nicholas Frank C | Method and System for the Creating, Managing, and Delivery of Feed Formatted Content |
US8166005B2 (en) * | 2004-09-21 | 2012-04-24 | Emc Corporation | Pathname caching and protection of the root directory in a nested multilayer directory structure |
JP2006252001A (en) * | 2005-03-09 | 2006-09-21 | Fuji Xerox Co Ltd | Document processor |
US8356053B2 (en) * | 2005-10-20 | 2013-01-15 | Oracle International Corporation | Managing relationships between resources stored within a repository |
US9959577B1 (en) * | 2006-09-28 | 2018-05-01 | Intuit Inc. | Tax return preparation automatic document capture and parsing system |
US20080104203A1 (en) * | 2006-10-31 | 2008-05-01 | Microsoft Corporation | Viewing Digital Information Over a Network |
US9286375B2 (en) * | 2007-02-06 | 2016-03-15 | Red Hat, Inc. | Linked lightweight directory access protocol (LDAP) attributes |
NO326945B1 (en) * | 2007-03-19 | 2009-03-16 | Science Linker As | Authenticated Database System. |
US8990426B2 (en) * | 2007-11-28 | 2015-03-24 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for providing electronic transactions |
US9251548B1 (en) * | 2008-03-31 | 2016-02-02 | The Mathworks, Inc. | Object transformation for object trees utilized with multiprocessor systems |
US20100211445A1 (en) * | 2009-01-15 | 2010-08-19 | Shaun Bodington | Incentives associated with linked financial accounts |
US20110093324A1 (en) | 2009-10-19 | 2011-04-21 | Visa U.S.A. Inc. | Systems and Methods to Provide Intelligent Analytics to Cardholders and Merchants |
US9471926B2 (en) | 2010-04-23 | 2016-10-18 | Visa U.S.A. Inc. | Systems and methods to provide offers to travelers |
US9760905B2 (en) | 2010-08-02 | 2017-09-12 | Visa International Service Association | Systems and methods to optimize media presentations using a camera |
US10223707B2 (en) | 2011-08-19 | 2019-03-05 | Visa International Service Association | Systems and methods to communicate offer options via messaging in real time with processing of payment transaction |
WO2014037759A1 (en) * | 2012-09-05 | 2014-03-13 | Winmagine | Computer installation for the management of a set of files, method, program and computer medium associated therewith |
US9384290B1 (en) | 2012-11-02 | 2016-07-05 | Google Inc. | Local mobile memo for non-interrupting link noting |
US10360627B2 (en) | 2012-12-13 | 2019-07-23 | Visa International Service Association | Systems and methods to provide account features via web based user interfaces |
EP2757800A1 (en) * | 2013-01-21 | 2014-07-23 | Thomson Licensing | A Transmission method, a receiving method, a video apparatus and a database system |
DE102013211726A1 (en) * | 2013-06-20 | 2014-12-24 | Robert Bosch Gmbh | Information system and method for selecting and reproducing information, in particular for use in the workshop sector |
EP3057009A1 (en) | 2015-02-10 | 2016-08-17 | ResearchGate GmbH | Online publication system and method |
EP3096277A1 (en) | 2015-05-19 | 2016-11-23 | ResearchGate GmbH | Enhanced online user-interaction tracking |
WO2016191133A1 (en) * | 2015-05-22 | 2016-12-01 | Pcms Holdings, Inc. | Retrieving sensor data based on user interest |
US10657186B2 (en) * | 2015-05-29 | 2020-05-19 | Dell Products, L.P. | System and method for automatic document classification and grouping based on document topic |
EP3319286B1 (en) * | 2015-07-29 | 2021-03-24 | Huawei Technologies Co., Ltd. | Neighbor relationship establishment method, device and system |
US10089687B2 (en) * | 2015-08-04 | 2018-10-02 | Fidelity National Information Services, Inc. | System and associated methodology of creating order lifecycles via daisy chain linkage |
US11037253B2 (en) * | 2016-04-04 | 2021-06-15 | Hexagon Technology Center Gmbh | Apparatus and method of managing 2D documents for large-scale capital projects |
US20170353397A1 (en) * | 2016-06-06 | 2017-12-07 | Advanced Micro Devices, Inc. | Offloading Execution of an Application by a Network Connected Device |
US10387559B1 (en) * | 2016-11-22 | 2019-08-20 | Google Llc | Template-based identification of user interest |
US11153400B1 (en) | 2019-06-04 | 2021-10-19 | Thomas Layne Bascom | Federation broker system and method for coordinating discovery, interoperability, connections and correspondence among networked resources |
US20220012750A1 (en) * | 2020-07-10 | 2022-01-13 | Venminder, Inc. | Systems and methods for vendor exchange management |
US11204975B1 (en) * | 2020-08-10 | 2021-12-21 | Coupang Corp. | Program interface remote management and provisioning |
CN112528595B (en) * | 2020-12-15 | 2023-05-09 | 北京字跳网络技术有限公司 | Document processing method and device and electronic equipment |
Citations (104)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4982344A (en) * | 1988-05-18 | 1991-01-01 | Xerox Corporation | Accelerating link creation |
US5204947A (en) * | 1990-10-31 | 1993-04-20 | International Business Machines Corporation | Application independent (open) hypermedia enablement services |
US5297249A (en) * | 1990-10-31 | 1994-03-22 | International Business Machines Corporation | Hypermedia link marker abstract and search services |
US5297283A (en) * | 1989-06-29 | 1994-03-22 | Digital Equipment Corporation | Object transferring system and method in an object based computer operating system |
US5303379A (en) * | 1987-08-21 | 1994-04-12 | Wang Laboratories, Inc. | Link mechanism for linking data between objects and for performing operations on the linked data in an object based system |
US5321841A (en) * | 1989-06-29 | 1994-06-14 | Digital Equipment Corporation | System for determining the rights of object access for a server process by combining them with the rights of the client process |
US5499359A (en) * | 1994-01-18 | 1996-03-12 | Borland International, Inc. | Methods for improved referential integrity in a relational database management system |
US5537526A (en) * | 1993-11-12 | 1996-07-16 | Taugent, Inc. | Method and apparatus for processing a display document utilizing a system level document framework |
US5608900A (en) * | 1994-06-21 | 1997-03-04 | Internationl Business Machines Corp. | Generation and storage of connections between objects in a computer network |
US5634048A (en) * | 1989-09-14 | 1997-05-27 | Fujitsu Limited | Distributed database system having a center system with a link file and a method for retrieving data from same |
US5634124A (en) * | 1987-08-21 | 1997-05-27 | Wang Laboratories, Inc. | Data integration by object management |
US5649192A (en) * | 1993-01-15 | 1997-07-15 | General Electric Company | Self-organized information storage system |
US5649594A (en) * | 1995-12-11 | 1997-07-22 | Boots & Coots, L.P. | Method and apparatus for servicing a wellhead assembly |
US5715441A (en) * | 1992-07-06 | 1998-02-03 | Microsoft Corporation | Method and system for storing and accessing data in a compound document using object linking |
US5717917A (en) * | 1994-03-04 | 1998-02-10 | Mitsubishi Denki Kabushiki Kaisha | Method of controlling information on data links and apparatus for controlling information on data links |
US5717922A (en) * | 1995-07-31 | 1998-02-10 | International Business Machines Corporation | Method and system for management of logical links between document elements during document interchange |
US5721911A (en) * | 1996-06-25 | 1998-02-24 | International Business Machines Corporation | Mechanism for metadata for an information catalog system |
US5742284A (en) * | 1990-07-31 | 1998-04-21 | Hewlett-Packard Company | Object based system comprising weak links |
US5761683A (en) * | 1996-02-13 | 1998-06-02 | Microtouch Systems, Inc. | Techniques for changing the behavior of a link in a hypertext document |
US5787442A (en) * | 1996-07-11 | 1998-07-28 | Microsoft Corporation | Creating interobject reference links in the directory service of a store and forward replication computer network |
US5787440A (en) * | 1994-03-10 | 1998-07-28 | Crossties Software Corp. | Object oriented architecture with bidirectional linking of relationships between objects |
US5802539A (en) * | 1995-05-05 | 1998-09-01 | Apple Computer, Inc. | Method and apparatus for managing text objects for providing text to be interpreted across computer operating systems using different human languages |
US5809317A (en) * | 1992-12-30 | 1998-09-15 | Intel Corporation | Creating and maintaining hypertext links among heterogeneous documents by the establishment of anchors and connections among anchors |
US5872973A (en) * | 1995-10-26 | 1999-02-16 | Viewsoft, Inc. | Method for managing dynamic relations between objects in dynamic object-oriented languages |
US5884079A (en) * | 1996-06-17 | 1999-03-16 | Yamatake-Honeywell Co., Ltd. | Design part reusing method in configuration tool |
US5895471A (en) * | 1997-07-11 | 1999-04-20 | Unwired Planet, Inc. | Providing a directory of frequently used hyperlinks on a remote server |
US5895470A (en) * | 1997-04-09 | 1999-04-20 | Xerox Corporation | System for categorizing documents in a linked collection of documents |
US5900870A (en) * | 1989-06-30 | 1999-05-04 | Massachusetts Institute Of Technology | Object-oriented computer user interface |
US5917491A (en) * | 1997-08-29 | 1999-06-29 | Netscape Communications Corporation | Page proxy |
US6016498A (en) * | 1996-03-04 | 2000-01-18 | Bakke; Stephen Peter | Object oriented architecture with bidirectional linking of relationships between objects |
US6029182A (en) * | 1996-10-04 | 2000-02-22 | Canon Information Systems, Inc. | System for generating a custom formatted hypertext document by using a personal profile to retrieve hierarchical documents |
US6032196A (en) * | 1995-12-13 | 2000-02-29 | Digital Equipment Corporation | System for adding a new entry to a web page table upon receiving a web page including a link to another web page not having a corresponding entry in the web page table |
US6032162A (en) * | 1998-01-08 | 2000-02-29 | Burke; Alexander James | System for processing and storing internet bookmark address links |
US6035325A (en) * | 1998-05-13 | 2000-03-07 | International Business Machines Corporation | Retrieval, saving and printing in a computer network system environment |
US6035330A (en) * | 1996-03-29 | 2000-03-07 | British Telecommunications | World wide web navigational mapping system and method |
US6035281A (en) * | 1997-06-16 | 2000-03-07 | International Business Machines Corporation | System and method of multiparty billing for Web access |
US6037935A (en) * | 1998-04-28 | 2000-03-14 | International Business Machines Corporation | Web page exploration indicator and method |
US6041360A (en) * | 1997-11-21 | 2000-03-21 | International Business Machines Corporation | Web browser support for dynamic update of bookmarks |
US6044374A (en) * | 1997-11-14 | 2000-03-28 | Informatica Corporation | Method and apparatus for sharing metadata between multiple data marts through object references |
US6044378A (en) * | 1997-09-29 | 2000-03-28 | International Business Machines Corporation | Method and system for a federated digital library by managing links |
US6049799A (en) * | 1997-05-12 | 2000-04-11 | Novell, Inc. | Document link management using directory services |
US6055542A (en) * | 1997-10-29 | 2000-04-25 | International Business Machines Corporation | System and method for displaying the contents of a web page based on a user's interests |
US6055540A (en) * | 1997-06-13 | 2000-04-25 | Sun Microsystems, Inc. | Method and apparatus for creating a category hierarchy for classification of documents |
US6069630A (en) * | 1997-08-22 | 2000-05-30 | International Business Machines Corporation | Data processing system and method for creating a link map |
US6073135A (en) * | 1998-03-10 | 2000-06-06 | Alta Vista Company | Connectivity server for locating linkage information between Web pages |
US6081829A (en) * | 1996-01-31 | 2000-06-27 | Silicon Graphics, Inc. | General purpose web annotations without modifying browser |
US6081814A (en) * | 1997-07-07 | 2000-06-27 | Novell, Inc. | Document reference environment manager |
US6138129A (en) * | 1997-12-16 | 2000-10-24 | World One Telecom, Ltd. | Method and apparatus for providing automated searching and linking of electronic documents |
US6182091B1 (en) * | 1998-03-18 | 2001-01-30 | Xerox Corporation | Method and apparatus for finding related documents in a collection of linked documents using a bibliographic coupling link analysis |
US6181614B1 (en) * | 1999-11-12 | 2001-01-30 | International Business Machines Corporation | Dynamic repair of redundant memory array |
US6182113B1 (en) * | 1997-09-16 | 2001-01-30 | International Business Machines Corporation | Dynamic multiplexing of hyperlinks and bookmarks |
US6182072B1 (en) * | 1997-03-26 | 2001-01-30 | Webtv Networks, Inc. | Method and apparatus for generating a tour of world wide web sites |
US6184886B1 (en) * | 1998-09-04 | 2001-02-06 | International Business Machines Corporation | Apparatus and method for staging bookmarks |
US6185614B1 (en) * | 1998-05-26 | 2001-02-06 | International Business Machines Corp. | Method and system for collecting user profile information over the world-wide web in the presence of dynamic content using document comparators |
US6189019B1 (en) * | 1996-08-14 | 2001-02-13 | Microsoft Corporation | Computer system and computer-implemented process for presenting document connectivity |
US6189012B1 (en) * | 1998-01-23 | 2001-02-13 | Melting Point Limited | Apparatus and method for storing, navigating among and adding links between data items |
US6195681B1 (en) * | 1997-02-07 | 2001-02-27 | About.Com, Inc. | Guide-based internet directory system and method |
US6204582B1 (en) * | 1999-12-16 | 2001-03-20 | Eaton Corporation | Servo motor assembly and method of making same |
US6208992B1 (en) * | 1995-10-13 | 2001-03-27 | Genesys Software-Entwicklungs-Und Produktions-Gmbh | Information system and process for storing data therein |
US6209036B1 (en) * | 1997-06-06 | 2001-03-27 | International Business Machines Corporation | Management of and access to information and other material via the world wide web in an LDAP environment |
US6212533B1 (en) * | 1996-02-16 | 2001-04-03 | Nec Corporation | Hyper-media document management system having navigation mechanism |
US6226655B1 (en) * | 1996-10-08 | 2001-05-01 | Netjumper, Inc. | Method and apparatus for retrieving data from a network using linked location identifiers |
US6236768B1 (en) * | 1997-10-14 | 2001-05-22 | Massachusetts Institute Of Technology | Method and apparatus for automated, context-dependent retrieval of information |
US6236991B1 (en) * | 1997-11-26 | 2001-05-22 | International Business Machines Corp. | Method and system for providing access for categorized information from online internet and intranet sources |
US20010020238A1 (en) * | 2000-02-04 | 2001-09-06 | Hiroshi Tsuda | Document searching apparatus, method thereof, and record medium thereof |
US6336123B2 (en) * | 1996-10-02 | 2002-01-01 | Matsushita Electric Industrial Co., Ltd. | Hierarchical based hyper-text document preparing and management apparatus |
US6356922B1 (en) * | 1997-09-15 | 2002-03-12 | Fuji Xerox Co., Ltd. | Method and system for suggesting related documents |
US20020032672A1 (en) * | 2000-03-09 | 2002-03-14 | The Web Access, Inc | Method and apparatus for formatting information within a directory tree structure into an encylopedia-like entry |
US6366923B1 (en) * | 1998-03-23 | 2002-04-02 | Webivore Research, Llc | Gathering selected information from the world wide web |
US6389434B1 (en) * | 1993-11-19 | 2002-05-14 | Aurigin Systems, Inc. | System, method, and computer program product for creating subnotes linked to portions of data objects after entering an annotation mode |
US20020065671A1 (en) * | 2000-09-12 | 2002-05-30 | Goerz David J. | Method and system for project customized business to business development with indexed knowledge base |
US20020073174A1 (en) * | 1999-12-15 | 2002-06-13 | Mengerink Matthew W. | System and method to create a customized internet site |
US6411924B1 (en) * | 1998-01-23 | 2002-06-25 | Novell, Inc. | System and method for linguistic filter and interactive display |
US6518686B2 (en) * | 2001-02-23 | 2003-02-11 | Valeo Electrical Systems, Inc. | Electric motor including unitary brush card bushing holder |
US20030050916A1 (en) * | 1999-11-18 | 2003-03-13 | Ortega Ruben E. | Computer processes for selecting nodes to call to attention of a user during browsing of a hierarchical browse structure |
US6562076B2 (en) * | 1998-08-31 | 2003-05-13 | Xerox Corporation | Extending application behavior through active properties attached to a document in a document management system |
US6581065B1 (en) * | 1998-02-10 | 2003-06-17 | National Broadcasting Comany, Inc. | Dynamic insertion and updating of hypertext links for internet servers |
US20030115546A1 (en) * | 2000-02-17 | 2003-06-19 | Dubey Stuart P. | Method and apparatus for integrating digital media assets into documents |
US6584466B1 (en) * | 1999-04-07 | 2003-06-24 | Critical Path, Inc. | Internet document management system and methods |
US6582474B2 (en) * | 1998-08-31 | 2003-06-24 | Xerox Corporation | Tagging related files in a document management system |
US6651070B1 (en) * | 1999-06-30 | 2003-11-18 | Hitachi, Ltd. | Client/server database system |
US6684222B1 (en) * | 2000-11-09 | 2004-01-27 | Accenture Llp | Method and system for translating data associated with a relational database |
US6687877B1 (en) * | 1999-02-17 | 2004-02-03 | Siemens Corp. Research Inc. | Web-based call center system with web document annotation |
US6697838B1 (en) * | 2000-05-03 | 2004-02-24 | Software Leader, Llc | Method and system for annotating information resources in connection with browsing, in both connected and disconnected states |
US6711586B1 (en) * | 2000-07-17 | 2004-03-23 | William Mitchell Wells | Methods and systems for providing information based on similarity |
US6713916B1 (en) * | 2002-10-31 | 2004-03-30 | Black & Decker Inc. | Electric motor assembly |
US6725227B1 (en) * | 1998-10-02 | 2004-04-20 | Nec Corporation | Advanced web bookmark database system |
US6751777B2 (en) * | 1998-10-19 | 2004-06-15 | International Business Machines Corporation | Multi-target links for navigating between hypertext documents and the like |
US6754873B1 (en) * | 1999-09-20 | 2004-06-22 | Google Inc. | Techniques for finding related hyperlinked documents using link-based analysis |
US6858957B2 (en) * | 2002-10-31 | 2005-02-22 | Black & Decker Inc. | Electric motor end plate with visual alignment indicia |
US6877137B1 (en) * | 1998-04-09 | 2005-04-05 | Rose Blush Software Llc | System, method and computer program product for mediating notes and note sub-notes linked or otherwise associated with stored or networked web pages |
US6882995B2 (en) * | 1998-08-14 | 2005-04-19 | Vignette Corporation | Automatic query and transformative process |
US20050086186A1 (en) * | 1999-02-02 | 2005-04-21 | Alan Sullivan | Neural network system and method for controlling information output based on user feedback |
US20050114353A1 (en) * | 1998-12-08 | 2005-05-26 | Masroor Malik | Method and apparatus for tracking functional states of a Web-site and reporting results to Web developers |
US6983313B1 (en) * | 1999-06-10 | 2006-01-03 | Nokia Corporation | Collaborative location server/system |
US20060020586A1 (en) * | 2000-03-03 | 2006-01-26 | Michel Prompt | System and method for providing access to databases via directories and other hierarchical structures and interfaces |
US6993657B1 (en) * | 2000-09-08 | 2006-01-31 | Oracle International Corporation | Techniques for managing database systems with a community server |
US7013308B1 (en) * | 2000-11-28 | 2006-03-14 | Semscript Ltd. | Knowledge storage and retrieval system and method |
US7020679B2 (en) * | 2000-05-12 | 2006-03-28 | Taoofsearch, Inc. | Two-level internet search service system |
US7024468B1 (en) * | 2000-04-27 | 2006-04-04 | Hewlett-Packard Development Company, L.P. | Internet usage data recording system and method with configurable data collector system |
US7028032B1 (en) * | 1999-09-28 | 2006-04-11 | International Business Machines Corporation | Method of updating network information addresses |
US7152224B1 (en) * | 2000-11-21 | 2006-12-19 | Microsoft Corporation | Versioned project associations |
US7162499B2 (en) * | 2000-06-21 | 2007-01-09 | Microsoft Corporation | Linked value replication |
US20080133404A1 (en) * | 2001-03-07 | 2008-06-05 | Thomas Layne Bascom | Method for users of a network to provide other users with access to link relationships between documents |
Family Cites Families (85)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3577025A (en) | 1968-06-07 | 1971-05-04 | Union Carbide Corp | Clip for carbon brushes |
CA971212A (en) | 1973-07-30 | 1975-07-15 | Francis J. Rosenthal (Jr.) | Air flow baffle construction for electric motor devices |
DE2649181A1 (en) | 1976-10-28 | 1978-05-03 | Siemens Ag | Electric machine ventilating system with fan impeller - has radial fan cowl connected to machine and covering impeller |
DE8025424U1 (en) | 1980-09-23 | 1981-01-08 | Robert Bosch Gmbh, 7000 Stuttgart | ELECTRIC MACHINE |
SU964817A1 (en) | 1981-03-03 | 1982-10-07 | Куйбышевский политехнический институт | Bruh holder for electric machines |
JPS5837919U (en) | 1981-09-04 | 1983-03-11 | 日産自動車株式会社 | Automotive alternator cooling system |
US5715444A (en) | 1994-10-14 | 1998-02-03 | Danish; Mohamed Sherif | Method and system for executing a guided parametric search |
US5694594A (en) * | 1994-11-14 | 1997-12-02 | Chang; Daniel | System for linking hypermedia data objects in accordance with associations of source and destination data objects and similarity threshold without using keywords or link-difining terms |
US5801702A (en) * | 1995-03-09 | 1998-09-01 | Terrabyte Technology | System and method for adding network links in a displayed hierarchy |
US6901433B2 (en) | 1995-06-07 | 2005-05-31 | Microsoft Corporation | System for providing users with a filtered view of interactive network directory obtains from remote properties cache that provided by an on-line service |
US5794257A (en) | 1995-07-14 | 1998-08-11 | Siemens Corporate Research, Inc. | Automatic hyperlinking on multimedia by compiling link specifications |
JPH0934763A (en) * | 1995-07-19 | 1997-02-07 | Fuji Xerox Co Ltd | Device and method for managing file |
US5826025A (en) * | 1995-09-08 | 1998-10-20 | Sun Microsystems, Inc. | System for annotation overlay proxy configured to retrieve associated overlays associated with a document request from annotation directory created from list of overlay groups |
AU1122997A (en) | 1995-11-07 | 1997-06-11 | Cadis, Inc. | Search engine for remote object oriented database management system |
US5650199A (en) | 1995-11-22 | 1997-07-22 | Aem, Inc. | Method of making a multilayer electronic component with inter-layer conductor connection utilizing a conductive via forming ink |
US5822539A (en) * | 1995-12-08 | 1998-10-13 | Sun Microsystems, Inc. | System for adding requested document cross references to a document by annotation proxy configured to merge and a directory generator and annotation server |
US5778367A (en) | 1995-12-14 | 1998-07-07 | Network Engineering Software, Inc. | Automated on-line information service and directory, particularly for the world wide web |
US5794232A (en) * | 1996-03-15 | 1998-08-11 | Novell, Inc. | Catalog services for distributed directories |
US5987480A (en) | 1996-07-25 | 1999-11-16 | Donohue; Michael | Method and system for delivering documents customized for a particular user over the internet using imbedded dynamic content |
JPH1069423A (en) | 1996-08-28 | 1998-03-10 | Nec Corp | Hypermedia system and its directory data managing method |
US5933827A (en) | 1996-09-25 | 1999-08-03 | International Business Machines Corporation | System for identifying new web pages of interest to a user |
US6112024A (en) | 1996-10-02 | 2000-08-29 | Sybase, Inc. | Development system providing methods for managing different versions of objects with a meta model |
US6006252A (en) | 1996-10-08 | 1999-12-21 | Wolfe; Mark A. | System and method for communicating information relating to a network resource |
US5809250A (en) * | 1996-10-23 | 1998-09-15 | Intel Corporation | Methods for creating and sharing replayable modules representive of Web browsing session |
US5796393A (en) | 1996-11-08 | 1998-08-18 | Compuserve Incorporated | System for intergrating an on-line service community with a foreign service |
US6128667A (en) * | 1996-11-12 | 2000-10-03 | Elfnet, Inc. | System and method for deferred resolution hypertext links |
US5966126A (en) | 1996-12-23 | 1999-10-12 | Szabo; Andrew J. | Graphic user interface for database system |
US6175831B1 (en) | 1997-01-17 | 2001-01-16 | Six Degrees, Inc. | Method and apparatus for constructing a networking database and system |
US5937406A (en) * | 1997-01-31 | 1999-08-10 | Informix Software, Inc. | File system interface to a database |
US5842221A (en) * | 1997-02-19 | 1998-11-24 | Wisdomware, Inc. | Dynamic frequently asked questions (FAQ) system |
US5875446A (en) | 1997-02-24 | 1999-02-23 | International Business Machines Corporation | System and method for hierarchically grouping and ranking a set of objects in a query context based on one or more relationships |
US5941944A (en) * | 1997-03-03 | 1999-08-24 | Microsoft Corporation | Method for providing a substitute for a requested inaccessible object by identifying substantially similar objects using weights corresponding to object features |
US6112202A (en) | 1997-03-07 | 2000-08-29 | International Business Machines Corporation | Method and system for identifying authoritative information resources in an environment with content-based links between information resources |
US5940834A (en) | 1997-03-13 | 1999-08-17 | Mitel Corporation | Automatic web page generator |
DE29706216U1 (en) | 1997-04-08 | 1998-08-06 | Mulfingen Elektrobau Ebm | Arrangement for the vibration-isolating suspension of an electric motor |
US5924090A (en) | 1997-05-01 | 1999-07-13 | Northern Light Technology Llc | Method and apparatus for searching a database of records |
US6282548B1 (en) * | 1997-06-21 | 2001-08-28 | Alexa Internet | Automatically generate and displaying metadata as supplemental information concurrently with the web page, there being no link between web page and metadata |
US5958016A (en) | 1997-07-13 | 1999-09-28 | Bell Atlantic Network Services, Inc. | Internet-web link for access to intelligent network service control |
US6292789B1 (en) | 1997-08-26 | 2001-09-18 | Citibank, N.A. | Method and system for bill presentment and payment |
US6658623B1 (en) * | 1997-09-15 | 2003-12-02 | Fuji Xerox Co., Ltd. | Displaying in a first document a selectable link to a second document based on a passive query |
US5999929A (en) * | 1997-09-29 | 1999-12-07 | Continuum Software, Inc | World wide web link referral system and method for generating and providing related links for links identified in web pages |
US6009410A (en) | 1997-10-16 | 1999-12-28 | At&T Corporation | Method and system for presenting customized advertising to a user on the world wide web |
US7225463B2 (en) | 1997-10-24 | 2007-05-29 | Dusenbury Jr Richard G | Secure network architecture method and apparatus |
US6269369B1 (en) | 1997-11-02 | 2001-07-31 | Amazon.Com Holdings, Inc. | Networked personal contact manager |
US5987471A (en) * | 1997-11-13 | 1999-11-16 | Novell, Inc. | Sub-foldering system in a directory-service-based launcher |
US5943670A (en) | 1997-11-21 | 1999-08-24 | International Business Machines Corporation | System and method for categorizing objects in combined categories |
US6574644B2 (en) * | 1997-11-26 | 2003-06-03 | Siemens Corporate Research, Inc | Automatic capturing of hyperlink specifications for multimedia documents |
US6144991A (en) * | 1998-02-19 | 2000-11-07 | Telcordia Technologies, Inc. | System and method for managing interactions between users in a browser-based telecommunications network |
US6122647A (en) * | 1998-05-19 | 2000-09-19 | Perspecta, Inc. | Dynamic generation of contextual links in hypertext documents |
US6138159A (en) * | 1998-06-11 | 2000-10-24 | Phaal; Peter | Load direction mechanism |
US7051275B2 (en) * | 1998-09-15 | 2006-05-23 | Microsoft Corporation | Annotations for multiple versions of media content |
US6266649B1 (en) | 1998-09-18 | 2001-07-24 | Amazon.Com, Inc. | Collaborative recommendations using item-to-item similarity mappings |
US6772139B1 (en) | 1998-10-05 | 2004-08-03 | Smith, Iii Julius O. | Method and apparatus for facilitating use of hypertext links on the world wide web |
US6145000A (en) | 1998-10-06 | 2000-11-07 | Ameritech Corporation | System and method for creating and navigating a linear hypermedia resource program |
US6970867B1 (en) * | 1998-11-12 | 2005-11-29 | International Business Machines Corporation | Bookmarking of web page frames in world wide web for accessing web pages within a frames implementation |
US6434546B1 (en) | 1998-12-22 | 2002-08-13 | Xerox Corporation | System and method for transferring attribute values between search queries in an information retrieval system |
US6480835B1 (en) | 1998-12-31 | 2002-11-12 | Intel Corporation | Method and system for searching on integrated metadata |
US6631496B1 (en) * | 1999-03-22 | 2003-10-07 | Nec Corporation | System for personalizing, organizing and managing web information |
US6763496B1 (en) * | 1999-03-31 | 2004-07-13 | Microsoft Corporation | Method for promoting contextual information to display pages containing hyperlinks |
US6317777B1 (en) * | 1999-04-26 | 2001-11-13 | Intel Corporation | Method for web based storage and retrieval of documents |
US6560606B1 (en) | 1999-05-04 | 2003-05-06 | Metratech | Method and apparatus for processing data with multiple processing modules and associated counters |
US6493702B1 (en) | 1999-05-05 | 2002-12-10 | Xerox Corporation | System and method for searching and recommending documents in a collection using share bookmarks |
US6973616B1 (en) * | 1999-06-24 | 2005-12-06 | Microsoft Corporation | Associating annotations with a content source |
US7165069B1 (en) | 1999-06-28 | 2007-01-16 | Alexa Internet | Analysis of search activities of users to identify related network sites |
US6647534B1 (en) * | 1999-06-30 | 2003-11-11 | Ricoh Company Limited | Method and system for organizing document information in a non-directed arrangement of documents |
US7010742B1 (en) | 1999-09-22 | 2006-03-07 | Siemens Corporate Research, Inc. | Generalized system for automatically hyperlinking multimedia product documents |
US6546393B1 (en) | 1999-10-07 | 2003-04-08 | Clickmarks, Inc. | System method and article of manufacture for dynamically user-generated internet search directory based on prioritized server-sided user bookmarks |
US6981040B1 (en) | 1999-12-28 | 2005-12-27 | Utopy, Inc. | Automatic, personalized online information and product services |
FR2805121B1 (en) | 2000-02-11 | 2002-04-26 | Leroy Somer | MODULAR CONVERTER |
US6606654B1 (en) | 2000-02-14 | 2003-08-12 | Netjumper, Inc. | Link delivery for subsequent retrieval of networked information |
US7266762B1 (en) * | 2000-03-10 | 2007-09-04 | International Business Machines Corporation | Method and system for distributed autonomous maintenance of bidirectional hyperlink metadata on the web and similar hypermedia repository |
US6311194B1 (en) | 2000-03-15 | 2001-10-30 | Taalee, Inc. | System and method for creating a semantic web and its applications in browsing, searching, profiling, personalization and advertising |
US6628026B2 (en) | 2000-03-30 | 2003-09-30 | Asmo Co., Ltd. | Geared motor including ribbed gear housing |
US20010032672A1 (en) | 2000-04-18 | 2001-10-25 | Lancer Partnership Ltd. | Enhanced flow controller for a beverage dispenser |
US7373313B1 (en) | 2000-04-25 | 2008-05-13 | Alexa Internet | Service for enabling users to share information regarding products represented on web pages |
US7035864B1 (en) | 2000-05-18 | 2006-04-25 | Endeca Technologies, Inc. | Hierarchical data-driven navigation system and method for information retrieval |
US6417595B1 (en) | 2000-05-24 | 2002-07-09 | Mcmillan Electric Company | Spark suppression dust sealing for a motor apparatus |
US6948135B1 (en) | 2000-06-21 | 2005-09-20 | Microsoft Corporation | Method and systems of providing information to computer users |
US20020099552A1 (en) * | 2001-01-25 | 2002-07-25 | Darryl Rubin | Annotating electronic information with audio clips |
US6785693B2 (en) * | 2001-02-02 | 2004-08-31 | International Business Machines Corporation | Management of multiple links to a file in a file system |
US7185275B2 (en) * | 2001-02-27 | 2007-02-27 | International Business Machines Corporation | Method and computer system for enabling a user to construct a web-site navigation |
US6925594B2 (en) * | 2001-02-28 | 2005-08-02 | International Business Machines Corporation | Saving selected hyperlinks for retrieval of the hyperlinked documents upon selection of a finished reading button in a web browser |
DE10118275A1 (en) | 2001-04-12 | 2002-10-31 | Bosch Gmbh Robert | Housing with at least one functional element of an electrical machine |
US6798109B2 (en) | 2002-10-31 | 2004-09-28 | Black & Decker Inc. | Electric motor brush assembly |
US7574461B1 (en) * | 2005-12-28 | 2009-08-11 | Emc Corporation | Dividing data for multi-thread backup |
-
2002
- 2002-01-18 US US10/050,515 patent/US7386792B1/en not_active Expired - Fee Related
- 2002-03-06 US US10/090,739 patent/US7139974B1/en not_active Expired - Fee Related
-
2006
- 2006-11-20 US US11/601,645 patent/US8515998B1/en not_active Expired - Fee Related
-
2007
- 2007-10-31 US US11/979,260 patent/US20100023500A1/en not_active Abandoned
-
2012
- 2012-03-28 US US13/432,642 patent/US9128934B2/en not_active Expired - Fee Related
-
2013
- 2013-01-30 US US13/754,542 patent/US9047386B2/en not_active Expired - Fee Related
- 2013-08-30 US US14/015,782 patent/US9218431B2/en not_active Expired - Fee Related
-
2015
- 2015-12-14 US US14/968,796 patent/US20160154878A1/en not_active Abandoned
Patent Citations (105)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5634124A (en) * | 1987-08-21 | 1997-05-27 | Wang Laboratories, Inc. | Data integration by object management |
US5303379A (en) * | 1987-08-21 | 1994-04-12 | Wang Laboratories, Inc. | Link mechanism for linking data between objects and for performing operations on the linked data in an object based system |
US4982344A (en) * | 1988-05-18 | 1991-01-01 | Xerox Corporation | Accelerating link creation |
US5321841A (en) * | 1989-06-29 | 1994-06-14 | Digital Equipment Corporation | System for determining the rights of object access for a server process by combining them with the rights of the client process |
US5297283A (en) * | 1989-06-29 | 1994-03-22 | Digital Equipment Corporation | Object transferring system and method in an object based computer operating system |
US5900870A (en) * | 1989-06-30 | 1999-05-04 | Massachusetts Institute Of Technology | Object-oriented computer user interface |
US5634048A (en) * | 1989-09-14 | 1997-05-27 | Fujitsu Limited | Distributed database system having a center system with a link file and a method for retrieving data from same |
US5742284A (en) * | 1990-07-31 | 1998-04-21 | Hewlett-Packard Company | Object based system comprising weak links |
US5297249A (en) * | 1990-10-31 | 1994-03-22 | International Business Machines Corporation | Hypermedia link marker abstract and search services |
US5204947A (en) * | 1990-10-31 | 1993-04-20 | International Business Machines Corporation | Application independent (open) hypermedia enablement services |
US5715441A (en) * | 1992-07-06 | 1998-02-03 | Microsoft Corporation | Method and system for storing and accessing data in a compound document using object linking |
US5809317A (en) * | 1992-12-30 | 1998-09-15 | Intel Corporation | Creating and maintaining hypertext links among heterogeneous documents by the establishment of anchors and connections among anchors |
US5649192A (en) * | 1993-01-15 | 1997-07-15 | General Electric Company | Self-organized information storage system |
US5537526A (en) * | 1993-11-12 | 1996-07-16 | Taugent, Inc. | Method and apparatus for processing a display document utilizing a system level document framework |
US6389434B1 (en) * | 1993-11-19 | 2002-05-14 | Aurigin Systems, Inc. | System, method, and computer program product for creating subnotes linked to portions of data objects after entering an annotation mode |
US5499359A (en) * | 1994-01-18 | 1996-03-12 | Borland International, Inc. | Methods for improved referential integrity in a relational database management system |
US5717917A (en) * | 1994-03-04 | 1998-02-10 | Mitsubishi Denki Kabushiki Kaisha | Method of controlling information on data links and apparatus for controlling information on data links |
US5787440A (en) * | 1994-03-10 | 1998-07-28 | Crossties Software Corp. | Object oriented architecture with bidirectional linking of relationships between objects |
US5608900A (en) * | 1994-06-21 | 1997-03-04 | Internationl Business Machines Corp. | Generation and storage of connections between objects in a computer network |
US5802539A (en) * | 1995-05-05 | 1998-09-01 | Apple Computer, Inc. | Method and apparatus for managing text objects for providing text to be interpreted across computer operating systems using different human languages |
US5717922A (en) * | 1995-07-31 | 1998-02-10 | International Business Machines Corporation | Method and system for management of logical links between document elements during document interchange |
US6208992B1 (en) * | 1995-10-13 | 2001-03-27 | Genesys Software-Entwicklungs-Und Produktions-Gmbh | Information system and process for storing data therein |
US5872973A (en) * | 1995-10-26 | 1999-02-16 | Viewsoft, Inc. | Method for managing dynamic relations between objects in dynamic object-oriented languages |
US5649594A (en) * | 1995-12-11 | 1997-07-22 | Boots & Coots, L.P. | Method and apparatus for servicing a wellhead assembly |
US6032196A (en) * | 1995-12-13 | 2000-02-29 | Digital Equipment Corporation | System for adding a new entry to a web page table upon receiving a web page including a link to another web page not having a corresponding entry in the web page table |
US6081829A (en) * | 1996-01-31 | 2000-06-27 | Silicon Graphics, Inc. | General purpose web annotations without modifying browser |
US5761683A (en) * | 1996-02-13 | 1998-06-02 | Microtouch Systems, Inc. | Techniques for changing the behavior of a link in a hypertext document |
US6212533B1 (en) * | 1996-02-16 | 2001-04-03 | Nec Corporation | Hyper-media document management system having navigation mechanism |
US6016498A (en) * | 1996-03-04 | 2000-01-18 | Bakke; Stephen Peter | Object oriented architecture with bidirectional linking of relationships between objects |
US6035330A (en) * | 1996-03-29 | 2000-03-07 | British Telecommunications | World wide web navigational mapping system and method |
US5884079A (en) * | 1996-06-17 | 1999-03-16 | Yamatake-Honeywell Co., Ltd. | Design part reusing method in configuration tool |
US5721911A (en) * | 1996-06-25 | 1998-02-24 | International Business Machines Corporation | Mechanism for metadata for an information catalog system |
US5787442A (en) * | 1996-07-11 | 1998-07-28 | Microsoft Corporation | Creating interobject reference links in the directory service of a store and forward replication computer network |
US6189019B1 (en) * | 1996-08-14 | 2001-02-13 | Microsoft Corporation | Computer system and computer-implemented process for presenting document connectivity |
US6336123B2 (en) * | 1996-10-02 | 2002-01-01 | Matsushita Electric Industrial Co., Ltd. | Hierarchical based hyper-text document preparing and management apparatus |
US6029182A (en) * | 1996-10-04 | 2000-02-22 | Canon Information Systems, Inc. | System for generating a custom formatted hypertext document by using a personal profile to retrieve hierarchical documents |
US6226655B1 (en) * | 1996-10-08 | 2001-05-01 | Netjumper, Inc. | Method and apparatus for retrieving data from a network using linked location identifiers |
US6195681B1 (en) * | 1997-02-07 | 2001-02-27 | About.Com, Inc. | Guide-based internet directory system and method |
US6182072B1 (en) * | 1997-03-26 | 2001-01-30 | Webtv Networks, Inc. | Method and apparatus for generating a tour of world wide web sites |
US5895470A (en) * | 1997-04-09 | 1999-04-20 | Xerox Corporation | System for categorizing documents in a linked collection of documents |
US6049799A (en) * | 1997-05-12 | 2000-04-11 | Novell, Inc. | Document link management using directory services |
US6209036B1 (en) * | 1997-06-06 | 2001-03-27 | International Business Machines Corporation | Management of and access to information and other material via the world wide web in an LDAP environment |
US6055540A (en) * | 1997-06-13 | 2000-04-25 | Sun Microsystems, Inc. | Method and apparatus for creating a category hierarchy for classification of documents |
US6035281A (en) * | 1997-06-16 | 2000-03-07 | International Business Machines Corporation | System and method of multiparty billing for Web access |
US6081814A (en) * | 1997-07-07 | 2000-06-27 | Novell, Inc. | Document reference environment manager |
US5895471A (en) * | 1997-07-11 | 1999-04-20 | Unwired Planet, Inc. | Providing a directory of frequently used hyperlinks on a remote server |
US6069630A (en) * | 1997-08-22 | 2000-05-30 | International Business Machines Corporation | Data processing system and method for creating a link map |
US5917491A (en) * | 1997-08-29 | 1999-06-29 | Netscape Communications Corporation | Page proxy |
US6356922B1 (en) * | 1997-09-15 | 2002-03-12 | Fuji Xerox Co., Ltd. | Method and system for suggesting related documents |
US6182113B1 (en) * | 1997-09-16 | 2001-01-30 | International Business Machines Corporation | Dynamic multiplexing of hyperlinks and bookmarks |
US6044378A (en) * | 1997-09-29 | 2000-03-28 | International Business Machines Corporation | Method and system for a federated digital library by managing links |
US6236768B1 (en) * | 1997-10-14 | 2001-05-22 | Massachusetts Institute Of Technology | Method and apparatus for automated, context-dependent retrieval of information |
US6055542A (en) * | 1997-10-29 | 2000-04-25 | International Business Machines Corporation | System and method for displaying the contents of a web page based on a user's interests |
US6044374A (en) * | 1997-11-14 | 2000-03-28 | Informatica Corporation | Method and apparatus for sharing metadata between multiple data marts through object references |
US6041360A (en) * | 1997-11-21 | 2000-03-21 | International Business Machines Corporation | Web browser support for dynamic update of bookmarks |
US6236991B1 (en) * | 1997-11-26 | 2001-05-22 | International Business Machines Corp. | Method and system for providing access for categorized information from online internet and intranet sources |
US6138129A (en) * | 1997-12-16 | 2000-10-24 | World One Telecom, Ltd. | Method and apparatus for providing automated searching and linking of electronic documents |
US6032162A (en) * | 1998-01-08 | 2000-02-29 | Burke; Alexander James | System for processing and storing internet bookmark address links |
US6411924B1 (en) * | 1998-01-23 | 2002-06-25 | Novell, Inc. | System and method for linguistic filter and interactive display |
US6189012B1 (en) * | 1998-01-23 | 2001-02-13 | Melting Point Limited | Apparatus and method for storing, navigating among and adding links between data items |
US6581065B1 (en) * | 1998-02-10 | 2003-06-17 | National Broadcasting Comany, Inc. | Dynamic insertion and updating of hypertext links for internet servers |
US6073135A (en) * | 1998-03-10 | 2000-06-06 | Alta Vista Company | Connectivity server for locating linkage information between Web pages |
US6182091B1 (en) * | 1998-03-18 | 2001-01-30 | Xerox Corporation | Method and apparatus for finding related documents in a collection of linked documents using a bibliographic coupling link analysis |
US6366923B1 (en) * | 1998-03-23 | 2002-04-02 | Webivore Research, Llc | Gathering selected information from the world wide web |
US6877137B1 (en) * | 1998-04-09 | 2005-04-05 | Rose Blush Software Llc | System, method and computer program product for mediating notes and note sub-notes linked or otherwise associated with stored or networked web pages |
US6037935A (en) * | 1998-04-28 | 2000-03-14 | International Business Machines Corporation | Web page exploration indicator and method |
US6035325A (en) * | 1998-05-13 | 2000-03-07 | International Business Machines Corporation | Retrieval, saving and printing in a computer network system environment |
US6185614B1 (en) * | 1998-05-26 | 2001-02-06 | International Business Machines Corp. | Method and system for collecting user profile information over the world-wide web in the presence of dynamic content using document comparators |
US6882995B2 (en) * | 1998-08-14 | 2005-04-19 | Vignette Corporation | Automatic query and transformative process |
US6582474B2 (en) * | 1998-08-31 | 2003-06-24 | Xerox Corporation | Tagging related files in a document management system |
US6562076B2 (en) * | 1998-08-31 | 2003-05-13 | Xerox Corporation | Extending application behavior through active properties attached to a document in a document management system |
US6184886B1 (en) * | 1998-09-04 | 2001-02-06 | International Business Machines Corporation | Apparatus and method for staging bookmarks |
US6725227B1 (en) * | 1998-10-02 | 2004-04-20 | Nec Corporation | Advanced web bookmark database system |
US6751777B2 (en) * | 1998-10-19 | 2004-06-15 | International Business Machines Corporation | Multi-target links for navigating between hypertext documents and the like |
US20050114353A1 (en) * | 1998-12-08 | 2005-05-26 | Masroor Malik | Method and apparatus for tracking functional states of a Web-site and reporting results to Web developers |
US20050086186A1 (en) * | 1999-02-02 | 2005-04-21 | Alan Sullivan | Neural network system and method for controlling information output based on user feedback |
US6687877B1 (en) * | 1999-02-17 | 2004-02-03 | Siemens Corp. Research Inc. | Web-based call center system with web document annotation |
US6584466B1 (en) * | 1999-04-07 | 2003-06-24 | Critical Path, Inc. | Internet document management system and methods |
US6983313B1 (en) * | 1999-06-10 | 2006-01-03 | Nokia Corporation | Collaborative location server/system |
US6651070B1 (en) * | 1999-06-30 | 2003-11-18 | Hitachi, Ltd. | Client/server database system |
US6754873B1 (en) * | 1999-09-20 | 2004-06-22 | Google Inc. | Techniques for finding related hyperlinked documents using link-based analysis |
US7028032B1 (en) * | 1999-09-28 | 2006-04-11 | International Business Machines Corporation | Method of updating network information addresses |
US6181614B1 (en) * | 1999-11-12 | 2001-01-30 | International Business Machines Corporation | Dynamic repair of redundant memory array |
US20030050916A1 (en) * | 1999-11-18 | 2003-03-13 | Ortega Ruben E. | Computer processes for selecting nodes to call to attention of a user during browsing of a hierarchical browse structure |
US20020073174A1 (en) * | 1999-12-15 | 2002-06-13 | Mengerink Matthew W. | System and method to create a customized internet site |
US6204582B1 (en) * | 1999-12-16 | 2001-03-20 | Eaton Corporation | Servo motor assembly and method of making same |
US20010020238A1 (en) * | 2000-02-04 | 2001-09-06 | Hiroshi Tsuda | Document searching apparatus, method thereof, and record medium thereof |
US20030115546A1 (en) * | 2000-02-17 | 2003-06-19 | Dubey Stuart P. | Method and apparatus for integrating digital media assets into documents |
US20060020586A1 (en) * | 2000-03-03 | 2006-01-26 | Michel Prompt | System and method for providing access to databases via directories and other hierarchical structures and interfaces |
US20020032672A1 (en) * | 2000-03-09 | 2002-03-14 | The Web Access, Inc | Method and apparatus for formatting information within a directory tree structure into an encylopedia-like entry |
US7024468B1 (en) * | 2000-04-27 | 2006-04-04 | Hewlett-Packard Development Company, L.P. | Internet usage data recording system and method with configurable data collector system |
US6697838B1 (en) * | 2000-05-03 | 2004-02-24 | Software Leader, Llc | Method and system for annotating information resources in connection with browsing, in both connected and disconnected states |
US7020679B2 (en) * | 2000-05-12 | 2006-03-28 | Taoofsearch, Inc. | Two-level internet search service system |
US7162499B2 (en) * | 2000-06-21 | 2007-01-09 | Microsoft Corporation | Linked value replication |
US6711586B1 (en) * | 2000-07-17 | 2004-03-23 | William Mitchell Wells | Methods and systems for providing information based on similarity |
US6993657B1 (en) * | 2000-09-08 | 2006-01-31 | Oracle International Corporation | Techniques for managing database systems with a community server |
US20020065671A1 (en) * | 2000-09-12 | 2002-05-30 | Goerz David J. | Method and system for project customized business to business development with indexed knowledge base |
US6684222B1 (en) * | 2000-11-09 | 2004-01-27 | Accenture Llp | Method and system for translating data associated with a relational database |
US7152224B1 (en) * | 2000-11-21 | 2006-12-19 | Microsoft Corporation | Versioned project associations |
US7013308B1 (en) * | 2000-11-28 | 2006-03-14 | Semscript Ltd. | Knowledge storage and retrieval system and method |
US6518686B2 (en) * | 2001-02-23 | 2003-02-11 | Valeo Electrical Systems, Inc. | Electric motor including unitary brush card bushing holder |
US20080133404A1 (en) * | 2001-03-07 | 2008-06-05 | Thomas Layne Bascom | Method for users of a network to provide other users with access to link relationships between documents |
US7702521B2 (en) * | 2001-03-07 | 2010-04-20 | Thomas Layne Bascom | Method for users of a network to provide other users with access to link relationships between documents |
US6713916B1 (en) * | 2002-10-31 | 2004-03-30 | Black & Decker Inc. | Electric motor assembly |
US6858957B2 (en) * | 2002-10-31 | 2005-02-22 | Black & Decker Inc. | Electric motor end plate with visual alignment indicia |
Non-Patent Citations (4)
Title |
---|
DeRose, Stevens J., "XML Linking", ACM Computing Surveys, Vol. 31, Issue 4es, Article No. 21, Dec. 1999, pp. 1-12. * |
Lai, Kum-Yew, et al., "Object Lens: A "Spreadsheet" for Cooperative Work", ACM Transactions on Office Information Systems, Vol. 6, No. 4, Oct. 1998, pp. 332-353. * |
Olson, Michael R., et al., "Object Databases for SGML Document Management", HICSS, Maui, HI, Jan. 3-6, 1997, pp. 39-48. * |
Schwabe, Daniel, et al., "From Domain Models to Hypermedia Applications: an Object-Oriented Approach", CiteSeer, © 1994, pp. 1-17. * |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11550987B2 (en) | 2007-08-22 | 2023-01-10 | 9224-5489 Quebec Inc. | Timeline for presenting information |
US10430495B2 (en) | 2007-08-22 | 2019-10-01 | 9224-5489 Quebec Inc. | Timescales for axis of user-selectable elements |
US9690460B2 (en) | 2007-08-22 | 2017-06-27 | 9224-5489 Quebec Inc. | Method and apparatus for identifying user-selectable elements having a commonality thereof |
US10719658B2 (en) | 2007-08-22 | 2020-07-21 | 9224-5489 Quebec Inc. | Method of displaying axes of documents with time-spaces |
US10282072B2 (en) | 2007-08-22 | 2019-05-07 | 9224-5489 Quebec Inc. | Method and apparatus for identifying user-selectable elements having a commonality thereof |
US20110035388A1 (en) * | 2008-01-02 | 2011-02-10 | Samsung Electronics Co., Ltd. | Method and apparatus for recommending information using a hybrid algorithm |
US20120159320A1 (en) * | 2008-03-07 | 2012-06-21 | Mathieu Audet | Method of managing attributes and system of managing same |
US9652438B2 (en) | 2008-03-07 | 2017-05-16 | 9224-5489 Quebec Inc. | Method of distinguishing documents |
US9733801B2 (en) | 2011-01-27 | 2017-08-15 | 9224-5489 Quebec Inc. | Expandable and collapsible arrays of aligned documents |
US9588646B2 (en) | 2011-02-01 | 2017-03-07 | 9224-5489 Quebec Inc. | Selection and operations on axes of computer-readable files and groups of axes thereof |
US11281843B2 (en) | 2011-09-25 | 2022-03-22 | 9224-5489 Quebec Inc. | Method of displaying axis of user-selectable elements over years, months, and days |
US11080465B2 (en) | 2011-09-25 | 2021-08-03 | 9224-5489 Quebec Inc. | Method of expanding stacked elements |
US10289657B2 (en) | 2011-09-25 | 2019-05-14 | 9224-5489 Quebec Inc. | Method of retrieving information elements on an undisplayed portion of an axis of information elements |
US10558733B2 (en) | 2011-09-25 | 2020-02-11 | 9224-5489 Quebec Inc. | Method of managing elements in an information element array collating unit |
US11513660B2 (en) | 2012-06-11 | 2022-11-29 | 9224-5489 Quebec Inc. | Method of selecting a time-based subset of information elements |
US10845952B2 (en) | 2012-06-11 | 2020-11-24 | 9224-5489 Quebec Inc. | Method of abutting multiple sets of elements along an axis thereof |
US10180773B2 (en) | 2012-06-12 | 2019-01-15 | 9224-5489 Quebec Inc. | Method of displaying axes in an axis-based interface |
US20170344045A1 (en) * | 2012-07-31 | 2017-11-30 | Causam Energy, Inc. | System, method, and data packets for messaging for electric power grid elements over a secure internet protocol network |
US20170338693A1 (en) * | 2012-07-31 | 2017-11-23 | Causam Energy, Inc. | System, method, and apparatus for electric power grid and network management of grid elements |
US9069646B2 (en) * | 2012-12-17 | 2015-06-30 | Sap Se | Automatic documentation generator |
US20140173562A1 (en) * | 2012-12-17 | 2014-06-19 | Martina Rothley | Automatic Documentation Generator |
US10671266B2 (en) | 2017-06-05 | 2020-06-02 | 9224-5489 Quebec Inc. | Method and apparatus of aligning information element axes |
Also Published As
Publication number | Publication date |
---|---|
US9218431B2 (en) | 2015-12-22 |
US9047386B2 (en) | 2015-06-02 |
US8515998B1 (en) | 2013-08-20 |
US7139974B1 (en) | 2006-11-21 |
US7386792B1 (en) | 2008-06-10 |
US20130226947A1 (en) | 2013-08-29 |
US9128934B2 (en) | 2015-09-08 |
US20130346433A1 (en) | 2013-12-26 |
US20120233529A1 (en) | 2012-09-13 |
US20160154878A1 (en) | 2016-06-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7386792B1 (en) | System and method for collecting, storing, managing and providing categorized information related to a document object | |
US7111232B1 (en) | Method and system for making document objects available to users of a network | |
US9043352B1 (en) | Method for searching document objects on a network | |
US7702521B2 (en) | Method for users of a network to provide other users with access to link relationships between documents | |
US7792967B2 (en) | Method and system for sharing and accessing resources | |
US6487557B1 (en) | Network-access management system and method applied to network and computer program product including computer program recorded on storage medium for creating display data | |
US7831917B1 (en) | Method, system, and graphical user interface for identifying and communicating with meeting spots | |
US7548914B2 (en) | System and method for providing active tags | |
US7711611B2 (en) | Wish list | |
TWI477992B (en) | Method, system and computer-readable medium for third-party information overlay on search results | |
US20090210391A1 (en) | Method and system for automated search for, and retrieval and distribution of, information | |
US7917866B1 (en) | Method, system, and graphical user interface for meeting-spot-related online communications | |
US7389241B1 (en) | Method for users of a network to provide other users with access to link relationships between documents | |
KR20030047885A (en) | System and method for obtaining and storing information for deferred browsing | |
JP4843428B2 (en) | Information processing apparatus, information processing method, and information processing system | |
KR20100094021A (en) | Customized and intellectual symbol, icon internet information searching system utilizing a mobile communication terminal and ip-based information terminal | |
KR20090080561A (en) | Techniques for including collection items in search results | |
US8171424B1 (en) | Method, system, and graphical user interface for meeting-spot maps for online communications | |
US7146407B2 (en) | Data synchronization mechanism for information browsing systems | |
KR100707969B1 (en) | Method for providing the sympathy of the classified objects having the property and computer readable medium processing the method | |
JP2002099568A (en) | Www server having function of automatically generating book mark for personal use | |
US20030078929A1 (en) | Data synchronization mechanism for information browsing systems | |
JP2001357055A (en) | Method and system for managing bookmark | |
US20030078993A1 (en) | Data synchronization mechanism for information browsing systems | |
KR20010081897A (en) | Method for fulfilling searching service by providing additional information for several service in the computer network system and computer-readable medium for recording the method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BASCOM RESEARCH, LLC, VIRGINIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BASCOM, THOMAS L.;REEL/FRAME:029073/0289 Effective date: 20120709 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: BASCOM, THOMAS L., VIRGINIA Free format text: PURCHASE AGREEMENT - 10% INTEREST CONVEYED;ASSIGNOR:BASCOM LINKING INTELLECTUAL PROPERTY, LLC;REEL/FRAME:037255/0971 Effective date: 20151209 |
|
AS | Assignment |
Owner name: DSS TECHNOLOGY MANAGEMENT, INC., VIRGINIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BASCOM RESEARCH, LLC;REEL/FRAME:038786/0362 Effective date: 20160525 |