JP5391738B2 - Annotation program, annotation apparatus, and annotation method - Google Patents

Description

  The present invention relates to an annotation program, an annotation apparatus, and an annotation method, and in particular, an annotation program that adds an annotation to information based on a request from a user, or acts on information based on a reference request from a user, an annotation The present invention relates to an apparatus and an annotation method.

  In recent years, Web annotation technology for giving annotations as secondary information to information resources (for example, Web pages) on a network such as the Internet or an intranet has been often used.

  In Web annotation technology, another third party different from the Web page creator gives a Web page on the network an annotation such as a tag, underline, or marker, and browses the Web page. At the time of (reference), the added annotation is displayed simultaneously with the Web page, or processing based on the added annotation is added to the Web page.

  Normally, when an annotation is added, a unique name (for example, URL) for the Web page is held, and when the Web page specified by the URL is browsed, the annotation attached to the Web page is restored. An annotation can be restored even when browsing a Web page over time or browsing by a third party different from the annotator with the annotation.

  Such Web annotation technology is widely used for information sharing, proofreading support, review support, survey support, advertising systems, and the like.

  Conventionally, when an annotation is given to a web page and the given annotation is shared by a plurality of users, the URL of the web page on the common server, the position of the annotation given to the HTML file indicated by the URL, The contents are often registered in a management table.

  When the user designates a URL and requests an HTML file from the Web server, the common server acquires the HTML file from the Web server. Next, the common server refers to the management table, and if an annotation corresponding to the designated URL is registered, the annotation is embedded in the HTML file and transmitted to the user's client. The common server can share the annotation given to the Web page among a plurality of users by doing the above (see, for example, cited document 1).

  Note that the technique described in the cited document 1 targets digital content such as an electronic book, and therefore uses a page identifier and a row identifier to specify the position of the annotation.

JP 2000-155766 A

  However, since there is a time lag between the time when an annotation is given and the time when the annotation is restored, an operation that gives another annotation to the Web page and the time when the annotation is given and restored. The annotation may have been deleted, or the annotation target Web page itself may have been changed, such as a news article or blog.

  With Web annotation technology, even if such annotation operations or web page changes occur, the intended position at the time of annotation assignment (not the physical position such as XY coordinates, but the relationship with the Web page was captured. There was a request to restore the annotation to (position).

  The actual Web page is described in a Web page description language such as HTML or XML (hereinafter described using HTML as an example). Annotations are also described as HTML fragments in the Web page. Here, for description, each HTML fragment will be described with a one-dimensional character string indicating characters.

  A web page without an annotation is indicated by “ABCDEFGHIJ”. Each character of “ABCDEFGHIJ” is actually an HTML fragment such as <table> <tr> <td> 1 </ td> <td> 2 </ td> </ tr> </ table>.

  Here, it is assumed that the annotation “X” is given to the Web page. The annotation “X” is actually an HTML fragment like <div class = "annotation"> annotation </ div>. The annotation “X” has a position in the Web page.

  For example, when it is given between “C” and “D”, the annotation “X” has a position of “3”. Actually, HTML is represented by a tree structure as shown in FIG. FIG. 1 is a configuration diagram of an example of HTML expressed in a tree structure. In FIG. 1, in order to specify the second (second from the left) “h2” under “body”, for example, a path expression (Xpath) of a tree structure “/ html / body / h2 [2]” is used. Used.

  Xpath is not a physical position depending on display such as XY coordinates, but a character position independent of the display of what character in what paragraph. Xpath is a standard method recommended by the W3C, and is a description method that points to a specific element of an XML document.

  For example, when the annotation “X” is given to the position “3”, the position and content of the annotation are held in the database (DB) that holds the annotation. Here, the position and content of the annotation are expressed as (3, X).

  What should be noted here is that the Web page exists on another Web server on the Internet. That is, the Web page itself is not under management. That is, the Web page cannot be freely rewritten on this side (this system), and the content may be rewritten before this is intended. Thus, what is managed on the system side is information on what annotations are assigned to which positions on which Web pages.

  For example, a Web page “ABCDEFGHIJ” with an annotation of (3, X) is restored to “ABCXDEFGHIJ” (actually an HTML document) when it is taken into this system. The restored web page is processed so that the annotation “X” is given to the original web page by being passed to a web browsing device (browser) or the like.

  For example, the annotation “X” is displayed at a position between “C” and “D” in a form like a sticky note. FIG. 2 is a screen image diagram of an example of a Web page on which annotations in the form of sticky notes are displayed. In FIG. 2, annotation 1 is an HTML fragment with respect to the original HTML, and these are combined into one HTML.

  When an annotation “Y” is further added between “G” and “H” to the annotated Web page as shown in FIG. 2, since the annotation “X” has already been added, the annotation “ The position of “Y” is “8”. (8, Y) is registered in the DB holding the annotation.

  As a result, the annotation of the Web page becomes (3, X), (8, Y), and when it is taken into the system, it is restored as “ABCXDEFGHIHIJ” (actually an HTML document).

  Further, when the annotation “Z” is given between “E” and “F”, (6, Z) is registered in the DB holding the annotation. The DB that holds annotations holds (3, X), (8, Y), and (6, Z) so as to maintain the order relationship of the annotations.

  In this system, the order relationship of each annotation is maintained, and the order relationship of annotation is also maintained in the action of annotation. For example, by adding the annotation “X” to the position “3”, the Web page is restored as “ABCXDEFGHIJ”. Next, by adding the annotation “Y” to the position “8”, the Web page is restored as “ABCXDEFGYHIJ”. Finally, by adding the annotation “Z” to the position “6”, the Web page is restored as “ABCXDEZFGYHIJ”. In this way, the position of the annotation can be correctly restored in this system.

  For example, if the order relationship of annotation is broken and annotation (6, Z) is added before annotation (8, Y), annotation (8, Y) cannot be restored to the intended position.

  As described above, in this system, annotation ordering relationship is saved, and annotations are restored in that order, so that annotations can be restored to the correct position even if multiple annotations exist for the same Web page. It is like that.

  However, this system has a problem that when a part of the annotation is deleted, the remaining annotation is not restored as intended. For example, it is assumed that a DB that holds annotations holds (3, X), (8, Y), and (6, Z) so as to maintain the order relationship of annotation assignment. Here, it is assumed that the annotation (3, X) has been deleted.

  As described above, the annotation is not directly assigned to the Web page, but is a database record that holds what annotation is assigned to which position on which Web page. Therefore, deleting the annotation means deleting this record.

  By deleting the record from the DB holding the annotation, the annotation is not restored on the Web page, and it appears that the annotation has been deleted from the Web page. In this case, (8, Y) and (6, Z) are held in the DB holding the annotation. When accessing this web page “ABCDEFGHIJ” and attempting to restore the annotation “Y” at the position “8”, the annotation “X” that existed when the position of the annotation “Y” was determined is lost in this system. Therefore, the position of “8” is not between “G” and “H” but behind “H”. Similarly, in this system, the annotation “X” that existed when the position of the annotation “Z” was determined to be lost, so the position of “6” is not between “E” and “F” but “F”. Will be behind.

  As a result, there is a problem that the Web page is not “ABCDEFZFGYHIJ” but “ABCDEFZGHYIJ”.

  An embodiment of the present invention has been made in view of the above points, and an object thereof is to provide an annotation program, an annotation apparatus, and an annotation method capable of preventing a shift in an annotation embedding position caused by deletion of another annotation. And

In order to solve the above-described problem, an embodiment of the present invention is an annotation program for operating a computer that manages annotation information, the computer including a reception unit that receives a Web resource, and an operation log for the received Web resource. Annotation operation log acquisition unit that retrieves the Web resource identification information and operation log in association with each other in time series, and an operation for the Web resource that is extracted from the annotation operation log storage unit Annotation marker adding means for selecting a log in chronological order and adding an identifiable marker to the annotation embedded in the Web resource when the operation log is an annotation giving operation; and the annotation operation log storage means From An operation log for the extracted Web resource is selected in chronological order, and when the operation log is an annotation deletion operation, an annotation that is the target of the deletion operation embedded in the Web resource using the marker Even if an annotation is deleted later by a deletion operation, the marker is temporarily added and embedded in the Web resource, and the time series is recorded from the operation log. based on the selected delete operation, by using the marker, an annotation program that identify and delete the annotation is the subject of the delete operation embedded in Web resources.

  In addition, what applied the component, the expression, or arbitrary combinations of the component of one Embodiment of this invention to a method, an apparatus, a system, a computer program, a recording medium, a data structure, etc. is also effective as an aspect of this invention. .

  As described above, according to an embodiment of the present invention, it is possible to provide an annotation program, an annotation apparatus, and an annotation method that can prevent a deviation in the annotation embedding position caused by deletion of another annotation.

It is a block diagram of an example of HTML expressed with a tree structure. It is a screen image figure of an example of the web page on which the annotation of a format like a sticky note is displayed. It is explanatory drawing of the Web annotation system of a present Example. It is explanatory drawing of the other example of the Web annotation system of a present Example. It is explanatory drawing of the other example of the Web annotation system of a present Example. It is a block diagram of one Example of the Web annotation system of a present Example. It is a block diagram of an example of a computer system. It is a flowchart showing the annotation display processing of the annotation action device. It is explanatory drawing which shows an example of a tree structure. It is explanatory drawing which shows an example of the operation log currently recorded on annotation operation log DB. It is explanatory drawing for demonstrating the relationship between a tree structure and the position which XPath shows. It is explanatory drawing of the tree structure showing the Web resource analysis result by which the first annotation was embedded. It is explanatory drawing of the tree structure showing the Web resource analysis result by which the 2nd annotation was embedded. It is explanatory drawing of the tree structure showing the Web resource analysis result from which div id = 001 or less was deleted. It is explanatory drawing which shows an example of a tree structure. It is explanatory drawing of the tree structure showing the Web resource analysis result to which the annotation was provided with respect to a part of character string. It is explanatory drawing of the tree structure where the annotation X was embedded. It is explanatory drawing of the tree structure where the annotation Y was provided to the annotation X. It is explanatory drawing of the tree structure from which the annotation X was deleted. It is a flowchart showing the process which deletes the annotation to which the annotation was provided from a web resource analysis result. It is a flowchart showing the process of the annotation provision apparatus. It is a flowchart showing the process of annotation provision operation. It is a flowchart showing processing of annotation deletion operation. 10 is a flowchart showing processing for specifying a correspondence assignment operation. It is a flowchart of the other example showing the process of annotation deletion operation. It is a flowchart showing an annotation position influence analysis process. It is explanatory drawing showing when the operation log of grant operation | movement and deletion operation can be removed from annotation operation log DB, and when cannot be removed. It is a flowchart showing the process which determines whether the operation log of grant operation and deletion operation can be removed from annotation operation log DB. It is a block diagram of the other example of annotation operation log DB. It is explanatory drawing of the tree structure showing the Web resource analysis result with which the trace which has been deleted remains. It is a flowchart showing the annotation display processing of the annotation action device. It is a block diagram of an example of the browser to which the annotation program of a present Example is applied.

  Next, modes for carrying out the present invention will be described based on the following embodiments with reference to the drawings.

(Overview of this example)
In this embodiment, a Web annotation position restoration method using time series operation holding will be described. In the present embodiment, the annotation position is held as structure position information such as XPath, and the annotation corresponding position on the external web page (text) is obtained from the structure position information of each annotation, and the annotation is temporarily embedded. Will be described.

  In the Web annotation system, the calculation for obtaining a specific position for embedding the annotation on the Web text from the structural position information is affected by the presence of other annotations. Therefore, in the Web annotation system, when other annotations that existed when a certain annotation is added are deleted, there is a problem that the structural position information is shifted and the embedded position of the annotation is shifted.

  In order to prevent the annotation embedding position from deviating, the Web annotation system is temporarily used as a dummy on the Web resource (Web page) analysis result even if other annotations that existed at the time of annotation assignment are deleted and no longer exist. Exist. As described above, the Web annotation system can correctly calculate the position where the remaining annotation is embedded.

  Furthermore, the Web annotation system solves the problem of displacement of the embedding position due to deletion of other annotations or the like by adding a process of erasing or ignoring the annotation given as a dummy later.

  In the present embodiment, the position on the Web resource with respect to the Web resource is stored in the external storage device (annotation DB) as the structure position information such as XPath, and the Web resource according to the structure position information stored in the annotation DB A Web annotation system that performs annotation by temporarily embedding an annotation text fragment will be described as an example.

  In the Web annotation system of the present embodiment, the deviation of the calculation of the structure position information caused by deleting other Web annotations that existed when a certain Web annotation was added from the annotation DB is corrected, and is the same as that at the time of giving Restore the Web annotation to the position.

  In the above example, even if the annotation (3, X) is deleted after the annotation (3, X), (8, Y), (6, Z) is registered, the annotation is “ABCDEZFGYHIJ” as intended. And restored.

  In the Web annotation system of the present embodiment, if the annotation data is simply deleted from the annotation DB when the annotation is deleted, the position cannot be restored. For example, in order to restore the annotation as intended when the annotation is deleted, all the operations on the annotation DB including deletion are retained as a history, and the operation on the annotation DB is a Web resource that is the analysis result of the Web resource. A method of restoring the analysis result can be considered.

  However, deleting an annotation originally deletes the corresponding record from the annotation DB if only the history is restored. However, if only this is done, the annotation text fragment reflected in the Web resource analysis result remains. A new problem arises. That is, in the Web resource analysis result created by reflecting the state of the annotation DB at each time point, the difference of the Web resource analysis result is obtained from each operation on the annotation DB such as annotation addition / deletion, and is inherently direct. It becomes a problem to restore the history on the Web resource analysis result that is not operated.

  For example, <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> <div> text1 </ div> <div class = "annotation"> annotation </ div> <div> text 2 </ div> <div class = "annotation"> annotation </ div> <div> text 3 </ div> </ body> </ html> In the Web resource analysis result, when one annotation on the annotation DB is deleted, this single annotation is deleted instead of creating a new Web resource analysis result from the deleted annotation DB. From this history, it becomes a problem to correctly modify the Web resource analysis result.

  In order to solve this problem, the Web annotation system according to the present embodiment assigns and embeds a marker at the time of an annotation giving operation so that when the annotation is deleted from the annotation DB, the corresponding marker is displayed as a result of the Web resource analysis. Add an operation to find and delete from.

  Alternatively, when adding the annotation text fragment to the Web resource analysis result, the Web annotation system according to the present embodiment determines whether or not the annotation text fragment corresponds to the annotation to be deleted later.

  In the case of an annotation to be deleted later, the Web annotation system of the present embodiment gives an annotation text fragment having a marker that is calculated as being present at the time of position calculation but is handled as being absent at the time of operation.

  A technique for holding an operation log and reproducing it in the operation order of the history information is disclosed in, for example, Japanese Patent Laid-Open No. 7-134716. Japanese Patent Application Laid-Open No. 7-134716 discloses that, in order to restore the state of a hypermedia document, an operation history is stored in time series, and the operation is later re-executed from the top of the operation history. As described in Japanese Patent Laid-Open No. 7-134716, “the same processing as the corresponding processing is performed”, the history reproduction in the prior art is premised on the same processing as the normal operation. . For example, in the deletion of text, the range from a certain position on the text to the certain position itself and the operation of deletion are directly left in the history, and the processing itself left in the history is restored at the time of reproduction.

  In the annotation shown here, generally, the deletion operation is merely a process of deleting the corresponding record from the annotation DB, and no operation is performed on the Web resource analysis result.

  Therefore, only by reproducing the history information as disclosed in JP-A-7-134716, the annotation text fragment once reflected in the Web resource analysis result remains. If the Web resource analysis result is newly recreated from the beginning when the corresponding record is removed from the annotation DB, there arises a problem that the position of the annotation is shifted as shown in the problem of the conventional technology. That is, this problem cannot be solved only by a reproduction process as disclosed in Japanese Patent Laid-Open No. 7-134716.

  In other words, in addition to the operation of deleting an annotation in the normal annotation DB, in addition to the operation of deleting the annotation, a process of replaying the history is provided although it should have been deleted and should not exist in the Web resource analysis result. Therefore, it is necessary to newly provide a process for finding the annotation text fragment embedded in the Web resource analysis result and removing it from the Web resource analysis result. This point is a big difference between the technique of storing the history in a conventional general editor and reproducing the execution history, and the Web annotation system of the present embodiment.

  In order to find the corresponding annotation text fragment, it is necessary to correctly identify the corresponding annotation text fragment, and it is necessary to attach and embed a marker during the annotation assignment operation.

  For example, the position information at the time of embedding such as annotation (3, X) may be shifted in the first place. When the annotation (3, Y) is given to the web page “ABCXDEFGHIJ”, the web page “ABCYXDEFGHIJ” is obtained, and an annotation text fragment corresponding to the annotation “Y” is found at the position “3”. An annotation text fragment corresponding to "is not found.

(Principle of this embodiment)
FIG. 3 is an explanatory diagram of the Web annotation system of this embodiment. FIG. 3 shows a Web resource acquisition unit 10, Web resource analysis result preparation unit 11, annotation operation log acquisition unit 12, annotation restoration unit 13, annotation marker addition unit 14, annotation embedding unit 15, annotation fragment specifying unit 16, annotation fragment A deletion unit 17, an annotation operation unit 18, a Web resource analysis result 19, an annotation DB 20, and an annotation operation log DB 21 are shown.

  When the location information (URL) of a specific Web resource is specified, the Web resource acquisition unit 10 takes out the Web resource of the specified URL from the network. The Web resource analysis result preparation unit 11 can use the extracted Web resource as it is as the Web resource analysis result 19, but normally holds the tree structure as a result of parsing the Web resource as the Web resource analysis result 19. To do.

  The annotation restoration unit 13 retrieves the annotation information given to the retrieved Web resource from the annotation DB 20. The annotation embedding unit 15 finds the structure position indicated in the annotation information on the Web resource analysis result 19 and embeds the annotation content in the structure position in an appropriate format. The processing so far is performed for all annotations related to the Web resource.

  The annotation operation unit 18 operates the Web resource analysis result 19 in which annotation information is embedded. The action performed by the annotation action unit 18 is typically converted into a form visible by the rendering engine and displayed.

  The annotation operation log DB 21 holds operations related to annotation, annotation structure position information, and annotation contents separately from the annotation DB 20. The annotation operation log acquisition unit 12 extracts an annotation operation log (hereinafter simply referred to as an operation log) for the current Web resource.

  The annotation restoration unit 13 does not restore according to the information in the annotation DB, but performs time series processing according to the annotation operation and the annotation position described in the operation log. When the annotation operation recorded in the operation log is annotation addition, the annotation embedding unit 15 finds the position on the Web resource analysis result 19 according to the structure position information described in the operation log, and creates it according to the annotation content Embed annotation text fragment.

  At that time, the annotation marker attaching unit 14 attaches and embeds a marker that can be identified when the annotation text fragment to be embedded is deleted later. Conventionally, since the deleted annotation is not in the annotation DB 20, nothing can be done. In the present embodiment, the deleted annotation is once embedded in the Web resource analysis result 19 as an annotation text fragment. Therefore, the annotation text fragment corresponding to the deletion of the annotation is deleted from the Web resource analysis result 19. Is required.

  Therefore, the annotation text fragment specifying unit 16 searches the Web resource analysis result 19 for an annotation text fragment corresponding to the deleted annotation, using the identification marker embedded in the annotation text fragment as a clue. The annotation fragment deletion unit 17 removes the annotation text fragment corresponding to the deleted annotation from the Web resource analysis result 19.

  As described above, in the Web annotation system of this embodiment, not only annotations but also annotation deletions are recorded as operation logs, and the deleted annotations are once embedded in the Web resource analysis result 19.

  After adding other annotations, the annotation text fragment is deleted from the Web resource analysis result 19 at the timing of actual deletion according to the operation log. Even if annotations are deleted, the positions of the remaining annotations can be correctly restored.

  In the Web annotation system of this embodiment, the annotation DB 20 can be eliminated by retaining all annotation information in the annotation operation log DB 21, or only basic information of the operation log is retained 21 in the annotation operation log DB 21. The detailed information of the annotation may be held in the annotation DB 20.

  For example, when the annotation “X” is first given to the position “3” for the Web page “ABCDEFGHIJ” when the annotation is given, the Web annotation system of the present embodiment, for example, the annotation position and the annotation position are stored in the annotation DB 20 that holds the annotation. Annotation content is retained. At the same time, in the Web annotation system of this embodiment, the annotation “X” is added (inserted) to the position “3” in the annotation operation log DB 21 and recorded.

  Here, the Web annotation system of this embodiment describes (# 1, insert, 3, X) in the annotation operation log DB 21. “# 1” is an identification ID (event number) for referring to an annotation operation (event) later.

  Next, the fact that the annotation “Y” is added to the position between “G” and “H” in the Web annotation system of the present embodiment is shown in (# 2, insert, 8, Y) and the annotation operation log DB 21. Record. Note that the position between “G” and “H” is the position “8” because the annotation “X” has already been added.

  Next, the fact that the annotation “Z” is added to the position between “E” and “F” in the Web annotation system of the present embodiment is shown in (# 3, insert, 6, Z) and the annotation operation log DB 21. Record. Note that the position between “E” and “F” is the position “6” because the annotation “X” has already been added.

  Thereafter, the Web annotation system of the present embodiment records that the annotation “X” has been deleted (# 4, delete, # 1) in the annotation operation log DB 21. (# 4, delete, # 1) means that the annotation given in event 1 (# 1) is deleted. That is, the deleted annotation is indicated by the event number in the annotation operation log DB 21. As described above, the annotation operation log DB 21 holds an operation log.

  At the time of annotation action, the Web annotation system of this embodiment uses (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, insert,) as operation logs from the annotation operation log DB 21. 6, Z) and (# 4, delete, # 1) are taken out. In the extracted operation log, the annotation “X” is once given to the web page “ABCDEFGHIJ” to become “ABCXDEFGHIJ”, the annotation “Y” is given to “ABCXDEFGHIHIJ”, the annotation “Z” is given, and “ ABCXDEZFGYHIJ ".

  Actually, since an identifier such as “# 1” is assigned to the annotation “X” as a marker, the annotation “X” to which the marker “# 1” is assigned by the operation log (# 4, delete, # 1). "Is removed, and the Web page becomes" ABCDEZFGYHIJ ".

  As described above, the Web annotation system according to the present embodiment can obtain the position of the remaining annotation in the state where the deleted annotation exists even if a part of the annotation is deleted. Since the annotation is deleted at the timing when the deletion occurs in the Web annotation system of this embodiment, the remaining annotation can be restored to the correct position.

  FIG. 4 is an explanatory diagram of another example of the Web annotation system of this embodiment. The Web annotation system of FIG. 4 includes an annotation position influence analysis unit 30 and an annotation operation log rewriting unit 31 between the annotation operation log acquisition unit 12 and the annotation restoration unit 13 of the Web annotation system of FIG.

  The Web annotation system in FIG. 3 reproduces all operation logs honestly. If all operation logs are reproduced, the time overhead increases when annotations are added and deleted repeatedly. Therefore, in the Web annotation system of FIG. 4, in order to reduce the temporal overhead, the annotation position effect analysis unit 30 and the annotation operation log rewriting unit 31 are provided, and the annotation position effect analysis unit 30 affects the position of other annotations. Annotated annotation operations are removed from the annotation operation log DB 21.

  In the Web annotation system of FIG. 3, (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, delete, # 2), (# 4, insert, 6, Z) Also, the annotation Y (# 2) is honestly given to the operation log like this, and the annotation Y (# 2) is deleted.

  However, operation logs such as (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, delete, # 2), (# 4, insert, 6, Z) In this case, there is no other annotation operation from the time when the annotation Y (# 2) is assigned until the annotation Y is deleted, and the reproduction of the giving / deleting of the annotation Y is meaningless.

  For operation logs such as (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, delete, # 2), (# 4, insert, 6, Z) , (# 2, insert, 8, Y), (# 3, delete, # 2) can be deleted.

  Similarly, operation logs such as (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, insert, 6, Z), (# 4, delete, # 2) In the case of (# 2, insert, 8, Y) and (# 4, delete, # 2), there is (# 3, insert, 6, Z), but (# 3, insert, 6, Z). ) Is assigned to the front of (# 2, insert, 8, Y), and the calculation of the position is not affected by the annotation Y (# 2). Therefore, the reproduction of adding / deleting the annotation Y is meaningless.

  For operation logs such as (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, insert, 6, Z), (# 4, delete, # 2) , (# 2, insert, 8, Y), (# 4, delete, # 2) pairs can be deleted.

  As described above, in the Web annotation system of FIG. 4, the influence of the annotation position is analyzed, and the annotation position influence analysis unit 30 finds an annotation operation pair that does not affect the position calculation of other annotations. 31 deletes an annotation operation pair record that does not affect the calculation of the position of another annotation from the annotation operation log DB 21.

  FIG. 5 is an explanatory diagram of another example of the Web annotation system of this embodiment. The Web annotation system of FIG. 5 includes a dummy annotation text fragment generation unit 40 instead of the annotation marker adding unit 14, the annotation fragment specifying unit 16, and the annotation fragment deletion unit 17 of the Web annotation system of FIG. Deleted annotation recognition means 41 is newly provided.

  5 embeds a dummy annotation text fragment instead of embedding a true annotation text fragment when embedding the deleted annotation as an annotation text fragment in the web resource analysis result 19.

  The dummy annotation text fragment is embedded in the Web resource analysis result 19 so that when the position of the annotation embedding point is obtained, it is normally obtained, and there is nothing when the annotation action unit 18 tries to process it. It becomes equivalent to. The dummy annotation text fragment generation unit 40 generates a dummy annotation text fragment.

  The Web annotation system of FIG. 5 is provided with a deleted annotation recognition unit 41 that determines whether or not an operation log assigned with an annotation operation is deleted later among operation logs recorded in the annotation operation log DB 21. . Then, the deleted annotation recognition means 41 determines whether or not the annotation of the assigning operation in the annotation operation log DB 21 has been deleted later.

  Then, the Web annotation system of FIG. 5 processes the operation log in time series using the annotation operation log DB 21. The annotation embedding unit 15 embeds a normal annotation text fragment at a corresponding position on the Web resource analysis result 19 for a normal annotation giving operation.

  Further, the annotation embedding unit 15 embeds the dummy annotation text fragment generated by the dummy annotation text fragment generation unit 40 in the corresponding position on the Web resource analysis result 19 in response to the annotation adding operation of the deleted annotation.

  The dummy annotation text fragment is ignored (not showing any effect) when the annotation action unit 18 processes later, but shows the same effect as when the annotation is given in the annotation position calculation.

  For example, the annotation operation log DB 21 has operation logs (# 1, insert, 3, X), (# 2, insert, 8, Y), (# 3, insert, 6, Z) for the Web page “ABCDEFGHIJ”. And Next, if the annotation X (# 1) is deleted, the Web annotation system of FIG. 5 records (# 4, delete, # 1) in the annotation operation log DB 21.

  However, since the Web annotation system of FIG. 5 is different from the Web annotation system of FIG. 3 and the log of the deletion operation is not used later, the log of the deletion operation may not be recorded in the annotation operation log DB 21. However, the Web annotation system of FIG. 5 gives a deleted mark to the operation log (# 1, insert, 3, X) of the annotation operation log DB 21.

  As a result, when the annotation position is later restored, the Web annotation system of FIG. 5 is provided with the annotation text fragment “x” indicating that the annotation assignment of the annotation “X” is a dummy. “ABCDEFFGHIJ” becomes “ABCxDEFGHHIJ”, and the annotations “Y” and “Z” are restored to “ABCxDEZFGYHIJ”, which is the correct annotation position.

  Moreover, since “x” is a dummy, it has no effect at the time of an annotation operation, and is almost the same effect as when it is completely deleted. Incidentally, when the annotation “X” is added between “F” and “G” after the annotation X (# 1) is deleted in the Web annotation system of FIG. Since the trace “x” remains as “ABCxDEZFGYHIJ”, the position of the annotation “W” becomes “8” when calculated. On the other hand, since the Web annotation system of FIG. 3 calculates based on “ABCDEZFGYHIJ”, the position of the annotation “W” becomes “7”.

  FIG. 6 is a configuration diagram of an embodiment of the Web annotation system of the present embodiment. The Web annotation system of FIG. 6 includes an annotation assigning device 50, an annotation action device 51, an annotation management server 52, and an annotation operation log management device 53.

  The annotation assignment apparatus 50 includes a Web browsing device 61, an annotation assignment extension unit 62, and an annotation operation log extension unit 63. The annotation action device 51 includes an annotation action extension unit 64, an annotation operation log extension unit 65, and a web browsing device 66. The annotation management server 52 includes an annotation DB management unit 67 and an annotation DB 68. The annotation operation log management device 53 includes an annotation list management unit 69 and an annotation operation log DB 70.

  The Web annotation system of FIG. 6 is implemented as an extended function of the Web browsing devices 61 and 66. The annotation giving device 50 adds or deletes an annotation in response to a user's specific operation. The annotation operation device 51 displays or operates the annotation when accessing the Web resource.

  One embodiment of the annotation giving device 50 and the annotation action device 51 extends the web browsing devices 61 and 66. Note that the annotation assigning device 50 and the annotation action device 51 can simultaneously expand one browsing device.

  In the case of the Web annotation system of FIG. 3, the Web resource acquisition unit 10, the Web resource analysis result preparation unit 11, the annotation operation log acquisition unit 12, the annotation restoration unit 13, the annotation marker addition unit 14, the annotation embedding unit 15, and the annotation fragment specification The unit 16, the annotation fragment deletion unit 17, and the annotation operation unit 18 correspond to the annotation operation device 51 of FIG.

  In the case of the Web annotation system of FIG. 4, the Web resource acquisition unit 10, the Web resource analysis result preparation unit 11, the annotation operation log acquisition unit 12, the annotation restoration unit 13, the annotation marker addition unit 14, the annotation embedding unit 15, and the annotation fragment specification The part 16, the annotation fragment deletion part 17, the annotation action part 18, the annotation position influence analysis part 30, and the annotation operation log rewrite part 31 correspond to the annotation action device 51 of FIG.

  In the case of the Web annotation system of FIG. 5, the Web resource acquisition unit 10, the Web resource analysis result preparation unit 11, the annotation operation log acquisition unit 12, the annotation restoration unit 13, the annotation embedding unit 15, the annotation action unit 18, and the dummy annotation text fragment The generation unit 40 corresponds to the annotation action device 51 of FIG.

  The annotation assigning device 50, the annotation action device 51, the annotation management server 52, and the annotation operation log management device 53 in FIG. 6 can be realized by, for example, a computer system shown in FIG.

  FIG. 7 is a configuration diagram of an example of a computer system. The computer system includes an input device 81, an output device 82, a drive device 83, an auxiliary storage device 84, a main storage device 85, an arithmetic processing device 86, and an interface device 87 that are mutually connected by a bus B.

  The input device 81 includes a keyboard and a mouse, and is used for inputting various signals. The output device 82 includes a display device and is used to display various windows and data. The interface device 87 is a modem, a LAN card, or the like, and is used for connecting to a network.

  The annotation program of this embodiment is at least a part of various programs that control the annotation assigning device 50 and the annotation action device 51. The annotation program is provided, for example, by distributing the recording medium 88 or downloading from the network. The recording medium 88 on which the annotation program is recorded is information such as a CD-ROM, a flexible disk, a magneto-optical disk, etc., a recording medium for recording information optically, electrically or magnetically, a ROM, a flash memory, etc. Various types of recording media such as a semiconductor memory for electrical recording can be used.

  When the recording medium 88 on which the annotation program is recorded is set in the drive device 83, the annotation program is installed from the recording medium 88 to the auxiliary storage device 84 via the drive device 83. The annotation program downloaded from the network is installed in the auxiliary storage device 84 via the interface device 87. The auxiliary storage device 84 stores the installed annotation program and also stores necessary files, data, and the like.

  The main storage device 85 reads and stores the annotation program from the auxiliary storage device 84 when the computer is activated. The arithmetic processing unit 86 implements various processes as will be described later in accordance with the annotation program stored in the main storage device 85.

  In the following, a process for displaying (acting) an annotation, a process for giving an annotation, and a process for deleting an annotation will be described in the Web annotation system of the present embodiment.

(An example in which the annotation device 51 has the configuration of FIG. 3)
Web browsing devices (or generally Web clients) 61 and 66 incorporating the annotation program of this embodiment perform operations as shown in the flowchart of FIG. FIG. 8 is a flowchart showing annotation display processing of the annotation action device.

  In step S1, the web browsing device 66 receives the location information (URL) of the web resource to be displayed (acted). In step S2, the web browsing device 66 reads the web resource specified by the received URL from the network. In step S3, the Web browsing device 66 analyzes the read Web resource (text file described in HTML or the like) with a parser, and extracts the structure. The extracted structure takes the form of a tree structure (tree) (for example, a DOM tree).

  For example, the following HTML <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> <div> text 1 </ div> <div> If there is text 2 </ div> <div> text 3 </ div> </ body> </ html>, the tree structure as a parsing result is as shown in FIG. FIG. 9 is an explanatory diagram showing an example of a tree structure.

  The Web browser 66 sends a tree structure as shown in FIG. 9 to the rendering engine, interprets the tag (for example, <title> is a title, <h2> is a header, <p> is a paragraph, etc.) and converts it into a visible form. (Or some action instead of rendering).

  The above is a static page movement. In a dynamic page, after the Web browser 66 analyzes a Web resource by a parser, a program described in, for example, Javascript is sent to the JavaScript engine and executed to change the tree structure (a document is dynamically created). .

  The web browsing device 66 sends the tree structure to the rendering engine for display. In some cases, the Web browsing device 66 rewrites the tree structure according to the user's action, and repeatedly sends and displays the new tree structure to the rendering engine.

  The Web browsing device 66 incorporating the annotation program of this embodiment is similar to the Web browsing device 66 incorporating the normal Web annotation, and the result of analyzing the read Web resource by the parser (for example, DOM tree) is the Web resource analysis result. As a result, the following processing is performed without immediately passing to the rendering engine.

  The annotation action extension unit 64 extracts annotation data related to the Web resource that is currently displayed (action) from the annotation DB 68 of the annotation management server 52 via the annotation DB management unit 67, and extracts the annotation text fragment from the Web resource analysis result. It is embedded in (grafted on the tree structure).

  In the Web browsing device 66 in which the normal Web annotation is incorporated, the annotation data fragment is extracted from the annotation DB 68 using the URL of the Web page as a clue, and the annotation text fragment is placed at the specified position of the Web resource analysis result in the order in which the annotation is given. Go embedded.

  Note that the annotation data of the deleted annotation does not exist in the annotation DB 68 and thus is not reflected in the Web resource analysis result. On the other hand, the Web browsing device 66 in which the annotation program of this embodiment is incorporated has the annotation operation log DB 70, and therefore does not access the annotation DB 68 but accesses the annotation operation log DB 70.

  In step S4, the annotation operation log expansion unit 65 extracts all operation logs from the annotation operation log DB 70 using the URL of the web page as a clue, and arranges them in order from the oldest one.

  FIG. 10 is an explanatory diagram showing an example of an operation log recorded in the annotation operation log DB. The operation log shown in FIG. 10 has ID, operation type, XPath or ID, annotation content, and annotation record as fields.

  ID is an ID assigned to each operation. The ID may be a serial number, for example. The operation type describes the type of operation related to the annotation. As the operation type, a value of “grant” or “delete” is described.

  XPath or ID describes the XPath as the structure position to which the annotation was added when the operation is “granted”, and the ID on the operation log indicating which annotation was deleted when the operation was “deleted” Has been. The annotation content is information described in the assigned annotation. The annotation content is reflected in the annotation text fragment, and may be a character string or a link, or the HTML itself may be described in some cases.

  The annotation record is a pointer indicating a record on the annotation DB 68 of the assigned annotation. An annotation record is used to confirm whether or not an annotation to be deleted is pointed out when an annotation deletion operation is performed.

  FIG. 10 shows an example in which the XPath and the annotation content are described directly in the annotation operation log DB 70. Since the XPath and the annotation content also overlap with the annotation information in the annotation DB 68, the annotation DB 68 can be accessed by following the pointer of the annotation record and taken out.

  However, when the XPath and the annotation content are extracted from the annotation DB 68, the operation log cannot be restored if the record is simply deleted from the annotation DB 68 when the annotation is deleted.

  When deleting the annotation, it is necessary to transfer / save the contents of the record to be deleted from the annotation DB 68 somewhere, so that the annotation record of the operation log indicates the transfer / save location.

  In addition, when deleting an annotation, it is possible to deal with it by marking the record to be deleted in the annotation DB 68 as deleted and not deleting the data itself.

  In step S5, the annotation operation log extension unit 65 pays attention to the first (oldest) operation (record) in the operation log. Proceeding to step S6, the annotation operation log expanding unit 65 proceeds to step S7 while there is an operation (record) currently focused on. In step S <b> 7, the annotation operation log extension unit 65 determines whether the operation of interest is given or deleted.

  If the noticed operation is grant, the annotation operation log extension unit 65 proceeds to step S8, and obtains annotation information (XPath, annotation content) assigned at the time of the grant operation. In step S9, the annotation operation log extension unit 65 obtains the position of the annotation in the Web resource analysis result from the structure position information (XPath) obtained in step S8.

  For example, / html / body / div [1] included in the operation log in FIG. 10 indicates that the tree structure of the Web resource analysis is traced from the top to the nodes html, body, and div. Here, div [1] indicates the first div. Therefore, / html / body / div [1] indicates a node indicated by an arrow in the tree structure of FIG. FIG. 11 is an explanatory diagram for explaining the relationship between the tree structure and the position indicated by XPath.

  In the above, the Web resource analysis result is shown as a tree structure. However, since the tree structure corresponds to the original HTML, the <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> < div> Text 1 </ div> <div> Text 2 </ div> <div> Text 3 </ div> </ body> </ html> It is also possible to proceed.

  In step S10, the annotation operation log extension unit 65 creates an annotation text fragment from the annotation content. At this time, a portion corresponding to the annotation marker adding unit 14 of the annotation operation log extending unit 65 adds an identification marker to the text. As the identification marker, for example, the ID (serial number) of the operation log is used.

  In addition, how to act as an annotation can be created by a text fragment, or the class attribute and its value of an annotation text fragment like <div class = "annotation" id = "001"> X </ div> It can also be processed using CSS (Cascading Style Sheets). Note that annotation content (such as specific text described in a corresponding record in the annotation DB 68 or HTML text including a link to an image) is given to a portion surrounded by tags.

  In step S11, the annotation operation log extension unit 65 embeds the annotation text fragment with the identification marker in the position of the Web resource analysis result obtained in step S9. The embedding position can be determined by agreement such as before, after, or below the designated node.

  Here, it is assumed that it is embedded after the designated node (younger brother), and FIG. 12 shows the Web resource analysis result in which the first annotation is embedded. FIG. 12 is an explanatory diagram of a tree structure representing a Web resource analysis result in which the first annotation is embedded. In the XPath tree representation, attributes are also represented by nodes. The tree structure in FIG. 12 is shown in a simplified manner. 12, “X” is #text (character string) as XPath, but “X” is shown to clarify the distinction from other #text. The same applies to the drawings.

  The text representation of the tree in Figure 12 is <html> <head> <title> Title </ title> </ head> <body> <h1> Header </ h1> <div> Text 1 </ div> <div class = "annotation" id = "001"> X </ div> <div> Text 2 </ div> <div> Text 3 </ div> </ body> </ html> This completes the restoration of the given grant operation.

  In step S12, the annotation operation log expansion unit 65 moves the attention position to the next operation in the operation log and returns to step S6. The annotation operation log extension unit 65 performs processing for the next giving operation (ID = 002) in the same manner as the first giving operation (ID = 001). FIG. 13 shows the state of the Web resource analysis result when the processing for the grant operation (ID = 002) is completed. FIG. 13 is an explanatory diagram of a tree structure representing a Web resource analysis result in which the second annotation is embedded.

  The text representation of the tree in Figure 13 is <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> <div> text1 </ div> <div class = "annotation" id = "001"> X </ div> <div> Text 2 </ div> <div class = "annotation" id = "002"> Y </ div> <div> Text 3 </ div > </ body> </ html>.

  In step S7, when the operation of interest is deletion, the annotation operation log expansion unit 65 proceeds to step S13, and obtains the deleted annotation identification marker as information indicating which annotation has been deleted. For example, in the operation log in FIG. 10, the ID of the operation log when an annotation is given is described as an identification marker for the deleted annotation.

  In step S14, the annotation operation log extension unit 65 obtains the deleted annotation text fragment (with the identification marker) on the Web resource analysis result. In step S15, the annotation operation log extension unit 65 deletes the text fragment obtained in step S14 from the Web resource analysis result.

  In the example of FIG. 13, div id = 001 or less (<div class = "annotation" id = "001"> X </ div> in the text expression) is deleted. FIG. 14 is an explanatory diagram of a tree structure representing a Web resource analysis result from which div id = 001 or less has been deleted. The text representation of the tree in FIG. 14 is <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> <div> text1 </ div> <div> Text 2 </ div> <div class = "annotation" id = "002"> Y </ div> <div> Text 3 </ div> </ body> </ html>

  Although the deletion is simply performed here, an annotation may be added to the annotation, so a little more strict processing is required. An embodiment in which an annotation is added to the annotation will be described later.

  If it is determined in step S6 that all the operation logs on the annotation operation log DB 70 are reflected in the Web resource analysis result, the annotation action extension unit 64 and the annotation operation log extension unit 65 pass the Web resource analysis result to the rendering engine (or other than rendering) ).

  In the examples so far, examples have been shown in which annotations are assigned to structures such as <div> to </ div>. However, annotations can be added to a part of the character string (#text). <Html> <head> <title> Title </ title> </ head> <body> <h1> Header </ h1> <p> Text 1 </ p> <p> abcde </ p> <p> Text 3 </ p> </ body> </ html> is represented by a tree as shown in FIG. FIG. 15 is an explanatory diagram showing an example of a tree structure.

  Here, a case will be described in which annotations X are sequentially given between b and c in the character string abcde in the tree of FIG. 15 and Y between d and e in this order. The text representation of the tree in this case is <html> <head> <title> Title </ title> </ head> <body> <h1> Header </ h1> <p> Text1 </ p> <p> ab <div class = "annotation" id = "001"> X </ div> cd <div class = "annotation" id = "002"> Y </ div> e </ p> <p> Text 3 </ p> </ body> </ html>. In this case, the tree structure is as shown in FIG. FIG. 16 is an explanatory diagram of a tree structure representing a Web resource analysis result in which an annotation is given to a part of a character string.

  If the structure position of annotation X is simply / html / body / p [2] / # text [1], it will not be understood what character #text is inserted, so / html / body / Record the structure position of the previous #text block and the offset after which the character is inserted (in the example above, the number after :), such as p [2] / # text [1]: 2. ing. Similarly, the structure position of annotation Y is recorded as / html / body / p [2] / # text [2]: 2.

  Here, if annotation X is deleted, the position of annotation Y cannot be resolved (it will be #text [1]: 4 instead of #text [2]: 2). It is the same as the example given to the structure up to>.

  If annotation X is deleted, the problem that the position of annotation Y cannot be resolved is an example where annotation is given to a structure from <div> to </ div> even when annotating the text As well as solved.

  An annotation can also be added to the annotation. FIG. 17 is an explanatory diagram of a tree structure in which the annotation X is embedded. Here, it is assumed that an annotation Y is given to a character string of annotation X (XPath is / html / body / div [2] / # text). Note that the annotation X is a character string of several characters, and any number of characters in the character string can be specified, but the following description assumes that the entire annotation X has been selected.

  FIG. 18 is an explanatory diagram of a tree structure in which annotation Y is added to annotation X. The text representation of the tree in FIG. 18 is <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> <div> text1 </ div> <div class = "annotation" id = "001"> X <div class = "annotation" id = "002"> Y </ div> </ div> <div> Text 2 </ div> <div> Text 3 </ div > </ body> </ html>.

  At this time, the XPath of the annotation Y is recorded as / html / body / div [2] / # text: n (n is the number of X characters). Conventionally, when annotation X is deleted, a node with div id = 001 is not created, so annotation Y is to be assigned under the node after div id = 001.

  The processing in step S23 for deleting the annotation text fragment in consideration of such a case is as follows. For example, deleting a node with div id = 001 does not simply delete everything below the node with div id = 001, but deletes other annotation nodes below the node. In other words, in the above example, div id = 001 and the text part X are deleted, and div id = 002 or less is placed under the body (position of the original div id = 001) (in the text, < body> …… <div id = "001"> X <div id = "002"> Y </ div> </ div> …… </ body> into <body> …… <div id = "002"> Y </ equivalent to div> ... </ body>).

  That is, a tree structure as shown in FIG. 19 is obtained. FIG. 19 is an explanatory diagram of a tree structure from which the annotation X is deleted. The text representation of the tree in FIG. 19 is <html> <head> <title> title </ title> </ head> <body> <h1> header </ h1> <div> text1 </ div> <div class = "annotation" id = "002"> Y </ div> <div> Text 2 </ div> <div> Text 3 </ div> </ body> </ html>

  FIG. 20 is a flowchart showing a process of deleting an annotation with an annotation from the Web resource analysis result. In step S21, the annotation operation log extension unit 65 sets div id = 001 as P as a node to be deleted. Proceeding to step S22, the annotation operation log expansion unit 65 sequentially traces the node X and the node div id = 002 as the child elements of P as the element of attention. First, the annotation operation log extension unit 65 processes the node X as an element of interest.

  Proceeding to step S23, since there is an unprocessed element of interest, the annotation operation log expanding unit 65 proceeds to step S24. Since the node X of the element of interest is not another annotation, the annotation operation log extension unit 65 proceeds to step S25, and removes the elements X and below of the element of interest from P. In step S27, the annotation operation log extension unit 65 sets the next element of interest as the node div id = 002, and returns to step S23.

  Proceeding to step S23, since there is an unprocessed element of interest, the annotation operation log expanding unit 65 proceeds to step S24. The annotation operation log extension unit 65 proceeds to step S26 because the element div id = 002 or less of the element of interest is another annotation. In step S26, the annotation operation log extension unit 65 proceeds to step S27 while leaving the node div id = 002 or less of the element of interest.

  In step S27, the annotation operation log extension unit 65 returns to step S23 without selecting the next element of interest. Since there is no unprocessed element of interest, the annotation operation log extension unit 65 proceeds to step S28 and is replaced with a node div id = 002 or less, which is an element in which P is left (in this case, only one annotation is left. If there are multiple annotations, replace P while keeping the order).

(Annotation giving device 50)
The annotation assigning device 50 of FIG. 6 performs processing as shown in the flowchart of FIG. FIG. 21 is a flowchart showing the processing of the annotation assigning apparatus.

  In step S31, the annotation assignment extension unit 62 performs a process of displaying the annotation attached to the noticed Web resource before displaying the Web resource, and the annotation is provided. Web resources are displayed in the state of being.

  In step S32, the annotation addition extension unit 62 receives a user operation. If the user operation is to add annotations to the Web resource, the annotation addition extension unit 62 proceeds to step S33, and the annotation addition extension unit 62 calls the annotation addition unit (not shown) to give the annotation.

  If the user operation deletes an annotation for a Web resource, the annotation assignment extension unit 62 proceeds to step S34, calls an annotation deletion unit (not shown), and deletes the annotation.

  The annotation assignment extension unit 62 stores the result in which annotation assignment / deletion is reflected in the annotation DB 68 and waits for the next user operation. The annotation operation log expansion unit 63 stores the annotation addition / deletion result in the annotation operation log DB 70 and waits for the next user operation.

  FIG. 22 is a flowchart showing the processing of the annotation giving operation. The annotation giving operation is performed by allowing the user to specify an appropriate position on the screen, inputting text as annotation content, or specifying an image on a file.

  In step S41, the annotation assigning unit obtains an XPath indicating the position of the Web resource currently displayed on the screen specified by the user. Thus, the annotation assigning unit receives the URL, XPath, annotation content, etc. of the Web resource as annotation information.

  In step S42, the annotation assignment extension unit 62 registers the URL, XPath, annotation content, etc. of the received Web resource as annotation information in the annotation DB 68. Note that since the XPath is obtained for the currently displayed Web resource, if an annotation has already been given, it can be obtained by the XPath including the annotation.

  In step S43, the annotation operation log extension unit 63 registers the annotation operation log with annotation in the annotation operation log DB. The annotation operation log extension unit 63 adds an operation type to the end of a series of records in the annotation operation log DB 70 in which an operation log of the current Web resource is recorded, and registers an XPath, annotation content, and an annotation record as an annotation structure position. Further processing is added.

  FIG. 23 is a flowchart showing the processing of the annotation deletion operation. The annotation deletion operation is performed by an annotation deletion action (for example, a prepared button or menu) after the user specifies an annotation on the screen.

  In step S51, the annotation deletion unit recognizes which annotation is the deletion action. In step S52, the annotation addition extension unit 62 obtains a record on the annotation DB 68 corresponding to the annotation to be deleted.

  In step S 53, the annotation addition extension unit 62 specifies a correspondence operation record corresponding to the annotation to be deleted on the annotation DB 68. Details of the processing in step S53 will be described later. In step S54, the annotation addition extension unit 62 deletes the record specified in step S53 from the annotation DB 68.

  In step S55, the annotation operation log extension unit 63 registers the annotation operation log for deleting annotations in the annotation operation log DB. The annotation operation log expansion unit 63 records what the deleted annotation was in the annotation operation log DB 70 with an ID (identification marker).

  As the ID (identification marker), for example, the ID on the operation log when given can be used. The annotation operation log extension unit 63 further includes a process of deleting and registering an ID (identification marker) as an operation type at the end of a series of records in the annotation operation log DB 70 in which an operation log of the current Web resource is recorded.

  FIG. 24 is a flowchart showing processing for specifying the correspondence assignment operation. The process of specifying the correspondence assignment operation is to identify the operation in which the deleted annotation is assigned by the operation log on the annotation operation log DB 70. The annotation operation log extension unit 63 traces the operation log of the current Web resource in order from the latest one, obtains an operation in which the annotation to be deleted and the annotation content match from the grant operation, and the grant operation May be used as the ID (identification marker) of the correspondence giving operation. The annotation deletion operation is registered in the annotation operation log DB 70 by deleting the operation type field and registering an ID (identification marker) in the XPath or ID field.

  In step S 61, the annotation operation log extension unit 63 pays attention to the latest operation log on the annotation operation log DB 70. Proceeding to step S62, if the operation type of the noticed operation log is given, the annotation operation log extending unit 63 proceeds to step S63.

  In step S63, the annotation operation log extension unit 63 reads a record in the annotation DB 68 based on the annotation record described in the noticed operation log. The annotation operation log extension unit 63 determines whether the read annotation record matches the annotation record currently being deleted.

  If the read annotation record matches the annotation record that is currently to be deleted, the current operation of interest is an assign operation corresponding to the annotation that is currently being deleted. Is returned to the annotation assigning extension unit 62, and the processing of the flowchart of FIG.

  If the read annotation record does not match the annotation record that is currently being deleted, the current operation of interest is not a grant operation corresponding to the annotation that is currently being deleted, and the annotation operation log extension unit 63 proceeds to step S64. , The operation log of interest is moved to the previous operation log, and the process returns to step S62.

(An example in which the annotation device 51 has the configuration of FIG. 4)
The annotation position influence analysis unit 30 and the annotation operation log rewrite unit 31 illustrated in FIG. 4 can rewrite the operation log by scanning the annotation operation log DB 70 at an arbitrary timing. A typical embodiment is performed at the timing when “deletion operation” is registered in the operation log in the processing of annotation deletion operation.

  That is, for the annotation deleted this time, the annotation position influence analysis unit 30 analyzes whether the annotation position is not affected even if it is deleted from the operation log together with the adding operation corresponding to the annotation deleted this time. .

  If there is no influence, the annotation operation log rewriting unit 31 deletes the corresponding grant operation record from the operation log. Further, the annotation operation log expansion unit 63 does not register the current deletion operation in the operation log.

  If there is an influence, the operation log assignment operation record is left as it is, and the current deletion operation is also left in the operation log. When the annotation action device 51 has the configuration shown in FIG. 4, the processing of the annotation deletion operation shown in FIG. 23 is replaced with the following flowchart.

  FIG. 25 is a flowchart of another example showing the processing of the annotation deletion operation. The processing in steps S71 to S75 in the flowchart in FIG. 25 is the same as the processing in steps S51 to S55 in the flowchart in FIG. The annotation position influence analysis processing in step S76 obtains a position influence relationship with other added annotations from the time when the annotation is added to the deletion annotation, and an operation having an influence is performed. When there is no, delete the grant / delete pair.

  The position influence relationship is obtained by determining whether the block is ahead of itself or another block of a tree structure. Further, by deleting the pair, the pair that can be deleted among the pair of grant and deletion that could not be deleted until now is further deleted.

  FIG. 26 is a flowchart showing the annotation position influence analysis process. In step S81, the annotation position influence analysis unit 30 receives an ID (identification marker) on the operation log of the deleted annotation. The annotation position influence analysis unit 30 creates a list of 1 element having only the received ID as an element and sets it as a deletion event list.

  In step S82, the annotation position influence analysis unit 30 extracts the first element from the deletion event list. Initially, the deletion event list is a list with 1 element. For this reason, the ID extracted in step S82 is the ID set in step S81 (the operation specified by this ID is always a deletion). In addition, as a result of extracting the element, the deletion event list becomes empty.

  In step S83, the annotation position influence analysis unit 30 obtains an ID at the time of grant corresponding to the ID extracted in step S82. In the processing of the annotation deletion operation illustrated in FIG. 23, the operation type value in the operation log is extracted because the corresponding operation ID (identification marker) is registered in the record of the operation type deletion in the operation log. Through the processing so far, the annotation position influence analysis unit 30 obtains the ID of the deletion operation for deleting the annotation and the ID of the giving operation to which the annotation corresponding to the deletion operation is added.

  Proceeding to step S84, the annotation position influence analysis unit 30 refers to the operation log recorded in the annotation operation log DB 70, and performs the grant operation obtained at step S83 between the grant operation obtained at step S83 and the delete operation. When the operation log is deleted, the presence / absence of an annotation that affects position reproduction is determined. Details of the process in step S84 will be described later.

  If there is an annotation that affects position reproduction, the annotation position influence analysis unit 30 proceeds to step S85, determines that the operation log of the assigning operation obtained in step S83 cannot be deleted, and obtains the annotation operation log DB 70 in step S83. The operation log of the added and deleted operations is left as it is.

  Progressing to step S86 following step S85, the annotation position influence analysis unit 30 determines whether or not the deletion event list is empty. If the deletion event list is empty, the annotation position influence analysis unit 30 ends the process of the flowchart of FIG. If the deletion event list is not empty, the annotation position influence analysis unit 30 returns to step S82.

  On the other hand, in step S84, the annotation position influence analysis unit 30 determines that the operation log of the assigning operation obtained in step S83 can be deleted if there is no annotation that affects the position reproduction. In step S87, the annotation position influence analysis unit 30 causes the annotation operation log rewriting unit 31 to delete the operation log of the pairing operation and deletion operation obtained in step S83 from the annotation operation log DB 70.

  For example, when the operation log is (# 1, insert, 3, X), (# 2, insert, 5, Y), (# 3, delete, # 1), at the time of the delete operation in # 3, # 2 The pair of # 1 and # 3 cannot be removed from the operation log due to the presence of the annotation Y given in.

  However, if a deletion operation of (# 4, delete, # 2) is added, the pair of # 2 and # 4 can be removed from the operation log. Then, there is no giving operation having an influence between the pair of # 1 and # 3, and the pair of # 1 and # 3 can be removed from the operation log. In order to realize such a ripple effect, the annotation position influence analysis unit 30 proceeds to step S88 following step S87, and deletes the ID of the delete operation between the operation logs of the removed assignment operation and the delete operation. In addition, the process returns to step S82. By repeatedly performing the processes of steps S82 to S88, the annotation position influence analysis unit 30 can obtain an operation log that can be rippled and removed.

  The influence presence / absence determination process, which is the process of step S84, is performed as follows. When the IDs on the operation logs of the grant operation and the delete operation are given, the annotation position influence analysis unit 30 determines whether or not the operation log of the grant operation and the delete operation can be removed from the annotation operation log DB 70.

  FIG. 27 is an explanatory diagram showing when the operation log of the assigning operation and the deleting operation can be removed from the annotation operation log DB, and when it cannot be removed. For example, it is assumed that the node I wants to remove the operation log from the annotation operation log DB 70 is node I.

  The operation log of the node I can be removed from the annotation operation log DB 70 because the structure position (XPath) of all the annotations given before the node I is added and deleted is not changed regardless of the presence or absence of the node I. When it is. If the structure position of the annotation that has been given before the node I is added and deleted changes depending on the presence or absence of the node I, the operation log of the node I can be removed from the annotation operation log DB 70. Absent.

  The nodes J and K which are descendants of the node I in FIG. 27 naturally change their structural positions when the node I disappears. In addition, the node L, which is the brother of the node I, and the nodes M and N, which are descendants of the node L, change their structural positions when the node I disappears.

  On the other hand, the nodes B, C, D, O, P, and Q that do not share the parent with the node I have the same structure position even if the node I disappears. Even if node I and the parent are common, node F, which is the older brother in front of node I, and its descendants, nodes G and H, have the same structural position even if node I disappears.

  After all, if at least one annotation is given to a position that becomes a descendant of itself (node I) or a younger brother and its descendant during the period from addition to deletion of node I, the annotation position influence analysis unit 30 It is determined that the operation log of I cannot be removed from the annotation operation log DB 70. Also, if no annotation is added to the position of its own descendant, or the brother and its descendant, from the grant to deletion of the node I, the annotation position influence analysis unit 30 displays the operation log of the node I as the annotation operation log. It is determined that it can be removed from DB70.

  FIG. 28 is a flowchart showing processing for determining whether or not the operation log of the assigning operation and the deleting operation can be removed from the annotation operation log DB.

  Proceeding to step S91, the annotation position influence analysis unit 30 sets the grant operation ID to i and the delete operation ID to j. In step S92, the annotation position influence analysis unit 30 obtains the structure position (XPath) of i and sets it to p.

  Note that the structure position registered in the annotation DB 68 and the annotation operation log DB 70 is the position after which the annotation is inserted. For example, in the case of FIG. 27, the node I designates the node F as the structure position. However, here, not the structure position of the node F but the structure position of the node I itself is assumed to be p.

  In step S93, the annotation position influence analysis unit 30 sets the position i on the operation log to be noted as the ID of the operation log next to the current i. Since the operation log may be removed from the annotation operation log DB 70, the ID of the operation log next to the current i may not be a sequential number.

  In step S94, the annotation position influence analysis unit 30 determines whether the position i on the operation log to be noticed is an operation performed in the past before the deletion operation (j). If the position i on the operation log to be noticed is an operation performed before the deletion operation (j), the annotation position influence analysis unit 30 proceeds to step S95.

  In step S95, the annotation position influence analysis unit 30 determines whether the operation indicated by i is a giving operation. If the operation indicated by i is an assignment operation, the annotation position influence analysis unit 30 proceeds to step S96, extracts the structure position of the assignment operation indicated by i, and sets the structure position to q. Here, similarly to p, the structure position of the assigned annotation itself is assumed to be q.

  In step S97, the annotation position influence analysis unit 30 determines whether q is a descendant of p, a younger brother, or a younger brother. If q is a descendant of p, a younger brother, or a descendant of the younger brother, the annotation position influence analysis unit 30 determines that there is an affected annotation. If q is not a descendant of p, a younger brother, or a younger brother, the annotation position influence analysis unit 30 returns to step S93.

  In step S94, if the position i on the noticed operation log is not an operation performed before the deletion operation (j) (matches j), the annotation position influence analysis unit 30 has an affected annotation. Judge that not. If the operation indicated by i is not an assignment operation in step S95, the annotation position influence analysis unit 30 returns to step S93.

(An example in which the annotation device 51 has the configuration of FIG. 5)
As shown in FIG. 29, the annotation action device 51 having the configuration shown in FIG. 5 adds a deleted marker to the corresponding record in the annotation operation log DB 70 in response to the annotation deletion operation. FIG. 29 is a configuration diagram of another example of the annotation operation log DB. The annotation operation log DB 70 of FIG. 29 differs from the annotation operation log DB 70 shown in FIG. 10 in that a marker indicating whether or not the assigned annotation has been deleted is recorded.

  In addition, the operation log of the deletion operation is not recorded in the annotation operation log DB 70 of FIG. 29 (even if it is recorded, it is ignored). Although the operation type field is left in the annotation operation log DB 70 of FIG. 29, the operation type field may be omitted because the operation log to be recorded is only the giving operation.

  29 is different from the annotation operation log DB 70 of FIG. 10 in the XPath of ID003. This is because the deleted trace remains in the Web resource analysis result. FIG. 30 is an explanatory diagram of a tree structure representing a Web resource analysis result in which a deleted trace remains. In FIG. 30, since the deleted trace of div class = deleted remains, the structure position of the annotation Z is / html / body / div [4].

  FIG. 31 is a flowchart showing annotation display processing of the annotation action device. Compared with the flowchart of FIG. 8, the flowchart of FIG. 31 considers the “deleted” marker when displaying (acting) the annotation, recognizes the deleted annotation, and assigns the “deleted” marker. Is different.

  Specifically, the flowchart of FIG. 31 differs from the flowchart of FIG. 8 in the following points. First, since the annotation operation device 51 configured as shown in FIG. 5 does not record the delete operation in the annotation operation log DB 70, steps S7 and S13 to S15 in the flowchart of FIG. 8 are not necessary.

  Second, the annotation action device 51 configured as shown in FIG. 5 has a case where there is a “deleted” marker and a case where there is no “deleted” marker in the processing corresponding to the text fragmentation in step S10 in the flowchart of FIG. And the text fragment to create is different. Thirdly, the annotation action device 51 having the configuration shown in FIG. 5 does not need to delete the operation log later, and therefore does not need an identification marker.

  The processing in steps S101 to S106, S107, S108, S112, and S113 is the same as the processing in steps S1 to S6, S8, S9, S12, and S16 in FIG.

  In step S109, the annotation operation log extension unit 65 confirms whether or not the annotation has already been deleted with reference to the marker field in the annotation operation log DB 70 when the annotation is converted into a text flag. If the “deleted” marker is not attached, the annotation operation log extension unit 65 determines that there is an annotation, and proceeds to step S110. In step S110, the annotation operation log extension unit 65 creates a text fragment for annotation from the annotation content as in step S10 of FIG. 8, but it is not necessary to embed an identification marker in the text fragment.

  If the “deleted” marker is attached, the annotation operation log expansion unit 65 determines that the annotation has already been deleted, and proceeds to step S114. In step S114, the annotation operation log extension unit 65 creates a dummy annotation text fragment. A dummy annotation text fragment is a text fragment that works in the same way as an annotation when calculating the structure position, but has no effect on display or action. Specifically, for example, <div class = "annotation deleted" /> is created as a text fragment having deleted as an attribute value and an empty text element.

  An exemplary embodiment for recognizing a deleted annotation is called when an annotation deletion operation is performed. For example, instead of registering “deletion” in the annotation operation log in step S55 in the annotation deletion embodiment of FIG. 23, the flowchart of FIG. 31 shows the corresponding assignment operation (this is determined in step S53 in the flowchart of FIG. 23). This is different in that a marker “deleted” is added to the record of “Yes”.

  Further, the deleted annotation recognition means 41 in FIG. 5 does nothing at the time of the annotation deletion operation, and checks whether or not the “deleted” marker is present when checking whether the annotation has already been deleted in step S109. Instead, it is possible to check whether the annotation exists or has been deleted by accessing the annotation DB 68 and checking whether the annotation record exists. In this method, the “deleted” marker field in the operation log is not necessary. Note that access to the annotation DB 68 may be performed when the annotation information is extracted in step S107 instead of this timing.

(Example of annotation program applied to browser)
FIG. 32 is a configuration diagram of an example of a browser to which the annotation program of this embodiment is applied. The browser 200 shown in FIG. 32 shows a typical configuration, and details such as CSS processing and PDF plug-in that are unnecessary for the description are omitted.

  The HTML parser 201 analyzes the HTML document 100 received via the network, and generates a tree structure (DOM tree) 202. At the same time, the Javascript program 205 executes the Javascript program 205 existing in the HTML document 100 and rewrites the contents of the DOM tree 202. The rewritten DOM tree 202 is sent to the rendering engine 203.

  The rendering engine 203 converts the received DOM tree 202 into a form that can be seen on the screen. Then, the JavaScript program 205 rewrites the DOM tree 202 and changes the content to be displayed by a user operation or the like via the user interface 204.

  The annotation program 210 is typically held in the browser 200 (ie, implemented in a form that is incorporated into the browser 200 or added as a function extension).

  Then, in addition to the Javascript program 205 of the read HTML document 100 being executed, the annotation program 210 is executed and the DOM tree 202 is rewritten. Note that data such as the annotation DB referred to by the annotation program 210 is held outside the browser 200.

  As another embodiment for holding the annotation program 210, it is conceivable to hold the annotation program 210 in a read HTML document. In this embodiment, the applicable Web pages are limited, but the same effect as that in which the annotation program 210 is held in the browser 200 can be provided.

The present invention may have the following configurations as described below.
(Appendix 1)
An annotation program for operating a computer for managing annotation information,
The computer,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
When an operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and the operation log is an annotation assignment operation, a marker that can identify the annotation is embedded in the annotation embedded in the Web resource. Annotation marker giving means for giving,
The operation log for the Web resource extracted from the annotation operation log storage means is selected in time series, and when the operation log is an annotation deletion operation, the deletion embedded in the Web resource using the marker An annotation program that operates as an annotation specific deletion means that specifies and deletes the annotation that is the target of the operation.
(Appendix 2)
The computer,
Of annotation operation log pairs stored in the annotation operation log storage means, an annotation assignment operation and a deletion operation operation that do not affect other annotation assignment positions even if deleted. An annotation position influence analysis means for analyzing log pairs;
Supplementary Note 1 that operates as an annotation operation log rewriting unit that rewrites a pair of operation logs of an annotation giving operation and a deleting operation that do not affect other annotation giving positions even if deleted so as to be deleted from the annotation operation log storage unit Annotation program as described.
(Appendix 3)
An annotation program for operating a computer for managing annotation information,
The computer,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
The operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation assignment operation that has already been deleted, it affects the assignment position of other annotations, Dummy annotation generating means for generating dummy annotation that does not affect the operation of the annotation;
An operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation giving operation, the annotation is embedded in the Web resource, and the operation log has already been stored. An annotation program that operates as an annotation embedding unit that embeds the dummy annotation in the Web resource when the operation is to add an annotation that has been deleted.
(Appendix 4)
An annotation device that manages annotation information,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
When an operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and the operation log is an annotation assignment operation, a marker that can identify the annotation is embedded in the annotation embedded in the Web resource. Annotation marker giving means for giving,
The operation log for the Web resource extracted from the annotation operation log storage means is selected in time series, and when the operation log is an annotation deletion operation, the deletion embedded in the Web resource using the marker An annotation device having annotation specific deletion means for specifying and deleting an annotation to be operated.
(Appendix 5)
An annotation device that manages annotation information,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
The operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation assignment operation that has already been deleted, it affects the assignment position of other annotations, Dummy annotation generating means for generating dummy annotation that does not affect the operation of the annotation;
An operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation giving operation, the annotation is embedded in the Web resource, and the operation log has already been stored. An annotation apparatus comprising: an annotation embedding unit that embeds the dummy annotation in the Web resource when the operation is to add a deleted annotation.
(Appendix 6)
An annotation method for an annotation device that manages annotation information,
A receiving step of receiving a web resource;
An annotation operation log acquisition step for retrieving the operation log for the received Web resource from the annotation operation log storage unit that stores the Web resource identification information and the operation log in association with each other in time series;
When an operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and the operation log is an annotation assignment operation, a marker that can identify the annotation is embedded in the annotation embedded in the Web resource. An annotation marker giving step to be given;
The operation log for the Web resource extracted from the annotation operation log storage means is selected in time series, and when the operation log is an annotation deletion operation, the deletion embedded in the Web resource using the marker An annotation method comprising: an annotation identification / deletion step for identifying and deleting an annotation to be operated.
(Appendix 7)
An annotation method for an annotation device that manages annotation information,
A receiving step of receiving a web resource;
An annotation operation log acquisition step for retrieving the operation log for the received Web resource from the annotation operation log storage unit that stores the Web resource identification information and the operation log in association with each other in time series;
The operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation assignment operation that has already been deleted, it affects the assignment position of other annotations, A dummy annotation generation step for generating a dummy annotation that does not affect the operation of the annotation;
An operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation giving operation, the annotation is embedded in the Web resource, and the operation log has already been stored. An annotation method comprising an annotation embedding step of embedding the dummy annotation in the Web resource when the deleted annotation is added.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

DESCRIPTION OF SYMBOLS 1 Annotation 10 Web resource acquisition part 11 Web resource analysis result preparation part 12 Annotation operation log acquisition part 13 Annotation restoration part 14 Annotation marker assignment part 15 Annotation embedding part 16 Annotation fragment identification part 17 Annotation fragment deletion part 18 Annotation action part 19 Web Resource analysis results 20 Annotation DB
21 Annotation operation log DB
DESCRIPTION OF SYMBOLS 30 Annotation position influence analysis part 31 Annotation operation log rewriting part 40 Dummy annotation text fragment generation part 41 Deleted annotation recognition means 50 Annotation giving apparatus 51 Annotation action apparatus 52 Annotation management server 53 Annotation operation log management apparatus 61 Web browsing apparatus 62 Annotation assignment Extension unit 63 Annotation operation log extension unit 64 Annotation action extension unit 65 Annotation operation log extension unit 66 Web browsing device 67 Annotation DB management unit 68 Annotation DB
69 Annotation List Management Unit 70 Annotation Operation Log DB
81 Input Device 82 Output Device 83 Drive Device 84 Auxiliary Storage Device 85 Main Storage Device 86 Arithmetic Processing Device 87 Interface Device 100 HTML Document 200 Browser 201 HTML Parser 202 DOM Tree 203 Rendering Engine 204 User Interface 205 Javascript Engine 206 Javascript Engine

Claims (5)

An annotation program for operating a computer for managing annotation information,
The computer,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
When an operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and the operation log is an annotation assignment operation, a marker that can identify the annotation is embedded in the annotation embedded in the Web resource. Annotation marker giving means for giving,
The operation log for the Web resource extracted from the annotation operation log storage means is selected in time series, and when the operation log is an annotation deletion operation, the deletion embedded in the Web resource using the marker Operate as annotation specific deletion means to identify and delete the annotation that is the target of operation ,
Even if the annotation is deleted later by a deletion operation, the marker is temporarily added and embedded in the Web resource, and the marker is used based on the deletion operation selected in time series from the operation log. Te, to delete identify the which is the subject of deletion operations that are embedded in a Web resource annotation program. The computer,
Of annotation operation log pairs stored in the annotation operation log storage means, an annotation assignment operation and a deletion operation operation that do not affect other annotation assignment positions even if deleted. An annotation position influence analysis means for analyzing log pairs;
An operation of an annotation operation log rewrite unit that rewrites an operation log pair of an annotation assignment operation and a deletion operation that does not affect another annotation assignment position even if deleted so as to be deleted from the annotation operation log storage unit. The annotation program according to 1. An annotation program for operating a computer for managing annotation information,
The computer,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
The operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation assignment operation that has already been deleted, it affects the assignment position of other annotations, Dummy annotation generating means for generating dummy annotation that does not affect the operation of the annotation;
An operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and when the operation log is an annotation giving operation, the annotation is embedded in the Web resource, and the operation log has already been stored. An annotation program that operates as an annotation embedding unit that embeds the dummy annotation in the Web resource when the operation is to add an annotation that has been deleted. An annotation device that manages annotation information,
Receiving means for receiving Web resources;
An annotation operation log acquisition unit that retrieves an operation log for the received Web resource from an annotation operation log storage unit that stores Web resource identification information and an operation log in association with each other in time series;
When an operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and the operation log is an annotation assignment operation, a marker that can identify the annotation is embedded in the annotation embedded in the Web resource. Annotation marker giving means for giving,
The operation log for the Web resource extracted from the annotation operation log storage means is selected in time series, and when the operation log is an annotation deletion operation, the deletion embedded in the Web resource using the marker the annotation is an operation target specifying to possess the annotation specific deletion means for deleting,
Even if the annotation is deleted later by a deletion operation, the marker is temporarily added and embedded in the Web resource, and the marker is used based on the deletion operation selected in time series from the operation log. An annotation device that identifies and deletes the annotation that is the target of the deletion operation embedded in the Web resource . An annotation method for an annotation device that manages annotation information,
A receiving step of receiving a web resource;
An annotation operation log acquisition step for retrieving the operation log for the received Web resource from the annotation operation log storage unit that stores the Web resource identification information and the operation log in association with each other in time series;
When an operation log for the Web resource extracted from the annotation operation log storage unit is selected in time series, and the operation log is an annotation assignment operation, a marker that can identify the annotation is embedded in the annotation embedded in the Web resource. An annotation marker giving step to be given;
The operation log for the Web resource extracted from the annotation operation log storage means is selected in time series, and when the operation log is an annotation deletion operation, the deletion embedded in the Web resource using the marker operations that are the subject of the annotation specified by chromatic and annotation specific deletion step of deleting,
Even if the annotation is deleted later by a deletion operation, the marker is temporarily added and embedded in the Web resource, and the marker is used based on the deletion operation selected in time series from the operation log. An annotation method for identifying and deleting an annotation that is a target of a deletion operation embedded in the Web resource .

Images