JP4843512B2 - Information presentation server - Google Patents

Description

  The present invention relates to an information presentation server that accepts trackbacks such as blogs (Web logs: diary-like sites).

  A general blog has a function of attaching a comment to an article posted by the author, and a function called Trackback for associating with an article of another blog. A blog with a trackback function has issued a trackback URL (Uniform Resource Locator) for an article that accepts a trackback, and if you write an article (child article) on your blog with reference to that article (parent article) By sending a trackback Ping to the trackback URL of the parent article, a summary of the child article, a URL link, etc. (trackback information) are posted in the blog on the parent article side in a state associated with the parent article (for example, patents) Reference 1 etc.).

Trackback is a specification implemented by Six Type's Mobile Type (product name) and is the de facto standard. The specification does not include information on the design, and the display design including the layout is determined by the template of the track back destination, and the track back information is generally posted only by the character information.
JP 2005-250826 A

  By the way, trackbacks are performed with the expectation of the guidance of browsing from the blog of the trackback destination to your blog (trackback source), and I want to assert myself with an eye-catching design (including layout). As described above, since the information on the design is not included in the general specification of the trackback, there is a problem that it is difficult to obtain the individuality of the trackback source. In addition, there is a problem that the viewer lacks conclusiveness when searching for a blog to be browsed from a title or summary based only on text information in the trackback list.

  In order to include information about the design in the trackback, it is necessary to extend the specification independently, but in order to perform an extended display of the design, both the trackback source and the trackback destination must implement this extended specification, For blogs that accept only regular trackbacks, there is a problem that trackbacks are not possible.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to provide compatibility and expandability information that can include information on the design designated by the trackback source in the trackback. To provide a presentation server.

In order to solve the above-described problems, in the present invention, as described in claim 1, trackback receiving means for receiving trackback based on a general specification from another server, and general to another server Trackback transmission means for transmitting trackbacks based on various specifications, and design information acquisition for requesting other servers to acquire design information described in the markup language for trackback display when receiving trackbacks from other servers Means, design information transmitting means for transmitting design information in response to a request for design information described in a markup language for trackback display from another server, and based on the design information at the time of a browsing request from a client and display means for displaying the trackback contents Te, by the display means Means for obtaining an induced number of browsing to track back the source from link shown trackback contents were, a means for specifying the date and time of track back to be displayed, and means for changing the display of the trackback in accordance with the derived number and the date and time An information presentation server comprising

  Also, as described in claim 2, in the information presentation server according to claim 1, the design information acquisition means includes a design in which a predetermined character string is added to an address of a trackback source included in the received trackback information. Design information can be acquired by transmitting a request for acquiring design information to the information acquisition address.

  According to a third aspect of the present invention, in the information presentation server according to the first aspect, the design information acquisition unit includes a design information acquisition address included in a parameter added to the destination address of the received trackback. On the other hand, a design information acquisition request can be transmitted to acquire design information.

  In addition, as described in claim 4, in the information presentation server according to claim 1, the design information acquisition unit requests the design information acquisition for the design information acquisition address included in the received trackback information. To obtain design information.

In addition, as described in claim 5 , receiving a trackback based on a general specification from another server, transmitting a trackback based on the general specification to another server, and from another server The process of obtaining the design information described in the markup language for the trackback display by requesting the other server when the trackback is received, and the design information described in the markup language for the trackback display from the other server Of the trackback content displayed by the step of transmitting the design information corresponding to the request of the client, the step of displaying the trackback content based on the design information at the time of browsing request from the client, and the step of displaying the trackback content. A method to obtain the number of browsing guidance from the link to the trackback source When, it is possible to configure the step of specifying the date and time of track back to be displayed, the display of the trackback as trackback information presentation control method and a step of changing in response to the induction number and the date and time.

In addition, as described in claim 6 , a function of receiving a trackback based on a general specification from another server, a function of transmitting a trackback based on a general specification to another server, and a function from another server A function for requesting the other server to acquire the design information described in the markup language for the trackback display when the trackback is received, and the design information described in the markup language for the trackback display from the other server Of the trackback content displayed by the function of transmitting the design information corresponding to the request for the trackback, the function of displaying the trackback content based on the design information at the time of browsing request from the client, and the function of displaying the trackback content. A machine that obtains the number of leads for browsing from the link to the trackback source When, it is possible to configure the function of specifying the date and time of track back to be displayed, the display of the trackback as trackback information presentation control program for realizing the function of changing in accordance with the derived number and the date and time to the computer.

  In the information presentation server of the present invention, the information related to the design designated by the trackback source can be included in the trackback, and both compatibility and expandability can be achieved.

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

<System configuration>
FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 1, a blog server 2A, 2B that supports the design function of the present invention and a blog server 2C that does not support the design function are connected to a network 1 such as the Internet, and a plurality of arbitrary clients 3A. 3B etc. are connected.

  FIG. 2 is a diagram showing a configuration example of the blog servers 2A and 2B corresponding to the design function of the present invention.

  In FIG. 2, the blog servers 2A and 2B include a web server 21. The web server 21 has a blog DB 22, a template storage unit 23, an account management unit 24, an article submission management unit 25, a comment management unit 26, and a trackback management unit. 27, a design management unit 28, and a page display unit 29. A typical system for a blog is a mobile type of Six Apart. Mobile Type is server software that generates and manages a blog site, and is used by being incorporated into a standard Web server. Articles submitted by users from web browsers, etc., are stored in a database built with RDBMS (Relational Data Base Management System), and pages are generated based on templates prepared in advance. A list of articles is automatically generated. It also provides a series of functions required for weblogs, such as a calendar, comment posting field, and trackback.

  In FIG. 2, the blog DB 22 holds various information necessary for processing as a blog. An account table 221 that holds account information, an article table 222 that holds article information, and a comment that holds comment information. The table 223 includes a trackback table 224 that holds trackback information, and a trackback design table 225 that holds trackback design information.

  FIG. 3 is a diagram illustrating examples of various tables in the blog DB 22. The account table 221 includes fields such as account ID, account name, password, blog name, blog URL, blog creation date, e-mail address, nickname, real name, date of birth, and other personal information. The article table 222 includes fields such as an article ID, an account ID, a title, a body text, a summary, and a posting date / time. The comment table 223 includes fields such as a comment ID, an article ID, a title, a body text, a nickname, an e-mail address, a URL, and a posting date / time. The trackback table 224 includes fields such as a trackback ID, an article ID, a title, an outline, a blog name, a URL, and a posting date / time. The trackback design table 225 includes fields such as a trackback design ID, a trackback ID, and design information. The account table 221 and the article table 222 are associated with each other by the account ID, the article table 222, the comment table 223, and the trackback table 224 are associated with each other by the article ID, and the trackback table 224 and the trackback design table 225 are associated with the trackback ID. They are associated with each other.

  FIG. 4 is a diagram showing an example of design information stored in the trackback design table 225, which is described in general HTML (Hyper Text Markup Language). The "<! --- image_file --->" part is replaced with the image file name such as an icon, the "<! --- title --->" part is replaced with the title of the entry, and the "<! --- excerpt ---> ”is replaced with the entry summary,“ <! --- url ---> ”is replaced with the entry's permalink (URL), and“ <! --- blog_name ” ---> "is replaced with the name of the blog where the entry is posted.

  Returning to FIG. 2, the account management unit 24 manages accounts of users who use the blog servers 2 </ b> A and 2 </ b> B, and includes an account addition unit 241 that adds accounts, an account deletion unit 242 that deletes accounts, An account editing unit 243 that performs account editing and an account authentication unit 244 that performs account authentication are provided.

  The article submission management unit 25 manages the submission of articles to the blog, and includes an article addition unit 251 for adding articles, an article deletion unit 252 for deleting articles, and an article correction unit 253 for correcting articles. It has.

  The comment management unit 26 manages comments attached to a blog article by a viewer. A comment submission unit 261 that inputs a comment, a comment deletion unit 262 that deletes a comment, and a correction of the comment And a comment correction unit 263.

  The trackback management unit 27 manages trackbacks with other blog servers (both when performing trackbacks on other blog servers and when receiving trackbacks from other blog servers). A trackback transmission unit 271 that transmits a trackback to a blog server, a trackback reception unit 272 that receives a trackback from another blog server, and a trackback design that transmits design information corresponding to a request for design information from another blog server A transmission unit 273 and a trackback design acquisition unit 274 that requests the other blog server to acquire design information when a trackback is received from another blog server.

  The design management unit 28 manages a template used for displaying a blog, and includes a template registration unit 281 that registers a template in the template storage unit 23 and a template correction unit 282 that corrects the template. The template is described in HTML, and a template for displaying a blog title, an article title, an article body, a trackback list, a menu, navigation, a blog part, etc. as elements of a blog page as shown in FIG. Become.

  Returning to FIG. 2, the page display unit 29 displays a blog page in response to access from the clients 3A and 3B (FIG. 1), and displays an article list display unit 291 that displays an article list and article contents. An article display unit 292, a comment display unit 293 for displaying comments, and a trackback display unit with design 294 for displaying a trackback list with design are provided.

  Although the configuration of the blog server 2C that does not support the design function is not particularly illustrated, the trackback design table 225, the trackback design transmission unit 273, and the trackback design acquisition unit 274 are removed from the configuration of FIG. The display unit 294 is configured as a normal trackback display unit.

<Operation>
FIG. 5 is a diagram showing an outline of the operation of the above-described embodiment.

  5, when a trackback is transmitted from the blog server 2B corresponding to the design function to the blog server 2A corresponding to the design function (step S1), the blog server 2A makes an inquiry about design information to the blog server 2B. The blog server 2B transmits design information to the blog server 2A (step S3). As a result, when the access is made from the clients 3A and 3B, the design information is reflected on the trackback of the blog server 2B in the trackback list of the blog server 2A.

  Further, when a trackback is transmitted from the blog server 2C that does not support the design function to the blog server 2A that supports the design function (step S4), the blog server 2A inquires of the blog server 2C about design information. However, since the blog server 2C does not support the design function, an error is transmitted to the blog server 2A (step S6). As a result, when accessing from the clients 3A and 3B, the trackback of the blog server 2C in the trackback list of the blog server 2A is displayed with the default design information.

  As described above, the trackback itself is performed according to the normal specification, and the design information is acquired by the processing after receiving the trackback. Therefore, both compatibility and expandability can be achieved.

  Hereinafter, the operation will be described in more detail.

  FIG. 6 is a diagram showing a processing example at the time of trackback transmission, and is a processing example when a trackback is transmitted from the blog server 2B corresponding to the design function to the blog server 2A corresponding to the design function.

  In FIG. 6, when a trackback is transmitted from the trackback transmission unit 271 of the blog server 2B to the blog server 2A (step S11), the trackback reception unit 272 receives the trackback in the blog server 2A.

  Next, in the blog server 2A, the trackback design acquisition unit 274 acquires a design information acquisition URL (design information URL) from the trackback information or the like (step S12), and transmits a request to the design information acquisition URL of the blog server 2B. Thus, the design information is inquired (step S13).

  7 to 9 are diagrams showing examples of transmission data. In each figure, (a) shows trackback transmission data (HTTP (Hyper Text Transfer Protocol) POST request) from the blog server 2B to the blog server 2A. (B) is an example of design data inquiry transmission data (HTTP GET request) from the blog server 2A to the blog server 2B.

  FIG. 7 shows a predetermined character string “/ tracktemp” in the “url = http: //blogs.yahoo.co.jp/hoge/1234” portion indicating the URL of the trackback source of the trackback information included in the trackback transmission data (a). A URL to which “.html” is added is determined in advance as a design information acquisition URL, which is used as the destination URL of the design information inquiry transmission data (b).

  FIG. 8 includes a parameter “temp = http: //blogs.yahoo.co.jp/hoge/1234/tracktemp.html” added to the trackback destination URL included in the trackback transmission data (a). “http://blogs.yahoo.co.jp/hoge/1234/tracktemp.html” is used as the destination URL of the design information inquiry transmission data (b).

  FIG. 9 shows “http: // blogs” included in one item “tracktmp = http: //blogs.yahoo.co.jp/hoge/1234/tracktemp.html” of the trackback information included in the trackback transmission data (a). .yahoo.co.jp / hoge / 1234 / tracktemp.html "is used as the destination URL of design information inquiry transmission data (b).

  Returning to FIG. 6, the blog server 2B that has received the design information inquiry acquires design information prepared in advance from the designated design information acquisition URL (step S14), and the trackback design transmission unit 273 causes the blog server 2A to acquire the design information. The design information is transmitted to (step S15).

  The blog server 2A stores the acquired design information in the trackback design table 225 by the trackback design acquisition unit 274 (step S16), and prepares for display of a trackback list at the time of access from the clients 3A and 3B.

  FIG. 10 is a diagram showing an example of blog display at the time of access from the clients 3A and 3B. According to the template stored in the template storage unit 23, the blog title, article title, article body, trackback list, menu, navigation, Blog parts and the like are displayed, and the trackback list is displayed according to the design information stored in the trackback design table 225.

  FIG. 11 is a diagram showing a processing example at the time of trackback transmission, and is a processing example when a trackback is transmitted from the blog server 2C not supporting the design function to the blog server 2A corresponding to the design function.

  In FIG. 11, when a trackback is transmitted from the trackback transmission unit 271 of the blog server 2C to the blog server 2A (step S21), the trackback reception unit 272 receives the trackback in the blog server 2A.

  Next, in the blog server 2A, the trackback design acquisition unit 274 acquires a design information acquisition URL (design information URL) from the trackback information or the like (step S22), and transmits a request to the design information acquisition URL of the blog server 2C. Thus, the design information is inquired (step S23). In addition, when the URL obtained by adding a predetermined character string to the trackback source URL shown in FIG. 7 is used as the design information acquisition URL, the design information can be inquired. However, in the method shown in FIG. Since the corresponding URL is not included in the trackback transmission data from the blog server 2C that does not support the function, the design information is not inquired.

  The blog server 2C that has received the inquiry about the design information tries to access the designated design information acquisition URL, but the acquisition fails because the design function is not supported (step S24), and the blog server 2A receives an error ( 404 not found) is transmitted (step S25).

  Since the blog server 2A cannot acquire design information, the trackback design acquisition unit 274 sets default design information in the trackback design table 225 (no special setting is made when the default design is automatically applied). (Step S26), in preparation for displaying a trackback list at the time of access from the clients 3A, 3B. When accessed from the clients 3A and 3B, the trackback of the blog server 2C in the trackback list of the blog server 2A is displayed with default design information.

<Modification>
FIG. 12 is a diagram illustrating a configuration example of the blog servers 2A and 2B according to another embodiment. The display of the trackback list is changed according to the number of guidance (the number of guidance from the trackback list to the trackback source) and the date and time when the trackback is performed. It is what I did.

  In FIG. 12, the design trackback display unit 294 of the blog servers 2A and 2B has a display position control unit 295 that controls the display position of the entry of the blog that has been tracked back, and changes the display size of the entry according to the number of guidance. A display size control unit 296 and a display gray level control unit 297 that changes the display gray level of the entry according to the date and time designated by a slider or the like are provided.

  In order to obtain the number of leads, the link in the trackback article points to the blog servers 2A and 2B, and the redirector 201 that redirects to the original link destination (trackback source) in response to access to the URL; A guidance number totaling unit 202 that totals redirect processing of the redirector 201 and stores it in the guidance number DB 203 is provided. The reason for this configuration is that the link source (trackback destination) cannot know whether or not the link (anchor) displayed on the client side has been clicked on a normal link.

  FIG. 13 is a diagram illustrating an example of the guidance number DB 203, where (a) is a field configuration and (b) is an example of specific values. The guidance number DB 203 has fields such as guidance number ID, trackback ID, date and time, and guidance number.

  FIG. 14 is a diagram showing an example of a correspondence relationship between the number of leads and the display size. The number of display pixels is increased in accordance with the number of leads, but the minimum and maximum sizes are defined in advance. Aside from this, even when the number of inductions is far from the others, it is within a certain range. In the example shown in the figure, the minimum size is 50 pixels and the maximum size is 200 pixels, and the size is increased by 10 pixels for every 10 guidances.

FIG. 15 is a diagram showing a display example of the trackback list. Blog entries tracked back after the date and time designated by the slider 31 are not displayed, and blog entries 32, 33 and 34 tracked back immediately before the date and time are not displayed. Is displayed darker, and the color of the old entry becomes lighter as the time interval with the date and time designated by the slider 31 becomes longer. For the color density of the entry, the difference between the posting date and time specified in the trackback table 224 (FIG. 3) and the date and time specified by the slider 31 is obtained, and the transparency per unit time is multiplied by the difference time. For example, if the unit time is 1 hour, the transparency per unit time is 90%, and the trackback posted at 10:00 on 2006/12/4 16:00 is displayed at 16:00 on 2006/12/4,
Time difference 6 hours → 6 unit hours,
90% × 90% × 90% × 90% × 90% × 90% = 53.1441%
Thus, it is displayed with a color of 53.1441% of the original color.

  Also, the display size changes depending on the number of inductions per unit time. For example, if the number of inductions from the track back during one hour is large, the display size is large. If the number of inductions is small, the display size is small. In the figure, the entries 32 and 33 have the same number of inductions, and the number of inductions of the entry 34 is small. The display size of the entry is obtained from the guidance number DB 203 for each trackback at the date and time designated by the slider 31, and the entry display size is obtained from the table shown in FIG. 14 based on the obtained guidance number.

  Each entry display can be moved by dragging with a mouse or the like.

  Further, by moving the slider 31, it is possible to go back to the past, new entries that have been displayed so far are not displayed, light-colored entries become darker, and the display size becomes the current size. You can also go back to when the trackback was posted by double-clicking on the entry. In this case, the position of the slider 31 is also interlocked.

<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 structural example of the system concerning one Embodiment of this invention. It is a figure which shows the structural example of a blog server. It is a figure which shows the example of the various tables in blog DB. It is a figure which shows the example of design information. It is a figure which shows the operation | movement outline | summary of embodiment. FIG. 10 is a diagram (part 1) illustrating a processing example during trackback transmission; FIG. 6 is a diagram (part 1) illustrating an example of transmission data. FIG. 11 is a second diagram illustrating an example of transmission data. FIG. 10 is a diagram (part 3) illustrating an example of transmission data; It is a figure which shows the example of a display of a blog. FIG. 10 is a second diagram illustrating a process example during track back transmission; It is a figure which shows the structural example of the blog server concerning other embodiment. It is a figure which shows the example of induction | guidance | derivation number DB. It is a figure which shows the example of the correspondence of the induction | guidance | derivation number and display size. It is a figure which shows the example of a display of a track back list.

Explanation of symbols

1 Network 2A to 2C Blog Server 21 Web Server 22 Blog DB
221 Account table 222 Article table 223 Comment table 224 Trackback table 225 Trackback design table 23 Template storage unit 24 Account management unit 241 Account addition unit 242 Account deletion unit 243 Account editing unit 244 Account authentication unit 25 Article submission management unit 251 Article addition unit 252 Article deletion unit 253 Article correction unit 26 Comment management unit 261 Comment submission unit 262 Comment deletion unit 263 Comment correction unit 27 Trackback management unit 271 Trackback transmission unit 272 Trackback reception unit 273 Trackback design transmission unit 274 Trackback design acquisition unit 28 Design management Section 281 Template registration section 282 Template correction section 29 Page display section 91 article list display unit 292 articles display section 293 comments display unit 294 design with trackback display unit 295 display position control unit 296 display size control unit 297 display grayscale control unit 201 redirector 202 induction number counting unit 203 induced the number of DB
3A, 3B client

Claims (6)

Trackback receiving means for receiving trackbacks based on general specifications from other servers;
A trackback transmission means for transmitting a trackback based on a general specification to another server;
Design information acquisition means for requesting the other server to acquire design information described in a markup language for trackback display when receiving a trackback from another server;
Design information transmission means for transmitting design information corresponding to a request for design information described in a markup language for trackback display from another server;
Display means for displaying the trackback content based on the design information at the time of a browsing request from the client ;
Means for obtaining the number of browsing guidance from the link of the trackback content displayed by the display means to the trackback source;
Means to specify the date and time of the trackback to be displayed;
An information presentation server comprising: means for changing a trackback display according to the number of guidance and the date and time . In the information presentation server according to claim 1,
The design information acquisition means acquires design information by transmitting a design information acquisition request to a design information acquisition address in which a predetermined character string is added to the trackback source address included in the received trackback information. Feature information presentation server. In the information presentation server according to claim 1,
The design information acquisition means transmits the design information acquisition request to the design information acquisition address included in the parameter added to the received trackback destination address, and acquires the design information. server. In the information presentation server according to claim 1,
The information presentation server, wherein the design information acquisition means acquires a design information by transmitting a design information acquisition request to a design information acquisition address included in the received trackback information. Receiving trackbacks from other servers based on general specifications;
Sending trackbacks based on general specifications to other servers;
A step of requesting the other server when receiving a trackback from another server and obtaining design information described in a markup language for displaying the trackback; and
A step of transmitting design information corresponding to a request for design information described in a markup language for trackback display from another server;
A step of displaying the trackback content based on the design information at the time of a browsing request from a client ;
Obtaining the number of browsing guidance from the link of the trackback content displayed in the step of displaying the trackback content to the trackback source;
A process for specifying the date and time of the trackback to be displayed;
A trackback information presentation control method comprising: a step of changing a trackback display according to the number of guidance and the date and time . The ability to receive trackbacks based on general specifications from other servers;
The ability to send trackbacks based on general specifications to other servers,
A function of requesting the other server to acquire design information described in a markup language for displaying a trackback when a trackback is received from another server;
A function for transmitting design information in response to a request for design information described in a markup language for trackback display from another server;
A function to display the trackback content based on the design information when a browsing request is made from a client ;
A function of acquiring the number of browsing guidance from the link of the trackback content displayed by the function of displaying the trackback content to the trackback source;
A function to specify the date and time of the trackback to be displayed,
A trackback information presentation control program for causing a computer to realize a function of changing a trackback display according to the number of guidance and the date and time .