JP2005352774A - Information processor, control method for information processor, computer program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate data conversion between data of a tabular form and data of a markup language form, or between different markup language forms. <P>SOLUTION: It is characterized by that tabular form data generated by inputting predetermined information in template information of a tabular form is converted into document data of a first markup language form by using a markup table registered with correspondence information of the template information of the tabular form, and composition information of a document of the first markup language form. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information processing apparatus, a control method for the information processing apparatus, a computer program, and a storage medium.

  There is a markup language in which a part of a document is surrounded by a special character string called a tag to describe the structure and modification information of the document in the sentence. Typical markup languages include SGML (Standard Generalized Markup Language), HTML (Hyper Text Markup Language), and XML (Extensible Markup Language). Moreover, there is XBRL (Extensible Business Reporting Language) as a markup language for disclosing corporate financial information (see Non-Patent Document 1).

  These markup language format data are suitable for the computer to perform processing according to the purpose of each language format, but refer to unintended processing such as data input, display, and printing It is not suitable for doing. For this reason, a technology has been proposed in which data is input using commercially available spreadsheet software, and this tabular data is converted to markup language format data or from markup language format to tabular data. Has been.

However, in these techniques, the table format is a specific format determined in advance, or is limited to a fixed configuration in which, for example, the first line is an item name, and the second and subsequent lines are data (see Patent Document 1). )), There is a problem in that the spreadsheet software and the version that can be used are limited by realizing the macro function of the spreadsheet software.
JP 2001-109741 (page 6, Fig. 2-3) Supervised by XBRL Japan, Manabu Sakagami and Yoshiko Shirata, “Financial Statement Preparation Manual by XBRL”, Nihon Keizai Shimbun, November 2003, p.6-24, p.188-220

  It is an object of the present invention to facilitate data conversion between tabular data and markup language data or between different markup language formats.

  The present invention for solving the above-described problems includes at least information on identification information for identifying a data input area and information on a start position of the data input area in tabular template information composed of a plurality of cells. Table, input items in the data input area, elements constituting a first markup language format tag associated with the input items, and cell positions corresponding to the input items in the data input area And a selection means for selecting a data input area based on the identification information from the tabular data generated by inputting predetermined input data to the tabular template information. And from the selected data input area to a cell in the data input area based on the start position and the position of the cell. First acquisition means for acquiring the inputted input data, first temporary storage means for temporarily storing the acquired input data in association with elements constituting the tag, and the first temporary storage First generation means for generating data in the first markup language format corresponding to the tabular data from the input data stored in the means and the elements constituting the tag. .

  In the present invention for further solving the above problem, the second table further includes an element constituting a second markup language format tag associated with the input item, The second acquisition means for acquiring the input data from the data of the first markup language format corresponding to the tabular data based on the elements constituting the tag of the first markup language format and the acquired Second temporary storage means for temporarily storing the elements constituting the tag of the first markup language format and the input data; and the first markup language format stored in the second temporary storage means. An element constituting the tag is converted into an element constituting the tag in the second markup language format, and the input data and the element constituting the tag in the second markup language format are used. Characterized in that it comprises a second generating means for generating data of the second markup language format that corresponds to the serial tabular data further.

  Furthermore, the present invention for further solving the above-described problem is that at least information on identification information for identifying a data output area and start position of the data output area in tabular template information composed of a plurality of cells. A first table comprising: the identification information; an output item in the data output area; an element constituting a first markup language format tag associated with the output item; and the data output area. From the second table having at least information about the position of the cell corresponding to the output item, and the first markup language format data expressing the tabular data as data in the first markup language format, the identification information Selection means for selecting corresponding data in the data output area based on the element, and an element constituting the tag from the selected data Acquisition means for acquiring the output data surrounded by a tag constituted by, a temporary storage means for temporarily storing the acquired output data in association with the cell position, and the temporary storage means stored in the temporary storage means And generating means for generating the tabular data by outputting the data to the tabular template information based on the cell position of the output data.

  According to the present invention, it is possible to easily convert data between tabular data and markup language data or between different markup language formats.

  An example of the system configuration of the data conversion system according to the present invention is shown in FIG. 1a, a data conversion system 100 includes a data conversion server 101, a terminal 102, an external storage device 103 for storing a mapping table, an external storage device 104 for storing a table format template, an external storage device 105 for storing additional information, and a table format. The external storage device 106 stores data and the external storage device 107 stores markup language format data. The data conversion server 101 includes a markup language format generation unit 108, a table format conversion unit 109, and a markup language format conversion unit 110 as processing units for data conversion.

  The configuration of the data conversion system 100 is not limited to a stand-alone computer, and may be a system in which the data conversion server 101, the terminal 102, and the external storage devices 103 to 107 are connected by an electric communication line.

  FIG. 1b shows a hardware configuration when the data conversion system in FIG. 1a is configured as a stand-alone information processing apparatus.

  A CPU 111 controls the apparatus using programs, data, and the like stored in a RAM (Random Access Memory) 112 and a ROM (Read Only Memory) 115, and also includes a markup language format generation unit 108 and a table format conversion unit. 109 and the markup language format conversion unit 110 perform data conversion processing corresponding to the present invention. Reference numeral 112 denotes a RAM which includes an area for reading information such as a data conversion processing program stored in the internal storage device 117 and a mapping table stored in the database 118, and a work used when the CPU 111 executes various processes. It also has an area.

  Reference numeral 113 denotes an input unit that receives input from the user, and includes a keyboard and a mouse. A communication I / F (interface) 114 functions as an I / F for connecting to the Internet or a LAN (local area network).

  A ROM 115 stores a program (for example, a boot program) for controlling the entire information processing apparatus. Reference numeral 116 denotes a display unit as a display screen, which includes a CRT or a liquid crystal screen.

  Reference numeral 117 denotes an internal storage device mainly composed of a hard disk, and stores a data conversion processing program and various application data. The data stored here is read out to the RAM 112 as necessary. Reference numeral 118 denotes an external storage device that stores a mapping table, a tabular template, additional information, tabular data, and markup language format data. A bus 119 connects the above-described units.

  In the present embodiment, an example will be described in which XBRL is used as the markup language and a format used in general-purpose spreadsheet software is used as the table format.

  The user of the data conversion system 100 creates a table format template that defines the structure of the table format to be processed and stores it in the external storage device 104 as advance preparation for data conversion. The tabular structure represents a position where a data value (input numerical value or the like) is set, a title position, and a blank area position. Also, a mapping table for defining the structure of the markup language format and defining the correspondence between the table format for the data value and the markup language format is created and stored in the external storage device 103. The definition of the structure in the markup language format represents a tag name and an attribute. The correspondence between the tabular format and markup language format for data values is the specification of the variable area or fixed area that sets the data value, the variable direction, the variable end condition, the relationship between the position where the data value is set and the tag, the data type Is expressed.

  Here, the variable area refers to an area where the number of data sets set in the area changes to 2 or more, and the fixed area refers to a fixed number of data sets set in the area. It is the area that is.

  When creating a tabular template, you can select one of a plurality of standard template sheets prepared for each spreadsheet software and change them based on this, or create a new template from a new sheet. Also good. The tabular template defines a tabular structure, and includes a blank cell and a title (title) cell in addition to a cell for setting a data value related to the markup language format. When creating a mapping table, for example, a method for selecting and specifying tag names and attribute information by a menu method by specifying individual cells of the created tabular template, or a method for recording tag names and attribute information on the sheet itself It may be performed by.

  Next, an example of a tabular template will be specifically described with reference to FIG. FIG. 2 is a diagram illustrating an example of a tabular template that displays daily stock price information. A configuration example of the mapping table corresponding to the tabular template 200 of FIG. 2 is shown in FIGS. 3a to 3c. The tabular template 200 shown in FIG. 2 includes a fixed area 201 for displaying the date, a brand 203, and a variable area 202 for price display (204 to 207) (one column corresponding to each item is prepared. And the number of rows is not fixed).

  In the present embodiment, these data setting areas are called forms. In FIG. 2, the fixed area 201 and the variable area 202 are composed of two forms. The format for storing the table format template and / or the mapping table may be the table format shown in FIGS. 2 and 3a to 3c, or may be a markup language format (not shown). In FIG. 2, “date / time stock price information”, “year”, “month”, “day”, “brand”, “open price”, “high price”, “low price”, and “close price” are the titles in the tabular template. It corresponds to.

  FIG. 3 a is a diagram illustrating an example of region information in the mapping table. The area information is information that defines a variable area or a fixed area for setting a data value, a variable direction, and a variable end condition. In the area information 301, “form identification name” represents an identifier for uniquely identifying each form included in the area information. “Type” indicates whether each form is fixed or variable. The “start cell position” represents the start position of each form in the tabular template.

  The “increase direction” indicates in which direction the row or column increases when the table is variable. “Search position” represents the number of rows or columns to be searched when searching for the presence or absence of input items of rows or columns in a direction orthogonal to the direction specified by “increase direction”. For example, if the “increase direction” is “row” and the “search position” is “1”, data related to a predetermined item is input in the row direction in the cell. Is determined, the cell in the first column is targeted.

  The “cell interval” represents the size of a cell into which data is input. For example, if the “cell interval” is “1”, data is input in units of one cell. The “end condition” indicates a condition for determining how far a cell in which data is input has been entered. For example, if it is set to “blank”, if a cell is blank in a row next to a certain row, data input in that column has been completed. If the number of times is set such as “5 times”, it is determined that the cells from the first cell up to 5 times are valid, and the input is completed when the number of times exceeds 5 times.

  Other values will be described later in the processing section of the markup language format generation unit. The items included in the region information 301 are not limited to those shown in FIG. In addition to the information shown here, if there is information included in the tabular template, the corresponding item is naturally included in the area information 301.

  More specifically, the form 201 for date display is “Form1” as the value of “form identification name”, “year / month / day” as the value of “form tag name”, and “fixed” as the value of “type”. The value of “start cell position” indicating the upper left position of the form is set to (3, 5) in the form of (row, column) by the cell number.

  The price display form 202 has “Form2” as the value of “form identification name”, “stock price information” as the value of “form tag name”, “variable” as “type”, and “value of“ start cell position ”. (7,2), “Increase direction” is set to “Row”, “Search position” is set to “1”, “Cell spacing” is set to “1”, and “End condition” is set to “Blank”. .

  FIG. 3b describes an example of a data structure of information (form information) constituting each form. Form information is information required to convert information input to each form identified by the “form identification name” in FIG. 3A into markup language format data such as a tag. This includes elements constituting a markup language format tag associated with an input item in the form.

  In the form information 302 shown in FIG. 3B, “prefix character string” is a character string added to the head of the XBRL tag name. The “item name” is a character string constituting the XBRL tag name for representing the value of the cell of “cell position”. “Item tag name” is a character string used as a tag name when the XML format described later is handled. “Cell position” represents a relative position when the upper left start cell position of the form is (1,1). For example, for the item whose “form identification name” is “Form1”, “year”, “month”, and “day” are set as titles on the left side as shown in the form 201 in FIG. "2" is specified for each column position where data values are set. “Data type” is a character string representing an attribute of input data. The data type includes a character string type and a money amount type.

  In XBRL, when describing actual data, additional information is described as information representing the attribute of the data such as which company belongs to which period and what unit. This information is called a context in this embodiment. “Context ID” is a character string for identifying a context, and the form information 302 in FIG. 3B is associated with a context of context ID: c0. The “unit ID” is a character string for identifying the currency unit of the input monetary amount when the “data type” of the input data is the monetary type. The “group name” is a character string for handling a plurality of “item names” as a set.

  FIG. 3c shows an example of the data structure of the group information. The group information is information related to “group name” input in the form information 302. In the group information 303 shown in FIG. 3c, “group name” is a character string corresponding to the group name in FIG. 3b, and “group tag name” corresponds to the “group name” and handles the XML format described later. This is a character string used as a tag name. The “tuple ID” is a character string for identifying a group.

[First Embodiment]
In the present embodiment, data conversion processing for converting tabular data into markup language data will be described.

  After the user generates the mapping table corresponding to the tabular template and completes the preparation as described above, the data shown in FIG. 4 is transmitted from the terminal to the predetermined tabular format using the spreadsheet software. When a template is input and stored in the external storage device 106 as tabular data, the mapping table 103 corresponding to the tabular data 106 is designated and the markup language format generator 108 is activated and executed. The generation unit 108 creates markup language format data in accordance with the processing flow shown in FIGS. 5 a and 5 b, and stores the data in the external storage device 107.

  Hereinafter, processing corresponding to the flowcharts of FIGS. 5A and 5B will be described. First, in step S501 of FIG. 5a, the mapping table 103, the tabular data 106, and the additional information 105 are read. In the present invention, context and currency information commonly used by users (see Non-Patent Document 1) is created in advance as additional information shown as an example in FIG. 6 and stored in the external storage device 105.

  In the example illustrated in FIG. 6, <cdt: contextData contextRef = "c0"> <xbrli: context id = "c0">... </ Xbrli: context> </ cdt: contextData> is a context ID: represents the data range of the context of c0, and <xbrli: entity>... / xbrli: entity> means that information on an organization related to the data is included, and <xbrli: identifier scheme = "qq2"> c0 </ xbrli: identifier> represents an identifier of the organization and a standard that defines the identifier.

  In addition, <xbrli: period> ... </ xbrli: period> represents a period or a period in which data is applied, and <xbrli: forever> </ xbrli: forever> in this embodiment corresponds to a period. It means that it does not depend on the date and time to be performed.

  Other information included in the context is also interpreted in the same manner as described above.

  Furthermore, for the currency information included in FIG. 6, <cdt: unitData unitRef = "u0"> <xbrli: unit id = "u0"> ... </ xbrli: unit> </ cdt: unitData> The data range of the currency information with ID: u0 is shown. <Xbrli: measure> iso4217: JPY </ xbrli: measure> is the Japanese currency unit code defined by ISO4217 as the unit actually specified A circle is specified. Other information included in the currency is also interpreted in the same manner as described above.

  The markup language format generation unit 108 reads the mapping table, tabular data, and additional information from the external storage device (103, 106 and 105) into the RAM 112.

  In step S502, one form is a processing target. The markup language format generation unit 108 sets one of unprocessed forms as a processing target based on the contents of the mapping table as shown in FIGS. 3a to 3c.

  Next, in step S503, a value in tabular data is obtained based on the cell position. More specifically, with reference to FIGS. 3 a to 3 c, the markup language format generation unit 108 uses the value of “start cell position” (upper left position of the form) of the area information 301 and “cell position of the form information 302. ”(Relative position from the upper left of the form), the position of the cell in the table format is calculated to obtain the value of the data input for each cell. For example, the “form identification name” value “Form2” and the “start cell position” value “(7,2)” in FIG. 3A and the “form identification name” value “Form2” and “cell position” in FIG. From the value “(2,1)”, the cell position is calculated as (7 + 2-1,2 + 1-1) = (8,2), and the data of the cell position (8,2) in FIG. The value “Company A” is obtained.

  In step S504, the data value and the mapping table information are stored in association with each other. The markup language format generation unit 108 includes a “prefix string”, “item name”, “item tag name”, “cell position”, “data type”, “context ID”, “unit ID” of the form information 302, A value such as “group name” and the value of the cell obtained in step S503 are associated with each other and stored in the RAM 112 in the data conversion server 101. Here, in the RAM 112, predetermined data is registered in association with the cell value as shown in FIG. 14a.

  Here, when the “type” value of the target form is “variable”, the context ID value (for example, “c0”) is the same for multiple cell values obtained by changing the cell position in the increasing direction. The value of the “context ID start number” (for example, “1”), the value of the “context ID delimiter” (for example, “-”), the value of the “context ID increment” (for example, “1”) ) To generate different context IDs and store them in the RAM 112 (for example, “c0-1”, “c0-2”...). However, if you want to use the same ID, you can set the value of “Context ID increment” to “0”. The same applies to the unit ID and tuple ID.

  In step S505, it is checked whether an unprocessed “cell position” value remains for the target form in FIG. 3B. If there is an unprocessed form, the process returns to step S503 to continue the process. If there are no unprocessed items, the process advances to step S506. For example, in the form of “Form2” in FIG. 3B, “(2,1)”, “(2,2)”, “(2,3)” are indicated by the value of “cell position”. , “(2,4)” and “(2,5)” are set, the tabular data acquisition process in step S503 is repeated a total of five times.

  Next, in step S506, variable processing is performed. This variable process is a process for determining whether or not there is data input in the direction set in the “increase direction” of the area information 301. Details of the processing here will be described with reference to the flowchart shown in FIG.

  First, in step S511, the markup language format generation unit 108 checks the “type” value of the form to be processed with reference to FIG. 3A. If the value is “fixed”, the markup language format generation unit 108 proceeds to step S516. In step S516, it is determined that the processing of the processing target form is completed, and the process proceeds to step S507 in FIG. Here, when the “type” of the form is “fixed”, the reading of the data value input in the “cell position” shown in FIG. 3B has already been completed in the processing from step S503 to step S505. Because it is.

  On the other hand, if the value of “type” is “variable”, the process proceeds to step S512, and the value of “end condition” in FIG. If the number is specified as a value such as “5 times”, for example, the process proceeds to step S513, and the value of “end condition” is compared with the number of repetitions so far. If the value of “end condition” <the number of repetitions, the process proceeds to step S516 described above. Otherwise, the process proceeds to step S517.

  In step S512, if the “end condition” value is not designated as the number of times, the process proceeds to S514, and the value of the current cell position in the direction designated by the “increase direction” value in FIG. To change. For example, if the value of “start cell position” is “(7,2)”, the value of “increase direction” is “row”, and the value of “cell interval” is “1”, the value of the current cell position is determined in step S514. For each iteration, increase it by 1 in the row direction and change it to (8,2), (9,2),.

  In step S515, the value of the cell designated by “search position” in FIG. 3A and the value of “end condition” are compared with the current position as a reference. If they match, the process proceeds to step S516 described above. In the condition shown in FIG. 3A, when the value of the target cell is blank (no input), the “end condition” is met.

  On the other hand, if the “end condition” is not met, the process proceeds to step S517. In step S517, it is determined that the process is repeated. In step S518, the values of “context ID increment”, “unit ID increment”, and “tuple ID increment” in FIG. To reflect. Thereafter, the process proceeds to step S503 in FIG. 5 in order to read the data input to the row.

  Here, returning to FIG. 5a again, in step S507, it is determined whether or not to end the process. If the processing is completed for all the forms, the process proceeds to step S508. On the other hand, if there is an unprocessed form, the process returns to step S502 to continue the process.

  In step S508, the stored data is written as markup language format data. More specifically, the markup language format generation unit 108 creates markup language format data based on the information stored in the RAM 112 in step S504 and the additional information read in step 501 to create an external data. Write to the storage device 107.

  As an example of the result of this writing process, FIG. 7 shows an example of the XBRL format data created when processing is performed on the tabular data of FIG.

  For example, for the value “2002” of the cell position (3, 6) in FIG. 4, the value “Form1” of the “form identification name” and the value “jp-bs-” of the “prefix string” in the form information 302 of FIG. 0 "," item name "value" Year "," context ID "value" c0 "based on the data shown in FIG. 7 (a)" <jp-bs-0: Year contextRef = "c0" > 2002 </ jp-bs-0: Year> ".

  As described above, by using the mapping table corresponding to the tabular template, the tabular data created by inputting data using the tabular template is converted into desired markup language format data. Can do.

  In the above description, the case where XBRL is adopted as the markup language has been described. However, the language to be converted is not limited to XBRL. That is, data registered in the mapping table may be associated with each markup language format.

  In addition, the mapping table determines the correspondence between the table format and the markup language format, so by preparing multiple mapping tables for the same data, the table format at input and the table format at output can be different. It is also possible to output in multiple tabular formats depending on.

  Further, since the area information is held for each form in the mapping table, the format can be easily changed. In addition, since the tag name in the markup language format can be set and changed by the mapping table, the tag name can be meaningful to the user.

  Moreover, in the data conversion system corresponding to this embodiment, since a conversion rule is held in the mapping table, a single system can handle a plurality of markup language formats and table formats.

[Second Embodiment]
In the present embodiment, a data conversion process for converting markup language data into tabular data will be described.

  For example, when the user designates markup language format data (for example, XBRL format data in FIG. 7), a table format template, and a mapping table and starts the table format conversion unit 109, the table format conversion unit 109 The markup language data is converted into tabular data along the processing flow shown in FIG. 8a and FIG. 8b, and stored in the external storage device 106.

  Processing corresponding to the flowcharts of FIGS. 8a and 8b will be described below.

  First, in step S801 of FIG. 8a, a mapping table, a table format template, and markup language format data are read. The table format conversion unit 109 reads the mapping table, the table format template, and the markup language format data from the external storage devices 103, 104, and 107 into the RAM 112, respectively.

  In step S802, one form is a processing target. The table format conversion unit 109 sets one of the unprocessed forms as a processing target based on the mapping tables of FIGS. 3A to 3B.

  In step S803, data in a markup language format is obtained. The table format conversion unit 109 uses the markup language format based on the tag name created from the values of “prefix character string”, “group name”, and “item name” of the form information 302 of the mapping table for the target form. Specify the data and get the value.

  For example, the tag name from the value “jp-bs-0” of “prefix string” of “value 1” of “Form 1” of “Form 1” of the form information 302 of FIG. 3B and the value “Year” of “Item name” Create "jp-bs-0: Year", identify the XBRL format data (a) in Fig. 7 based on this tag name, and enclose it in the tag name "jp-bs-0: Year" The value "2002" is obtained.

  In step S804, the data value and the cell are stored in association with each other. The table format conversion unit 109 calculates a table from the “start cell position” value (upper left position of the form) of the area information 301 of the mapping table and the “cell position” value (relative position from the upper left of the form) of the form information 302. The cell position in the format is calculated and stored in the RAM 112 as shown in FIG. 14b in association with the data value obtained in step S803.

  In step 805, it is checked whether an unprocessed “item name” value of the target form in FIG. 3B remains. If there is an unprocessed value, the process returns to step S803 to continue the process. If there are no unprocessed items, the process advances to step S806. For example, in the form whose “form identification name” is “Form1” in FIG. 3b, the value of “item name” indicates three values “Year”, “Month”, and “Day”. A total of 3 repetitions will be performed.

  In step S806, variable processing is performed. This variable process is a process for extracting all the data enclosed by the tags in the form corresponding to the case where the “type” of the form is set to be variable. Details of the processing here will be described with reference to the flowchart of FIG.

  In FIG. 8B, the table format conversion unit 109 checks the “type” value of the form to be processed with reference to FIG. 3A in step S811, and proceeds to step S816 if the value is “fixed”. In step S816, it is determined that the processing of the processing target form is finished, and the process proceeds to step S807 in FIG. Here, when the “type” of the form is “fixed”, data corresponding to the tag name specified in the processing from step S803 to step S805 has already been acquired.

  On the other hand, if the value is “variable”, the process proceeds to step 812 to check the value of “end condition” in FIG. If the value is specified as a number of times such as “5 times”, for example, the process proceeds to step S813, and the value of “end condition” is compared with the number of repetitions so far. If the value of “end condition” <the number of repetitions, the process proceeds to step S816 described above. Otherwise, the process proceeds to step S817.

  In step S812, if the value of “end condition” is not the number of times designation, the process proceeds to S814, and it is checked whether there is more data of the tag name specified in step S803 of FIG. In step S815, if there is no data, the process proceeds to S816 described above. If data exists, the process proceeds to step S817.

  In step S817, after it is determined to be repeated, in step S818, the value of the current cell position is changed by the value of “cell interval” in the direction specified by the value of “increase direction” in FIG. For example, if the value of “start cell position” is “(7,2)”, the value of “increase direction” is “row”, and the value of “cell interval” is “1”, the value of the current cell position is repeated. Every time, it is incremented by 1 in the row direction and changed to (8,2), (9,2),. Thereafter, the process proceeds to step S803 in FIG. 8 for repeated processing.

  In step S807, it is determined whether or not the process is finished. If all forms have been processed, the process proceeds to step S808. If there is an unprocessed form, the process returns to step S802 to repeat the process.

  In step S808, the stored data is written as tabular data. The tabular conversion unit 109 creates tabular data based on the information stored in the RAM 112 in step S804 and the tabular template read in step S801, and writes the tabular data to the external storage device 106.

  In this way, the table format conversion unit 109 converts the data in the XBRL format in FIG. 7 to the data in the table format in FIG. 4 using, for example, the table format template in FIG. 2 and the mapping tables in FIGS. 3a to 3c. It can be performed. The table format conversion unit 109 creates CSV (Comma Separated Value) format data (not shown), which is data in a format in which character strings are separated by commas, according to the user's specification, and creates an external storage device 106. You can also export to

  As described above, in the invention corresponding to this embodiment, conversion from markup language format data to tabular data can be performed.

[Third Embodiment]
In this embodiment, a case where data conversion is performed between different markup language format data will be described.

  For example, data in XBRL format is suitable for the distribution and use of financial information using a computer, but the language specification is strict and is different from the names of account items used in general companies. Knowledge of taxonomies (see, for example, Non-Patent Document 1) where tag names must be used, lists of accounts listed in financial statements, and dictionary of items that can be handled in financial statements Since it is required, it is not suitable for use in other business processes as it is.

  On the other hand, in XML, a user can freely decide a tag name. Also in the present invention, the tag name can be set and changed by the user as the values of “form tag name”, “group tag name”, and “item tag name” in the mapping table. If the data in the XBRL format is converted into the XML format by the processing of the markup language format conversion unit 110 according to the present invention, the use of information in other business processing becomes easy. It is also possible to create data in XML format from data held in other processing and convert it to XBRL format by the processing of the markup language format conversion unit according to the present invention.

  When the user designates the first markup language format data and the mapping table and activates the markup language format conversion unit 110, the markup language format conversion unit 110 performs the process shown in FIG. According to the flow, the data in the first markup language format is converted into the data in the second markup language format and stored in the external storage device 107.

  In the following, the process performed by the markup language format conversion unit will be described with reference to the flowchart of FIG. 9, taking as an example the case of converting the data in the XBRL format in FIG. 7 into the data in the XML format in FIG.

  In step S901, the mapping table and the first markup language format data are read out. The markup language format conversion unit 110 reads the mapping table and the data of the first markup language format from the external storage devices 103 and 107a into the RAM 112.

  In step S902, one form is a processing target based on the mapping table. The markup language format conversion unit 110 obtains one “form identification name” value from the area information 301 of the mapping table and sets it as a processing target. For example, the form identification name “Form1” is obtained from the area information 301 in FIG. 3A and is processed, and is combined with the value “year / month / day” of “form tag name”. Form 1 “>” is stored in the RAM 112.

  In step S903, the value of the first markup language format data is obtained based on the item name. The markup language format conversion unit 110 obtains one “item name” value (referred to as “ITMNM”) from the form information 302 of the mapping table, and this value and the “prefix string” value (“PRFX”). Based on the above, the data of the tag name “PRFX: ITMNM” is obtained from the first markup language format data, and the value surrounded by the tag name is obtained.

  For example, from the form information 302 in FIG. 3B, based on the item name value “Year” and the “prefix string” value “jp-bs-0”, “<jp-bs-0” in FIG. : Year contextRef = "c0"> 2002 </ jp-bs-0: Year> "is obtained, and the value" 2002 "enclosed in the tag name is obtained. At this time, if the value of “group name” is set, the group information 303 is referred to, and the values of “group tag name” and “tuple ID” are obtained and stored in the RAM 112 (for example, (C) in FIG. )reference).

  In step S904, the tag name, attribute, and value are stored in association with each other. The markup language format converter 110 converts the “item tag name”, “context ID”, “unit ID” values corresponding to the “item name” value obtained in step S903, and a value surrounded by the tag name (for example, "2002", "920", etc.) are associated and stored in the RAM 112 as shown in FIG. 14c.

  In step S905, if there is another “item name” value in the processing target form, the processing from step S903 is repeated. If there is no other “item name” value, the process proceeds to step S906, where the “type” value of the form to be processed is checked. If the value is “variable”, the processing from step S903 is repeated.

  On the other hand, if the value is not “variable”, the process proceeds to step S907 to determine whether or not to end the process. Specifically, it is determined whether or not all items of the processing target form have been processed. If so, the processing from step S902 is repeated for another unprocessed form. On the other hand, if all forms have been processed, the process proceeds to step S908.

  In step S908, the stored data is written as data in the second markup language format. The markup language format conversion unit 110 creates data in the second markup language format based on the information stored in the RAM 112 in steps S902, S903, and S904, and writes the data in the external storage device 107b.

  The markup language format conversion unit 110 uses the same mapping table as that used when converting from the XBRL format to the XML format, and uses the same processing procedure as shown in FIG. 9 to convert the XML format to the XBRL format. Can also be converted.

  Also, for markup language formats other than the XBRL format and the XML format, the language format can be easily converted by associating tags in the mapping table.

  As described above, in the present embodiment, data conversion can be performed between different markup language formats. When a plurality of different markup language format data is generated from the same table format data and mapping table, a markup language format conversion unit 110 is provided after the markup language format generation unit 108 to further perform data conversion processing. May be executed. In this case, step S901 need not be executed.

[Fourth Embodiment]
By preparing different tabular templates and mapping tables for the same data, the tabular format at the time of output can be made different. The other tabular template in FIG. 11 and the other mapping table in FIG. 12 are different from those in FIGS. 2 and 3a to 3b in that they do not display the position of the form, the high price, and the low price. .

  Since the form having the “form identification name” “Form1” changes only the start cell position without changing the structure, it is only necessary to change the value of the “start cell position” in the area information 301 of the mapping table. The value of “cell position” in the form information 302 is not changed. In the present invention, a form can be easily changed by adopting a form.

  When the user designates the XBRL format data in FIG. 7, the other table format template in FIG. 11 and the other mapping table in FIG. 12, and starts and executes the table format conversion unit, the table format conversion unit Export data in other display formats shown in. In addition, when converting from the same markup language format data to a plurality of different table formats, the data conversion process in the table format conversion unit 109 may be executed continuously. In this case, it is not necessary to read markup language format data in step S801 of the second and subsequent processing.

  As described above, in the present invention corresponding to the first to fourth embodiments, even in the same markup language format data, different table formats can be obtained by changing the table format template and the mapping table. Can be output. Further, by changing the table format template and the mapping table, it is possible to output data in a table format different from that at the time of data input via data in the markup language format.

[Other Embodiments]
The above processing (for example, processing according to the flowchart shown in the above embodiment) is stored as a program in a computer-readable storage medium such as a CD-R, ROM, DVD-ROM, or MO, and is stored in this storage medium. This computer can perform the above processing by causing the computer to read (install or copy) the program. Therefore, it is clear that this storage medium is also within the scope of the present invention.

It is a figure which shows an example of a structure of the data conversion system corresponding to embodiment of this invention. It is a figure which shows an example of the hardware constitutions of the data conversion system corresponding to embodiment of this invention. It is a figure which shows an example of the tabular template corresponding to embodiment of this invention. It is a figure which shows an example of the area | region information in the mapping table corresponding to embodiment of this invention. It is a figure which shows an example of the form information in the mapping table corresponding to embodiment of this invention. It is a figure which shows an example of the group information in the mapping table corresponding to embodiment of this invention. It is a figure which shows an example of the tabular data corresponding to embodiment of this invention. It is a flowchart corresponding to an example of the data conversion process corresponding to the 1st Embodiment of this invention. It is a flowchart corresponding to an example of the variable process corresponding to the 1st Embodiment of this invention. It is a figure which shows an example of the additional information corresponding to embodiment of this invention. It is a figure which shows an example of the data of the XBRL format corresponding to embodiment of this invention. It is a flowchart corresponding to an example of the data conversion process corresponding to the 2nd Embodiment of this invention. It is a flowchart corresponding to an example of the variable process corresponding to the 2nd Embodiment of this invention. It is a flowchart corresponding to an example of the data conversion process corresponding to the 3rd Embodiment of this invention. It is a figure corresponding to an example of the XML data corresponding to the 3rd Embodiment of this invention. It is a figure which shows an example of the tabular template corresponding to the 4th Embodiment of this invention. It is a figure which shows an example of the area | region information in the mapping table corresponding to the 4th Embodiment of this invention. It is a figure which shows an example of the form information in the mapping table corresponding to the 4th Embodiment of this invention. It is a figure which shows an example of the group information in the mapping table corresponding to the 4th Embodiment of this invention. It is a figure which shows an example of the tabular data corresponding to the 4th Embodiment of this invention. It is a figure which shows an example of the data corresponding to the 1st Embodiment of this invention. It is a figure which shows an example of the data corresponding to the 2nd Embodiment of this invention. It is a figure which shows an example of the data corresponding to the 3rd Embodiment of this invention.

Claims (6)

A first table including at least identification information for identifying a data input area and information on a start position of the data input area in tabular template information composed of a plurality of cells;
Information on the input item in the data input area, the elements constituting the first markup language format tag associated with the input item, and the position of the cell corresponding to the input item in the data input area A second table comprising at least;
Selecting means for selecting a data input area based on the identification information from the tabular data generated by inputting predetermined input data to the tabular template information;
First acquisition means for acquiring, from the selected data input area, the input data input to a cell in the data input area based on the start position and the position of the cell;
First temporary storage means for temporarily storing the acquired input data in association with elements constituting the tag;
First generation means for generating data in the first markup language format corresponding to the tabular data from the input data stored in the first temporary storage means and elements constituting the tag; An information processing apparatus comprising: The first table further includes information on a cell type in the region, an increasing direction of the cell, and an end condition for determining the end of data input,
A determination means for determining whether or not the termination condition is satisfied in an increasing direction of the cell when the cell type is variable;
2. The information according to claim 1, wherein when the determination unit determines that the termination condition is satisfied, the selection unit selects another data input area that is not selected in the tabular data. Processing equipment. The second table further includes an element constituting a second markup language type tag associated with the input item,
Second acquisition means for acquiring the input data from the first markup language format data corresponding to the generated tabular data based on elements constituting the first markup language format tag; Second temporary storage means for temporarily storing the elements constituting the acquired tag in the first markup language format and the input data;
Converting an element constituting the first markup language format tag stored in the second temporary storage means into an element constituting the second markup language format tag, and the input data; And a second generation means for generating data in the second markup language format corresponding to the tabular data from elements constituting the tag in the second markup language format. The information processing apparatus according to claim 1 or 2. A first table comprising at least identification information for identifying a data output area and information on a start position of the data output area in tabular template information composed of a plurality of cells;
The identification information, the output item in the data output area, the elements constituting the first markup language format tag associated with the output item, and the cell corresponding to the output item in the data output area A second table comprising at least information about the position;
Selecting means for selecting corresponding data in the data output area from the first markup language format data expressing the tabular data as data in the first markup language format;
Obtaining means for obtaining, from the selected data, the output data surrounded by tags constituted by elements constituting the tags;
Temporary storage means for temporarily storing the acquired output data in association with the cell position;
An information processing apparatus comprising: generating means for generating the tabular data by outputting the data to the tabular template information based on a cell position of the output data stored in the temporary storage means .   The information processing apparatus according to claim 1, wherein the first markup language format is an XBRL format or an XML format.   A computer program for causing a computer to function as the information processing apparatus according to any one of claims 1 to 5.

Images