The present invention relates generally to software applications for annotating web pages. In particular, the present invention is a system and method for use by web site operators to facilitate user posting of public and private comments at a web site.
Although web site blogs that provide commentary on a variety of topics are very popular, they typically emphasize the web site owner's or blogger's comments. Many bloggers do not allow readers to comment on posts for fear of the readers submitting inappropriate comments. As a result, reader interaction with blogs and other web sites is limited. If readers were permitted to post private rather than public comments, bloggers could allow readers to comment on posts without the fear that inappropriate comments will be read by other readers. However, blogs and web sites typically do not support posting of private comments.
Another problem with current web technology is that adapting blogs and other web pages for annotations and comments is very cumbersome and difficult. Even if a blogger would like to invite his or her readers to comment on the blogger's posts, adapting the blog or other web site content to allow such interactivity is difficult and requires programming skills. Details related to web page layout and content can also make it difficult to adapt pages for comments. Because of the difficulties in facilitating comments on individual web pages, many web site operators maintain a single blog for the entire site. Comments regarding unrelated content appear in the same area of the web site simply because a blog is supported in only one area of the site that users can visit to post. If a blogger would like to support private as well as public comments, additional programming is required to allow such postings on web pages. There is a need for a software system and method that allows web site operators to easily adapt web pages to facilitate posting of comments at web sites. There is also a need for a system and method that supports posting of private as well as public user comments at sites.
The present invention is a software system and method that allows web site operators to easily adapt web page content to support posting of public and private user comments at web sites. Web site operators can support interactivity with their web site visitors centering on public reader comment areas as well as private visitor journals.
Reader comment areas according to the present invention allow web site visitors to comment on the content found on the particular web pages where the reader comment areas appear. Examples of such pages are ones containing articles, newsletters, photographs, quotes, news commentaries, etc. An important design feature of the present invention is the ability to create a “mini-blog” out of every single content-oriented web page of an owner's web site. Reader comment areas are added easily to all types of web pages and in fact, may be added to literally thousands of web pages, requiring just a minute or two of time for each new page.
To prevent publication of inappropriate comments, the web site owner or an administrator has a variety of controls to maintain the privacy of comments. One such control is a “hide incoming posts” control that allows the administrator to review posts before permitting them to be published. Other controls allow the administrator to hide or delete posts that have already been published. Every reader who makes a comment on a web page enabled according to the present invention may be automatically added to the web site owner's subscriber list (if the web site owner so chooses, and if the reader approves via typical double opt-in methods). Every end user who makes a comment on the web site owner's site also has the opportunity to sign up for a personal journal. This option further enrolls the end user to return to the owner's site and become part of the web site owner's community and subscriber list.
A variety of personal journal features are also supported. Personal journal features include keeping comments private for the user's personal viewing only, posting comments to other public web pages containing the specialized reader comment areas, and creating a unique page with the user's own individualized URL that mimics the public web page to which he or she has posted a comment. The end user comment is always displayed most prominently (e.g., at the top of all other comments entered by other end users, and/or highlighted in some way such as in bold or in a different color or any number of other highlighting techniques that may be selected. The end user may also be permitted to choose to eliminate all the other comments posted on the original web page so his or her comment is the only one featured.)
Additionally, from the personal journal page, the end user may print all or pre-selected journal entries in various design formats (such as mini-books or ebooks or on-line or off-line greeting cards), create a public blog out of posts he or she chooses to make public under a private domain or sub-domain name, create his or her own web pages or a web site using additional formatting features or simply publish his or her posts as text under a private domain or sub-domain name, enter audio comments to a journal, enter video comments to a journal, create podcasts of these audio and video comments, and make actual saleable products of these written, audio and/or video posts, which will be available collectively on a common commercial web site.
The features and functionality of the present invention are made available to web site owners in a “prepackaged” and ready-made, ready-to-install system. The present invention allows web site owner to avoid hiring programmers to create each individual feature. The system enables the web site owner to be the administrator of the entire system. The administrator may perform the following functions:
The present invention facilitates eliciting reader comments to engage readers in the blogger's or web site owner's writings. It also provides greater search engine optimization resulting from specialized keyword utilization associated with the incoming posts, as well as list building advantages.
FIGS. 23A-23OO are a flow diagram illustrating the web site administration, user administration, and end user components for an example embodiment of the present invention;
Referring to
Referring to
Referring to
Referring to
Referring to
Posting data fields are in the middle section of the screen. The end user may provide a title for his or her post in a post title field 180. A comment field 182 is where the end user enters his or her actual post. An enlarge writing area option 184 results in a popup that provides the end user with an enlarged writing area to compose his or her comment. The end user can adjust this writing area to any comfortable size including full screen. It automatically adjusts the writing area field proportionately to whatever size the end user desires the page to appear on his screen. A choose icon pull down menu 186 allows the end user to choose from the icons the administrator entered in the “add icons for posts” field of the administrator page creator screen (
Post fields appear at the bottom of the screen. The newsletter/miscellaneous title 194 listing reflects which newsletter or miscellaneous page the end user selected previously. The title listing reflects the title the end user chose from post title field 196. The comment field has the content entered previously by the end user. Next to the comment field is the icon selected by the end user. The identifier reflects the name option selected previously 198.
Referring to
Each end user post may be displayed in a separate portion of the screen. The icon the end user selected appears with his or her post 210. The title 210 selected by the end user is displayed as well as the end user's comment 210. Also shown is the identifier 212 (name, initials, user name) selected by the end user. A publish option 214 enables the administrator to allow the end user's post to appear on the display page if the administrator had previously chosen to hide this post either via a hide post option 216, or the hide new posts option above 208. The hide post option 216 enables the administrator to hide any individual end user post from appearing on a display page. The entire post appears with a grey background when it is hidden so the administrator knows at a glance it is hidden. A delete post option 218 permanently deletes the post. An email-a-friend option 220 results in a popup that enables the administrator to email the end user who wrote the post (e.g., to thank them for posting, to ask permission to quote his or her post, etc.)
Posts may be selected (e.g., by selecting a checkbox next to each post) for printing, to appear in an ebook, or for other functions. A post counter may be used to tell the administrator how many total posts were received for each newsletter or miscellaneous web page.
Reader comments areas defined by administrators and comments entered by end users are hosted on a server and stored in database remote from the administrator's web site server. An “iFrame” substitution process is used to allow this remote hosting of the reader comments. The iFrame substitution of the present invention provides a simple “window” to the server and database where all reader comments are actually entered, stored, and posted. However, they are also a part of the local site. It is important for the actual text of the posts to be a part of the local site (i.e., the administrator's web site) rather than just being reflected there so that the administrator gets the benefit of using incoming posts for search engine optimization. The administrator does not receive this benefit if the text in the posts is not actually on the local site and remains solely in the remote database.
Referring to
The display page comprises a reader comment input section 230. The reader enters comment data in this section of the display page. In the title field 232, the end user provides a title for his or her post. The end user enters his or her actual comment in the comment field 236. The end user can select an icon from the icon pull down menu 238 which has the icons the administrator originally uploaded in the administrator page creator. The end user enters a name in the name field and an email address 240. The end user can select an option for publishing his or her full name, first name only, or initials 242. The user name options from the personal journal page are not available on the display page because end users coming to the display page may not yet have signed up for a personal journal, and therefore, do not have a user name.
If the end user then chooses an option to create a personal journal 244, Javascript Show-Hide Layer Code allows the appearance of the otherwise invisible user name and password fields 248. The end user chooses a use name for logging onto his or her personal journal and a password. These user name and password fields 248 remain hidden if the end user chooses a “just post my comments below without creating my personal journal” option 246. The end user's comments are posted with the selection of a post comments option 250.
The display page also comprises a reader comment output section 252. The post fields appear at the bottom of the display page in the reader comment output section. The most recent end user's post is posted first on the page rather then last. The advantage of publishing the most recent end user's post first is the immediate gratification it gives the end user of being “headlined,” versus stuck at the bottom of the webpage. An RSS option 254 enables web site visitors to create RSS feeds of the incoming posts on his or her own web sites if they like, or to view in other RSS-viewable places (e.g., choosing different RSS feeds is one of various preferences available to Yahoo.com's users). This option support further promotion of the administrator's web site.
The icon 256 for the post reflects the icon selected by the user from the icon pull down menu 238. The title 258 reflects the title entered by the end user previously in the title field 232. The comment 260 reflects the content entered by the end user in the comment field 236. The identifier 262 reflects the end user's choice for identifying his or her posts 242. Because the posts here also reflect posts made by end users in their personal journals, the identifier may reflect the end user's user name per that option uniquely available to end users posting from a personal journal. The date and time labels 264 reflect the date and the time the end user's post was made. The keyword label 266 reflects the keywords the administrator chose in the administrator page creator screen (
A tell-a-friend option 268 displayed next to each post results in a tell-a-friend popup. This feature enables the end user to email any post to multiple friends, which brings more traffic to the site. A rating option 268 may also be added next to each post to allow the end user and other visitors to rate every post on the page (e.g., 1=I didn't like this post; 2=I liked this post; and 3=I loved this post!). This option enables the administrator to create a contest for web page postings. As an incentive to get end users to write more posts, the administrator can award prizes to the top-winning end user poster for a given period of time.
Referring to
Referring to
Referring to
A “look-at-me page” may be virtually identical to the display page of—
A contest generator page hosts the results of end-user post rankings using web site visitors' ratings of the various posts via the ratings feature on the display page of
A “create blog” feature allows each end user to create a blog that displays just his or her posts, and just the ones they choose to make public via checkmark boxes that appear next to each of his or her posts. The end user performs the functions of a “secondary administrator,” and promotes greater use of the primary administrator's web site thereby greatly increasing the primary administrator's traffic.
An ebook feature allows each end user to create an ebook of all his or her unique “look-at-me” pages. The end user chooses which posts to include in the ebook. This feature automatically puts all selected posts into an MS Word format or a pdf. format, per his or her own choosing. It also includes various cover template designs, table of content designs, and overall book designs. The administrator may also be ebook creator by creating ebooks of reader comments. The ebooks may be sold or distributed as a “virtual marketing tool.” End users whose comments appear frequently in an ebook may be inclined to distribute the ebook to others.
An end user greeting card creator feature enables the end user to send his or her posts as virtual greeting cards. This feature may be used in addition to or instead of the tell-a-friend emails and provides another dynamic marketing tool for the administrator's web site.
A comment rotator and emailer feature allows an administrator to rotate posts appearing at the top of each web page. The posts may be rotated daily or more frequently throughout the day. An email may be sent automatically to each particular end user at the time his/her post is headlined. This feature creates a reason for the end user to revisit the web page and to refer friends to it.
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
The end user's comment is displayed in the reader comment output section at the bottom of the screen 376. The comment is displayed 380 along with a time stamp indicating when it was entered. The user may select an option to hide the comment once it has been entered 382. The end user can also choose to see only his or her comment or all of the comments entered by other users 384. Referring to
Technical details related to the category/sub-category feature of the present invention are as follows. AJAX framework (HTML AJAX) controls AJAX functionalities for the present invention. The code<?php $utils->get_category_list(‘slt_category’,“onchange=\“sendSub-category(-this.value);showOther( )\””);?>loads a list of categories in the Manage Sub Category page (manage_sub_category.php) page. A utility class is defined in a classes folder (root_folder/classes/utils.class.php) which is a collection of utility functions. This class has many functions including redirecting and displaying JavaScript message, and listing many other functions. The above function get_category_list( ) is defined in a root_folder/classes/utils.class.php file which will that takes some parameters and lists the all the categories made by the current administrator.
When the selection of items listed in the category dropdown list is changed, an onchange event (onchange=\″sendSub-category(this.value)) is called in this function and this sendSub-cateory(this.value) sends the selected item id to sendSub-category(cat_id) javascript function defined in the current page. After the a value is passed to sendSub-category(cat_id) function and parameter values are passed to the function, it hides the Options Panel and sub category Panel if the passed parameter value is 0 . Otherwise it creates an instance of object of review class defined in root_folder/ajax_classes/review.class.php.
After the instance of object of review class is created using javascript, a last line of code defined in the function sendSub-cateogry(cat_id) registers a php function loadSub-category(cat_id,″) defined in review.class.php class file. While using HTML_AJAX framework in our program we have to register our user defined class to the ReviewServer defined in root_folder/ajax_claases/auto_server.class.php. After the loadSub-category(cat_id) is called this function connects to the database and loads all the sub-categories under selected category and return to the JavaScript. Again there is a function called loadSub-category: function(result) which is a part of HTML_AJAX. This retrieves the HTML and reloads the sub category drop down box. The options panel is also visible.
Referring to FIGS. 23A-23OO, a flow diagram illustrating the web site administration, user administration, and end user components for an example embodiment of the present invention is shown. The present invention comprises an iFrame substitution solution to provide features and functionality related to reader comment areas. The embedded technologies in the iFrame substitution solution include HTML, PHP, Javascript, MySQL, CSS, and AJAX methods.
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to
Referring to FIG. 23AA, beginning at 452, the following steps are performed.
Referring to FIG. 23BB, beginning at 454, the following steps are performed.
Referring to FIG. 23CC, beginning at 456, the following steps are performed.
Referring to FIG. 23DD, beginning at 458, the following steps are performed.
Referring to FIG. 23EE, beginning at 460, the following steps are performed.
Referring to FIG. 23FF, beginning at 462, the following steps are performed.
Referring to FIG. 23GG, beginning at 464, the following steps are performed.
Referring to FIG. 23HH, beginning at 464, the following steps are performed.
Referring to FIG. 23II, beginning at 468, the following steps are performed.
Referring to FIG. 23JJ, beginning at 470, the following steps are performed.
Referring to FIG. 23KK, beginning at 472, the following steps are performed.
Referring to FIG. 23LL, beginning at 474, the following steps are performed.
Referring to FIG. 23MM, beginning at 476, the following steps are performed.
Referring to FIG. 23NN, beginning at 480, the following steps are performed.
Referring to FIG. 23OO, beginning at 482, the following steps are performed.
The present invention comprises an “iFrame solution” to add reader comment areas to web pages. The “iFrame solution” of the present invention may be implemented with an existing web page framework. In the following example, the www.wealthysoul.com domain is used. An iFrame is a webpage element that creates an inline frame that contains another document. An iFrame functions as a document within a document, or like a floating FRAME. It just loads another HTML document within the <iframe> tags. Syntax <IFRAME> . . . </IFRAME>. The following example uses the IFRAME element and an HTML fragment to create a frame containing the page sample.htm as shown in
The embedded technologies into iFrame solution are HTML, PHP, Javascript, MySQL, CSS and AJAX methods.
Referring to
The iFrame substitution solution of the present invention allows the reader comments to be stored at a web site remote from the administrator's hosting web site resulting in many benefits for the web site administrator and the readers who enter comments on the administrator's web site. While certain exemplary embodiments are described in detail above, the scope of the application is not to be considered limited by such disclosure, and modifications are possible without departing from the spirit of the invention as evidenced by the following claims.
This application is a continuation of the United States Application for Patent that was filed on Feb. 5, 2013 and assigned Ser. No. 13/759,693, which application is a continuation of the United States Application for Patent that was filed on Jun. 15, 2007 and assigned Ser. No. 11/818,912 and issued as U.S. Pat. No. 8,402,357 on Mar. 19, 2013, which application claims the benefit of the filing date of U.S. Provisional Application 60/813,982 which was filed on Jun. 15, 2006. Each of these applications are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5794039 | Guck | Aug 1998 | A |
6297819 | Furst | Oct 2001 | B1 |
6421724 | Nickerson | Jul 2002 | B1 |
6606581 | Nickerson et al. | Aug 2003 | B1 |
6748449 | Dutta | Jun 2004 | B1 |
6928392 | Nickerson | Aug 2005 | B2 |
7032005 | Mathon et al. | Apr 2006 | B2 |
7060532 | Takyu et al. | Jun 2006 | B2 |
7062532 | Sweat et al. | Jun 2006 | B1 |
7085820 | Nickerson | Aug 2006 | B1 |
7130885 | Chandra et al. | Oct 2006 | B2 |
7162471 | Knight et al. | Jan 2007 | B1 |
7203704 | Stern et al. | Apr 2007 | B1 |
7370285 | Nickerson et al. | May 2008 | B1 |
7478121 | Nickerson et al. | Jan 2009 | B1 |
7529795 | Arav | May 2009 | B2 |
7548930 | Kobza et al. | Jun 2009 | B2 |
7548957 | Wichmann et al. | Jun 2009 | B1 |
7552383 | Morris et al. | Jun 2009 | B2 |
7558828 | Panzer | Jul 2009 | B1 |
7734610 | Rakowski et al. | Jun 2010 | B2 |
7774378 | Nelson | Aug 2010 | B2 |
7810027 | Bendik | Oct 2010 | B2 |
7827487 | Nickerson et al. | Nov 2010 | B1 |
7970887 | Nickerson | Jun 2011 | B2 |
8024668 | Nickerson | Sep 2011 | B2 |
8041805 | Nickerson | Oct 2011 | B2 |
8112403 | Repasi et al. | Feb 2012 | B2 |
8275796 | Spivack et al. | Sep 2012 | B2 |
8396891 | Tsao | Mar 2013 | B2 |
8601060 | Barkley et al. | Dec 2013 | B2 |
8606845 | Dickinson et al. | Dec 2013 | B2 |
8694490 | Mandel et al. | Apr 2014 | B2 |
8700704 | Arav | Apr 2014 | B2 |
20020046244 | Bimson et al. | Apr 2002 | A1 |
20020062368 | Holtzman et al. | May 2002 | A1 |
20020073160 | Purcell | Jun 2002 | A1 |
20020085030 | Ghani | Jul 2002 | A1 |
20020087660 | Martin et al. | Jul 2002 | A1 |
20020111838 | Welbourne | Aug 2002 | A1 |
20020126708 | Skog et al. | Sep 2002 | A1 |
20020174179 | Toyota et al. | Nov 2002 | A1 |
20030167315 | Chowdhry et al. | Sep 2003 | A1 |
20030204490 | Kasriel | Oct 2003 | A1 |
20040019688 | Nickerson et al. | Jan 2004 | A1 |
20040021686 | Barberis | Feb 2004 | A1 |
20040028212 | Lok et al. | Feb 2004 | A1 |
20040075681 | Anati | Apr 2004 | A1 |
20040163050 | Matter | Aug 2004 | A1 |
20040172405 | Farran | Sep 2004 | A1 |
20040205547 | Feldt et al. | Oct 2004 | A1 |
20050086188 | Hillis et al. | Apr 2005 | A1 |
20050198299 | Beck et al. | Sep 2005 | A1 |
20050228742 | McHale et al. | Oct 2005 | A1 |
20050240618 | Nickerson et al. | Oct 2005 | A1 |
20050240623 | Kobza et al. | Oct 2005 | A1 |
20050271037 | Habaguchi et al. | Dec 2005 | A1 |
20060010194 | Inage | Jan 2006 | A1 |
20060059160 | Smola et al. | Mar 2006 | A1 |
20060173775 | Cullen et al. | Aug 2006 | A1 |
20060173985 | Moore | Aug 2006 | A1 |
20060178910 | Eisenberger et al. | Aug 2006 | A1 |
20060230021 | Diab et al. | Oct 2006 | A1 |
20060240851 | Washburn | Oct 2006 | A1 |
20060242554 | Gerace et al. | Oct 2006 | A1 |
20060253365 | Langshur et al. | Nov 2006 | A1 |
20060265368 | Nickerson et al. | Nov 2006 | A1 |
20060284744 | Shotland | Dec 2006 | A1 |
20060294215 | Noble et al. | Dec 2006 | A1 |
20070043617 | Stein et al. | Feb 2007 | A1 |
20070191040 | Kadar et al. | Aug 2007 | A1 |
20070282904 | Mitchell | Dec 2007 | A1 |
20090006549 | Singh et al. | Jan 2009 | A1 |
Number | Date | Country |
---|---|---|
10131571 | Jan 2003 | DE |
EP 0940960 | Sep 1999 | FR |
2366497 | Mar 2002 | GB |
WO0109738 | Feb 2001 | WO |
WO2004015897 | Jun 2004 | WO |
Entry |
---|
Fiedler, Sebastian, et al, “Navigating Personal Information Repositories with Weblog Authoring and Concept Mapping”, Jan. 2005, University of Augsburg, Augsburg, Germany, pp. 302-325, ISBN 3-540-26921-5 978-3-540-26921-2. |
www.cocomTitle: Www.cocomment.com; (web.archive.org) Pub. Date: Feb. 16, 2006 (Capture date on archive.org) Bibliographic Info: URL:https://web.archive.org/web/20060216105050/http://www.co comment.com/learnmore Located Via: www.archive.orgment.com (web.archive.org) published Feb. 16, 2. |
Title: Xara online feedback form (web.archive.org) Pub. Date: Feb. 7, 2005 (Capture date on archive.org) Bibliographic Info: URL:https://web.archive.org/web/20050207180348/http://www.xa raonline.com/home/applications/ffo—home.htm Located Via: www.archive.org. |
Shozu: shozu one—click camera phone image sharing service adds support for personal blogs, 2—way messages & more shoot. click. share. anywhere M2 Presswire Apr. 2006 Found via Proquest Technology Collection ProQuest document ID 443614005 Document URL http://search.proquest.com/docview/443614005?accountid=142944. |
Gathering customer feedback via the Internet: instruments and prospects Scott E. Sampson Industrial Management & Data Systems 1998, Issue 2, pp. 71-82 Located via Google Scholar. |
GuestWorld Debuts With 500,000 Web Sites, Oct. 28, 1997, Business Wire. |
Number | Date | Country | |
---|---|---|---|
20140298160 A1 | Oct 2014 | US |
Number | Date | Country | |
---|---|---|---|
60813982 | Jun 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13759693 | Feb 2013 | US |
Child | 14267299 | US | |
Parent | 11818912 | Jun 2007 | US |
Child | 13759693 | US |