Method and apparatus for automatic document generation based on annotation

• US 20040122912A1
• Filed: 08/14/2003
• Published: 06/24/2004
• Est. Priority Date: 12/21/2002
• Status: Active Grant

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: Kim, Jae Hong, Sohn, Joo Chan, Jang, Min Su
• Granted Patent: US 7,318,193 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 40/169 Annotation, e.g. comment data or footnotes
• CPC Class Codes: G06F 40/56 Natural language generation

Abstract

An annotation based automatic web document generation apparatus includes a web server, an annotation editor, an annotation server, an annotation/meta file database, and annotation processing system. The web server provides a web document. The annotation editor refers the web document from the web server to generate at least one annotation and generates a merged command for data for said at least one annotation. The annotation/meta file database stores the data for said at least one annotation and a merged meta file including the merged command for the data for said at least one annotation. Thus, it is possible to generate a new web document adapted for a user terminal by combining context information with the merged meta file and efficiently provide a plurality of user terminals of various characteristics with existing web documents.

Claims

1. An annotation based automatic web document generation apparatus comprising:

a web server for providing a web document;

an annotation editor for referring the web document from the web server to generate at least one annotation and for generating a merged command for data for said at least one annotation; and

an annotation/meta file database for storing the data for said at least one annotation and a merged meta file including the merged command for the data for said at least one annotation.

2. The apparatus of claim 1, wherein the annotation editor including:

a user interface for inputting a URL of a web document requested by a user, displaying the web document transmitted from the web server, and generating said at least one annotation for the web document by referring the web document;

a request processor for providing a request for the web document to the web server and receiving the web document from the web server to supply the received web document to the user interface; and

an annotation processor for generating the merged command and providing the merged command to the annotation/meta file database.

3. The apparatus of claim 2, wherein the user interface refer the web document by using the WYSIWYG scheme.

4. The apparatus of claim 1, wherein the annotation is one of an author annotation, a contents provider annotation, and a user annotation, the author annotation being made by an author of the web document, the contents provider annotation being made by a provider of the web document, and the user annotation being made by one of users of the web document.

5. The apparatus of claim 4, wherein the annotation includes an address of a destination node, an importance level of the destination node, a context indicating characteristics of a user terminal accessing the destination node, and alternative resources for the destination node.

6. The apparatus of claim 5, wherein the importance level is one of “

high”

, “

medium”

, and “

low”

, “

high”

means that intact contents of the destination node should be displayed at the user terminal, “

medium”

means that the modified contents of the destination node may be displayed at the user terminal, and “

low”

means that the contents of the destination node is permitted to be deleted.

7. The apparatus of claim 5, wherein the annotation further includes an action for the contents of the destination address if the annotation is one of the contents provider annotation and the user annotation, the action being one of “

preserve current contents”

, “

replace with a text”

, and “

replace with a URL”

, “

preserve current contents”

indicating that the contents should be preserved intact, “

replace with a text”

indicating that the contents should be replaced with the text specified in the alternative resources, and “

replace with a URL”

indicating that the contents should be replaced with the URL specified in the alternative resources.

8. The apparatus of claim 7, wherein the merged meta file is generated as follows:

i) in case that there exists the author annotation alone as said at least one annotation,

a) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

;

b) “

replace contents”

command is generated in the merged meta file if the importance level of the author annotation is “

medium”

; and

c) no command is generated in the merged meta file if the importance level of the author annotation is “

low”

;

ii) in case that there exists one of the contents provider annotation and the user annotation as said at least one annotation, said at least one annotation is regenerated as the merged meta file;

iii) in case that there exist the author annotation and the contents provider annotation as said at least one annotation,

a) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

; and

b) the contents provider annotation is regenerated as the merged meta file otherwise;

iv) in case that there exist the author annotation and the user annotation as said at least one annotation,

a) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

; and

b) the user annotation is regenerated as the merged meta file otherwise;

v) in case that there exist the author annotation, the contents provider annotation, and the user annotation as said at least one annotation,

a) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

; and

b) the user annotation is regenerated as the merged meta file otherwise; and

vi) in case that there exist the contents provider annotation and the user annotation as said at least one annotation, the user annotation is regenerated as the merged meta file.

9. The apparatus of claim 1, further comprising an annotation processing system for providing a URL where a web document requested by a user to the web server, and, in response to a request for the web document, for generating a new web document by using the merged meta file stored in the annotation/meta file database.

10. The apparatus of claim 9, wherein the annotation processing system including:

a pre-processing component for extracting user context information having the URL, a user ID, and characteristics of a user terminal from the request;

an annotation processing component for retrieving the merged meta file corresponding to the web document from the annotation/meta file database based on the URL and the user ID to generate a new web document adapted for the user terminal; and

a post-processing component for performing tag conversion and document fragmentation for the new web document and for transmitting the result web document to the user terminal.

11. An annotation based automatic web document generation method for used in an annotation based automatic web document generation apparatus comprising a web server for providing the web document and an annotation/meta file database for storing the annotations corresponding to the web document, the method comprising the steps of:

referring the web document from the web server to generate at least one annotation for the web document and generating a merged command for data for said at least on annotation; and

storing the data for said at least on annotation and a merged meta file including the merged command for the data.

12. The method of claim 11, wherein the annotation is one of an author annotation, a contents provider annotation, and a user annotation, the author annotation being made by an author of the web document, the contents provider annotation being made by a provider of the web document, and the user annotation being made by one of users of the web document.

13. The method of claim 12, wherein the annotation includes an address of a destination node, an importance level of the destination node, a context indicating characteristics of a user terminal accessing the destination node, and alternative resources for the destination node.

14. The method of claim 13, wherein the importance level is one of “

high”

, “

medium”

, and “

low”

, “

high”

means that intact contents of the destination node should be displayed at the user terminal, “

medium”

means that the modified contents of the destination node may be displayed at the user terminal, and “

low”

means that the contents of the destination node may be deleted.

15. The method of claim 13, wherein the annotation further includes an action for the contents of the destination address if the annotation is one of the contents provider annotation and the user annotation, the action being one of “

preserve current contents”

, “

replace with a text”

, and “

replace with a URL”

, “

preserve current contents”

indicating that the contents should be preserved intact, “

replace with a text”

indicating that the contents should be replaced with the text specified in the alternative resources, and “

replace with a URL”

indicating that the contents should be replaced with the URL specified in the alternative resources.

16. The method of claim 11, wherein the merged meta file is generated as follows:

i) in case that there exists the author annotation alone as said at least one annotation,

d) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

;

e) “

replace contents”

command is generated in the merged meta file if the importance level of the author annotation is “

medium”

; and

f) no command is generated in the merged meta file if the importance level of the author annotation is “

low”

;

ii) in case that there exists one of the contents provider annotation and the user annotation as said at least one annotation, said at least one annotation is regenerated as the merged meta file;

iii) in case that there exist the author annotation and the contents provider annotation as said at least one annotation,

c) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

; and

d) the contents provider annotation is regenerated as the merged meta file otherwise;

iv) in case that there exist the author annotation and the user annotation as said at least one annotation,

c) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

; and

d) the user annotation is regenerated as the merged meta file otherwise;

v) in case that there exist the author annotation, the contents provider annotation, and the user annotation as said at least one annotation,

c) “

preserve contents”

command is generated in the merged meta file if the importance level of the author annotation is “

high”

; and

d) the user annotation is regenerated as the merged meta file otherwise; and

vi) in case that there exist the contents provider annotation and the user annotation as said at least one annotation, the user annotation is regenerated as the merged meta file.