Source: https://patents.google.com/patent/US7089490?oq=7%2C181%2C690
Timestamp: 2018-04-24 05:17:35
Document Index: 684292448

Matched Legal Cases: ['§ 1', '§ 1', '§1', '§ 1', '§ 1', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 1', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4', '§ 4']

US7089490B1 - Identifying navigation bars and objectionable navigation bars - Google Patents
Identifying navigation bars and objectionable navigation bars Download PDF
US7089490B1
US7089490B1 US09727212 US72721200A US7089490B1 US 7089490 B1 US7089490 B1 US 7089490B1 US 09727212 US09727212 US 09727212 US 72721200 A US72721200 A US 72721200A US 7089490 B1 US7089490 B1 US 7089490B1
US09727212
The description of art in this section is not, and should not be interpreted to be, an admission that such art is prior art to the present invention. The Internet and traditional modes of Internet access are introduced in § 1.2.1 below. The growth of information access via portable (e.g., wireless) devices having smaller display screens, as well as challenges related to such access and rendering, are then introduced in § 1.2.2 below.
§1.2.1 The Internet and Traditional Modes of Internet Access
§ 1.2.2 The Growth of Content Access Via, and Content Rendering on, Devices with Smaller Display Screens
§ 1.2.2.1 Challenges Related to Reformatting Content for Rendering on Smaller Display Screens
In the following, an environment in which the present invention may operate is described in § 4.1. Then, functions that may be performed by the present invention are described in § 4.2. Thereafter, exemplary processes, apparatus, methods and data structures that may be used to effect those functions are described in § 4.3. Examples of operations of an exemplary embodiment of the invention are then provided in § 4.4. Finally, some conclusions regarding the present invention are set forth in § 4.5.
A format converter 136 may be used to convert the format of the content. For example, the format converter 136 may be used to convert content authored and formatted with the assumption that it will be rendered on a normal size display screen (e.g., HTML documents), to a format better suited for rendering on a smaller size display screen (e.g., WML documents). An example of such a format converter 136 is a WAP proxy operated by Google, Inc. of Mountain View, Calif. The present invention may reside within the format converter 136. Naturally, the format converter 136 may be a part of the content server 134 and/or may be a client-side utility on the device 110. Further, the various operations of the format converter 136 may be performed at various facilities (e.g., server, proxy, client device, etc.). The present invention may be used as a part of a format converter 136 as described in § 4.3.1 below. Basically, the format converter 136 may include an automated re-authoring process 137. This process 137 may include a navigation bar detection process 138 and an objectionable navigation bar detection process 139 (which may operate on the results of the navigation bar detection process 138).
Having described an environment in which the present invention may operate, functions that may be performed by the present invention are now introduced in § 4.2 below. The foregoing exemplary environment illustrates but one application to which the teachings of the present invention may be applied. The teachings of the present invention have other applications. For example, as noted in § 1.1 above, navigation bar detection may be used for determining whether or not to index text, and whether or not to show text in a snippet search result.
Having introduced various functions which may be performed by the present invention, exemplary processes, architecture, methods and data structures that may be used to perform at least some of those functions are described in § 4.3 below.
§ 4.3 Exemplary Processes, Architecture, Methods and Data Structures
In the following, processes that may be performed by the present invention are introduced in § 4.3.1 below. Then, architecture, methods and data structures that may be used to effect these processes are described in § 4.3.2.
§ 4.3.1 Processes
Exemplary systems on which the navigation bar detection process 138 and/or the objectionable navigation bar detection process 139 may be effected are described in § 4.3.2.1 below. Then exemplary data structures that may be used by these processes, as well as exemplary methods that may be used to effect these processes are described in § 4.3.2.2 below.
Having described processes that may be performed by the present invention, as well as an exemplary device that may be used to effect such processes, exemplary methods and data structures that may be used to perform such processes are described in § 4.3.2.2 below.
This is a <a href=“http://foobar.com”>link</a>.
<li> foo!sample.
Can be represented by the parse tree 400 of FIG. 4.
This section provides three examples which illustrate operations of an exemplary embodiment of the present invention. The SF (San Francisco) Gate Traffic HTML page display, as well as its WML display pages without and with the present invention are illustrated in § 4.4.1 below with reference to FIGS. 6A through 6C. The Microsoft Network (MSN) Love & Relationships HTML page display, as well as its WML display pages without and with the present invention are illustrated in § 4.4.2 below with reference to FIGS. 7A through 7C. Finally, the Open Directory Project HTML page display, as well as its WML display pages without and with the present invention are illustrated in § 4.4.3 below with reference to FIGS. 8A through 8C.
§ 4.4.1 San Francisco Gate Traffic Page Example
§ 4.4.2 MSN Love & Relationships Page Example
As shown in FIG. 7A, a number of navigation bars 710 a through 740 a (actually, component 730 a is not considered a navigation bar, as will be explained below) appear across the top and in the left column of the MSN Love & Relationships HTML page. As shown in FIG. 7B, without the present invention, these navigation bars would be presented in full, as denoted by labels 710 b through 740 b. Finally, as shown in FIG. 7C, an exemplary embodiment of the present invention may determine that some of these navigation bars are objectionable navigation bars. That is, each of the navigation bars 710 a, 720 a, and 740 a is not very small, does not occupy at least a predetermined amount (e.g., 33 percent) of the screen, and is not a descendant of a navigation bar that was disqualified from being classified as an objectionable navigation bar and that has only navigation bars as its children. However, since the hyper-text link “More communities . . . ” has more than a predetermined number of words (e.g., four), the non-anchor word count is incremented. Thus, the navigation bar 730 a is not deemed objectionable. Indeed, since the component 730 a is not anchor-heavy in accordance with one exemplary embodiment of the present invention, it is not even considered to be a navigation bar. This is because it is presumed (by virtue of its word count) that this component has immediate context. As shown in FIG. 7C, each of the objectionable navigation bars, 710 a, 720 a and 740 a, are provided in a single line 710 c, 720 c and 740 c, respectively as a hyper-text link to the individual navigation bars. Notice, however, that since component 730 a was disqualified from being classified as an objectionable navigation bar (or more specifically, was not found to be a navigation bar), it is rendered over multiple lines 730 c, in the same manner as 730 b.
§ 4.4.3 Open Directory Project Page Example
As shown in FIG. 8A, navigation bars 810 a and 820 a appear across the top and in the center, respectively, of the “ODP” HTML page. As shown in FIG. 8B, without the present invention, these navigation bars would be presented in full, as denoted by labels 810 b and 820 b. Finally, as shown in FIG. 8C, an exemplary embodiment of the present invention may determine that one of these navigation bars is an objectionable navigation bars. That is, navigation bar 810 a is not very small, does not occupy at least a predetermined amount (e.g., 33 percent) of the screen, and is not a descendant of a navigation bar that was disqualified from being classified as an objectionable navigation bar and that has only navigation bars as its children. On the other hand, since the navigation bar 820 a takes up more than a predetermined amount (e.g., 33 percent) of the screen, it is disqualified from being deemed objectionable. Further, although each of the column and cell components of the table 820 a may be navigation bars, since each is a descendant of a disqualified navigation bar (i.e., the table) and since that table has only navigation bar components, each of the column and cell components of the table 820 a are disqualified from being classified as an objectionable navigation bar. As shown in FIG. 8C, the objectionable navigation bar 810 a is provided in a single line 810 c as a hyper-text link to the links in the navigation bar. Notice, however, that since component 820 a was disqualified from being classified as an objectionable navigation bar, it is rendered over multiple lines 820 c, in the same manner as 820 b.
US09727212 2000-11-30 2000-11-30 Identifying navigation bars and objectionable navigation bars Active 2022-09-09 US7089490B1 (en)
US09727212 US7089490B1 (en) 2000-11-30 2000-11-30 Identifying navigation bars and objectionable navigation bars
US7089490B1 true US7089490B1 (en) 2006-08-08
ID=36942155
US09727212 Active 2022-09-09 US7089490B1 (en) 2000-11-30 2000-11-30 Identifying navigation bars and objectionable navigation bars
US (1) US7089490B1 (en)
Alfred V. Aho, Ravi Sethi, and Jerffrey D. Ullman, "Compilers Principles, Techniques, and Tools." Mar. 1988, pp. 29-82, and pp. 169-278.
Mr. Cluey, How Can I find out how many hyperlinks there are on a page?, Sep. 10, 2000, <http://www.sqa-test.com/mr<SUB>-</SUB>cluey/countlinks.html>. *
Timothy W. Bickmore and Bill N. Schilit, "Digestor: Device-independent Access to the World Wide Web", Proc. of the Sixth World Wide Web Conference (Downloaded from http://decweb.ethz.ch/WWW6/Technical/Paper177/Paper177.html on Mar. 24, 2000, pp. 1-10).
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TAN, CHADE-MENG;DULITZ, DANIEL;REEL/FRAME:011326/0181;SIGNING DATES FROM 20001116 TO 20001123