Merging tagged documents and scripts having dynamic content6061698Abstract Disclosed are a method and processor for linking a dynamic data fetch command to a document file, the document file initially in a preliminary markup state having at least one matching pair of a special beginning tag and a special ending tag, the tags separately contained in sequential comment statements of the preliminary markup document file, the tags delimiting and identifying an area in the preliminary markup document file for placement of requested dynamic data, the dynamic data fetch command located in a predefined script file having a linkage identifier, comprising the steps of identifying, in the preliminary markup document file, the matching pair of the special beginning tag and the special ending tag to identify the delimited area therebetween; selecting the predefined script file; generating a linked document file from the preliminary markup document file, adding, at the identified area in the preliminary markup document file, the linkage identifier for the selected predefined script file; and merging the predefined script file having the dynamic data variable fetch command with the linked document file. Claims We claim: Description TECHNICAL FIELD
______________________________________
% define DATABASE = "stock"
% SQL(sql1) {
select price from quota where company = 'IBM'
%SQL.sub.-- REPORT {
%ROW {
$(V1)
%}
%}
%}
%HTML.sub.-- REPORT {
%exec.sub.-- sql (sql1)
%}
______________________________________
The above term "% exec.sub.-- sq1(sq11)" is an exemplary Net.data function call which, when executed by Net.data, will execute the SQL statement and put the result into a variable. When the script file is executed by Net.Data, it will fetch the current IBM stock price for the database. The user may also decide to make modifications or changes 17 to the script file 16 by again using the tool 15, or, more likely, will want to add additional accesses to other dynamic data as described above. It is likely that the user will want many instances of dynamic data in the final document, with the result that the last document 11 will have many identifiers (or the user may have an extensive side listing) of intended dynamic data insert points, and that there will be a corresponding number of data script dynamic data accesses in data script file 16 (see FIG. 1). The difficult project is to merge the data script file 16 and the document 11. Another difficult project is to later modify the document 11. The merging of the data script file 16 and the document 11 in the prior art is illustrated by step 20. A way of manually conducting the merging of the data script file 16 and the document 11 is to cut and paste parts of document 11 into the data script file 16. This is a very tedious step because every element of document 11 must separately be placed into the data script file 16 and the dynamic data accesses of data script file 16 must be located at the appropriate points in the document as desired by the user. The data script file program (e.g., Net.Data) is then run to produce the final document 21. The incorporation of both the HTML file and the Net.Data script file into the final Net.Data script file appears as:
______________________________________
%define DATABASE = "stock"
%SQL(sql1) {
select price from quota where company = 'IBM'
%SQL.sub.-- REPORT {
%ROW {
$(V1)
%}
%}
%}
%HTML.sub.-- REPORT {
<HTML>
<TITLE>IBM Stock Report</TITLE>
<P >
The current stock price for IBM is % exec.sub.-- sql(sql1)
<P >
</HTML>
%}
______________________________________
If the user wishes to change or modify the document 21 at this stage, such as to change color, there is no way to do so, since the visual tool 10 is not available to the user at this stage. Rather, the user must go back to visual tool 10, make the change to document 11, and create the final document 21 again in step 20. Since this step 20 essentially repeats the incorporation work, it can be very tedious. The key difficulty, again, is that no single tool is presently usable to both create a document and to write the script to fetch dynamic data. Therefore, two tools 10 and 15 must be used separately to produce a separate document and script, and the tedious manual step 20 employed to merge the two. Executing the final script will produce the final document 21. Each time the user wishes to change the document, tool 10 must be used with document 11 as the basis for the change. The tedious manual merge step 20 must then be repeated to generate the changed final script. SUMMARY OF THE INVENTION An object of the present invention is to provide a method for merging dynamic data access commands and a document, and for generating a final document from the merged document. Disclosed are a method and processor for linking a dynamic data fetch command to a document file, the document file initially in a preliminary markup state having at least one matching pair of a special beginning tag and a special ending tag, the tags separately contained in sequential comment statements of the preliminary markup document file, the tags delimiting and identifying an area in the preliminary markup document file for placement of requested dynamic data, the dynamic data fetch command located in a predefined script file, the predefined script file having a linkage identifier, comprising the steps of: identifying, in the preliminary markup document file, the matching pair of the special beginning tag and the ending tag, thereby identifying the delimited area therebetween; selecting the predefined script file; generating a linked document file by adding, at the identified area in the preliminary markup document file, the linkage identifier for the selected predefined script file; and generating a final script file merging the predefined script file having the dynamic data fetch command with the linked document file. For a fuller understanding of the present invention, reference should be made to the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagrammatic representation of the prior art process flow for generating a document incorporating dynamic data; FIG. 2 is a diagrammatic representation of the process flow of the present invention for generating a document incorporating dynamic data; FIG. 3 is a flow chart depicting the linkage process of FIG. 2; and FIG. 4 is a flow chart depicting the merging process of FIG. 2. DETAILED DESCRIPTION OF THE INVENTION Referring to FIG. 2, the present invention provides a generic way to insert dynamic data into a tagged document. In one embodiment, the present invention comprises a method implemented by a data processing computer. In another embodiment, the invention comprises a system of a data processing computer. The invention may also be implemented to provide a signal bearing medium tangibly embodying computer readable code as a computer program product stored in a storage device, such as a magnetic disk drive or memory, etc., in a computer, or as an article of manufacture, such as a CD ROM, magnetic tape, etc. The user will have used a visual tool 10 as in the prior art to create a document file 30 that needs to have dynamic data filled in. The user will also have used a tool 15 as in the prior art to create a script file 31, such as Net.Data macro file or similar file, that can be executed to fetch data from a database into variables. As with respect to the prior art, the user will have made many changes to document 30, using the visual tool to change the document. Similarly, the user will likely have made changes to the script file 31, adding additional dynamic data fetching command sequences and possibly making other changes. To operate the invention, the user will conduct a markup phase 38 by inserting appropriate "special" tags into the places where the user wants to have dynamic data filled in. The special tags are placed as comments of the corresponding tag language of the tool 10 and of the document 30. The special tags are recognizable by the program of the present invention as designating that dynamic data is to be entered. For example, the special tags may comprise a matching pair of a beginning special tag and ending special tag, and delimiting and identifying the area between as the location of the desired dynamic data. The format of the special tag is in the form of the matching pair: <begin datatag> <end datatag> Using the same example as before, the user will mark up the HTML document 30 as follows: <HTML> <TITLE>IBM Stock Report</TITLE> <P> The current stock price for IBM is <!-dtb ->XXX<!-/dte -> <P> </HTML> In HTML format, the "<!-" and "->" designate the beginning and the end of a comment. In an example of the format of the invention, "dtb" and "/dte" designate the matching pair of a special beginning tag and a special ending tag, respectively, and, for the purpose of the invention, delimiting the area therebetween. The script file created by visual tool 15 will be the same macro as in the prior art as follows:
______________________________________
%define DATAEASE = "stock"
%SQL(sql1) {
select price from quota where company = "IBM"
%SQL.sub.-- REPORT {
%ROW {
$(V1)
%}
%}
%}
%HTML.sub.-- REPORT {
%exec.sub.-- sql(sql1)
%}
______________________________________
The linking information of the script file is the source string "% exec.sub.-- sq1(sq11)" variable, identified by the "% exec.sub.-- " term. The script file may also be marked up in a markup phase (not shown)in the use of visual tool 15, allowing the variable to be directly presented to the user in the prompting step 44. A linkage tool 40 of the present invention is used to make the linkage between the document 30 and the data script file 31. The linkage tool 40 is illustrated in FIG. 3. In step 41, document 30 is searched to locate comment statements. As an example, step 41 searches the document 30 sequentially. Upon identifying a comment statement, step 42 determines whether a "special tag" is incorporated in the comment statement. If "No", the process loops to step 41 to again search for the next comment statement. If "YES", step 43 identifies the area between a matching pair of special comment statements. In the specific example, the matching pair of comment statements are: <!-dtb ->and <!-/dte ->. Thus, the area between the matching pair of comment statements in the example is "XXX". In step 44, the user is prompted to make a selection of the desired predefined script file to match the area between the matching pair of comment statements. The prompting may, for example, be of the next sequentially available predefined script file variable identifier. If the user does not select the displayed predefined script file, the next sequentially available predefined script file will be shown. Alternatively, all predefined script file variable identifiers may be displayed, or all of the predefined script file variable identifiers that have not been previously selected. The display may, for example, be in the form of a listing of an identifier together with a definition statement or with a comment which helps to indicate to the user which of the predefined script files is identified in the list. In step 45, the user makes the selection, and step 46 performs the link by substituting the variable statement of the desired tag for the link in the area between the matching pair of comment statements. In the above example, with the tag in the form of a matching pair, the link is made as follows in step 46: <begin datatag, subs/source-string/target-string> <end datatag>, the link of the items marked up in the HTML file to the dynamic data items defined in the script file is: <HTML> <TITLE>IBM stock Report</TITLE> <P> The current stock price for IBM is <!-dtb s/XXX/% exec.sub.-- sq1(sq11)->XXX<!-/dte -> <P> </HTML>. As the result of the linking, the original tag is changed by substituting to embed the linking information. The only change to the document 30 are the dynamic data linkage identifiers that link to dynamic data variable fetch commands in the data script file 31. The dynamic data linkage identifier comprises a linkage command which when executed, will substitute the linked dynamic data variable command into the linked document at the linked location. Upon completion of linking step 46, the process loops back to step 41 to search for the next comment statement, etc. After the entire document has been searched for comment statements and for special tags within comment statements, the process terminates 48 at the end of the document. As an alternative to presenting the user with the predefined script file variable identifier, a comment in the script file may be utilized which is identified in similar fashion to that of the special tag of the document. Referring again to FIG. 2, linkage tool 40, upon completion of the process of FIG. 3, produces linked document 50. In the generation phase 54, the script file 31 is merged with the linked document 50 to create a final script file 55. The merging process is illustrated in FIG. 4 and involves performing substitutions of marked text based on the contents of the special tags. In step 60, document 50 is searched to locate comment statements, preferably in the same manner as step 41 of FIG. 3. As an example, step 60 searches the document 50 sequentially. Upon identifying a comment statement, step 61 determines whether a "special tag" is incorporated in the comment statement. If "NO", the process loops to step 60 to again search for the next comment statement. If "YES", step 62 executes the linkage command to substitute the marked text into the data script file at the location of the linkage identifier. Then, the process deletes the comment statements and special tags in step 63. The process then loops back to step 60 to search the linked document for the next comment statement. After the entire document has been searched for comment statements and for special tags within comment statements and all commands executed, data script files are effectively merged with the document and the process terminates 65 at the end of the linked document 50. The result of the process of FIG. 4 is the final script file 55. In the instant example, the file 55 incorporates the linked document 50 and the Net.Data script files 31 into a final Net.Data script file 55 of FIG. 2, which appears as:
______________________________________
%define DATABASE = "stock"
%SQL(sql1) {
select price from quota where company = 'IBM'
%SQL.sub.-- REPORT {
%ROW {
$(V1)
%}
%}
%}
%HTML.sub.-- REPORT {
<HTML>
<TITLE>IBM Stock Report</TITLE>
<P>
The current stock price for IBM is %exec.sub.-- sql(sql1)
<P>
</HTML>
%}
______________________________________
The final document 70 for display is then generated by the normal Net.Data system. If it is desired to make subsequent updates or to make changes, visual tool 1 may be used in step 71 to change the linked document 50 without starting over as is required by the prior art process and without relinking the document with linkage tool 40. Examples of changes are font sizes or colors, or adding material to the document 50. Once all the changes have been made, the generator process 54 is again run to generate a new final document 70. These changes can be made because the markup process 38 and link process 40 do not change the visual properties of the original document 30 and script files 31. The user can still use his favorite visual tools 71 to change the document after the markup and linkage processes, and the linking information is not lost after the changes have been made. The programming of the present invention may comprise a computer program product embodied as program code stored in a storage device, such as a magnetic disk drive or memory etc., in a computer, or may comprise an article of manufacture, such as a CD ROM, magnetic tape, etc. While the preferred embodiments of the present invention have been illustrated in detail, it should be apparent that modifications and adaptations to those embodiments may occur to one skilled in the art without departing from the scope of the present invention as set forth in the following claims.
|
Same subclass Same class Consider this |
||||||||||