JP2006331348A - COLLECTING METHOD AND DEVICE FOR TRACKBACK OR COMMENT / TRACKBACK, PROGRAM, AND STORAGE MEDIUM CONTAINING PROGRAM - Google Patents

Abstract

PROBLEM TO BE SOLVED: To collect trackback source comments and trackbacks by tracing trackbacks.
SOLUTION: The present invention acquires the URL of a Blog article, comments and trackback anchors from a Blog article, acquires each comment sentence from a comment page, acquires each trackback sentence from a trackback page, and stores it in a DB Then, a trackback source article indicated by each trackback sentence described in the DB is acquired, a comment sentence described in the DB, and a comment page and a trackback page are newly generated based on the trackback sentence. The URL given by the comment and trackback anchor assigned to the article is changed to the URL to the generated comment page and trackback page.
[Selection] Figure 1

Description

  The present invention relates to a trackback source comment / trackback aggregating method and apparatus, a program, and a storage medium storing the program. The present invention traces a web page linked by a hyperlink and generates a web page that aggregates information of each link destination. In particular, the present invention relates to a method for aggregating link destination information, and particularly relates to a method and apparatus for aggregating comments and trackbacks of trackback sources in Blog (blog) articles, a program, and a storage medium storing the program.

  The number of sites that use “tools that can easily and quickly update websites” called blogs has increased since around 2001, and with the provision of blog services by major portal sites, blogs have exploded in popularity. ing.

  Blog is defined as a diary-like website that is updated daily by individual management. In particular, articles (Blog articles) that link to websites on the Internet and add their own reviews are written in chronological order. Represents a Web site placed in The Blog is described using HTML (Hyper Text Markup Language) as shown in FIG.

  Blog has a unique feature, “Comment” that allows viewers to write comments on each Blog article. At this time, as shown in FIG. 19B, a title, a contributor name, a comment text, etc. can be entered as a comment.

  Also, when a link is made from one blog article to another blog article, it has a “trackback” function that notifies the linked site that the link has been made. At this time, the URL and title of the blog article that is the trackback source, the summary of the article, and the like are transmitted to the linked site (trackbacked site). Then, as shown in FIG. 19C, the trackback site automatically generates a “trackback to this article” list based on this information.

  The trackback relationship between blog articles will be described with reference to FIG. For example, the trackback source of the blog article A_E1 is the blog article B_E1 (A_T1 (1) in FIG. 19C) of the site B and the blog article C_E1 of the site C (A_T1 (2) in FIG. 19C). In A, a trackback page A_T1 is automatically generated.

  Here, in general, the relevance between tracked blog articles is high, and if you are interested in a blog article, follow the trackback for that article to get information related to that blog article. Browsing often occurs. At this time, if “comment” or “trackback” exists in the article of the trackback source, the comment or trackback is browsed. Furthermore, there are occasions when the trackback of the article of the trackback source is further traced and new Blog articles are browsed hierarchically.

  For example, with reference to a Blog article A_E1 shown in FIG. 20, browsing is performed as a Blog article B_E1, a Blog article D_E1, and a Blog article E_E1.

Here, as a technique for efficiently browsing a plurality of Web pages connected by hyperlinks (trackback is also a type of hyperlink), a plurality of Web pages can be browsed continuously with a simple operation. Has proposed a method of displaying hop-up hierarchically (see, for example, Patent Document 1).
JP-A-2005-32041

  Here, when trying to get the related information of a blog article, when accessing the “comment” or “trackback” of that article, not only the comments and trackbacks given to that article, but also the article of the trackback source of that article If the comments and trackbacks given, and the comments and trackbacks assigned to the trackback source article of the trackback source article are also displayed, the amount of information that can be obtained at one time increases, and the trackback source This will save you the trouble of moving to the article and enable efficient browsing.

  Such aggregating comments and trackbacks assigned to trackback source articles has not been realized so far.

  Furthermore, at the time of aggregating comments and trackbacks, the trackback is duplicated (article D_E1 is duplicated as the trackback source of articles B_E1 and C_E1 in FIG. 20) and re-referenced (article B_E1 is re-referenced as the trackback source of article D_E1 in FIG. 20) If it is displayed in an organized manner, the user himself / herself does not need to manage the read / unread status of each blog article, and it is possible to efficiently obtain related information continuing from a certain article.

  The present invention has been made in view of the above points. By tracking the trackback and aggregating the comments and trackbacks of the trackback source, it is possible to efficiently obtain related information from a certain blog article. It is an object of the present invention to provide an aggregation method and apparatus, a program, and a storage medium storing the program.

  FIG. 1 is a diagram for explaining the principle of the present invention.

The present invention (Claim 1) is a method of aggregating comments / trackbacks of trackback sources, which generates a page in which comments and trackbacks of trackback sources are aggregated by tracing trackbacks attached to blog articles.
Using the Blog analysis rule that describes the processing contents to be executed and stored in the storage means, the URL of the Blog article, the comment attached to the Blog article and the anchor of the track back are acquired from the Blog article, and the comment / trackback Blog article analysis step (step 1) to be stored in the storage database;
Using the blog analysis rule, a comment acquisition step (step 2) of acquiring each comment sentence from the page (comment page) indicated by the comment anchor and storing it in the comment / trackback storage database;
A trackback acquisition step (step 3) for acquiring each trackback sentence from the page (trackback page) indicated by the trackback anchor using the Blog analysis rule and storing it in the comment / trackback storage database;
A trackback source acquisition step (step 4) for acquiring a trackback source article indicated by each trackback statement described in the comment / trackback storage database;
A comment page described in the comment / trackback storage database, a comment page based on the trackback statement, and a comment page / trackback page generation step (step 5) for newly generating a trackback page;
The comment given to the blog article, the URL indicated by the trackback anchor, the comment page generated in the comment page / trackback page generation step, and the comment / trackback anchor change step (step 6) for changing the URL to the trackback page. Do.

Further, the present invention (Claim 2) is provided in a comment / trackback storage database.
For each blog article, the hop count indicating how many steps the blog article is from the first blog article, the comment sentence and trackback sentence given to the blog article, the URL of the trackback source article indicated by each trackback sentence, and each trackback source Manage article acquisition status.

  FIG. 2 is a principle configuration diagram of the present invention.

The present invention (Claim 3) is a trackback source comment / trackback aggregating apparatus that traces a trackback attached to a blog article and generates a trackback source comment or a trackback page.
Blog article analysis means 51 for obtaining the URL of the Blog article, the comment given to the Blog article and the anchor of the track back from the Blog article,
Comment acquisition means 54 for acquiring each comment sentence from the page (comment page) indicated by the anchor of the comment;
Trackback acquisition means 55 for acquiring each trackback sentence from the page (trackback page) indicated by the trackback anchor;
The blog article analysis means 51, the comment acquisition means 54, and the trackback acquisition means 55 describe the processing contents to be executed, and the Blog analysis rules 52 stored in the storage means;
A comment / trackback storage database 53 for storing information acquired by the blog article analysis means 51, the comment acquisition means 54, and the trackback acquisition means 55;
Trackback source acquisition means 56 for acquiring the trackback source article indicated by each trackback sentence described in the comment / trackback storage database 53;
A comment page described in the comment / trackback storage database 53, a comment page based on the trackback statement, and a comment page / trackback page generation means 57 for newly generating a trackback page;
Comments / trackback anchor changing means 58 for changing a comment given to a blog article and a URL indicated by a trackback anchor to a comment page generated by the comment page / trackback page generating means 57 and a URL to the trackback page.

Further, the present invention (Claim 4) is provided in a comment / trackback storage database.
For each blog article, the hop count indicating how many steps the blog article is from the first blog article, the comment sentence and trackback sentence given to the blog article, the URL of the trackback source article indicated by each trackback sentence, and each trackback source Manage article acquisition status.

  The present invention (Claim 5) is a trackback source comment / trackback aggregation program that causes a computer to execute the steps of the trackback source comment / trackback aggregation method according to claims 1 and 2.

  According to the present invention (Claim 6), a program for causing a computer to execute the steps of the method for aggregating comments / trackbacks according to claims 1 to 2 is stored. A storage medium storing a program.

  As described above, according to the present invention, the amount of information obtained as a comment or trackback of a certain Blog article increases, and the user can save time and effort to move to the trackback source article, thereby enabling efficient information acquisition. .

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 3 shows a configuration of a trackback source comment / trackback aggregation system according to an embodiment of the present invention.

  The system shown in FIG. 1 includes an extended blog server 3 provided with a trackback source comment / trackback aggregation device 2, which is the main part of the present invention, the other blog server 4, and a viewer's personal computer (PC). ) 5 are connected to each other.

  The extended blog server 3 and the blog server 4 have a basic function for creating a blog and publishing on the Internet, and the viewer PC 5 has a Web browser for browsing the Internet.

  FIG. 4 shows an example of a display screen presented to the user when browsing the blog site on the extended blog server in one embodiment of the present invention. In the display screen shown in the figure, an aggregation operation interface 41 for operating the comment / trackback aggregation device of the trackback source is newly displayed. Details of the aggregation operation interface 41 will be described later.

  FIG. 5 shows the configuration of a trackback source comment / trackback aggregation device according to an embodiment of the present invention.

  The trackback source comment / trackback aggregation device 2 includes a Blog article analysis unit 51, a Blog analysis rule 52, a comment / trackback storage database (DB) 53, a comment acquisition unit 54, a trackback acquisition unit 55, a trackback source acquisition unit 56, and a comment. The page / trackback page generating unit 57 and the comment / trackback anchor changing unit 58 are configured. Of these, the Blog analysis rule 52 is assumed to be stored in storage means such as a memory.

  The operation in the above configuration will be described below.

  FIG. 6 is a flowchart of the operation in one embodiment of the present invention.

  First, the user inputs in the “hop count” column of the aggregation operation interface shown in FIG. I press the button.

  Here, when “2” is set as the number of hops, “comment” and “trackback” of the second blog article (article D_E1 in FIG. 20) from the currently viewed blog article (article A_E1 in FIG. 20). ”(Comment D_C1, track back D_T1 in FIG. 20).

  When the above operation from the user occurs, the Blog article analysis unit 51 acquires the “hop count” designated by the user and initializes the “hop count” to 0 (step 51).

  The hop count is a variable for managing the number of stages of the Blog article to be processed in the subsequent processing. The number of hops and the hop count are not shown in FIG. 5, but are managed by the internal memory of the comment / trackback aggregation device 2 of the trackback source.

  Further, the blog article analysis unit 51 refers to the blog analysis rule 52, and the URL of the blog article currently being browsed by the user (article A_E1 in FIG. 19), as well as “comment” and “ An “trackback” anchor is acquired (step 52).

Here, in the Blog analysis rule 52, as a method of acquiring the URL of the Blog article, for example, the href attribute (<Ahref = ”***”><SPAN class = etTitle> title </ SPAN> indicated by the anchor of the title is used. *** part of </A>) and obtaining the href attribute of the anchor described as “ fixed link ” or “ PermanentLink ”.

In addition, as a method of acquiring the anchors of “comment” and “trackback”, for example, “ comment (2), comment (2) , comments (2) , comment a word (2) ”, and “ trackback (2 ) , TrackBack (2) , Trackback (2) ”, and the like are described to acquire an anchor. As a result, only comments and trackback anchors are extracted from the anchors included in the Blog article.

  Then, the URL of the acquired blog article and the current hop count (here, 0) are recorded in the comment / trackback storage DB 53, and a column for describing the comment or trackback assigned to the blog article is newly provided (step) 53).

  Here, as shown in FIG. 7, in the comment / trackback storage DB 53, for each Blog article, the hop count, the comment sentence and the trackback sentence described later, the URL of the trackback original article indicated by each trackback sentence, and the acquisition of each trackback original article Manage the situation.

  Next, the comment acquisition unit 54 acquires the comment page (A_C1 in FIG. 19) indicated by the “comment” anchor acquired in step 52. Then, referring to the Blog analysis rule 52, the comment text (A_C1 (1), A_C1 (2) in FIG. 19) is extracted from the acquired comment page (step 54).

  Here, the blog analysis rule 52 describes the description format of the comment text on the comment page as shown in FIG. 8, and actually, the information described in the format, for example, a comment tag (<!- -Comment->, <! /-Comment->), and extract the comment text based on the class attribute (class = ”cmTitle”, etc.) of the SPAN tag and TD tag.

  Then, as shown in FIG. 7, the extracted comment text is entered in the field generated in step 53 of the comment / trackback storage DB 53 (step 55).

  Next, the trackback acquisition unit 55 acquires the trackback page (A_T1 in FIG. 19) indicated by the “trackback” anchor acquired in step 52. Then, referring to the Blog analysis rule 52, a trackback sentence (A_T1 (1), A_T1 (2) in FIG. 19) is extracted from the acquired trackback page (step 56).

  Here, the blog analysis rule 52 describes the description format of the trackback sentence in the trackback page as shown in FIG. 9. Actually, information described in the format, for example, a comment tag (<!- -Trackback->, <! /-Trackbak->), and extract the trackback sentence using the class attribute (class = ”tbETitle” etc.) of the SPAN tag and TD tag.

  Then, the extracted trackback text and the URL of the trackback source article (B_E1, C_E1 in FIG. 19) indicated by each trackback text are entered in the field generated in step 53 of the comment / trackback storage DB 53 (step 57).

  Here, the URL of the trackback source article describes, for example, the href attribute of the anchor in which the title of the trackback source article is described as shown in FIG.

  Next, the trackback source acquisition unit 56 reads the information of the trackback source article (in this case, B_E1) from the comment / trackback storage DB 53 (step 58), and the hop count described in the column of the trackback source article (here, 0) and the number of hops acquired in step 51 (here, 2) are compared (step 59).

  If the number of hops> the hop count (Yes in step 59), the URL of the trackback source article (here, B_E1) and the blog article being browsed (here, A_E1) described in the comment / trackback storage DB 53 ) And the URLs of other trackback source articles described in the comment / trackback storage DB 53 that have a non-blank trackback source acquisition status (not applicable here) (step 60). The contents described in the trackback source acquisition status will be described later.

  If the same URL is not found as a result of the comparison (OK in step 50), the process for acquiring the trackback source article indicated by the URL is started (step 61). At this time, “◯ (acquiring)” is entered in the acquisition status column of the trackback original article in the comment / trackback storage DB 53.

  On the other hand, if the same URL is found as a result of the comparison in step 60 (No in step 60), the trackback source article indicated by the URL has already been acquired. (Completed) "is entered.

  Thereafter, the comment / trackback storage DB 53 is referred to, and information on new trackback source articles is read from the comment / trackback storage DB 53 until there are no trackback source articles whose trackback source acquisition status is blank (step 58). The process from step 59 to step 61 is repeated.

  Here, the information of the trackback source article C_E1 is read from the comment / trackback storage DB 53, and the processing of step 59 to step 61 is repeated.

  At this time, in step 60, the URL of C_E1, the URL of A_E1, and the URL of B_E1 are compared.

  Thereafter, when reading of all the trackback original articles described in the comment / trackback storage DB 53 is completed (Yes in step 62), the hop count is incremented by 1 (here, 1) (step 63), and the trackback original article ( Here, the process proceeds to acquisition processing of the articles B_E1 and C_E1).

  If the number of hops is equal to or less than the hop count as a result of the comparison in step 59 (No in step 59), the process proceeds to a comment page / trackback page generation process. Details of the processing will be described later.

  Hereinafter, the process for acquiring the trackback original article will be described.

[First trackback source article acquisition process]
Hereinafter, the processing at the time of track back original article acquisition will be described using the flowchart of FIG.

  First, when the trackback source acquisition unit 56 receives the transaction completion of the trackback source article (in this case, the article B_E1 / article C_E1 in FIG. 20), the acquisition status column of the trackback source article in the comment / trackback storage DB 53 is set to “black circle”. (Acquired) "(step 64).

  Then, the blog article analysis unit 51 refers to the blog analysis rule 52 to acquire the URL of the acquired blog article and the “comment” and “trackback” anchors assigned to the blog article (step 52).

  Thereafter, using the acquired blog article (the blog article of the trackback source), the processing of the above-described step 53 to step 63 is executed.

  At this time, in step 53, the URL of the acquired blog article (B_E1 / C_E1 in FIG. 20) and the current hop count (here, 1) are recorded in the comment / trackback storage DB 53 and given to the blog article. A new field describing comments and trackbacks will be provided.

  In step 54, a comment sentence is extracted from the comment page (B_C1 / C_C1 in FIG. 20) attached to the acquired blog article (B_E1 / C_E1 in FIG. 20), and the comment sentence extracted in step 55 is commented / tracked back. Fill in the storage DB 53.

  Further, in step 56, a trackback sentence is extracted from the trackback page (B_T1 / C_T1 in FIG. 20) attached to the acquired blog article (B_E1 / C_E1 in FIG. 20). In step 57, the extracted trackback sentence, The URL of the trackback source article (D_E1 in FIG. 20) indicated by each trackback sentence is entered in the comment / trackback storage DB 53.

  FIG. 11 shows the comment / trackback storage DB 53.

  Thereafter, when the information of the trackback source article D_E1 is processed for the first time as the trackback source of the article B_E1 in step 58, the URL of D_E1 is compared with the URLs of A_E1, B_E1, and C_E1 in step 60. As a result, the same URL is not found (OK in step 60), and the acquisition process of the article D_E1 is started in step 61. At this time, as shown in FIG. 11, “O (acquisition)” is entered in the trackback source acquisition status column of the trackback source article D_E1 described in the Blog article B_E1 column of the comment / trackback storage DB 53.

  On the other hand, when the information of the trackback source article D_E1 is processed as the trackback source of the article C_E1 after the above process, in step 60, the URL of D_E1 is compared with the URLs of A_E1, B_E1, C_E1, and D_E1. As a result, the same URL is found (No in Step 60). As shown in FIG. 11, the trackback source acquisition status column of the trackback source article D_E1 described in the Blog article C_E1 column of the comment / trackback storage DB 53 is “×”. (Completed) "is entered.

  Thereafter, when reading of all the trackback source articles described in the comment / trackback storage DB 53 is completed, the hop count is incremented by 1 (here, 2) (step 63), and the trackback source article (here, the article D_E1) )

[Get second trackback source article]
When the trackback source acquisition unit 56 receives the acquisition completion of the trackback source article (in this case, the article D_E1), the acquisition status column of the trackback destination article in the comment / trackback storage DB 53 is changed to “black circle (acquired)”. .

  Then, using the acquired Blog article, the processing of Step 53 to Step 63 described above is executed.

  FIG. 12 shows the comment / trackback storage DB.

  At this time, in step 59, information on the trackback source article of the article D_E1 is read, and the hop count described in the column of the trackback source article (here, 2) and the hop count acquired in step 51 (here, 2) , The number of hops ≦ the hop count (No in step 59).

  At this point, the trackback source article acquisition process is terminated, and the process proceeds to a comment page / trackback page generation process.

[Generate comment page / trackback page]
Next, the generation of the comment page / trackback page will be described with reference to the flowchart of FIG.

  First, the comment page / trackback page generation unit 57 refers to the comment / trackback storage DB 53 and waits until there is no description of “O (acquiring)” in the acquisition status column of the trackback source. That is, it waits until the trackback source aggregation processing with the specified number of hops is completed (step 65).

  When the trackback source aggregation process is completed (Yes in step 65), the comment page / trackback page generation unit 57, for example, as shown in FIG. 12, the trackback source article described in the comment page / trackback storage DB 53 is used. Among them, the URL of the trackback source is blank (here, articles B_E1, E_E1 described in the column of Blog article D_E1), the URL of the currently viewed Blog article (here, A_E1), and the trackback The URL with the original acquisition status “black circle (acquired)” or “× (already acquired)” is compared (step 65).

  If the same URL is not found as a result of the comparison, “△ (reference)” is entered in the trackback source article acquisition status column indicated by the URL.

  On the other hand, when the same URL is found, “× (already acquired)” is entered in the acquisition status column of the trackback source article indicated by the URL.

  In the example of FIG. 12, “× (already processed)” is entered in the article B_E1 described in the Blog article D_E1 column, and “Δ (reference)” is entered in the article E_E1.

  Next, all comment statements (here, A_C1 (1), A_C1 (2), B_C1 (1), B_C1 (2), D_C1 (1)) described in the comment / trackback storage DB 53 are read and all the comments are read. A new comment page listing the sentences is generated (step 67).

  Here, as an example of the comment page, as shown in FIG. 14B, it is conceivable to separately present the comments to each trackback source article obtained by aggregating with the original comment sentence.

  Of the trackback statements described in the comment / trackback storage DB 53, the trackback source acquisition status is “black circle (acquired)” or “△ (reference)” (here, A_T1 (1), A_T1 ( 2), B_T1 (1), D_T1 (2)) are called to generate a new trackback page listing these trackback statements (step 68).

  Here, as an example of the trackback page, as shown in FIG. 14C, it is conceivable to separately present the trackback to each trackback source article obtained by aggregation with the original trackback.

  Although the newly generated comment page and trackback page are not shown in FIG. 5, they are managed on the internal memory or the hard disk of the comment / trackback aggregation device 2 of the trackback source.

  Next, in the comment / trackback anchor changing unit 58, the “comment” and “trackback” anchors given to the blog article (in this case, article A_E1) being browsed by the user acquired in the first step 52 are indicated. The URL is changed to the URL for the comment page and trackback page generated in step 67 and step 68 (step 69).

  At this time, as shown in FIG. 14A, the number of comments and the number of trackbacks described as anchor texts of “comments” and “trackbacks” are aggregated with the original number of comments and the number of trackbacks, for example. It is possible to present it so that the number of comments and trackbacks increased can be clearly understood.

  After that, when the user clicks on the modified “comment” or “trackback” anchor, the trackback of the article is added to the number of hops specified by the user in addition to the comment or trackback originally assigned to the blog article. A comment page and a trackback page, which are a compilation of comments and trackbacks attached to the original article, are presented.

  Examples of the present invention will be described below.

[First embodiment]
In the best mode for carrying out the invention described above, the case where there is one Blog article being viewed has been described. Here, as shown in FIG. 15, there may be a case where there are a plurality of Blog articles on the page being browsed.

  In this case, a comment / trackback storage DB 53 is prepared for each blog article being browsed, and the processing described in the best mode for carrying out the invention is executed for each blog article. “Comments” and “trackbacks” can be aggregated at once.

[Second Embodiment]
In the best mode for carrying out the invention, “comments” and “trackbacks” are dynamically aggregated when an action from a user using the aggregation operation interface occurs. On the other hand, in this embodiment, it is conceivable that the number of hops is set separately and the aggregation processing described in the best mode for carrying out the invention is performed in advance (periodically).

  In this case, when an action from the user occurs, a process of changing the URL indicated by the “comment” and “trackback” anchors described in step 69 to the URL generated in advance for the comment page and the trackback page. The response is faster than when the comment page and trackback page are dynamically generated.

[Third embodiment]
In addition, in the best mode for carrying out the invention, the comment / trackback aggregation device 2 of the trackback destination is introduced into the blog server and provided as one service of the blog site.

  In this embodiment, as shown in FIG. 16, the trackback destination comment / trackback aggregation device 2 is provided as a plug-in of the Web browser 6 of the user PC 2, and the best mode for carrying out the invention is shown. It is conceivable to execute the processing described in the above item on the user PC 2.

  At this time, as shown in FIG. 17, the aggregation operation interface 41 is displayed on the toolbar portion of the browser, so that the user can perform the “comment” and “trackback” aggregation operations for any blog site (Blog article). Can be executed.

[Fourth embodiment]
Further, as a fourth embodiment, as shown in FIG. 18, a dedicated Web service server 7 on which a trackback destination comment / trackback destination comment / trackback aggregation device 2 is mounted is provided and described in the best mode. It is conceivable that processing is executed by this Web service server.

  At this time, as shown in FIG. 17, a plug-in that displays the aggregation operation interface 41 on the toolbar portion of the Web browser is provided, and when an action from the user occurs, the URL of the Blog article being browsed by the user, It is conceivable that the designated number of hops is transmitted to the Web service server 7 and the subsequent aggregation process is executed by the Web service server 7.

  In addition, by using this Web service server 7 as a proxy of the Web browser, when browsing an arbitrary blog site, an aggregation operation interface 41 is additionally displayed as shown in FIG. Is also possible.

  The operations of the above embodiments and examples can be constructed as a program and installed in a computer used as a trackback source comment / trackback aggregation device, or distributed via a network.

  Further, the constructed program can be stored in a hard disk drive, a portable storage medium such as a flexible disk, a CD-ROM, or the like, and can be installed in a computer or distributed.

  The present invention is not limited to the above-described embodiments and examples, and various modifications and applications can be made within the scope of the claims.

  The present invention can be applied to a technology for following and linking a comment page and a trackback page of Blog.

It is a figure for demonstrating the principle of this invention. It is a principle block diagram of this invention. It is a block diagram of the comment / trackback aggregation system of the trackback source according to the embodiment of the present invention. It is an example of the display screen shown to a user at the time of browsing a blog site on an extended blog server in an embodiment of the present invention. 1 is a configuration diagram of a trackback source comment / trackback aggregation device according to an embodiment of the present invention. FIG. It is a flowchart of the operation | movement in one embodiment of this invention. It is an example of comment / trackback storage DB in one embodiment of this invention. It is an example (comment sentence) of the Blog analysis rule in one embodiment of the present invention. It is an example (trackback original article) of a Blog analysis rule in an embodiment of the present invention. It is the flowchart (the 1) of the acquisition process of the track back original article in one embodiment of this invention. It is an example (the 1) of comment track back storage DB in one embodiment of this invention. It is an example (the 2) of comment track back storage DB in one embodiment of this invention. It is a flowchart at the time of comment page / trackback page generation in one embodiment of the present invention. It is an example of presentation of a comment page / trackback page in an embodiment of the present invention. It is an example when there are a plurality of Blog articles according to the first embodiment of the present invention. It is a system configuration | structure figure of the 2nd Example of this invention. It is an example of a display of the aggregation interface of 2nd Example of this invention. It is a system configuration | structure figure of the 4th Example of this invention. This is an example of generating a comment page / trackback page from a blog article. This is an example of browsing blog articles hierarchically.

Explanation of symbols

1 Internet 2 Trackback source comment / trackback aggregation device 3 Extended blog server 4 Blog server 5 User PC
6 Web browser 7 Web service server 41 Aggregation operation interface 51 Blog article analysis unit, Blog article analysis unit 52 Blog analysis rule 53 Comment / trackback storage database 54 Comment acquisition unit, comment acquisition unit 55 Trackback acquisition unit, trackback acquisition unit 56 Trackback source Acquisition means, trackback source acquisition section 57 comment page / trackback page generation means, comment page / trackback page generation section 58 comment / trackback anchor change means, comment / trackback anchor change section

Claims (6)

This is a method of aggregating comments and trackbacks from trackbacks, by tracking the trackbacks on the blog articles and generating a page that summarizes the comments and trackbacks from the trackbacks.
Using the Blog analysis rule that describes the processing contents to be executed and stored in the storage means, the URL of the Blog article, the comment attached to the Blog article and the anchor of the track back are obtained from the Blog article, Blog article analysis step to store in the trackback storage database,
Using the Blog analysis rule, a comment acquisition step of acquiring each comment sentence from a page indicated by the anchor of the comment (comment page) and storing it in the comment / trackback storage database;
Using the Blog analysis rule, a trackback acquisition step of acquiring each trackback sentence from a page indicated by the trackback anchor (trackback page) and storing it in the comment / trackback storage database;
A trackback source acquisition step for acquiring a trackback source article indicated by each trackback statement described in the comment / trackback storage database;
A comment page described in the comment / trackback storage database, a comment page based on the trackback sentence, and a comment page / trackback page generation step for newly generating a trackback page;
Comment / trackback anchor change step for changing the comment given to the blog article and the URL indicated by the trackback anchor to the comment page generated in the comment page / trackback page generation step and the URL to the trackback page;
A method for aggregating comments and trackbacks of trackback sources, characterized in that The comment / trackback storage database is:
For each blog article, the hop count indicating how many steps the blog article is from the first blog article, the comment sentence and trackback sentence given to the blog article, the URL of the trackback source article indicated by each trackback sentence, and each trackback source The trackback source comment / trackback aggregation method according to claim 1, wherein the article acquisition status is managed. A trackback source comment / trackback aggregator that traces trackbacks on blog articles and generates trackback source comments and trackback pages.
Blog article analysis means for acquiring the URL of the Blog article from the Blog article, the comment attached to the Blog article and the anchor of the track back,
Comment acquisition means for acquiring each comment sentence from a page (comment page) indicated by the anchor of the comment;
Trackback acquisition means for acquiring each trackback sentence from a page (trackback page) indicated by the trackback anchor;
Describe the processing content executed by the Blog article analysis means, the comment acquisition means, the trackback acquisition means, and a Blog analysis rule stored in the storage means,
A comment / trackback storage database for storing information acquired by the blog article analysis means, the comment acquisition means, and the trackback acquisition means;
Trackback source acquisition means for acquiring the trackback source article indicated by each trackback statement described in the comment / trackback storage database;
A comment page described in the comment / trackback storage database, a comment page based on the trackback sentence, and a comment page / trackback page generating means for newly generating a trackback page;
Comment / trackback anchor changing means for changing the comment given to the blog article and the URL indicated by the trackback anchor to the comment page generated by the comment page / trackback page generating means and the URL to the trackback page;
An apparatus for aggregating comments / trackbacks of trackbacks, characterized by comprising: The comment / trackback storage database is:
For each blog article, the hop count indicating how many steps the blog article is from the first blog article, the comment sentence and trackback sentence given to the blog article, the URL of the trackback source article indicated by each trackback sentence, and each trackback source The trackback source comment / trackback aggregation device according to claim 3, which manages an article acquisition status.   3. A trackback source comment / trackback aggregating program for causing a computer to execute the steps of the trackback source comment / trackback aggregating method according to claim 1 or 2.   3. A storage medium storing a trackback source comment / trackback aggregation program, wherein a program for causing a computer to execute each step of the trackback source comment / trackback aggregation method according to claim 1 is stored.

Images