JP2008108144A - Information processing method, information processor, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To verify validity of a transformation rule of structured data. <P>SOLUTION: This information processor stores first data in memory, stores data for verification where the second data output when first data is correctly transformed into a second form by the program and transformation rule is estimated, transforms the first data into second data of the second form by providing the transformation rule to be verified and actually executing the program, compares the content of the second element constituting the second data after the transformation with the second element constituting the data for verification stored in the memory, and generates the data showing the second element of mismatch. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an information processing method, an information processing apparatus, and a program for verifying whether or not structured data conversion rules are correct.

XSLT (eXtensible Stylesheet Language Transformations) is known as a convention for describing conversion rules for converting structured data represented by XML (eXtensible Markup Language). In addition, an application program that can create a conversion rule using a GUI is also provided (see Non-Patent Document 1).
Apresso, Inc., "Data Spider", [online], [Search September 27, 2006], Internet <URL: http://www.appresso.com/products/dataspider/pdfs/dataspider_catalogue.pdf>

  In order to verify whether the conversion rule is correct, it is necessary to actually apply the conversion rule to the structured data and check whether the data generated as a result has the expected contents.

  However, when the conversion rule defines processing such as repetition or combination, or when the hierarchy of structured data to be generated becomes deep, the contents to be verified are various. Also, in many structured data formats such as XML, it is possible to freely set the presence / absence of line breaks and indents, the description order of elements and attributes, etc. , It is not always written in the expression planned by the user. Therefore, it is difficult for the user to judge with eyes whether the converted structured data is correct.

  The present invention has been made in view of such a background, and an object thereof is to provide an information processing method, an information processing apparatus, and a program capable of verifying the correctness of a conversion rule for structured data. .

  The main invention of the present invention for solving the above-mentioned problem is that the first data structured in the first format constituted by a plurality of first elements is converted into a first data constituted by a plurality of second elements. An information processing method for verifying the correctness of a conversion rule in which a relationship between the first element and the second element is defined, which is given when executing a program for converting to second data in the form of 2. And an information processing apparatus comprising a memory, wherein the first data is stored in the memory, and the first data is output when the first data is correctly converted into the second format by the program and the conversion rule. Data for verification assuming second data is stored in the memory, and the first rule is converted into the second format by actually executing the program by giving the conversion rule to be verified. The contents of the second element constituting the second data after conversion to the second data and the second element constituting the verification data stored in the memory are converted into the second data. In comparison, data indicating the mismatched second element is generated.

  According to the present invention, it is possible to verify the correctness of the structured data conversion rule.

  Hereinafter, an information processing apparatus 100 according to an embodiment of the present invention will be described. The information processing apparatus 100 according to the present embodiment converts data structured in XML (eXtensible Markup Language) defined by the first schema (hereinafter referred to as XML data) and uses the second schema. The correctness of the conversion rule given to the program for generating the defined XML data is verified.

  The first and second schemas that define XML are data that define the structure (format) of XML, and are described by, for example, DTD (Document Type Definition) or XML Schema. In the following description, the first and second schemas are referred to as a conversion source schema and a conversion destination schema, respectively.

  A conversion rule given to a program for converting XML data is described in, for example, the format of XSLT or XQuery. In the present embodiment, the first and second schemas are described by XML Schema, and the conversion rules are described by XSLT. A program that converts XML data in accordance with a conversion rule described by XSLT is called an XSLT engine.

  The information processing apparatus 100 according to the present embodiment is XML data (hereinafter referred to as conversion source data, which corresponds to the first data of the present invention) defined in advance by a first schema (hereinafter referred to as conversion source schema). And XML data that is assumed to be output when the conversion source data is correctly converted (hereinafter referred to as conversion destination data, which corresponds to the verification data of the present invention) are stored in accordance with the conversion rules. The conversion source data is converted by the XSLT engine, the conversion result data by the XSLT engine (hereinafter referred to as test data, which corresponds to the second data of the present invention), and the conversion destination data stored in advance. Whether the conversion rule is correct or not is determined based on whether or not they match. The second schema defining the conversion source data is hereinafter referred to as a conversion destination schema.

== Hardware configuration ==
FIG. 1 is a diagram illustrating a hardware configuration of the information processing apparatus 100. As shown in the figure, the information processing apparatus 100 includes a CPU 101, a memory 102, a hard disk 103, a video memory 104, a display device 105, and an input device 105. The hard disk 103 stores programs and data. The CPU 101 implements various functions by reading a program stored in the hard disk 103 into the memory 102 and executing it. The video memory 104 is a memory for writing information to be displayed to the user of the information processing apparatus 100, and the information written in the video memory 104 is displayed on the display device 105. The input device 106 is, for example, a keyboard, a mouse, a touch panel, or the like that accepts input of information from the user.

== Software configuration ==
FIG. 2 is a diagram illustrating a software configuration of the information processing apparatus 100. As shown in the figure, the information processing apparatus 100 includes a schema input unit 111, a pattern data input unit 112, a mapping data input unit 113, a conversion rule generation unit 114, a data conversion unit 115, a data comparison unit 116, and a difference display unit 117. , A model data generation unit 118 and a model data display unit 119, and a schema storage unit 151, a pattern data storage table 152, a conversion rule storage unit 153, and a difference storage table 154 storage unit. .

  Note that each of the functional units 111 to 119 is realized by the CPU 101 included in the information processing apparatus 100 reading out the program stored in the hard disk 103 to the memory 102 and executing the program. The storage units 151 to 154 are realized as storage areas provided by the memory 102 and the hard disk 103.

  The schema storage unit 151 stores a conversion source schema and a conversion destination schema. A configuration example of the schema storage unit 151 is shown in FIG. As shown in the figure, the schema storage unit 151 stores a conversion source schema and a conversion destination schema.

  The schema input unit 111 receives input of the conversion source schema and the conversion destination schema from the user, and stores the received conversion source schema and conversion destination schema in the schema storage unit 151.

  The pattern data storage table 152 stores records (hereinafter referred to as pattern data) that associate conversion source data and conversion destination data. FIG. 4 shows a configuration example of the pattern data storage table 152. As shown in the figure, the pattern data stored in the pattern data storage table 152 includes a pattern number, a conversion source file, and a conversion destination file. The pattern number is identification information of pattern data. The conversion source file is the file name of the file in which the conversion source data is stored. The conversion destination file is the file name of the file in which the conversion destination data is stored.

  The pattern data input unit 112 receives input of conversion source data and conversion destination data from the user, and stores the received conversion source data and conversion destination data in files. The pattern data input unit 112 generates pattern data including the file name of the file storing the conversion source data and the conversion destination data, and registers the generated pattern data in the pattern data storage table 152.

  The mapping data input unit 113 includes an element defined in the conversion source schema (hereinafter referred to as a conversion source element; corresponding to the first element of the present invention) and an element defined in the conversion destination schema (hereinafter referred to as the conversion destination). An input of data defining an association with an element (corresponding to the second element of the present invention) (hereinafter referred to as mapping data) is accepted.

  The schema input unit 111, the pattern data input unit 112, and the mapping information input unit 113 described above, via the screen 200 shown in FIG. 5, the conversion source schema and the conversion destination schema, the conversion source data, the conversion destination data, and the mapping data Accept. As shown in FIG. 5, the screen 200 includes a mapping data input field 201, a conversion source schema input field 202, a conversion destination schema input field 203, a conversion source data input field 204, and a conversion destination data input field 205. It has.

  In the conversion source data input field 204 and the conversion destination data input field 205, the conversion source data and the conversion destination data are displayed as they are, and the user can edit them with a keyboard or the like. The pattern data input unit 112 receives a file name specification from the user, reads the XML data stored in the file corresponding to the specified file name, and displays the read XML data in the input field 204 or 205. You may do it.

  In the conversion source schema input field 202 and the conversion destination schema input field 203, a tree structure of XML data is displayed. The user may be able to edit the order of items and the parent-child relationship by operating a mouse, a keyboard, or the like. In the input columns 202 and 203, all the elements constituting the XML data are displayed in the depth priority order. The schema input unit 111 receives designation of a file name from the user, reads a schema described in a file corresponding to the designated file name, analyzes the read schema, and inputs a tree structure of XML data. You may make it display on 202 and 203. FIG.

  In the mapping data input field 201, the user can associate elements by connecting the conversion source element and the conversion destination element with a line by operating the mouse. In addition to the one-to-one correspondence between the conversion source element and the conversion destination element, one-to-multiple or multiple-to-one association may be used. In this case, for example, an icon indicating processing such as division, combination, or repetition is combined on a line segment connecting the conversion source element and the conversion destination element, such as combining a plurality of conversion source elements into one conversion destination element. Try to arrange. For example, in the example of FIG. 5, a “repeat” icon indicating that the element repeats is arranged between the “address” element of the conversion source element and the “employee” element of the conversion destination element. Between the “firstname” element and “lastname” element of the original element and the “name” element of the conversion destination element, a “combine” icon indicating that the two conversion source elements are combined is arranged.

  Of the association between the conversion source element and the conversion destination element input in the input field 201, the range associated with the conversion source element “name” by combining the conversion source elements “firstname” and “lastname” An example of mapping data 600 representing 500 is shown in FIG.

  The range 500 includes a “firstname” element 501 and a “lastname” element 502 as conversion source elements, and a “name” element 503 as a conversion destination element. The “firstname” element 501 and the “lastname” element 502 are connected to the “join” process 504 by the line segment 505 and the line segment 506, and the “join” process 504 is connected to the “name” element 503 of the conversion destination element. They are connected by a line segment 507.

  The association between the conversion source element and the conversion destination element included in the range 500 as described above is expressed as a “connector” object in the mapping data 600.

  Each object included in the mapping data 600 includes two areas for storing references to other objects (hereinafter referred to as reference holding areas) on the input side and the output side.

  In the example of FIG. 6, the mapping data 600 corresponding to the range 500 includes objects 601 and 602 that represent conversion source elements, an object 603 that represents a conversion destination element, an object 604 that represents processing, and a conversion source element. And line segments 505 and 506 for associating the process with each other and objects 605 to 607 representing the line segment 507 for associating the process with the conversion destination element. The “firstname” object 601 stores a reference to the “connector” object 605 in the output-side reference holding area, and the “lastname” object 602 stores a reference to the “connector” object 606 in the output-side reference holding area. Is stored. In the “connector” object 605, a reference to the “firstname” object 601 is stored in the reference holding area on the input side, and a reference to the “join” object 604 is stored in the reference holding area on the output side. In the “join” object 604, references to the “connector” objects 605 and 606 are stored in the reference holding area on the input side, and a reference to the “connector” object 607 is stored in the reference holding area on the output side. The In the “name” object 603, a reference to the “connector” object 607 is stored in the reference holding area on the input side, and in the “connector” object 607, a reference to the “join” object 604 is stored in the reference holding area on the input side. And a reference to the “name” object 603 is stored in the reference holding area on the output side.

  The mapping data input unit 113 receives input of association between the conversion source element and the conversion destination element, and stores the received association between the conversion source element and the conversion destination element in the memory as the mapping data 600 as described above. . Also, the mapping data input unit 113 receives a conversion rule described in XSLT, generates mapping data 600 from the received conversion rule, and displays a line segment or an icon in the input field 201 based on the generated mapping data 600. You can also. In this case, the mapping data input unit 113 is an object corresponding to the conversion source element among the objects included in the generated mapping data 600 (in the example of FIG. 6, the “firstname” object 601 and the “lastname” object 602). ) To obtain the reference to the “connector” object stored in the reference holding area on the output side, and to perform various processing stored in the reference holding area on the output side of the “connector” object indicated by the acquired reference A reference to a corresponding object (in the example of FIG. 6, a “join” object 604) or an object corresponding to the conversion destination element (in the example of FIG. 6, a “name” object 603) is acquired, Enter the correspondence between the conversion source element and the process or conversion destination element corresponding to the object indicated by the acquired reference. To be displayed by line segments in the column 201.

  The conversion rule generation unit 114 generates a conversion rule 701 described in XSL based on the mapping data 600, and stores the generated conversion rule 701 in the conversion rule storage unit 153. FIG. 7 is a diagram illustrating an example of the conversion rule 701 generated based on the mapping data 600 illustrated in FIG. As shown in FIG. 7, in the conversion rule 701, a template “<xsl: template name =” to “>” is described for each conversion source element, and if the conversion source element has a child element, the child element is created. Template call "<xsl: call-template name =" ~ "/>" is described. In each template, describe "<xsl: element name =" ~ "" to output the conversion destination element, and output the contents of the conversion source element as <xsl: value- of select = "~" /> "is described. In the conversion rule 701, the conversion source element is specified by an expression in XPath. Note that the range 500 described above is expressed as a “func_name” template in the example of FIG. 7, and the concatenation process is a “concat” function that combines the “firstname” element, the blank character, and the “lastname” element. Is described in the argument of “<xsl: value-of select =” to “/>”.

  The data conversion unit 115 reads the conversion source data from the file indicated by the conversion source file for each of the pattern data stored in the pattern data storage table 152, and the conversion rule generation unit 114 generates the read conversion source data. By starting the XSLT engine by giving the conversion rule, XML data obtained by converting the conversion source data according to the conversion rule (hereinafter referred to as test data, which corresponds to the conversion data of the present invention) is generated.

  The data comparison unit 116 compares the element of the test data generated by the data conversion unit 115 with the element of the conversion destination data included in the pattern data. When the elements of the test data and the elements of the conversion destination data do not match, the data comparison unit 116 generates data indicating the difference regarding the mismatched elements (hereinafter referred to as difference data), and stores the generated difference data as differences. Register in table 154. Details of the comparison processing by the data comparison unit 116 will be described later.

  A configuration example of the difference storage table 154 is shown in FIG. As shown in the figure, the difference data stored in the difference storage table 154 includes an XPath indicating a conversion destination element that does not match the element of the test data, a pattern number of the pattern data, expected data, actual data, and an explanation. Contains. The content of the conversion destination element is set in the expected data, and the content of the test data element that does not match is set in the actual data. In the description, an explanation about the difference is set. In this embodiment, when the element type is different, the type is different, when the content of the element is different, the value is different, when the element name is different, the tag name is different, and the element attribute is “Different attributes” is set when they are different.

  The difference display unit 117 displays the difference between the conversion destination data and the test data on the display device 105 based on the difference data stored in the difference storage table 154. Details of the difference display processing by the difference display unit 117 will be described later.

  The template data generation unit 118 generates a template of XML data based on the schema. The template data generation unit 118 generates XML data describing tags with empty contents for all elements defined in the conversion source schema and the conversion destination schema, thereby generating the template of the conversion source data and the conversion destination data. Generate. Details of the XML data template generation processing by the template data generation unit 118 will be described later.

  The template data display unit 119 displays a template of XML data generated by the template data generation unit 118 on the display device 105. For example, the template data display unit 119 displays the template of the conversion source data in the input column 204 and the template of the conversion destination data in the input column 205 on the above-described screen 200 so that the user can edit the XML data. To.

  Hereinafter, processing by the information processing apparatus 100 of the present embodiment will be described.

== Verification process ==
As described above, the information processing apparatus 100 generates the test data obtained by converting the conversion source data by giving the conversion source data and the conversion rule to the XSLT engine, and compares the generated test data with the conversion destination data. Verify correctness of conversion rules. When the test data and the conversion destination data do not match, the information processing apparatus 100 displays a difference to assist the user in correcting the conversion rule or the like.

  FIG. 9 is a PAD diagram showing the flow of conversion rule verification processing in the information processing apparatus 100 of this embodiment. The process shown in FIG. 9 is performed, for example, by placing a button on the above-described screen 200 in FIG. 5 and when the user presses the button, or when the mapping data is changed. To be executed regularly at regular time intervals.

  The conversion rule generation unit 114 generates a conversion rule based on the mapping data 600 (S1001), and the following processing is performed for each of the pattern data stored in the pattern data storage table 152 (S1002). The data conversion unit 115 generates test data obtained by converting the conversion source data by executing the XSLT engine by giving the conversion source data included in the pattern data and the conversion rule generated by the conversion rule generation unit 114 Data conversion processing is performed (S1003). The data comparison unit 116 performs data comparison processing described later (S1004). If the above processing is performed for all pattern data and there is a difference between the test data and the conversion destination data, that is, if difference data is registered in the difference storage table 154 (S1005: true), the difference The display unit 117 performs a difference display process described later (S1006).

== Data comparison ==
FIG. 10 is a PAD showing the flow of data comparison processing.
The data comparison unit 116 converts each of the conversion source data and the test data into accessible data (hereinafter referred to as DOM data) in accordance with DOM (Document Object Model) rules (S1101). In addition, a well-known conversion process can be used for the process which converts XML data into DOM data. The data comparison unit 116 has the nodes shown in FIG. 11 for the DOM data obtained by converting the conversion source data (hereinafter referred to as conversion source DOM data) and the DOM data obtained by converting the test data (hereinafter referred to as test DOM data). A comparison process is performed (S1102).

  The data comparison unit 116 extracts one node from each of the conversion source DOM data and the test DOM data, and extracts a node from the conversion source DOM data (hereinafter referred to as a conversion source node) and a node extracted from the test DOM data ( The types of test nodes are compared (S1201). Here, the node type includes a document node, an element node, and a text node. The document node is a node that represents the entire DOM data, and serves as a root of the DOM data. An element node or the like is set as a child of the document node. The element node is a node indicating an element of XML data or an attribute of the element, and has a node name corresponding to the element name or attribute name. The text node is a node indicating the content of an element or attribute, and has a character string value.

  When the node types are different (S1202: true), the data comparison unit 116 indicates that the XPath is the XPath indicating the transformation source node, the pattern number is the pattern number of the pattern data, and the expected data is the node name of the transformation source node. Difference data whose actual data is the node name of the test node and whose description is “different type” is generated, and the generated difference data is registered in the difference storage table 154 (S1203).

  On the other hand, if the node types are the same (S1202: false), the data comparison unit 116 checks whether the node type is a document node or an element node (S1204), and the node type is a document node or element node. If (S1204: true), the process proceeds to (S1205).

  If the node type is an element node (S1205: true), the data comparison unit 116 compares the node name of the conversion source node with the node name of the test node (S1206), and if the node names are different (S1207). : True), XPath is the XPath indicating the transformation source node, the pattern number is the pattern number of the pattern data, the expected data is the node name of the transformation source node, the actual data is the node name of the test node, Difference data whose description is “tag name is different” is generated, and the generated difference data is registered in the difference storage table 154 (S1208). The data comparison unit 116 compares the attribute set in the conversion source node with the attribute set in the test node (S1209), and if the attribute name or content is different (S1210: true), XPath is the XPath indicating the transformation source node, the pattern number is the pattern number of the pattern data, and the difference data having the description “different attribute” is generated, and the expected data of the generated difference data is added to the transformation source node Set a character string that includes the node name of the node and the attribute name and content of the attribute of the transformation source node, and the actual data of the difference data includes the node name of the test node and the attribute name and content of the attribute of the test node A character string is set and registered in the difference storage table 154 (S1211).

Next, the data comparison unit 116 acquires the number of nodes that are children of the node (hereinafter referred to as the number of child nodes) from each of the conversion source DOM data and the test DOM data (S1212), and the acquired number of child nodes is If they are different (S1213: true), XPath is the XPath indicating the transformation source node, the pattern number is the pattern number of the pattern data, the expected data is the node name of the transformation source node, and the actual data is the test node. The difference data having the description “the number of child elements is different” is generated, and the generated difference data is registered in the difference storage table 154 (S1214).
If the number of child nodes is 1 or more (S1215: true), node comparison processing is recursively performed for each node that is a child of the transformation source node (S1216) (S1217).

  On the other hand, if the node type is neither a document node nor an element node (S1204: false), and if the node type is a text node (S1218: true), the data comparison unit 116 determines the value of the conversion source node and the test. The node value is compared (S1219). If the values are different (S1220: true), XPath is the XPath indicating the conversion source node, the pattern number is the pattern number of the pattern data, and the expected data is converted. Difference data that is the value of the original node, the actual data is the value of the test node, and the description is “differing in content” is generated, and the generated difference data is registered in the difference storage table 154 (S1221).

== Difference display processing ==
FIG. 12 is a PAD showing the flow of the difference display process.
For each pattern data stored in the pattern data storage table 152 (S1301), the difference display unit 117 registers the difference data in which the pattern number matching the pattern number of the pattern data is set in the difference storage table 154. If the difference data is not registered in the difference storage table 154 (S1302: true), the pattern data conversion source file and the conversion destination file and “x” are displayed on the screen 200 (S1303). If false, the pattern data conversion source file and the conversion destination file and “◯” are displayed on the screen 200 (S1304).

  Next, for each difference data stored in the difference storage table 154 (S1305), the difference display unit 117 identifies the element corresponding to the XPath of the difference data from the elements defined by the conversion destination schema, and displays the screen. In 200, an “x” icon is displayed in the element name of the identified element (S1306). Further, the difference display unit 117 displays the explanation of the difference data, the expected data, the actual data, and the XPath on the screen 200.

  An example of the screen 200 displayed by the difference display unit 117 is shown in FIG. As shown in the figure, the screen 200 includes a list display column 401 that displays a conversion source file and a conversion destination file for each pattern data, and an information display column 402 that displays an error message and the like. In the example of FIG. 13, the conversion source file and the conversion destination file are displayed in the list display column 401 along with “◯” or “×” for the three pattern data. The row where “x” is displayed indicates that the conversion source data is not converted as scheduled for the pattern data of the pattern number “2” and the difference data is registered. Further, the expected data, the actual data, and the XPath of the difference data are displayed in the information display column 402.

  Among the elements of the conversion destination data defined by the conversion destination schema, “x” icons 403 are displayed for the elements indicated by the XPath of the difference data.

  In the list display field 401, a line indicating a file storing the XML data displayed in the input field 204 and the input field 205 may be highlighted.

  Further, each input field on the screen 200 may be made uneditable while the data verification process is being performed, and each input field may be made editable again when difference data is registered. In addition, when difference data is registered, there is often a problem with any of the conversion source schema, conversion source data, conversion destination schema, conversion destination data, and conversion rules, so that the user can edit again. A prompt message may be output.

== Effect ==
As described above, according to the information processing apparatus 100 of the present embodiment, the test data obtained by converting the conversion source data according to the conversion rule input by the user is compared with the conversion destination data, and the difference is output. Can do. Therefore, the user can easily determine whether or not the conversion rule defines the expected conversion process, and the conversion rule can be easily verified.

  In the information processing apparatus 100 according to the present embodiment, a plurality of pattern data can be registered in the pattern data storage table 152 in advance, so that conversion rules can be verified for various XML data. Therefore, the conversion rule verification accuracy can be improved. Further, since the information processing apparatus 100 collectively performs verification processing for a plurality of pattern data, the conversion rule can be efficiently verified.

  In addition, when the user adds a new conversion definition to the conversion rule, it is possible to add pattern data for verification related to the added conversion definition. Therefore, it is possible to prevent so-called degradation, in which other conversion processing is affected by changing the conversion rule.

== Display of correction candidates ==
The difference display unit 117 searches the conversion source data for the conversion source element having the content that matches the content of the conversion destination element indicated by the XPath of the difference data, and converts the searched conversion source element and the conversion destination indicated by the XPath of the difference data. The association with the element can also be displayed as a correction candidate. FIG. 14 shows the flow of correction candidate display processing.

The difference display unit 117 performs the following processing for each of the difference data stored in the difference storage table 154 and whose description is “different value” (S1401).
The difference display unit 117 acquires the contents of the conversion destination element indicated by the XPath of the difference data from the conversion destination data (S1402), all the conversion source elements constituting the conversion source data (S1403), and converts the conversion source data into the conversion source. The content of the element is acquired (S1404), and when the content of the conversion destination element matches the content of the conversion source element (S1405: true), the correspondence between the conversion destination element and the conversion source element is displayed on the screen 200 as a correction candidate. (S1406).

  An example of a screen 200 on which correction candidates are displayed is shown in FIG. In the example in the figure, a correspondence is created that converts the source element “email” to the destination element “birthday” and the source element “birthday” to the destination element “email”. ing. Here, the difference display unit 117 displays a correspondence candidate between the conversion destination element and the conversion source element with a dotted line 411.

  As described above, when the test data and the conversion destination data do not match, the information processing apparatus 100 according to the present embodiment can display the correspondence between the conversion source element and the conversion destination element having the same content. it can. Therefore, even when the user inputs an incorrect association, the user can correct the association with reference to the correction candidate display. Therefore, the conversion rule can be corrected efficiently.

  When the correction candidates are displayed as described above, the mapping data 600 described above includes an object indicating the correction candidate dotted line 411, and the reference holding area on the input side of the correction candidate dotted line 411 includes A reference to the object corresponding to the conversion source element is stored, and the reference to the object corresponding to the conversion destination element is stored in the reference holding area on the output side. The object corresponding to the conversion source element and the conversion destination element is provided with a reference holding area (hereinafter referred to as a correction reference holding area) for storing a reference to the object corresponding to the dotted line.

== User data input support ==
In this embodiment, it is assumed that conversion source data, conversion destination data, and mapping data are each input from a user. However, in the information processing apparatus 100 of this embodiment, a template of conversion source data and conversion destination data is used. By generating and displaying the element of the conversion destination data that matches the content of the element of the conversion source data, it is possible to reduce the trouble of creating the conversion source data, the conversion destination data, and the mapping data by the user. Hereinafter, these processes will be described.

== Output of conversion source data and conversion destination data template ==
FIG. 16 is a PAD diagram showing the flow of template generation processing of conversion source data and conversion destination data. The template data generation unit 118 newly generates conversion source data and conversion destination data (S1501), and for all elements defined in the conversion source schema (S1502), "<element name></ element name>" A tag indicating an element having an empty content is generated, and the generated tag is added to the conversion source data (S1503). Similarly, the template data generation unit 118 tags all elements defined in the conversion destination schema (S1504) to indicate elements having empty contents so as to be “<element name></ element name>”. And the generated tag is added to the conversion destination data (S1505).

  As described above, a template of conversion source data and conversion destination data in which elements having empty contents are described is generated based on the conversion source schema and the conversion destination schema. The generated conversion source data and conversion destination data are displayed in the input field 204 and the input field 205 of the screen 200 shown in FIG. 5 by the template data display unit 119, and can be edited by the user. Thereby, it is possible to reduce the time and effort for the user to input the tag, which is convenient.

  Here, the template data generation unit 118 can generate a default value corresponding to the type of the element and use it as the content of the element. FIG. 17 shows a flow of template generation processing for setting a default value according to the element type.

  The template data generation unit 118 newly generates conversion source data and conversion destination data (S1601), and sets the counter to 1 (S1602). The template data generation unit 118 performs the following processing for all elements defined in the conversion source schema (S1603).

  The template data generation unit 118 acquires the element type from the conversion source schema (S1604), and if the acquired element type is a numerical type (S1605: true), the counter is set to an 8-digit numerical value “<element A tag described so that “name> 8-digit numerical value </ element name>” is generated, and the generated tag is added to the conversion source data (S1606). If the element type is not a numerical type (S1605: false), the template data generation unit 118 describes the counter as a three-digit numerical value such that “<element name> str three-digit numerical value </ element name>”. The generated tag is generated, the generated tag is added to the conversion source data (S1607), and the counter is incremented (S1608).

  If the description format related to the content of the element is defined in the conversion source schema or the conversion destination schema, the default value of the element may be generated so as to follow the description format.

The template data generation unit 118 generates conversion source data by performing the above processing for all elements defined in the conversion source schema.
Next, the template data generation unit 118 initializes the counter to 1 again (S1609), and generates the template of the conversion destination data in the same manner as the generation of the conversion source data template. That is, the template data generation unit 118 acquires element types from the conversion destination schema (S1611) for all elements defined in the conversion destination schema (S1610), and if the acquired element type is a numeric type ( S1612: true), a tag described as “<element name> 8-digit number </ element name>” with an 8-digit numeric value is added to the conversion destination data (S1613), and the element type is numeric. If the type is other than the type (S1612: false), a tag described as “<element name> three-digit numerical value </ element name>” is added to the conversion destination data as a three-digit numerical value (S1614). ), The counter is incremented (S1615).

  As described above, the template data generation unit 118 generates a template of conversion source data and conversion destination data composed of elements in which contents such as “00000001” and “str001” are set. The conversion source data and the conversion destination data generated as described above are displayed in the input column 204 and the input column 205 of the screen 200 shown in FIG. 5 by the template data display unit 119, and can be edited by the user. . Since the user can create the conversion source data and the conversion destination data by editing the templates displayed in the input fields 204 and 205, it is possible to reduce time and effort required to create the conversion source data and the conversion destination data. . Moreover, since the value according to the type is preset as the contents of each element, it is convenient because the user can easily imagine the value to be input.

  FIG. 18 shows an example of conversion source data and conversion destination data generated by the template data generation unit 118. The upper part of FIG. 18 shows an element tree structure 711 defined by the conversion source schema and an element tree structure 712 defined by the conversion destination schema. The middle part of FIG. 18 shows a conversion source data template 721 and a conversion destination data template 722 generated by the processing of FIG. 16 described above. The lower part of FIG. 18 shows a conversion source data template 731 and a conversion destination data template 732 generated by the processing of FIG. 17 described above.

  As shown in FIG. 18, the conversion source data template 721 and the conversion destination data template 722 generated by the processing of FIG. 16 are each configured with an empty element. On the other hand, values such as “00000001” and “str001” are set as the contents of the conversion source data template 731 and the conversion destination data template 732 generated by the processing of FIG.

  Note that the data input from the user to edit the template displayed in the input fields 204 and 205 as described above corresponds to the update data of the present invention.

  When the conversion source data and the conversion destination data displayed in the input fields 204 and 205 are edited by the user, the pattern data input unit 112 stores the conversion source data and the conversion destination data in files according to instructions from the user. Then, pattern data including the file name of the stored file is generated and registered in the pattern data storage table 152.

== Output of conversion destination data template ==
In the processing shown in FIG. 16 and FIG. 17, the template of the conversion source data and the conversion destination data is generated based on the conversion source schema and the conversion destination schema. However, the input of the conversion source data and the mapping data is accepted and the conversion source data is received. A template of the conversion destination data may be generated by converting.

  FIG. 19 shows a flow of processing for converting the conversion source data and generating a model of the conversion destination data. The process shown in FIG. 19 is performed after the user inputs conversion source data and mapping data into the input field 204 and the input field 201. The conversion source data is generated by the process shown in FIG. 16 or FIG. It is good also as what is done.

  The conversion rule generation unit 114 generates a conversion rule from the mapping data (S1701). The data conversion unit 115 converts the conversion source data according to the conversion rule by starting the XSLT engine by giving the conversion source data input in the input field 204 and the conversion rule generated by the conversion rule generation unit 114. Test data is generated (S1702). The template data display unit 119 displays the test data generated by the data conversion unit 115 as the conversion destination data in the input field 205 of the screen 200 (S1703).

  As described above, the input field 205 displays a template of the conversion destination data obtained by converting the conversion source data and can be edited by the user. Therefore, since the user can create the conversion destination data by editing the above template, it is possible to reduce the time and effort required to create the conversion destination data.

  The pattern data input unit 112 stores the conversion source data and the conversion destination data input to the input fields 204 and 205 in files, generates pattern data including the file names of the stored files, and stores the pattern data. Register in the table 152.

== Display of mapping candidates ==
Next, a mapping candidate display process for displaying a correspondence candidate (hereinafter referred to as a mapping candidate) between a conversion source element and a conversion destination element will be described. FIG. 20 is a PAD showing the flow of the mapping candidate display process. FIG. 21 is a diagram showing a work table (hereinafter referred to as a work list) used for the mapping candidate display process. As shown in FIG. 21, a pattern number, a conversion source path, and a conversion destination path are registered in association with each other in the work list. The conversion source path is an XPath indicating an element of the conversion source data, and the conversion destination path is an XPath indicating an element of the conversion destination data.

  The mapping data input unit 113 initializes the work list to be empty (S1801), and performs the following processing on each pattern data stored in the pattern data storage table 152 (S1802).

  The mapping data input unit 113 reads the conversion source data and the conversion destination data from the pattern data conversion source file and the conversion destination file (S1803), and converts each of the conversion source elements constituting the conversion source data (S1804). The contents of the element are acquired (S1805). The mapping data input unit 113 acquires the contents of the conversion destination element for each of the conversion destination elements constituting the conversion destination data (S1806) (S1807), and the contents of the conversion source element match the contents of the conversion destination element. In this case (S1808: true), the pattern number of the pattern data, the XPath indicating the conversion source element, and the XPath indicating the conversion destination element are associated with each other and registered in the work list (S1809).

  Next, the mapping data input unit 113 counts the number of pattern data stored in the pattern data storage table 152 (S1810), and extracts a combination of conversion source paths and conversion destination paths from the work list without duplication (S1810). S1811). The mapping data input unit 113 counts the number of records that match the conversion source path and the conversion destination path from the work list for all the extracted combinations (S1812).

  If there is a combination in which the number of records matches the number of the pattern data among the above combinations (S1814: true), the mapping data input unit 113 sets each of the combinations in which the number of records and the number of pattern data match ( In step S1815, the conversion source element of the conversion source schema indicated by the conversion source path and the conversion destination element of the conversion destination schema indicated by the conversion destination path are displayed in association with each other on the screen 200 (S1816).

  An example of a screen 200 on which mapping candidates are displayed is shown in FIG. In FIG. 22, a dotted line 411 connecting the change source element and the change destination element represents the association between the conversion source element indicated by the conversion source path and the conversion destination element indicated by the conversion destination path.

  As described above, the information processing apparatus 100 according to the present embodiment can display the association between the conversion source element and the conversion destination element based on the change source schema and the change source data, and the change destination schema and the change destination data. it can. Therefore, the user can input the mapping data with reference to the above association, and can input efficiently.

  Note that the above mapping candidate display process may be performed according to an instruction from the user, or automatically performed when the change source schema and the change source data, and the change destination schema and the change destination data are input. You may do it. Further, the mapping candidate display process may be performed while the user is performing mapping data input work in the input field 201.

  In the above mapping candidate display process, only matching elements in all pattern data are displayed in association with each other. However, the present invention is not limited to this, and the change source data and changes displayed in the input fields 204 and 205 are displayed. The element association may be displayed based on the previous data. In this case, in FIG. 20 described above, the mapping data input unit 113 empties the work list (S1801), and then converts the conversion source data and the conversion destination data displayed in the input fields 204 and 205 (S1804) to (S1804) to ( The processing of S1809) is performed, and the association between the conversion source element and the conversion destination element is displayed for each combination registered in the work list.

  Further, in the processing of FIG. 20, the association is searched for all the elements at once. However, the present invention is not limited to this. For example, for the change source element selected by the user, a change in which the contents match from the change destination data. A destination element may be searched, and the association between the searched change destination element and the change source element selected by the user may be displayed.

  In the present embodiment, XML structured tree-structured data is assumed as structured data, but the present invention is not limited to this, and data structured in various formats can be used. For example, CSV (Comma Separated Values) format or tab-delimited text format table structure data can be used. Here, the schema that defines the structure of the table-structured data as described above can be described in, for example, SQL (Structured Query Language).

  In the present embodiment, in the screen 200, only the elements constituting the XML data are displayed in the input fields 202 and 203, and only the mapping data for associating the conversion source element with the conversion destination element is input in the input field 201. However, the present invention is not limited to this, and the attributes of each element may be displayed. In this case, in the input fields 202 and 203, the elements constituting the XML data are displayed in the depth priority order, and the attributes of each element are also displayed as child nodes of each element. , “◇” is displayed in the attribute name of the attribute.

  Although the present embodiment has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

2 is a diagram illustrating a hardware configuration of the information processing apparatus 100. FIG. 2 is a diagram illustrating a software configuration of the information processing apparatus 100. FIG. 3 is a diagram illustrating a configuration example of a schema storage unit 151. FIG. It is a figure which shows the structural example of the pattern data storage table. It is a figure which shows an example of the screen 200 which the information processing apparatus 100 displays. 6 is a diagram illustrating an example of mapping data 600 expressing a range 500. FIG. It is a figure which shows an example of the conversion rule 701 produced | generated by the conversion rule production | generation part 114. FIG. It is a figure which shows the structural example of the difference storage table 154. 6 is a PAD showing a flow of conversion rule verification processing in the information processing apparatus 100. FIG. It is a PAD figure which shows the flow of a data comparison process. It is a PAD figure which shows the flow of a node comparison process. It is a PAD diagram showing a flow of a difference display process. It is a figure which shows an example of the screen 200 displayed by the difference display part. It is a PAD showing a flow of correction candidate display processing. It is a figure which shows an example of the screen 200 on which the correction candidate was displayed. It is a PAD figure which shows the flow of the template production | generation process of conversion source data and conversion destination data. FIG. 10 is a PAD diagram showing a flow of a template generation process for setting a default value according to an element type. It is a figure which shows an example of the model of conversion source data and conversion destination data. It is a PAD showing a flow of processing for converting conversion source data and generating a model of conversion destination data. It is a PAD figure which shows the flow of a mapping candidate display process. It is a figure which shows the operation | work list used for a mapping candidate display process. It is a figure which shows an example of the screen 200 on which the mapping candidate was displayed.

Explanation of symbols

100 Information processing apparatus 101 CPU
102 memory 103 hard disk 104 video memory 105 display device 106 input device 111 schema input unit 112 pattern data input unit 113 mapping data input unit 114 conversion rule generation unit 115 data conversion unit 116 data comparison unit 117 difference display unit 118 template data generation unit 119 Template data display unit 151 Schema storage unit 152 Pattern data storage table 153 Conversion rule storage unit 154 Difference storage table 200 Screen 201 Input field for mapping data 202 Input column for conversion source schema 203 Input column for conversion destination schema 204 Input of conversion source data Field 205 Conversion destination data input field 401 List display field 402 Information display field 403 Icon 411 Dotted line 412 Dotted line 500 Range 501 “firstname” element 502 “lastname” Element 503 “name” element 504 “join” processing 505 line segment 506 line segment 507 line segment 601 “firstname” object 602 “lastname” object 603 “name” object 604 “join” object 605 “connector” object 606 “connector” object 607 "Connector" object 701 Conversion rule

Claims (10)

Execution of a program for converting first data structured in a first format composed of a plurality of first elements into second data in a second format composed of a plurality of second elements An information processing method for verifying correctness of a conversion rule in which a relationship between the first element and the second element is defined,
An information processing apparatus including a CPU and a memory is provided.
Storing the first data in the memory;
Storing verification data in the memory assuming the second data output when the first data is correctly converted into the second format by the program and the conversion rule;
The first data is converted into the second data in the second format by actually executing the program by giving the conversion rule to be verified,
The content of the second element constituting the second data after the conversion is compared with the second element constituting the verification data stored in the memory, and the mismatched second data Generating data indicating the elements of
An information processing method characterized by the above. The first element constituting the first XML data, which is given when executing the program for converting the first XML data defined by the first schema into the second XML data defined by the second schema And an information processing method for verifying the correctness of a conversion rule in which the relationship between the second element constituting the second XML data is defined,
An information processing apparatus including a CPU and a memory is provided.
A first input field for inputting the first XML data, and output when the first XML data is correctly converted into a format defined by the second schema by the program and the conversion rule. A screen comprising: a second input field for inputting verification data assuming the second XML data; and a third input field for inputting an association between the first element and the second element. Display
Generating the conversion rule based on the correspondence input in the third input field;
The first data is converted into the second data by giving the generated conversion rule and executing the program,
The content of the second element constituting the second data after conversion is compared with the second element constituting the verification data input in the second input field, and a mismatch is found. Identifying the second element;
Displaying a message indicating the identified second element on the screen;
An information processing method characterized by the above. An information processing method according to claim 1,
The information processing apparatus identifies the first element having a content that matches the content of the second element that is inconsistent from the first data, and identifies the first element and the second element that have been identified. Output in association with elements,
An information processing method characterized by the above. An information processing method according to claim 1,
The information processing apparatus includes:
Storing the first data and the verification data in the memory in association with each other;
Each of the first data stored in the memory is converted to the second data by giving the conversion rule and executing the program, and the verification data corresponding to the first data Is read from the memory, the second element constituting the read verification data is compared with the second element constituting the second data after conversion, and the mismatched second elements are compared. Generating data representing the element,
An information processing method characterized by the above. An information processing method according to claim 1,
The information processing apparatus includes:
Storing metadata defining the second format of the verification data in the memory;
Based on the metadata, generates and outputs template data that is the verification data composed of the second element whose contents are empty,
Accepting input of update data for updating the template data,
Update the template data with the received update data,
Storing the updated template data in the memory as the verification data;
An information processing method characterized by the above. An information processing method according to claim 5,
The metadata defines a type of the second element,
The information processing apparatus includes:
For each of the types, content determination information that is information for determining the content of the second element is stored in the memory;
For each of the second elements constituting the verification data, the type of the second element is specified from the metadata, and the content determination information corresponding to the specified type is read from the memory and read. Determining the content of the second element based on the content determination information,
Generating the template data constituted by the second element having the determined content based on the metadata;
An information processing method characterized by the above. An information processing method according to claim 1,
The information processing apparatus includes:
Storing the first data and the conversion rule in the memory;
Generate and output template data that is the second data obtained by converting the first data by giving the conversion rule and executing the program,
Receiving input of first update data for updating the template data;
Storing the template data updated by the received first update data in the memory as the verification data;
Receiving an input of second update data for updating the conversion rule;
Updating the conversion rule with the received second update data;
Converting the first data into the second data by giving the updated conversion rule and executing the program;
An information processing method characterized by the above. An information processing method according to claim 1,
For each of the first elements constituting the first data, the information processing apparatus matches the contents of the first element among the second elements constituting the verification data. If there is a thing, outputting a correspondence between the second element and the first element whose contents match,
An information processing method characterized by the above. Execution of a program for converting first data structured in a first format composed of a plurality of first elements into second data in a second format composed of a plurality of second elements An information processing apparatus that verifies whether the conversion rule that defines the relationship between the first element and the second element is correct or not,
Storing the first data and verification data assuming the second data output when the first data is correctly converted into the second format by the program and the conversion rule; A data storage unit;
A data conversion unit that converts the first data into the second data in the second format by actually executing the program by giving the conversion rule to be verified;
The content of the second element constituting the second data after the conversion is compared with the second element constituting the verification data stored in the memory, and the mismatched second data A data comparison unit that generates data indicating the elements of
An information processing apparatus comprising: Execution of a program for converting first data structured in a first format composed of a plurality of first elements into second data in a second format composed of a plurality of second elements A program for verifying the correctness of the conversion rule in which the relationship between the first element and the second element is defined,
In an information processing apparatus including a CPU and a memory,
Storing the first data in the memory;
Storing verification data in the memory assuming the second data output when the first data is correctly converted into the second format by the program and the conversion rule;
Converting the first data into second data in the second format by actually executing the program by giving the conversion rule to be verified;
The content of the second element constituting the second data after the conversion is compared with the second element constituting the verification data stored in the memory, and the mismatched second data Generating data indicating the elements of
A program for running

Images