JP2008117374A - Page additional information sharing management method - Google Patents

Abstract

One or more people can add additional information including highlighting of underline, marker, italic, bold, etc., and annotation information such as comments and related articles to objects such as character strings in a page. Provided is a page additional information sharing management method that makes it possible to visualize how a system user is interested so that it can be seen at a glance when browsing a page.
A management method in which a plurality of users attach additional information including highlighting and necessary comments to an object in an arbitrary page, and the plurality of users share the additional information. Browsing when a request to receive additional information including a range specification for an object in the file, a saving step to store the received additional information in association with the target page, and display of additional information are requested A providing step of acquiring additional information corresponding to the page and providing it to the request source.
[Selection] Figure 2

Description

  The present invention relates to a technique for operating a web page on the Internet.

  Opportunities for browsing a wide variety of Web pages are increasing due to the spread of the Internet. However, since the amount of information is enormous, it has become difficult to select useful information from among them.

  In such a situation, when a page of interest is found, a technique called a social bookmark exists as a technique for sharing the URL (Uniform Resource Locator) with other users. The user can register the URL of a Web page in a social bookmark using the browser toolbar, etc., in the same way as a normal bookmark, and the registered social bookmark can be used from other computers connected to the network. .

  The applicant has not been able to find published prior art documents related to the present invention by the time of filing. Therefore, prior art document information is not disclosed.

  In the above-mentioned social bookmark, by sharing the URL of a specific Web page among multiple users, it is possible to know how each system user is interested, and efficiently use useful information from a vast amount of information. It is effective in acquiring.

  However, since social bookmarks can only specify the URL of a web page, if the page content is enormous or complicated, it is impossible to specify which part of it is interested in Met.

  The present invention has been proposed in view of the above-described conventional problems. The object of the present invention is to highlight one or more objects such as underline, marker, italic, and bold on an object such as a character string in a page. Additional information including annotation information such as comments can be added, and the page additional information sharing can be visualized so that each user of the system can be made visible while viewing the page at a glance. To provide a management method.

  In order to solve the above-mentioned problems, according to the present invention, as described in claim 1, additional information including highlighting and necessary comments is attached to an object in an arbitrary page by a plurality of users. In addition, a management method for sharing the additional information among a plurality of users, and accepting the setting of the additional information including the range specification for the object in the page, and the received additional information corresponding to the target page A page additional information sharing management method comprising a storing step of attaching and storing and a providing step of acquiring additional information corresponding to a page to be browsed and providing to a request source when display of additional information is requested Yes.

  Further, as described in claim 2, in the page additional information sharing management method according to claim 1, the browser for browsing the page browses a script for performing a request for acquiring additional information and rendering the acquired additional information. It can be provided with a step of providing it to the browser side by including it in the target page data.

  Further, as described in claim 3, in the page additional information sharing management method according to claim 1 or 2, the additional information is combined with the page data to be browsed and provided to the request source. The process to perform can be provided.

  In addition, as described in claim 4, in the page additional information sharing management method according to any one of claims 1 to 3, a step of storing in a cache a page to be set for the additional information; Providing a cache of the corresponding page when browsing to the page is requested.

  Further, as described in claim 5, in the page additional information sharing management method according to claim 1, the accepting step acquires additional information from a trackback article on the trackback side based on a predetermined tag. To be able to.

  Also, as described in claim 6, in the page additional information sharing management method according to any one of claims 1 to 5, a user who is strongly related to the current user is found based on the stored additional information. Can be provided with the process of presenting.

  Further, as described in claim 7, in the page additional information sharing management method according to any one of claims 1 to 6, the object is a character string, and the range specification specifies a head position. This can be done by specifying a character string and a character string specifying the end position.

  In addition, as described in claim 8, in the page additional information sharing management method according to any one of claims 1 to 6, the object is a character string, and the range specification is described in a markup language. This can be done by specifying the elements of the document.

  Further, as described in claims 9 to 14, it can be configured as a page additional information sharing management device.

  In the page additional information sharing management method of the present invention, one or a plurality of persons can add additional information including highlighting and annotation information to objects in the page, and these can be seen with a view when browsing the page. In this way, it is possible to visualize how each system user is interested.

  Hereinafter, preferred embodiments of the present invention will be described.

<Overview>
FIG. 1 is a diagram showing an example of a screen according to an embodiment of the present invention.

  FIG. 1 shows an example of a screen 23 when a user c (usr_c) is browsing a Web page with a browser. In addition to the contents of the original page being browsed, an underline L1 drawn by the user c, etc. The underline L2 drawn by the user a (usr_a) and the underline L3 drawn by the other user b (usr_b) are displayed, and the current user c is displayed to the right of the horizontal position corresponding to each of the underlines L1 to L3. On the other hand, a frame B1 that enables operations such as "draw another underline" and "write a comment", a frame B2 indicating a comment corresponding to the underline L2 drawn by another user a, and an underline drawn by another user b A frame B3 or the like indicating a comment corresponding to L3 is displayed.

  In addition, although the case where an underline is mainly added as an highlight display of the additional information on the page has been described as an example, a marker, italic, bold, or the like may be used.

  In this way, additional information including highlighting such as underline and annotation information such as comments can be added to any Web page, and it can be shared with other users, so that each system user is interested. This is effective in efficiently obtaining useful information from a vast amount of information.

<First Embodiment>
FIG. 2 is a diagram illustrating a configuration example of a system according to the first embodiment of the present invention.

  2, the system includes a server 1 that manages additional information, a browser 2 that is operated by a user U, and an arbitrary external Web server 3 that is a browsing target. The server 1, the browser 2, and the web server 3 are connected via a network such as the Internet.

  The server 1 includes a standard Web server component 101, a JavaScript generation unit 102 that generates JavaScript for acquiring and rendering (drawing) additional information when browsing the Web page in the browser 2, and additional information by the user U And a page generation unit 103 that generates a registration detail page and a page for displaying a list of additional information.

  In addition, the server 1 transmits information to the browser 2, a user authentication unit 105 that manages and authenticates user information that uses the functions of the server 1, a request processing unit 106 that processes a request from the browser 2, and the browser 2. An additional information transmitting unit 108 that calculates a user relevance level and a user relevance level calculation unit 109 that discovers another user (a person who is expected to have similar interests) marking a location similar to the current user. It has.

  The server 1 also includes a cache DB (Data Base) 110 that holds page data of a Web page for which additional information is registered, and an additional information DB 111 that holds additional information.

  The browser 2 includes a JavaScript engine 21 that executes JavaScript, a registration bookmarklet (script written in JavaScript) 22 that registers additional information, and a screen 23 that displays a Web page and the like.

  FIG. 3 is a diagram illustrating an example of a database. The cache DB 110 includes an article URI indicating a URI (Uniform Resource Identifier) of the cached Web page, an article body made up of data in a BLOB (Binary Large Object) format, and a registration date and time indicating the cached date and time. The additional information DB 111 includes a user name indicating a user who has registered the additional information, an article URI indicating a Web page to which the additional information is added, an additional range indicating the range to which the additional information is added, and a comment content for the additional range. And a registration date and time indicating the date and time when the additional information is registered. The data in the cache DB 110 and the additional information DB 111 are linked to each other by the article URI.

  FIG. 4 is a diagram showing an outline of the operation of each unit in the registration of additional information.

  In FIG. 4A, when the user U calls a web page to the browser 2 (step S1), the browser 2 acquires the corresponding web page from the web server 3 and displays it on the screen 23 (step S2). ).

  Next, when the user U selects a range to be underlined on the Web page of the screen 23 (Step S3) and activates the registration bookmarklet 22 (Step S4), the browser 2 stores the data of the Web page to be underlined. The data is sent to the server 1 (step S5), and the request processing unit 106 of the server 1 stores the web page data in the cache DB 110 (step S6).

  Next, in FIG. 4B, the page generation unit 103 of the server 1 generates a correction / confirmation page and sends it to the browser 2 (step S7), and the browser 2 displays the correction / confirmation page on the screen 23. .

  On the other hand, the user U confirms the underlined range, adds a comment if necessary (step S8), and clicks the enter button (step S9), the browser 2 sends information such as the selected range to the server 1. Send (step S10). At this time, the browser 2 also sends information such as a cookie indicating the user (logged-in user, etc.) of the browser 2 together.

  The request processing unit 106 of the server 1 identifies the user from the information such as the cookie by the user authentication unit 105 (step S11), and if the user is permitted to use, {add user name, cached page] Of the article URI, the underline addition range, the comment, and the registration date and time} are stored (step S12).

  FIG. 5 is a sequence diagram showing an example of processing for registering additional information.

  5A, when the user U requests a page from the screen 2 of the browser 2 (step S21), the screen 23 requests a page from the web server 3 (step S22), receives the page, and displays the page. This is performed (step S23).

  Next, when the user U selects a range to be underlined in the page (step S24) and activates the registration bookmarklet 22 (step S25), the registration bookmarklet 22 receives the data on the display screen of the screen 23. The data is acquired (steps S26 and S27), sent to the request processing unit 106 of the server 1 as cache data (step S28), and the request processing unit 106 stores the received data in the cache DB 110 (step S29).

  Next, the registration bookmarklet 22 calls the page to the request processing unit 106 (step S30), and the request processing unit 106 causes the page generation unit 103 to generate a correction / confirmation page for additional information registration (step S30). S31, S32), the correction / confirmation page is sent to the registration bookmarklet 22 (step S33), and the registration bookmarklet 22 displays the correction / confirmation page on the screen 23 (step S34).

  Next, in FIG. 5B, the user U corrects the range underlined on the screen 23 of the browser 2 or adds a comment by using the correction / confirmation page (step S35), and determines (submit). (Step S36), the screen 23 sends the underlined range, comments, etc. to the request processing unit 106 of the server 1 (Step S37). At this time, the browser 2 also sends information such as a cookie indicating the user (logged-in user) of the browser 2 together.

  Next, the request processing unit 106 acquires user information from the user authentication unit 105 based on information such as a cookie (steps S38 and S39), and registers additional information in the additional information DB 111 if the user is permitted to use. (Step S40), the completion of work is notified to the screen 23 of the browser 2 (Step S41).

  FIG. 6 is a diagram showing an outline of the operation of each part in browsing a page.

  In FIG. 6A, when the user U selects a desired article page from the top page displayed on the screen 23 of the browser 2 (step S51), the screen 23 sends a request to the request processing unit 106 of the server 1. (Step S52).

  The request processing unit 106 acquires the cache of the corresponding page from the cache DB 110 (step S53), acquires the JavaScript from the JavaScript generation unit 102 (step S54), and sends the page data including the JavaScript to the browser 2 as a response. (Step S55).

  Next, in FIG. 6B, when the JavaScript in the page starts execution by the JavaScript engine 21 in the browser 2 (FIG. 2), the page is specified and sent to the request processing unit 106 of the server 1 (step S56). At this time, the browser 2 also sends information such as a cookie indicating the user (logged-in user) of the browser 2 together.

  The request processing unit 106 specifies a user by the user authentication unit 105 from information such as a cookie (step S57).

  Next, when the user is permitted to browse, the request processing unit 106 acquires additional information (including comments) related to the cache page from the additional information DB 111 and passes it to the additional information transmitting unit 108 (step S58). , S59).

  The additional information transmitting unit 108 sends the additional information to the browser 2 (Step S60), and JavaScript in the page renders the additional information (Step S61).

  FIG. 7 is a sequence diagram illustrating a processing example in browsing a page.

  In FIG. 7A, when the user U selects a page on the screen 23 of the browser 2 (step S71), the screen 23 makes a request by specifying a page to the request processing unit 106 of the server 1 (step S72). ).

  The request processing unit 106 acquires the cache of the corresponding page from the cache DB 110 (Steps S73 and S74), then acquires the JavaScript from the JavaScript generation unit 102 (Steps S75 and S76), and returns it as a response to the screen 23 of the browser 2. (Step S77), the screen 23 activates JavaScript included in the response page (Step S78).

  Next, in FIG. 7B, JavaScript in the page specifies the page to the request processing unit 106 of the server 1 and makes a request (step S79), and the request processing unit 106 acquires the user information by the user authentication unit 105. At the same time (steps S80 and S81), additional information related to the target page is acquired from the additional information DB 111 (steps S82 and S83).

  Then, the request processing unit 106 sends the acquired additional information as a response to JavaScript in the page of the browser 2 (step S84), and the JavaScript in the page renders the additional information on the screen 23 (step S85).

  FIG. 8 is a diagram showing an example of rendering by JavaScript in the browser 2, and the character string on the page corresponding to the start position character string (from) “describe data” of “usr1” of the additional information obtained from the server 1 The underline L1 is rendered over the character string T12 on the page corresponding to the end position character string (to) “There was a defect” from T11, and the start position character string (from) of “usr2” “Development of processing system” The underline L2 is rendered from the character string T21 on the page corresponding to to the character string T22 on the page corresponding to the end position character string (to) “Technology”. In addition, a frame B1 indicating comments “comment” “comment 1” “comment 2” of “usr1” is rendered on the right side of the horizontal position corresponding to the underline L1, and the comment “comment” “interesting” of “usr2” is displayed. A frame B2 shown is rendered on the right side of the horizontal position corresponding to the underline L2.

  FIG. 9 is a diagram showing another example of range specification, which is an example of range specification using the data structure of the target page. That is, if an original document described in HTML (Hyper Text Markup Language) has elements “head” and “body”, and “body” further has an element “p”, elements below “p” When specifying a range of a block, it is described in a format such as “/ html / body / p /...” Using Xpath (a standard that defines a description method indicating a specific element in an XML (Extensible Markup Language) document). can do. When the “id” attribute is given to the element “p”, it can be described in a format such as “// p [id =“ xxx ”]” by using an abbreviation of Xpath together.

  FIG. 10 is a diagram showing an example of rendering by JavaScript in the browser 2 in the case of the range designation described above. In FIG. 10, the underline L1 is rendered on the block BL1 on the page corresponding to the range (/ range) “// p [id = '121-122']” of “usr1” of the underline information obtained from the server 1, and “ The underline L2 is rendered on the block BL2 on the page corresponding to the range “/ p [id = '123']” of “usr2”. Also, the frame B1 indicating the comment “comment” “comment 1” of “usr1” is rendered at the horizontal position corresponding to the underline L1, and the frame B2 indicating the comment “comment” “interesting” of the “usr2” is underlined L2. Rendering to the corresponding horizontal position.

  FIG. 11 is a diagram illustrating an example of processing and display of a list display of additional information.

  In FIG. 11A, when the user U requests the browser 2 to display a list by a predetermined button operation or the like (step S101), the browser 2 requests the list processing from the request processing unit 106 of the server 1 (step S102). ), The request processing unit 106 requests the page generation unit 103 to generate pages for list display (step S103).

  In response to this, the page generation unit 103 acquires the additional information registered by the user U from the additional information DB 111 (steps S104 and S105). Further, the page generation unit 103 requests related user information from the user relevance calculation unit 109 (step S106).

  The user relevance calculation unit 109 acquires additional information of other users for the same page as the user U from the additional information DB 111 (steps S107 and S108), and selects other users who are interested in the user U based on the user relevance. A response is made to the page generation unit 103 as an associated user (step S109). A method for calculating the user relevance level will be described later.

  Then, the page generation unit 103 generates a page to which the user U has added additional information and a page to which another user who is interested in the user U has added additional information as a list page and sends it to the request processing unit 106 ( In step S110), the request processing unit 106 sends this to the browser 2 (step S111), and the browser 2 displays on the screen 23.

  FIG. 11B shows an example of a list display. When user A performs a list display, a plurality of URIs are displayed together with comments as “page list underlined by Mr. A” V1. A list V2 of “users close to Mr. A” is displayed with a plurality of user names displayed together with URIs of unread articles (unread articles for Mr. A).

  FIG. 12 is a diagram illustrating an example of a user relevance calculation method by the user relevance calculation unit 109.

  In FIG. 12A, the degree of association between user A and user B is the range (number of characters) in which both user A and user B underlined the page where both user A and user B added additional information. , Defined by dividing by the sum of the range (number of characters) underlined by user A and the range (number of characters) underlined by user B. The user relevance calculation unit 109 in FIG. 2 refers to the cache DB 110 and the additional information DB 111 and performs the above calculation with other users for the current user, thereby marking a user ( Who are expected to have similar interests) and can introduce highly relevant users.

  FIG. 12C shows an example in which the degree of association between the user A and the user B is calculated when the additional information DB 111 is in the state shown in FIG. Here, both user A and user B register additional information in article URIs “http://foo.com/123/456” and “http://example.jp/55555”, and user A and user B The range underlined by both parties does not exist in “http://foo.com/123/456”, 1150-1222 in “http://example.jp/55555”, and user A “http: //foo.com/123/456 "underlined ranges 1033-1086, user A underlined" http://example.jp/55555 "1100-1222, user B" http: //foo.com/123/456 ”is underlined 1772 to 1851, and user B is“ http://example.jp/55555 ”underlined 1150 to 1250. Calculated as 20.3%. In addition, since user A and user C do not register additional information on the same page, the degree of association is calculated as 0%.

  FIG. 13 is a diagram showing another configuration example for browsing a page. That is, in the above-described embodiment, the page data cached in the cache DB 110 (FIG. 2) of the server 1 is sent to the browser 2 and the underline is rendered, but in FIG. Acquire and display the page, and underline information is acquired from the additional information DB 111 of the server 1 in a format such as RSS (RDF (Resource Description Framework) Site Summary, Rich Site Summary, Really Simple Syndication), etc. An underline or the like is added to the page being displayed on the screen 23 by the customization unit 24. The page customization unit 24 can be realized by a browser extension function such as “Greasemonkey”.

  FIG. 14 is a diagram illustrating an example of range designation for a moving image. In other words, in the above-described embodiment, an example in which a character string in a Web page is targeted is shown, but in FIG. 14, a desired portion along the time axis of a moving image can be designated. In FIG. 14, a moving image is displayed on the moving image screen 201, and the start / stop of the reproduction can be controlled by the play / stop button 202. Can be specified. In addition, the current reproduction position can be confirmed by the reproduction time indicator 204 and the range designated by the range designation indicator 205 can be confirmed. It is also possible to change the designated range by dragging the end of the range display portion 206 of the range designation indicator 205 with a mouse or the like.

  On the other hand, in the above-described embodiment, the application has been shown mainly for marking and sharing a portion where a plurality of users have shown interest. However, the same system is applied to a system in which a draft is edited by a plurality of people. Can be applied. In this case, the additional information DB 111 (FIG. 2) has the edited content for the specified range in the form of a difference, and the edited content of the specified range is accepted at the time of registration, and the underlined range at the time of rendering is edited. Replace with content.

Also, in this case, there is a problem with handling multiple edits within the same range.
(1) Priority is given to the first one (2) Priority is given to the last one (3) It is possible to cope by detecting at the time of registration and further editing the previously edited one.

<Second Embodiment>
FIG. 15 is a diagram illustrating a configuration example of a system according to the second embodiment of the present invention. In the first embodiment described above, the additional information is transmitted from the server 1 to the browser 2 and the additional information is rendered on the page on the browser 2 side. In the second embodiment, the additional information is displayed on the server 1 side. Is generated and transmitted to the browser 2 for display.

  In FIG. 15, the system includes a server 1 that manages additional information, a browser 2 that is operated by a user U, and an arbitrary external Web server 3 that is a browsing target. The server 1, the browser 2, and the web server 3 are connected via a network such as the Internet.

  The server 1 includes a standard Web server component 101 and a page generation unit 103 that generates a registration detail page and the like when the user U registers additional information.

  In addition, the server 1 manages the information of the user who uses the function of the server 1 and authenticates the user, the request processing unit 106 that processes a request from the browser 2, and the page data for which the display request has been made. Information adding unit 107 for generating new page data by adding additional information corresponding to the page, page transmitting unit 108+ for transmitting the page data to which the additional information has been added to browser 2, and calculating the user relevance to the current user And a user relevance calculation unit 109 for discovering other users who have marked similar parts.

  The server 1 also includes a cache DB 110 that holds a Web page for which additional information is registered, and an additional information DB 111 that holds additional information. The data held in the cache DB 110 and the additional information DB 111 is the same as that shown in FIG.

  The browser 2 includes a registration bookmarklet 22 for registering additional information and a screen 23 for displaying a Web page or the like.

  In the operation, the additional information registration process is the same as that shown in FIGS.

  FIG. 16 is a diagram showing an outline of the operation of each part in browsing a page.

  In FIG. 16A, when the user U selects a page of a desired article from the top page displayed on the screen 23 of the browser 2 (step S201), the screen 23 identifies the page to the request processing unit 106 of the server 1. A request is sent (step S202). At this time, the browser 2 also sends information such as a cookie indicating the user (logged-in user, etc.) of the browser 2 together.

  Next, in FIG. 16B, the request processing unit 106 identifies the user from the information such as the cookie by the user authentication unit 105 (step S203), and if the browsing is permitted, the request processing unit 106 sends a page to the information addition unit 107. (Page with additional information) is requested (step S204).

  In response to this, the information adding unit 107 acquires the additional information related to the page from the additional information DB 111 (step S205), acquires the cache of the page from the cache DB 110 (step S206), and obtains page data incorporating the additional information. It is generated and delivered to the page transmission unit 108+ (step S207).

  The page transmission unit 108+ transmits the received page data as a response to the browser 2 (step S208), and the browser 2 displays a page including additional information on the screen 23.

  FIG. 17 is a sequence diagram illustrating a processing example in browsing a page.

  In FIG. 17, the browser 2 transmits a request specifying the page to the request processing unit 106 of the server 1 in response to the page selection by the user U (step S211). At this time, the browser 2 also sends information such as a cookie indicating the user (logged-in user, etc.) of the browser 2 together.

  The request processing unit 106 acquires user information from the user authentication unit 105 based on information such as a cookie (steps S212 and S213), and requests a page from the information addition unit 107 if browsing is permitted. (Step S214).

  The information adding unit 107 acquires additional information relating to the page from the additional information DB 111 (steps S215 and S216), acquires a page cache from the cache DB 110 (steps S217 and S218), and combines the additional information and the contents of the cache. Then, page data incorporating additional information is generated.

  The information adding unit 107 then passes the page data incorporating the additional information to the page transmitting unit 108+ (step S219), and the page transmitting unit 108+ transmits the received page data as a response to the browser 2 (step S220). In response to this, the browser 2 displays a page including additional information on the screen 23.

  FIG. 18 is a diagram showing an example of HTML data of a page to which additional information is added. A description D2 of additional information is inserted in the body element together with a description D1 of the same text as the original page, and the system further adds the additional information. The state where the description D3 indicating that it has been added is shown.

<Third Embodiment>
FIG. 19 is a diagram showing a configuration example of a system according to the third embodiment of the present invention. In the first and second embodiments described above, additional information is held and managed in a single server 1. In the third embodiment, a plurality of servers 1 (# 1, # 2,...) Are used. Thus, additional information is held and managed.

  In FIG. 19, the system includes a plurality of servers 1 for managing additional information, a browser 2 operated by a user U, and an arbitrary external Web server 3 to be browsed. The server 1, the browser 2, and the web server 3 are connected via a network such as the Internet.

  Each server 1 includes a standard Web server component 101, a user authentication unit 105 that manages and authenticates user information that uses the functions of the server 1, and a request processing unit that processes requests from the browser 2. 106, an additional information transmitting unit 108 that transmits additional information to the browser 2 in the form of RSS or JSON (JavaScript Object Notation), and an additional information DB 111 that holds additional information. The data held in the additional information DB 111 is the same as that shown in FIG.

  The browser 2 includes an additional information plug-in 25 that registers additional information in the server 1, acquires additional information from the server 1, and renders additional information, and a screen 23 that displays a Web page or the like. . The additional information plug-in 25 includes an additional information searching unit 251 that searches for and acquires additional information from a plurality of servers 1, an input form providing unit 252 that provides an input form for registering additional information, and input of additional information. An additional information sending unit 253 that sometimes sends additional information to the server 1, a renderer 254 that renders the additional information acquired from the server 1 on a page, and a server list 255 that holds the address (URL) of the server 1 to be accessed. I have.

  FIG. 20 is a diagram showing an example of processing at the time of page access, (a) shows an outline of the operation, and (b) shows a sequence diagram of processing between the functional units.

  20A and 20B, when the user U requests a page from the browser 2 (step S301), the browser 2 requests the web server 3 to acquire the page data (steps S302 and S303). .

  Next, the browser 2 specifies the target page from the additional information search unit 251 of the additional information plug-in 25 and requests additional information (step S304), and the additional information search unit 251 searches for the address of the server 1 from the server list 255. A list is acquired (steps S305 and S306).

  Then, the additional information search unit 251 specifies a target page for each server 1 in the acquired list and requests additional information (step S307), and each server 1 passes through the additional information transmission unit 108. Applicable additional information (if any) is acquired from the additional information DB 111 and transmitted to the additional information search unit 251 of the browser 2 (steps S308 to S312). If the corresponding additional information does not exist, the additional information is not acquired and transmitted. Although omitted in the sequence diagram, each server 1 performs user authentication by the user authentication unit 105 based on a cookie included in the request prior to acquisition of the additional information, and is a user who is permitted to browse. Acquire and send additional information.

  The additional information search unit 251 delivers the acquired additional information to the browser 2 (step S313), and the browser 2 renders page data and additional information on the screen 23 by the renderer 254 (steps S314 and S315).

  Note that page data and additional information are rendered together after acquisition of additional information, but only page data is rendered immediately after the page data is acquired from the Web server 3, and then added when additional information is acquired. Information may be superimposed and rendered.

  FIG. 21 is a diagram showing an example of processing when additional information is input. FIG. 21A shows an outline of the operation, and FIG. 21B shows a sequence diagram of processing between the functional units.

  21 (a) and 21 (b), the browser 2 displays the page of the Web server 3, and then the input form providing unit 252 of the additional information plug-in 25 displays the input form on the screen 23 automatically or according to the operation of the user U. Is displayed by overlay or pop-up (step S321).

  Then, when the user U inputs a range for adding additional information to the input form and if necessary, a comment is input (step S322), the input form delivers the additional information (range, comment) to the additional information sending unit 253 (step S322). S323).

  In response, the additional information sending unit 253 acquires a server list from the server list 255 (steps S324 and S325), and requests the server 1 in the list to register additional information (step S326). The server 1 registers the received additional information in the additional information DB 111 (steps S327 and S328), and when the registration is completed normally, notifies the additional information sending unit 253 to that effect (step S329). Although the additional information search probability can be increased by registering additional information in each server 1 in the list obtained from the server list 255, on the other hand, there is a waste due to the presence of duplicate additional information. Therefore, the registration of additional information may be limited to a predetermined server 1 in the list. For example, registration of additional information is attempted from the highest server 1 in the list. If registration is not successful, registration is attempted with the next server 1 and processing is terminated when registration is successful. can do.

<Fourth Embodiment>
FIG. 22 is a diagram showing a configuration example of a system according to the fourth embodiment of the present invention. In the fourth embodiment, the present invention is applied to a blog (diary-like site), and a trackback mechanism (for example, see http://lowlife.jp/yasusii/stories/8.html for details). ) Is used to register additional information in the blog itself, and the additional information is also displayed when browsing the blog.

  In FIG. 22, the system includes a normal blog 4, a blog 5 that has been expanded in function of the present invention, and a browser 2 operated by a user U. The blog 4, the blog 5, and the browser 2 are connected via a network such as the Internet. Here, it is assumed that a trackback is transmitted from the blog 4 to the blog 5 and the blog 5 is viewed from the browser 2.

  The blog 4 includes a component 41 of a standard blog processing system. The component 41 includes a trackback transmission unit 42 that transmits trackbacks to other blogs, and a text DB 43 that holds the content of the article of the blog. And are provided.

  The blog 5 includes a standard blog processing system component 51, a trackback processing unit 54 that receives a trackback and performs processing such as registration of additional information, and an additional information DB 55 that holds additional information (the contents of the retained data are shown in FIG. 3) and an information adding unit 56 for adding additional information to the blog contents when browsing the blog. The component 51 of the standard blog processing system is provided with a body text DB 52 that holds the article content of the blog and a track back DB 53 that holds information about the received track back.

  In this embodiment, a unique tag set for additional information is defined in advance, and the additional information is embedded in advance in the trackback article of the blog 4 on the trackback side using the tag. In the blog 5 that has received the trackback, the trackback article of the blog 4 is referred to, and additional information is acquired from a tag unique to the additional information and registered.

  FIG. 23A is a sequence diagram illustrating a processing example at the time of trackback transmission.

  In FIG. 23A, when a trackback is transmitted from the trackback transmission unit 42 to the blog 5 according to the operation of the operator of the blog 4 (step S401), the trackback is accepted by the trackback processing unit 54 of the blog 5. . FIG. 23B shows an example of the contents of the articles of the blogs 4 and 5 at the time of the trackback, and is added to the trackback article of the blog 4 on the side performing the trackback with respect to the trackback article (original page) of the blog 5. Information-specific tags "<socialunderline: range>", "</ socialunderline: range>", "<socialunderline: comment>", and "</ socialunderline: comment>" indicate that the underlined range and comments are described in advance. To do. In other words, the content of the trackback article “If you trackback this blog article in a certain format, you can directly underline or comment on this site. Please try it. ”In the trackback article“ <socialunderline: range> Directly underline this site or add a comment </ socialunderline: range> ”has an underlined range of“ Underline this site directly ” Or comment on it. "<Socialunderline: comment> Try commenting on the trial. </ Socialunderline: comment>" means that the comment is "Try commenting on the trial." Show.

  Returning to FIG. 23A, the trackback processing unit 54 that has received the trackback stores the trackback information in the trackback DB 53 and performs trackback processing for displaying a trackback list or the like (steps S402 and S403).

  Next, the trackback processing unit 54 accesses the blog 4 that is the trackback source, and acquires the text of the trackback article from the text DB 43 (steps S404 and S405).

  When the acquired trackback article contains a tag specific to the additional information, the trackback processing unit 54 extracts the additional information and registers it in the additional information DB 55 (steps S406 and S407). When restricting the users who can register additional information, the user identification can be performed from the URL of the blog 4 that is the trackback source, and whether or not the registration process is performed can be branched.

  FIG. 24A is a sequence diagram illustrating a processing example when browsing a blog.

  In FIG. 24A, when a page display request is transmitted from the browser 2 to the blog 5 in accordance with the operation of the user U (step S411), the information adding unit 56 of the blog 5 performs the body text DB 52 as page rendering processing. The contents of the body from the track back (steps S412 and S413), the trackback information from the trackback DB 53 (steps S414 and S415), and the page rendering (step S416) are performed.

  Next, the information adding unit 56 acquires additional information from the additional information DB 55 (steps S417 and S418), and renders the additional information on the page (step S419).

  FIG. 24B shows a screen display example of the article of the blog 5 in the browser 2, and an underline 502 is drawn in the part of the article body 501 that “directly underline this site or attach a comment”. In addition, a comment 504 for the underlined portion is displayed. A column 503 is an area where trackback information is displayed.

<Summary>
The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the example of a screen concerning one Embodiment of this invention. It is a figure which shows the structural example of the system concerning the 1st Embodiment of this invention. It is a figure which shows the example of a database. It is a figure which shows the operation | movement outline | summary of each part in registration of additional information. It is a sequence diagram which shows the process example in registration of additional information. It is a figure which shows the operation | movement outline | summary of each part in browsing of a page. It is a sequence diagram which shows the process example in browsing of a page. It is a figure which shows the example of rendering by JavaScript in a browser. It is a figure which shows the other example of range specification. It is a figure which shows the example of rendering by JavaScript in a browser. It is a figure which shows the example of the process of a list display of additional information, and a display. It is a figure which shows the example of the calculation method of a user relevance degree. It is a figure which shows the other structural example for the browsing of a page. It is a figure which shows the example of the range specification which made the moving image object. It is a figure which shows the structural example of the system concerning the 2nd Embodiment of this invention. It is a figure which shows the operation | movement outline | summary of each part in browsing of a page. It is a sequence diagram which shows the process example in browsing of a page. It is a figure which shows the example of the HTML data of the page to which additional information was added. It is a figure which shows the structural example of the system concerning the 3rd Embodiment of this invention. It is a figure which shows the process example at the time of page access. It is a figure which shows the process example at the time of additional information input. It is a figure which shows the structural example of the system concerning the 4th Embodiment of this invention. It is a figure which shows the process example at the time of trackback transmission. It is a figure which shows the process example at the time of blog browsing.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Server 101 Standard component 102 JavaScript production | generation part 103 Page production | generation part 105 User authentication part 106 Request processing part 107 Information addition part 108 Additional information transmission part 108+ Page transmission part 109 User relevance degree calculation part 110 Cache DB
111 Additional information DB
2 Browser 21 JavaScript Script 22 Registration Bookmarklet 23 Screen 24 Page Customization Unit 25 Additional Information Plug-in 251 Additional Information Search Unit 252 Input Form Providing Unit 253 Additional Information Sending Unit 254 Renderer 255 Server List 3 Web Server 4 Blog 41 Standard Configuration Element 42 Trackback transmitter 43 Text DB
5 Blogs 51 Standard components 52 Full text DB
53 Trackback DB
54 Trackback processing section 55 Additional information DB
56 Information adding part U User

Claims (14)

A management method in which a plurality of users attach additional information including highlighting and necessary comments to an object in an arbitrary page, and the plurality of users share the additional information,
A reception process for accepting additional information including a range specification for an object in the page;
A storing step of storing the received additional information in association with the target page;
A page additional information sharing management method, comprising: a provision step of acquiring additional information corresponding to a page to be browsed and providing it to a request source when display of the additional information is requested. In the page additional information sharing management method according to claim 1,
Additional page information sharing management characterized in that it includes a step of providing the browser side with a script for performing additional information acquisition request and rendering of the acquired additional information in the page data to be viewed on the browser side that performs page browsing Method. In the page additional information sharing management method according to claim 1 or 2,
A page additional information sharing management method comprising the step of combining the additional information with the page data to be browsed and providing the page information to the request source. In the page additional information sharing management method according to any one of claims 1 to 3,
Storing the page for which the additional information is to be set in a cache;
And a page additional information sharing management method comprising: providing a cache of a corresponding page when browsing of the page is requested. In the page additional information sharing management method according to claim 1,
In the page receiving information sharing management method, the receiving step acquires additional information from a trackback article on the trackback side based on a predetermined tag. In the page additional information sharing management method according to any one of claims 1 to 5,
A page additional information sharing management method comprising a step of discovering and presenting a user strongly related to the current user based on the stored additional information. In the page additional information sharing management method according to any one of claims 1 to 6,
The page additional information sharing management method, wherein the object is a character string, and the range designation is performed by designating a character string specifying a head position and a character string specifying a terminal position. In the page additional information sharing management method according to any one of claims 1 to 6,
The page additional information sharing management method, wherein the object is a character string, and the range specification is performed by specifying an element of a document described in a markup language. A management apparatus for a plurality of users to attach additional information including highlighting and necessary comments to an object in an arbitrary page, and for the plurality of users to share the additional information,
Accepting means for accepting additional information settings including range specification for objects in the page;
Storage means for storing the received additional information in association with the target page;
A page additional information sharing management apparatus, comprising: a providing unit that acquires additional information corresponding to a page to be browsed and provides it to a request source when display of the additional information is requested. In the page additional information sharing management apparatus according to claim 9,
Additional page information sharing management, characterized in that it includes a means for providing the browser side with a script for rendering the additional information to be retrieved and included in the page data to be browsed. apparatus. In the page additional information sharing management device according to any one of claims 9 and 10,
A page additional information sharing management device comprising means for combining the additional information with the page data to be browsed and providing it to the request source. The page additional information sharing management apparatus according to any one of claims 9 to 11,
Means for storing in a cache the page for which the additional information is to be set;
A page additional information sharing management device comprising: means for providing a cache of a corresponding page when browsing of the page is requested. In the page additional information sharing management apparatus according to claim 9,
The page additional information sharing management apparatus, wherein the receiving means acquires additional information from a trackback article on the trackback side based on a predetermined tag. In the page additional information sharing management device according to any one of claims 9 to 13,
A page additional information sharing management apparatus comprising means for discovering and presenting a user strongly related to the current user based on the stored additional information.

Images