Method for converting two-dimensional data into a canonical representation

[0002] This application is a Continuation of U.S. patent application Ser. No 09/394,120 filed Sep. 10, 1999.

[0003] This invention relates to customization of data into a representation suitable for presentation in different formats, including aural and limited visual formats. This invention relates specifically to selection of data in a HyperText Markup Language (HTML) so that it is suited for rendering in another form such as an audio format or a visual format other than the source format.

[0004] A great deal of valuable information is now available in HTML format. However, HTML is primarily designed for access in a specific visual context, namely by means of a graphical user interface of the type designed for use with web browsers. There is a need to make HTML data accessible via other interfaces and readers. The invention herein described is intended to address an important aspect of that need.

[0005] According to the invention, in a computer network system, a method is provided for converting two-dimensional data, particularly information in HTML format, into a canonical representation for rendering in aural or other visual forms wherein each element of interest is selected based on it being part of a mathematically regular expression, namely any expression that can be parsed in a tree. To perform the selection, the container of the element is located, and then the local route of the element within the parsed tree is followed, such that a signature of the element built upon this identification can be constructed and stored for later use in retrieving and rendering the value of the element of interest. As a further refinement of the invention, the method searches for repeated elements and then stores only one of the selected repeated elements, such as the first repeated element.

[0006] It is an important recognition of the present invention that HTML pages can be represented by regular expressions. It is also an important recognition of the invention that only elements need to be selected, and that the actual values of the elements need not be selected, thus permitting the values to be dynamically updated and rendered with the current value.

[0007] The invention will be better understood by reference to the following detailed description in conjunction with the accompanying drawings.

[0008] FIG. 1 is a block diagram of a system according to the invention in which a design tool is employed to select and identify elements HTML pages.

[0009] FIG. 2 is a block diagram illustrating in greater detail the functional relationships of identification, extraction, and translation.

[0010] FIGS. 3A and 3B are a flow chart of a method according to a specific embodiment of the invention.

[0011] FIG. 4 is a block diagram of the relationship of HTML pages and processing triplets.

[0012] Referring to FIG. 1, the invention is explained in the context of a web page in the world web. On the web, an interactive designer tool 10 according to the invention is employed to customize web pages 11 written in a mathematically regular form such as HTML found on a source web site located on a host server 12 after first copying the desired web pages to a storage means 14. The storage means 14 may be a shared persistent store such as a bank of disk drives or other database storage means with persistent storage. By using the designer tool 10 as hereinafter explained, designers can select and identify and customize information from an existing web application without disturbing the source web application. To customize each web page, the designer determines what text and prompts will be rendered to the user, typically a telephone caller if an aural interface is the target, what input data the caller needs to provide for input components, and what order the caller will visit any audio-enabled pages. The designer creates design objects 16. The output of the design process in a particular embodiment is audio metadata. This metadata is represented via a script, specifically herein called collections of elements, which are stored in a database of the storage means 14. The runtime engine hereinafter described uses this script to enable callers to interact with an audio enabled Web site.

[0013] The interactive designer tool 10 in operation acts like a web browser to the host Web server 12 in that it queries and downloads the site's HTML pages 11. The designer/user of the tool 10 decides which pages to audio-enable. For each such page, the designer selects the information that will be rendered at runtime. The designer may create vocal prompts that will ask the caller to provide data for the page's input controls. The designer may further decide what words and phrases will be recognized as proper responses from the caller in response to each prompt. For example, if the Web page has a drop-down selection list for choosing a color, the prompt could be “Please choose red, white, or blue.” The designer specifies that the caller should respond by saying either “red,” “white,” or “blue.”

[0014] The designer also specifies the audio control flow. Within a single Web page, the intra-page flow determines the order that text will be read and which prompts will be issued to the caller. Inter-page flow determines the order that the caller will visit the audio-enabled pages of the site. The audio path followed through a Web site is typically similar to a visual path using a visual Web browser.

[0015] The designer tool 10 is provided with components to create a set of design objects that are kept in the storage means 14. These objects encapsulate all the information necessary to audio-enable a Web site. The designer tool can retrieve these objects from the storage means 14, update them, and save them back into the storage means.

[0016] Upon saving the design objects 16 to the storage means 14, the designer tool 10 invokes a generator 18 to create textual script written in a specification language called herein AML. The AML scripts encode information extracted from the design objects 16 that will be rendered at the run time. Each script contains the IRL of its corresponding Web page. Since the URLs and AML scripts are used at run time. AML scripts are also kept in the storage means 18. The values on the web pages are expressed using AML.

[0017] A. Component selection, identification and customization

[0018] During a design process, component selection and customization consists of the following steps:

[0019] 1. Selection of components from an existing HTML page;

[0020] 2. Identification of selected components from the HTML page;

[0021] 3. Customization of selected components from the HTML page;

[0022] 4. Specification of the selected and customized components via a language that is functionally complete in expressing any selection and customization required.

[0023] The above technique of design is controlled and implemented by the user interface, freeing the designer from the details and the underlying algorithms that are required to correctly select, identify and generate AML scripts.

[0024] B. Selection and identification of components from HTML pages

[0025] FIG. 2 is a conceptual depiction of a runtime system for selecting and rendering data from an HTML page into a target viewing aural rendering language. The web pages 11 are retrieved from the host web server 12 into a translator 20, which in turn retrieves corresponding AML documents 21 from the shared persistent store 14 to produce WML pages 23 and runtime objects 24. After a designer 13 has selected some data, henceforth called a “component” 17, from an HTML page 11 by pointing and clicking on it, the designer tools 10 (FIG. 1 ) automatically generate a unique signature that is subsequently employed by the runtime environment via the runtime engine 22 in order to extract real time data from the HTML page. The runtime engine 22 interfaces with the phone server 26 and the user 28. The signature of the component 11 may comprise one or more of the following:

[0026] 1. The position of the component 17 on the HTML page. Consider the following simple HTML page (This code will produce an HTML page if executed by a web browser operating on a client computer):

[0027] <HTML>

[0028] <table name=“T1”>

[0029] <tr>

[0030] <td width=“13%”>Row 1</td>

[0031] <td width=“13%” align=“center”>r1c2</td>

[0032] <td width=“66%” align=“center”>r1c3</td>

[0033] <td width=“8%”><p align=“center”>r1c4</td>

[0034] <\tr>

[0035] <tr>

[0036] <td>

[0037] <form method=“POST” name=“Form 1” action=“WEBBOT-SELF”>

[0038] <input type=“checkbox” name=“C1” value=“ON”>

[0039] <input type=“radio” value=“V1” checked name=“R1”>

[0040] <input type=“radio” name=“R1” value=“V2”>

[0041] <\form>

[0042] <\td>

[0043] <\tr>

[0044] <\table>

[0045] <\HTML>

[0046] In the above example, if a designer 13 (FIG. 1) selects the entire table T1 and if it is always the first table on the HTML page, then table T1 can identified by its position as “1” with the signature being the symbol representing “the first table on the HTML page.”

[0047] 2. Attributes of the component. Consider the above example in which the second row of table T1 contains form Form 1. If a designer 13 selects Form 1 , then it can be uniquely identified by its action attribute. If this is the only form with value WEBBOT-SELF for this attribute then the identifier of this attribute-value pair becomes the signature of Form 1.

[0048] 3. The ancestors of the component, i.e., the identification of other components on the page which associate with the component. Unlike the foregoing cases where the signature of a component is determined by its one of properties such as position or attribute-value pair, the signature of a component could depend on the identification of other components in the HTML page. Any HTML page can be represented by a regular expression. For example, consider the above HTML page. If the syntax A (B) is used to imply that component A contains B within the scope of component A, then the above simple HTML page can be expressed as HTML (T1 (tr tr (td (Form 1 (C1 V1 R1))))). Furthermore, the identification of a given component in a mathematically regular expression depends on the ancestor components that contain the given component. Consequently, the identification of Form 1 depends on the identification of the enclosing components such as HTML, Table T1 , and so on. By recursively identifying these enclosing elements, one can uniquely identify form Form 1. For example, Form 1 can be uniquely identified by identifying container T1 , second tr in T1 and td with in the second tr. Thus, form Form1's signature is: “look for highest level container HTML, within HTML container look for container table T1 , with in container T1 , look for second row container and with in this container look for first cell which contains form Form1”.

[0049] 4. The “left” siblings of the component, in addition to the identification of its ancestor components. The identification of left siblings is required in the case when one or more left siblings of component repeats a number of times. In this case, it is necessary to identify these left siblings as well. Consider the following HTML page:

[0050] <HTML>

[0051] <table name=“T1”>

[0052] <tr>

[0053] <td width=“13% ”>Row 1</td>

[0054] <td width=“13%” align=“center”>r1c2</td>

[0055] <td width=“66%” align=“center”>r1c3</td>

[0056] <td width=“8%”><p align=“center”>r1c4</td>

[0057] <\tr>

[0058] <tr>

[0059] <td>12.5<\td>

[0060] <td>2.5<\td>

[0061] <td><form method=“POST” name=“Form1” action=“WEBBOT-SELF”>

[0062] <input type=“checkbox” name=“C1” value=“ON”>

[0063] <input type=“radio” value=“V1” checked name=“R1”>

[0064] <input type=“radio” name=“R1” value=“V2”>

[0065] <\form>

[0066] <\td>

[0067] <\tr>

[0068] <\table>

[0069] <\HTML>

[0070] In the above example, the second row of Table T1 contains an initial set of columns that contain digits in them. If the number of these columns varies from one instantiation to the next instantiation of the HTML page, then the identification of form Form1 requires identification of these repeating columns. Thus, can be uniquely identified by identifying container T1 that contains second <tr> which in turn contains repeating <td>'s containing digits (12.5 & 2.5. respectively) and the final <td> containing form Form1. In this case, the signature of component Form1 will be: “look for highest level container HTML, within HTML container look for container table T1 , within container T1 , look for second row container and within this container look for container <td> that repeats ‘n’ times, followed by last container <td> that contains form Form1”.

[0071] 5. A pattern extracted from the HTML page. Consider the previous example. If Form1 is always expected to contain three inputs, then these inputs provide the identification for the form. Thus its signature is: “look for a form that contains three inputs with pattern for the first input is:

[0072] <input type=“checkbox” name=“C1” value=“ON”>.

[0073] the pattern for the second input is:

[0074] <input type=“radio” value=“V1” checked.>”.

[0075] Sometimes the final signature of a component may consist of a combination of methods described above. However, once the signature of the component is established, it is considered the canonical representation, that is, the representation which uniquely and most compactly identifies the component and its associated attributes.

[0076] FIGS. 3A and 3B provide an overview of the identification algorithm that implements the methods according to the invention. The input to the identification algorithm is a component selected by a designer and the output of the algorithm is a script in a target language, a form of markup language, herein called AML (described in the next section) that specifies the complete signature of the selected component.

[0077] First a component of the target language, in this case the AML language, is created for the source language component, in this case the HTML component, as selected by the designer (Step A). Then the values for the attributes of that AML component are obtained or retrieved (Step B). The attributes are tested to determine if the attributes of the components uniquely specify the component in its parent container (Step C) and continues. If not, then a sequence of “left” sibling components is selected such that the sequence followed by the component has a unique signature in the context of the parent container. This sequence is then included in the component specification (Step D). With the uniqueness specification of components, all other components are tested to determine if they need to be specified at this level (Step E). If so, then the specification of the other components of interest at this level is obtained (Step F).

[0078] The following steps focus on uniqueness in the specifications. Having thus gotten the specification of separately specified components, the specifications are each tested to determine if the subject specification is part of a case-type specification at the current level (Step G). If it is, then the specification for all other patterns are retrieved or obtained and an identification switch component (IdSwitch) is defined which is used to enclose the patterns so obtained (Step H). Each specification is thereafter tested to determine if it is part of a repeating pattern (Step I). If so then an identification loop (IdLoop) is defined which encloses the current specification (Step J). The specification is then tested against other specifications on the same HTML page to determine if the specification thus defined is unique (Step L). If not then the type information about the ancestor containers is retrieved and enclosing AML components are defined to reflect the containment property in the HTML page (Step M). The process cycle is repeated for all AML components selected by the designer until done (Step M), finally outputting an AML script (Step O).

[0079] A computer language according to the invention must meet certain requirements in order to specify the identification and customization steps of the selected components. The language used according to the invention herein called AML complies with these requirements. Additionally, this language is also XML compliant.

[0080] In order to correctly express any combination of methods employed for identification (as per the algorithm detailed in connection with FIGS. 3A and 3B), the target markup language must be able to specify the following:

[0081] It should be able to specify HTML elements alone with all their relevant attributes.

[0082] It should be able to describe any regular expression.

[0083] It should have advanced constructs such as switch, case, loop, etc that are useful in describing alternate and repeating components, respectively.

[0084] It should be able describe concatenation of HTML elements.

[0085] It should be able to describe string pattern.

[0086] The AML language according to the invention meets the above requirements. It views an HTML page in terms of its components as herein defined: forms, tables, and lists. A description of a component is split into three parts:

[0087] Identification: The identification is used to identify various components on the HTML page.

[0088] Extraction: The extraction is used to specifies how data is extracted from the components selected.

[0089] Translation: The translation specifies how the components are rendered over the phone.

[0090] All the identifications, extractions, and translations for the components on a given HTML page are collectively placed in a dialogue.

[0091] FIG. 4 is a diagram chart illustrating the association of identification/extraction/translation triplets with each HTML page and the association of flow elements with each url/action transition between HTML pages. An HMTL page 36 has associated HTML pages 38 and 40 to which it is nominally a parent. Each HTML page is connected by a url/action transition 50, 51, 52. Moreover. each identification/exraction/translation triplet 30, 32, 34 is associated with a corresponding HTML page 36, 38, 40 by a ur1/action transition 54, 55, 56. However, there is also the flow of information among the triplets along information paths 58, 59, 60. The following sections describe in greater detail the components, identification methods, extraction methods and the underlying grammer that are embodied in a specific example of AML according to the invention.

[0092] C. Identification & Extraction

[0093] A component is identified using the element “component”, where the value for all attribute value pairs inside any element is herein rendered in quotations to set it off as a value. Thus a row can be identified as component A as follows:

[0094] <component name=“A” type=“tr”> </component>

[0095] The type of a component corresponds to an HTML tag.

[0096] Components may recursively contain components using a nested component notation. Thus, the following notation expresses that component A is contained within component B:

[0097] <component name=“B” type=“table”>

[0098] <component name=“A” type=“tr”> </component>

[0099] </component>

[0100] Further components may be repeated multiple times using the “idloop” element. Thus, the following notation means that the component named A can appear multiple times:

[0101] <idloop name=“aloop”>

[0102] <component name=“A” type=“tr”>

[0103] </component>

[0104] </idloop>

[0105] A component can be composed of two alternate components. The following notation expresses that component A is made up of either component X or component Y:

[0106] <component name=“A” type=“form”>

[0107] <idswitch name=“switch1”>

[0108] <idcase define=“pattern1”>

[0109] <component name=“X” type=“input”>

[0110] </component>

[0111] </idcase>

[0112] <idcase define=“pattern2”>

[0113] <component name=“Y” type=“select”>

[0114] </component>

[0115] </idcase>

[0116] </idswitch>

[0117] </component>

[0118] This illustrates provision of the ability to express regular expressions:

[0119] Parent-child relationship is expressed by nesting; in shorthand notation A(B) specifies that A is parent of B.

[0120] Repitition is expressed by idloop: in shorthand notation A* specifies that A is repeated

[0121] OR is expressed by switch: in shorthand notation A/B specifies that either A or B exists

[0122] AND is expressed by concatenation: in shorthand notation AB specifies that A is followed by B.

[0123] For example, the regular expression A(B/C)*D—where A is the parent of a idloop or-expression of components B and C, followed by a component D—can be written as:

[0124] <component name=“X” type=“type1”>

[0125] <component name=“A” type=“type2”>

[0126] <idloop name=“loop1”>

[0127] <idswitch name=“switch1”>

[0128] <idcase define=“pattern1”>

[0129] <component name=“B”

[0130] type=“type3”></component>

[0131] </idcase>

[0132] <idcase define=“pattern2”>

[0133] <component name=“C”

[0134] type=“type4”></component>

[0135] </idcase>

[0136] </idswitch>

[0137] </idloop>

[0138] </component>

[0139] <component name=“D” type=“type5”> </component>

[0140] </component>

[0141] The name of a component, or an idswitch or an idloop, could be used as a variable. A variable defined inside an idloop has several instances. An instance is specified by qualifying the variable name with a subscripted idloop name. For example, “loop1[0].C” represents the instance of “C” identified during the first iteration of the idloop “loop1”. In general, an instance of a variable is specified by qualifying the name of the variable with subscripted names of the enclosing idloops.

[0142] A variable could also be explicitly declared/defined using the <amlvar>element.

[0143] C.1. Variable definition

[0144] Variable are created using the amlvar element. The scope of a variable is global to an audio page. Its lifetime is until the audio page is being referenced in a user session. The name of the variable must be unique for an audio page. A variable has the following attributes which help define the name, type, etc. of the variable.

[0145] The following notation describes a variable x which encodes a field of type “date”:

[0146] <amlvar name=x type=‘date’ format=‘mmddy4’ render=‘y4’></amlvar>

[0147] C.2. Variable usage

[0148] All variables are objects containing the following elements:

[0149] Thus, a loop, named var1, could be accessed using the variable Samlvar(varl). The following would be true of the varl object:

[0150] var1 { vector=yes; length=# elements in loop:

[0151] Similarly a variable cell1, which represents a cell element in the table, could be accessed using the notation Samlvar(cell1), and its fields could be accessed as Samlvar(cell1.vector), Samlvar(cell1).colspan. etc. If cell1 was in the fifth iteration of the loop var1, then the anchor element associated with cell1 could be accessed as Samlvar(var1[4].cell1.anchor).

[0152] C.2.1. Global system variables

[0153] Variables can be marked as “global”. Their defintions are available across all pages that are traversed subsequently. The order of accessing of variables is: local variables (loop indexes), page variables (variables extracted from the page), followed by global variables.

[0154] amlerror

[0155] The amlerror variable is a system variable which exposes errors to the user. The variable is an object and has the following fields:

[0156] The user can refer to the type of the error as Samlvar(amlerror.type). The errors can be one of the following types:

[0157] ERROR={

[0158] RECOGNITION_FAILURE,

[0159] CALLER_TIMEOUT,

[0160] OTHER_ERROR,

[0161] WRONG_NUMBER_DIGITS

[0162] {

[0163] The following table describes default action taken on error for the following error conditions.

[0164] C.3. Identification of components

[0165] Components can be combined into regular expressions. Components can be identified, including such components as forms, tables, and lists on an HTML page. A component can be identified using one of two broad techniques:

[0166] Identify type (e.g., form, table, tr, td, etc.) and one or more of name/position/URL/dimension.

[0167] Identify “structure” of the component. This all-encompassing method can be the only method chosen. However, it needs much more user interaction than type identification. In many cases it would be easier for the user to use one of the other mechanisms. Therefore the designer should be allowed to move forward from easier to more difficult methods of identification.

[0168] Keeping in mind the preference for workflow to the designer, the following methods of identification are provided:

[0169] 1) Type: What is the type of the object, e.g., form, table, row, cell, cell, input, etc. E.g., <component name=“keywordsearch” type=“form”>// component is a form

[0170] 2) ID: Some components may be uniquely identifiable because they are given a unique <ID> on the HTML page.

[0171] <component name=“table1” class=class1 id=table1>

[0172] 3) HTMLname: name attribute on the HTML page

[0173] 4) Position: Specifies the ordinal number of that type of component in the subtree of the HTML parse tree rooted at the HTMLnode corresponding to the parent aml component. The second row of the first table in the document could be specified as

[0174] <component name=“tab1” type=“table” position=“1”>

[0175] <component name=“Interesting_row” type=“tr” position=“2”>

[0176] </component>

[0177] </component>

[0178] Note that the position is the rank among the sub-containers of the same type within the parent container.

[0179] Similarly the second table on the second frame can be specified using the following nested specification:

[0180] <component name=“keywordsearchframe” type=“frame” position=“2”>

[0181] <component name=“keywordsearchform” type=“form” position=“2”>

[0182] </component>

[0183] </component>

[0184] Similarly, if Table A has nested within it Table B, and Table B has Table C nested within it, then Table C could be specified with nested component specification as:

[0185] <component name=“A” type=“table” position=“1”>

[0186] <component name=“B” type=“table” position=“1”>

[0187] <component name=“C” type=“table” position=“1”>

[0188] </component>

[0189] </component>

[0190] </component>

[0191] 5) URL: A fixed form can be specified using the action URL. E.g.,

[0192] <component name=“keywordsearch” type=“form” url=“www.amazon.com/kevword-search>”

[0193] 6) Dimension: Fixed forms, tables, rows and lists can be specified using their dimensions. The sizes of tables and forms can be specified as follows:

[0194] <component name=“keywordsearch” type=“form” dimension=“3” form with 3 visible controls

[0195] <component name=“stockquotes” type=“table” dimension=“3”>table with 3 rows

[0196] <component name=“row1” type=“tr” dimension=“2”>//2 cells in the row

[0197] 7) Structure: This is the choice of last resort, or if sub-component level information about the component is desired. The text in the component can be specified in terms of two types of objects:

[0198] (a) quoted text which is matched exactly, and

[0199] (b) any text specified by the tag amlvar

[0200] A form could be specified as:

[0201] structure=“<form> <amlvar name=‘formbody’></form>” where “<form>” and </form> are matched exactly, and the entire body of the form is matched by the variable-text element <amlvar> and is assigned to the variable formbody.

[0202] If multiple conditions are used to specify the page then they all must be true. For example, in the following identification the component being identified is of type form and has an action method which is the value “vwww.amazon.com/keyword-search, has 3 inputs, and is the first form on the page”:

[0203] <component

[0204] name=“keywordsearch”

[0205] url=“www.amazon.com/keyword-search”

[0206] type=“form”

[0207] position=“1”

[0208] dimension=“3”>

[0209] In some cases, a component cannot be identified unambiguously by itself. In such cases, it must reference its parent subtree until it reaches an ancestor which can be unambiguously identified. Consider a parse tree, where it is necessary to identify the second cell in the second row of table level2 and consider where the number of cells in any of the rows in table level1 are not pre-determined. All that is known is that the last cell in the last row in level1 has the table level2 embedded within it. The lowest cell might be identified as:

[0210] <component name=“level1” type=“table” position=“1”

[0211] <component name=“level1_row” type=“tr” position=“2”

[0212] //[comment: It may not be necessary to specify the row in the above line]

[0213] <component name=“cell2” type=“td” position=“2”>

[0214] <component name=“level2” type=“table” position=“1”>

[0215] //position is relative to parent

[0216] <idloop ignore=“ALL_BUT_LAST”>

[0217] <component name=“first_rows” type=“tr”></component>

[0218] </idloop>

[0219] //[comment: The above is the first set of rows]

[0220] <component name=“last_row” type=“tr”>

[0221] <idloop ignore=“ALL_BUT_LAST”>

[0222] //[comment: The above is the first set of cells]

[0223] <component name=“first_cells” type=“td”> </component>

[0224] </idloop>

[0225] <component name=“last_cell” type=“td”>

[0226] </component>

[0227] </component>

[0228] </component>

[0229] </component>

[0230] </component>

[0231] </component>

[0232] Once a component is identified, the data within the component can be extracted.

[0233] C.4 Extraction: forms

[0234] Consider an example form such as a broker's sign-on page. This form has two inputs specified by the user: name and password. The remaining inputs are hidden elements as far as the user is concerned. There is also an option list to specify where the user wants to start the session.

[0235] The HTML code for such a form is shown below:

[0236] <FORM NAME=“SignonForm”

[0237] ACTION=“https://trading2.schwab.com/trading/signon/.” METHOD=“POST”

[0238] TARGET=_“self”>

[0239] <table>

[0240] <tr> <td> Account Number </td> <td> <INPUT TYPE=“text”

[0241] NAME=“SignonAccountNumber” SIZE=11 MAXLENGTH=9> </td></ tr>

[0242] <tr><td> Password </td><td> <INPUT TYPE=“password”

[0243] NAME=“SignonPassword” SIZE=11 MAXLENGTH=8> </td></tr>

[0244] <tr><td> Select </td> <td>

[0245] <SELECT NAME=StartAnchor>

[0246] <option Value=CCbodyi>Account Overview

[0247] <option Value=TradingEQ>Stock Trading

[0248] <option Value=TradingOpt>Options Trading

[0249] <option Value=TradeMF>Mutual Fund Trading

[0250] <option Value=TradeCorpBonds>Corporate Bond Trading

[0251] <option Value=Quotes>Real-Time Quotes

[0252] <option Value=Balance>Account Balances

[0253] <option Value=Position>Positions

[0254] </select>

[0255] <INPUT TYPE=HIDDEN NAME=PARMS VALUE=“ ”>

[0256] <INPUT TYPE=HIDDEN NAME=ShowUN VALUE=“YES”>

[0257] <INPUT TYPE=HIDDEN NAME=SANC VALUE=“ ”>

[0258] <INPUT TYPE=HIDDEN NAME=NewsURL>

[0259] <INPUT TYPE=HIDDEN NAME=“QCdata”>

[0260] <INPUT TYPE=HIDDEN NAME=“page”>

[0261] <INPUT TYPE=HIDDEN NAME=“story”>

[0262] <INPUT TYPE=HIDDEN NAME=“symbols”>

[0263] <INPUT TYPE=HIDDEN NAME=“watch_list”>

[0264] <INPUT NAME=“SignonSubmit” TYPE=“Submit” VALUE=“Submit”></td></tr></table></form>

[0265] The component specifies that there is one form of interest on this page, and it is placed as the first form on the page, namely:

[0266] <component Name=“Logon” TYPE=“FORM” position=“1”></component>

[0267] The action method of the form can be extracted using the following structure specification (where the tag amlvar describes any free-matched text):

[0268] structure=“<form> <amlvar> action=<amlvar name=‘url’>METHOD <amlvar>”>

[0269] This is interpreted as follows:

[0270] Start off by matching <form, then there is text until you match action=“, then the next part is a variable from the HTML page, which ends when you reach METHOD. Name the component Logon. Refer to the variable “url” as Samlvar(Logon.url).

[0271] Consider the following text in a page:

[0272] The source HTML language for the above table is as follows:

[0273] <TABLE BORDER=0 WIDTH=430 CELLPADDING=0 CELLSPACING=2>

[0274] <TR ALIGN=LEFT>

[0275] <TD VALIGN=TOP><FONT COLOR=“#000000”

[0276] FACE=“ARIAL.HELVETICA”CLASS=“NORM” SIZE=2>11/11/98</FONT><TD>

[0277] <TD WIDTH=“5”><IMG

[0278] SRC=“http://gsf.quote.com/fast/graphics/trading3/blank.gif” WIDTH=“1” HEIGHT=“1”

[0279] BORDER=0><TD>

[0280] <TD VALIGN=TOP><FONT COLOR=“#000000”

[0281] FACE=“ARIAL.HELVETICA” CLASS=“NORM” SIZE=2>16:47</FONT><TD>

[0282] <TD WIDTH=“5”><IMG

[0283] SRC=“http://gsf.quote.com/fast/graphics/trading3/blank.gif” WIDTH=“1” HEIGHT=“1”

[0284] BORDER=0></TD>

[0285] <TD VALIGN=TOP><FONT FACE=“ARIAL.HELVETICA” CLASS=“NORM” SIZE=2><U><A HREF=“/fq/trading3/news? story=8176218&symbols=csco”>(UPDATE) VocalTec. Cisco To Develop Products For Voice Calls Over Internet</A></U></FONT>&nbsp;<FONT COLOR=“#000000” FACE=“ARIAL.HELVETICA” CLASS=“SMALL” SIZE=1>[&nbsp;Dow&nbsp;Jones&nbsp;Online&nbsp;News&nbsp;]</F ONT></TD>

[0286] </TR>

[0287] <!-The rest of the rows are cut. -->

[0288] <!--They all have the same syntax. -->

[0289] </TABLE>

[0290] The table above has a variable number of rows, each of which has 5 cells. Of this table, only cells 1, 3, and 5 are intended for use. The structure of the table can be described as follows:

[0291] <component name=“headline” type=“table” position=“1”>

[0292] <idloop name=“headlines”>

[0293] <component name=‘news_item’ type=‘tr’>

[0294] <component name=“cell1”type=“td” position=“1”

[0295] structure=“<amlvar> SIZE=2> <amlvar name=‘date’ type=‘date’></FONT></TD>”>

[0296] </component>

[0297] <component name=“cell3”type=“td” position=“3”

[0298] structure=“<amlvar> SIZE=2> <amlvar name=‘time’ type=‘time’> </FONT></TD>”>

[0299] </component>

[0300] <component name=“cell5”type=“td” position=“5”

[0301] structure=“<amlvar> SIZE=2> <amlvar name=‘headline’ type=‘text’> </A></U> <amlvar>”>

[0302] </component>

[0303] </component>

[0304] </idloop>

[0305] </component>

[0306] The specification of each cell using the structure mechanism seems convoluted because of the HTML constructs appearing in the specification. One simplification is to have the structure refer to the “visible” part of the cell—this is what the user sees on a regular web browser.

[0307] <component name=“headline” type=“table” position=“1”>

[0308] <idloop name=“headlines”>

[0309] <component name=‘news_item’ type=‘tr’>

[0310] <component name=“date” type=“td” position=“1” visible=“true”></component>

[0311] <component name=“time” type=“td” position=“3” visible=“true”></component>

[0312] <component name=“cell5”type=“td” position=“5” structure=“<amlvar>

[0313] HREF=<amlvar name=‘url’>><amlvar name=‘news’ visible=‘true’> </A<amlvar>”>

[0314] </component>

[0315] </component>

[0316] </idloop>

[0317] </component>

[0318] The variables can be referred to as Samlvar(headlines[index].date). Samlvar(headlines[index].time), and Samlvar(headlines[index].news). Further, the anchor element of the 5th column could be referred to as Samlvar(headlines[index].url)

[0319] C.6 Extraction: looping variable component (e.a. list)

[0320] A variable component is one whose structure may change from one version of the HTML page to another. For example, when searching for a book on amazon.com, the results constitute a variable component, because the components cannot be identified as rows/cells of a table. It is possible though to have a generic specification of how the sub-components of a component are defined. In the source HTML, each component is started with a <dt> tag, and ended with the <p> tag.

[0321] <d1>

[0322] <dt><b><a href=“/exec/obidos/ASIN/0471880736/qid=909790477/sr=1-1/002-5206325-4441208”>Design and Inference in Finite Population Sampling (Wiley Series in Probability and Mathematical Statistics)</a></b>˜<NOBR><font color=#990033>Ships in 2-3 days</font></NOBR><dd> A. S. Hedayat(Contributor). B. K. Sinha/Paperback/Published 1991

[0323] <br> Our Price: $101.00 <br> <a href=“/exec/obidos/ASIN/0471880736/qid=909790477/sr=1-1/002-5206325-4441208”><i>Read more about this title . . . </i></a><p>

[0324] <dt> . . .

[0325] The above is an example of a component from a site labeled amazon.com. The result component could be specified as follows:

[0326] <component name=“resultssection” type=“body”>

[0327] <component name=“list” type=“d1”>

[0328] <idloop name=“resultsection2”>

[0329] <component name=“item” type=“dt”> </component>

[0330] </idloop>

[0331] </component>

[0332] </component>

[0333] In the above specification, there is a fixed header component “<d1>” followed by a loopingz component. In each iteration of the looping component we need to identiy the following sections:

[0334] Title=Design and Inference in Finite Population Sampling (Wiley Series in Probability and Mathematical Statistics)

[0335] Shipping=Ships in 2-3 days

[0336] Author=A. S. Hedayat(Contributor), B. K. Sinha

[0337] Type=Paperback

[0338] Date=1991

[0339] Price=$101.00

[0340] To extract the above sections, the result component could be described as follows:

[0341] <component name=resultssection>

[0342] <component name=“list” type=“d1”>

[0343] <idloop name=“loop1”>

[0344] <component name=“item” type“dt”

[0345] structure=“<dt> <b> <amlvar name=‘title’ visible=‘true’> </b><nobr> <amlvar name=‘shipping’ visible=‘true’> </nobr><amlvar> <dd><amlvar name=‘author’ visible=‘true’>/<amlvar name=‘type’ visible=‘true’>/Published<amlvar name=‘date’ visible=‘true’> <br> <amlvar> Price: <amlvar name=‘price’ visible=‘true’> <br><amlvar name=‘detail’visible=‘true’><p>”

[0346] </component>

[0347] </idloop>

[0348] </component

[0349] </component>

[0350] The title text can be referred to as Samlvar(loop1[index].title); information about the title can be accessed as Samlvar(loop1[index].detail).

[0351] C.7 Extraction: alternate structures

[0352] In the best case, a component of interest to the user may, be identified using exactly one method. However, there may be cases in which the same form may appear as the 1st/3rd form on a page, or a table may appear with 3 or 4 cells. Extending the identification of components using unique structures to identification of components with alternate structures vields the following examples:

[0353] Consider the following table (transaction history table from a stock quote site) where the rows are of three different types.

[0354] In this case, since the rows do not represent the same “types” of transactions they may need to be read out in different formats. Also, their input is organized differently. The rules for this table can be as follows:

[0355] it is a transaction of type interest.

[0356] it is a transaction of type dividend.

[0357] it is a buy/sell transaction.

[0358] To specify the above table:

[0359] <component name=“transaction” type=“table” position=“1”>

[0360] <idloop name=“transactionList” loopindex=“index”><idswitch name=“switch1”>

[0361] <idcase define=“INTEREST”>

[0362] <component name=“intrst” type=“tr” structure=“<amlvar>interest<amlvar>”>

[0363] <component name=icol1 type=“td” position=1></component>.

[0364] <component name=icol2 type=“td” position=2></component>

[0365] <component name=icol3 type=“td” position=3></component>

[0366] <component name=icol4 type=“td” position=4></component>

[0367] <component name=icol5 type=“td” position=5></component>

[0368] </component>

[0369] </idcase>

[0370] <idcase define=“DIVIDEND”>

[0371] <component name=“dvdnc” type=“tr” structure=“<amlvar>dividend<amlvar>”>

[0372] <component name=dcol1 type=“td” position=1></component>

[0373] <component name=dcol2 type=“td” position=2></component>

[0374] <component name=dcol3 type=“td” position=3></component>

[0375] <component name=dcol4 type=“td” position=4></component>

[0376] <component name=dcol5 type=“td” position=5></component>

[0377] </component>

[0378] </idcase>

[0379] <idcase define=“default”>

[0380] <component name=“intrst” type=“tr” >

[0381] <component name=col1 type=“td” position=1></component>

[0382] <component name=col2 type=“td” position=2></component>

[0383] <component name=col3 type=“td” position=3></component>

[0384] <component name=col4 type=“td” position=4></component>

[0385] <component name=col5 type=“td” position=5></component>

[0386] </component>

[0387] </idcase>

[0388] </idloop>

[0389] </component>

[0390] The invention has been described with reference to specific embodiments. Other embodiments will be evident to those of ordinary skill in the relevant art. It is therefore not intended that the invention be limited, except as indicated by the appended claims.