JP2004240507A - Xml generation device and xml generation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily generate a plurality of XML data, and to reduce man-hours for generating the XML data. <P>SOLUTION: A structure analysis part 203 develops input DTD data 11 read from a storage device A10 by a DTD input part 202 onto a memory as a DTD object. A path compounding part 208 compounds path information based on generation option information and generation default information from a generation option inputting part 201 according to the DTD object on the memory, and develops a composite DOM object onto the memory. Also, the path compounding part 208 compounds the path information by referring to XML conversion NV list data and input NV list data 13 as necessary. Then, an XML generation part 209 generates output XML data 31 based on the composite DOM object. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an XML generation device that generates XML data based on definition information that defines a data structure of XML data, and an XML generation program.
[0002]
[Prior art]
In an affiliated system such as B2Bi (Business to Business Integration) or EAI (Enterprise Application Integration), when conducting a continuity test using test data between companies, an XML (Extensible Markup Language data using an Extensible Markup) is used when conducting a continuity test using test data between companies. There is. It is convenient to have template data (hereinafter referred to as a template) when formulating business specifications in system construction.
[0003]
Since the XML data has a complicated structure, editing work may be troublesome. Patent Literature 1 discloses a data structuring method capable of improving work efficiency and reducing a burden on an operator when generating XML data. In the data structuring method described in Patent Document 1, document structure constraint information such as DTD (Document Type Definition) is input. Then, a document structure such as text document data to be structured is edited based on an instruction from an operator using the graphical user interface.
[0004]
[Patent Document 1]
JP 2001-101183 A (Page 5-8, FIG. 1, FIG. 4-6)
[0005]
[Problems to be solved by the invention]
In the data structuring method described in Patent Literature 1, work efficiency is improved by realizing a structure in which structuring is instructed while looking at the actual document itself to be structured, thereby reducing the burden on the worker. Reduced. However, this is merely to reduce the load when the user edits XML data or the like, and does not realize a configuration for reducing the number of steps when generating XML data. Therefore, a template for test data or XML data cannot be easily generated.
[0006]
Therefore, it is an object of the present invention to be able to easily generate a plurality of XML data, and to reduce the number of steps when generating the XML data.
[0007]
[Means for Solving the Problems]
An XML generation apparatus according to the present invention is an XML generation apparatus that generates XML data according to a specified data structure, and inputs structure information (for example, input DTD data 11) that specifies a data structure of XML data to be generated. Structure information input means (implemented by the DTD input unit 202) and correspondence information indicating the correspondence between the element indicated by the path and the number of elements or the correspondence between the element and the value of the element (for example, the input NV list data 13 ) Or existing XML data (for example, input XML data 12) as reusable information input means (implemented by the XML input unit 205 and the NV list input unit 207) for inputting as reusable information. Setting information that holds setting information (for example, generation default information) that is information for specifying a generation pattern of power XML data A storage unit (implemented by the storage device of the XML generation device 20) and a path indicating the path name and the number of elements or the value of the element for each path specified from the structure information based on the setting information and the reuse information Path information synthesizing means (realized by the path synthesizing unit 208) for generating and synthesizing information, and XML generation for generating XML data based on synthetic information (for example, synthetic DOM object) synthesized by the path information synthesizing means (Implemented by the XML generation unit 209).
[0008]
The XML generation apparatus includes setting information input means (implemented by the generation option input unit 201) for inputting setting information (for example, generation option information), and the path information synthesizing means includes setting information input by the setting information input means. The path information of the XML data may be generated and combined based on the setting information held by the setting information holding unit and the reuse information. According to such a configuration, when generating the XML data, the user can arbitrarily change a generation pattern such as an element value and an attribute value included in the generated XML data.
[0009]
The reuse information input means includes correspondence information input means (implemented by the NV list input unit 207) for inputting correspondence information as reuse information, and the path information synthesizing means receives input from the correspondence information input means. The path information included in the correspondence information may be extracted, and the extracted path information may be adopted as a synthesis target to synthesize the path information. According to such a configuration, it is possible to generate XML data by using data edited based on past accumulated data by the user as reuse data. Therefore, compared to the case of editing the XML data, it is possible to reduce processing related to the manual work of the user.
[0010]
The reuse information input means includes an XML input means (implemented by the XML input unit 205) for inputting existing XML data as reuse information, and the path information synthesizing means includes an existing XML data input by the XML input means. Is extracted, and the extracted path information is adopted as a synthesis target to synthesize the path information. The XML generation unit converts the new XML data based on the synthesis information synthesized by the path information synthesis unit. It may be generated. According to such a configuration, by generating new XML data by reusing the existing XML data, it is possible to reduce processing related to the manual work of the user.
[0011]
The path information synthesizing means may synthesize the path information by preferentially adopting the path information included in the correspondence information over the path information included in the existing XML data. According to such a configuration, it is possible to generate XML data in which the reuse data edited by the user is preferentially reflected.
[0012]
When the path information specified from the structure information is not included in the correspondence information or the existing XML data, the path information combining unit may combine the path information according to the generation pattern specified in the setting information. . According to such a configuration, the XML data can be generated even when the path information corresponding to the reuse data edited or specified by the user is not included.
[0013]
The XML generation apparatus performs correspondence information (for example, output NV list data) based on synthesis information synthesized by the path information synthesis unit, structure information input by the structure information input unit, or existing XML data input by the XML input unit. 32, which is provided with correspondence information generation means (realized by the NV list generation unit 211, the DTD conversion unit 204, or the XML conversion unit 206) for generating DTD conversion NV list data or XML conversion NV list data). There may be. According to such a configuration, the user can easily edit the reuse data based on the structure information or the existing XML data as a result of combining the path information. Therefore, the reuse data edited by the user can be reused at the next generation of the XML data.
[0014]
The reuse information input means may input the XML data generated by the XML generation means or the correspondence information generated by the correspondence information generation means as reuse information. According to such a configuration, the generated XML data and the data edited by the user can be reused as reusable data at the next generation of the XML data.
[0015]
An XML generation program according to the present invention is an XML generation program mounted on an XML generation apparatus having setting information holding means for holding setting information which is information for specifying a generation pattern of XML data to be generated. Processing for inputting structure information for designating the data structure of the XML data to be generated, and correspondence information indicating the correspondence between the element indicated by the path and the number of elements or the correspondence between the element and the value of the element, A process of inputting XML data as reuse information, and generating path information indicating a path name and the number of elements or the value of an element for each path specified from the structure information based on the setting information and the reuse information. It is characterized by executing a process of combining and a process of generating XML data based on the combined information obtained by combining the path information.
[0016]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of the configuration of an XML generation device according to the present invention. As shown in FIG. 1, the XML generation device 20 obtains data stored in the storage device A10, generates XML data, and outputs the generated XML data to the storage device B30. The XML generation device 20 is realized by an information processing device such as a personal computer or a server. The storage device A10 and the storage device B30 are realized by a magnetic storage device or the like. Note that the storage device A10 and the storage device B30 may be realized by a semiconductor storage device or the like.
[0017]
In the present embodiment, the XML generation device 20 generates XML data based on each set value input from a user or the like according to the data structure definition information included in the DTD data stored in the storage device A10. When generating the XML data, the XML generation device 20 refers to data stored in the storage device A10 other than the DTD data. The data that the XML generation device 20 refers to when generating the XML data includes existing data generated by the XML generation device 20 in the past and edited data created by the user. That is, the XML generation device 20 generates XML data by reusing existing data generated in the past. Further, the XML generation device 20 generates XML data by using data edited and created by a user using an editor or the like based on existing data.
[0018]
The storage device A10 stores input DTD data 11 including information on a data structure of XML data to be generated, and input XML data 12 and input NV list data 13 referred to by the XML generation device 20 when generating XML data. . The input DTD data 11 is DTD data including definition information of the data structure of the generated XML data. The input XML data 12 is XML data generated by the XML generation device 20 in the past. The input NV list data 13 is NV list (Name and Value List) data generated by the XML generation device 20 in the past.
[0019]
The NV list data is text data in which the correspondence between each element and the number of elements and the correspondence between each element and the value of the element are listed. In the NV list data, the correspondence between each element is displayed by associating each element with the number of elements or each element and the value of the element with “=”. For example, the correspondence between the elements is displayed as “element name = number of elements” or “element name = element value”. Also, for example, using “,” instead of “=”, the correspondence between “element name, number of elements” or “element name, element value” and each element is displayed in CSV (Comma Separated Value) format. Good. The input NV list data 13 is, for example, NV list data in which information on the correspondence relationship between elements included in the XML data generated in the past by the XML generation device 20 is listed. Therefore, the user can easily edit the input NV list data 13 using editing software such as an editor.
[0020]
The input data including the definition information of the data structure of the generated XML data is not limited to the DTD data. For example, an XML schema including definition information of a data structure of XML data may be used.
[0021]
As shown in FIG. 1, the XML generation device 20 includes a generation option input unit 201 for inputting each setting value for specifying a generation pattern of XML data, and a DTD input unit 202 for inputting input DTD data 11 from the storage device A10. A structure analysis unit 203 that analyzes the input DTD data 11, a DTD conversion unit 204 that converts the input DTD data 11 into NV list data, an XML input unit 205 that inputs the input XML data 12 from the storage device A10, An XML conversion unit 206 that converts the input XML data 12 into NV list data, an NV list input unit 207 that inputs the input NV list data 13 from the storage device A10, and a path synthesis unit that synthesizes path information based on each input data. An XML generator 209 for generating XML data based on the synthesis result; Comprising an XML output unit 210 for outputting the XML data, the NV list generating unit 211 for generating NV list data based on the combined result, the NV list output unit 212 for outputting the generated NV list data.
[0022]
The generation option input unit 201 is realized by an input device such as a keyboard and a mouse, and a control unit of the XML generation device 20. The generation option input unit 201 inputs each setting value that specifies a generation pattern of XML data according to an input instruction from a user as necessary. Accept. Hereinafter, information including a setting value for generating XML data input according to an instruction from a user is referred to as generation option information. Instead of inputting the generation option information from the input device according to an instruction from the user, the generation option input unit 201 may read an external file including the generation option information from an external storage device and input the external file.
[0023]
Note that the XML generation device 20 holds information on default values of each set value that specifies a generation pattern of the XML data in a storage device (not shown) of the XML generation device 20 or the like. Hereinafter, the information on the default value of each setting value held by the XML generation device 20 is referred to as generation default information. Of the setting values, for the setting value input as generation option information from the generation option input unit 201, the XML generation device 20 generates XML data based on the setting value included in the generation option information. For a setting value not input as generation option information, the XML generation device 20 generates XML data based on the setting value included in the generation default information.
[0024]
The DTD input unit 202, the XML input unit 205, and the NV list input unit 207 are realized by the input / output interface unit and the control unit of the XML generation device 20. The DTD input unit 202 reads the input DTD data 11 from the storage device A10. The XML input unit 205 reads the input XML data 12 from the storage device A10 as needed. The NV list input unit 207 reads the input NV list data 13 from the storage device A10 as needed.
[0025]
The structure analysis unit 203, the DTD conversion unit 204, the XML conversion unit 206, the path synthesis unit 208, the XML generation unit 209, and the NV list generation unit 211 execute a program stored in a storage device of the XML generation device 20. It is realized by. The structure analysis unit 203 expands the data structure of the DTD data 11 input from the DTD input unit 202 as a DTD object on a memory (not shown) of the XML generation device 20. The DTD conversion unit 204 converts the input DTD data 11 into an NV list data format based on the expanded DTD object, and generates NV list data. Hereinafter, NV list data generated by converting the input DTD data 11 is referred to as DTD converted NV list data. The XML conversion unit 206 converts the input XML data 12 from the XML input unit 205 into an NV list data format, and generates NV list data. Hereinafter, NV list data generated by converting the input XML data 12 will be referred to as XML-converted NV list data.
[0026]
The path synthesis unit 208 synthesizes path information based on the DTD object expanded by the structure analysis unit 203, the generation option information from the generation option input unit 201, and the generation default information. The concept of path information will be described later. The path combining unit 208 combines the path information with reference to the XML-converted NV list data and the input NV list data 13 as necessary. The path synthesis unit 208 develops a synthesis result obtained by synthesizing the path information on a memory as a DOM (Document Object Model) object. Hereinafter, the DOM object expanded on the memory based on the synthesis result obtained by synthesizing the path information by the path synthesis unit 208 is referred to as a synthesized DOM object.
[0027]
The XML generation unit 209 converts the synthesized DOM object into a text format to generate XML data. Hereinafter, the XML data generated by the XML generation unit 209 will be referred to as output XML data 31. The NV list generation unit 211 converts the composite DOM object into the NV list format and generates NV list data. Hereinafter, the NV list data generated by the NV list generation unit 211 is referred to as output NV list data 32.
[0028]
The XML output unit 210 and the NV list output unit 212 are realized by the input / output interface unit and the control unit of the XML generation device 20. The XML output unit 210 outputs and stores the output XML data 31 generated by the XML generation unit 209 to the storage device B30. The NV list output unit 212 outputs and stores the output NV list data 32 generated by the NV list generation unit 211 to the storage device B30.
[0029]
The storage device B30 stores output XML data 31 and output NV list data 32 output from the XML generation device 20, as shown in FIG. Note that the storage device A10 and the storage device B30 may be realized by one semiconductor storage device, one magnetic storage device, or the like.
[0030]
The structure information input unit is realized by the DTD input unit 202. The reuse information input unit is realized by the XML input unit 205 and the NV list input unit. The setting information holding unit is realized by the storage device of the XML generation device 20. The path information synthesizing unit is realized by the path synthesizing unit 208. The XML generation unit is realized by the XML generation unit 209. The setting information input unit is realized by the generation option input unit 201. The XML input unit is realized by the XML input unit 205. The correspondence information input unit is realized by the NV list input unit 207. The correspondence information generation unit is realized by the NV list generation unit 211, the DTD conversion unit 204, and the XML conversion unit 206.
[0031]
FIG. 2 is an explanatory diagram illustrating an example of the content of the input DTD data 11. As shown in FIG. 2, in this example, in the input DTD data 11, a parent element "Simple" is defined, and further, child elements "One", "ZeroOrOne?", "ZeroOrMore *", "OneOrMore +" and the like are defined. You. As shown in FIG. 2, the input DTD data 11 includes child elements to which XML language symbols defining the number of times of description of elements such as “?”, “*”, And “+” are added. In this example, attribute names “idReq” and “idImp” are defined for the child element “One”. The attribute “idReq” describes a declaration “#REQUIRED” of the XML language indicating that the attribute value must be specified. The attribute “idImp” describes an XML language declaration “#IMPLIED” indicating that the attribute value can be omitted.
[0032]
In this example, as shown in FIG. 2, among the child elements defined in the parent element "Simple", one of "OrA", "OrB" and "OrC" is selected and designated. The symbol "|" of the XML language indicating that this must be done is described. When "OrA" is designated, one of the data types of "selectType 1,""selectType2," and "selectType 3" must be further selected and designated. In the present embodiment, when no set value is input as generation option information for an element having a “|” symbol, the generation default information is set to select and specify the first element. Will be described as an example.
[0033]
FIG. 3 is an explanatory diagram showing an example of the content of the input XML data 12. In this example, as shown in FIG. 3, “000001” is designated as the attribute value of the attribute “idReq” in the input XML data 12. Further, it is specified that the number of elements of the child element “OneOrMore” included in the input XML data 12 is two, and element values “data1” and “data2” are specified, respectively. The child element "OrA" is selected and specified, and "selectType 1" is selected and specified as the data type. Then, “Value A” is specified as the attribute value of the child element “OrA”.
[0034]
Note that the input XML data 12 does not necessarily need to be data that matches the data structure defined by the input DTD data 11. For example, in the input DTD data 11 shown in FIG. 2, since the attribute “idReq” is declared as #REQUIRED, the element “One” is a required element, but the input XML data 12 is data that does not include the element “One”. Is also good. Also, the input XML data 12 may declare a reference to DTD data different from the input DTD data 11 in the DTD external file declaration section.
[0035]
FIG. 4 is an explanatory diagram illustrating an example of the contents of the input NV list data 13. In this example, as shown in FIG. 4, in the input NV list data 13, three paths “/ Simple / One / @ idImp”, “/ Simple / OneOrMore +”, and “/ Simple / OneOrMore [2]” are used. Respectively, the pass values “implied”, “3” and “data 2” are designated.
[0036]
Next, the concept of path information will be described. The path indicates the relationship between the parent element and the child element using a delimiter such as “/” for each element included in the XML data or NV list data. In the present embodiment, an example will be described in which a path name is expressed by XPath (XML Path Language). For example, a path indicating the relationship between the parent element "Simple" and the child elements "One" and "OneOrMore" is expressed as "/ Simple / One / @ idReq" or "/ Simple / OneOrMore". The path information is information indicating a path name and the number of elements or a path value (for example, an element value or an attribute value).
[0037]
When symbols such as “?”, “*”, And “+” exist in the DTD data and XML data when converting the path format, the symbols are converted to the path format by adding these symbols to the end of each element name. I do. For example, paths such as “/ Simple / ZeroOrOne?”, “/ Simple / ZeroOrMore *”, and “/ Simple / OneOrMore +” are generated. If the symbol "|" exists, it is converted to a path format by adding parentheses before and after the selected element. For example, a path such as “/ Simple / (OrA | OrB | OrC)” is generated.
[0038]
For example, in the generation option information, the number of elements to which "?" And "*" are added is set to "0", the number of elements to which "+" is added is set to "1", and the path information is set. An example in which the images are combined will be described. FIG. 5 is an explanatory diagram showing an example of NV list data obtained by converting the result of combining path information by the path combining unit 208 according to the input DTD data 11 shown in FIG. 2 into an NV list. The NV list data shown in FIG. 5 has no input of the input XML data 12 and the input NV list data 13 and is data based on a synthesis result obtained by synthesizing path information based on generation option information and generation default information.
[0039]
Also, as a setting value other than the number of elements to which "?", "*", And "+" are added, the path delimiter is set to "/" and the path prefix (path prefix) is set. It is assumed that no designation is set, that a null value (undefined value) is not output as a default value of an element value or an attribute value, and that no IMPLIED attribute is output. If it is set not to output a null value, for example, a path name is output as it is as a path value.
[0040]
As shown in FIG. 5, for the path "/ Simple / One / @ idReq", "null value" is set not to be output. For example, the path name "/ Simple / One / @ idReq" is not changed. Path information is generated as a path value. For the paths “/ Simple / ZeroOrOne?” And “/ Simple / ZeroOrMore *”, the number of elements is set to “0”, so that the path information is generated as the path value “0”. Since the number of elements is “0”, no path information is generated for the paths “/ Simple / ZeroOrOne” and “/ Simple / ZeroOrMore” indicating the contents of the elements. For the path “/ Simple / OneOrMore +”, since the number of elements is set to “1”, path information is generated as a path value “1”. For the path “/ Simple / OneOrMore” indicating the content of the element, it is set that a null value is not output. For example, path information is generated using the path name “/ Simple / OneOrMore” as it is as the path value. You.
[0041]
Since the selection designation of the "|" symbol is not set, the head information is selected based on the generated default information. That is, “OrA” and “selectType1” are selected, and path information is generated based on the selection result. If the generation option information is set to select the second information, “/ Simple / (OrA | OrB | OrC) = 2” is generated as the path information, and the content of the element “OrB” Is generated. Since no output is set for the IMPLIED attribute, path information for the attribute “idImp” is not generated in this example.
[0042]
When the number of all elements to which "?", "*", And "+" are added in the generation option information is set to "1", the number of elements included in the input DTD data 11 shown in FIG. All path information can be generated. FIG. 6 is an explanatory diagram showing another example of NV list data obtained by converting the result of combining path information according to the input DTD data 11 shown in FIG. 2 into an NV list. Set values other than the number of elements including “?”, “*”, And “+” and other conditions are the same as those in FIG. That is, the path separator is set to "/", the prefix of the path is not specified, the null value is not output as the default value of the element value or the attribute value, and the IMPLIED attribute is not output. Is set.
[0043]
As shown in FIG. 6, in addition to the path information generated in FIG. 5, path information about the paths “/ Simple / ZeroOrOne?” And “/ Simple / ZeroOrMore *” is generated. That is, for the path “/ Simple / ZeroOrOne?”, Path information is generated as a path value “1”. For the path "/ Simple / ZeroOrOne" indicating the content of the element, for example, path information is generated using the path name "/ Simple / ZeroOrOne" as a path value. For “/ Simple / ZeroOrMore *”, path information is generated as a path value “1”. For the path “/ Simple / ZeroOrMore” indicating the content of the element, for example, path information is generated using the path name “/ Simple / ZeroOrMore” as a path value.
[0044]
Next, the operation will be described. FIG. 7 is a flowchart illustrating an example of a process of generating the XML data by the XML generation device 20. The DTD input unit 202 reads the input DTD data 11 from the storage device A10 (Step S101). The structure analysis unit 203 analyzes the data structure of the input DTD data 11 from the DTD input unit 202 and develops it on the memory as a DTD object (step S102).
[0045]
The generation option input unit 201 accepts input of generation option information according to an input instruction from a user and sets each set value of the generation option information (step S103). The generation option input unit 201 sets the following setting values as generation option information.
[0046]
For example, the generation option input unit 201 presets the number of elements to which symbols such as “?”, “*”, And “+” are added. The generation option input unit 201 sets a path delimiter. For example, the generation option input unit 201 sets “/” as a path separator. The generation option input unit 201 sets a prefix that is a prefix of a path. The generation option input unit 201 sets whether to output a null value as a default value of each element value or attribute value of data. Further, when an element specified as IMPLIED exists in the data, the generation option input unit 201 sets whether or not to output the element.
[0047]
If the input instruction of the generation option information has not been input from the user, the process of step S103 is not performed. When the process of step S103 is not performed, the XML generation device 20 generates XML data based on the generation default information in the following process. For the setting values that are not input as the generation option information among the setting values, the XML generation device 20 generates XML data based on the setting values included in the generation default information.
[0048]
When the file name of the input XML data is input by the user, the XML input unit 205 reads the input XML data 12 corresponding to the input file name from the storage device A10 (Step S104). If the file name has not been input by the user, the XML input unit 205 does not execute the process of step S104. That is, the XML generation apparatus 20 generates XML data without referring to the input XML data 12 in the following processing.
[0049]
When the file name of the input NV list data is input by the user, the NV list input unit 207 reads the input NV list data 13 corresponding to the input file name from the storage device A10 (Step S105). When the file name is not input by the user, the NV list input unit 207 does not execute the process of step S105. That is, the XML generation apparatus 20 generates XML data without referring to the input NV list data 13 in the following processing.
[0050]
Note that, when the file name is input from the user, instead of executing the processing of step S104 or S105, for example, the processing of step S104 or S105 may be executed according to an instruction included in the batch processing. Good.
[0051]
The order in which the processes of steps S103, S104, and S105 are performed is not limited to the order described in the present embodiment. Further, any or all of steps S103, S104, and S105 may be performed before the processing of steps S101 and S102.
[0052]
When the user inputs an instruction to convert the input DTD data 11 to NV list data, the DTD conversion unit 204 converts the input DTD data 11 based on the DTD object expanded on the memory of the XML generation device 20. The data is converted into an NV list data format to generate DTD converted NV list data (step S106). When a conversion instruction for the input DTD data 11 has not been input from the user, the DTD conversion unit 204 does not execute the process of step S106. That is, the DTD conversion unit 204 does not generate DTD conversion NV list data.
[0053]
When the user inputs an instruction to convert to NV list data, the process of step S106 is not executed, but, for example, the process of step S106 is executed according to an instruction included in the batch process. Is also good.
[0054]
The XML conversion unit 206 converts the input XML data 12 from the XML input unit 205 into a data format of an NV list and generates the data as NV list data (step S107). If the file name is not input by the user and the process of step S104 is not executed, the XML conversion unit 206 does not execute the process of step S107. That is, the XML conversion unit 206 does not generate the XML conversion NV list data.
[0055]
FIG. 8 is an explanatory diagram illustrating an example of XML conversion NV list data generated by the XML conversion unit 206. The XML conversion NV list data shown in FIG. 8 is NV list data generated by converting the input XML data 12 shown in FIG. 3 into an NV list. As shown in FIG. 8, the XML conversion unit 206 converts the input XML data 12 into an NV list according to the above-described concept of a path to generate XML converted NV list data.
[0056]
The path synthesizing unit 208 synthesizes the path information based on each setting value included in the generation option information and the generation default information according to the DTD object of the input DTD data 11 expanded on the memory (Step S108). When the XML conversion NV list data is generated, the path synthesis unit 208 synthesizes the path information with reference to the XML conversion NV list data. When the input NV list data 13 has been input, the path combining unit 208 combines the path information with reference to the input NV list data 13.
[0057]
FIG. 9 is a flowchart illustrating an example of the progress of the process in which the path combining unit 208 combines the path information. The path combining unit 208 first refers to the input NV list data 13 and determines whether or not the corresponding part of the path information exists in the input NV list data 13 (step S21). If the path information exists, the path synthesis unit 208 extracts the path information included in the input NV list data 13 (Step S22). If there is no path information of the corresponding part in step S21 or if there is no input NV list data 13, the path synthesis unit 208 refers to the XML conversion NV list data. The path synthesis unit 208 determines whether the path information of the corresponding part exists in the XML conversion NV list data (Step S23). If the path information exists, the path synthesis unit 208 extracts the path information included in the XML conversion NV list data (step S24).
[0058]
If there is no path information of the corresponding part in step S23 or if there is no XML conversion NV list data, the path combining unit 208 specifies that a null value is output as a default value in the generation option information or the generation default information. It is determined whether or not there is (step S25). If there is a designation to output a null value, the path synthesis unit 208 generates path information using the path value of the corresponding part as a null value (step S26). If there is no designation to output a null value, the path synthesis unit 208 generates path information using the path name of the corresponding part as a path value as it is (step S27). The path combining unit 208 combines the extracted or generated path information according to the procedure from step S21 to step S27. Then, the path synthesis unit expands the synthesized DOM object on the memory.
[0059]
When the path information is synthesized, the XML generation unit 209 converts the synthesized DOM object configured on the memory into a text format and generates the output XML data 31 (Step S109). Further, when an instruction to generate the output NV list data 32 is input from the user, the NV list generation unit 211 converts the combined DOM object into the NV list format and generates the output NV list data 32 (Step S110). ). When an instruction to generate the output NV list data 32 has not been input from the user, the NV list generation unit 211 does not execute the process of step S110. That is, the NV list generation unit 211 does not generate the output NV list data 32.
[0060]
Note that, when an instruction to generate the output NV list data 32 is input from the user, the process of step S110 is not executed, but the process of step S110 is executed according to, for example, an instruction included in the batch process. It may be.
[0061]
FIG. 10 is an explanatory diagram showing an example of the generated output XML data 31 and output NV list data 32. FIG. 10A shows output XML data 31 generated by the XML generation unit 209. FIG. 10B shows the output NV list data 32 generated by the NV list generation unit 211. In this example, there is no input of the input XML data 12 and the input NV list data 13, and the output XML data 31 and the output NV list data are based on the generation option information and the generation default information according to the input DTD data 11 shown in FIG. 32 will be described as an example. In step S103, the number of elements to which "?" And "*" are added is set to "0", the number of elements to which "+" is added is set to "1", and a path delimiter is set. Is set to "/", the path prefix is not specified, the null value is output as the default value of the element value and the attribute value, and the IMPLIED attribute is not output. And
[0062]
As shown in FIG. 10A, the XML generation unit 209 includes an XML declaration unit “? Xml version = '1.0' encoding = 'UTF-8'?” And a DTD external file declaration unit “! DOCTYPE Simple SYSTEM”. simple. dtd "" is automatically generated. Note that, in the XML declaration part, the part of “encoding = 'UTF-8'” that is the designation of the output character code may be set as the setting value of the generation option information in step S103.
[0063]
The XML generation unit 209 generates one tag for the element “OneOrMore” because the generation option information is set to generate one element to which “+” is added. In the present example, the output of the null value is set as the default value, so the path synthesis unit 208 synthesizes the path information assuming that the path value is a null value in step S27. Therefore, the XML generation unit 209 generates the tag “OneOrMore” as an empty element tag. The XML generation unit 209 generates “#### required ####” indicating the warning display because the attribute “idReq” has been declared as #REQUIRED and a null value cannot be generated as the attribute value. . Also, since the selection designation of the “|” symbol is not set in the generation option information, the XML generation unit 209 selects the head information based on the generation default information and generates a tag. In this example, the XML generation unit 209 selects “OrA” and “selectType 1” to generate tags.
[0064]
As shown in FIG. 10B, the NV list generation unit 211 generates an element value “0” for the elements “ZeroOrOne?” And “ZeroOrMore *”, and an element value “1” for the element “OneOrMore +”. Generate Since it is set to output a null value as a default value, the NV list generation unit 211 generates an element value of the element “OneOrMore” as a blank. Also, the NV list generation unit 211 generates a warning “#### required ####” because the attribute “idReq” has been declared as #REQUIRED and cannot be generated as a null value as the attribute value. Regarding the selection designation of the “|” symbol, the NV list generation unit 211 selects “OrA” and “selectType 1” to generate element values.
[0065]
FIG. 11 is an explanatory diagram showing another example of the generated output XML data 31 and output NV list data 32. FIG. 11A shows output XML data 31 generated by the XML generation unit 209. FIG. 11B shows the output NV list data 32 generated by the NV list generation unit 211. In the present example, similarly to FIG. 10, a case where output XML data 31 and output NV list data 32 are generated based on generation option information and generation default information in accordance with input DTD data 11 shown in FIG. explain. In this example, in step S103, the number of elements to which “?”, “*”, And “+” are added is set to “1”, the path separator is set to “/”, and the path prefix is It is assumed that no designation is set, that a null value is not output as a default value of an element value or an attribute value, and that an IMPLIED attribute is output.
[0066]
As illustrated in FIG. 11A, since one element is set for each element to which “?”, “*”, And “+” are added, the XML generation unit 209 sets the element “ One tag is generated for each of “ZeroOrOne”, “ZeroOrMore”, and “OneOrMore”. Also, as shown in FIG. 11B, the NV list generation unit 211 generates one element value for each of the elements “ZeroOrOne”, “ZeroOrMore”, and “OneOrMore”. In this example, since it is set that the null value is not output as the default value, the path combining unit 208 combines the path information with the path name as it is in step S27. Therefore, the XML generation unit 209 generates a tag using the path name as it is as each element value. Similarly, the NV list generation unit 211 generates the path name as it is as the element value of each element.
[0067]
In addition, since it is set that the null value is not output as the default value, the XML generation unit 209 and the NV list generation unit 211 generate the path name as it is as the attribute value of the attribute “idReq”. In addition, since the setting is made to output the IMPLIED attribute, the XML generation unit 209 and the NV list generation unit 211 each generate the path name of the attribute “idImp” as the attribute value as it is.
[0068]
FIG. 12 is an explanatory diagram showing still another example of the generated output XML data 31 and output NV list data 32. FIG. 12A shows the output XML data 31 generated by the XML generation unit 209. FIG. 12B shows the output NV list data 32 generated by the NV list generation unit 211. In this example, a case will be described as an example where only the input XML data 12 shown in FIG. 3 is input as reference data. In this example, in step S103, the number of elements to which “?”, “*”, And “+” are added is set to “1”, the path separator is set to “/”, and the path prefix is It is assumed that no designation is set, that a null value is not output as a default value of an element value or an attribute value, and that an IMPLIED attribute is output.
[0069]
For each element to which “?”, “*”, And “+” are added, one element is generated. For the element “OneOrMore”, two paths are used in the input XML data 12 shown in FIG. Since the value is specified, the path synthesis unit 208 extracts the path value specified by the input XML data 12 in step S24 and synthesizes the path information. Therefore, the XML generation unit 209 generates two tags for the element “OneOrMore” as shown in FIG. Further, the XML generation unit 209 generates “data1” and “data2” specified by the input XML data 12 as element values of two tags “OneOrMore”, respectively. Also, as shown in FIG. 12B, the NV list generation unit 211 generates “data1” and “data2” specified in the input XML data 12 as element values of “OneOrMore”.
[0070]
Further, it is set that a null value is not output as a default value. However, since the attribute value “idReq” is specified as the attribute value “000001” in the input XML data 12 shown in FIG. 3, the path combining unit 208 In step S24, the attribute value "000001" specified by the input XML data 12 is extracted and the path information is synthesized. Accordingly, the XML generation unit 209 and the NV list generation unit 211 generate “000001” as the attribute value for the attribute “idReq”, as shown in FIGS. 12A and 12B.
[0071]
Regarding the selection designation of the “|” symbol, since “OrA” and “selectType 1” are designated in the input XML data 12 shown in FIG. 3, the path synthesis unit 208 sets the data type in step S24. Extracts the path value of the element “OrA” having “selectType 1” and synthesizes the path information. Accordingly, the XML generation unit 209 generates a tag for the element “OrA” whose data type is “selectType 1”, as shown in FIG. Since the path value of “OrA” is specified as “Value A” in the input XML data 12 shown in FIG. 3, the path synthesis unit 208 is specified in the input XML data 12 as the element value of the tag “OrA”. "Value A" is generated. Also, as shown in FIG. 13B, the NV list generation unit 211 generates “Value A” specified by the input XML data 12 as an element value of “OrA”.
[0072]
FIG. 13 is an explanatory diagram showing still another example of the generated output XML data 31 and output NV list data 32. FIG. 13A shows output XML data 31 generated by the XML generation unit 209. FIG. 13B shows the output NV list data 32 generated by the NV list generation unit 211. In this example, a case will be described as an example where input XML data 12 shown in FIG. 3 and input NV list data 13 shown in FIG. 4 are input as reference data. In this example, in step S103, the number of elements to which “?”, “*”, And “+” are added is set to “1”, the path separator is set to “/”, and the path prefix is It is assumed that no designation is set, that a null value is not output as a default value of an element value or an attribute value, and that an IMPLIED attribute is output.
[0073]
For each element to which “?”, “*”, And “+” are added, one element is set. However, for the element “OneOrMore”, the input NV list data 13 shown in FIG. Since the number is specified as “3”, the path synthesis unit 208 extracts the number of elements specified in the input NV list data 13 in step S22 and synthesizes the path information. Therefore, the XML generation unit 209 generates three tags for the element “OneOrMore” as shown in FIG. Further, since the second element value of the element “OneOrMore” is specified as “data 2” in the input NV list data 13 shown in FIG. 4, the path synthesizing unit 208 determines in step S22 that the input NV list data 13 Extracts the value of the element specified in and synthesizes the path information. Therefore, the XML generation unit 209 generates “data 2” as the second element value of the tag “OneOrMore”, as shown in FIG.
[0074]
The NV list generation unit 211 generates three elements for the element “OneOrMore”, as shown in FIG. Further, the NV list generation unit 211 generates “data 2” specified by the input NV list data 13 as a second element value of the element “OneOrMore”.
[0075]
Also, it is set that a null value is not output as a default value. However, since the attribute “idImp” is specified to be output as “implied” in the input NV list data 13 shown in FIG. The combining unit 208 extracts the attribute value specified in the input NV list data 13 in step S22 and combines the extracted attribute values. Therefore, as shown in FIGS. 13A and 13B, the XML generation unit 209 and the NV list generation unit 211 generate “implied” as the attribute value for the attribute “idImp”.
[0076]
Further, since the first value of the element “OneOrMore” is specified as “data1” in the input XML data 12 shown in FIG. 3, the path synthesis unit 208 is specified as the input XML data 12 in step S24. Extract values and combine path information. Therefore, the XML generation unit 209 generates the first value of the tag “OneOrMore” as “data1”, as shown in FIG. Further, the NV list generation unit 211 generates the first element value of the element “OneOrMore” as “data1”, as shown in FIG. 13B.
[0077]
Since the attribute “idReq” is specified to be output as “000001” in the input XML data 12 shown in FIG. 3, the path synthesizing unit 208 sets the element specified in the input XML data 12 in step S24. Extract and combine path information. Therefore, as shown in FIGS. 13A and 13B, the XML generation unit 209 and the NV list generation unit 211 generate “000001” as the attribute value for the attribute “idReq”.
[0078]
Regarding the selection designation of the "|" symbol, "OrA" and "selectType 1" are designated to be selected in the input XML data 12 shown in FIG. 3, so the XML generation unit is similar to the case of FIG. 209 generates a tag for the element “OrA” whose data type is “selectType 1” and generates “Value A” specified by the input XML data 12 as an element value. Further, the NV list generation unit 211 generates “Value A” specified by the input XML data 12 as an element value of “OrA”.
[0079]
When the output XML data 31 is generated in step S109, the XML output unit 210 outputs the generated output XML data 31 to the storage device B30 and stores it (step S111). Further, when step S110 is executed, the NV list output unit 212 outputs the generated output NV list data 32 to the storage device B30 and stores it (step S112). In addition, when step S106 is executed, the NV list output unit 212 outputs the generated DTD converted NV list data to the storage device B30 and stores it (step S113). When step S107 is executed, the NV list output unit 212 outputs the generated XML converted NV list data to the storage device B30 and stores the data (step S114). Note that the order in which steps S111, S112, S113, and S114 are executed is not limited to the order shown in the present embodiment.
[0080]
As described above, according to the present embodiment, existing XML data or NV list data edited by a user based on existing data or the like is used as reuse data in accordance with the definition information of the data structure of the XML data to be generated. The XML data is generated by using the XML data. Therefore, by using the reuse data, it is possible to reduce processing related to the manual work of the user. Therefore, it is possible to easily generate a large number of test data and XML data templates that differ only in a part of the data, and to reduce the number of steps in generating the XML data.
[0081]
Further, according to the present embodiment, the generated output XML data 31 can be stored, and the data to be reused can be designated from the previously generated output XML data 31 and used as the input XML data 12. Therefore, by generating new XML data by reusing the existing XML data, it is possible to reduce processing related to the manual work of the user.
[0082]
Further, according to the present embodiment, the input DTD data 11, the input XML data 12, or the output XML data 31 can be generated and stored as NV list data that can be easily edited by a user with an editor or the like. Therefore, XML data can be generated by using NV list data edited by the user based on past accumulated data as reuse data. Therefore, compared to the case of editing the XML data, it is possible to reduce processing related to the manual work of the user.
[0083]
Note that, in the present embodiment, a case where the storage device A10 and the storage device B30 are connected to the XML generation device 20 has been described as an example, but the XML generation device 20 is stored in a storage device built in the XML generation device 20. XML data may be generated based on input data. Further, the XML generation device 20 may store the generated XML data in a storage device built in the XML generation device 20.
[0084]
Further, in the present embodiment, an example has been described in which “/” is specified as a path delimiter and a path prefix is not specified. However, the path delimiter and the prefix are the same as those described in the present embodiment. Not limited to For example, “.” May be specified as a path delimiter, and the prefix of the path may be “data”. When such designation is made, for example, the path value indicated as “/ Simple / One / @ idReq” in the present embodiment is output as “data.Simple.One. @ IdReq”.
[0085]
Further, in the present embodiment, an example has been described in which XML data is generated by using NV list data edited by the user as reuse data as an example, but XML data edited by the user is used as reuse data. You may.
[0086]
The configuration shown in FIG. 1 can be realized by software. That is, in the present embodiment, a process of inputting, to a computer, structure information for specifying a data structure of XML data to be generated, a correspondence between an element indicated by a path and the number of elements, or a correspondence between an element and an element value A process of inputting correspondence information indicating a relationship or existing XML data as reuse information, and a path name and the number of elements or elements for each path specified from the structure information based on the setting information and the reuse information. An XML generation apparatus can be realized by an XML generation program for executing a process of generating and combining path information indicating the value of and the process of generating XML data based on the combined information obtained by combining the path information. .
[0087]
【The invention's effect】
According to the present invention, a structure information input unit for inputting structure information for designating a data structure of XML data to be generated, a correspondence relationship between an element indicated by a path and an element number, or an element to element value Reusable information input means for inputting relevance information indicating a relevance relationship with existing or existing XML data as reusable information, and for each path specified from the structure information based on the setting information and the reusable information, A path information synthesizing unit that generates and synthesizes path information indicating a path name and the number of elements or an element value; and an XML generating unit that generates XML data based on the synthesis information synthesized by the path information synthesizing unit. With this configuration, existing XML data and data edited by the user based on existing data can be used as reusable data, thereby reducing user manual work. It is possible to reduce the processing that. Therefore, it is possible to easily generate a template of test data and a large number of XML data, and it is possible to reduce man-hours at the time of generating the XML data.
[0088]
Further, according to the present invention, the XML generation program inputs, to the computer, structure information for designating the data structure of the XML data to be generated, the correspondence between the element indicated by the path and the number of elements, or the element and element. A process of inputting, as reuse information, correspondence information indicating the correspondence relationship with the value of the XML or existing XML data, and a path name for each path specified from the structure information based on the setting information and the reuse information. To generate and combine path information indicating the number of elements and the value of the element, and to generate XML data based on the combined information obtained by combining the path information. By using data edited based on existing data or the like as reusable data, it is possible to reduce processing related to a user's manual work. Therefore, a template for test data or XML data can be easily generated, and the number of steps for generating XML data can be reduced.
[Brief description of the drawings]
FIG. 1 is a block diagram illustrating an example of a configuration of an XML generation device according to the present invention.
FIG. 2 is an explanatory diagram illustrating an example of the content of input DTD data.
FIG. 3 is an explanatory diagram showing an example of the content of input XML data.
FIG. 4 is an explanatory diagram showing an example of the contents of input NV list data.
FIG. 5 is an explanatory diagram showing an example of NV list data based on a path synthesis result.
FIG. 6 is an explanatory diagram showing another example of NV list data based on a path synthesis result.
FIG. 7 is a flowchart illustrating an example of a process of generating XML data;
FIG. 8 is an explanatory diagram showing an example of XML conversion NV list data.
FIG. 9 is a flowchart showing an example of the progress of path synthesis processing.
FIG. 10 is an explanatory diagram showing an example of the contents of output XML data and output NV list data.
FIG. 11 is an explanatory diagram showing another example of the contents of output XML data and output NV list data.
FIG. 12 is an explanatory diagram showing still another example of the contents of output XML data and output NV list data.
FIG. 13 is an explanatory diagram showing still another example of the contents of output XML data and output NV list data.
[Explanation of symbols]
10 Storage device A
11 Input DTD data
12 Input XML data
13 Input NV list data
20 XML generator
201 Generation option input section
202 DTD input unit
203 Structural Analysis Department
204 DTD converter
205 XML input unit
206 XML converter
207 NV list input section
208 Path synthesis unit
209 XML generation unit
210 XML output unit
211 NV list generation unit
212 NV list output unit
30 Storage device B
31 Output XML data
32 Output NV list data

Claims (9)

An XML generation device that generates XML data according to a specified data structure,
Structure information input means for inputting structure information for designating a data structure of XML data to be generated;
Reuse information input means for inputting, as reuse information, correspondence information indicating the correspondence between the element indicated by the path and the number of elements or the correspondence between the element and the value of the element, or existing XML data;
Setting information holding means for holding setting information which is information for specifying a generation pattern of XML data to be generated;
Path information synthesizing means for generating and synthesizing path information indicating a path name and the number of elements or element values for each path specified from the structure information, based on the setting information and the reuse information,
An XML generation apparatus, comprising: XML generation means for generating XML data based on synthesis information synthesized by the path information synthesis means. A setting information input means for inputting setting information;
2. The path information synthesizing unit generates and synthesizes path information of XML data based on the setting information input by the setting information input unit, the setting information held by the setting information holding unit, and the reuse information. XML generation device. The reuse information input means includes correspondence information input means for inputting correspondence information as reuse information,
The path information combining unit extracts path information included in the correspondence information input by the correspondence information input unit, and combines the path information by using the extracted path information as a combination target. 2. The XML generator according to 2. The reuse information input means includes an XML input means for inputting existing XML data as reuse information,
Path information combining means for extracting path information included in the existing XML data input by the XML input means, and combining the extracted path information as a synthesis target to synthesize path information;
4. The XML generation device according to claim 1, wherein the XML generation unit generates new XML data based on the synthesis information synthesized by the path information synthesis unit. 5. The path information combining means according to claim 1, wherein the path information included in the correspondence information is combined with the path information by prioritizing the path information included in the existing XML data. 2. The XML generation device according to item 1. 6. The XML according to claim 5, wherein the path information combining means combines the path information according to the generation pattern specified in the setting information when the path information specified from the structure information is not included in the correspondence information or the existing XML data. Generator. Claims: A correspondence information generating means for generating correspondence information based on synthetic information synthesized by path information synthesizing means, structure information input by structure information input means, or existing XML data input by XML input means. The XML generation device according to any one of claims 4 to 6. 8. The XML generation device according to claim 7, wherein the reuse information input unit inputs the XML data generated by the XML generation unit or the correspondence information generated by the correspondence information generation unit as reuse information. An XML generation program mounted on an XML generation apparatus including setting information holding means for holding setting information which is information for specifying a generation pattern of XML data to be generated,
On the computer,
A process of inputting structure information for designating a data structure of XML data to be generated, and a relationship information indicating a correspondence between an element indicated by a path and the number of elements or a correspondence between an element and an element value, or an existing XML A process of inputting data as reuse information;
Based on the setting information and the reuse information, for each path specified from the structure information, processing to generate and synthesize path information indicating the path name and the number of elements or the value of the element,
And a process for generating XML data based on the combined information obtained by combining the path information.

Images