JP6572249B2 - Content conversion apparatus, content conversion method, program, and recording medium - Google Patents

Description

  The present invention relates to a technique for receiving a request from a client such as a browser, converting content such as an existing Web site, and sending it as a response.

  The attributes of users browsing web content, such as age, native language, presence / absence of disabilities, and the terminals used, are diversifying. For example, in the past, browsing from personal computer (PC) browsers has been the mainstream for terminals, but the spread of smartphones and the appearance of tablets, and recently, signage has attracted attention. There is a need for multi-device Web content that can be viewed in an appropriate layout by switching user agents (UAs).

  Web content consists of HTML (Hypertext Markup Language) that defines elements and structures, and CSS (Cascading Style Sheets) files that define styles such as element colors, and service providers can use existing websites. Multi-device Web content is realized by preparing HTML and CSS separately for each user agent type (hereinafter referred to as an existing site).

  However, the cost of developing and designing such Web content and the cost of managing each content increase in proportion to the type of user agent (Non-Patent Document 1). There is a method called responsive web design for this problem. In responsive web design, it is possible to display appropriate Web content by preparing multiple CSS for one HTML and switching the CSS based on the width size of the browser to be accessed (Non-patent Document 2). Further, a method of combining these technologies and calling a plurality of CSSs from one HTML by user agent switching (hereinafter, CSS switching by UA) can be easily constructed to some extent (Non-patent Document 3).

  As described above, in CSS switching by UA, by creating a CSS for each user attribute by switching the user agent for each target user attribute, and introducing a system that the user can select arbitrarily, users such as color weakness Can provide easy-to-read web content. Also, users with different languages can be handled by using existing APIs such as Microsoft translation API and google translation API. By combining these, Web contents can be displayed appropriately according to user attributes.

http://www.hp-stylelink.com/news/2013/07/20130716.php https://en.wikipedia.org/wiki/%E3%83%AC%E3%82%B9%E3%83%9D%E3%83%B3%E3%82%B7%E3%83%96%E3 % 82% A6% E3% 82% A7% E3% 83% 96% E3% 83% 87% E3% 82% B6% E3% 82% A4% E3% 83% B3 http://www.hp-stylelink.com/news/2014/05/20140516.php

  However, if an existing website creator creates CSS according to all user attributes, the cost of building the website increases according to the user attributes, so there is a problem that the content creation cost is very high. It was.

  In addition, to switch existing Web sites, it is necessary to improve the Web system that has been operated in the past, and it is necessary to worry about degration. In addition, there is a problem that other than the website creator cannot handle the user attributes of the existing website.

  In view of the above-described problems, an object of the present invention is to realize site display corresponding to various user attributes while operating an existing system without creating CSS according to all user attributes.

  In order to solve the above-described problem, according to one aspect of the present invention, a receiving unit that receives a conversion request and a terminal type together with an access request to a site, and conversion applicability indicating whether conversion of each element in the display information of the site is applicable A conversion unit that determines a conversion target element and a conversion method based on information and the conversion request, converts the determined conversion target element according to the corresponding conversion method, and a transmission unit that transmits display information after conversion The present invention relates to a content conversion apparatus having

  According to the present invention, since it is not necessary to create CSS for an existing Web site, it is possible to display a site for each user while operating an existing system. In addition, since there is no need to create CSS, the construction cost of content conversion can be reduced.

FIG. 1 is a block diagram showing a configuration of a communication system according to an embodiment of the present invention. FIG. 2 is a flowchart showing content conversion processing according to an embodiment of the present invention. FIG. 3 is a flowchart showing content conversion processing according to an embodiment of the present invention. FIG. 4 is a flowchart showing content conversion processing according to an embodiment of the present invention. FIG. 5 is a diagram illustrating a conversion API rule according to an embodiment of the present invention. FIG. 6 is a diagram illustrating an input screen according to an embodiment of the present invention. FIG. 7 is a diagram illustrating an input screen according to an embodiment of the present invention. FIG. 8 is a diagram showing element-specific display definitions according to an embodiment of the present invention. FIG. 9 is a diagram showing an element-specific conversion API definition according to an embodiment of the present invention. FIG. 10 is a diagram illustrating an element-specific API application rule according to an embodiment of the present invention. FIG. 11 is a diagram illustrating an element extraction rule according to an embodiment of the present invention. FIG. 12 is a diagram illustrating a target existing site according to an embodiment of the present invention. FIG. 13 is a diagram illustrating an acquired image according to an embodiment of the present invention. FIG. 14 is a diagram illustrating an existing site to be converted according to an embodiment of the present invention. FIG. 15 is a diagram illustrating an input screen according to an embodiment of the present invention. FIG. 16 is a diagram illustrating an existing site to be converted according to an embodiment of the present invention. FIG. 17 is a diagram illustrating an input screen according to an embodiment of the present invention. FIG. 18 is a diagram illustrating an existing site to be converted according to an embodiment of the present invention.

  Hereinafter, the content conversion apparatus of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a system configuration of a content conversion apparatus according to the present invention. As shown in FIG. 1, the content conversion apparatus 100 includes a receiving unit 101, a template acquisition unit 102, an element-specific application API determination unit 103, an element extraction unit 104, a Web content element extraction rule acquisition unit 105, a template storage unit 106, An element extraction rule storage unit 109, an element-specific conversion unit 110, a display shaping unit 111, and a transmission unit 112 are included. The template storage unit 106 includes an element-specific display definition unit 107 and an element-specific conversion API definition unit 108.

  In addition, the content conversion apparatus 100 includes a browser 201 on a user terminal 200 such as a personal computer (PC), a tablet, and a smartphone, an existing site 300 on a Web server, a conversion API # 1 (301), and a conversion API # 2 via a network. (302) and conversion API # 3 (303). The browser 201 receives and displays the existing site 300 converted by the content conversion apparatus 100.

  In the following embodiments, the conversion API # 1 (301) will be described as a translation (English) function, the conversion API # 2 (302) as a supplementary explanation function, and the conversion API # 3 (303) as an API having a color arrangement correction function. . Although there are three types of conversion APIs specified in the figures and examples, the number of APIs is actually not limited, and communication with many APIs is performed.

  The operation of the content conversion apparatus 100 of the present invention will be described with reference to FIGS.

Example 1
In step S101 in FIG. 2, the user inputs a site URL from the input screen 1 shown in FIG. In FIG. 6, http: //www.hogehoge.yyy.z is input as the URL of the Web site to be converted. When the user inputs the URL in FIG. 6 and presses the “Next” button, the screen of FIG. 7 (input screen 2) is displayed. Next, the user selects a user attribute and a template type from the input screen shown in FIG. 7, and presses the “Send” button. As the user attributes displayed on the input screen 2, an API (Application Programming Interface) that can be used is determined from the site URL information input on the input screen 1, and the user attributes corresponding to the API are displayed.

  In FIG. 7, the attributes of translation (English) are executed, supplementary explanation is executed, and color arrangement correction is no conversion are selected as attributes of translation. Hereinafter, the user attribute value is described as the user attribute “API function”. “API function” represents the type of conversion API, and corresponds to conversion API # 1 (301), conversion API # 2 (302), conversion API # 3 (303), etc. in FIG. Specifically, it is a “translation (English)” API that translates into English, a “supplemental explanation” API that automatically generates and adds supplementary explanations, or “color scheme correction” that corrects color schemes for people with color weakness API etc.

  The value of the user attribute indicates whether to execute these APIs. “O” indicates that the conversion function of the conversion API is used for conversion and display. “X” represents non-display. “-” Indicates that the received information is output and displayed without being converted by the conversion API.

  For example, when the API function is “translation (English)” and the value of the user attribute is “◯” indicating execution, the user attribute value of the user attribute “translation (English)” is “◯”. When the user designates as shown in FIG. 7, the three user attribute values (user attribute “translation (English)”, user attribute “supplementary explanation”, user attribute “color arrangement correction”) are respectively “O”, “O”, and “−”. These values are referred to as U-1, U-2, U-3 for the sake of explanation. That is, U-1 = user attribute “translation (English)” = ◯, U-2 = user attribute “supplementary explanation” = ◯, U-3 = user attribute “color arrangement correction” = −.

  Even without operating the input screen 2 in FIG. 7, user attribute values may be stored in advance in the terminal 200 on which the browser 201 is installed. In that case, the site URL and the user attribute value may be sent to the content conversion apparatus 100 simply by operating the input screen 1 of FIG.

  Further, “PC1” is selected as the template type as shown in FIG. The value of the template type is a value as shown in FIG. 7, and can take PC1, PC2, tablet 1, smartphone 1, signage 1, and the like. These values represent templates corresponding to the terminal 200, such as PC1, PC2, tablet, and smartphone. There are multiple PCs, PC1 and PC2, which can be selected from multiple templates because the screen size and resolution are different among PC terminals. In this embodiment, since PC1 is selected as the template, the template type (PC1) is set. If this template type value is referred to as T-1 for explanation, T-1 = PC1.

  By pressing the transmission button, the URL of the site to be converted, the user attribute selected by the user, and the template type are transmitted to the receiving unit 101 of the content conversion apparatus 100. In this embodiment, user attributes are always specified, but there may be settings that are not specified. As shown in FIG. 7, since three user attribute values (U-1, U-2, U-3) and a template type value (T-1) are designated here, these are content conversion devices. It is transmitted to 100 receiving units 101.

  In step S102, the receiving unit 101 of the content conversion apparatus 100 receives a site URL (http: //www.hogehoge.yyy.z) (hereinafter referred to as URL-1) transmitted from the browser 201, and three user attribute values. (U-1, U-2, U-3) and the template type value (T-1) are received.

  In step S103, the reception unit 101 transmits the received template type value (T-1) to the template acquisition unit 102.

  In step S104, the reception unit 101 transmits three user attribute values (U-1, U-2, U-3) to the element-specific application API determination unit 103.

  In step S105, the reception unit 101 transmits a site URL (URL-1) to the element extraction unit 104.

  In step S106, the reception unit 101 transmits the site URL (URL-1) and the template type value (T-1) to the Web content element extraction rule acquisition unit 105.

  In step S107, the template acquisition unit 102 receives the template type value (T-1) transmitted from the reception unit 101.

  In step S108, the template acquisition unit 102 uses the template type value (T-1) to display the element-specific display definition (T-1) corresponding to the template type value (T-1) from the element-based display definition unit 107 of the template storage unit 106. -1) is acquired from the element-specific conversion API definition unit 108 for each element-specific conversion API definition (T-1) corresponding to the template type value (T-1). In the element-specific display definition (T-1), as shown in FIG. 8, information defining the layout of each element such as “product overview”, “image”, and “product name” is described. Element-specific display definitions and element-specific conversion API definitions corresponding to various template type values are registered in the template storage unit 106 in advance.

  As shown in FIG. 8, the element-specific display definition corresponding to T-1 is read. In the element-specific display definition corresponding to T-1, the elements to be displayed and the layout are specified. For example, as shown in FIG. 8, an element “product overview”, an element “image”, and an element “product name” are arranged in order from the top, and each of them is specified to be displayed in the center. ing.

  However, there is no need for element-specific display definitions. In that case, the element-specific display definition of the existing site 300 is used. The element-specific conversion API definition corresponding to the element-specific display definition of the existing site 300 is registered in the template storage unit 106 in advance.

  In the element-specific conversion API definition (T-1), as shown in FIG. 9, information indicating whether each API is applicable to each element whose layout is defined in FIG. 8 is described.

  In step S109, the template acquisition unit 102 transmits the element-specific display definition (T-1) of FIG.

  In step S110, the template acquisition unit 102 transmits the element-specific conversion API definition (T-1) of FIG. 9 to the element-specific application API determination unit 103.

  Next, in step S111, the element-specific application API determination unit 103 transmits the three user attribute values (U-1, U-2, U-3) transmitted from the reception unit 101 and the template acquisition unit 102. The element-specific conversion API definition (T-1) in FIG. 9 is received.

  In step S112, the element-specific application API determination unit 103 converts the element-specific conversion API definition (T-1) in FIG. 9 into three user attribute values (U-1, U-2) based on the conversion API rule in FIG. , U-3), and create element-specific API application rules. “Any” described in the conversion API rule of FIG. 5 means all patterns of ○, ×, and −. In this embodiment, the “color arrangement correction” API of the image is converted from ○ to − according to rule 3.

  In step S113, the element-specific application API determination unit 103 transmits the created element-specific API application rule of FIG. 10 to the element-specific conversion unit 110.

  In step S114, the Web content element extraction rule acquisition unit 105 receives the site URL (URL-1) and the template type value (T-1) transmitted from the reception unit 101.

  In step S115, the Web content element extraction rule acquisition unit 105 acquires the element extraction rule of FIG. 11B using the site URL (URL-1) and the template type value (T-1). Which element extraction rule is to be acquired based on the site URL and the template type is stored in the Web content element extraction rule acquisition unit 105 in advance. For example, a correspondence table as shown in FIG. FIG. 11A shows that the element extraction rule 11 corresponds to URL-1 and PC1.

  FIG. 11B shows the contents of the element extraction rule 11, which describes the XPath of the element on the existing site and information on which variable of the element-specific display definition unit 107 stores the extracted element.

  In step S116, the Web content element extraction rule acquisition unit 105 transmits the acquired element extraction rule in FIG. 11B to the element extraction unit 104.

  FIG. 11B shows that the contents of an element whose XPath is / html / body / div / div / p are stored in variables “product overview” and “product name”. In addition, the contents of the element whose XPath is / html / body / div / div / img are stored in a variable “image”.

  In step S117, the element extraction unit 104 receives the site URL (URL-1) transmitted from the reception unit 101 and the element extraction rule of FIG. 11B transmitted from the Web content element extraction rule acquisition unit 105. .

  In step S118, the element extraction unit 104 uses the acquired site URL (URL-1) and the element extraction rule shown in FIG. 11B to extract Web content elements from the existing site 300 shown in FIG. "Aji no Namero" as the image, the image shown in FIG. 13 as the image, and "Aji no Namero" as the product name. These are called Web content elements.

  In step S119, the element extraction unit 104 transmits the acquired Web content element to the element-specific conversion unit 110.

  In step S120, the element-by-element conversion unit 110 performs the element-by-element API application rule of FIG. 10 transmitted from the element-by-element application API determination unit 103, the Web content element transmitted from the element extraction unit 104, and the product overview ), An image (FIG. 13), and a product name (Aji no Lick). Here, for the sake of explanation, the content of the product overview (Aji no Namenro) will be referred to as product overview 1, the content of the image (FIG. 13) will be referred to as image 1, and the content of the product name (Ajino Namero) will be referred to as product name 1. .

  In step S121, the element-by-element conversion unit 110 transmits the Web content element to the conversion API # 1 (301).

  In step S122, the conversion API # 1 (301) receives the Web content element, the product outline 1 and the product name 1 transmitted from the element-specific conversion unit 110.

  In step S123, the conversion API # 1 (301) converts the Web content element, the product outline 1 and the product name 1 according to the element-specific API application rule of FIG. Both Product Overview 1 and Product Name 1 are “Aji no Nametsuro”, but this is translated into English by conversion API # 1 (301) and becomes “A mackerel namero”. This is called product overview 2 and product name 2. Image 1 is not converted.

  In step S124, the conversion API # 1 (301) transmits the Web content element, the product outline 2 and the image 1, and the product name 2 to the conversion API # 2 (302).

  In step S125, the conversion API # 2 (302) receives the Web content element, the product outline 2 and the image 1, and the product name 2 transmitted from the conversion API # 1 (301).

  In step S126, the conversion API # 2 (302) converts the Web content element according to the element-specific API application rule of FIG. That is, product summary 2 (A mackerel namero) is converted to product summary 3 (A traditional food of Chiba pref. It's like 'tartar for appetizers'.).

  Here, the same output can be obtained regardless of the order of the conversion API # 1 (301) and the conversion API # 2 (302). That is, if the conversion source is English, it is converted into English supplementary explanation. You can also translate Japanese into supplementary explanations and then translate them into English, both of which produce the same output. Image 1 and product name 2 are not converted.

  In step S127, the conversion API # 2 (302) transmits the Web content element, the product outline 3 and the image 1, and the product name 2 to the conversion API # 3 (303).

  In step S128, the conversion API # 3 (303) receives the Web content element, the product outline 3 and the image 1, and the product name 2 transmitted from the conversion API # 2 (302).

  In step S129, the conversion API # 3 (303) converts the Web content element according to the element-specific API application rule of FIG. However, since no conversion of “−” is instructed for each element, the product outline 3, the image 1, and the product name 2 are output as they are without being converted.

  In step S130, the conversion API # 3 (303) transmits the Web content element, the product outline 3 and the image 1, and the product name 2 to the element-specific conversion unit 110.

  In step S131, the element-by-element conversion unit 110 converts the converted Web content element transmitted from the conversion API # 3 (303), product overview 3 (A traditional food of Chiba pref. It's like 'tartar for appetizers'.), Image 1 (FIG. 13) and product name 2 (A mackerel namero) are received.

  In step S132, the element conversion unit 110 transmits the converted Web content element, the product outline 3 and the image 1, and the product name 2 to the display shaping unit 111.

  In step S133, the display shaping unit 111 converts the element-specific display definition unit 107 in FIG. 8 transmitted from the template acquisition unit 102 and the converted Web content element, product outline 3, image 1 transmitted from the element-by-element conversion unit 110. , Receive product name 2.

  In step S134, the display shaping unit 111 inserts the converted Web content element, the product outline 3, the image 1, and the product name 2 into each element defined in the element-specific display definition in FIG. Generated web content

  In step S135, the display shaping unit 111 transmits the converted Web content in FIG.

  In step S136, the transmission unit 112 receives the converted Web content in FIG. 14 from the display shaping unit 111.

  In step S137, the transmission unit 112 transmits the converted Web content in FIG. The converted web content viewed by the user looks like FIG.

  Here, we explained an example in which an existing Japanese website was translated into English and supplementary information was added. If there are multiple translation APIs whose translation APIs are "Translation (English)", "Translation (Chinese)", and "Translation (Korean)", you can specify as many user attribute values by using them. A national language can also be written.

(Example 2)
In the second embodiment, a case where the user attribute is different from that of the first embodiment will be described. The user attribute value is ○. A site URL similar to that in the first embodiment is input, user attributes and template types are selected as shown in FIG. 15, and the “Send” button is pressed. In this case, the three user attribute values (user attribute “translation (English)”, user attribute “supplementary explanation”, user attribute “color arrangement correction”) are −, ×, and ◯, respectively.

  Since the subsequent processing is the same as in the first embodiment, it is omitted.

  In step S 112, the “color correction” API of the image is converted from ○ to − according to rule 3. The “translation (English)” API of the product summary is converted from ○ to − by rule 3. The “supplemental explanation” API in the product overview is converted from ○ to × by rule 2. The “translation (English)” API of the product name is converted from ○ to − according to rule 3.

  As a result, the converted Web content finally obtained by the user after obtaining the element-specific API application rules looks as shown in FIG.

(Example 3)
In the third embodiment, a case where no user attribute is selected will be described. The user attribute value is ○. A site URL similar to that in the first embodiment is input, user attributes and template types are selected as shown in FIG. 17, and the “Send” button is pressed. In this case, three user attribute values (user attribute “translation (English)”, user attribute “supplementary explanation”, user attribute “color scheme correction”) are not specified. Therefore, an initial value set in advance for each API is substituted. In this embodiment, the user attribute “translation (English)”, the user attribute “supplementary explanation”, and the user attribute “color arrangement correction” are −, ×, and −, respectively.

  Since the subsequent processing is the same as in the first embodiment, it is omitted.

  In step S 112, the “color correction” API of the image is converted from ○ to − according to rule 3. The “translation (English)” API of the product summary is converted from ○ to − by rule 3. The “supplemental explanation” API in the product overview is converted from ○ to × by rule 2. The “translation (English)” API of the product name is converted from ○ to − according to rule 3.

  As a result, the converted Web content that the user finally obtains by obtaining the element-specific API application rule looks like FIG.

  Note that the content conversion device 100 may be configured by hardware resources such as a drive device, an auxiliary storage device, a memory device, a processor, an interface device, and a communication device that are interconnected via a bus. Various computer programs including programs for realizing various functions and processes in the content conversion apparatus 100 may be provided by a recording medium such as a CD-ROM (Compact Disk-Read Only Memory), a DVD (Digital Versatile Disk), or a flash memory. Good. When the recording medium storing the program is set in the drive device, the program is installed from the recording medium to the auxiliary storage device via the drive device. However, it is not always necessary to install the program using a recording medium, and the program may be downloaded from any external device via a network or the like. The auxiliary storage device stores the installed program and also stores necessary files and data. The memory device reads and stores the program and data from the auxiliary storage device when there is an instruction to start the program. The processor executes various functions and processes of the content conversion apparatus 100 according to various data such as a program stored in the memory device and parameters necessary for executing the program. The interface device is used as a communication interface for connecting to a network or an external device. The communication device executes various communication processes for communicating with a network such as the Internet. However, the content conversion apparatus 100 is not limited to the hardware configuration described above, and may be realized by any other appropriate hardware configuration.

  The user terminal 200 may be various information processing apparatuses having communication functions such as a personal computer (PC), a smartphone, a tablet, and a television, and is connected to the site 300 via the content conversion apparatus 100.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment mentioned above, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

DESCRIPTION OF SYMBOLS 100 Content conversion apparatus 101 Reception part 102 Template acquisition part 103 Element application API determination part 104 Element extraction part 105 Web content element extraction rule acquisition part 106 Template storage part 107 Element display definition part 108 Element conversion API definition part 109 Element extraction Rule accumulation unit 110 Element-specific conversion unit 111 Display shaping unit 112 Transmission unit 200 User terminal 201 Browser 300 Existing sites 301 to 303 Conversion API

Claims (5)

A receiving means for receiving a conversion request based on a user attribute and a template type together with an access request to the site;
Conversion applicability information indicating conversion applicability of the elements in the display information of the site, converting API rules, and based on the conversion request, the conversion target element, a conversion method to be applied to each of the converted element conversion Converting means for determining an API and converting the determined conversion target element according to the corresponding conversion method;
A transmission means for transmitting the display information after conversion;
A content conversion device comprising :
The user attributes include items for translation, supplementary explanation and color correction,
The receiving means receives a conversion request indicating execution, no conversion or non-display specified by the user for each item of the user attribute,
The template type indicates a template type that is set in plural for each of a plurality of predetermined user terminal types,
The receiving means receives a template type selected by the user;
The conversion applicability information indicates whether the conversion API can be applied to each element,
The conversion API rule has items of the template type and the user attribute,
The conversion API rule is:
If the value of the user attribute received by the receiving means indicates no conversion, the content of the element is displayed in the template corresponding to the template type without applying the conversion API,
When the value of the user attribute received by the receiving means indicates non-display, the content of the element is hidden in the template corresponding to the template type,
If the value of the user attribute received by the receiving means indicates neither conversion nor non-display, execute a conversion request based on the user attribute in a template corresponding to the template type;
Rules,
The conversion means is based on the conversion API rule.
If the value of the user attribute received by the receiving means indicates no conversion, the content of the element is displayed in the template corresponding to the template type without applying the conversion API,
When the value of the user attribute received by the receiving means indicates non-display, the content of the element is hidden in the template corresponding to the template type,
When the value of the user attribute received by the receiving means indicates neither non-conversion nor non-display, the conversion applicability of the item of the user attribute indicated by the user attribute value received by the receiving means By applying the conversion API based on information and by setting the conversion API to be applied, the element-specific API application that determines the conversion target element and the conversion API that is the conversion method to be applied to each of the conversion target elements Create a rule
Each of the web content elements of the requested site extracted based on the web content element extraction rule set in advance so that the extraction method is determined by the site, the template, and the site and the template type. Is converted to a conversion API determined by the element-specific API application rule,
The display information after the conversion is generated by the Web content element after conversion,
The content conversion apparatus, wherein the conversion API used for conversion of the color scheme correction is an API that corrects the color scheme for a weak user . When the receiving unit does not receive the conversion request based on the user attribute, the converting unit determines a conversion target element and a conversion method according to a predetermined initial value, and corresponds to the determined conversion target element converting in accordance with the conversion method, according to claim 1 Symbol placing content conversion apparatus. Receiving a conversion request based on user attributes and a template type together with a request to access the site;
Conversion applicability information indicating conversion applicability of the elements in the display information of the site, converting API rules, and based on the conversion request, the conversion target element, a conversion method to be applied to each of the converted element conversion Determining the API ,
Converting the determined conversion target element according to the corresponding conversion method;
Sending the converted display information;
A content conversion method comprising :
The user attributes include items for translation, supplementary explanation and color correction,
The receiving step receives a conversion request indicating execution, no conversion or non-display specified by the user for each item of the user attribute;
The template type indicates a template type that is set in plural for each of a plurality of predetermined user terminal types,
The receiving step receives a template type selected by the user;
The conversion applicability information indicates whether the conversion API can be applied to each element,
The conversion API rule has items of the template type and the user attribute,
The conversion API rule is:
When the received value of the user attribute indicates no conversion, the content of the element is displayed in the template corresponding to the template type without applying the conversion API,
If the received value of the user attribute indicates non-display, the content of the element is hidden in the template corresponding to the template type,
If the received value of the user attribute indicates neither conversion nor non-display, execute a conversion request based on the user attribute in the template corresponding to the template type;
Rules,
The converting step is based on the conversion API rule.
When the received value of the user attribute indicates no conversion, the content of the element is displayed in the template corresponding to the template type without applying the conversion API,
If the received value of the user attribute indicates non-display, the content of the element is hidden in the template corresponding to the template type,
If the received value of the user attribute indicates neither conversion nor non-display, the user attribute value indicating the execution of the received user attribute value is a conversion API based on the conversion applicability information. By setting applicability and the conversion API to be applied, create an element-specific API application rule that determines the conversion target element and a conversion API that is a conversion method to be applied to each of the conversion target elements,
Each of the web content elements of the requested site extracted based on the web content element extraction rule set in advance so that the extraction method is determined by the site, the template, and the site and the template type. Is converted to a conversion API determined by the element-specific API application rule,
The display information after the conversion is generated by the Web content element after conversion,
The content conversion method, wherein the conversion API used for the conversion of the color correction is an API that corrects the color for the color weak . The program for functioning a computer as each means of the content conversion apparatus of Claim 1 or 2 . A recording medium for recording the program according to claim 4 .