JP2006018449A - Structured data conversion apparatus and method - Google Patents

Abstract

Differences in XML expressions caused by differences in viewpoints can be easily corrected by changing the usage of element names, attributes, and element contents.
A conversion method database 10 stores a plurality of conversion method definition files 12. The conversion engine 30 selects the conversion method definition file 12 for converting the XML data specified by the user into the XML data of the expression format specified by the user from the plurality of conversion method definition files 12. Based on the selected conversion method definition file 12, the conversion engine 30 selects elements specified by the conversion target specifying information included in the file 12 among the elements included in the XML data specified by the user. Based on the conversion operation designation information included in the file 12, a conversion operation by shifting or rotating the value between the element name, attribute, and element content of the element is executed on the target.
[Selection] Figure 1

Description

  The present invention relates to a structured data conversion apparatus and conversion method for converting the representation format of structured data (structured document), and more particularly to semi-structured data (semi-structured document) which is a kind of structured data (structured document). The present invention relates to a structured data conversion apparatus and method suitable for converting the expression format of XML data (XML document).

  With the spread of XML (Extensible Markup Language), various software (application software) for the purpose of reference, conversion processing, storage, and the like is distributed.

  Data described using XML (XML document) logically represents a tree structure having a hierarchy. Many of the above-mentioned softwares are provided with a GUI (Graphical User Interface) that makes XML data, that is, an XML document or the contents of its sub-tree, graphically presented to the user and facilitates understanding and operation thereof. . One typical example is an XML conversion support tool. This tool supports, for example, generation of a definition (XSLT stylesheet) of an transformation method for XML transformation using XSLT (XSL Transformations, XSL: Extensible Stylesheet Language) (see, for example, Non-Patent Document 1). In a general user interface of such an XML conversion support tool, the XML structures before conversion and after conversion are converted into a figure and compared, and the correspondence between the two structures is input to the user.

Conventionally, this kind of software for converting XML into a graphic analyzes the target XML data based on the syntax, and arranges its constituent elements. That is, the nested structure of XML elements starting from the root element is expressed as a tree structure as it is. Here, an element that does not include a child element is a leaf. In addition, for an element having an attribute, the attribute can also be expressed as a kind of leaf.
XSL Transformations (XSLT) Version 1.0, [online], November 16, 1999, World Wide Web Consortium (W3C), [Search June 21, 2004], Internet <URL: http: //www.w3 .org / TR / 1999 / REC-xslt-19991116>

  As described above, in the prior art, in order to graph XML data, it is common to analyze the syntax of the XML data and graph the XML data as it is based on the analysis result. However, in the XML data graphic in this prior art. Even XML data that expresses the same object will look different depending on how the viewpoint is placed in the design process of the XML expression. In other words, in the prior art, there is a problem that even XML data representing the same object is rendered differently (hereinafter referred to as problem 1). In the prior art, the difference in the XML expression due to the difference in viewpoint extends to the entire XML data created from the same viewpoint. For this reason, in the prior art, there is also a problem (hereinafter referred to as problem 2) that the operability of the tool that supports the graphic data rendering operation is impaired.

  Hereinafter, these problems 1 and 2 will be described in detail.

(Problem 1)
The purpose of drawing XML data is to present information expressed by the XML data to the user in an easily understandable manner. However, there is a case where appropriate information presentation cannot be performed depending on the application in the graphic representation based only on the syntax of the XML data. For example, when the target data is expressed as XML data, when the data name is expressed as an element name, and when the structural type of the data is expressed as an element name, both XML data are represented based on the syntax only. If it becomes, it becomes difficult to understand the correspondence between the two. The reason for this is that when designing an XML notation that expresses certain target data, the difference in the viewpoint of whether the target is captured as the subject of the data name or the subject of the structure type of the data becomes noticeable due to graphicization. It depends. A specific example is shown in FIG. FIG. 9 shows the target data X in the XML representation and three types of XML data A to C expressing the target data X. As the XML data representing the target data X, any of the XML data A to C can be used. There can be many other expressions besides this.

As described above, a major reason why various expressions are generated with respect to the same expression object is the degree of freedom inherent in XML. In general, the components of XML are:
-Element name: Concept classification-Attribute: Attribute or meta-information-Element content: Most characteristic value-Lower nesting: Used like a substructure. XML is characterized in that specific association of these elements can be defined for each application (application software). On the other hand, human concepts have a complex information structure, and if they are expressed with a simple tree structure like XML, it is very difficult to obtain a very rough approximation. Therefore, the XML designer determines an XML expression format that is considered optimal based on each object understanding and use, that is, based on the viewpoint, as in the example of FIG.

  For example, assume that an XML data conversion support tool defines a conversion method between XMLs representing two different objects. At this time, if the difference between these XML expressions is derived from the original difference of the object being expressed, the conversion between the two is not a problem because it is the purpose of the tool itself. However, in the actual XML representation, as in the above example, the difference in viewpoints by the designer at the stage of converting the object to XML is synthesized, making the definition of the conversion method unnecessarily difficult or inefficient. ing.

(Problem 2)
The difference in the XML expression due to the difference in viewpoint covers the entire area of the XML data. For this reason, the user of the XML data manipulation tool has to repeat the same type of replacement many times. This replacement is not limited to single XML data processing, but is necessary for all XML data created from the same viewpoint.

  In general, software tools are required to free humans from repeated mechanical operations, eliminating complexity and inefficiencies. For this fundamental purpose of the tool, Problem 2 is fatal.

  If, for example, the three types of XML data A to C having different representations shown in FIG. 9 all represent data X, this is not the surface syntax of XML, but the meaning thereof is understood. It is possible to eliminate the difference in expression method if it can be made into a figure based on the above. However, in practice, it is difficult to automatically analyze the meaning embedded in the XML data representation.

  The present invention has been made in view of the above circumstances, and its purpose is to provide a structured data conversion apparatus that can easily correct differences in expression format caused by differences in viewpoints by altering the usage of element names, attributes, and element contents, and It is to provide a method.

  According to one aspect of the present invention, a structured data conversion apparatus for converting the representation format of structured data is provided. The structured data conversion apparatus includes a plurality of conversion method definition files stored in a conversion method database, the conversion target specifying information for specifying an element to be converted, and the element specified by the conversion target specifying information. , The structured data specified by the user from the plurality of conversion method definition files including the conversion operation specification information that defines the shift or rotation of the value between the element name, attribute, and element content of the element. A conversion method definition file selection means for selecting a conversion method definition file to be converted into structured data of a specified expression format, and a structuring designated by the user based on the conversion method definition file selected by the selection means Among the elements included in the data, specify the conversion target specification information included in the conversion method definition file A conversion operation that performs a conversion operation by shifting or rotating a value between the element name, attribute, and element contents of the element based on the conversion operation specification information included in the conversion method definition file. Means.

  In the structured data conversion apparatus having the above-described configuration, the conversion target designation information in the conversion method definition file selected by the conversion method definition file selecting means among the elements included in the structured data designated by the user. Based on the conversion operation specification information in the conversion method definition file, the conversion operation means executes a conversion operation by shifting or rotating the value between the element name, attribute, and element content of the element. Is done.

  As described above, according to the structured data conversion device having the above-described configuration, the data conversion for correcting the expression depending on the designer's viewpoint is included in the structured data designated by the user. Each element designated by the conversion target designation information is executed by a conversion operation by shifting or rotating a value between the element name, attribute, and element content of the element. By this conversion operation, the usage of the element name, attribute, and element content specified by the conversion operation specification information is changed for each element specified by the conversion target specification information, and the representation format of the structured data is structured data conversion. It is converted into another representation format specific to the conversion method definition file applied to.

  Here, in the conversion operation specification information in the conversion method definition file, the element name, attribute, and element contents of the element related to the element specified by the conversion target specification information included in the conversion method definition file are specified as fields. While the field specification column is included, the conversion operation means specifies the old value of the field specified in the preceding field specification according to the field specification column in the field specification following the preceding field specification. It is preferable to include a copying means for copying as a new value of the field. In this way, the data conversion for correction of the expression depending on the designer's viewpoint is performed using the field designation column for each designated element, and the designation of usage of the element name, attribute, and element content of the designated element is designated. Can be easily defined. The conversion method definition file including a field specification column for each specified element can be applied to the same kind of conversion of all structured data created in a corresponding expression format, that is, structured data created from the same viewpoint.

  According to the present invention, the difference in expression format caused by the difference in viewpoint can be easily corrected by changing the usage of element names, attributes, and element contents for each predetermined element.

Hereinafter, an embodiment in which the present invention is applied to an XML data conversion apparatus that converts an expression format of XML data that is representative of structured data will be described with reference to the drawings.
FIG. 1 is a block diagram showing the configuration of an XML data conversion apparatus according to an embodiment of the present invention. The XML data conversion apparatus includes a conversion method database 10, an XML database 20, an XML data conversion engine 30, a memory 40, an input device 50, and an output device 60.

  The conversion method database 10 stores a conversion method index file 11 and a plurality of conversion method definition files 12. The conversion method index file 11 is a file storing a conversion method index. The conversion method definition file 12 is a file that defines a conversion method of XML data.

  FIG. 2 shows the data structure of the conversion method index file 11. The conversion method index file 11 stores a plurality of sets of an input format name 111, an output format name 112, and a file name 113 of the conversion method definition file 12 as index information. By referring to the conversion method index file 11 using the input format name and output format name pair as a key, the conversion method definition file 12 that defines a conversion method specific to the input format name and output format name pair is defined. You can get the file name. Here, the input format name and the output format name are information for specifying the corresponding expression format, for example, the identification name of the application that handles the XML of the corresponding expression format.

  FIG. 3 shows the data structure of the conversion method definition file 12. The conversion method definition file 12 includes an input format name 121, an output format name 122, and at least one conversion target / conversion operation designation information 123. As illustrated in FIG. 3, the conversion target / conversion operation designation information 123 includes conversion target designation information 123a and at least one conversion operation designation information 123b.

The conversion target designation information 123a designates a conversion target of XML data. Here, the conversion target designation information 123a designates an element to be converted by a description conforming to XPath (XML Path Language), which is recommended by the World Wide Web Consortium (W3C). The conversion operation designation information 123b includes a list of field designation (field designation information). There are four types of field specification: • “Constant”: Constant value enclosed in quotation marks • Name: Element name • Content: Element content • @Attribute name: One of the attribute values with that name.

  Referring again to FIG. 1, the XML database 20 stores a plurality of XML data files (XML documents) 21. The XML data file 21 designated by the user's operation from among the plurality of XML data files 21 stored in the XML database 20 is the object of XML data conversion.

  It is assumed that the conversion method database 10 and the XML database 20 are stored in an external storage device (not shown) represented by a hard disk drive. Note that the conversion method database 10 and the XML database 20 can be made independent from the XML data converter, and can be accessed from the conversion engine 30 in the XML data converter via a network, for example. In this case, the conversion method database 10 and the XML database 20 can be shared by a plurality of XML data conversion apparatuses.

  The XML data conversion engine 30 converts the XML data file specified by the user operation according to the conversion method defined in the conversion method definition file 12 specific to the pair of the input format name and the output format name specified by the user operation. To do. The conversion engine 30 includes a user interface 31. The user interface 31 serves as an interface for the user to use the conversion engine 30. The conversion engine 30 is realized by the computer reading and executing a specific software program installed in the computer. This program is stored in advance in a computer-readable storage medium (a magnetic disk typified by a floppy (registered trademark) disk, a CD-ROM, an optical disk typified by a DVD, a semiconductor memory typified by a flash memory, etc.). Can be distributed. Further, this program may be downloaded (distributed) via a network.

  The memory 40 includes storage areas 41 to 45. The storage area 41 is a conversion method index file area for temporarily storing the conversion method index file 11 read from the conversion method database 10 by the conversion engine 30. The storage area 42 is a conversion method definition file area for storing the conversion method definition file 12 read from the conversion method database 10 by the conversion engine 30. The storage area 43 is an XML data file name area for storing the file name of the XML data file 21 to be converted designated by the user operation. The storage area 44 is an XML data file area for storing the XML data file 21 having a file name designated by a user operation. The storage area 45 is a work area for the conversion engine 30.

  The input device 50 inputs an input format name and an output format name for specifying the conversion method definition file 12 used for the XML data conversion, a file name of the XML data file 21 to be subjected to the XML data conversion, and the like by a user operation. Used to do. The input device 50 is, for example, a keyboard or a mouse. The output device 60 is, for example, a display device, and is used to display a file name input request to the user, a list of input format name / output format name pairs, and the like.

  In the present embodiment, the conversion method definition file 12 stored in the conversion method database 10 is created by, for example, a user. The meanings and restrictions of the conversion target designation information 123a and the conversion operation designation information 123b in the conversion target / conversion operation designation information 123 stored in the conversion method definition file 12 are as follows.

<Meaning>
The conversion target designation information 123a is an XPath notation for determining whether or not a certain XML element is a conversion target.
The field designation listed in each conversion operation designation information 123b indicates that the old value of the preceding field is set as the new value of the subsequent field. It is also possible to enumerate three or more field specifications and forward the values.
When the same field is specified at the beginning and the end of the field specification column included in the conversion operation specification information 123b, the conversion operation forms a forward rotation (rotation) of the circulated values.
• The constant value is the value enclosed in quotation marks.
-Setting a certain value for the element content indicates that the value is used as the new element content of the element.
-Setting a certain value to the element name name means that the value is used as the new element name of the element.
-Setting a value to an attribute indicates overwriting the attribute value or creating a new attribute.

<Restrictions>
• Constants can only be used at the beginning of operation specifications.
Except in the case of a rotation operation, if the beginning of the conversion operation specification information 123b is an attribute name, the attribute is lost from the converted XML.
Except in the case of a rotation operation, if the beginning of the conversion operation specification information 123b is content, the element is an empty element after conversion.
Except in the case of a rotation operation, name cannot be used at the head of the conversion operation designation information 123b. The reason is that an element always has an element name at the beginning of the tag.
• Name, content, and the same attribute name cannot be used more than once through a single transformation method definition, except when specified at the beginning and end of a rotation operation.

  Next, the overall flow of the operation of the present embodiment will be described with reference to the flowchart of FIG. First, when the XML data conversion engine 30 is activated, a file name input request screen for requesting the user to input the file name of the XML data file to be converted is displayed on the output device (display device) by the user interface 31. 60 is displayed (step S1). In this state, when the conversion engine 30 detects that the user has performed an operation of inputting the file name of the desired XML data file 21 using the input device 50 (step S2), the conversion file 30 stores the input file name in the memory 40. It stores in the XML data file name area 43 (step S3).

  Next, the conversion engine 30 reads the input file name, that is, the XML data file 21 having the file name designated by the user, from the XML database 20 into the XML data file area 44 of the memory 40 (step S4). The conversion engine 30 reads the conversion method index file 11 from the conversion method database 10 into the conversion method index file area 41 of the memory 40 (step S5).

  The conversion engine 30 generates a list of pairs of the input format name 111 and the output format name 112 according to the conversion method index file 11 read into the conversion method index file area 41, and outputs the list to the output device (display) by the user interface 31. (Device) 60 is displayed (step S6). As described above, the input format name 111 and the output format name 112 stored in the conversion method index file 11 are identification names of applications that handle XML in the corresponding format. The user can identify the first application identification name that can handle the XML data file (the XML data file created from the first viewpoint) selected by the user according to the input request screen, and the XML data in the target format. The identification name of the second application capable of handling the file (the XML data file created from the second viewpoint) is specified. Then, the user operates the input device 50 to select the input format name 111 and the output format name 112 that match the identified pair of identification names of the first and second applications from the list.

  When an arbitrary input format name 111 and output format name 112 pair is selected by the user's operation (step S7), the conversion engine 30 functions as a search unit. As a result, the conversion engine 30 refers to the conversion method index file 11 read in the area 41 by using the selected pair of the input format name 111 and the output format name 112 as a key, thereby converting the conversion method unique to the pair. The file name of the definition file 12 is searched (step S8). Then, the conversion engine 30 functions as a conversion method definition file selection means, selects the conversion method definition file 12 having the searched file name from the conversion method database 10, and reads it into the conversion method definition file area 42 of the memory 40 (step). S9). At this time, the conversion engine 30 checks whether the definition content of the conversion method definition file 12 read from the conversion method database 10 satisfies the above-described restrictions, and if there is a nonconformity, notifies the user of an error via the user interface 31. To do. In addition, when the conversion method definition file 12 is newly stored in the conversion method database 10, such a test | inspection is also possible. In this case, the number of inspections can be reduced.

  When the selected conversion method definition file 12 is read into the area 42, the conversion engine 30 functions as a conversion operation unit. As a result, the conversion engine 30 causes the elements to be converted among the elements included in the data (XML data) of the XML data file 21 read into the area 44 according to the conversion method definition file 12 read into the area 42. And the conversion operation based on the conversion operation designation included in the conversion method definition file 12 is performed on the element to be converted (step S10). In this conversion operation, as will be described later, a value shift (and rotation) is performed between the element name, attribute, and element content of the element to be converted. The XML data conversion result by the conversion engine 30 is displayed on the output device (display device) 60 by the user interface 31 (step S11).

  Next, the detailed procedure of step S10 (XML data conversion process) by the conversion engine 30 will be described with reference to FIGS. First, the conversion engine 30 selects the first element from the data of the XML data file 21 read into the area 44, that is, the XML data to be converted (step S21). Next, the conversion engine 30 selects the first conversion target / conversion operation designation information 123 from the conversion method definition file 12 read in the area 42 (step S22).

  The conversion engine 30 refers to the conversion target designation information 123a in the selected conversion target / conversion operation designation information 123, and whether the selected element is the conversion target element designated by the conversion target designation information 123a. Is determined (step S23). If the selected element is not a conversion target element, the conversion engine 30 determines whether or not the unprocessed conversion target / conversion operation designation information 123 is included in the conversion method definition file 12 (step S24).

  If the conversion method definition file 12 includes unprocessed conversion target / conversion operation designation information 123, the conversion engine 30 selects the next conversion target / conversion operation designation information 123 from the file 12. (Step S25), the process returns to the determination process of step S23. On the other hand, if the unprocessed conversion target / conversion operation designation information 123 is not included in the conversion method definition file 12, the conversion engine 30 determines whether unprocessed elements are included in the XML data to be converted. (Step S26).

  If the unprocessed element is not included in the XML data to be converted, the conversion engine 30 ends the XML data conversion process. On the other hand, if the unprocessed element is included in the XML data to be converted, the conversion engine 30 selects the next element from the XML data to be converted (step S27). Then, the conversion engine 30 returns to step S22 and selects the first conversion target / conversion operation designation information 123 from the conversion method definition file 12 again.

  On the other hand, when the element selected in step S21 or S27 is designated as a conversion target (step S23), the conversion engine 30 proceeds to step S28. In this step S28, the conversion engine 30 selects the first conversion operation designation information 123b from the currently selected conversion target / conversion operation designation information 123. Then, the conversion engine 30 functions as a determination unit (rotation operation determination unit), and determines whether a rotation operation is specified as the conversion operation based on the selected conversion operation specification information 123b (step S29). As described above, whether the rotation operation is designated depends on whether the same field is designated at the beginning (first) and the end (last) of the field designation columns included in the conversion operation designation information 123b. Judgment is possible.

  If the rotation operation is specified, the conversion engine 30 temporarily saves (saves) the value of the field specified by the last field specification of the conversion operation specification information 123b in the work area 45 (step S30). Then, the process proceeds to step S31. On the other hand, if the rotation operation is not designated, the conversion engine 30 skips step S30 and proceeds to step S31.

  In step S31, the conversion engine 30 sets the last field specification in the conversion operation specification information 123b as Fc. Fc indicates a field specification currently being processed (that is, current). Next, the conversion engine 30 sets the field designation preceding Fa in the conversion operation designation information 123b as Fa (step S32). Then, the conversion engine 30 functions as copying means (value shifting means), and copies the field value specified by Fa to the field value specified by Fc (step S33). That is, the conversion engine 30 shifts the value of the field specified by Fa to the value of the subsequent field specified by Fc. In this way, the old value of the preceding field is set as the new value of the following field.

  Next, the conversion engine 30 determines whether Fa is the head field specification in the conversion operation specification information 123b (step S34). If Fa is not the head field designation, the conversion engine 30 sets the current Fa as a new Fc (step S35) and returns to step S32. In step S32, the conversion engine 30 sets the field specification preceding the newly set Fc in the conversion operation specification information 123b as Fa. Then, as described above, the conversion engine 30 copies the value of the field specified by Fa to the value of the field specified by Fc (step S33).

  As described above, it is assumed that, as a result of repeating steps S32 to S35, Fa becomes the first field designation in the conversion operation designation information 123b (step S34). In this case, if the rotation operation is designated (step S36), the conversion engine 30 sets the value stored in the work area 45 in the previous step S30 to the value of the field designated by Fc (step S36). S37). As a result, the field value (old value) specified by the last specification in the conversion operation specification information 123b is used as the value (new value) of the field specified by the second field specification in the conversion operation specification information 123b. Is set. That is, for the element specified by the conversion target specifying information 123a, the rotation of the value between the element name, attribute, and element content of the element specified by the conversion operation specifying information 123b is realized. On the other hand, if the rotation operation is not designated (step S36), the conversion engine 30 performs the following processing in accordance with the field designation indicated by Fa (here, the first field designation). That is, if the attribute value is specified by the head field specification (step S38), the conversion engine 30 functions as an attribute removal unit and removes the attribute from the current element (step S39). If the content is specified by the head field specification (step S38), the conversion engine 30 functions as an empty element conversion unit and sets the current element as an empty element (step S40).

  When the conversion engine 30 executes step S37, S39 or S40, the conversion target / conversion operation designation information 123 determines whether or not the unprocessed conversion operation designation information 123b is included for the current element (step S41). ). If the unprocessed conversion operation designation information 123b is included, the conversion engine 30 selects the next conversion operation designation information 123b from the conversion target / conversion operation designation information 123 (step S42). Then, the conversion engine 30 returns to the determination process in step S29. On the other hand, if the unprocessed conversion operation specification information 123b is not included, the conversion engine 30 determines whether the conversion method definition file 12 includes the unprocessed conversion target / conversion operation specification information 123 (step S43). ). If the unprocessed conversion target / conversion operation designation information 123 is included, the conversion engine 30 returns to step S25 and selects the next conversion target / conversion operation designation information 123 from the conversion method definition file 12. To do. On the other hand, if the unprocessed conversion target / conversion operation designation information 123 is not included, the conversion engine 30 returns to step S27 to determine whether the conversion target XML data includes an unprocessed element. If an unprocessed element is not included, the conversion engine 30 ends the XML data conversion process.

Next, a specific example of the XML data conversion process by the conversion engine 30 will be described with reference to FIGS. 7 and 8 in addition to the flowchart values of FIGS.
7A shows an example of one element (element whose element name is “extended device”) of the XML data to be converted, and FIG. 7B shows the element of FIG. 7A. An example of an element after XML data conversion (element whose element name is “card type disk”) is shown. Assume that applications (application software) that are compatible with the processing of XML data including elements of different representation formats shown in FIGS. 7A and 7B are applications AP1 and AP2, respectively.

  FIG. 8 shows an example of the conversion target / conversion operation designation information 123 in the conversion method definition file 12 used for this XML data conversion. In FIG. 8, the character string starting with the symbol # represents the conversion target designation information 123a or the description (note) related to the field designation described on the left side.

  The conversion target / conversion operation designation information 123 shown in FIG. 8 includes conversion target designation information 123a for designating “extended device” as an element name of an element to be converted, and two conversion operation designation information 123b. The first conversion operation designation information 123b includes a conversion operation designation 91 indicating “shift” and three field designations 921 to 923. The field designation 921 designates the attribute value of the attribute “name” by having the @ name as the @ attribute name. The field designation 922 designates name, that is, an element name. When “shift” is designated by the conversion operation designation 91, the field designation 922 designates the element name as the attribute value of the attribute “name” designated by the preceding field designation 921. The field designation 923 designates the attribute value of the attribute “classification” by having @classification as the @attribute name. When “shift” is designated by the conversion operation designation 91, the field designation 923 designates that the attribute value of the attribute “classified” is the old element name designated by the preceding field designation 922.

  Next, the second (last) conversion operation specification information 123b includes a conversion operation specification 93 indicating shift and two field specifications 941 to 942. The field designation 941 designates the attribute value of the attribute “weight” by having @weight as the @attribute name. The field designation 942 designates content, that is, element content. When “shift” is designated by the conversion operation designation 93, the field designation 942 designates that the element content is the attribute value of the attribute “weight” designated by the preceding field designation 941.

  Assume that the application AP2 wants to process XML data including elements in the expression format shown in FIG. In this case, when a list of pairs of input format names and output format names is displayed (step S6), the user selects input format names and output format names that match the identification name pairs of AP1 and AP2 from the list. Select a pair. Then, the conversion engine 30 selects the conversion method definition file 12 having a file name unique to the pair of AP1 and AP2 from the conversion method database 10 (step S8). The conversion method definition file 12 includes conversion target / conversion operation designation information 123 shown in FIG. The conversion engine 30 executes the data conversion processing of the XML data including the elements shown in FIG. 7A according to the conversion target / conversion operation designation information 123 as follows.

  First, it is assumed that the element “extended device” shown in FIG. 7A is selected from the XML data to be converted (step S21 or S27). Further, it is assumed that the conversion target / conversion operation designation information 123 shown in FIG. 8 including the conversion target designation information 123a for designating the element “extended device” as the conversion target is selected (step S22 or S25). None of the two conversion operation designation information 123b included in the conversion target / conversion operation designation information 123 designates a rotation operation. This can be determined from the fact that the same field is not designated at the beginning and end of each of the two conversion operation designation information 123b.

  When the rotation operation is not designated, first, the last field designation 923 (= @ classification) and the field designation 923 out of the field designations 921 to 923 included in the first conversion operation designation information 123b are preceded. Based on the field designation 922 (= name) (steps S31 and S32), the value (attribute value) of the attribute “classification” is set to the selected element name (old element name) “extended device” (step S33). ).

  Next, based on the second field designation 922 (= name) of the field designations 921 to 923 and the first field designation 921 (= @ name) preceding the field designation 922 (steps S35 and S32), The element name of the element after conversion is set to “card type disk” (see FIG. 7A) which is the value of the attribute “name” (step S33).

Next, since the head field designation 921 is an @ name and an attribute value of an attribute having the name “name” is designated (step S38), the attribute “name” is removed from the current element. (Step S39). That is, the attribute “name” is lost. At this stage, the element shown in FIG. 7A is the next element (current element).
<Card type disk classification = "Extended device" Format = "DK123EC" Weight = "35" Capacity = "16"/>
Has been converted.

  Next, the second (last) conversion operation designation information 123b is selected from the conversion target / conversion operation designation information 123 shown in FIG. 8 (steps S41 and S42). As described above, the second (last) conversion operation designation information 123b also does not designate a rotation operation. In this case, based on the field designations 941 and 942 included in the second (last) conversion target / conversion operation designation information 123, that is, the last field designation 942 (= content) and the field designation preceding the field designation 942. 941 (= @ weight) (steps S31 and S32), the element content is set to the attribute “weight” value (“35”) (step S33). When this element content is set, an end tag </ element name>, that is, a </ card type disk> is additionally set immediately after the element content.

  Next, since the first field designation 941 is @weight and the attribute value of the attribute having the name “weight” is designated (step S38), the attribute “weight” is removed from the current element. (Step S39). Thereby, the element shown in FIG. 7A is converted into the element shown in FIG. 7B having a different representation format. Through similar conversion processing, XML data in an expression format suitable for the application AP1 including the elements shown in FIG. 7A is converted into XML data in an expression format compatible with the application AP2. That is, in the present embodiment, XML data in an expression format that can be processed by the application AP1 but cannot be processed by the application AP2 can be converted into XML data in an expression format that can be processed by the application AP2. The reverse XML data conversion is also possible. 7A and 7B, the XML data of one of the representation formats is converted into the XML data of the other representation format by the XML data conversion device of FIG. It is possible to create a graphic along the desired viewpoint. Here, the conversion method defined by the conversion target / conversion operation designation information 123 shown in FIG. 8 can be applied to all XML data created from the same viewpoint as in FIG.

  In the example of FIG. 8, field specification for specifying a constant is not used. If a field specification that specifies a constant is used at the beginning of the field specification column, this constant is set as the value of the field specified in the subsequent field specification.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment.

FIG. 1 is a block diagram showing the configuration of an XML data (structured data) conversion apparatus according to an embodiment of the present invention. The figure which shows the data structure of the conversion method index file 11 in FIG. The figure which shows the data structure of the conversion method definition file 12 in FIG. The flowchart which shows the whole flow of operation | movement of the embodiment. The figure which shows a part of flowchart which shows the detailed procedure of step S10 (XML data conversion process) in FIG. The figure which shows the remainder of the flowchart which shows the detailed procedure of step S10 (XML data conversion process) in FIG. The figure which shows the example of one element of the XML data used as conversion object matched with the example of the element after conversion. The figure which shows an example of the conversion object / conversion operation designation | designated information 123 used for the XML data conversion shown in FIG. The figure which shows that the XML data of a different expression format is produced by the difference in a viewpoint of an XML data designer, when expressing the same object by XML data.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Conversion method database, 11 ... Conversion method index file, 12 ... Conversion method definition file, 20 ... XML database, 21 ... XML data file, 30 ... Conversion engine, 31 ... User interface, 40 ... Memory, 41 ... Conversion method index File area 42 ... Conversion method definition file area 43 ... XML data file name area 44 ... XML data file area 45 ... Work area 50 ... Input device 60 ... Output device 123 ... Conversion target / conversion operation designation information , 123a ... conversion target designation information, 123b ... conversion operation designation information 123b.

Claims (10)

In a structured data conversion apparatus for converting the representation format of structured data,
Multiple conversion method definition files stored in the conversion method database, and for the conversion target specification information for specifying the element to be converted and the element specified by the conversion target specification information, the element name and attribute of the element Structured data in an expression format specified by the user from among multiple conversion method definition files containing conversion operation specification information that defines shift or rotation of values between the element contents A conversion method definition file selection means for selecting a conversion method definition file for conversion to
Based on the conversion method definition file selected by the conversion method definition file selection means, among the elements included in the structured data specified by the user, the conversion target specification included in the conversion method definition file Based on the conversion operation specification information included in the conversion method definition file, a conversion operation by shifting or rotating a value between the element name, attribute, and element content of the element A structured data conversion device comprising: conversion operation means for executing The conversion operation specification information included in the conversion method definition file is a field for the element name, attribute, and element content of the element regarding the element specified by the conversion target specification information included in the conversion method definition file. Contains a field specification column specified as
The conversion operation means is a copying means for copying the old value of the field designated by the preceding field designation as the new value of the field designated by the field designation following the preceding field designation in accordance with the field designation column. The structured data conversion device according to claim 1, comprising: The conversion operation means is a determination means for determining that a rotation operation is specified when the first and last fields are specified in the field specification column included in the conversion operation specification information. Further including
When the determination unit determines that the rotation operation is specified, the copying unit replaces the old value of the field specified by the last field specification in the field specification column with the field specification column. The structured data conversion device according to claim 2, wherein a new value of the field designated by the second field designation is set.   The conversion operation means determines that the rotation operation is not specified by the determination means, and if the attribute is specified at the beginning of the field specification column, the conversion target in the structured data conversion 4. The structured data conversion apparatus according to claim 3, further comprising attribute removal means for removing the attribute from the element designated by the designation information.   The conversion operation means determines that the rotation operation is not specified, and if the determination means determines that the content of the element is specified at the beginning of the field specification column, the conversion is being performed during structured data conversion. 4. The structured data conversion apparatus according to claim 3, further comprising empty element converting means that uses an element specified by the target specifying information as an empty element. As a field specification that can be defined by the conversion operation specification information, a first field specification that specifies an element name, a second field specification that specifies an element content, and a third value that specifies an attribute value having the specified attribute name There are at least three types of field designations,
The copying means includes
If the field specification following the preceding field specification is the first field specification, the value of the field specified by the preceding field specification is set as the element name,
When the field specification subsequent to the preceding field specification is the second field specification, the value of the field specified by the preceding field specification is set as the element content,
When the field specification subsequent to the preceding field specification is the third field specification, the value of the field specified by the preceding field specification is used as the value of the attribute having the attribute name specified by the third field specification. The structured data conversion device according to claim 2, wherein the structured data conversion device is set. As a field specification that can be defined by the conversion operation specification information, in addition to the first to third field specifications, a fourth field specification that specifies a constant that can be used only at the head of the field specification column is prepared. Has been
The copying means includes
If the preceding field specification is the fourth field specification, the constant specified by the fourth field specification is set as the value of the field specified by the field specification following the fourth field specification. The structured data conversion apparatus according to claim 6, wherein: The conversion method database includes a pair of an input format name that specifies an expression format of structured data to be converted and an output format name that specifies an expression format of structured data after conversion, and the input format name and output format. Stores a conversion method index file in which the file name of the conversion method definition file used for conversion of the expression format specified by the name pair is stored in association with each other,
The structured data conversion device comprises:
A user interface that allows a user to select a desired input format name and output format name pair by displaying a list of input format name and output format name pairs;
A search means for searching the conversion method index file for a file name associated with the input format name and output format name pair selected from the list;
The structured data conversion apparatus according to claim 1, wherein the conversion method definition file selection unit selects a conversion method definition file having a file name searched by the search unit from the database. In the structured data conversion method for converting the representation format of structured data,
Multiple conversion method definition files stored in the conversion method database, and for the conversion target specification information for specifying the element to be converted and the element specified by the conversion target specification information, the element name and attribute of the element Structured data in an expression format specified by the user from among multiple conversion method definition files containing conversion operation specification information that defines shift or rotation of values between the element contents Selecting a conversion method definition file for conversion to
Based on the selected conversion method definition file, among the elements included in the structured data specified by the user, the element specified by the conversion target specification information included in the conversion method definition file is targeted. And performing a conversion operation by shifting or rotating a value between the element name, attribute, and element content of the element based on the conversion operation designation information included in the conversion method definition file. A structured data conversion method characterized by: The conversion operation specification information included in the conversion method definition file is a field for the element name, attribute, and element content of the element regarding the element specified by the conversion target specification information included in the conversion method definition file. Contains a field specification column specified as
In the step of executing the conversion operation, the old value of the field specified by the preceding field specification is copied as the new value of the field specified by the field specification following the preceding field specification according to the field specification column. The structured data conversion method according to claim 9, further comprising the step of:

Images