CA2342488A1 - The system and method for private virtual web - Google Patents
The system and method for private virtual web Download PDFInfo
- Publication number
- CA2342488A1 CA2342488A1 CA002342488A CA2342488A CA2342488A1 CA 2342488 A1 CA2342488 A1 CA 2342488A1 CA 002342488 A CA002342488 A CA 002342488A CA 2342488 A CA2342488 A CA 2342488A CA 2342488 A1 CA2342488 A1 CA 2342488A1
- Authority
- CA
- Canada
- Prior art keywords
- private
- pvw
- hypertext links
- page
- url
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/957—Browsing optimisation, e.g. caching or content distillation
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The technical field of the present invention is directed to a method and computer system for setting up and using a personalized platform - Private Virtual Web to make users more efficiently browse World Wide Web. Problems with existing World Wide Web technologies include that users have to browse websites by the hypertext link structures set up by operators. The present invention provides a method and system for users of World Wide Web to browse web sites by the link structures set up by themselves. The present invention creates at least one private hypertext links page corresponding to a URL, and presents the private hypertext links page with the public web page addressed by the URL concurrently within a web browser. By editing and using the private hypertext links pages, users can set up their own link structures based on World Wide Web. A Private Virtual Web consists of private hypertext links pages and relevant data directed to an application.
Description
THE SYSTEM AND METHOD FOR PRIVATE VIRTUAL WEB
Field of the Invention This invention relates to the technical field of setting up and using a personalized platform to browse the World Wide Web. More specifically, the invention is directed to a method and computer system for setting up and using Private Virtual Web to make users more efficiently browse and get information from Internet.
t o Background of the Invention The Internet is a vast computer network, consisting of many smaller networks and individual computers that, when connected, span the entire globe.
The World Wide Web and the Internet are widely used for the dissemination of information contained in web pages. The World Wide Web is the Internet' s multimedia information retrieval system. In the Web environment, client machines effect transactions to Web servers using the Hypertext Transfer Protocol (HTTP), which is a known application protocol providing users access to files (e.g., text, graphics, images, sound, video, etc.) using a standard page 2o description language known as Hypertext Markup Language (HTML). A web page is a file in a computer system containing information for display or other presentation to a user. Web pages are typically written HTML and contain references to associated text, graphics, and other multimedia files. A system for accessing web pages includes several parties and components. A
content author creates web pages of information. A server system stores the web pages, including their content and possibly executable scripts embedded in the web pages, and accepts requests for access to the web pages. A client system executing a browser program generates requests for web pages that are sent to the server system. The client system and the server system are typically connected via a computer network (e.g., the Internet or a company Intranet). The server system retrieves the requested web pages and forwards them to the browser 3o program on the client system for viewing by the user of the client system.
One important aspect of an HTML document is the connectors or "h ypertext links" to connect to other parts of the text or even to other documents on the same or remote servers. In the Internet paradigm, a network path to a server is identified by a so-called Uniform Resource Locator (URL) having a special syntax for defining a network connection. Use of a Web browser (e.g., Netscape Navigator or Microsoft Internet Explorer) at a client machine involves specification of a hypertext link via the URL. In response, the client makes a request to the web server identified in the hypertext link and, in return, receives a document or other object formatted according to HTML. On a Web browser the links are part of ordinary text but are distinctively displayed. Each link is associated with a corresponding URL.
Hence, a user may "jump" to other portions of the same document or to another document by selecting a link and causing the browser to transmit a request for a new Web page through the associated URL.
Elements of web pages can be divided into two types: hypertext links and other elements (e.g., text, graphics, video, voice). The hypertext links serve as backbone to how the World Wide Web operates, and the other elements constitute nodes to be connected. Those two types of elements constitute web pages. In a typical web page, hypertext links are embedded in the other elements in a mixed way .
In the prior art, as a browser application is moved from one URL to another URL at the user's 2o direction, the content addressed by the active URL will be presented in the browser application.
URL always addresses unique data content, such as a web page.
Facing web sites that double and triple in size every six months, web sites operators and users feel more difficult to efficiently get the required information from Internet.
Web sites are setup by operators following their own styles and requirements (e.g., business flows, product groups).
Those sites make it easy for operators to maintain or browse, but users always feel difficult to use those sites because structures of those web sites are complex and confusing. Users spend much time on browsing irrelevant content. Actually many users only need parts of web site but whole web site. They also want to change structure of the web site to their preferred structures 3o so they can browse the web site more efficiently. But it's impossible for operators to provide
Field of the Invention This invention relates to the technical field of setting up and using a personalized platform to browse the World Wide Web. More specifically, the invention is directed to a method and computer system for setting up and using Private Virtual Web to make users more efficiently browse and get information from Internet.
t o Background of the Invention The Internet is a vast computer network, consisting of many smaller networks and individual computers that, when connected, span the entire globe.
The World Wide Web and the Internet are widely used for the dissemination of information contained in web pages. The World Wide Web is the Internet' s multimedia information retrieval system. In the Web environment, client machines effect transactions to Web servers using the Hypertext Transfer Protocol (HTTP), which is a known application protocol providing users access to files (e.g., text, graphics, images, sound, video, etc.) using a standard page 2o description language known as Hypertext Markup Language (HTML). A web page is a file in a computer system containing information for display or other presentation to a user. Web pages are typically written HTML and contain references to associated text, graphics, and other multimedia files. A system for accessing web pages includes several parties and components. A
content author creates web pages of information. A server system stores the web pages, including their content and possibly executable scripts embedded in the web pages, and accepts requests for access to the web pages. A client system executing a browser program generates requests for web pages that are sent to the server system. The client system and the server system are typically connected via a computer network (e.g., the Internet or a company Intranet). The server system retrieves the requested web pages and forwards them to the browser 3o program on the client system for viewing by the user of the client system.
One important aspect of an HTML document is the connectors or "h ypertext links" to connect to other parts of the text or even to other documents on the same or remote servers. In the Internet paradigm, a network path to a server is identified by a so-called Uniform Resource Locator (URL) having a special syntax for defining a network connection. Use of a Web browser (e.g., Netscape Navigator or Microsoft Internet Explorer) at a client machine involves specification of a hypertext link via the URL. In response, the client makes a request to the web server identified in the hypertext link and, in return, receives a document or other object formatted according to HTML. On a Web browser the links are part of ordinary text but are distinctively displayed. Each link is associated with a corresponding URL.
Hence, a user may "jump" to other portions of the same document or to another document by selecting a link and causing the browser to transmit a request for a new Web page through the associated URL.
Elements of web pages can be divided into two types: hypertext links and other elements (e.g., text, graphics, video, voice). The hypertext links serve as backbone to how the World Wide Web operates, and the other elements constitute nodes to be connected. Those two types of elements constitute web pages. In a typical web page, hypertext links are embedded in the other elements in a mixed way .
In the prior art, as a browser application is moved from one URL to another URL at the user's 2o direction, the content addressed by the active URL will be presented in the browser application.
URL always addresses unique data content, such as a web page.
Facing web sites that double and triple in size every six months, web sites operators and users feel more difficult to efficiently get the required information from Internet.
Web sites are setup by operators following their own styles and requirements (e.g., business flows, product groups).
Those sites make it easy for operators to maintain or browse, but users always feel difficult to use those sites because structures of those web sites are complex and confusing. Users spend much time on browsing irrelevant content. Actually many users only need parts of web site but whole web site. They also want to change structure of the web site to their preferred structures 3o so they can browse the web site more efficiently. But it's impossible for operators to provide
2 web sites fitting every user's requirements on content and structure. How to implement a full personalized solution for users to personalize every web site is becoming a tough problem to rapid growing Internet industry.
s Most enterprises transfer their mission critical business applications (e.g., ERP, CRM) from other platforms to web-based platform since the World Wide Web becomes a consistent environment of business. The hypertext links among web pages in the applications control the business flows implemented in the applications. When reengineering the business flows, the enterprises have to change those hypertext links embedded in web pages even though other elements in web pages don't need to be changed. Facing the challenge of rapid changing business and more competitors, enterprises have to change their business flows flexibly and rapidly to win the game. The enterprises need a powerful platform that can flexibly and rapidly deploy and change the business flows based on hypertext links in web-based applications.
1s In the web server tier, many organizations are using Web content management (WCM), thereby operators can easily take control of Web content to achieve their business goals. But as a web server based solution, WCM still sets up web sites with fixed structure following operators' style. In the prior art it's impossible to set up web sites following every user's style, users don't have their own personalized solu tion to browse and get information from web sites.
In the user tier, almost all hypertext systems provide a facility for providing easy and fast access to a user's favorite pages on the web. Such a facility is often referred to as a hotlist or a bookmark list. Existing systems depict the bookmark list as textual list of web page titles (called "bookmarks") in a pull-down menu on a web browser. A typical pull-down menu also permits 2s users to add new bookmarks to the list, update the titles associated with the web pages, and display the updated lists. As a client side personalized solution, bookmarks record discrete web pages, and can't change user's view to the structure of the Internet. It's a limited personalized tool.
s Most enterprises transfer their mission critical business applications (e.g., ERP, CRM) from other platforms to web-based platform since the World Wide Web becomes a consistent environment of business. The hypertext links among web pages in the applications control the business flows implemented in the applications. When reengineering the business flows, the enterprises have to change those hypertext links embedded in web pages even though other elements in web pages don't need to be changed. Facing the challenge of rapid changing business and more competitors, enterprises have to change their business flows flexibly and rapidly to win the game. The enterprises need a powerful platform that can flexibly and rapidly deploy and change the business flows based on hypertext links in web-based applications.
1s In the web server tier, many organizations are using Web content management (WCM), thereby operators can easily take control of Web content to achieve their business goals. But as a web server based solution, WCM still sets up web sites with fixed structure following operators' style. In the prior art it's impossible to set up web sites following every user's style, users don't have their own personalized solu tion to browse and get information from web sites.
In the user tier, almost all hypertext systems provide a facility for providing easy and fast access to a user's favorite pages on the web. Such a facility is often referred to as a hotlist or a bookmark list. Existing systems depict the bookmark list as textual list of web page titles (called "bookmarks") in a pull-down menu on a web browser. A typical pull-down menu also permits 2s users to add new bookmarks to the list, update the titles associated with the web pages, and display the updated lists. As a client side personalized solution, bookmarks record discrete web pages, and can't change user's view to the structure of the Internet. It's a limited personalized tool.
3 Summary of the Invention It is therefore the primary object of the present invention to provide ways in which to implement fully web personalized systems and methods - Private Virtual Web (PVW). As used in this description and in the appended claim, the phrase "PVW (Private Virtual Web)"
means a computer system which is implemented by the methods of the present invention or which is described through the present invention. Through PVW platform, users can make the World Wide Web to be viewed and browsed as their preferred structures. Because the invention is implemented based on the World Wide Web, the word "Web" is used. The means of expressing "private" is through its antonym, "p ublic" . In the present invention, we call web servers in current World Wide Web "public web servers" and web pages in those public web servers "public web pages" . As used in this description and in the appended claim, the phrase "public web page" means a web page which exists in a web server in World Wide Web. As used in this description and in the appended claim, the phrase "private web page" means a web page which doesn't exist in a web server in World Wide Web. The "public" means those web servers and web pages are openly accessible to all authorized users. "Pri vate" means PVW
is not openly accessible to all the users of corresponding public web servers. PVW users are the users of corresponding public web servers with PVW authorization. "Pri vate" also means PVWs are implemented on the basis of private hypertext links pages that are private web pages embracing 2o hypertext links. As used in this description and in the appended claim, the phrase "private hypertext links page" means a private web page which embraces hypertext links.
The private hypertext links pages and relevant data are stored in PVW clients or PVW
servers. PVWs are set up according to different applications (e.g., sales, marketing, provisioning, services) and can be set different authorization levels to give PVW users different access privileges. The term "Virtual " means PVW uses different implementation method from the World Wide Web implementation method to simulate the World Wide Web. PVW doesn't change the structure of World Wide Web, but in PVW user's view, the structure of World Wide Web seems to be changed. The present invention provides methods to change view of Internet users on structure of webs by creating private hypertext links pages for corresponding URLs. On the Internet or 3o Intranet, the methods of the present invention provide private virtual environments for users to
means a computer system which is implemented by the methods of the present invention or which is described through the present invention. Through PVW platform, users can make the World Wide Web to be viewed and browsed as their preferred structures. Because the invention is implemented based on the World Wide Web, the word "Web" is used. The means of expressing "private" is through its antonym, "p ublic" . In the present invention, we call web servers in current World Wide Web "public web servers" and web pages in those public web servers "public web pages" . As used in this description and in the appended claim, the phrase "public web page" means a web page which exists in a web server in World Wide Web. As used in this description and in the appended claim, the phrase "private web page" means a web page which doesn't exist in a web server in World Wide Web. The "public" means those web servers and web pages are openly accessible to all authorized users. "Pri vate" means PVW
is not openly accessible to all the users of corresponding public web servers. PVW users are the users of corresponding public web servers with PVW authorization. "Pri vate" also means PVWs are implemented on the basis of private hypertext links pages that are private web pages embracing 2o hypertext links. As used in this description and in the appended claim, the phrase "private hypertext links page" means a private web page which embraces hypertext links.
The private hypertext links pages and relevant data are stored in PVW clients or PVW
servers. PVWs are set up according to different applications (e.g., sales, marketing, provisioning, services) and can be set different authorization levels to give PVW users different access privileges. The term "Virtual " means PVW uses different implementation method from the World Wide Web implementation method to simulate the World Wide Web. PVW doesn't change the structure of World Wide Web, but in PVW user's view, the structure of World Wide Web seems to be changed. The present invention provides methods to change view of Internet users on structure of webs by creating private hypertext links pages for corresponding URLs. On the Internet or 3o Intranet, the methods of the present invention provide private virtual environments for users to
4 browse Internet or Intranet and get information from Internet or Intranet. In the PVW
environments, Internet or Intranet users don't need to browse webs following the web structures set up by web operator anymore. Since those PVWs follow users' styles, users can more efficiently browse Internet or Intranet and get information from Internet or Intranet.
It is another more particular object of the present invention to implement more structured view of webs by using private hypertext links pages to separate hypertext links from the other elements of web pages virtually. In PVW environment, hypertext links in public web pages are extracted as templates to create corresponding private hypertext links pages.
As the private to copies, hypertext links of the public webs can be clearly separated from the other elements of the webs. Through processing those private copies, users can get more structured view of webs.
For those organizations running web-based business applications in Internet or Intranet, the present invention provides a way to more efficiently reengineer and remodel business flows.
These and other improvements are set forth in the following detailed description. For a better understanding of the present invention with advantages and features, refer to the description and to the drawings.
2o Brief Desciription of the Drawings The foregoing and the other objects, features and advantages of the present invention will be better understood from the following detailed description of the preferred embodiments of the present invention with reference to the accompanying drawings in which:
Figure 1 is a diagrammatic representation of the World Wide Web;
Figure 2 is an example links structure of public web site;
Figure 3 illustrates the corresponding relationship among URL, public hypertext link and public web page;
3o Figure 4 illustrates the two types of the elements in a web page;
Figure 5 is an example links structure of PVW;
environments, Internet or Intranet users don't need to browse webs following the web structures set up by web operator anymore. Since those PVWs follow users' styles, users can more efficiently browse Internet or Intranet and get information from Internet or Intranet.
It is another more particular object of the present invention to implement more structured view of webs by using private hypertext links pages to separate hypertext links from the other elements of web pages virtually. In PVW environment, hypertext links in public web pages are extracted as templates to create corresponding private hypertext links pages.
As the private to copies, hypertext links of the public webs can be clearly separated from the other elements of the webs. Through processing those private copies, users can get more structured view of webs.
For those organizations running web-based business applications in Internet or Intranet, the present invention provides a way to more efficiently reengineer and remodel business flows.
These and other improvements are set forth in the following detailed description. For a better understanding of the present invention with advantages and features, refer to the description and to the drawings.
2o Brief Desciription of the Drawings The foregoing and the other objects, features and advantages of the present invention will be better understood from the following detailed description of the preferred embodiments of the present invention with reference to the accompanying drawings in which:
Figure 1 is a diagrammatic representation of the World Wide Web;
Figure 2 is an example links structure of public web site;
Figure 3 illustrates the corresponding relationship among URL, public hypertext link and public web page;
3o Figure 4 illustrates the two types of the elements in a web page;
Figure 5 is an example links structure of PVW;
5 Figure 6 illustrates the corresponding relationship among URL, public web page, public hypertext link, private hypertext links page and private hypertext link;
Figure 7 is a diagram of 2-Tier PVW;
Figure 8 is a diagram of 3-Tier PVW;
Figure 9 is an example of a PV W browser interface;
Figure 10 is an example structure of a PVW database;
Figure 11 is a flow chart representation of the present invention;
Figure 12 illustrates a further special application of PVW;
Figure 13 illustrates an operational view of an Enterprise Resource planning application io example interface within a PVW browser;
Figure 14 illustrates an operational view of the Enterprise Resource planning application example interface with the private presenting sub-window within the PVW
browser;
Figure 15 illustrates an operational view of the "New PVW" window with the PVW
browser;
Figure 16 illustrates an operational view of the PVW browser after the new PVW
is created;
Figure 17 illustrates an operational view of the private hypertext links is being selected in the PVW browser;
Figure 18 illustrates an operational view of the selected private hypertext links are being 2o drag-and-dropped into the recycle bin button in the PVW browser;
Figure 19 illustrates an operational view of the PVW browser after the selected private hypertext links are deleted;
Figure 20 illustrates an operational view of the PVW browser after all irrelevant private hypertext links are deleted;
Figure 21 illustrates an operational view of the PVW browser after the public hypertext link is selected;
Figure 22 illustrates an operational view of the PVW browser is shown when the selected public hypertext link is drag-and-dropped into the active private hypertext links page;
Figure 23 illustrates an operational view of the PV W browser after the selected public 3o hypertext link is drag-and-dropped;
Figure 7 is a diagram of 2-Tier PVW;
Figure 8 is a diagram of 3-Tier PVW;
Figure 9 is an example of a PV W browser interface;
Figure 10 is an example structure of a PVW database;
Figure 11 is a flow chart representation of the present invention;
Figure 12 illustrates a further special application of PVW;
Figure 13 illustrates an operational view of an Enterprise Resource planning application io example interface within a PVW browser;
Figure 14 illustrates an operational view of the Enterprise Resource planning application example interface with the private presenting sub-window within the PVW
browser;
Figure 15 illustrates an operational view of the "New PVW" window with the PVW
browser;
Figure 16 illustrates an operational view of the PVW browser after the new PVW
is created;
Figure 17 illustrates an operational view of the private hypertext links is being selected in the PVW browser;
Figure 18 illustrates an operational view of the selected private hypertext links are being 2o drag-and-dropped into the recycle bin button in the PVW browser;
Figure 19 illustrates an operational view of the PVW browser after the selected private hypertext links are deleted;
Figure 20 illustrates an operational view of the PVW browser after all irrelevant private hypertext links are deleted;
Figure 21 illustrates an operational view of the PVW browser after the public hypertext link is selected;
Figure 22 illustrates an operational view of the PVW browser is shown when the selected public hypertext link is drag-and-dropped into the active private hypertext links page;
Figure 23 illustrates an operational view of the PV W browser after the selected public 3o hypertext link is drag-and-dropped;
6 Figure 24 illustrates an operational view of the new window notifying saving the active private hypertext links page;
Figure 25 illustrates an operational view of the PVW browser after it changes back to browse mode;
s Figure 26 illustrates an operational view of the PVW browser 22 when all public hypertext links in the public web page 7 are disabled.
DETAILED DESCRIPTION OF THE INVENTION
1o To make it easier to understand the preferred embodiments, figure 1 to figure 4 illustrate current diagrams and situation of Internet, Intranet and the World Wide Web. Figure 1 illustrates a typical World Wide Web connectivity diagram. Web server 1 is a computer with associated programs that sends data over the Internet 3 or Intranet 4 to a matching web client 2 having a browser capable of interpreting the data. The data is referred to as a web page.
is Figure 2 illustrates an example public web links structure. URL 6 has a corresponding Public web page 7. The public web page 7 includes public hypertext links 5. And each of those public hypertext links 5 indicates one specific URL 6.
2o Figure 3 further illustrates the relationship among URL 6, public web page
Figure 25 illustrates an operational view of the PVW browser after it changes back to browse mode;
s Figure 26 illustrates an operational view of the PVW browser 22 when all public hypertext links in the public web page 7 are disabled.
DETAILED DESCRIPTION OF THE INVENTION
1o To make it easier to understand the preferred embodiments, figure 1 to figure 4 illustrate current diagrams and situation of Internet, Intranet and the World Wide Web. Figure 1 illustrates a typical World Wide Web connectivity diagram. Web server 1 is a computer with associated programs that sends data over the Internet 3 or Intranet 4 to a matching web client 2 having a browser capable of interpreting the data. The data is referred to as a web page.
is Figure 2 illustrates an example public web links structure. URL 6 has a corresponding Public web page 7. The public web page 7 includes public hypertext links 5. And each of those public hypertext links 5 indicates one specific URL 6.
2o Figure 3 further illustrates the relationship among URL 6, public web page
7 and public hypertext link 5. URL 6 typically has one corresponding public web page 7.
Public web page 7 includes multiple public hypertext links 5 and each of those hypertext links 5 indicates one specific URL 6.
2s Figure 4 illustrates the two types of elements in public web page 7. Public web page 7 includes public hypertext links 5, text 8, graphics 9, form 10, video 11, JAVA applet, images, sound and so on. The elements of public web page 7 can be divided into two types: public hypertext links 5 and the other elements 12. Public hypertext links 5 serve as the backbone of Web and the other elements 12 as the nodes of Web.
THE PREFERRED EMBODIMENTS
The preferred embodiments of the present invention herein are generally described within the Internet context as a typical HTTP environment. The methods and systems of the present s invention are, however, equally applicable to an Intranet or other networks based on HTTP.
Referring now to the figures 5 through 26.
Referring now to Figure 5, an example links structure in a PVW is shown.
Comparing to the structure showing an example public web links structure in Figure 2, the links structure in current Figure shows the most important change made in PVW environment. In a PVW, a URL
6 can have a corresponding private hypertext links page 14 except a corresponding public web page 7. The private hypertext links page 14 includes private hypertext links 16 and each of those private hypertext links 16 indicates to one specific URL 6.
15 Referring now to Figure 6, the relationship among URL 6, public web page 7, public hypertext link 5, private hypertext links page 14 and private hypertext link 16 in PVW
environment is shown. Comparing to the relationship shown in Figure 3, the relationship in current Figure additionally shows the private hypertext links page 14 and the private hypertext link 16 and their relationships with the other three elements. In PVW, a URL 6 typically can have one 2o corresponding private hypertext links page 14 per PVW except one corresponding public web page 7. Public web page 7 can include multiple public hypertext links 5 and each of those hypertext links 5 indicates to one corresponding URL 6. Private hypertext links page 14 can include multiple private hypertext links 16 and each of those private hypertext links 16 indicates to one corresponding URL 6.
Referring now to Figure 7, a graphical illustration of the 2-Tier Private Virtual Web. 2-Tier PVW consists of web server tier 18 and PVW client tier 20. Current World Wide Web has similar 2-Tier structure, web server tier and web client tier. The web server tier 18 of PVW is composed of web server 1 and Internet 3 and Intranet 4. The web server tier 18 is the same in 3o PVW environment as in current World Wide Web environment. The PVW client tier 20 is s different from web client tier in current World Wide Web environment. The PVW
client tier consists of PVW clients 21. The PVW client 21 is a web client with additional PVW functions and features. The PVW client 21 is composed of PVW browser 22, private hypertext links page store 23 and PVW data store 24. Because PVW is implemented in PVW client tier 20 in 2-Tier PVW, 2-Tier PVW can also be called "Client-based PVW". PVW browser 22 is a web browser with PVW functions. As used in this description and in the appended claims, the phrase "private hypertext links page store" means a store which stores private hypertext links pages.
The private hypertext links page store 23 could be files, file folders or databases. As used in this description and in the appended claims, the phrase "PVW data store" means a store which stores relational records of PVW. The relational record 26 is a record storing relationship among users, PVWs, URLs and private hypertext links pages. PVW data store 24 can be files or databases .
Referring now to Figure 8, a graphical illustration of the 3-Tier Private Virtual Web.
Comparing to 2-Tier PVW, 3-Tier PVW has one more Tier - PVW Server Tier 28. In 3-Tier PVW, web server tier 18 is the same as in 2-Tier PVW, but PVW Client 21 in PVW
client tier only consists of PVW browser 22. PVW server 29 in PVW server tier 28 holds private hypertext links page store 23 and PVW data store 24. Private hypertext links page store 23 is a server-based store to store private hypertext links pages 14. The store 23 could be files, file 2o folders or databases. PVW data store 24 is a server-based store to store relational records 26.
Implemented in Client-Server structure, 3-Tier PVW can also be called "Client-Server Based PVW".
PVW browser 22, private hypertext links page store 23 and PVW data store 24 are three main components to implement PVW. PVW browser 22, which interacts with the other two components, is the main user interface in PVW environment. It can be looked as presentation layer of PVW. Private hypertext links page store 23 and PVW data store 24 are main data storage for PVW, and can be looked as data storage layer of PVW.
Implemented in different structures, 2-Tier PVW and 3-Tier PVW can therefore be used in different scenarios. In 2-Tier PVW, PVW browser 22, private hypertext links page store 23 and PVW data store 24 co-locate in PVW client. Since whole PVW process is implemented in PVW
client 21 and PVW client 21 can only hold small amount data storage, 2-Tier PVW is an ideal solution for individual users to set up small independent PVWs. In 3-Tier PVW, PVW browser 22 locates in PVW clients 21 as the interface for users, Private hypertext links page store 23 and PVW data store 24 locate in PVW server 29 as centralized data storage. In this Client-Server model, PVW client 21 serves as single role - interface, and PVW server 29 hold centralized and shared data storage. PVW clients interact with PVW server to implement PVW.
Based on a Client-Server model, 3-Tier PVW is an ideal solution for business to set up distributed PVWs.
In recent years, Enterprises transfer their mission critical business applications (e.g., ERP, CRM) to web platform by using web-related technologies (e.g., Java). By 3-Tier PVW, enterprises can easily implement different business flows for different occupations on the basis of those existing web-based applications. 3-Tier PVW is a powerful platform to reengineer business flows flexibly.
Referring now to Figure 9, PVW browser 22 is a web browser with additional PVW
functions and features. Comparing to other kinds of web browsers, PVW browser 22 has an additional private presenting sub-window 30. PVW browser 22 has two main presenting sub-windows:
2o private presenting sub-window 30 and public presenting sub-window 32. The private hypertext links page 14 of the active PVW corresponding to the active URL 6 is presented in private presenting sub-window 30, public web page 7 corresponding to the active URL 6 is presented in public presenting sub-window 32. Address bar is used to input and present URL
6. PVW tabs 34 in private presenting sub-window 30 represent different PVW folders or PVWs used by the active user. When one of those PVW tabs 34 is clicked to be active, the represented PVW
becomes the active PVW in PVW browser 22.
Primary tab 35 is a special tab that doesn't represent any PVW. When the Primary tab becomes active, primary private hypertext links page corresponding to the active URL 6 is presented in 3o private presenting sub-window 30. Primary private hypertext links page, which is created by extracting all public hypertext links 5 embraced in the corresponding public web page 7, is a special private hypertext links page. Primary private hypertext links page changes as the change of the hypertext links 5 in corresponding public web page 7. Primary private hypertext links page is used as a template to create corresponding private hypertext links pages for different PVWs. Primary tab 35 is used when users want to use primary private hypertext links page that holds all hypertext links of the corresponding public web page.
PVW browser has two modes: Browse mode and Edit mode. Browse mode is the mode by which users use PVW browser to browse PVWs. Under browse mode, the private hypertext links pages 14 of the active PVW corresponding to the active URL 6 is presented in private presenting sub-window 30, the public web page 7 corresponding to the active URL 6 is presented in public presenting sub-window 32. When the active URL 6 changes, both the private hypertext links page 14 presented and the public web page 7 presented change accordingly.
When the active PVW changes, the private hypertext links page 14 presented changes accordingly. Under edit mode, users can use edit functions (e.g., cut, copy, paste and drag-and-drop) to add hypertext links in private hypertext links page and remove hypertext links from private hypertext links page 14. Under edit mode, the private presenting sub-window 30 can be locked, which means the private hypertext links page 14 in the private presenting sub-window 30 doesn' t change following the change of the active URL 6. But the public web page 7 2o changes following the change of the active URL 6. In this way, the private hypertext links page can be added hypertext links from other public web pages except corresponding public web page by drag-and-drop.
Referring now to Figure 10, PVW data store 24 typically can be implemented as PVW data store databases. PVW data store databases include tables that store records recording users profile, security information and relationships among users, PVWs, URLs and Private hypertext links pages. Figure 10 is an example relational database structure of a PVW
data store database.
Referring now to Figure 11, a flow chart of the present invention is generally shown in 40. The 3o method starts at 41 and creates and names a new PVW 42. A new PVW is created with the orientation to a new application. For example, a data network engineer does some research on Gigabit Ethernet switch. Facing different information from different web sites, the engineer can create a PVW named "Gigabit Ethernet switch" and put all interesting hypertext link structures in this PVW. After setting up this PVW, the engineer can easily find Gigabit Ethernet switch information next time. For another example, IT department can extract all cost-related link structures from web sites of finance department to create a PVW named "Cost"
shared by finance department. The creator can give users in finance department various authority to use this PVW and even give them change privilege to change this PVW according to their requirements. In a typical PVW scenario, an individual user can also set up a PVW under 1o his/her name and put his/her favorite link structures in the World Wide Web into this PVW.
After said PVW is created, a check is made to determine if it needs a corresponding PVW folder 44. If said PVW needs a corresponding PVW folder, the method continues to set the folder for the PVW 46. As used in this description and in the appended claim, the phrase "PVW folder"
means a folder which represents a conglomerate of PVWs. PVW users can put related PVWs in a folder to make it easy to manage those PVWs. For example, a PVW folder named "Netw ork Equipment" includes several PVWs named "Ethernet Switch", "VPN", "ATM Switch", "Frame Relay", " Terabit Core Router" etc. A PVW folder can have sub-folders or be sub-folder of other PVW folder. A PVW with a corresponding PVW folder is presented with the 2o PVW folder in PVW browser. If said PVW doesn't have PVW folder, the method skips over step 46 to step 48. The PVW without corresponding PVW folder is presented independently in PVW browser.
Home page of said PVW is set 48. Every PVW has a unique home page that is the start page when the PVW becomes active in PVW browser. As used in this description and in the appended claim, the phrase "home page of PVW" means a web page which is the start point of the PVW. A specific URL indicates the home page of PVW. The URL can be changed when users want to set a new home page for PVW. Users can click home page button or menu option to go to home page of PVW in PVW browser as well.
Next, all hypertext links embraced in the public web page addressed by a URL
are extracted to create a primary private hypertext links page 50. Primary private hypertext links page includes all hypertext links in the corresponding public web page. Primary private hypertext links page is used as a template to create corresponding private hypertext links pages for different PVWs.
A check is made to determine if said primary private hypertext links page needs to be stored 52.
If stored copy of primary private hypertext links page is needed, said primary private hypertext links page is stored 54. Otherwise, the method skips over step 54. The content of primary private hypertext links page changes as the changes of the corresponding public web page's to content. Primary private hypertext links page implemented without stored copy is recommended since primary private hypertext links page can be created dynamically when it is needed.
A check is made to determine if a private hypertext links page needs to be created corresponding to a user, said PVW and said URL S5. If it needs to be created, the private hypertext links page is created for said user, said PVW and said URL by using said primary private hypertext links page as template 56. Otherwise, the method skips over steps 56, 57, 58, 60, 62 and 64 to step 66. Said private hypertext links page can be changed by removing some hypertext links 57 from it and adding some hypertext links 58 to it. A check is made to determine if said private hypertext links page needs to be saved 60. If said private hypertext links page needs to be saved, 2o the method continues to store said private hypertext links page corresponding to said user, said PVW and said URL into a private hypertext links page store 62. In 2-Tier PVW, the private hypertext links page is stored in the private hypertext links page store in a PVW client. In 3-Tier PVW, the private hypertext links page is stored in the private hypertext links page store in a PVW server. A relational record is stored in a PVW data store to record the corresponding 2s relationship among said user, said PVW, said URL and said private hypertext links page 64.
The record includes fields representing said user, said PVW, said URL and said private hypertext links page. In 2-Tier PVW, the relational record is stored in the PVW data store in a PVW client. In 3-Tier PVW, the relational record is stored in the PVW data store in a PVW
server. If said private hypertext links page doesn't need to be saved, the method skips over step 30 62 and 64 to step 66.
A check is made by querying the PVW data store to determine if the private hypertext links page corresponding to the said user, said PV W and said URL exists in the private hypertext links page store 66. If said private hypertext links page exists in the private hypertext links page store, the private hypertext links page store is queried to find said private hypertext links page corresponding to said user, said PVW and said URL 68. The said private hypertext links page is presented in PVW browser with the said public web page addressed by said URL
concurrently 70. If said private hypertext links page doesn't exist in the private hypertext links page store 23, said primary private hypertext links page is presented in PVW browser with said public web 1 o page concurrently 72.
A check is made to determine if the public hypertext links in said public web page need to be disabled 74. Disabling those public hypertext links means those public hypertext links in public presenting sub-window can't be clicked to implement corresponding functions (e.g., transfer to corresponding new URL). By disabling those public hypertext links, the function of hypertext links can only be implemented in the private presenting sub-window in PVW
window. To make PVW interface more clear and structured, users can disable public hypertext links in the public web page in the public presenting sub-window. If the hypertext links in said public web page need to be disabled, the hypertext links in said public web page is disabled 76. Otherwise, the 2o method skips over step 76. The method stops at 78.
The foregoing description is illustration of general components and implementation methods of PVW. Those methods are implemented on the basis of current web server structure and public web page structure. In those methods, the structures of the web servers and public web pages remain the same as before. Figure 12 illustrates a further special application of PVW. In this special application, the structures of web servers and web pages are changed.
Referring now to Figure 12, in current World Wide Web environment 80, URL 6 has unique corresponding public web page 7 in Web server 1. In the further special application of the PVW 82, the public web page 7 in current World Wide Web environment doesn't exist any more. It is split into a 3o unique public content web page 83 and a unique public hypertext links page 85 for corresponding URL 6 in Web server 1. As used in this description and in the appended claim, the phrase "pub lic hypertext links page" means a public web page which only includes all hypertext links for corresponding URL. As used in this description and in the appended claim, the phrase "pub lic content web page" means a public web page which includes all other elements except hypertext links for corresponding URL. In the special application, most steps of the procedure implementing PVW shown in Figure 11 doesn't change except that steps 50, 52 and 54 are invalid because primary private hypertext links page is invalid and replaced by the public hypertext links page 85 in the implementation procedure. In step 56 in Figure 11, the public hypertext links page 85 is used as the template to create private hypertext links page 14 1o for corresponding user, PVW and URL. By implementing the special application of the PVW, the content of the web site change to be more structured. The PVW is implemented based on better support in the special application since primary private hypertext links page doesn't exist any more.
For Figure 13 through Figure 26, an example Enterprise Resource Planning application illustrates the preferred embodiments of the present invention. The Enterprise Resource Planning application includes five functions groups: Enterprise Management, Customer Relationship Management, Marketing & Innovation, Supply Chain Management and Business Support. And each of those functions groups includes several functions. In the example, an 2o accounting staff working for sales department wants to set up a PVW to restructure all hypertext links relevant to accounting for sales department. A consecutive procedure to show basic functions of the PVW will be illustrated in the example.
Referring now to Figure 13, an operational view of an example Enterprise Resource planning application interface is shown within a PVW browser 22. The five functions groups included in the Enterprise Resource Planning application are presented as the public hypertext links of the pubic web page 7 in the public presenting sub-window 32. The functions included in those functions groups are presented as the public hypertext links as well. The active URL 6 is Http://www.pvwsoft.com/erpdemo. The PVW button 101, upon a mouse point and click event, opens a new private presenting sub-window 30.
Referring now to Figure 14, an operational view of the example Enterprise Resource planning application interface is shown with the private presenting sub-window 30 within the PVW
browser 22. When the private presenting sub-window 30 is opened, primary tab 35 is activated s by default. So the primary private hypertext links page 104, which includes all hypertext links in the active public web page 7, is presented in the private presenting sub-window 30. The New button 102, upon a mouse point and click event, opens a new pop-up window titled "New PVW".
to Referring now to Figure 15, an operational view of the "New PVW" window 105 is shown with the PVW browser 22. In the window 105, "Sale Accounting" is inputted into name field 106 as the name of a new PVW. The active URL Htt~://www.pvwsoft.com/erpdemo by default is shown in home page field 108 as the home page of the new PVW. The home page of the new PVW can be changed to another URL. In the window 105, users can create new PVW
folders 15 and add PVWs to an existing PVW folder as well. But in the example the new PVW doesn't have corresponding PVW folder. The OK button 110, upon a mouse point and click event, closes the window 105 and creates the new PVW and a new tab named "Sale Accounting"
representing the new PVW in the private presenting sub-window 30.
2o Referring now to Figure 16, an operational view of the PVW browser 22 is shown after the new PVW is created. The new PVW is the active PVW by default. So the PVW tab representing the new PVW is activated. The primary private hypertext links page 104 corresponding to the active URL 6 is presented in the private presenting sub-window 30 since no private hypertext links page corresponding to the active user, PVW and URL exists. The Edit button 112, upon a 2s mouse point and click event, changes the PVW browser 22 into edit mode and creates a private hypertext links page corresponding to the active URL, PVW and user by copying the primary private hypertext links page.
Referring now to Figure 17, an operational view of the PVW browser 22 in edit mode is shown 3o when some private hypertext links in the private hypertext links page is being selected. The private hypertext links page 14 replaces the primary private hypertext links page in the private presenting sub-window 30. The private hypertext links 16: "E nterprise Management", "Strategic Enterprise Management" and "Business Intelligence" are determined to be irrelevant hypertext links for the active PVW. So those private hypertext links are selected upon a mouse s or keyboard event.
Referring now to Figure 1$, an operational view of the PVW browser 22 in edit mode is shown when the selected private hypertext links are being drag-and-dropped into the recycle bin button 114. After selected in Figure 17, the private hypertext links "Ent erprise Management", "Strategic Enterprise Management" and "Bu siness Intelligence" are deleted from the private hypertext links page 14 by being drag-and-dropped into the recycle bin button 114.
Referring now to Figure 19, an operational view of the PVW browser 22 is shown after the selected private hypertext links are deleted. The selected private hypertext links are deleted from ~s the private hypertext links page 14.
Referring now to Figure 20, an operational view of the PVW browser 22 is shown after all irrelevant private hypertext links are deleted. After determined to be deleted, all irrelevant private hypertext links are removed from the active private hypertext links page 14 by repeating 2o the steps shown in Figure 17 through 19. The private hypertext links also can be deleted by using delete key on keyboard. The public hypertext link "Sales Force Management", upon a mouse point and click event, opens the corresponding public web page in the public presenting sub-window 32.
2s Referring now to Figure 21, an operational view of the PVW browser 22 is shown after the public hypertext link is clicked. The active URL 6 changes from Http://www.pvwsoft.com/erpdemo to Http://www.pvwsoft.com/salesforcedemo. The private hypertext links page 14 in the private presenting sub-window 30 doesn't change since it' s locked in edit mode. The public web page 7 in the public presenting sub-window 32 changes to 3o the public web page corresponding to the active URL
Http://www.pvwsoft.com/salesforcedemo.
m The public hypertext link "Sales Planning/Budgeting" is selected after it is determined to be added to the active private hypertext links page 14.
Referring now to Figure 22, an operational view of the PVW browser 22 is shown when the selected public hypertext link is drag-and-dropped into the active private hypertext links page 14. The public hypertext link "Sales Planning/Budgeting" is drag-and-dropped into the active private hypertext links page 14.
Referring now to Figure 23, an operational view of the PVW browser 22 is shown after the 1o selected public hypertext link is drag-and-dropped. The selected public hypertext link "Sales Planning/Budgeting" is added to the private hypertext links page 14 in the private presenting sub-window 30. The Edit button, upon a mouse point and click event, changes the PVW
browser 22 into browse mode and opens a new window to notify saving the private hypertext links page.
Referring now to Figure 24, an operational view of the new window notifying saving the private hypertext links page is shown. The new window reminds the user to save the private hypertext links page in the private hypertext links page store. The Yes button 116, upon a mouse point and click event, saves the private hypertext links page to the private hypertext links page store.
2o Concurrently, a record storing relationship among the active user, active PVW, active URL and the private hypertext links page is saved into the PVW data store.
Referring now to Figure 25, an operational view of the PVW browser 22 is shown after it changes back to browse mode. The active URL 6 changes back to Ht~://www.~vwsoft.com/erpdemo by default. The pubic web page 7 presented in the public presenting sub-window 32 also changes back to the corresponding public web page. The private hypertext links page is presented in the private presenting sub-window 30 since it exists. The Disable button 118, upon a mouse point and click event, disables all the public hypertext links in the public web page.
Referring now to Figure 26, an operational view of the PVW browser 22 is shown when all public hypertext links in the public web page 7 are disabled. All public hypertext links in the public web page 7 are disabled and don't perform hypertext link functio ns any more.
s The foregoing example is only an operational view example to illustrate the preferred embodiment of the present invention. Those skilled in the art will appreciate the procedure which may vary without departing from the scope and spirit of the present invention.
It should be readily understood that the foregoing description is only illustrative of the present to invention and in particular provides a preferred embodiment of the present invention. Various alternatives and modifications can be devised by those skilled in the art without departing from the spirit of the present invention. Accordingly, the present invention is intended to embrace all such alternatives, modifications and variations which fall within the scope of the appended claims.
Public web page 7 includes multiple public hypertext links 5 and each of those hypertext links 5 indicates one specific URL 6.
2s Figure 4 illustrates the two types of elements in public web page 7. Public web page 7 includes public hypertext links 5, text 8, graphics 9, form 10, video 11, JAVA applet, images, sound and so on. The elements of public web page 7 can be divided into two types: public hypertext links 5 and the other elements 12. Public hypertext links 5 serve as the backbone of Web and the other elements 12 as the nodes of Web.
THE PREFERRED EMBODIMENTS
The preferred embodiments of the present invention herein are generally described within the Internet context as a typical HTTP environment. The methods and systems of the present s invention are, however, equally applicable to an Intranet or other networks based on HTTP.
Referring now to the figures 5 through 26.
Referring now to Figure 5, an example links structure in a PVW is shown.
Comparing to the structure showing an example public web links structure in Figure 2, the links structure in current Figure shows the most important change made in PVW environment. In a PVW, a URL
6 can have a corresponding private hypertext links page 14 except a corresponding public web page 7. The private hypertext links page 14 includes private hypertext links 16 and each of those private hypertext links 16 indicates to one specific URL 6.
15 Referring now to Figure 6, the relationship among URL 6, public web page 7, public hypertext link 5, private hypertext links page 14 and private hypertext link 16 in PVW
environment is shown. Comparing to the relationship shown in Figure 3, the relationship in current Figure additionally shows the private hypertext links page 14 and the private hypertext link 16 and their relationships with the other three elements. In PVW, a URL 6 typically can have one 2o corresponding private hypertext links page 14 per PVW except one corresponding public web page 7. Public web page 7 can include multiple public hypertext links 5 and each of those hypertext links 5 indicates to one corresponding URL 6. Private hypertext links page 14 can include multiple private hypertext links 16 and each of those private hypertext links 16 indicates to one corresponding URL 6.
Referring now to Figure 7, a graphical illustration of the 2-Tier Private Virtual Web. 2-Tier PVW consists of web server tier 18 and PVW client tier 20. Current World Wide Web has similar 2-Tier structure, web server tier and web client tier. The web server tier 18 of PVW is composed of web server 1 and Internet 3 and Intranet 4. The web server tier 18 is the same in 3o PVW environment as in current World Wide Web environment. The PVW client tier 20 is s different from web client tier in current World Wide Web environment. The PVW
client tier consists of PVW clients 21. The PVW client 21 is a web client with additional PVW functions and features. The PVW client 21 is composed of PVW browser 22, private hypertext links page store 23 and PVW data store 24. Because PVW is implemented in PVW client tier 20 in 2-Tier PVW, 2-Tier PVW can also be called "Client-based PVW". PVW browser 22 is a web browser with PVW functions. As used in this description and in the appended claims, the phrase "private hypertext links page store" means a store which stores private hypertext links pages.
The private hypertext links page store 23 could be files, file folders or databases. As used in this description and in the appended claims, the phrase "PVW data store" means a store which stores relational records of PVW. The relational record 26 is a record storing relationship among users, PVWs, URLs and private hypertext links pages. PVW data store 24 can be files or databases .
Referring now to Figure 8, a graphical illustration of the 3-Tier Private Virtual Web.
Comparing to 2-Tier PVW, 3-Tier PVW has one more Tier - PVW Server Tier 28. In 3-Tier PVW, web server tier 18 is the same as in 2-Tier PVW, but PVW Client 21 in PVW
client tier only consists of PVW browser 22. PVW server 29 in PVW server tier 28 holds private hypertext links page store 23 and PVW data store 24. Private hypertext links page store 23 is a server-based store to store private hypertext links pages 14. The store 23 could be files, file 2o folders or databases. PVW data store 24 is a server-based store to store relational records 26.
Implemented in Client-Server structure, 3-Tier PVW can also be called "Client-Server Based PVW".
PVW browser 22, private hypertext links page store 23 and PVW data store 24 are three main components to implement PVW. PVW browser 22, which interacts with the other two components, is the main user interface in PVW environment. It can be looked as presentation layer of PVW. Private hypertext links page store 23 and PVW data store 24 are main data storage for PVW, and can be looked as data storage layer of PVW.
Implemented in different structures, 2-Tier PVW and 3-Tier PVW can therefore be used in different scenarios. In 2-Tier PVW, PVW browser 22, private hypertext links page store 23 and PVW data store 24 co-locate in PVW client. Since whole PVW process is implemented in PVW
client 21 and PVW client 21 can only hold small amount data storage, 2-Tier PVW is an ideal solution for individual users to set up small independent PVWs. In 3-Tier PVW, PVW browser 22 locates in PVW clients 21 as the interface for users, Private hypertext links page store 23 and PVW data store 24 locate in PVW server 29 as centralized data storage. In this Client-Server model, PVW client 21 serves as single role - interface, and PVW server 29 hold centralized and shared data storage. PVW clients interact with PVW server to implement PVW.
Based on a Client-Server model, 3-Tier PVW is an ideal solution for business to set up distributed PVWs.
In recent years, Enterprises transfer their mission critical business applications (e.g., ERP, CRM) to web platform by using web-related technologies (e.g., Java). By 3-Tier PVW, enterprises can easily implement different business flows for different occupations on the basis of those existing web-based applications. 3-Tier PVW is a powerful platform to reengineer business flows flexibly.
Referring now to Figure 9, PVW browser 22 is a web browser with additional PVW
functions and features. Comparing to other kinds of web browsers, PVW browser 22 has an additional private presenting sub-window 30. PVW browser 22 has two main presenting sub-windows:
2o private presenting sub-window 30 and public presenting sub-window 32. The private hypertext links page 14 of the active PVW corresponding to the active URL 6 is presented in private presenting sub-window 30, public web page 7 corresponding to the active URL 6 is presented in public presenting sub-window 32. Address bar is used to input and present URL
6. PVW tabs 34 in private presenting sub-window 30 represent different PVW folders or PVWs used by the active user. When one of those PVW tabs 34 is clicked to be active, the represented PVW
becomes the active PVW in PVW browser 22.
Primary tab 35 is a special tab that doesn't represent any PVW. When the Primary tab becomes active, primary private hypertext links page corresponding to the active URL 6 is presented in 3o private presenting sub-window 30. Primary private hypertext links page, which is created by extracting all public hypertext links 5 embraced in the corresponding public web page 7, is a special private hypertext links page. Primary private hypertext links page changes as the change of the hypertext links 5 in corresponding public web page 7. Primary private hypertext links page is used as a template to create corresponding private hypertext links pages for different PVWs. Primary tab 35 is used when users want to use primary private hypertext links page that holds all hypertext links of the corresponding public web page.
PVW browser has two modes: Browse mode and Edit mode. Browse mode is the mode by which users use PVW browser to browse PVWs. Under browse mode, the private hypertext links pages 14 of the active PVW corresponding to the active URL 6 is presented in private presenting sub-window 30, the public web page 7 corresponding to the active URL 6 is presented in public presenting sub-window 32. When the active URL 6 changes, both the private hypertext links page 14 presented and the public web page 7 presented change accordingly.
When the active PVW changes, the private hypertext links page 14 presented changes accordingly. Under edit mode, users can use edit functions (e.g., cut, copy, paste and drag-and-drop) to add hypertext links in private hypertext links page and remove hypertext links from private hypertext links page 14. Under edit mode, the private presenting sub-window 30 can be locked, which means the private hypertext links page 14 in the private presenting sub-window 30 doesn' t change following the change of the active URL 6. But the public web page 7 2o changes following the change of the active URL 6. In this way, the private hypertext links page can be added hypertext links from other public web pages except corresponding public web page by drag-and-drop.
Referring now to Figure 10, PVW data store 24 typically can be implemented as PVW data store databases. PVW data store databases include tables that store records recording users profile, security information and relationships among users, PVWs, URLs and Private hypertext links pages. Figure 10 is an example relational database structure of a PVW
data store database.
Referring now to Figure 11, a flow chart of the present invention is generally shown in 40. The 3o method starts at 41 and creates and names a new PVW 42. A new PVW is created with the orientation to a new application. For example, a data network engineer does some research on Gigabit Ethernet switch. Facing different information from different web sites, the engineer can create a PVW named "Gigabit Ethernet switch" and put all interesting hypertext link structures in this PVW. After setting up this PVW, the engineer can easily find Gigabit Ethernet switch information next time. For another example, IT department can extract all cost-related link structures from web sites of finance department to create a PVW named "Cost"
shared by finance department. The creator can give users in finance department various authority to use this PVW and even give them change privilege to change this PVW according to their requirements. In a typical PVW scenario, an individual user can also set up a PVW under 1o his/her name and put his/her favorite link structures in the World Wide Web into this PVW.
After said PVW is created, a check is made to determine if it needs a corresponding PVW folder 44. If said PVW needs a corresponding PVW folder, the method continues to set the folder for the PVW 46. As used in this description and in the appended claim, the phrase "PVW folder"
means a folder which represents a conglomerate of PVWs. PVW users can put related PVWs in a folder to make it easy to manage those PVWs. For example, a PVW folder named "Netw ork Equipment" includes several PVWs named "Ethernet Switch", "VPN", "ATM Switch", "Frame Relay", " Terabit Core Router" etc. A PVW folder can have sub-folders or be sub-folder of other PVW folder. A PVW with a corresponding PVW folder is presented with the 2o PVW folder in PVW browser. If said PVW doesn't have PVW folder, the method skips over step 46 to step 48. The PVW without corresponding PVW folder is presented independently in PVW browser.
Home page of said PVW is set 48. Every PVW has a unique home page that is the start page when the PVW becomes active in PVW browser. As used in this description and in the appended claim, the phrase "home page of PVW" means a web page which is the start point of the PVW. A specific URL indicates the home page of PVW. The URL can be changed when users want to set a new home page for PVW. Users can click home page button or menu option to go to home page of PVW in PVW browser as well.
Next, all hypertext links embraced in the public web page addressed by a URL
are extracted to create a primary private hypertext links page 50. Primary private hypertext links page includes all hypertext links in the corresponding public web page. Primary private hypertext links page is used as a template to create corresponding private hypertext links pages for different PVWs.
A check is made to determine if said primary private hypertext links page needs to be stored 52.
If stored copy of primary private hypertext links page is needed, said primary private hypertext links page is stored 54. Otherwise, the method skips over step 54. The content of primary private hypertext links page changes as the changes of the corresponding public web page's to content. Primary private hypertext links page implemented without stored copy is recommended since primary private hypertext links page can be created dynamically when it is needed.
A check is made to determine if a private hypertext links page needs to be created corresponding to a user, said PVW and said URL S5. If it needs to be created, the private hypertext links page is created for said user, said PVW and said URL by using said primary private hypertext links page as template 56. Otherwise, the method skips over steps 56, 57, 58, 60, 62 and 64 to step 66. Said private hypertext links page can be changed by removing some hypertext links 57 from it and adding some hypertext links 58 to it. A check is made to determine if said private hypertext links page needs to be saved 60. If said private hypertext links page needs to be saved, 2o the method continues to store said private hypertext links page corresponding to said user, said PVW and said URL into a private hypertext links page store 62. In 2-Tier PVW, the private hypertext links page is stored in the private hypertext links page store in a PVW client. In 3-Tier PVW, the private hypertext links page is stored in the private hypertext links page store in a PVW server. A relational record is stored in a PVW data store to record the corresponding 2s relationship among said user, said PVW, said URL and said private hypertext links page 64.
The record includes fields representing said user, said PVW, said URL and said private hypertext links page. In 2-Tier PVW, the relational record is stored in the PVW data store in a PVW client. In 3-Tier PVW, the relational record is stored in the PVW data store in a PVW
server. If said private hypertext links page doesn't need to be saved, the method skips over step 30 62 and 64 to step 66.
A check is made by querying the PVW data store to determine if the private hypertext links page corresponding to the said user, said PV W and said URL exists in the private hypertext links page store 66. If said private hypertext links page exists in the private hypertext links page store, the private hypertext links page store is queried to find said private hypertext links page corresponding to said user, said PVW and said URL 68. The said private hypertext links page is presented in PVW browser with the said public web page addressed by said URL
concurrently 70. If said private hypertext links page doesn't exist in the private hypertext links page store 23, said primary private hypertext links page is presented in PVW browser with said public web 1 o page concurrently 72.
A check is made to determine if the public hypertext links in said public web page need to be disabled 74. Disabling those public hypertext links means those public hypertext links in public presenting sub-window can't be clicked to implement corresponding functions (e.g., transfer to corresponding new URL). By disabling those public hypertext links, the function of hypertext links can only be implemented in the private presenting sub-window in PVW
window. To make PVW interface more clear and structured, users can disable public hypertext links in the public web page in the public presenting sub-window. If the hypertext links in said public web page need to be disabled, the hypertext links in said public web page is disabled 76. Otherwise, the 2o method skips over step 76. The method stops at 78.
The foregoing description is illustration of general components and implementation methods of PVW. Those methods are implemented on the basis of current web server structure and public web page structure. In those methods, the structures of the web servers and public web pages remain the same as before. Figure 12 illustrates a further special application of PVW. In this special application, the structures of web servers and web pages are changed.
Referring now to Figure 12, in current World Wide Web environment 80, URL 6 has unique corresponding public web page 7 in Web server 1. In the further special application of the PVW 82, the public web page 7 in current World Wide Web environment doesn't exist any more. It is split into a 3o unique public content web page 83 and a unique public hypertext links page 85 for corresponding URL 6 in Web server 1. As used in this description and in the appended claim, the phrase "pub lic hypertext links page" means a public web page which only includes all hypertext links for corresponding URL. As used in this description and in the appended claim, the phrase "pub lic content web page" means a public web page which includes all other elements except hypertext links for corresponding URL. In the special application, most steps of the procedure implementing PVW shown in Figure 11 doesn't change except that steps 50, 52 and 54 are invalid because primary private hypertext links page is invalid and replaced by the public hypertext links page 85 in the implementation procedure. In step 56 in Figure 11, the public hypertext links page 85 is used as the template to create private hypertext links page 14 1o for corresponding user, PVW and URL. By implementing the special application of the PVW, the content of the web site change to be more structured. The PVW is implemented based on better support in the special application since primary private hypertext links page doesn't exist any more.
For Figure 13 through Figure 26, an example Enterprise Resource Planning application illustrates the preferred embodiments of the present invention. The Enterprise Resource Planning application includes five functions groups: Enterprise Management, Customer Relationship Management, Marketing & Innovation, Supply Chain Management and Business Support. And each of those functions groups includes several functions. In the example, an 2o accounting staff working for sales department wants to set up a PVW to restructure all hypertext links relevant to accounting for sales department. A consecutive procedure to show basic functions of the PVW will be illustrated in the example.
Referring now to Figure 13, an operational view of an example Enterprise Resource planning application interface is shown within a PVW browser 22. The five functions groups included in the Enterprise Resource Planning application are presented as the public hypertext links of the pubic web page 7 in the public presenting sub-window 32. The functions included in those functions groups are presented as the public hypertext links as well. The active URL 6 is Http://www.pvwsoft.com/erpdemo. The PVW button 101, upon a mouse point and click event, opens a new private presenting sub-window 30.
Referring now to Figure 14, an operational view of the example Enterprise Resource planning application interface is shown with the private presenting sub-window 30 within the PVW
browser 22. When the private presenting sub-window 30 is opened, primary tab 35 is activated s by default. So the primary private hypertext links page 104, which includes all hypertext links in the active public web page 7, is presented in the private presenting sub-window 30. The New button 102, upon a mouse point and click event, opens a new pop-up window titled "New PVW".
to Referring now to Figure 15, an operational view of the "New PVW" window 105 is shown with the PVW browser 22. In the window 105, "Sale Accounting" is inputted into name field 106 as the name of a new PVW. The active URL Htt~://www.pvwsoft.com/erpdemo by default is shown in home page field 108 as the home page of the new PVW. The home page of the new PVW can be changed to another URL. In the window 105, users can create new PVW
folders 15 and add PVWs to an existing PVW folder as well. But in the example the new PVW doesn't have corresponding PVW folder. The OK button 110, upon a mouse point and click event, closes the window 105 and creates the new PVW and a new tab named "Sale Accounting"
representing the new PVW in the private presenting sub-window 30.
2o Referring now to Figure 16, an operational view of the PVW browser 22 is shown after the new PVW is created. The new PVW is the active PVW by default. So the PVW tab representing the new PVW is activated. The primary private hypertext links page 104 corresponding to the active URL 6 is presented in the private presenting sub-window 30 since no private hypertext links page corresponding to the active user, PVW and URL exists. The Edit button 112, upon a 2s mouse point and click event, changes the PVW browser 22 into edit mode and creates a private hypertext links page corresponding to the active URL, PVW and user by copying the primary private hypertext links page.
Referring now to Figure 17, an operational view of the PVW browser 22 in edit mode is shown 3o when some private hypertext links in the private hypertext links page is being selected. The private hypertext links page 14 replaces the primary private hypertext links page in the private presenting sub-window 30. The private hypertext links 16: "E nterprise Management", "Strategic Enterprise Management" and "Business Intelligence" are determined to be irrelevant hypertext links for the active PVW. So those private hypertext links are selected upon a mouse s or keyboard event.
Referring now to Figure 1$, an operational view of the PVW browser 22 in edit mode is shown when the selected private hypertext links are being drag-and-dropped into the recycle bin button 114. After selected in Figure 17, the private hypertext links "Ent erprise Management", "Strategic Enterprise Management" and "Bu siness Intelligence" are deleted from the private hypertext links page 14 by being drag-and-dropped into the recycle bin button 114.
Referring now to Figure 19, an operational view of the PVW browser 22 is shown after the selected private hypertext links are deleted. The selected private hypertext links are deleted from ~s the private hypertext links page 14.
Referring now to Figure 20, an operational view of the PVW browser 22 is shown after all irrelevant private hypertext links are deleted. After determined to be deleted, all irrelevant private hypertext links are removed from the active private hypertext links page 14 by repeating 2o the steps shown in Figure 17 through 19. The private hypertext links also can be deleted by using delete key on keyboard. The public hypertext link "Sales Force Management", upon a mouse point and click event, opens the corresponding public web page in the public presenting sub-window 32.
2s Referring now to Figure 21, an operational view of the PVW browser 22 is shown after the public hypertext link is clicked. The active URL 6 changes from Http://www.pvwsoft.com/erpdemo to Http://www.pvwsoft.com/salesforcedemo. The private hypertext links page 14 in the private presenting sub-window 30 doesn't change since it' s locked in edit mode. The public web page 7 in the public presenting sub-window 32 changes to 3o the public web page corresponding to the active URL
Http://www.pvwsoft.com/salesforcedemo.
m The public hypertext link "Sales Planning/Budgeting" is selected after it is determined to be added to the active private hypertext links page 14.
Referring now to Figure 22, an operational view of the PVW browser 22 is shown when the selected public hypertext link is drag-and-dropped into the active private hypertext links page 14. The public hypertext link "Sales Planning/Budgeting" is drag-and-dropped into the active private hypertext links page 14.
Referring now to Figure 23, an operational view of the PVW browser 22 is shown after the 1o selected public hypertext link is drag-and-dropped. The selected public hypertext link "Sales Planning/Budgeting" is added to the private hypertext links page 14 in the private presenting sub-window 30. The Edit button, upon a mouse point and click event, changes the PVW
browser 22 into browse mode and opens a new window to notify saving the private hypertext links page.
Referring now to Figure 24, an operational view of the new window notifying saving the private hypertext links page is shown. The new window reminds the user to save the private hypertext links page in the private hypertext links page store. The Yes button 116, upon a mouse point and click event, saves the private hypertext links page to the private hypertext links page store.
2o Concurrently, a record storing relationship among the active user, active PVW, active URL and the private hypertext links page is saved into the PVW data store.
Referring now to Figure 25, an operational view of the PVW browser 22 is shown after it changes back to browse mode. The active URL 6 changes back to Ht~://www.~vwsoft.com/erpdemo by default. The pubic web page 7 presented in the public presenting sub-window 32 also changes back to the corresponding public web page. The private hypertext links page is presented in the private presenting sub-window 30 since it exists. The Disable button 118, upon a mouse point and click event, disables all the public hypertext links in the public web page.
Referring now to Figure 26, an operational view of the PVW browser 22 is shown when all public hypertext links in the public web page 7 are disabled. All public hypertext links in the public web page 7 are disabled and don't perform hypertext link functio ns any more.
s The foregoing example is only an operational view example to illustrate the preferred embodiment of the present invention. Those skilled in the art will appreciate the procedure which may vary without departing from the scope and spirit of the present invention.
It should be readily understood that the foregoing description is only illustrative of the present to invention and in particular provides a preferred embodiment of the present invention. Various alternatives and modifications can be devised by those skilled in the art without departing from the spirit of the present invention. Accordingly, the present invention is intended to embrace all such alternatives, modifications and variations which fall within the scope of the appended claims.
Claims (52)
1. A method for presenting one private hypertext links page addressed by a URL
(Uniform Resource Locator), comprising the steps of:
presenting one private hypertext links page addressed by a URL with the public web page addressed by said URL concurrently within a WEB Browser.
(Uniform Resource Locator), comprising the steps of:
presenting one private hypertext links page addressed by a URL with the public web page addressed by said URL concurrently within a WEB Browser.
2. A method for storing and presenting at least one private hypertext links page corresponding to a URL (Uniform Resource Locator), comprising the steps of:
storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store;
presenting said private hypertext links page with the public web page addressed by said URL
concurrently within a WEB Browser.
storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store;
presenting said private hypertext links page with the public web page addressed by said URL
concurrently within a WEB Browser.
3. A method for storing and presenting at least one private hypertext links page corresponding to a URL (Uniform Resource Locator), comprising the steps of:
storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a client computer;
presenting said private hypertext links page with the public web page addressed by said URL
concurrently within a WEB Browser.
storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a client computer;
presenting said private hypertext links page with the public web page addressed by said URL
concurrently within a WEB Browser.
4. A method for storing and presenting at least one private hypertext links page corresponding to a URL (Uniform Resource Locator), comprising the steps of:
storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a server;
presenting said private hypertext links page with the public web page addressed by said URL
concurrently within a WEB Browser.
storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a server;
presenting said private hypertext links page with the public web page addressed by said URL
concurrently within a WEB Browser.
5. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store for recording the corresponding relationship between said private hypertext links page and said URL.
6. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store in a client computer for recording the corresponding relationship between said private hypertext links page and said URL.
7. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store in a server for recording the corresponding relationship between said private hypertext links page and said URL.
8. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
9. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store in a client computer for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
10. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store in a server for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
11. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
12. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store in a client computer for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
13. A method according to claim 1, 2, 3 or 4 further comprising the step of storing a relational record in a PVW data store in a server for recording the among said private hypertext links page, said URL, corresponding PVW and corresponding user.
14. A method according to claim 1, 2, 3, 4, 5, 6 or 7 further comprising the step of querying said PVW data store and said private hypertext links page store to find said private hypertext links page corresponding to said URL.
15. A method according to claim 1, 2, 3, 4, 8, 9 or 10 further comprising the step of querying said PVW data store and private hypertext links page store to find said private hypertext links page corresponding to said URL and said PVW.
16. A method according to claim 1, 2, 3, 4, 11, 12 or 13 further comprising the step of querying said PVW data store and private hypertext links page store to find said private hypertext links page corresponding to said URL, said PVW and said user.
17. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 or 16 further comprising the step of extracting hypertext link embraced in the public web page addressed by said URL as a template to create said private hypertext links page.
18. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 or 16 further comprising the step of creating a public hypertext links page and a public content web page corresponding to said URL.
19. A method according to claim 18 further comprising the step of using the public hypertext links page as a template to create said private hypertext links page.
20. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18 or 19 further comprising the step of adding hypertext link to said private hypertext links page.
21. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17 , 18, 19 or 20 further comprising the step of removing hypertext link from said private hypertext links page.
22. A method according to claim 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 or 21 wherein said PVW data store is a database.
23. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21 or 22 wherein said private hypertext links page only comprises hypertext links.
24. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 22 or 23 further comprising the step of setting a home page for the active PVW.
25. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 22, 23 or 24 further comprising the step of setting a PVW folder for the active PVW.
26. A method according to claim 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24 or 25 further comprising the step of disabling hypertext links in said public web page.
27. A computer system for presenting one private hypertext links page addressed by a URL
(Uniform Resource Locator), comprising:
means for presenting one private hypertext links page addressed by a URL with the public web page addressed by said URL concurrently within a WEB Browser.
(Uniform Resource Locator), comprising:
means for presenting one private hypertext links page addressed by a URL with the public web page addressed by said URL concurrently within a WEB Browser.
28. A computer system for storing and presenting at least one private hypertext links page corresponding to a URL (Uniform Resource Locator), comprising:
means for storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store;
means for presenting said private hypertext links page with the public web page addressed by said URL concurrently within a WEB Browser.
means for storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store;
means for presenting said private hypertext links page with the public web page addressed by said URL concurrently within a WEB Browser.
29. A computer system for storing and presenting at least one private hypertext links page corresponding to a URL (Uniform Resource Locator), comprising:
means for storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a client computer;
means for presenting said private hypertext links page with the public web page addressed by said URL concurrently within a WEB Browser.
means for storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a client computer;
means for presenting said private hypertext links page with the public web page addressed by said URL concurrently within a WEB Browser.
30. A computer system for storing and presenting at least one private hypertext links page corresponding to a URL (Uniform Resource Locator), comprising:
means for storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a server;
means for presenting said private hypertext links page with the public web page addressed by said URL concurrently within a WEB Browser.
means for storing at least one private hypertext links page corresponding to a URL in a private hypertext links page store in a server;
means for presenting said private hypertext links page with the public web page addressed by said URL concurrently within a WEB Browser.
31. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store for recording the corresponding relationship between said private hypertext links page and said URL.
means for storing a relational record in a PVW data store for recording the corresponding relationship between said private hypertext links page and said URL.
32. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store in a client computer for recording the corresponding relationship between said private hypertext links page and said URL.
means for storing a relational record in a PVW data store in a client computer for recording the corresponding relationship between said private hypertext links page and said URL.
33. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store in a server for recording the corresponding relationship between said private hypertext links page and said URL.
means for storing a relational record in a PVW data store in a server for recording the corresponding relationship between said private hypertext links page and said URL.
34. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
means for storing a relational record in a PVW data store for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
35. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store in a client computer for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
means for storing a relational record in a PVW data store in a client computer for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
36. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store in a server for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
means for storing a relational record in a PVW data store in a server for recording the relationship among said private hypertext links page, said URL and corresponding PVW.
37. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
means for storing a relational record in a PVW data store for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
38. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store in a client computer for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
means for storing a relational record in a PVW data store in a client computer for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
39. A computer system according to claim 27, 28, 29 or 30 further comprising:
means for storing a relational record in a PVW data store in a server for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
means for storing a relational record in a PVW data store in a server for recording the relationship among said private hypertext links page, said URL, corresponding PVW and corresponding user.
40. A computer system according to claim 27, 28, 29, 30, 31, 32 or 33 further comprising:
means for querying said PVW data store and said private hypertext links page store to find said private hypertext links page corresponding to said URL.
means for querying said PVW data store and said private hypertext links page store to find said private hypertext links page corresponding to said URL.
41. A computer system according to claim 27, 28, 29, 30, 34, 35 or 36 further comprising:
means for querying said PVW data store and private hypertext links page store to find said private hypertext links page corresponding to said URL and said PVW.
means for querying said PVW data store and private hypertext links page store to find said private hypertext links page corresponding to said URL and said PVW.
42. A computer system according to claim 27, 28, 29, 30, 37, 38 or 39 further comprising:
means for querying said PVW data store and private hypertext links page store to find said private hypertext links page corresponding to said URL, said PVW and said user.
means for querying said PVW data store and private hypertext links page store to find said private hypertext links page corresponding to said URL, said PVW and said user.
43. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 or 42 further comprising: means for extracting hypertext link embraced in the public web page addressed by said URL as a template to create said private hypertext links page.
44. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 or 42 further comprising: means for creating a public hypertext links page and a public content web page corresponding to said URL.
45. A computer system according to claim 44 further comprising: means for using the public hypertext links page as a template to create said private hypertext links page.
46. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44 or 45 further comprising: means for adding hypertext link to said private hypertext links page.
47. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45 or 46 further comprising: means for removing hypertext link from said private hypertext links page.
48. A computer system according to claim 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46 or 47 wherein said PVW data store is a database.
49. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47 or 48 wherein said private hypertext links page only comprises hypertext links.
50. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48 or 49 further comprising: means for setting a home page for the active PVW.
51. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49 or 50 further comprising: means for setting a PVW
folder for the active PVW.
folder for the active PVW.
52. A computer system according to claim 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50 or 51 further comprising: means for disabling hypertext links in said public web page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002342488A CA2342488A1 (en) | 2001-04-04 | 2001-04-04 | The system and method for private virtual web |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002342488A CA2342488A1 (en) | 2001-04-04 | 2001-04-04 | The system and method for private virtual web |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2342488A1 true CA2342488A1 (en) | 2002-10-04 |
Family
ID=4168736
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002342488A Abandoned CA2342488A1 (en) | 2001-04-04 | 2001-04-04 | The system and method for private virtual web |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2342488A1 (en) |
-
2001
- 2001-04-04 CA CA002342488A patent/CA2342488A1/en not_active Abandoned
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7127670B2 (en) | Document management systems and methods | |
| US6026433A (en) | Method of creating and editing a web site in a client-server environment using customizable web site templates | |
| US7680856B2 (en) | Storing searches in an e-mail folder | |
| Maglio et al. | Intermediaries personalize information streams | |
| CA2219563C (en) | Browser and plural active url manager for network computers | |
| US6990629B1 (en) | Publishing system for intranet | |
| US7761443B2 (en) | Implementing access control for queries to a content management system | |
| US8522345B2 (en) | Management of hierarchical reference data | |
| US20070239726A1 (en) | Systems and methods of transforming data for web communities and web applications | |
| US6732148B1 (en) | System and method for interconnecting secure rooms | |
| CN100458789C (en) | Method for exchanging portlet configuration data and portal | |
| US20090282062A1 (en) | Data protection and management | |
| US20100115389A1 (en) | Method and System for Publication and Revision or Hierarchically Organized Sets of Static Intranet and Internet Web Pages | |
| JP2004005406A (en) | Method and system for assisting creation of document | |
| US7120870B1 (en) | Method, system, and program for presenting data in a limited display area | |
| US20100192054A1 (en) | Sematically tagged background information presentation | |
| CA2356846A1 (en) | Generalized multi-interfaced extensible content management and delivery system, and on-line calendar | |
| US8849692B1 (en) | Online advertising program enrollment program | |
| US6915341B2 (en) | System for sending messages to all users in a web hosting environment | |
| CA2342488A1 (en) | The system and method for private virtual web | |
| JP3587512B2 (en) | Website creation support system | |
| US20050120299A1 (en) | System and method for creation of a network server application page | |
| Barkowski | Intranets for project and cost management in manufacturing | |
| Aversano et al. | Integrating document and workflow management systems | |
| Uelpenich et al. | Supporting the knowledge life cycle with a knowledge network management system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Dead |