JP2009122949A - System, method and program for restoring xml data structure - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To accurately restore an XML data structure in interconversion between XML data and a text or CSV format data regardless of a description structure in the XML data. <P>SOLUTION: This restoration system 100 of the XML data structure includes: a data acquisition part 110 storing the XML data; a tag reading part 111 retrieving a start tag, and reading a tag to a layer Y wherein an end tag is detected; a position information storage part 112 numbering a tag position ID in association with the read tag, and storing a tag position ID group for a route to the layer Y from a layer X; a record generation part 113 generating and storing a record wherein the tag position ID and layer data are associated for the route from the layer X to the layer Y; a restoration processing part 114 generating a layer in the XML data structure for each tag position ID included in the record, setting the layer data, and restoring the XML data; and an output processing part 115 transmitting or outputting the restored XML data to a predetermined terminal. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an XML data structure restoration system, an XML data structure restoration method, and an XML data structure restoration program. More specifically, the present invention relates to an XML data conforming to a distribution business message standard and text and CSV format data. The present invention relates to a technique for restoring an XML data structure in conversion.

  An EDI (Electronic Data Interchange) mechanism for exchanging various types of data related to business transactions between companies (unified in a standard format) has begun to spread. In this system, data related to order placement / quotation, settlement, settlement, and arrival / departure of goods is digitized according to a predetermined format and transmitted / received between terminals of trading companies through a network. Under these circumstances, when data is transmitted / received using an XML file conforming to the distribution business message standard, a means for converting the distribution business message received from a terminal such as a business partner into text or CSV format, converted text or CSV Means for reconverting the format into an XML file structure that conforms to the distribution business message standard has been proposed.

  For example, it is possible to reduce the processing load of remote method invocation that delivers structured data, and to reduce the storage capacity in the construction of a system that performs this XML parsing. A non-recursive data representation generation serializer for creating structured text data and basic type data in a programming language into a text document having at most one level that can be inversely converted at a destination, and the client non-recursive data A server non-recursive data representation interpretation parser that interprets a text document with at most one level created by the data representation generation serializer and retrieves information necessary for starting the server application, and a structural type that is the return value that started the server application Data and basic data A server non-recursive data representation generation serializer that creates a text document that is one level of hierarchy and can be reverse-converted on the client side, and a text document that has at most one level of hierarchy, and a structure that is the return value from the server application Providing a service non-recursive data expression interpretation parser that creates a parameter with a service cooperation system (see Patent Document 1) that enables cooperation between a client application and a server application has been proposed. Yes.

In addition, legacy data and XML data used by a legacy system, which aims to provide a data conversion processing device, a conversion processing method, and a program thereof that make it possible to use data after data conversion more flexibly. A data conversion processing apparatus comprising data conversion means for performing data conversion processing with reference to a format definition XML file in which a format used by the legacy system is defined in XML when performing data conversion processing (Patent Document) 2) is also proposed.
JP 2004-265164 A JP 2004-318420 A

  By the way, in the XML schema defined in the distribution business message standard, each item (tag) is defined in a hierarchical structure. The repeated description in this schema has two structural patterns: a case where tags with different contents are repeatedly described in the same layer, and a case where tags are repeatedly described from a tag in a higher layer to a tag in a predetermined layer. If the tags repeatedly described in each of the two structural patterns are the same between the two patterns, the conversion result will be the same when the XML data is converted to text or CSV format. That is, it is unclear which XML pattern data is described in which structure pattern. For this reason, even if this converted text or CSV format data is reversely converted to XML data, restoration to the same structure as the original XML data is not guaranteed.

  Therefore, the present invention has been made in view of the above problems, and enables accurate restoration of the XML data structure at the time of mutual conversion between XML data and text or CSV format data, regardless of the description structure in the XML data. The purpose is to provide technology.

  The XML data structure restoration system according to the present invention is a computer system for interconverting XML data and text or CSV data, and obtains data to be received from a predetermined terminal on a network and stored in a storage device. XML data is read from the storage device to the memory, a start tag in the XML data is searched, and the tag from the hierarchy X where the start tag is searched to the lower hierarchy until the hierarchy Y where the end tag is detected In response to the tag reading unit, the tag position ID that uniquely identifies each tag is assigned in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y, and the hierarchy X A position information storage unit that stores in a memory a tag position ID group for a route from the level Y to the level Y, and the level X to level Y of the XML data The hierarchical data described in each hierarchy in FIG. 5 is read from the XML data, the XML data in each hierarchy is associated with the tag position ID of each hierarchy included in the tag position ID group in the memory, and the hierarchy X to the hierarchy Y A record generation unit for generating a record in which a tag position ID and hierarchical data are associated with each other for a route to the destination, and storing the record in a storage device as data in text or CSV format, and an XML data structure from a predetermined terminal or input interface on the network When the restoration instruction is received, or the arrival of the restoration time of the XML data structure preset in the storage device is detected, the record is read from the storage device to the memory, and each tag position ID included in the record is read. A hierarchy in the XML data structure is generated, and the corresponding tag position I is generated for each generated hierarchy. Hierarchical data corresponding to is extracted and set from the record, and XML data having a structure in which each hierarchy from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected includes the hierarchy data is restored. And an output processing unit that transmits the XML data restored in the memory to a predetermined terminal on the network or outputs it to an output interface.

  According to this, XML data received from a predetermined terminal, for example, conforming to the distribution business message standard can be converted into a text or CSV format and stored while taking into consideration the XML data structure. Therefore, even if the XML data itself is lost, it can be guaranteed that the data converted into text or CSV format and stored is restored to XML data having a data structure as received from the terminal. Therefore, it is possible to accurately restore the XML data structure at the time of mutual conversion between the XML data and the text or CSV format data regardless of the description structure in the XML data.

  Further, in the XML data structure restoration system, the tag reading unit executes the reading process of the end tag of the hierarchy Y, and then, in the upper hierarchy A including the hierarchy Y, what is the hierarchy Y Search for another start tag, and execute a tag reading process from the hierarchy A in which the start tag is searched to the lower hierarchy to the hierarchy B where an end tag different from that of the hierarchy Y is detected. The position information storage unit assigns a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy A to the hierarchy B, and has already assigned the tag position ID. The tag position ID group for the route from the hierarchy A to the hierarchy B is merged with the tag position ID group for the route from the predetermined hierarchy X to the hierarchy A, and the layers X to A to B are merged. About the route The record generation unit reads the hierarchical data described in each of the hierarchical levels X to AB of the XML data from the XML data, and stores the XML data in each hierarchical level. Is associated with the tag position ID of each hierarchy included in the tag position ID group in the memory, and a record in which the tag position ID and the hierarchy data are associated with each other for the route to the hierarchy X to AB is generated. The data is stored in a storage device as text or CSV format data, and the restoration processing unit reads the record from the storage device into a memory, and among the tag position IDs included in the record, the hierarchy A to the hierarchy B A hierarchy in the XML data structure is generated for those up to and including the corresponding tag position ID for each hierarchy from hierarchy A to hierarchy B Corresponding hierarchical data is extracted and set from the record, XML data having a structure in which each hierarchy from the hierarchical level A to the hierarchical level B includes hierarchical data is restored, and this XML data is restored to the already restored hierarchical level. It is good also as what adds to the XML data from X to the hierarchy Y, and restore | restores the XML data which makes each hierarchy of the said hierarchy XA to B the hierarchy data.

  According to this, in correspondence with the situation where the hierarchical structure of the XML data is multiplexed, the tag position can be grasped and stored, the conversion of the XML data into the text or CSV format, and the text or CSV format data. Can be accurately restored along with the XML data structure.

  In the XML data structure restoration system, the XML data may be data on shipping packaging among data compliant with a distribution business message standard.

  This solves the problem that it is difficult to restore the exact XML data structure from the data once converted to text or CSV format for the shipping packing data conforming to the distribution business message standard that is currently widely handled as XML data. It becomes possible to do.

  The XML data structure restoration method of the present invention includes a process in which a computer that mutually converts XML data and text or CSV format data receives XML data from a predetermined terminal on the network and stores it in a storage device. XML data is read from the storage device into the memory, a start tag in the XML data is searched, and a tag reading process is performed from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected from the lower hierarchy. And a path from the hierarchy X to the hierarchy Y by assigning a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y Processing for storing the tag position ID group in the memory, and hierarchical data described in each hierarchy from hierarchy X to hierarchy Y of the XML data The XML data is read from the ML data, the XML data of each layer is associated with the tag position ID of each layer included in the tag position ID group in the memory, and the tag position ID and the layer data are obtained for the route from the layer X to the layer Y. A process for generating the associated record and storing it in the storage device as data in text or CSV format, and receiving an instruction to restore the XML data structure from a predetermined terminal or input interface on the network, or preset in the storage device If it is detected that the restoration time of the XML data structure that has been stored is reached, the record is read from the storage device to the memory, and a hierarchy in the XML data structure is generated for each tag position ID included in the record, and each generated hierarchy On the other hand, the hierarchical data corresponding to the corresponding tag position ID is extracted from the record and set. Then, a process of restoring the XML data in which each hierarchy from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected includes a hierarchy data, and the XML data restored in the memory And transmitting to a predetermined terminal on the network or outputting to an output interface.

  According to this, XML data received from a predetermined terminal, for example, conforming to the distribution business message standard can be converted into a text or CSV format and stored while taking into consideration the XML data structure. Therefore, even if the XML data itself is lost, it can be guaranteed that the data converted into text or CSV format and stored is restored to XML data having a data structure as received from the terminal. Therefore, it is possible to accurately restore the XML data structure at the time of mutual conversion between the XML data and the text or CSV format data, regardless of the description structure in the XML data.

  The XML data structure restoration program of the present invention includes a step of receiving XML data from a predetermined terminal on a network and storing the XML data in a storage device in a computer that mutually converts the XML data and text or CSV data. XML data is read from the storage device into the memory, a start tag in the XML data is searched, and a tag reading process is performed from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected from the lower hierarchy. And a path from the hierarchy X to the hierarchy Y by assigning a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y And a step of storing the tag position ID group in the memory, and the XML data are described in each hierarchy from hierarchy X to hierarchy Y. The hierarchical data is read from the XML data, the XML data of each hierarchy is associated with the tag position ID of each hierarchy included in the tag position ID group in the memory, and the tag position ID and the path from the hierarchy X to the hierarchy Y are A record in which hierarchical data is associated is generated and stored in the storage device as text or CSV format data, and an instruction to restore the XML data structure is received from a predetermined terminal or input interface on the network, or the storage device If the arrival of the restoration time of the preset XML data structure is detected, the record is read from the storage device to the memory, and a hierarchy in the XML data structure is generated for each tag position ID included in the record, For each generated hierarchy, the hierarchy data corresponding to the corresponding tag position ID is Extracting and setting from the code, restoring the XML data having a structure in which each hierarchy from the hierarchy X in which the start tag is searched to the hierarchy Y in which the end tag is detected includes hierarchy data; The step of transmitting the restored XML data to a predetermined terminal on the network or outputting the XML data to an output interface is executed.

  According to this, XML data received from a predetermined terminal, for example, conforming to the distribution business message standard can be converted into a text or CSV format and stored while taking into consideration the XML data structure. Therefore, even if the XML data itself is lost, it can be guaranteed that the data converted into text or CSV format and stored is restored to XML data having a data structure as received from the terminal. Therefore, it is possible to accurately restore the XML data structure at the time of mutual conversion between the XML data and the text or CSV format data regardless of the description structure in the XML data.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.

  According to the present invention, it is possible to accurately restore the XML data structure at the time of mutual conversion between the XML data and the text or CSV format data, regardless of the description structure in the XML data.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a configuration diagram of an XML data structure restoration system 100 according to this embodiment. An XML data structure restoration system 100 (hereinafter, system 100) in the present embodiment is a computer system that mutually converts XML data and text or CSV format data. For example, XML data structure restoration system 100 conforms to a distribution business message standard. An enterprise server device that exchanges data can be assumed. Such a server device digitizes various data related to commercial transactions, for example, data related to ordering / quoting of products, settlement, settlement / in / out of goods, etc. in accordance with a predetermined format, and communicates with other company terminals 200 provided by other companies through a network. Send and receive.

  In order to send and receive XML data compliant with the distribution business message standard, a relative relationship between companies is a prerequisite. Therefore, in the present embodiment, the companies that are opposed to each other are shown separately for other companies and their own companies. For example, in-house, in addition to the transmission / reception server 100 that implements the XML data structure restoration system of the present invention, the backbone server 11 that has conventionally controlled data processing related to commercial transactions, receives instructions from the person in charge, and performs the transmission / reception. It can be assumed that the operation terminal 12 and the like input to the server are included. Further, for example, it can be assumed that the other company terminal 200 provided by the other company includes the transmission / reception server 20 (as in the function of the transmission / reception server 100), the backbone system 21 that has conventionally controlled data processing related to commercial transactions, and the like. In addition, such a configuration example is an example of an image of a specific device configuration. In the following description, a device that receives XML data from an opposing company and converts the XML data into text or CSV format data. Is the system 100, and the other company's terminal 200 is the destination to which the system 100 transmits XML data generated by performing reverse conversion from text or CSV format data.

  Of course, the XML data compliant with the distribution business message standard is not only sent from the other company's terminal 200 to the system 100 side (the company's own with respect to the other company) but also sent from the system 100 to the other company's terminal 200. The other company terminal 200 may have the function 100, and the system 100 of the other company and the other company terminal 200 of the other company may perform the XML data transmission / reception and the XML data structure restoration method of the present invention.

  The system 100 reads the program 102 stored in the storage device 101 such as a nonvolatile memory into the memory 103 and executes it by the CPU 104 which is an arithmetic device in order to realize the function of executing the method for restoring the XML data structure. Further, the system 100 includes various buttons generally provided in a computer device, an input interface 105 such as a keyboard, an output interface 106 such as an LED and a display, and a communication device 107 that is responsible for communication with terminals of other companies. is doing.

  Next, functional units that are configured and held by the system 100 based on the program 102 will be described. The system 100 includes a data acquisition unit 110 that receives XML data from another company terminal 200 that is a predetermined terminal on the network 140 and stores the XML data in the storage device 101.

  Further, the system 100 reads the XML data from the storage device 101 to the memory 103, searches for the start tag in the XML data, and detects the end tag from the hierarchy X where the start tag is searched toward the lower hierarchy. A tag reading unit 111 is provided that executes a tag reading process up to level Y.

  Further, the system 100 assigns a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y, and reaches from the hierarchy X to the hierarchy Y. A location information storage unit 112 that stores a tag location ID group for the route in the memory 103 is provided.

  In addition, the system 100 reads hierarchical data described in each hierarchy from the hierarchy X to the hierarchy Y of the XML data from the XML data, and the tag position ID group in the memory 103 includes the XML data of each hierarchy. Corresponding to the tag position ID of each hierarchy, a record in which the tag position ID and the hierarchy data are associated with each other for the route from the hierarchy X to the hierarchy Y is generated, and stored in the storage device 101 as data in text or CSV format The record generation unit 113 is provided.

  In addition, the system 100 receives an XML data structure restoration instruction from the predetermined terminal 200 or the input interface 105 on the network 140 or detects the arrival of the restoration time of the XML data structure preset in the storage device 101. Then, the record is read from the storage device 101 to the memory 103, a hierarchy in the XML data structure is generated for each tag position ID included in the record, and a hierarchy corresponding to the corresponding tag position ID is generated for each generated hierarchy. A restoration processing unit that extracts and sets data from the record and restores XML data having a structure in which each hierarchy from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected includes the hierarchy data 114.

  The system 100 further includes an output processing unit 115 that transmits the XML data restored in the memory 103 to a predetermined terminal 200 on the network 140 or outputs the XML data to the output interface 106.

  In addition, after the tag reading unit 111 executes the reading process of the end tag of the hierarchy Y, in the upper hierarchy A including the hierarchy Y, the tag reading unit 111 searches for a start tag different from that of the hierarchy Y, The tag reading process may be executed from the hierarchy A where the start tag is searched to the lower hierarchy until the hierarchy B where the end tag different from that of the hierarchy Y is detected. In this case, the position information storage unit 112 assigns a tag position ID that uniquely identifies each tag in association with the tag read in each hierarchy from the hierarchy A to the hierarchy B, and already has the tag position ID. Are merged with the tag position ID group assigned to the route from the hierarchy A to the hierarchy B, and the hierarchy X to AB. This is stored in the memory 103 as a tag position ID group for the route. In addition, the record generation unit 113 reads the hierarchical data described in the hierarchical levels X to A to B of the XML data from the XML data, and the XML data of each hierarchical level is a tag position ID group in the memory 103. Is generated in association with the tag position ID of each hierarchy included in the record, and a record in which the tag position ID and the hierarchy data are associated with each other for the route to the hierarchy X to AB is generated and stored as text or CSV format data 101 is stored. In addition, the restoration processing unit 114 reads the record from the storage device 101 to the memory 103 and generates a hierarchy in the XML data structure for the tag position IDs included in the record from the hierarchy A to the hierarchy B. Then, for each of the generated layers A to B, the layer data corresponding to the corresponding tag position ID is extracted and set from the record, and each layer from the layer A to the layer B includes the layer data. The XML data having the structure is restored, the XML data is added to the already restored XML data from the hierarchy X to the hierarchy Y, and each of the hierarchies X to A to B includes the hierarchy data The XML data forming the above is restored.

  In the system 100, the XML data may be data on shipping packaging among data compliant with the distribution business message standard.

  The functional units 110 to 115 in the system 100 described so far may be realized as hardware, or as a program stored in an appropriate storage device such as a memory or an HDD (Hard Disk Drive). Also good. In this case, the CPU of the system 100 reads the corresponding program from the storage device into the memory in accordance with the program execution, and executes it.

---- Example of overall flow 1 ---
The actual procedure of the XML data structure restoration method in the present embodiment will be described below with reference to the drawings. Various operations corresponding to the XML data structure restoration method described below are realized by a program that the system 100 reads into the memory and executes. And this program is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 2 is an entire sequence example 1 of the present embodiment. Here, the data acquisition unit 110 of the system 100 receives the XML data from the other company's terminal 200 on the network 140 and stores it in the storage device 101 (s100).

  Further, the tag reading unit 111 of the system 100 reads the XML data from the storage device 101 to the memory 103, searches for the start tag in the XML data, and starts from the hierarchy X where the start tag is searched toward the lower hierarchy. The tag reading process is executed up to level Y where the end tag is detected (s101).

  Next, the position information storage unit 112 of the system 100 assigns a tag position ID that uniquely identifies each tag in association with the tag read in each hierarchy from the hierarchy X to the hierarchy Y, and The tag position ID group for the route from the hierarchy X to the hierarchy Y is stored in the memory 103 (s102).

  In addition, the record generation unit 113 of the system 100 reads the hierarchical data described in the hierarchical levels from the hierarchical level X to the hierarchical level Y of the XML data from the XML data, and reads the XML data of each hierarchical level in the tag in the memory 103. Corresponding to the tag position ID of each hierarchy included in the position ID group, a record in which the tag position ID and the hierarchy data are associated with each other for the route from the hierarchy X to the hierarchy Y is generated, and the data is text or CSV format data. The data is stored in the storage device 101 (s103).

  Thereafter, the restoration processing unit 114 of the system 100 receives an instruction to restore the XML data structure from the other company's terminal 200 or the input interface 105 on the network 140, or has an XML data structure preset in the storage device 101. If the arrival of the restoration time is detected, the record is read from the storage device 101 to the memory 103, and a hierarchy in the XML data structure is generated for each tag position ID included in the record. Hierarchical data corresponding to the tag position ID is extracted from the record and set, and each hierarchy from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected has a structure including hierarchy data. The data is restored (s104).

  The output processing unit 115 of the system 100 transmits the XML data restored in the memory 103 to the other company's terminal 200 on the network 140 or outputs it to the output interface 106 (s105).

--- Example of overall flow 2 ---
FIG. 3 is an overall sequence example 2 of the present embodiment. Next, after the tag reading unit 111 executes the reading process of the end tag of the hierarchy Y, the tag reading unit 111 searches the upper hierarchy A including the hierarchy Y for a start tag different from that of the hierarchy Y. The processing in the case will be described. In this case, the tag reading unit 111 executes the reading process of the end tag of the hierarchy Y, and then searches for a start tag different from that of the hierarchy Y in the upper hierarchy A including the hierarchy Y. The tag reading process is executed from the hierarchy A where the start tag is searched to the hierarchy below the hierarchy B where the end tag different from that of the hierarchy Y is detected (s200).

  In addition, the position information storage unit 112 assigns a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy A to the hierarchy B, and already assigns the tag position ID. The tag position ID group assigned to the route from the hierarchy A to the hierarchy B is merged with the tag position ID group for the route from the predetermined hierarchy X to the hierarchy A, and the route of the hierarchy X to AB is merged. Is stored in the memory 103 as a tag position ID group (S201).

  Next, the record generation unit 113 reads the hierarchical data described in the hierarchical levels X to A to B of the XML data from the XML data, and uses the XML data of each hierarchical level as the tag position ID in the memory 103. Corresponding to the tag position ID of each hierarchy included in the group, a record in which the tag position ID and the hierarchy data are associated with each other for the route to the hierarchy X to AB is generated and stored as text or CSV format data The data is stored in the device 101 (s202). After that, the restoration processing unit 114 reads the record from the storage device 101 to the memory 103, and among the tag position IDs included in the record, the hierarchy in the XML data structure is assigned to the hierarchy from the hierarchy A to the hierarchy B. The hierarchy data corresponding to the corresponding tag position ID is extracted from the record and set for each hierarchy from the hierarchy A to the hierarchy B generated, and each hierarchy from the hierarchy A to the hierarchy B stores the hierarchy data. The XML data having the included structure is restored, and the XML data is added to the already restored XML data from the hierarchy X to the hierarchy Y, and each of the hierarchies X to A to B includes the hierarchy data. The XML data having the structure is restored (s203).

--- Example structure of XML data and text or CSV format data ---
Next, an example of the structure of XML data and text or CSV format data obtained by converting the XML data will be described. FIG. 4 shows an example of the structure of XML data defined in the distribution business message standard. The XML data 40 in this example indicates the XML data structure of the shipping packing among the data types such as ordering, receiving, returning, payment, billing, shipping slip, shipping packing. In this XML data structure, the highest hierarchy (tier 1) is defined as SBDH (Standard Business Document Header), and a shipping packing file header (ListOfPackageShipments: hierarchy 2) is defined in a form included in the SBDH. Yes. Similarly, what is included in the hierarchy 2 is shipping package order source information (PackageShipmentByReciever: Hierarchy 3), and the shipping packing information (PackageInfo: Hierarchy 4) and the shipping packing item information (ItemInfo: Hierarchy 5) are also in one stage. It is included in the upper hierarchy.

  FIG. 5 shows an example of the structure of a text or CSV file in this embodiment. The text or CSV file 50 shown here is generated by converting the XML data 40 by the XML data structure restoration method of the present invention. The text or CSV file 50 is a text or tag text ID that is tag position information in the XML data structure. It is a CSV file structure (shipping packaging). The structure of the CSV file 50 is a structure in which the structure of the XML data 40 represented hierarchically in FIG. 4 is represented in a two-dimensional table format, and the tag position ID is incorporated for each layer of the XML data 40.

--- Conversion processing example 1 ---
Next, details of conversion processing from XML data to text or CSV format data will be described. FIG. 6 is a flowchart showing a processing procedure example 1 of the XML data structure restoration method of the present embodiment. First, as a premise in this description, the data acquisition unit 110 of the system 100 receives XML data conforming to the distribution business message standard transmitted from the other company terminal 200 via the network 140, and stores it in the storage device 101 or the like (s300).

  Next, the tag reading unit 111 of the system 100 determines whether the XML data stored in the storage device 101 includes an argument in the area of the message type information 208 (see FIG. 4), for example (s301).

  If it is determined in the determination process that the argument exists in the XML data (s301: Yes), the tag reading unit 111 saves the corresponding argument on the memory 103 (s302). On the other hand, if it is determined in the determination process that the argument does not exist in the XML data (s301: No), this flow ends.

  Subsequent to step s302, the tag reading unit 111 determines whether the argument saved in the memory 103 in step s302 matches the argument defined in the argument list provided in advance in the storage device 101. (S303). As the argument list, order: order, receipt: RecievingNotification, ... all: ALL, etc. can be assumed. As an example, at the time of mutual conversion between XML data and text or CSV format data, only the argument related to “shipping packing”, which has been difficult to restore the XML data structure in the past, is defined in the argument list. Assume that the system 100 detects the presence of XML data.

  When the argument saved in the memory 103 in step s303 matches the argument set in the argument list (s303: Yes), the tag reading unit 111 performs the process shown in the example of FIG. The start tag is sequentially searched from the upper hierarchy (SBDH) toward the lower hierarchy, and the end tag is detected from the hierarchy X (hierarchy 1 in the case of FIG. 4) where the start tag is searched toward the lower hierarchy. The tag reading process is executed up to level Y (level 5 in the case of FIG. 4) (s304). If the argument saved in the memory 103 does not match the argument set in the argument list (s303: No), this flow ends.

  Subsequently, the position information storage unit 112 of the system 100 sets a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy 1 as the hierarchy X to the hierarchy 5 as the hierarchy Y. Numbering is performed, and the tag position ID group for the route from the hierarchy X to the hierarchy Y is stored in the memory 103 (s305).

  Then, the record generation unit 113 of the system 100 reads the hierarchical data described in the hierarchical levels from the hierarchical level X to the hierarchical level Y of the XML data from the XML data, and reads the XML data of each hierarchical level in the tag in the memory 103. Corresponding to the tag position ID of each hierarchy included in the position ID group, a record in which the tag position ID and the hierarchy data are associated with each other for the route from the hierarchy X to the hierarchy Y is generated, and the data is text or CSV format data. The data is stored in the storage device 101 (s306). The tag position ID group in the record is set in the tag position ID fields 297 to 301 in the CSV file 50 shown in FIG.

  Here, the details of the tag position ID numbering and record setting processing will be described. As XML data used in the description here, XML data 41 shown in FIG. 8 is assumed. Also, a CSV file 51 shown in FIG. 10 is assumed as a CSV file (or text) obtained by converting the XML data 41.

  For example, when the repeated data is described in the level 5 (start tags 217, 219, and 221) as in the XML data 41 in FIG. 8, the tag reading unit 111 detects the start tag 213 in the layer 1. The hierarchical data 282 (data “AAA”) in the hierarchical level 1 is saved in the memory 103. Then, when the next start tag 214 of level 2 is read, 1 is added to the memory counter (the system 100 is equipped with the tag reading unit 111 and controlled by the initial value: 000). Then, “001” is assigned.

  The record generation unit 113 sets the data “001” numbered by the tag reading unit 111 as a tag position ID in the tag position ID column 243 of the first record in the CSV file 51 (FIG. 10). . After the tag position ID is set, the hierarchical data 282 (“AAA”) in the hierarchical level 1 saved in the memory 103 is set in the hierarchical column 1 data column 244 of the first record in the CSV file 51. Then, the same processing as described above in the hierarchy 1 is performed from the hierarchy 2 to the hierarchy 4, and the tag position ID column 245 for each of the hierarchy 2, the hierarchy 3, and the hierarchy 4 of the first record in the CSV file 51, Tag position IDs “002”, “003”, and “004” are set in 247 and 249, respectively. In addition, the hierarchical data “BBB”, “CCC”, and “DDD” are set in the data columns 246, 248, and 250, respectively.

  Similarly, for the layer 5, the tag reading unit 111 detects the first start tag 217 of the layer 5 and saves the layer data 286 (“EEE”) in the layer 5 in the memory 103. Since the start tag that can be detected next is the end tag 218 of the hierarchy 5, 1 is added to the memory counter ("004" at this time) that has been added up to the hierarchy 4, and the tag position ID "005". Number.

  Then, the record generation unit 113 sets the tag position ID “005” in the tag position ID column 251 of the first record in the hierarchy 5 in the CSV file 51. After the tag position ID “005” is set, the hierarchy data 286 (“EEE”) in the hierarchy 5 saved in the memory 103 is set in the data field 252 in the hierarchy 5 of the first record in the CSV file 51.

  Next, the tag reading unit 111 detects another start tag 219 in the hierarchy 5 before reading the end tag 223 in the hierarchy 4. Further, the hierarchical data 287 (“FFF”) corresponding to the start tag 219 is saved in the memory 103, 1 is added to the memory counter (“005” at this time), and the tag position ID “006” is set. Numbering.

  The record generation unit 113 generates a new record (second record) in the CSV file 51 and sets the tag position ID “006” in the tag position ID column 261 of the hierarchy 5 of the second record. . After the tag position ID is set, the hierarchical data 287 (“FFF”) in the hierarchical level 5 saved in the memory 103 is set in the hierarchical column 5 data column 262 of the second record.

  When the record generation unit 113 generates the second record, the tag position ID fields 253, 255, 257, and 259 of the second record, the hierarchy 1, the hierarchy 2, the hierarchy 3, and the hierarchy 4, respectively, The tag position IDs “001”, “002”, “003”, and “004” of the first layer, the first layer 2, the second layer 3, and the fourth layer are set. In the data fields 254, 256, 258, and 260 of the second record, the hierarchical data “AAA”, “BBB”, “CCC”, and “DDD” of the first record are set.

  Thus, a CSV file 51 incorporating XML data structure information is generated for the XML data 41.

--- Conversion processing example 2 ---
Further, as in the XML data 42 shown in FIG. 9, there is a hierarchy 4 (including hierarchy data 292 and one hierarchy 5) divided by the start tag 230 and the end tag 233, and the start tag 234. Details of the tag position ID numbering and the record setting processing are described for XML data including the other layer 4 (including the layer data 294 and the two layers 5) separated by the end tag 239. Keep it.

  In this case, first, the tag reading unit 111 detects and reads the start tag 227 of the hierarchy 1 and stores the hierarchy data 289 (“AAA”) in the hierarchy 1 in the memory 103. Then, the start tag 228 of level 2 which is the next start tag is detected and read, and 1 is added to the memory counter (initial value: 000) to assign the tag position ID “001”.

  Further, the record generation unit 113 sets the tag position ID “001” in the tag position ID column 263 of the first layer in the CSV file 52 shown in FIG. After the tag position ID is set, the record generation unit 113 sets the hierarchy data “AAA” in the hierarchy 1 saved in the memory 103 in the data field 264 of the first record in the CSV file 52.

  The record generation unit 113 performs processing similar to the processing contents shown for the layer 1 up to the layer 2 and subsequent layers, and each of the layer 2, layer 3, and layer 4 of the first record in the CSV file 52, Tag position IDs “002”, “003”, and “004” are set in the tag position ID columns 265, 267, and 269. In addition, the hierarchy data “BBB”, “CCC”, and “DDD” are set in the data fields 266, 268, and 270 of the hierarchy 2, 3, and 4, respectively, of the first record in the CSV file 52.

  Similarly to the above, the tag reading unit 111 detects and reads the start tag 231 of the layer 5 after reading the start tag 230 of the layer 4 and reads the layer data 293 (“FFF”) in the layer 5. ) Is saved in the memory 103. Further, since the next tag to be read is the end tag 232 of the hierarchy 5, 1 is added to the memory counter ("004") added up to the hierarchy 4, and the tag position ID "005" is assigned.

  The record generation unit 113 sets the tag position ID “005” in the tag position ID column 271 of the first layer in the CSV file 52. Further, after setting the tag position ID, the hierarchical data “FFF” of the hierarchical level 5 saved in the memory 103 is set in the hierarchical column 5 data column 272 of the first record of the CSV file 52.

  After reading the end tag 233 of level 4 after reading the end tag 233 of level 4, the tag reading unit 111 newly detects and reads the start tag 234 of another level 4. . Therefore, the hierarchy data 294 (“GGG”) in the new hierarchy 4 is saved in the memory 103. Further, 1 is added to the memory counter (“005” at this time), and the tag position ID “006” is assigned.

  After that, the record generation unit 113 generates the second record in the CSV file 52 and sets the tag position ID “006” in the tag position ID column 279 of the hierarchy 4 of the second record. Then, after the tag position ID “006” is set, the hierarchical data “GGG” saved in the memory 103 is set in the data field 280 of the second record in the CSV file 52.

  When the record generation unit 113 sets the second record of the level 4, the tag position ID fields 273, 275, and 277 of the level 1, level 2, and level 3 of the second record respectively include the first record. Tag position IDs “001”, “002”, and “003” are set for each of layer 1, layer 2, and layer 3, respectively. In the data fields 274, 276, and 278 for the first record, the first record, the second record, and the second record, the hierarchy data “AAA” and “BBB” for the first record, the first record, the second record, and the second record, respectively. "," CCC ".

  After reading the hierarchical data 294 of the hierarchy 4, the tag reading unit 111 detects and reads the new start tag 235 of the hierarchy 5. Therefore, the hierarchical data 295 (“HHH”) of the hierarchical level 5 is saved in the memory 103. Further, since the next tag to be read is the end tag 236 of the hierarchy 5, 1 is added to the memory counter ("006" at this time) that has been added up to the hierarchy 4 of the second record, and the tag position ID " Number 007 ".

  Then, the record generation unit 113 sets the tag position ID “007” in the tag position ID column 281 of the hierarchy 5 of the first record in the CSV file 52. After the tag position ID is set, the hierarchy data “HHH” of the hierarchy 5 saved in the memory 103 is set in the data field 282 of the hierarchy 5 of the second record in the CSV file 52.

  After reading the end tag 236 of level 5 and before reading the end tag 239 of level 4, the tag reading unit 111 newly detects and reads the start tag 237 of another level 5. . Therefore, the hierarchy data 296 (“III”) in the new hierarchy 5 is saved in the memory 103. Further, 1 is added to the memory counter (“007” at this time), and the tag position ID “008” is assigned.

  Thereafter, the record generation unit 113 generates the third record in the CSV file 52 and sets the tag position ID “008” in the tag position ID column 291 of the third layer in the third record. Then, after setting the tag position ID “008”, the hierarchical data “III” of the hierarchical level 5 saved in the memory 103 is set in the data field 292 of the hierarchical level 5 of the third record in the CSV file 52.

  Note that when the record generation unit 113 sets the third record of the hierarchy 5, the tag position ID fields 283, 285, 287, and 289 of the third record, the hierarchy 1, the hierarchy 2, and the hierarchy 3 respectively have 2 Tag position IDs “001”, “002”, “003”, and “006” are set for each of layer 1, layer 2, layer 3, and layer 4 of the record. In the data fields 284, 286, 288, and 290 for the first record, the first record, the second record, and the second record, the hierarchy data “AAA” of the second record, the first record, the second record, and the second record, respectively. “BBB”, “CCC”, “DDD” are set.

  Thus, a CSV file 52 incorporating the XML data structure information is generated for the XML data 42.

--- About inverse transformation process ---
Next, a process for restoring the original XML data by inversely converting the CSV file generated from the XML data will be described. FIG. 7 is a diagram illustrating a processing procedure example 2 of the restoration method of the XML data structure according to the present embodiment. Here, the restoration processing unit 114 of the system 100 receives an XML data structure restoration instruction from the other company's terminal 200 or the input interface 105 on the network 140, or restores the XML data structure preset in the storage device 101. If the arrival of the time is detected (eg, the arrival of a predetermined date and time is detected by the clock function or calendar function of the computer) (s400), the XML data that has received the restoration instruction or the XML data that has come to the restoration time is generated. The text or CSV file is read from the storage device 101 to the memory 103 (s401). Of course, a comparison table is generated in advance in the storage device 101 for the XML data and the text or CSV file generated based on the XML data.

  The restoration processing unit 114 reads the records constituting the text or CSV file one by one and saves them in the memory 103 (s402). Then, duplication is determined between the tag position IDs included in the record, and a hierarchy in the XML data structure is generated for each tag position ID that does not overlap (s403). Further, for each generated hierarchy, the hierarchy data corresponding to the corresponding tag position ID is extracted and set from the record (s404), and from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected. XML data having a structure in which each hierarchy includes hierarchy data is restored (s405).

  Then, the output processing unit 115 of the system 100 transmits the XML data restored in the memory 103 to the other company's terminal 200 on the network or outputs it to the output interface 106, and ends the processing.

  Next, details of processing for importing the tag position ID from the record and CSV file generation will be described. In this description, it is assumed that the CSV file 60 shown in FIG. 12 is assumed as the CSV file to be inversely transformed, and the XML data 70 shown in FIG. 13 is assumed as the XML data restored by the inverse transformation. For example, as shown in FIG. 12, when the CSV file 60 includes two records, the restoration processing unit 114 first reads the first record, and each of the hierarchy 1, the hierarchy 2, the hierarchy 3, the hierarchy 4, and the hierarchy 5 respectively. Tag position IDs “001”, “002”, “003”, “004”, “005” in the tag position ID fields 305, 306, 307, 308, and 309 are saved in the memory 103. Similarly, the hierarchical data included in the first record is read as “AAA”, “BBB”, “CCC”, “DDD”, “EEE” and saved in the memory 103 for each of the hierarchical levels 1 to 5. . Then, a hierarchy is generated for each tag position ID saved in the memory 103, hierarchical data corresponding to this hierarchy is set, and the XML data 350 is generated.

  Next, the restoration processing unit 114 reads the second record of the CSV file 60, and similarly to the first record, the tag position IDs 310, 311, 312, 313, tiers of the tier 1, tier 2, tier 3, and tier 4, respectively. As 314, “001”, “002”, “006”, “007”, “008” are read. Then, the data of the tag position ID is saved in the memory 103 (saved in a storage area different from the storage area of the first record in the memory 103).

  Further, the restoration processing unit 114 has a tag position ID of each tag position ID group 315 saved in the first record and a tag position ID of each layer tag position ID group 316 saved in the second record. If there is a tag position ID 317 in a different hierarchy, a new tag (box 318 in the figure) is generated from this different hierarchy. The generated XML data 360 is transmitted to the other company's terminal 200 by the output processing unit 115, and the process is terminated.

  Thus, XML data can be restored from a CSV file or the like while reproducing an accurate data structure.

  According to the present embodiment, for example, XML data conforming to a distribution business message standard received from a predetermined terminal can be converted into a text or CSV format and stored while considering the XML data structure. Therefore, even if the XML data itself is lost, it can be guaranteed that the data converted into text or CSV format and stored is restored to XML data having a data structure as received from the terminal.

  Therefore, it is possible to accurately restore the XML data structure at the time of mutual conversion between the XML data and the text or CSV format data regardless of the description structure in the XML data.

  As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.

1 is an overall configuration diagram of an XML data structure restoration system in the present embodiment. It is a figure which shows the example 1 of the whole sequence of this embodiment. It is a figure which shows the whole sequence example 2 of this embodiment. It is a figure which shows Example 1 of the XML data structure in this embodiment. It is a figure which shows the structural example of the text or CSV file in this embodiment. It is a flowchart which shows the process procedure example 1 of the decompression | restoration method of the XML data structure of this embodiment. It is a figure which shows process procedure example 2 of the decompression | restoration method of the XML data structure of this embodiment. It is a figure which shows Example 2 of the XML data structure in this embodiment. It is a figure which shows Example 3 of the XML data structure in this embodiment. It is a figure which shows the structural example 1 of the text or CSV file after conversion of this embodiment. It is a figure which shows the structural example 2 of the text or CSV file after the conversion of this embodiment. It is a figure which shows the structural example of the text or CSV file of the reverse conversion process object of this embodiment. It is a figure which shows the XML data structure example 1 produced | generated by the inverse transformation process of this embodiment. It is a figure which shows the XML data structure example 2 produced | generated by the inverse transformation process of this embodiment.

Explanation of symbols

100 XML Data Structure Restoration System 101 Storage Device 102 Program 103 Memory 104 CPU
105 Input Interface 106 Output Interface 107 Communication Device 110 Data Acquisition Unit 111 Tag Reading Unit 112 Location Information Storage Unit 113 Record Generation Unit 114 Restoration Processing Unit 115 Output Processing Unit 200 Other Company Terminal

Claims (5)

A computer system for interconverting XML data and text or CSV format data,
A data acquisition unit that receives XML data from a predetermined terminal on the network and stores it in a storage device;
XML data is read from the storage device into the memory, a start tag in the XML data is searched, and a tag reading process is performed from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected from the lower hierarchy. Executing a tag reading unit;
A tag position ID group for assigning a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y, and for a route from the hierarchy X to the hierarchy Y A position information storage unit for storing the
The hierarchical data described in each hierarchical level from the hierarchical level X to the hierarchical level Y of the XML data is read from the XML data, and the XML data of each hierarchical level corresponds to the tag positional ID of each hierarchical level included in the tag positional ID group in the memory. A record generation unit that generates a record in which the tag position ID and the hierarchy data are associated with each other for the route from the hierarchy X to the hierarchy Y, and stores the record in the storage device as text or CSV data;
If an instruction to restore the XML data structure is received from a predetermined terminal or input interface on the network, or if the arrival of the restoration time of the XML data structure preset in the storage device is detected, the record is stored in the memory from the storage device. And generating a hierarchy in the XML data structure for each tag position ID included in the record, extracting and setting the hierarchy data corresponding to the tag position ID from the record for each generated hierarchy, and starting tag A restoration processing unit for restoring XML data having a structure in which each hierarchy from the hierarchy X searched for the hierarchy X to the hierarchy Y where the end tag is detected includes hierarchy data;
An output processing unit that transmits the XML data restored in the memory to a predetermined terminal on the network or outputs it to an output interface;
An XML data structure restoration system comprising: The tag reading unit, after executing the reading process of the end tag of the layer Y, searches for a start tag different from that of the layer Y in the upper layer A including the layer Y, and this start tag From the hierarchy A searched for to the lower hierarchy, the tag reading process is executed up to the hierarchy B where an end tag different from that of the hierarchy Y is detected,
The position information storage unit assigns a tag position ID that uniquely identifies each tag in correspondence with tags read in each hierarchy from the hierarchy A to the hierarchy B, and has already assigned a tag position ID. The tag position ID group numbered for the route from the hierarchy A to the hierarchy B is merged with the tag position ID group for the route from the predetermined hierarchy X to the hierarchy A, and the route of the hierarchy X to A to B is merged. It is stored in the memory as a tag position ID group,
The record generation unit reads hierarchical data described in each of the hierarchical levels X to AB of the XML data from the XML data, and each hierarchical level included in the tag position ID group in the memory includes the XML data of each hierarchical level A record in which the tag position ID and the hierarchical data are associated with each other for the route to the hierarchy X to AB is generated and stored in the storage device as text or CSV format data. And
The restoration processing unit reads the record from the storage device into the memory, generates a hierarchy in the XML data structure for the tag position IDs included in the record from the hierarchy A to the hierarchy B, and generates the generated hierarchy For each hierarchy from A to B, the hierarchy data corresponding to the corresponding tag position ID is extracted from the record and set, and each hierarchy from the hierarchy A to the hierarchy B has a structure including hierarchy data The data is restored, and the XML data is added to the already restored XML data from the hierarchy X to the hierarchy Y, and the XML data having a structure in which each of the hierarchies X to A to B includes the hierarchy data is added. To restore,
The XML data structure restoration system according to claim 1, wherein:   The XML data structure restoration system according to claim 1 or 2, wherein the XML data is data on shipping packaging among data compliant with a distribution business message standard. A computer that interconverts XML data and text or CSV data,
A process of receiving XML data from a predetermined terminal on the network and storing it in a storage device;
XML data is read from the storage device into the memory, a start tag in the XML data is searched, and a tag reading process is performed from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected from the lower hierarchy. Processing to execute
A tag position ID group for assigning a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y, and for a route from the hierarchy X to the hierarchy Y Storing the data in memory,
The hierarchical data described in each hierarchy from the hierarchy X to the hierarchy Y of the XML data is read from the XML data, and the XML data of each hierarchy corresponds to the tag position ID of each hierarchy included in the tag position ID group in the memory. Processing for generating a record in which the tag position ID and the hierarchy data are associated with each other for the route from the hierarchy X to the hierarchy Y, and storing the record in the storage device as text or CSV data;
If an instruction to restore the XML data structure is received from a predetermined terminal or input interface on the network, or if the arrival of the restoration time of the XML data structure preset in the storage device is detected, the record is stored in the memory from the storage device. And generating a hierarchy in the XML data structure for each tag position ID included in the record, extracting and setting the hierarchy data corresponding to the tag position ID from the record for each generated hierarchy, and starting tag A process of restoring XML data having a structure in which each hierarchy from the hierarchy X searched for the hierarchy to the hierarchy Y where the end tag is detected includes hierarchy data;
A process of transmitting the XML data restored in the memory to a predetermined terminal on the network or outputting it to an output interface;
A method for restoring an XML data structure, comprising: To a computer that converts XML data and text or CSV format data,
Receiving XML data from a predetermined terminal on the network and storing it in a storage device;
XML data is read from the storage device into the memory, a start tag in the XML data is searched, and a tag reading process is performed from the hierarchy X where the start tag is searched to the hierarchy Y where the end tag is detected from the lower hierarchy. A step of performing
A tag position ID group for assigning a tag position ID that uniquely identifies each tag in correspondence with the tag read in each hierarchy from the hierarchy X to the hierarchy Y, and for a route from the hierarchy X to the hierarchy Y Storing in a memory;
The hierarchical data described in each hierarchy from the hierarchy X to the hierarchy Y of the XML data is read from the XML data, and the XML data of each hierarchy corresponds to the tag position ID of each hierarchy included in the tag position ID group in the memory. And generating a record in which the tag position ID and the hierarchy data are associated with each other for the path from the hierarchy X to the hierarchy Y, and storing the record in the storage device as text or CSV data;
If an instruction to restore the XML data structure is received from a predetermined terminal or input interface on the network, or if the arrival of the restoration time of the XML data structure preset in the storage device is detected, the record is stored in the memory from the storage device. And generating a hierarchy in the XML data structure for each tag position ID included in the record, extracting and setting the hierarchy data corresponding to the tag position ID from the record for each generated hierarchy, and starting tag Restoring the XML data having a structure in which each hierarchy from the hierarchy X searched for to the hierarchy Y where the end tag is detected includes hierarchy data;
Transmitting the XML data restored in the memory to a predetermined terminal on the network or outputting it to an output interface;
A program for restoring the XML data structure.

Images