JPWO2009001440A1 - Annotation display program, annotation display method, and annotation display apparatus - Google Patents

Abstract

An object of the present invention is to enable any user to stop displaying additional information related to annotations that are not necessary for him or her so that the display of the additional information does not affect other users. When annotation data related to web page data is requested from the web browser machine, the annotation server machine detects the requested annotation data from the annotation data management table and the detected annotation data. The annotation data defined in the non-displayable state management table 34 is removed from the inside, and the rest is delivered to the requesting web browser machine 20. [Selection] Figure 16

Description

  The present invention relates to a program, method, and apparatus for displaying annotations.

  As is well known, annotation (web annotation) is a mechanism that allows a user of a web page to annotate additional information (metadata) without changing the web page data (see, for example, Patent Documents 1 and 2). This annotation basically consists of two stages, a registration stage and a display stage. In the registration stage, when the user designates a position where the additional information is annotated from the web page being browsed on the web browser and inputs the content of the additional information, the URL [Uniform Resource Locator] of the web page data, The position information of the annotation position and the contents of the additional information are registered in the annotation server as annotation data. In the display stage, when the user instructs the web browser to display the web page, the web browser acquires the web page data from the web server, and also acquires the annotation data related to the web page from the annotation server. Then, the additional information is incorporated into the web page data based on the annotation data, and then the web page is displayed based on the web page data incorporating the additional information.

  By the way, in many web pages, the content is updated moderately, so the content of the additional information related to the annotation may not match the content of the web page. In addition, if the content of the additional information related to the annotation becomes older with time, the annotation may not be meaningful. For this reason, when a problem is felt in the content of the additional information, anyone should be able to stop displaying the additional information.

  Here, in order to prevent the additional information from being displayed, it can be realized by deregistering the annotation itself (by deleting the annotation data from the annotation server). However, if anyone can cancel the registration of annotation, there is a security problem, so it has not been realized so far. However, a mechanism that allows only the user who created the annotation (annotator) to cancel the registration of the annotation has been realized. In this mechanism, annotator user identification information is incorporated into the annotation data at the annotation registration stage, and in the annotation deregistration, authentication is performed based on the user identification information entered by the user and approval is obtained. Only registered users can unregister annotations.

  Note that the annotation server only stores and provides annotation data, and the annotation server and its administrator do not manage annotation data (confirmation of content, determination of necessity, deletion operation), and cancel annotation registration. Is basically left to annotators. For this reason, conventionally, an annotator determines whether or not an annotation is necessary, and based on the determination, maintains or cancels registration.

  However, even annotations that users other than annotators still need are sometimes unregistered by annotators, so only annotations can be unregistered. If this is the case, it may be disadvantageous to other users.

JP 2000-222324 A JP 2003-150542 A

  The present invention has been made in view of the above-described problems of the prior art, and the problem is that any user can stop displaying additional information related to annotations that are unnecessary for the user, and the additional information can be used. The purpose is to prevent other users from being stopped.

  An annotation management program devised to solve the above-described problem is a computer that stores information on the location of web page data for displaying a web page, location information for specifying the location on the web page, and the location. A first storage means for storing annotation data including the content of additional information annotated in an annotation and unique annotation identification information for identifying an annotation based on the additional information in an annotation data management table in the storage device; A record including user identification information for identifying a user, annotation identification information of an annotation whose display should be stopped by the user, and location information of web page data associated with the annotation is stored. The first item stored in the deletion status management table Storage means, first receiving means for receiving location information, user identification information, and annotation data transmission request of any web page data from any web browser machine on the network through a communication device, Display using the location information received by the first receiving means as a search condition, the first search means for searching the annotation data management table, and the location information and user identification information received by the first receiving means as search conditions. Removing means for removing the annotation data relating to the record detected by the second searching means from the annotation data detected by the second searching means and the first searching means for searching the impossible state management table; The annotation data that has been removed by some means is transferred to the requesting web through the communication device. Transmitting means for transmitting to the browser machine, second receiving means for receiving user identification information, annotation identification information, location information of web page data, and a display impossible request from any web browser machine on the network through a communication device And the second receiving unit functions as a display stop unit that stores the record including the user identification information, the annotation identification information, and the location information in the undisplayable state management table.

  With this configuration, when the annotation data related to the web page data is requested from the web browser machine, the computer detects the requested annotation data from the annotation data management table, and from the detected annotation data The annotation data defined in the non-displayable state management table is removed, and the rest is delivered to the requesting web browser machine. Therefore, the annotation data is not delivered to the web browser machine if the related record is registered in the display disabled state management table.

  When the computer receives an annotation data non-display request from the web browser machine, the computer stores a record including the user identification information of the annotation, the annotation identification information, and the location information of the web page data in the non-displayable state management table. Looks like it works. Therefore, the user of the web browser machine can stop the display of the additional information related to the annotation on his / her web browser machine simply by requesting the computer to make the display impossible.

  However, the record registered in the non-displayable state management table includes user identification information. When annotation data is requested from the web browser machine, the record related to the user identification information of the user is referred to. Is done. Accordingly, the user can display additional information related to the annotation data on his / her web browser machine even if other users cannot display the same annotation data.

  Moreover, the annotation management method devised to solve the above-mentioned problem is that the computer has location information of web page data for displaying a web page, position information for specifying a position on the web page, A first storage procedure for storing annotation data including content of additional information annotated at the position and unique annotation identification information for identifying an annotation based on the additional information in the annotation data management table in the storage device A record including user identification information for identifying a user, annotation identification information of an annotation whose display should be stopped by the user, and location information of web page data associated with the annotation And store it in the display disabled state management table in the storage device Second storage procedure: a first reception procedure for receiving location information of any web page data, user identification information, and an annotation data transmission request from any web browser machine on the network through a communication device Using the location information received in the first reception procedure as a search condition, the first search procedure for searching the annotation data management table, and the location information and user identification information received in the first reception procedure as search conditions. A second search procedure for searching the undisplayable state management table; a removal procedure for removing annotation data related to the record detected in the second search procedure from the annotation data detected in the first search procedure; The annotation data left after some of the removal procedures are removed from the request source web browser via the communication device. Transmission procedure for transmitting to the user machine, a second reception procedure for receiving the user identification information, the annotation identification information, the location information of the web page data, and the display impossible request from any web browser machine on the network through the communication device And a display stop procedure for storing the record including the user identification information, the annotation identification information, and the location information received in the second reception procedure in the display disabled state management table.

  Therefore, an apparatus that implements this annotation management method functions as an apparatus equivalent to a computer that operates the annotation management program of the present invention described above.

  Also, the annotation management device devised to solve the above-mentioned problem is the location information of the web page data for displaying the web page, the location information for specifying the location on the web page, and the location. A first storage unit that stores annotation data including the content of additional information to be annotated and unique annotation identification information for identifying an annotation based on the additional information in the annotation data management table, and usage for specifying a user A record including the user identification information, the annotation identification information of the annotation whose display should be stopped by the user, and the location information of the web page data associated with the annotation in the display disabled state management table. Second storage unit to be stored, any one of the networks on the network A first receiving unit that receives location information of any web page data, user identification information, and an annotation data transmission request from a browser machine, and the location information received by the first receiving unit as a search condition A first search unit that searches the annotation data management table, a second search unit that searches the undisplayable state management table using the location information and user identification information received by the first receiving unit as search conditions, From the annotation data detected by the first search unit, a removal unit that removes annotation data related to the record detected by the second search unit, the annotation data that has been removed by some of the removal unit, The user identification information is sent from the sending unit that sends it to the requesting web browser machine or from any web browser machine on the network. , Annotation identification information, location information of web page data, and a second receiving unit that receives a display impossible request, and user identification information, annotation identification information, and location information received by the second receiving unit It is characterized by including a display stop unit for storing records in the display disabled state management table.

  Therefore, this annotation management apparatus functions as an apparatus equivalent to a computer that operates the above-described annotation management program of the present invention.

  Therefore, according to the present invention, any user can stop the display of the additional information related to the annotation unnecessary for the user, and the stop of the display of the additional information does not affect other users.

  The best mode for carrying out the present invention will be described below with reference to the accompanying drawings.

  First, the hardware configuration and software configuration of the computer network system of this embodiment will be described.

  FIG. 1 is a configuration diagram of a computer network system according to the present embodiment.

  As shown in FIG. 1, the computer network system according to this embodiment includes a web server machine 10, a web browser machine 20, and an annotation server machine 30. The machines 10, 20, and 30 are connected to each other via a network N so as to be able to communicate with each other.

  FIG. 2 is a configuration diagram of the web server machine 10.

  The web server machine 10 is a general-purpose computer to which a function as a web server is added. Accordingly, the web server machine 10 includes at least a communication adapter 10a, a storage unit 10b, a CPU [Central Processing Unit] 10c, and a memory unit 10d. The communication adapter 10a is a device for exchanging data with other computers on the network N. The storage unit 10b is a unit for recording various programs and data. The CPU 10c is a unit that performs processing according to a program in the storage unit 10b. The memory unit 10d is a unit for the CPU 10c to cache a program or expand a work area.

  The web server machine 10 stores web page data 11, a web server program 12, and a communication interface program 13 in the storage unit 10b. The web page data 11 is HTML (HyperText Markup Language) data provided to another computer through the network N as illustrated in FIG. Each web page data 11 is assigned a unique URL [Uniform Resource Locator] as its location information. It is assumed that the URL http: //xxx/a.html is assigned to the web page data 11 illustrated in FIG. The web server program 12 is a program for realizing the function of the web server on a computer. The function by the web server program 12 (hereinafter referred to as the web server 12) is the function of the web page at the URL when an HTTP [HyperText Transfer Protocol] request message is received from the web browser machine 20 together with information specifying the URL. An HTTP response message including data 11 in the body is transmitted. The communication interface program 13 is a protocol stack (program) for exchanging data with other computers via the network N according to TCP / IP [Transmission Control Protocol / Internet Protocol].

  FIG. 4 is a configuration diagram of the web browser machine 20.

  The web browser machine 20 is a personal computer to which a web browser function is added. Accordingly, the web browser machine 20 includes a display unit 20a such as a liquid crystal display, an input unit 20b such as a keyboard and a mouse, and a main body to which these units 20a and 20b are connected. The main body incorporates at least a communication adapter 20c, a storage unit 20d, a CPU 20e, and a memory unit 20f.

  Further, the web browser machine 20 stores web browser software 21 and a communication interface program 22 in the storage unit 20d. The web browser software 21 is software for realizing the function of the web browser on a computer. The function of the web browser software 21 (hereinafter referred to as the web browser 21) acquires web page data 11 from the web server machine 10 based on an instruction from the operator, and based on the acquired web page data 11. Display a web page in a window under control. The web browser software 21 includes a web client 21a, a parser 21b, and a renderer 21c. The web client 21 a is a program for acquiring the web page data 11 through exchanging HTTP messages with the web server 12 in the web server machine 10. The parser 21b is a program for separating tags from the web page data 11, analyzing a sentence structure and the like based on the tags, and converting the web page data 11 into a form that can be used by the renderer 21c. The renderer 21c is a program for drawing a web page based on the web page data 11 whose form has been converted by the parser 21b.

  Further, the web browser software 21 includes an annotation registration program 21d, an annotation built-in program 21e, and an annotation cancellation program 21f as programs for the extended functions. The annotation registration program 21d is a program for accepting annotation registration (to be described later) from the operator and instructing the annotation server machine 30. The annotation built-in program 21e is a program for obtaining annotation data, which will be described later, from the annotation server machine 30 and incorporating additional information related to the annotation data into the web page data 11. The annotation cancellation program 21f is a program for receiving an annotation cancellation described later from the operator and instructing the annotation server machine 30. The contents of the processing executed by the CPU 20e according to the programs 21d to 21f related to these annotations will be described later with reference to FIGS.

  The communication interface program 22 is a TCP / IP stack similar to that of the web server machine 10.

  FIG. 5 is a configuration diagram of the annotation server machine 30.

  The annotation server machine 30 is a general-purpose computer to which an annotation server function is added. Therefore, the annotation server machine 30 includes at least a communication adapter 30a, a storage unit 30b, a CPU 30c, and a memory unit 30d.

  Further, the annotation server machine 30 includes a user information management table 31, an annotation data management table 32, an access log table 33, an undisplayable state management table 34, a registration program 35, a provision program 36, and a release program 37 in the storage unit 30b. The communication interface program 38 is stored.

  FIG. 6 is a diagram schematically showing the table structure of the user information management table 31.

  The user information management table 31 is a table for managing information related to annotation users. As shown in FIG. 6, the user information management table 31 has the same number of records as the user. Each record has fields of “user ID [Identification]”, “name”, “name”, “nickname”, and “registration date”. The “user ID” field is a field in which a user ID, which is unique identification information for identifying a user, is recorded. Each field of “Mr.” and “Name” is a field in which the last name and name of the user are recorded. The “nickname” field is a field in which the user's name is recorded. The “registration date and time” field is a field in which the date and time when the user is registered as the annotation user is recorded.

  FIG. 7 is a diagram schematically showing the table structure of the annotation data management table 32. As shown in FIG.

  The annotation data management table 32 is a table for managing annotation data. As shown in FIG. 7, the annotation data management table 32 has the same number of records as the annotation data. Each record has fields of “data ID”, “URL”, “location information”, “user ID”, “registration date”, and “content”. The “data ID” field is a field in which a data ID that is unique identification information for specifying annotation data is recorded. The “URL” field is a field in which a URL that is the location information of the web page data 11 is recorded. The “position information” field is a field in which position information for specifying a position where the additional information is annotated in the web page based on the web page data 11 is recorded. Here, the positional information includes, for example, each block (<body> and </ body>) that are related in a tree structure on the source text, such as information described according to Xpath [XML Path Language]. The portion between the start tag and the end tag may be information specifying a route or node of one block), or may be a block ID uniquely assigned to each block. In any case, the position information is abstract information that logically specifies the position of the object (character string) to which the additional information is annotated. The “user ID” field is a field in which the user ID of the user (annotator) who created the annotation is recorded. The “registration date / time” field is a field in which the date / time when annotation data is registered in the table 32 is recorded. The “content” field is a field in which the content of the additional information related to the annotation is recorded.

  The annotation server machine 30 that stores annotation data in the annotation data management table 32 corresponds to the first storage unit and the first storage unit described above. The annotation server machine 30 storing annotation data in the annotation data management table 32 corresponds to the first storage procedure described above.

  FIG. 8 is a diagram schematically showing the table structure of the access log table 33.

  The access log table 33 is a table for managing the history of request for annotation data from the web browser 21 as log data. As shown in FIG. 8, the access log table 33 has the same number of records as the number of requests from the web browser 21. Each record has fields of “user ID”, “URL”, “log number”, and “access date / time”. The “user ID” field is a field in which a user ID of a user who has performed an operation for generating a request for annotation data is recorded. The “URL” field is a field in which the URL of the web page data 11 related to the requested annotation data is recorded. The “log number” field is a field in which a log number, which is unique identification information for specifying log data, is recorded. The “access date / time” field is a field in which the date / time when the annotation data is requested is recorded.

  FIG. 9 is a diagram schematically showing a table structure of the display disabled state management table 34. As shown in FIG.

  The non-displayable state management table 34 is a table for managing information related to annotations that are determined to be stopped by each user. As shown in FIG. 9, the display impossibility state management table 34 has the same number of records as the annotations that each user determines to stop displaying. Each record has fields of “user ID”, “URL”, “data ID”, and “release date”. The “user ID” field is a field in which a user ID is recorded. The “URL” field is a field in which the URL of the web page data 11 related to the annotation whose display is determined to be stopped is recorded. The “data ID” field is a field in which the data ID of an annotation for which display is determined to be stopped is recorded. The “release date and time” field is a field in which the date and time when the display is stopped by registering information related to the annotation in the table 34 is recorded.

  Note that the annotation server machine 30 that stores information related to the annotation for which display is determined to be stopped in the non-displayable state management table 34 corresponds to the second storage unit described above and the second storage unit described above. Yes. In addition, the annotation server machine 30 storing the information related to the annotation for which display is determined to be stopped in the non-displayable state management table 34 corresponds to the second storage procedure described above.

  Next, the flow of processing related to creation and registration of annotation data will be described.

  First, in the web browser machine 20, when a predetermined operation such as dragging and clicking on any part of the web page displayed in the window under the control of the web browser 21 is performed through the input unit 20b, The CPU 20e activates the annotation registration program 21d and starts annotation registration processing.

  FIG. 10 is a diagram showing the flow of annotation registration processing.

  In the first step S101 after the start of the annotation registration process, the CPU 20e displays an annotation input screen described later on the display unit 20a. For example, when the web page 41 shown in FIG. 11 is displayed on the display unit 20a based on the web page data 11 illustrated in FIG. 3, the first line in the web page 41 is selected and a predetermined operation is performed. When done, an annotation input screen 42 as shown in FIG. 12 is displayed on the display unit 20a. The annotation input screen 42 includes a text box 42a for inputting the content of additional information to be annotated with respect to a location in the web page 41 where a predetermined operation has been performed. The annotation input screen 42 also includes a registration button 42b to be clicked when the input to the text box 42a is completed, and a stop button 42c to be clicked when canceling such a registration operation. Yes.

  In the next step S102, the CPU 20e stands by until one of the two buttons 42b and 42c in the annotation input screen 42 in FIG. 12 is clicked. When any button is clicked, the CPU 20e advances the process to step S103.

  In step S103, the CPU 20e determines how many buttons are clicked. If the clicked button is the cancel button 42c, the CPU 20e branches the process from step S103, and ends the annotation registration process according to FIG. On the other hand, if the clicked button is the registration button 42b, the CPU 20e advances the process to step S104.

  In step S104, the CPU 20e acquires position information of a portion on the web page designated as an annotation position of additional information related to the annotation. Specifically, the CPU 20e first identifies each block related in a tree structure on the source text of the web page data 11, and identifies information for each block (information identifying a route or a node, or , By generating a unique block ID [Identification]) for each block, the structure of the web page data 11 is analyzed. Next, the CPU 20e identifies the lowest layer block including the portion designated as the annotate position of the additional information, and sets the information that logically identifies the block as the target position information. In the example of FIGS. 3 and 11, this position information can be expressed as “/ HTML / BODY / P / text ()” by Xpath.

  In the next step S105, the CPU 20e acquires a user ID. The user ID may be registered in advance in the web browser 21 or may be acquired through a dialog box including a text box for inputting the user ID.

  In the next step S106, the CPU 20e, the URL of the web page data 11 of the web page to which the additional information related to the annotation is pasted, the location information obtained in step S104, the user ID obtained in step S105, and the annotation input in FIG. The contents of the additional information inputted in the text box 42a when the registration button 42b on the screen 42 is detected in step S102 and the registration request for the annotation data are transmitted to the annotation server machine 30. The information transmitted to the annotation server machine 30 together with the registration request can be expressed as shown in FIG. 13 in the example of FIGS. Thereafter, the CPU 20e ends the annotation registration process according to FIG.

  On the other hand, when the annotation server machine 30 receives the annotation data registration request, the CPU 30c activates the registration program 35 and starts the registration process.

  FIG. 14 is a diagram showing the flow of registration processing.

  In the first step S201 after the start of the registration process, the CPU 20e issues a new data ID that has never been used in the annotation data management table 32.

  In the next step S202, the CPU 20e reads the date and time at this time from an internal clock unit (not shown).

  In the next step S203, the CPU 20e converts the annotation data including the received information (URL, location information, user ID, contents), the data ID issued in step S201, and the date and time read in step S202, to the annotation data. Add to the management table 32. Thereafter, the CPU 20e ends the registration process according to FIG.

  As described above, since the annotation registration program 21d (FIG. 10) in the web browser machine 20 and the registration program 35 (FIG. 14) in the annotation server machine 30 are linked, the annotation registration operation is performed by the user. For example, annotation data is registered in the annotation data management table 32. The record in the first line of the annotation data management table 32 in FIG. 7 is obtained by registering the data related to the annotation shown in the examples of FIGS. 3, 11, and 13 by the registration processing according to FIG. .

  Next, the flow of processing related to the display of annotation will be described.

  First, in the web browser machine 20, the link in the web page displayed in the window under the control of the web browser 21 is operated through the input unit 20b, or the URL is directly input, When the display of the web page is instructed, the CPU 20e acquires the web page data 11 through the web server 12 according to the web client 21a. At this time, the CPU 20e starts the annotation incorporation program 21e and starts the annotation incorporation process.

  FIG. 15 is a diagram illustrating the flow of the annotation incorporation process.

  In the first step S301 after the start of the annotation incorporation process, the CPU 20e acquires the request destination URL from the web client 21a.

  In the next step S302, the CPU 20e acquires a user ID. As described above, the user ID may be registered in advance in the web browser 21 or obtained through a dialog box including a text box for inputting the user ID. Also good.

  In the next step S303, the CPU 20e makes an inquiry to the annotation server machine 30 by transmitting the URL acquired in step S301, the user ID acquired in step S302, and the inquiry request.

  In the next step S304, the CPU 20e stands by until a response to the inquiry in step S303 is received from the annotation server machine 30.

  On the other hand, in the annotation server machine 30, when the CPU 30c receives this inquiry request, it starts the providing program 36 and starts the providing process.

  The CPU 30c that receives the inquiry request, the URL, and the user ID corresponds to the first receiving unit described above and the first receiving unit described above. In addition, the reception of the inquiry request, the URL, and the user ID by the CPU 30c corresponds to the first reception procedure described above.

  FIG. 16 is a diagram showing the flow of the providing process.

  In the first step S401 after the start of the providing process, the CPU 30c searches the annotation data management table 32 of FIG. 7 using the URL received from the web browser machine 20 as a search condition.

  Note that the CPU 30c executing step S401 corresponds to the first search unit described above and the first search unit described above. Step S401 corresponds to the first search procedure described above.

  In the next step S402, the CPU 20e temporarily stores the record detected by the search in step S401 in a work table (not shown).

  In the next step S403, the CPU 20e searches the undisplayable state management table 34 of FIG. 9 using the URL received from the web browser machine 20 and the user ID as search conditions.

  The CPU 30c executing step S403 corresponds to the above-described second search unit and the above-described second search unit. Step S403 corresponds to the second search procedure described above.

  In the next step S404, the CPU 20e deletes a record including the same data ID as the record detected by the search in step S403 from a work table (not shown).

  The CPU 30c that executes step S404 corresponds to the above-described removing unit and the above-described removing unit. Step S404 corresponds to the above-described removal procedure.

  In the next step S405, the CPU 20e transmits annotation data in a work table (not shown) as a response to the web browser machine 20 that is an inquiry source. Thereafter, the CPU 30c ends the providing process according to FIG.

  On the other hand, in the web browser machine 20, when the CPU 20e receives this response, the first processing loop L1 of FIG. 15 is executed.

  In the first processing loop L1, the CPU 20e sequentially executes the processing consisting of steps S305 to S309 for all annotation data received from the annotation server machine 30.

  In step S305, the CPU 20e generates an HTML tag group for displaying the content of the additional information included in the processing target annotation data on the web page as an annotation.

  In the next step S306, the CPU 20e searches for an object reference (not shown) developed in the memory unit 20f for the node elements constituting the web page data 11 using the position information included in the processing target annotation data as a search condition. The object reference is information that defines a method for reaching an object (a character string of a portion of the web page data 11 in which additional information is annotated) in the form of a containment tree. When processing, it expands on the memory unit 20f. Since this object reference is well-known, its description is omitted.

  In the next step S307, the CPU 20e determines whether or not an object has been detected as a result of the search in step S306. If the object can be detected, the CPU 20e advances the process to step S308.

  In step S308, the CPU 20e inserts the tag group generated in step S305 at a position on the web page data 11 specified by the position information included in the processing target annotation data. The web page data 44 in FIG. 17 is a tag group based on the record in the first line of the annotation data management table 32 in FIG. 7 (that is, the annotation data according to the examples in FIGS. 11 and 13). 11 shows the state of insertion. Thereafter, the CPU 20e ends the processing for the processing target annotation data in the first processing loop L1.

  On the other hand, when the object cannot be detected, the CPU 20e branches the process from step S307 to step S309.

  In step S309, the CPU 20e inserts the tag group generated in step S305 at the position specified by “/ HTML / BODY” (that is, the position corresponding to the upper left corner of the web page when the web page is displayed). To do. Thereafter, the CPU 20e ends the processing for the processing target annotation data in the first processing loop L1.

  When the CPU 20e finishes executing the processing including steps S305 to S309 for all annotation data received from the annotation server machine 30, the CPU 20e leaves the first processing loop L1 and ends the annotation incorporation processing according to FIG. To do.

  As described above, since the annotation built-in program 21e (FIG. 15) in the web browser machine 20 and the provision program 36 (FIG. 16) in the annotation server machine 30 cooperate with each other, the user instructs the display of the web page. If there is an instruction to obtain and incorporate annotation data from the web browser 21 that has been made, the annotation data is provided from the annotation server machine 30 to the web browser machine 20, and the web page obtained by the web browser 21 from the web server 12 Additional information related to the annotation data is incorporated into the data 11 in a form displayed as an annotation (a form interpreted by the renderer 21c). FIG. 18 shows a state where annotations are attached to the web page 41 of FIG. The web page 45 shown in FIG. 18 is displayed based on the web page data 44 of FIG. 17, and the annotation is pasted at the beginning of the first line.

  When the additional information related to the annotation is incorporated into the web page data 11 by the annotation incorporation program 21e, the renderer 21c then draws the web page based on the web page data 11, and the additional information related to the web page and the annotation is added. Information is displayed in a window under the control of the web browser 21.

  Next, the flow of processing related to the stop and release of annotation display will be described.

  The additional information displayed together with the web page through the display process as described above may be described as a simple character in the web page, but in the present embodiment, it is described in a pop-up window. . This pop-up window includes an “x” button for instructing the cancellation of the annotation. When this “x” button is operated, the CPU 20e activates the annotation cancellation program 21f to perform the annotation cancellation process. It is supposed to start.

  FIG. 19 is a diagram showing the flow of annotation cancellation processing.

  In the first step S501 after the start of the annotation cancellation process, the CPU 20e displays a confirmation dialog. Although not shown in the confirmation dialog, it is described that an inquiry about whether to actually cancel the annotation is made. In addition, the confirmation dialog includes a “Yes” button that is clicked when cancellation of annotation is continued, and a “No” button that is clicked when cancellation of annotation is canceled.

  In the next step S502, the CPU 20e waits until one of two buttons in a confirmation dialog (not shown) is clicked. When any button is clicked, the CPU 20e advances the process to step S503.

  In step S503, the CPU 20e determines whether the clicked button is a “Yes” button. If the clicked button is a “No” button, the CPU 20e branches the process from step S503, and ends the annotation cancellation process according to FIG. On the other hand, if the clicked button is a “yes” button, the CPU 20e advances the process to step S504.

  In step S <b> 504, the CPU 20 e transmits the data ID, user ID, URL, and release request related to the annotation to the annotation server machine 30. Thereafter, the CPU 20e ends the annotation cancellation process according to FIG.

  On the other hand, in the annotation server machine 30, when the CPU 30c receives this release request, the release program 37 is activated to start the release process.

  Note that the CPU 30c that receives the release request and the information related to the annotation corresponds to the above-described second receiving unit and the above-described second receiving unit. In addition, the reception of the release request and the information related to the annotation by the CPU 30c corresponds to the second reception procedure described above.

  FIG. 20 is a diagram illustrating the flow of the release process.

  In the first step S601 after the start of the release process, the CPU 30c reads the date and time at this time from a built-in clock unit (not shown).

  In the next step S602, the CPU 30c registers a record including the data ID, user ID, and URL received from the web browser machine 20 and the date and time read in step S601 in the undisplayable state management table 34 of FIG. . FIG. 21 shows a state after a new record (record indicated by an arrow) is added to the non-displayable state management table 34 of FIG.

  Note that the CPU 30c that executes step S602 corresponds to the display stop unit and the display stop unit described above. Step S602 corresponds to the display stop procedure described above.

  In the next step S603, the CPU 30c executes a weight calculation subroutine.

  FIG. 22 is a diagram showing a flow of processing by the weight calculation subroutine.

  In the first step S701 after the start of the weight calculation subroutine, the CPU 30c generates a new work table on the memory unit 30d.

  FIG. 23 is a diagram schematically showing the table structure of the work table 46.

  The work table 46 is a table for temporarily storing the number of times each user has accessed the web page. As shown in FIG. 23, each record of the work table 46 has fields of “user ID”, “number of accesses”, and “weight”. The “user ID” field is a field in which the user ID of the user is recorded. The “access count” field is a field in which the number of times the user accesses the web page of the URL received from the web browser machine 20 is recorded. The “weight” field is a field in which a weight (described later) determined according to the number of accesses by the user is recorded.

  The CPU 30c generates a new work table 46 in which no record is stored on the memory unit 30d, and then advances the processing to step S702 in FIG.

  In step S702, the CPU 30c reads the user information management table 31 of FIG. 6, and then executes the second processing loop L2.

  In the second processing loop L2, the CPU 30c sequentially executes the processing consisting of steps S703 to S706 for all the user IDs in the user information management table 31 of FIG.

  In step S703, the CPU 30c extracts a record including both the processing target user ID and the URL from the access log table 33 in FIG.

  In the next step S704, the CPU 30c removes from the record extracted in step S703 a record that does not include an access date and time within a predetermined period (for example, three months) from this point.

  In the next step S705, the CPU 30c counts the records that remain after being removed in step S704.

  In the next step S706, the CPU 30c stores the processing target user ID and the access count obtained in step S705 as a new record in the work table 46 of FIG. However, the “weight” field of the new record remains blank.

  The CPU 30c finishes executing the process consisting of steps S703 to S706 for all the user IDs in the user information management table 31 of FIG. 6, and then leaves the first process loop L1 and proceeds to step S707. To proceed.

  In step S707, the CPU 30c calculates and records the weight value of each user based on the number of accesses in the work table 46 of FIG. Specifically, the CPU 30c first identifies a record having the maximum number of accesses from the work table 46, and stores 1 in the “weight” field of the record. Subsequently, the CPU 30c obtains a value by dividing the number of accesses by the maximum number of accesses for records other than the record, and stores the value in the “weight” field. That is, the CPU 30c calculates, as a weight value, a value obtained by normalizing another access count with the maximum access count.

  After calculating the weight value for each user in this way, the CPU 30c ends the weight calculation subroutine according to FIG. 22, and advances the process to step S604 in FIG.

  In step S604, the CPU 30c extracts a record including the data ID received from the web browser machine 20 from the display disabled state management table 34 of FIG. 9, and reads the user ID from each extracted record.

  In the next step S605, the CPU 30c reads out the weight value corresponding to each user ID acquired in step S604 from the work table 46 of FIG. 23, and calculates the unnecessary degree based on each weight value. . Specifically, the CPU 30c calculates the unnecessary degree by adding the respective weight values and dividing the sum by the number of records (the number of registered users) in the user information management table 31 of FIG.

  In the next step S606, the CPU 30c determines whether or not the unnecessary degree calculated in step S605 is greater than or equal to a predetermined threshold value. If the degree of unnecessary is less than the predetermined threshold, the CPU 30c branches the process from step S606 and ends the cancellation process according to FIG. On the other hand, when the unnecessary degree is equal to or greater than the predetermined threshold, the CPU 30c advances the process to step S607.

  In step S607, the CPU 30c deletes the record (annotation data) including the data ID received from the web browser machine 20 from the annotation data management table 32 of FIG. FIG. 24 shows a state after deleting a record (annotation data) from the annotation data management table 32 of FIG. Thereafter, the CPU 30c ends the release process according to FIG.

  As described above, since the annotation cancellation program 21f (FIG. 19) in the web browser machine 20 and the cancellation program 37 (FIGS. 20 and 22) in the annotation server machine 30 cooperate, any annotation is not necessary. Is specified (the “×” button of the pop-up window is operated), information related to the unnecessary annotation is registered in the display disabled state management table 34 of FIG. 9 and at that time related to the annotation. The annotation data is deleted from the annotation data management table 32 of FIG. 7 according to the degree of unnecessaryness.

  Next, the effect of the computer network system of this embodiment will be described.

  The annotation whose information is registered in the display disabled state management table 34 in FIG. 9 is transmitted to the user's web browser machine 20 as described in the providing process of FIG. 16 even if requested by the web browser 21. Not. For this reason, the additional information related to the annotation is not displayed. At this time, even if other users are in a non-displayable state for the same annotation (registered in the non-displayable state management table 34 in FIG. 9), the fact that the user IDs do not match is shown in FIG. Since no record is detected from the non-displayable state management table 34 (step S403 in FIG. 16), after all, the cancellation state of the annotation by other users does not affect the display of the own annotation.

  In the present embodiment, after the user registers information related to an arbitrary annotation in the display disabled state management table 34 of FIG. 9 (steps S601 and S602), the number of users who have disabled the display of the annotation is set. When the unnecessary degree is calculated and the unnecessary degree is equal to or greater than a predetermined threshold, the annotation data itself is deleted from the annotation data management table 32 (steps S603 to S607). At this time, the degree of unnecessaryness is not simply calculated from the number of users, but is also calculated from the sum of the weights by assigning the weight of the user to 1 which is the number of users per user. You can also This weight increases as the user who accesses the web page more frequently (step S605). The greater the weight value, the more reliable the user's judgment regarding the maintenance and cancellation of annotation registration is. It shows what can be done. And since an unnecessary degree is calculated based on the sum total of such a weight, the user with a larger weight value will contribute to the increase in an unnecessary degree, and will exert influence.

  In the present embodiment described above, the weight of the user is calculated based on the number of accesses to the same web page. However, the present invention is not limited to this. For example, the weight of the user may be calculated based on the number of additional information annotated for the same web page. According to such weights, a user having a larger weight value uses an annotation, and therefore can make a judgment on maintaining and canceling the registration of the annotation.

  FIG. 25 is a diagram illustrating a flow of processing by a weight calculation subroutine in a modified form in which the weight of a user is calculated based on the number of additional information annotated for the same web page. FIG. 26 is a diagram schematically showing the table structure of the work table 47 used in the weight calculation subroutine in this modification.

  As is apparent from a comparison between FIG. 22 and FIG. 25, step S703 and step S753 are different. In step S703, as described above, the CPU 30c extracts the record including the processing target user ID and the URL from the access log table 33 in FIG. 8, but in the modified step S753, the CPU 30c A record including the user ID and URL is extracted from the annotation data management table 32 of FIG. Through this step S753, the number of registered annotations for the same web page is counted for each user (step S755), and a value normalized from this number is calculated as a weight. (Step S757, FIG. 26).

  In this embodiment (FIG. 22) and its modification (FIG. 25), the weight imposed on the number of users who cannot display the annotation is not always necessary, and the display is simply stopped for the annotation. The annotation data may be deleted based on the instructed number of users. In that case, in the deletion process of FIG. 20, steps S603 to S605 must be replaced with a step of counting the number of corresponding records in the display disabled state management table 34 of FIG. As a result of the replacement, in step S606, whether to delete annotation data is determined depending on whether the number of records is equal to or greater than a predetermined threshold.

  In the above, the embodiment in which the web browser machine 20 is provided with a program necessary for displaying an annotation, such as the annotation embedded program 21e, has been described. However, in implementing the present invention, it is not necessary to be limited to such a configuration. For example, even if these programs are provided in the annotation server machine 30, the effect of the present invention can be obtained.

Configuration diagram of the computer network system of the present embodiment Configuration diagram of web server machine Diagram showing an example of web page data Web browser machine configuration diagram Configuration diagram of annotation server machine The figure which shows the table structure of a user information management table typically The figure which shows the table structure of the annotation data management table typically The figure which shows the table structure of the access log table typically The figure which shows the table structure of a non-displayable state management table typically Diagram showing the flow of annotation registration processing The figure which shows the web page displayed based on the web page data of FIG. Figure showing an example of annotation input screen Diagram showing information sent to the annotation server machine along with the registration request Diagram showing the flow of registration processing Diagram showing the flow of annotation integration processing Diagram showing the flow of provision processing The figure which shows the state which inserted the tag group based on the annotation data based on the illustration of FIG.11 and FIG.13 in the web page data of FIG. The figure which shows the state by which the annotation was stuck on the web page of FIG. Diagram showing the flow of annotation release processing Diagram showing the flow of release processing The figure which shows the state which added the new record to the display impossible state management table of FIG. The figure which shows the flow of processing by the weight calculation subroutine The figure which shows the table structure of the work table typically The figure which shows the state which deleted the record from the annotation data management table of FIG. The figure which shows the flow of a process by the weight calculation subroutine in a deformation | transformation form The figure which shows typically the table structure of the work table used by the weight calculation subroutine in a deformation | transformation form

Explanation of symbols

10 Web server machine 10b Storage unit 10c CPU
11 Web page data 12 Web server program 20 Web browser machine 20a Display unit 20b Input unit 20d Storage unit 20e CPU
21 Web browser software 21d Annotation registration program 21e Annotation incorporation program 21f Annotation release program 30 Annotation server machine 30b Storage unit 30c CPU
31 User information management table 32 Annotation data management table 33 Access log table 34 Undisplayable state management table 35 Registration program 36 Provided program 37 Cancellation program 41 Web page 42 Annotation input screen 42a Text box 42b Registration button 42c Cancel button 46 Work table 47 Work table

Claims (4)

Computer
A database in which a URL, annotation data affixed to web page data specified by the URL, and user identification information of a user that does not need to display the annotation data are recorded in association with each other;
Acquisition means for acquiring web page data corresponding to a URL instructed by a user from a web server;
Annotation data that is attached to the web page data specified by the URL by referring to the database using the user identification information of the user and the URL, and is not required to be displayed to the user. An extraction means for extracting only annotation data;
An adding means for adding the annotation data extracted by the extracting means to the web page data acquired by the acquiring means; and
An annotation display program which causes the adding means to function as display means for displaying web page data to which annotation data has been added.   The extraction means counts the number of users who do not need to display annotation data in the database, and extracts annotation data other than annotation data in which the number of users who do not need to display exceeds a predetermined threshold. The annotation display program according to claim 1. A database in which URLs, annotation data pasted on web page data specified by the URLs, and user identification information of users who do not need to display the annotation data are recorded in association with each other;
Acquisition means for acquiring web page data corresponding to a URL instructed by a user from a web server;
Annotation data that is attached to the web page data specified by the URL by referring to the database using the user identification information of the user and the URL, and is not required to be displayed to the user. An extraction means for extracting only annotation data;
An adding means for adding the annotation data extracted by the extracting means to the web page data acquired by the acquiring means;
Display means for displaying web page data to which annotation data is added in the adding means;
An annotation display device comprising: An annotation display method by an annotation display device for adding and displaying annotation data to web page data,
An acquisition step of acquiring web page data corresponding to a URL instructed by a user from a web server;
Using the user identification information of the user and the URL, the URL, annotation data affixed to the web page data specified by the URL, and user identification of the user who does not need to display the annotation data An extraction step of referring to a database recorded in association with information and extracting only annotation data that is pasted on the web page data specified by the URL and is not required to be displayed to the user When,
An addition step of adding the annotation data extracted in the extraction step to the web page data acquired in the acquisition step;
A display step of displaying the web page data to which the annotation data is added in the adding step;
Annotation display method characterized by including:

Images