JP5237875B2 - Shared article publishing system - Google Patents

Description

The present invention, "weblog (hereinafter referred to as the blog, including a bulletin board)", "Home", as such as "mail" relates from a plurality of users in the public system of shared articles on the possible network browsing.

Currently, user terminals of personal computers and mobile phones have a display unit and a web browser for browsing a site displayed on the display unit on the Internet. In addition, tools such as “blog” in which a specific “article creator” writes “shared articles” composed of text, images, videos, etc. by a web browser of a user terminal are generally used. There is a blog system that allows the article creator to show / hide the shared article written in (For example, see Patent Document 1)
In the blog system of Patent Document 1, it is set whether an article created by the article creator on the management screen is to be disclosed (displayed) or not disclosed (not displayed). In the case of setting to non-public, this blog system can be set to hide for each item such as title, name, and body.

JP 2008-097238 A

  However, the conventional blog system has the following problems.

  For example, the name, title, body, etc. can be hidden by item, but a part of the blog article cannot be hidden.

The present invention has been made paying attention to the above problem, and it is possible to hide a part of a shared article such as a blog article on the article creator side, and to display this hidden part to the viewer of the shared article. by to select whether or not to, an object of the present invention to provide a shared article published system that can be made to have the stage to the openness of its own article to the article author.

In order to solve the above problem, in the shared article publishing system according to claim 1, a network using wireless and wired communication lines, a plurality of user terminals connected to the network, a server connected to the network, A database that is connected to a server and stores shared articles in a readable and writable manner, and each user terminal is connected to the server via the network to view or edit the shared articles. A display unit for displaying the shared article;
Operating means for operating the browsing / editing means,
The server includes a shared article output unit that outputs a shared article in the database, and the shared article output unit outputs a shared article from the database by browsing / editing by an operation unit of any of the plurality of user terminals. In the shared article publishing system that reads and displays the shared article on the display unit of the user terminal,
The server has a seal output unit that outputs a seal that can be displayed on the display unit of each user terminal and hides a shared article,
When a non-display range is set to the shared article displayed on the display unit by the operation means of the user terminal,
Each time the shared article is read from the database, the seal output means of the server outputs a seal that hides the shared article of the set non-display range,
When the user terminal that performs browsing or editing receives the sticker output from the sticker output unit of the server, the browsing / editing unit of the user terminal covers the shared article in the set non-display range with the sticker. Displayed on the display unit,
When this sticker is selected by operating the operation means of each user terminal (clicking a mouse button, etc.), the shared article part covered with this sticker is displayed ,
When the first seal is selected by operating the operation means of the user terminal, information on the selected first seal and the user terminal is transmitted to the server, and the server receives the information and receives the information. The terminal is prohibited from outputting the seal once selected .

  According to the present invention, a part of a shared article can be hidden on the user terminal, and the article creator can himself / herself select whether or not to display the hidden part for the viewer of the shared article. You can have a stage in the openness of articles.

1 is an overall configuration diagram of a blog system as an example of a shared article publishing system provided on a network. It is a figure which shows the flowchart of the main process operation | movement of a server. It is a figure which shows the flowchart of blog article creation / edit of FIG. It is a figure which shows the flowchart of the preview display of FIG. It is a figure which shows the flowchart of the blog article browsing operation | movement of the server of FIG. It is a figure which shows the flow of data and a process over time at the time of accessing a server from a user terminal and creating / editing a blog article. It is a figure which shows the flow and process of a time-dependent data at the time of accessing a server from a user terminal and browsing a blog article. It is a figure which shows a data flow and a process over time when accessing a server from a user terminal and browsing a blog article by an RSS reader. An example of a unique tag used on the blog article creation page and a tag example after the unique tag is converted by the server are shown. (A)-(C) It is explanatory drawing at the time of acquiring a seal | sticker display range. (A) It is a figure which shows the example of the article text at the time of editing the blog article by the tape type original tag. (B) The HTML source data after the article text of (A) is converted by the server. (C) It is a figure which shows the state which browsed this HTML source data actually with the browser. (D) It is a figure which shows the state which selected and peeled off the tape type seal displayed on (C). (A) It is a figure which shows the example of article text at the time of editing the blog article by the box type original tag. (B) The HTML source data after the article text of (A) is converted by the server. (C) It is a figure which shows the state which browsed this HTML source data actually with the browser. (D) It is a figure which shows the state which selected and peeled off the box-type seal | sticker currently displayed on (C). (A) It is a figure which shows the example of article text at the time of editing the blog article by the sticker type original tag. (B) The HTML source data after the article text of (A) is converted by the server. (C) It is a figure which shows the state which browsed this HTML source data actually with the browser. (D) It is a figure which shows the state which selected and peeled off the sticker type sticker currently displayed on (C). (A) It is a figure which shows the example of the article text at the time of sticking a sticker over. (B) The HTML source data after the article text of (A) is converted by the server. (C) It is a figure which shows the state which browsed this HTML source data actually with the browser. (D) It is a figure which shows the state which selected and peeled off the tape-type seal | sticker (1st) currently displayed on (C). (E) It is a figure which shows the state which selected and peeled off the tape-type seal | sticker (2nd) currently displayed on (D). (A) It is a figure which shows the state by which the tape-type seal | sticker and the box-type seal | sticker were piled up in this order on the blog article. (B) It is a figure which shows the state which the box type seal | sticker of (A) was peeled and the tape type seal | sticker was exposed. (C) It is a figure which shows the state by which the tape-type seal | sticker of (B) was peeled off. (A) It is a figure which shows the state by which three stickers are piled up on the blog article. (B) It is a figure which shows the state by which the 1st seal | sticker was peeled among the seal | stickers of (A). (C) It is a figure which shows the state by which the 2nd seal | sticker was peeled off. (D) It is a figure which shows the state by which the 3rd seal | sticker was peeled off. (A) It is a figure which shows the blog article in a message database. (B) A state where the blog article of (A) is converted by the server for RSS distribution. (C) A state where the converted blog article of (B) is viewed on the user terminal. It is the figure which showed the example which publishes a blog article in steps on the same page.

  Hereinafter, the form which implement | achieves the shared article publication | presentation system of this invention is demonstrated based on the Example shown, referring drawings.

  XML is an abbreviation for Extensible Markup Language, and is a language for describing the logical structure and physical structure of data and sentences. HTML is an abbreviation for HyperText Markup Language, and is one of the languages for creating Web pages. CSS is an abbreviation for cascading style sheet, and indicates how to display HTML and XML elements.

  URL is an abbreviation for Uniform Resource Locator, and is used to specify the location of a terminal or file on the network. RSS is an abbreviation for RDF Site Summary (RSS 0.9 and RSS 1.0), Rich Site Summary (RSS 0.91), and Really Simple Syndication (RSS 2.0). It is written in XML and used to distribute update information. .

  CGI is an abbreviation for Common Gateway Interface and refers to a mechanism for a Web server to start a program in response to a request from a Web browser. ASP is an abbreviation for Active Server Pages, and is an extended function of a Web server that dynamically generates a Web page.

The database (DB) collects and manages data in accordance with a specific theme so that it can be easily reused for search and extraction.
mp3 is an abbreviation for MPEG Audio Layer-3, and is one of compressed audio file formats for digital audio. WAV or WAVE (RIFF waveform Audio Format) is a format for describing audio data. JavaScript (registered trademark) is a script language used to create a program that operates on a Web page.

  GIF, PNG, and JPEG are image file formats often used on the Internet.

  A cookie is a mechanism in which a provider of a website temporarily writes and stores data on a user terminal of a viewer through a web browser. In this example, it indicates written information.

A hyperlink refers to position information such as another document or image embedded in a document. “Hyperlink” refers to the act of attaching a hyperlink.
Flash (registered trademark) is a standard for handling moving images and games developed by Adobe Systems and a software group of the company that produces the standard, and a content file created thereby is called a Flash file.

A search robot refers to a program that collects every web page in the world in order to create a search database of a full-text search type search engine.
A seal hides part or all of a shared article.

  As shown in FIG. 1, a blog system 100 that is an example of a shared article publishing system includes a network 1 using wireless and wired communication lines such as the Internet and an intranet, and a server 10 that is connected to the network 1 and provides Web content. And a database 2 connected to the server 10, personal computers (user terminals) 2A and 2B used by users (article creators and viewers), a mobile phone (user terminal) 2C, and the like. The user terminals 2A, 2B, 2C are connected to the network 1 described above.

The server 10 can exchange information with the user terminals 2A, 2B, and 2C via the network 1.
<Server>
The server 10 provides its own functions and data to the user terminals 2A, 2B, and 2C via the network 1 based on the web application program.

  That is, the server 10 uses a Web server function, a file server function, a function for outputting a sticker to the user terminals 2A, 2B, and 2C using these server functions (seal output means) and a function for outputting a blog article ( And a blog function having a shared article output unit), and performs each process in response to a request from the user terminals 2A, 2B, and 2C.

  The blog function is a function related to blog article browsing, such as a main processing operation function, a user authentication function, a user registration function, and a function related to blog article creation / editing, which will be described later.

  The database 2 is identified by a message database 4 for a blog article (shared article), a registered user information database (user database) 5 of a registered user, and an ID (hereinafter referred to as a seal ID) for specifying a seal type. A seal part database 3 storing seal images, sound data, and the like as seals; a server program for a Web server; a Web application program that is executed by the Web server and is a CGI such as an ASP; A CSS file, a file described in JavaScript, and the like are saved.

  In the message database 4, when a blog article is newly created by creating / editing a blog article described later, a blog article ID, a blog article title, a blog article, and an ID for identifying each seal set for this blog article (Hereinafter referred to as “seal SID”), a browsing log for each seal is stored.

  The blog article ID is a unique ID attached to the blog article, and is stored in the message database 4 together with the blog article. The blog article ID is used to specify the blog article when the server 10 reads the blog article from the message database 4.

  The seal SID is a unique ID such as a serial number assigned to the seal such as “tape1_1”, “tape1_2”, and “tape1_3”.

  The browsing log is a list composed of data such as time, seal SID, and user (viewer). That is, it indicates whether or not the seal image has been selected as described later by the viewer, that is, whether or not the seal has been removed, and is stored in the items of “time” (described later), “seal SID”, and “viewer”. In this case, for example, “200904030942131412”, “tape1_1”, and “user1”, respectively. In addition, the cookie issued to the user terminal can be used as the “viewer” data.

  The blog article title and the blog article are text data such as HTML format.

  When the user is registered, the user database 5 stores a user ID, a user password (hereinafter referred to as a user PWD), and the like. The user ID and user PWD are text, numeric data, or a combination thereof.

Although the blog function described above is carried out by one server 10, the present invention is not limited to this, and another server or database that cooperates with the server 10 may be provided through the network 1 or another network.
(Seal parts)
The seal includes a tape type, a box type, and a sticker type (see FIGS. 11C to 13C). The image (seal image) used as a sticker is, for example, a pattern or a comment character such as “I am surprised!” Or “!!”. For this image, an image in an image format that can be displayed on a web page such as PNG, JPEG, or GIF is selected. “Horizontal width” described below means the width and length in the left-right direction (in the figure), and “vertical width” means the width in the up-down direction (in the figure).
[Tape type]
The tape type sticker is a type of sticker that can hide blog articles in character units, and the width of the tape is the side of this blog article part when the blog article part surrounded by unique tags is displayed on the web page It is almost the same as the width.

In addition, the vertical width of the tape is basically the vertical width per line of the text of the blog article displayed on the web page (see the seal a1 in FIG. 11C), but as a result, the blog article is unreadable. Therefore, even if it is not substantially the same as the vertical width, it may be slightly smaller.
[Box type]
The box-type sticker is a sticker that hides a plurality of lines of a blog article at a time, and is pasted so as to hide a line including a blog article surrounded by a unique tag as will be described later.

The horizontal width of the seal is set to be equal to or larger than the horizontal width of the maximum row in the blog article portion when the blog article portion surrounded by the unique tag is displayed on the web page. Further, the vertical width of the seal is set to be equal to or greater than the vertical width occupied on the web page when the blog article portion is displayed on the web page (see seal a2 in FIG. 12C).
[Sticker type]
The sticker type sticker is a sticker of a type that is pasted on the basis of a blog article portion in which a unique tag (see FIG. 9) is described as described later and hides the blog article (see seal a3 in FIG. 13C). .

  As the sound data, for example, a sound format such as mp3, wave (WAV) is selected. This sound data is, for example, a sound effect that attracts the viewer's attention and is reproduced and played when a seal is selected. The sound format is not limited to the above, and any other sound format may be used as long as it is reproduced by the Flash (registered trademark) file reproduction function of the browser.

  In the CSS file, a setting of a display style of a general web page, a seal ID of each sticker, a URL of a sticker image corresponding thereto, and the like are described.

  In a file (JavaScript file) described in JavaScript, various processing functions, a seal ID, a URL of a sound file corresponding thereto, and the like are described.

The seal ID is an ID different from the seal SID, and is used to specify the type of seal and the type of sound related thereto.
<User terminal>
As shown in FIG. 1, a user terminal 2A, 2B, 2C includes a browser (browsing / editing means) (not shown) that can browse and edit web pages, a keyboard 6 and a mouse 8 as input means and operating means, It has a monitor (display unit) 7 for displaying a blog article and a blog article management screen, an RSS reader (not shown), a storage means (not shown), and the like.

  FIG. 1 simply shows two user terminals 2A and 2B using a personal computer and one user terminal 2C using a mobile phone, but actually there are a plurality of user terminals. Exists.

  Further, this RSS reader accesses the server 10 to acquire and analyze XML data for RSS distribution (hereinafter referred to as RSS file), and whether a blog article is newly created or whether an existing blog article is updated. Update information is acquired, and a part or all of this blog article is displayed on the monitor 7 of the user terminal, or the contents of the blog article are output to the user terminal by voice.

  The above-described browser is, for example, a web browser such as Internet Explorer (registered trademark), and is based on a Flash (registered trademark) file reproduction function, a communication function, an HTML parser function for analyzing HTML data, a sound data reproduction function, and HTML data. A hierarchical display function for hierarchically displaying images, text, or rectangles containing them, a program execution function for executing a program written in a predetermined language such as JavaScript, and the like.

  The hierarchical display function will be described in detail. For example, based on the z-index value specified in the above CSS file and the order of the tree of HTML elements for an HTML element, the image is superimposed on an image. This is a function for displaying, overlaying an image on text, or displaying an opaque rectangle in, for example, a single color (background color, etc.) on the text.

The browser has a display area for displaying a web page on the monitor 7, and coordinates are defined in the X direction and the Y direction with the upper left point of the web page (different from the display area) as the origin. ing.
<Server processing operations>
Processing operations that the server 10 has will be described below.
(Main processing operation)
The main processing operation is a processing operation that monitors the access from the user terminal, analyzes the URL that the user terminal is trying to access when accessed, and performs various operations described later from the analysis result Point.

  The main processing operation will be described below based on the flowchart shown in FIG.

  Referring to FIG. 2, in step S1, it is determined whether there is an access from the user terminal. If there is access and YES, the process proceeds to step S2. If there is no access and NO, the process returns to step S1.

  In step S2, the URL of which blog page the accessing user terminal is trying to access is analyzed. Also, here, from the URL analysis result, various data such as a user ID value inputted for login passed as an argument to the server program, values representing the following various requests, and the like are extracted.

  In step S3, it is determined whether user authentication is requested from the URL analysis result. If user authentication is required and the answer is YES, the process proceeds to user authentication in step S7. If user authentication is not requested and NO, the process proceeds to step S4.

  In step S4, it is determined whether user registration is requested from the URL analysis result. If user registration is requested and the answer is YES, the process proceeds to user registration in step S8. If user registration is not requested and the answer is NO, the process proceeds to step S5.

  In step S5, it is determined whether or not blog article editing is requested from the URL analysis result. If blog article editing is requested and YES, the process proceeds to step S9. If NO, the process proceeds to blog article browsing in step S6.

In step S9, it is determined whether or not the user terminal is in a login state. If the user terminal is in the logged-in state, the process proceeds to blog article editing in step S10. If the user terminal is NO in the login state, the process returns to step S1.
(User authentication)
In the user authentication in step S7, processing similar to that of a publicly known one is performed, and it is checked whether or not the user ID in the user database 5 matches the user PWD based on the user ID and user PWD input at the user terminal. If they match, the user terminal is in a login state. If they do not match, an error is displayed on the browser of the user terminal, and the process returns to step S1.
(user registration)
The user registration in step S8 performs the same processing as known ones. The HTML source data of the user new registration screen is transmitted to the user terminal, displayed on the browser, input at the user terminal, and transmitted from the user terminal. The user ID and the user PWD received are stored in the user database 5 and newly registered. Then, the process returns to step S1.
(Blog article creation / editing)
Referring to FIG. 3, in step S11, the corresponding blog title list is obtained from the URL analysis result in step S2, and the HTML source data of the blog article management screen created based on the title list is transmitted to the user terminal.

  The blog article management screen has, for example, titles of blog articles displayed in a hyperlinked state, a blog article new creation button, and the like, and is displayed on the monitor 7 (not shown).

  Hereinafter, a case where the user terminal 2A is connected to the network 1 will be described as an example.

  In step S12, the HTML source data of the blog article editing screen for editing the blog article selected on the blog article management screen or creating a new blog article is transmitted to the user terminal 2A. On this blog article editing screen, an article posting button, a text field for inputting and editing text, and a preview button are displayed on the monitor 7 (not shown).

  In step S13, it is determined whether or not a preview display of the blog article is requested from the user terminal 2A. If it is requested and YES, the process proceeds to preview display in step S14, and if NO, the process proceeds to step S16.

  In step S15 after the preview is displayed, it is determined whether there is a request to continue editing. If YES and YES, the process returns to step S12. If there is no request and NO, the process proceeds to step S16.

  In step S16, it is determined whether or not there is a write request from the user terminal 2A and there is write data for the blog article. If NO, return and return to step S1. If YES, the process proceeds to step S17.

In step S17, the blog article write data is stored in the message database 4.
(Preview display)
Referring to FIG. 4, in step S18, the article data for preview sent from user terminal 2A to server 10 is analyzed.

  In step S19, it is determined from this analysis result whether or not a unique tag (see FIG. 9) is described in the article data. If the unique tag is described and the answer is YES, the process proceeds to step S20. If NO, the unique tag is not described, the process proceeds to step S21.

  Step S20 replaces the unique tag with an HTML tag. For example, the original tags “<a: tape1>” and “</ a: tape1>” are converted into “<span class =“ tape1 ”>” and “</ span>”, respectively (see FIG. 9).

  In step S21, the article data is attached to the user terminal 2A with an HTML header, an HTML footer, or the like.

  In this HTML footer and HTML header, a function for obtaining a predetermined range for sticking a seal (hereinafter referred to as a seal display range), a processing function for removing a seal when a seal is selected, a seal is selected, and the seal is peeled off. Various processing functions for transmitting various data such as the seal SID of the seal and the cookie issued to the user terminal 2 </ b> A of the viewer are described. The URL of the CSS file is also described.

  These processing functions may be stored in the database 2 of the server 10 in a form described in an external file without being described in the HTML header or HTML footer, and may be always accessible.

  In step S22, it is determined whether there is a request for seal part data (seal image, sound data, etc.) from the user terminal 2A. If there is no request and the answer is NO, the process proceeds to step S15 in FIG. If YES and YES, the process proceeds to step S23.

In step S23, based on the request, the corresponding seal part data is transmitted to the user terminal 2A, and the process proceeds to step S15 in FIG.
(Blog article browsing)
Referring to FIG. 5, in step S24, corresponding article data is acquired from message database 4 from the URL analysis result of step S2.

  In step S25, the acquired article data is analyzed.

  In step S26, it is determined whether RSS distribution is requested from the URL analysis result in step S2. If YES, RSS distribution is requested, the process proceeds to step S27. When the RSS distribution is not requested, the process proceeds to step S31.

  In step S27, it is determined from the analysis result in step S25 whether or not there is a description of a unique tag (see FIG. 9) in the article data. If the unique tag is described and the answer is YES, the process proceeds to step S28. If the unique tag is not described and the answer is NO, the process proceeds to step S29.

  In step S28, the blog article part enclosed by the unique tag is replaced with alternative text (a character string representing a different meaning from the text part).

  For example, the part “<a: tape1> Morita-san </ a: tape1>” enclosed in the original tag is replaced with “<< Please come to see >>”. By this replacement, the information of the part (“Morita” in the above example) that the article creator tried to hide is not included in the delivered RSS file (see FIG. 17).

  In step S29, XML data (RSS file) for RSS distribution in which part or all of article data is embedded is created.

  In step S30, this RSS file is transmitted to the user terminal 2A, and the process returns to step S1.

  On the other hand, in step S31, it is determined from the analysis result in step S25 whether or not there is a description of a unique tag (see FIG. 9) described later in the article data. If there is a description of the unique tag, the process proceeds to step S32. If the unique tag is not described and the answer is NO, the process proceeds to step S33.

  In step S32, the description portion of the unique tag is converted into a general HTML tag, for example, a “<span>” tag.

  For example, the part “<a: tape1> Morita san </ a: tape1>” enclosed in the original tag is replaced with “<span class =” tape1 ”> Morita san </ span>”. In this way, the seal ID value (for example, “tape1”) corresponding to the type of the unique tag is described in the class value of the tag after conversion (see FIG. 9).

  In step S33, the article data is transmitted to the user terminal 2A with an HTML header and an HTML footer as described above so as to have an HTML file format.

  In step S34, it is determined whether there is a request for seal part data (seal image, sound data, etc.) from the user terminal 2A. If YES, the process proceeds to step S35. If the request is NO, the process returns and returns to step S1.

In step S35, the data of the corresponding seal part is transmitted to the user terminal 2A based on the request, and the process returns to return to step S1.
<Flow for creating and editing blog articles>
Referring to FIG. 6, in step S36, when an article creator who is not logged in enters the blog management screen, he / she inputs a user ID and a user PWD on the displayed login screen (not shown) and enters a login button (not shown). By clicking (shown), the user ID and the user PWD are transmitted from the user terminal 2A to the server 10, and the server 10 performs an authentication process.

  In step S37, when authenticated, the user terminal 2A enters a login state and the browser display screen changes to the blog management screen. If not authenticated, an error screen is displayed.

  In step S38, the article creator inputs and edits the content of the blog article in the edit text field of the blog article displayed on the blog article editing screen.

  When editing an existing blog article, for example, the article data is loaded into the edit text field by selecting the title of the blog article displayed in a list on the blog article management screen.

  When editing a sticker on a blog article, as shown in FIG. 9, FIG. 11 (A), FIG. 12 (A), and FIG. 13 (A), use a unique tag to describe the text you want to put the sticker on. To do. A description method for pasting and sticking a seal will be described later.

  For example, a tape-type sticker is described as "<a: tape1> Morita-san ... </ a: tape1>", and a box-type sticker is "<a: seal1> what ... ♪♪ ♪ </ a: seal1> ”, and sticker type stickers are described as“ <a: sticker1> ”(see FIG. 11 (A), FIG. 12 (A), and FIG. 13 (A)). ). Based on the description of the unique tag, a seal range (first non-display range) is set for the blog article.

  In step S39, when the editing of the blog article is completed, the article creator clicks a “preview button” (not shown) displayed on the blog management screen. By this click, the edited article data is transmitted to the server 10, and the server 10 performs a series of processes relating to the preview display in steps S18 to S23.

  In step S40, the user terminal 2A receives the HTML source data for preview transmitted from the server 10 (see FIGS. 11B, 12B, and 13B). If the “preview button” is not clicked, steps S39 and S40 are omitted.

  In step S41, based on the received HTML source data, the browser of the user terminal 2A displays how the edited blog article is actually displayed on its own blog in preview display (FIG. 11). (See (C), FIG. 12 (C), and FIG. 13 (C)).

  With this preview display, the article creator can actually click and select a sticker and try an operation such as peeling off the sticker (FIGS. 11D, 12D, and 13D). reference). Thereby, it is possible to confirm how the viewer is allowed to browse.

  In step S42, when the article creator determines that there is no problem in the state where the blog article edited by the article is displayed in a preview, the “article posting” button (not shown) on the blog article management screen is clicked.

In step S43, the edited content is transmitted as article data to the server 10, and the article data is stored in the message database 4 on the server 10 side. At this time, a sticker SID is given to each sticker included in the article data.
<Flow during browsing>
(Site browsing)
Hereinafter, a flow when a viewer browses a blog article with the user terminal 2 </ b> B using a browser will be described as an example with reference to FIG. 7.

  In step S <b> 44, the user terminal 2 </ b> B is connected to the server 10 via the network 1 by inputting the URL of the blog to be browsed by the browser on the browser. Then, the server 10 performs steps S24 to S33 of the above-described site browsing process, creates HTML source data, and transmits it to the user terminal 2B.

  In step S45, the user terminal 2B receives the HTML source data from the server 10.

  In step S46, the CSS file and the JavaScript file hyperlinked to the HTML source data are downloaded from the database 2, and the browser displays the blog page based on the received HTML source data, the CSS file, and the JavaScript file.

Prior to this display, the browser of the user terminal 2B analyzes the HTML tree of the received HTML source data. By this analysis, it is checked whether there is an instruction to attach a sticker, for example, “<span class =” tape1 ”> Morita-san </ span>”.
In some cases, the seal ID of the seal is acquired from the class value based on the processing function of the HTML header part or HTML footer part of the HTML source data.

  Here, when displaying the blog article, the browser of the user terminal 2B acquires the seal display range from the seal range set in the blog article by a method described later, and the seal display range is determined for each seal. A rectangle is displayed so that the blog article part in that range is not visible to the viewer.

  As a specific example, using the HTML element of “span”, according to the designation of z-index, the above rectangle such as an opaque layer is arranged above the display level of the blog article, and the blog in the seal range Cover the article.

  The reason for this is that since image data is generally larger in data size than text data, depending on the user terminal 2B, the speed of its communication line may be low, and download between both image data and text data is possible. The time difference increases. For this reason, the blog article portion that should be hidden is displayed at a point just before the seal image is displayed, and may be read by the viewer.

  For this reason, the process of displaying the single color rectangle in the seal display area and hiding the blog articles in the seal area prevents the text from being hidden and read by the viewer before the seal image is downloaded. To do.

  In step S47, the server 10 stores the cookie issued as information for specifying the user terminal 2B in the browser of the user terminal 2B.

  In step S48, the URL of the sticker image corresponding to the sticker ID is acquired from the CSS file downloaded in step S46. Also, the URL of the sound data corresponding to the seal ID is acquired from the downloaded JavaScript file.

  For example, when the seal ID of the class value is “tape1” as described above, the seal ID and the corresponding seal image URL such as “tape1./images/tape1.png” are included in the CSS file downloaded from the server 10. Is described, the browser of the user terminal 2B acquires the URL of the sticker image from this CSS file.

  In addition, since the JavaScript ID file describes the seal ID and the URL of the corresponding sound file such as “tape1 ./sounds/tape1.mp3”, the browser of the user terminal 2B uses the JavaScript file to store the sound file. Get the URL.

  The URL acquisition has been described by taking the tape type as an example, but the same applies to the box type and sticker type seals.

  In step S49, the browser of the user terminal 2B issues a request for a seal part to the server 10 based on the acquired URL, and downloads the seal image and related sound data from the server 10.

  In step S50, the browser of the user terminal 2B displays the sticker image downloaded in step S49 in the sticker display range (see FIGS. 11C, 12C, and 13C).

  For example, when “<span class =” tape1 ”> Morita-san </ span>” is described, the character “Morita-san” between “<span class =” tape1 ”>” and “</ span>” The blog post is covered with a tape-type sticker.

  In step S51, the viewer selects the sticker by clicking it with the mouse 8 or the like.

  In step S52, the browser of the user terminal 2B starts reproduction of the sound file downloaded in step S49 and decreases the width and width of the sticker, and finally deletes the sticker from the display area of the browser ( (See FIGS. 11D, 12D, and 13D). This process is performed based on a time function described by, for example, JavaScript. Thereby, the blog article portion hidden by the seal is displayed.

Here, the reader may be able to browse the blog article portion that has been hidden by moving the seal from the initial display position to a different position. For example, when the sticker is selected, the sticker may be skipped outside the display area of the browser or moved so as to drop to the lower part of the display area of the browser so as to be accumulated. Further, it may be a process of making it gradually transparent as time passes, or a process of replacing the seal image may be performed to display the blog article portion in the seal range. Also, the sound file need not be played back. In other words, it is only necessary that the blog article portion hidden by the seal is displayed and is readable.
When the process of updating and displaying the web page (new site browsing), this sticker is displayed again at the original display position, and the blog article portion is hidden and becomes unreadable.

  In step S53, the browser of the user terminal 2B transmits to the server 10 the blog article ID, the seal SID of the selected sticker, the cookie issued to the user terminal 2B, and the like. This process is performed, for example, by calling a processing function described in JavaScript when selecting a seal.

  As a specific example, as an argument of an ASP CGI program called by the server 10 side, “... Seal_sid = tape1_1 &...” Is added to the URL and passed to the server 10.

The server 10 creates time data when this data is received (for example, “200904030942131412”), specifies the storage area of the corresponding blog article in the message database 4 based on the blog article ID, and stores these data related to the selected seal. Information (a cookie issued to the user terminal 2B, a seal SID, etc.) and the time data are stored in the message database 4.
(Browse by RSS distribution)
Hereinafter, as an example, a flow when a viewer browses a blog article by RSS distribution by operating the user terminal 2C will be described with reference to FIG. It is assumed that the RSS reader URL of the user terminal 2C is registered with the URL for RSS distribution of the blog article site viewed by the viewer.

  In step S54, the user terminal 2C is connected to the server 10 by starting the RSS reader. The server 10 performs a series of RSS article distribution processing for RSS distribution in steps S24 to S30, and transmits an RSS file to the user terminal 2C.

  In step S55, the RSS reader of the user terminal 2C receives the RSS file.

  In step S56, the RSS reader presents the blog article to the user terminal 2C by causing the user terminal 2C to display a screen or output a voice based on the received RSS file.

Here, when the unique tag is replaced in the server 10, the replaced character is presented to the user of the user terminal 2C as a part of the blog article. (See FIG. 17).
<Acquisition method of seal display range>
A method of acquiring the seal display range from the seal range set in the blog article will be described with reference to the following sentence example and FIG.

Example 1: “That person is <span class =” tape1 ”> Morita-san </ span> !! I was surprised.”
As shown in FIG. 10A, when the part “Morita” is displayed in one line without a line feed, the upper left point p1 of the HTML element (in this case, the span element) including the part “Morita” , The XY coordinates (hereinafter referred to as XY coordinates) on the displayed page are acquired, and similarly, the XY coordinate information of the lower right point p2 of “n” is acquired. A rectangular range R1 having a line connecting the two points p1 and p2 as a diagonal line is a sticker display range.

  Depending on the environment such as browser type and display font size, as shown in FIG. 10 (B), when “Morita” extends over two or more lines, for example, “Morita” is a line break and “Mr. ”And the next line, the sticker display ranges R2a and R2b are acquired in the same manner as described above between two parts before and after the line feed of“ Mori ”and“ Tasan ”, that is, between points p3 and p4 and between points p5 and p6. Made. In the case of three or more rows, the seal display range is acquired in each row in the same manner as described above.

Example 2: “That person is <span class =” seal1 ”> Morita! </ Span> !!!”
Referring to Fig. 10 (C), in the case of a box-type sticker, the line in which the blog article part enclosed by sentence example 2 "<span class =" seal1 ">""</span>" is described is specified. (In this case, the second and third lines). The XY coordinates of the upper left point p7 in the second row and the lower right point p8 in the third row are respectively acquired, and a rectangular range R3 having a diagonal line connecting the two points p7 and p8 corresponds to the seal display range.

Example 3: “That person is <span class =” sticker1 ”></span> Morita !!”
In the case of the sticker type, the span element range R5 is obtained for the part enclosed by "<span class =" sticker1 ">" and "</ span>" in the same manner as the tape type seal, and the sticker is based on this range R5. A type of sticker is applied.

For example, processing is performed such as obtaining the point p9 that is the center of the range R5 and pasting this point concentrically with the center point of the seal image. In this case, since the seal display range is not particularly defined, it is substantially the range R4 occupied by the sticker type seal image. In the case of a sticker type sticker, since the sticker display range is not particularly defined, the process for displaying the above-described single color rectangle in the sticker display range is not performed.
<Overlaying>
With reference to FIG. 14, the sticking of the seal will be described below.
When the sticker is overlaid, as shown in FIG. 14 (A), the blog article entered in the edit text field of the blog article management screen is described so as to sandwich the range to be hidden with a unique tag. Then, the nested blog article portion is further nested with a unique tag.

  In the case of FIG. 14A, a seal range (first non-display range) is set by the description of “<a: tape2>” and “</ a: tape2>”, and “<a : tape1> ”and“ </ a: tape1> ”, another seal range (second non-display range) is set for the blog post.

  These unique tags are converted on the server 10 side as described above (see FIG. 14B). Then, the converted article data is transmitted to the user terminal and displayed on the browser of the user terminal (see FIG. 14C).

  At first glance, it appears that only the tape-type seal a4 is displayed, but when this seal a4 is selected and removed with the mouse 8 or the like, the tape-type seal a5 hidden underneath is displayed (FIG. 14 (D)).

  Furthermore, if this seal | sticker a5 is selected and peeled off, the blog article part which was hidden twice will be displayed (refer FIG.14 (E)).

  In this way, the seal can be overlaid by nesting the unique tag.

  The number of seals to be overlaid is not limited to two, and three or more seals can be overlaid by repeating the enclosing of the unique tag. At that time, as shown in the above example, the more unique tags located inside the enclosure, the corresponding seals are arranged in the back (lower layers) on the browser.

Hereinafter, the operation and effect of the blog system 100 of the embodiment will be described.
(1) The information that the article creator wants to hide can be partially hidden by the seal.
For example, an article creator can hide information that a person does not want to know, such as the end of a story, using a seal.

  Until now, the article creator has written the information he wants to hide in the same color as the background color, and the viewer who wants to know browses it in a readable state by selecting and inverting it by dragging the part with the mouse 8, etc. Or, only the viewer who wants to know by describing the information in the lower part of the page that does not fit in the display area of the browser scrolled the page and displayed the information in the display area, Such a troublesome operation is not forced on the viewer.

  In addition, since the viewer can peel off the seal by a simple selection operation such as a click and display the corresponding part, the information can be easily obtained.

(2) Since a part of the blog article is hidden with a seal and the reader is peeled off, the reader's attention to information hidden by the seal can be increased.
Since it is accompanied by the main action of letting the viewer choose to click on the sticker and peel off the sticker, the blog post text is displayed more boldly and decorative characters such as colored letters. The attention level of the person can be increased.

(3) By using a plurality of seals, it becomes possible to publish a document to be disclosed in stages within the same page.
For example, as shown in FIG. 18, by hiding the corresponding part with an individual sticker for each stage that the creator wants to make public, and allowing the viewer to peel it off one by one and read it within the same page Information can be disclosed in stages (see FIGS. 18A to 18D).

  For this reason, since it is not necessary to divide and describe the text to be disclosed in different web pages as in the past and to publish the information in stages by hyperlinking each, the viewer has to obtain the next level of information. There is no need to open a new page.

For this reason, problems such as a decrease in processing speed due to newly opening a web page and occurrence of a waiting time each time a page is read do not occur.
(Overlaying)

(4) By pasting a plurality of stickers on top of each other, it becomes possible to publish the text to be released in a stepwise manner on the same page.
For example, if the text of a blog post is merged into the page with the same color as the background color of the page, and the viewer selects and inverts this text to view it in a readable state, it is displayed / not displayed for the disclosure of information. Although only 0/1 switching is possible, by pasting a plurality of seals with the system of this embodiment, there will be a further seal under the seal in a single sentence, and step by step for each layer. A sentence is displayed.

  This makes it possible to disclose information little by little and allows the viewer himself to select how much information is to be disclosed.

  Moreover, in the above-mentioned conventional thing, since the text of the blog article is the same color as the background color of the web page and is blended into the web page, it is very easy for the viewer to specify where the information he wants to know is written. However, in the system of the present embodiment, such a problem does not occur because a part of the blog article is hidden by the seal and the part to which the seal is attached can be identified immediately. This is a characteristic of the present system that is common even when the overlaying is not performed.

In the example of staging by overlapping bonding shown in FIG. 15, only the box-type seal a6 is visible, but actually, the tape-type seal a7 is pasted on the back.
By sticking and hiding the sticker a6, a viewer who does not want to know the synopsis does not need to know the contents.

  In this case, a viewer who wants to know the outline of the story turns the seal a6 and browses the outline in a readable state. Furthermore, since the seal a7 is pasted on the “identity” portion in a state where the seal is turned over, the viewer who wants to know the “identity” only needs to peel off the seal a7 and read the seal a7. If you don't peel it off.

In addition, by adding a number of sheets, it is difficult for the viewer to select the sticker many times and the text will not be displayed. Enables a new production method for information disclosure.
For example, as shown in FIGS. 16A to 16D, as a new production method by overlapping, it is possible to turn the three stickers a8, a9, a10 so that the contents can be read.

(Actions and effects on RSS distribution / search robot patrol)
(5) Since the RSS file distributed to the user terminal includes a blog article, the contents of the blog article will be released if the RSS file is distributed as it is. In order to perform RSS distribution after replacing the information with a character string of another information (for example, text “Please come to see”), the blog article part in which the article creator set the seal range is distributed It is not included in the RSS file. For this reason, it is not displayed by the RSS reader of a user terminal.

  Even if the RSS file is acquired by the search robot, it is replaced with a character string of another information, so that the blog article portion in the seal range is not released.

  Therefore, information cannot be obtained unless a visitor actually visits the page of the blog article and removes the seal. It is possible to stage information disclosure in the sense that information is only disclosed to viewers who have actually visited the page.

  In addition, since the information cannot be obtained unless the blog article is actually browsed on the site, it is possible to create an opportunity to prompt the viewer to access the page (see FIG. 17).

Furthermore, when outputting HTML source data including article data to a search robot that patrols a website, the blog article portion in which the seal range is set may be replaced like character replacement at the time of RSS distribution. In this way, the blog article portion in which the seal range is set is not acquired by the search robot.
(6) You can find out who is sure to see the contents hidden by the sticker.

  Even with the conventional access log analysis, the visitor's site visit record can be taken, but even if the visitor visits the site for a moment, this access log remains, so it is not enough to judge whether the viewer really read the contents of the page It is.

  However, since the system of this embodiment involves the act of removing the sticker when browsing a blog article, the content obtained by it is easy to remain in the memory of the viewer, not just visiting the page, but there being there. Can be considered as confirmed information.

  At the same time as the operation of removing the seal, information about the viewer (Cookie) and the seal SID for specifying the selected seal are transmitted to the server 10, and the server 10 receives this data, By creating the time data and storing the received data and the time data in the message database 4 as a browsing log and confirming the browsing log, it is possible to know who has surely seen the contents there.

  For example, the article creator can hide the important information that the reader wants to know in particular with a seal, and by examining the browsing log of the viewer who removed the seal, it can know who viewed the important information.

  As mentioned above, although it demonstrated based on the Example concerning this invention, as for a concrete structure, unless it deviates from the summary of the invention which concerns on each claim of a claim, it is not restricted to this Example, Design changes and additions are allowed.

  For example, a blog system that can perform the editing without user registration and user authentication may be used. In addition, the web page data including the shared article in which the seal range is set is stored in the server 10 and can be browsed by the browser via the network 1 regardless of the blog system.

In this case, as described above, when the viewer browses the site, the shared article in the seal range is hidden, and the seal can be peeled off by the viewer.
Various processes in the blog system 100 are not limited to those described above. For example, all processing related to the display of the blog article may be performed by Flash or the like.

  Further, in this embodiment, when the server 10 is accessed for the purpose of browsing from the user terminal, the server 10 converts the unique tag in the article data read from the message database 4 in order to create the RSS file and the HTML source data. However, this conversion may be done before saving the blog post. In this case, when the unique tag is converted, an RSS file and article data are created and stored in the message database 4.

  Further, the process of converting the unique tag for preview display need not be transmitted to the server 10 as described above. For example, it may be performed on the user terminal using a function described in JavaScript, or may be performed using Flash or the like. Further, the article data edited without displaying the preview may be stored in the message database 4 as it is after being converted on the server 10 side.

  In this example, the seal is selected and the blog article portion that is hidden by moving from the original position is displayed, and then the web page on which the seal was displayed is updated. When displayed, the seal that has been selected and disappeared or moved is displayed again at the original position, but once selected, this seal is selected based on the browsing log that is sent to the server 10. For the sticker, output from the server 10 may be prohibited, and the sticker may not be displayed again even if it is updated.

  Further, based on the cookie stored in the message database 4, the prohibition of the output may be limited only to the user terminal of the viewer who has selected the seal.

  The design of the sticker image is not limited to a ready-made one, but a character input by the article creator on the user terminal may be transmitted to the server 10 side, and the sticker image may be dynamically created by a program on the server 10 side. In this way, the comment intended by the article creator can be formed on the seal image.

  The present invention can be applied to a learning site for educational institutions. As an example, the English word and its Japanese meaning are written so as to be adjacent to each other, and a sticker is put on the written part of the English word. The viewer then removes the seal.

  According to this, it is possible to confirm the answer by peeling off the seal and to accompany the operation of peeling off the seal, so that the hidden content easily remains in the memory of the viewer.

  In addition, it can be used as an auxiliary tool for studying, such as peeling off the seal each time a student answers, and matching the answers. When removing the seal, the pronunciation of the English word may be played as a sound, or the sound related to the answer may be played as well as the pronunciation of the English word.

1 Network 2 Database 2A, 2B Personal computer (user terminal)
2C mobile phone (user terminal)
3 Seal parts database 4 Message database 5 Registered user information database (user database)
6 Keyboard (input means, operation means)
7 Monitor (display section)
8 Mouse (operation means)
10 server (seal output means, shared article output means)
100 Blog System a1 to a10 Seal

Claims (5)

A network including wireless and wired communication lines; a plurality of user terminals connected to the network; a server connected to the network; and a database connected to the server and storing shared articles in a readable and writable manner. Each user terminal is connected to the server via the network and has a browsing / editing unit for browsing or editing the shared article, a display unit for displaying the shared article, and the browsing / editing unit. Operating means for operating,
The server includes a shared article output unit that outputs a shared article in the database, and the shared article output unit outputs a shared article from the database by browsing / editing by an operation unit of any of the plurality of user terminals. In the shared article publishing system that reads and displays the shared article on the display unit of the user terminal,
The server includes a seal output unit that outputs a first seal that can be displayed on the display unit of each user terminal and hides a shared article,
When the first non-display range is set to the shared article displayed on the display unit by the operation means of the user terminal,
Each time the shared article is read from the database, the seal output means of the server outputs a first seal that hides the shared article in the set first non-display range,
When the user terminal that performs browsing or editing receives the first sticker output from the sticker output means of the server, the browsing / editing means of the user terminal reads the shared article in the set first non-display range. Covered with the first seal and displayed on the display unit,
When this first sticker is selected by operating the operation means of each user terminal, the shared article part covered with this first sticker is displayed ,
When the first seal is selected by operating the operation means of the user terminal, information on the selected first seal and the user terminal is transmitted to the server, and the server receives the information and receives the information. A shared article publishing system that prohibits the output of a seal once selected for a terminal . When a plurality of different first non-display ranges are set for the shared article in the editing, the server seal output means outputs a plurality of first seals that hide the plurality of first non-display ranges, and The shared article publishing system according to claim 1, wherein the editing means covers each first non-display area by the plurality of first seals. When a second non-display range is set within the first non-display range by the editing,
The server seal output means outputs a first seal that covers the first non-display range and a second seal that covers the second non-display range;
The shared article publishing system according to claim 1, wherein the browsing / editing unit displays the first seal on the second seal. The user terminal has an RSS reader for browsing an RSS file in which the shared article is described,
When the user terminal connects to the server to acquire the RSS file, the shared article output means of the server reads the shared article from the database and also converts the shared article portion within the first non-display range to the shared article. Create an RSS file including the shared article by replacing with another character string having a different meaning from the part, and output the RSS file.
3. The shared article release according to claim 1, wherein the user terminal receives the RSS file and displays a shared article of the RSS file on the display unit or outputs the shared article as a voice. 4. system. When the user terminal is connected to the server in order to view a shared article in the database, the server includes information for specifying the user terminal and each of the first and second information set in the shared article. Information for identifying each seal corresponding to the non-display range is created in the browsing / editing means of the user terminal,
When the first seal or the second seal is selected by the operation of the operation means, the browsing / editing means transmits at least the two pieces of information to the server, and the server receives these pieces of information to receive the database. The shared article publishing system according to any one of claims 1 to 4, wherein the shared article publishing system according to claim 1 is stored.

Images