TW200521728A - System, method and machine-readable storage medium of transformation document management for structural language message - Google Patents

Abstract

A system, method and machine-readable storage medium of transformation document management for structural message include a storage device and a record generation module. The storage device stores a first and a second definition document, and a transformation document. The record generation module receives the first and second definition document, and transformation document, parses a source identity, a target identity and target structure path. The record generation module parses a source structure path and a transformation rule corresponding to each target structure path, and generates a transformation table including the source and target identity, source and target structure path, and the transformation rule.

Description

200521728

FIELD OF THE INVENTION The present invention is a message management system and method, and more particularly a structured message conversion file management system and method. Previous technology Today, data exchange and integration within or between companies are all implemented using eXtensible Markup Unguage (XML),

as basic. Taking RosettaNet, a standard currently used in the supply chain of high-tech industries, as an example, through the partner interface process CPaftnei · Interface Process (Pip) to define the operation process, to facilitate electronic transactions between enterprises. Its definition includes message format, file content, participating Roles and operational processes, among which the content of the messages exchanged are based on XML standards. With this trend, however, for system developers using this standard, many repetitive and similar XML file conversion procedures will need to be developed. Therefore, how to make XML files using different extensible markup language schemas (XML schemas) interchangeable is a problem that system developers often need to face.

On common data transformation issues, the current approach is roughly divided into two types. One is to write transformation files for two different XML schemas, for example, Extensible Stylesheet Language: Transformations (XSLT) files. XML files that use one schema can be converted into UL files that use another schema; another is to use existing tools such as XML Mapper for conversion. xSLT is another XML-based language (a subset of XSL, an extensible style sheet language). XSL is used to define the format of an XML file, while xslt contains Fan Wei and instructions to

200521728 V. Description of invention (2) _ Structure of selection and operation data. Whatever method is used, it will lead to the same conversion program that may be repeatedly written between: good first: 'vendor source, and when the number of elements of the XML file] = system 1 is not only easy to make mistakes in the funding process; It is more difficult to debug XML files between the three vendors. Beyond daggers, integration is more than ‘needs a system and method to effectively share rule definition files or generate new conversion rules: write = conversion burden on the sender. In view of this, the purpose of the present invention is to provide a system and method for document exchange and replacement, which can be effectively converted by the conversion history of the conversion history and the automatic generation technology of the conversion template. The conversion rules that have been written have been written to generate new conversion rule definition files to reduce developers: negative: according to the above purpose, the conversion file management system and method for structured information of the present invention, first set up a storage device, a A central processing unit, a memory, a display device, an input device, and a communication device, and connected together using a bus. The storage device stores multiple extensible markup language definition files, multiple extensible markup language conversion files, and multiple conversion tables. The memory contains a conversion record generation module composed of program scripts, a conversion template query module, and a conversion template generation module. ^ ’The Extensible Markup Language Definition document completes the definition of the entire structured message content (such as an‘ XML document ’) by describing elements and hierarchical inclusion relationships between elements. Extensible Markup Language Conversion File Definition

0213-A40128TWF (Nl); SNOWBALL.ptd Page 6 200521728 V. Description of the invention (3) The conversion rules between two extensible mark messages. The conversion table contains a header and multiple conversion details. The header contains the translation table name, category, description, identification field of the source file, and identification field of the destination file. Each conversion detail record contains the element path (xpath) of the source document, the conversion principle, and the element path of the destination document. The conversion record generating module first inputs a source file, a destination file, and a conversion rule definition file. The conversion record generation module can parse (farse) the source file and the conversion rule definition file 'or parse the source file and the destination file to obtain the identification code of the source file and the | code of the destination file from the destination file or the conversion rule definition file to parse Source

Hi: There are ΓΓ elements and their destination structure path. For each-purpose change the rule definition file, # to the corresponding source structure = principle. The parsed source document identification code, destination identification code, and multiple transformation principle data including the source structure path, the conversion principle, and the destination structure path are stored in the storage device. The course conversion table's shell structure conversion template query module provides a graphical operation ^ ^ ^ ^ user lnterface; GUI), which is convenient to use. "Uraphical code, the identification code of the destination file-the identification of each rain source file. : Find the corresponding conversion table, and display the query result on the display. The first turn of the transformation template generation module first input (transitive relation) is to generate a conversion rule definition file. Shift relationship conversion table and second conversion table, this conversion rule definition file can

200521728 V. Description of the invention (4) The structured information corresponding to the purpose of the first conversion table I & a e t in the second conversion table is converted into the structured information corresponding to the file from the two conversion tables. The above transfer relationship can be judged. The conversion template produces hibiscus, and "Fidi Yisi :: Wen: No. 4 domains block to store the header of the first conversion table nt second conversion table, the source file of the source table of the second conversion table, The target file is used to store the file of the second media table β_. Next, find out the purpose of the first conversion table, the source structure path of the second conversion table, and the phase record of the source structure path according to the first conversion table. And the first: = path 'generates the corresponding conversion rule definition file to the Le Er conversion table. Implementation Figure 1 shows the system architecture diagram of the conversion management system of the conversion message structured information according to the embodiment of the present invention. According to the present invention The structured glycoside conversion file management system 10 of the embodiment includes a storage device, a central office,

I 2 12, a memory 13, a display device ", an input device 15, and a communication J are set, and are connected together using a bus 17. Anyone familiar with this item knows that combining a storage device 11, a central processing unit 12, a memory, a display device 14, an input device 15, and a communication device 16 can form a mainframe, a personal computer, and a workstation , Laptop, or other computer equipment. The storage device stores a plurality of extensible markup language definition files ill, a plurality of extensible markup language conversion files 112, and a plurality of conversion tables 113. The memory 13 contains a conversion record composed of a program instruction code to generate a branch group 1 3 1, a conversion template query module 丨 3 2 and a conversion template to generate a branch group 1 3 3. The central processing unit 12 is used to load the memory 丨 3 contained in 0213-A40128TWF (N1); SNOWBALL · ptd Page 8 200521728 V. Description of the invention (5) " " -------- J Recorded generating module 131, conversion template query module 132, and conversion sample f generating module 133, and executes document management of structured information according to program instructions and data input by the user through input device 15 The work month b, in a better case, displays the result after execution on the display device 4. The extensible markup language definition file ln completes the definition of the entire structured message valley (eg, XML file) by describing the hierarchical inclusion relationship between element 2 and 7G elements. In the best case, it can be an extensible markup.

No language schema (XML schema) or document type definition (DTD) file. According to the embodiment of the present invention, the storage device u stores three XML schema files. The contents of the first XML schema are as follows, <? Xml version = n1.0 丨 'encoding: 丨 丨 TFF-8Π? ≫ < xs: schema targetNamespace = " http: //www.mysamples.com/sampleln xmlns = Mhttp: //www.mysamples.com/samplel" xmlns: xs = M http://www.w3.org/2001/XMLSchemaM elementFormDefault = n (iualifiedn > < xs: element name = 丨 丨 author 丨 丨 type = 丨 丨 xs: string ”/ >

< xs: element name = '丨 book 丨 · > < xs: comp 1exType > < xs: sequence〉 < xs: e1ement ref = " name " / > < xs: element ref = M author '1 / >

0213-A40128TWF (N1); SNOWBALL · ptd Page 9 200521728 V. Description of Invention (6) ISBN " / > publisher ”/ > ref =, f book type = " xs: stringn / > type = " xs: string " / > < xs: e1ement ref < xs: e 1 ement ref < / xs: sequence〉 < / xs: complexType > < / xs: e1ement > < xs: e 1 ement name = f, goods " > < xs: comp 1exType > < xs: sequence〉 < xs: element maxOccurs = n unbounded " / > < / xs: sequence〉 < / xs: complexType > < / xs: element〉 < xs: element name = MISBN " < xs: e 1 ement name = `` name '' < xs: e1ement name = n publisher " type = " xs: str i ng " / > < / xs: schema > The content of the second XML schema is as follows, <? xml version = n1.0M encodings " UTF-8M? > < xs: schema targetNamespace = nhttp: // www. mysamples. com / sample2 xmlns = n http: / / www. mysamples. com / sample2 丨 'xmlns: xs = 丨 丨 http: // www · w3 · org / 2001 / XMLSchema' 丨 elementFormDefault =, 丨 qualified ”> iim

0213-A40128TWF (Nl); SNOWBALL.ptd Page 10 200521728 V. Description of Invention (7) < xs: e1ement name = " i tern " > < xs: complexType > < xs: sequence〉 id " / > name " / > maker " / > < xs: e1ement ref < xs: e1ement ref < xs: element ref < / xs: sequence〉 < / xs: complexType > < / xs: e1ement > < xs: e1ement name = " id " type = " xs: stringM / > < xs: e 1 ement name = Mmaker " type = Mxs: stringM / > < xs: element name = M name " type = " xs: string " / > < xs: e 1 ement name = 丨, root 丨, > < xs: complexType > < xs: sequence〉 ref = n item " < xs: e1ement maxOccurs = n unbounded 丨 '/ > < / xs: sequence > < / xs: complexType > < / xs: e1ement > < / xs: schema > The content of the third XML schema is shown below, UTF-8n? > <? xm1 version ^ " 1.0n encoding < xs: schema

0213-A40128TW (N1); SNOWBALL.ptd Page 11 200521728 V. Description of the invention (8) targetNamespace = Mhttp: //www.mysamples.com/sample3 xmlns ^ " http: //www.mysamples.com/sample3M xmlns : xs = n http://www.w3.org/2001/XMLScheman elementFormDefault = n qualified " > < xs: e 1 ement name: 丨, bookn > < xs: comp 1 exType > < xs: sequence > ref t em1 < xs: e1ement maxOccurs = n unbounded " / ># < / xs: sequence〉 < / xs: complexType > < / xs: e 1 ement > < xs: e1ement name = n item " > < xs: comp 1exType > name " / > idM / > writer " / > < xs: sequence〉 < xs: element ref < xs: e1ement ref < xs: e1ement ref < xs: element ref = 丨 丨 publishing-house 丨 丨 / > < / xs: sequence〉 < / xs: complexType > < / xs: e1ement > < xs: e1ement name = M list " > < xs: comp 1 exType >

0213-A40128TWF (N1); SNOWBALL · ptd Page 12 200521728 V. Description of the invention (9) < xs: sequence> < xs: e1ement ref = n object " / > < / xs: sequence > < / xs: complexType > < / xs: e1ement > < xs: element name: 丨, id 丨 'type = n xs: string " / > < xs: e 1 ement name = n name 丨 type = M xs : string " / > < xs: element name = Mobject "> < xs: comp 1exType > < xs: sequence〉 < xs: e 1 ement ref = 丨 丨 book 丨 丨 / > < / xs: sequence〉 < / xs: complexType > < / xs: e1ement > < xs: e 1 ement name = n publishing-house 丨 丨 type = Mxs: string " / > < xs: e 1 ement name = 丨 丨 writer '丨 type II 丨' xs: stringn / > < / xs: schema > In these three XML schema files, the identification domains (namespaces) are respectively, http://www.mysamples.com/ samplel ", "http: // www · mysamples · com / sampl e2 丨 丨, and 丨 http://www.mysamples.com/samp1e3n. The first XML schema file contains four elements, "name", n author ", n ISBNn, and" publisher ", where the element path (xpath) is ϊη 0213-A40128TW (Nl); SNOWBALL.ptd first 13 pages 200521728 V. Description of the invention (丨) 丨 丨 goods / book / name " '' 丨 goods / book / author '', " goods / book / ISBN '' and ng〇〇ds / book / publisher ". Second XML The schema file contains three elements, "id ", " name ', and nmakern, where the element path (xpath) is n root / item / id "," root / item / name' 丨 and 丨 'root / item / maker '.. The third XML schema file contains four elements, n name' ', `` writer' ',, id, and n pub 1 ishing-housen, where the element path (XPath) is π list / object / book / item / name ", 丨 丨 list / object / book / item / writer '丨, " list / object / book / item / id' 'and `` list / object / book / item / publishing- house ". The extensible markup language conversion file 12 defines conversion rules for two extensible markup messages', and is preferably an extensible style sheet language conversion (XSLT) file. According to the embodiment of the present invention, the storage device 11 stores two XSLT files. The first XSLT file defines a conversion rule for converting from a first XML schema file to a third XML schema file. The content is as follows, <? Xml version:丨 丨 1.0 '丨 encoding =' 'UTF-8 丨 丨? > < xs 1: sty 1 esheet xmlns: ns =, 丨 http: // www · my s am ples.com/samplel 丨 丨 xmlns: xsl = " http: //www.w3.org/1999/ XSL / Transformn > < xs1: template match: "" > < 1i st > < object >

200521728 V. Description of the invention (11) < book > < item > < name > < xsl: value-of select ^ '丨 ns: goods / ns: book / ns: name 丨' / > < / name > < id > < xsl: value-of select: 1'ns: goods / ns: book / ns: ISBN " /> < / id > < wr i ter > < xsl: value-of slect = Mns: goods / ns: book / ns: authorM / > < / wr i ter > < publ ishing-house > < xs 1: va 1 ue-of select = ,, ns: goods / ns: book / ns: publisher, 丨 / > 〈/ publishing-house > < / item > < / book > < / ob j ect > < / 1 i st > < / xs1: temp 1 ate > < / xs 1: sty 1esheet > The second XSLT file defines the conversion rules from the third XML schema file to the _ XML schema file, as shown below,

200521728 V. Description of the invention (12) <? Xml version "1 · 0 " encoding: " UTF-8 "?> ≪ xs 1: sty 1 esheet xmlns: ns = n http://www.mysamples.com / sample3n xmlns: xsl = " http: // www. w3.org/1999/XSL/TransformM > < xsl: template match = M / " > < root > < it tem > < id > < xs1: va1ue-of select = " ns: list / ns: object / ns: book / ns: item / ns: id " / > < / id > < name > < xsl: value- of select = n ns: list / ns: object / ns: book / ns: item / ns: name " / > < / name > < maker > < xs1: va1ue-o f select: ”ns: list / ns: object / ns: book / ns: item / ns: write rM / > < / maker > < / item > < / root > < / xsl: template> < / xs 1: sty 1esheet > The first XSLT file is based on the element schema of the third XML schema file,

0213-A40128TWF (N1); SNOWBALL · ptd Page 16 200521728 V. Description of the Invention (13) A conversion rule that defines which element in each element should be selected from the first XML schema file. In the first XSLT file, you want to convert the conversion rules that conform to the four elements contained in the third XML schema file: "name", n wr it erπ, "'id", and "pub 1 i sh i ng_house". (transformation ru 1 e) In addition, J is, < xs 1: va 1 ue-〇f select = n ns: goods / ns: book / ns: name " / > f ,, '丨 < xs 1: va1ue-of select ^ " ns: goods / ns: book / ns: author " / > ", 丨 丨 < xsl: value-of select = " ns: goods / ns: book / ns: ISBN " / > > »and n < xsl: value-of select = 丨 丨 ns: goods / ns: book / ns: publisher 丨 '/ > 丨 丨 ° The second XSLT file is a second XML schema file Based on the element's schema, define the transformation rules for which each element should select from the third XML schema file which element contains the data. In the first XSLT file, to convert the four elements contained in the second XML schema file, the conversion rules for idn, " name, and "maker" are 1 < xSl: value-of select two 丨 ns: list / ns: object / ns: book / ns: item / ns: idn / > π, '丨 < xs 1: va 1 ue-of

select = M ns: list / ns: object / ns: book / ns: item / ns: nameH / > '' and `` &x; l: value-of select = n ns: list / ns: object / ns: book / ns: item / ns: write r ”/ >”. According to the embodiment of the present invention, each conversion table 1 1 3 includes a header and multiple conversion detail records. The header includes the conversion table name, category, and description. 0213-A40128TWF (N1); 5..ptd Page 17 1 ^^ 200521728

V. Description of the invention (14), the identification domain of the source file and the identification domain of the target file. Each conversion detail record contains the element path (XPath) of the source file, the conversion principle, and the element path of the destination file. The conversion table 11 3 may be recorded in a relational database system, an object database system, a file system, or another system for storing data. Conversion record generation module 1 31 First of all ... winter you, 1 dry i also come to drain

Extensible markup language definition file), a purpose file (ie, the purpose expandable layer markup language definition file), and a conversion rule definition file (that is, it can be extended to display the language conversion file). The conversion record generation module 1 3 1 can parse the source file and the conversion rule definition file, or parse the source file and the destination file to obtain the identification domain of the source file and the identification domain of the destination file. From the destination file or the transformation rule definition file, resolve all the contained destination elements and their destination structure paths. For each destination structure path, parse the conversion rule definition file to get the corresponding source and destination path and conversion principles. The parsed identification domain of the source document, the identification domain of the destination document, and a plurality of conversion principle data including the source structure path, the conversion principle, and the destination structure path are stored in the storage device 1 丨 according to the data structure of the conversion table 113.

According to the embodiment of the present invention, the conversion record generating module 丨 3} firstly input the first XMLschema file, flute-ymt and the first XSLT Duganshi file as shown in the second XML schema file, where the first XML The schema file is the source file, Μ: ^ ^ ^ -XSLT #, Γ # The file is a translation rule definition file corresponding to the XML file of the destination file. Conversion record generation module 131 will automatically parse it out

200521728 V. Description of the invention (15) The identification domain of the source file, the identification domain of the destination file, and the multiple original structure path, conversion principle, and conversion destination path of the destination structure path. Storage device. The “first” is an example of a first conversion table according to an embodiment of the present invention, and the figure a contains the data parsed automatically. Γ γ Figure 2b shows an example of a second-to-one intent according to an embodiment of the present invention, describing all conversion principles for transforming an XML file corresponding to a third XML schema into a table ^ not an XML file corresponding to a second XML schema . The project conversion template query module 1 32 provides a graphical user interface (GUI), which is convenient for users to turn in the identification field of =, the identification field of the destination document, the element path, or other related materials, to storage. The corresponding conversion table 113 is found in the device 11, and the query result is displayed on the display device 14. The conversion template generation module 133 first enters two first conversion tables and a second conversion table with a transltlve relation. The 5 generation-conversion rule definition text # 'This conversion rule defines a file that allows : The structured information of the source document of the first conversion table should be converted to the structured information of the corresponding document of the first: conversion table. The above-mentioned transfer relationship may be =: the identification field of the source file of the conversion table 113 and the identification of the target text ". The conversion template generation module 133 generates a table of the third conversion table US f and stores the source file of the first conversion table , The destination file stores the destination file of the second conversion table. Next, find the pair of conversion details of the structure path of the first conversion M iA and the source structure path of the second conversion table. Source structure path and the first

200521728

5. Description of the invention (16) The purpose structure path of the second conversion table, and the corresponding third conversion table. Corresponding conversion rule definition file According to the embodiment of the present invention, the conversion into the first example drag master generating module 133 shown in Fig. 2a first enters the second example conversion table. After that, find, ^, and the path shown in Figure 2b and the source of the second example conversion table with = = = =; Example conversion table record 322, the first example 艎 # 主 绿 1 corresponds to the first offense -Should manage the record of the example conversion table 3 1 2 corresponding to the record of the first example conversion table 313 and the second table record 323. According to the source of the first conversion table and the destination structure path of the second conversion table ’, a corresponding conversion rule definition file and a corresponding third conversion table are generated. FIG. 3 is a schematic diagram of an exemplary third conversion table according to an embodiment of the present invention, which includes the third XSLT file automatically generated by the above-mentioned automatically parsed data, as shown below, <? Xml version: " 1.0 丨 丨encoding: 丨 丨 UTF-8 丨 丨? 〉 ≪ xsl: stylesheet xmlns: ns =, fhttp: // www. Mysamples. Com / samplel " xmlns: xsl = n http://www.w3.org/ 1 999 / XSL / Transformn > < xs 1 : template match = 丨 丨 " > < root > < ittem > < id > < xs1: va1ue-o f select: 丨 丨 ns: goods / ns: book / ns: ISBNn / >

0213-A40128TWF (Nl); SNOWBALL.ptd Page 20 200521728

V. Description of the invention (17) < / id > < name > < xsl: value_of select: 丨, ns: goods / ns: book / ns: namen / > < / name > < maker > < xsl: value-of select = M ns: goods / ns: book / ns: authorM / > < / maker > < / item > < / root > < / xsl: template > < / xs1: sty 1esheet > Although the embodiment of the present invention uses two examples of conversion and transfer, it is not limited to only two conversion tables that can be processed, and the conversion tables are also available. Text two s files. For example, "Suppose there are three conversion tables and three conversion rules."

Piece D. Conversion template generation module 丨 33-combined conversion to righteousness] The source structure path of the phase c: two =; cattle D as the basis, nine to find the source structure B corresponding to C on Yidan M k 3 仫Finally, find the source structure path corresponding to B of C. FIG. Is a flow chart showing a method for generating a conversion record management method according to an embodiment of the present invention. This method ...

〇213-A40128TWF (Nl); SNOWBALL.ptd Page 21 200521728

It can be loaded and executed by the central processing unit. As shown in step S411, first, a source file, a destination file, and a conversion rule definition file are input. As shown in step 5421, the Coarse source file and the conversion rule definition file are parsed, or the source file and the destination file are parsed to obtain the identification domain of the source file and the destination file. As shown in step S431, a new As shown in the objective element step S432, the source structure path of the conversion rule path and whether there are unresolved objectives S 4 31 in the transition break are analyzed, and the analysis proceeds to the next objective S441. As shown in step S441, the identification field of the destination file, and multiple and destination data paths are stored in the file of the storage device i j or the conversion rule defines the document element and its destination structure path. For example, you can get the corresponding structure of the target file. If the structural path judged as in step S433 is yes, then return to the step structural path, otherwise proceed to step, the identification field of the extracted source document, the pen contains the source structural path, and the conversion principle data is based on the conversion table.

Fig. 5 shows the method for generating a conversion template for document management according to the present invention. The conversion code is composed of code and can be planted by the central processor: Fig. This method consists of 3

As shown in step S511, first enter and = 2. (transitive relation) the first two, the transition relationship between the transfer can be determined from the two conversion tables 113 = and the second conversion table, the identification field of the destination file. For example, step = the identification field of the file and the header of the conversion table…, the field of the source file = shows ”to generate the third and fourth sub-first conversion table.

200521728 V. Description of the invention (19) The file of the purpose file field stores the purpose file of the second conversion table. As shown in step S521, find the pair of detailed conversion records of the destination structure path of the first conversion table and the source structure path of the second conversion table. As shown in step S522, according to the source structure path of the first conversion table and the destination structure path of the second conversion table, a conversion detail record of the third conversion table is generated. Next, a judgment is performed as shown in step S523, and whether there is a pair-wise conversion detail record of the bean, and if so, it returns to step S5. ^ = Such as: "show" to generate a definition file corresponding to the third rotation = conversion Ding =. ^ The invention proposes a computer-readable storage medium for storing an electric moonlight program, and the above computer program is used to realize the conversion of structured information into a file management! Of: 6 change maps # Record / generation method 'This method will be executed Steps as described above. ,. " --- Figure. This storage medium 6. The conversion record management program used to store the structured information in the conversion file management program contains five logics, each of which is a receiving method. Its electric intestine's identification domain logic 622, analysis of the conversion principle of the destination element path: j and the destination element's path of the elementary logic are stored logically-computer program brain nm ::: storage media, used to store the conversion template generation method of file management, This method two: 0213-A40128TWF (N1); ^ -Ptd page 23 200521728

step. Figure 7 is a table of the conversion of structured information according to an embodiment of the present invention. ： 2 :: == Computer readable storage method of version generation method: Schematic diagram This wrong storage medium 70 is used to store the conversion template for structured information conversion file management. Take: The current program contains five logics, which are to receive the second conversion table and the second conversion table logic 721 with the conversion transfer relationship, generate the third conversion table header logic 722, and obtain the destination structure path of the -th conversion table and Paired conversion detail record logic with the same source path for the second conversion table 7 2 3. Generate the conversion detail record logic 724 for the third ^ and generate the conversion rule definition; logic: Therefore, by using the system and method provided by the present invention , Effectively share the burden of authoring or generating new conversion rule definition files. The structured information conversion file is completed. The conversion rule definition file is used to alleviate the developer ’s burden. Although the embodiment of the present invention is disclosed as above, it is not intended to limit the invention. Anyone who is familiar with this technology will not Without departing from the spirit of the present invention, some modifications and retouching can be done. Therefore, the protection of the present invention is subject to the scope of the appended patent application. Gudang

200521728 Brief description of the drawings In order to make the above-mentioned objects, features, and advantages of the present invention more comprehensible, the following specific examples are given in conjunction with the accompanying drawings to explain in detail as follows: Figure 1 shows the implementation according to the present invention Figure 2a is a schematic diagram of a structured message conversion file management system; Figure 2a is a schematic diagram of an exemplary first conversion table according to an embodiment of the present invention; Figure 2b is a schematic diagram of an exemplary second conversion table according to an embodiment of the present invention Figure 3 is a schematic diagram showing an exemplary third conversion table according to an embodiment of the present invention; Figure 4 is a flowchart showing a method for generating a conversion record official conversion document structured information according to an embodiment of the present invention; ^ FIG. 5 is a flowchart of a method for generating a conversion template of a structured message conversion document according to an embodiment of the present invention; FIG. 6 is a diagram of a conversion process of a structured message conversion document according to an embodiment of the present invention; Schematic diagram of computer-readable storage medium for record generation method; Figure 7 shows structured information J pieces according to the embodiment of the present invention The computer can read and store the managed conversion template generation method. Media show, figure. Explanation of symbols 1 0 ~ Structured information conversion file management system; 1 Bu storage device; 12 ~ Central processing unit;

200521728 Simple description of the style 1 3 ~ memory; 1 4 ~ display device; 15 ~ input device; 16 ~ communication device; 17 ~ bus; 1 3 1 ~ conversion record generation module 1 3 2 ~ conversion sample Version query module 133 ~ Conversion template generation module 3 11, 3 1 2, 3 1 3, 3 1 4 ~ Conversion detail record; 321, 322, 323 ~ Conversion detail record /, 1 'S411, S421 ... ..S441 ~ operation steps; S5U, S521 ..... S53 operation steps; '6 2 0 ~ structured message conversion text & technology " computer program; conversion file official conversion logic generation method logic 6 2 1Receive source file, destination file, and conversion rule definition file 6 2 2 ~ Analyze source file and fi? 3 ~ 纮 iff acknowledgement 丨 mountain-master, file identification domain logic '623 analysis destination element path logic 6 2 4 ～ Resolve the corresponding destination element, 625 ～ Generate the conversion table logic; Beijing Path's conversion principle logic; the first conversion table and the second conversion of the conversion pattern generation method of the file management 7 2 0 ～ the conversion message of the structured message computer Program; 7 2 1 ~ Receive with conversion and transfer table logic

200521728 Schematic description 722 ~ Generate the third conversion table header logic; 72 3 ~ Get the pairing conversion detail record logic with the same destination structure path as the first conversion table and the source path of the second conversion table; 724 ~ Generate the third The conversion details of the conversion table record logic; 725 ~ Generate conversion rule definition file logic.

0213-A40128TWF (Nl); SNOWBALL.ptd Page 27

Claims (1)

200521728 VI. Scope of patent application1. A structured information conversion file management system, including a storage device for storing a first definition file, a file, and a conversion file. The above definition file is described by an element The hierarchy between the format and the elements contains the content of the message. The conversion file includes the conversion rules for the structured information corresponding to the first definition and the structured information corresponding to the second definition file. The conversion record generating module receives the above-mentioned first and second definition files and the above-mentioned conversion files, and the above-mentioned definition files and the conversion files are parsed to find out whether they correspond to μ, +, dream—or the above and corresponding to the above-mentioned: definition = -source Identification of the second definition file or the solution of the above conversion = The first conversion file from the above conversion analysis, corresponding to the sergeant ^ 仏, contains the above source structure path 'the above conversion record generation module production path, the above source ί :: The above-mentioned purpose identification code, the above purpose ends, and stores the above-mentioned transformation principle In the table, please refer to the interface of the Λ structured message as described above, m to enter: the description of the source :: 珣 module 'to provide the name of the graphical operation element, to the above materials to find a 1-purpose identification code or — Code, the above-mentioned purpose identification code or the above element ::: =, the source identification shall be the above-mentioned source identification code and the above-mentioned conversion table, and the relative conversion table is displayed on the display device or the above-mentioned element name on the display device 200521728 6 3. Patent application scope 3. The conversion of structured information as described in item 1 of the patent application scope = management system, where the above-mentioned extensible markup language definition file is an extensible markup language schema (XML schema) file or file type definition ( Document type Definition; DTD) file. 4. The structured message conversion file management system as described in item 丨 of the patent application scope, wherein the conversion file is an extensible style sheet language conversion (XSLT) file. 5, · A structured message conversion file management system, including: a storage, a device for storing a first conversion table and a second conversion table, wherein each of the above conversion tables includes a source identification code, a purpose An identification code, and a plurality of conversion rule records including a destination structure path, a source structure path, and a conversion principle, the identification code corresponds to a definition file 'the structure path corresponds to an element in the definition file; and The conversion of the sample product and the destination structure path of the first source identification and the third conversion mentioned above and the pair of a first conversion specification conversion table with the above-mentioned other codes should correspond to one of the above conversion tables. Converting the third conversion application patent student chess group to receive the above-mentioned second conversion table with a conversion transfer relationship, and generating a conversion table header including the first conversion table code and the above-mentioned purpose identification table in the second conversion table, Search the first conversion table for a detailed record with the same source structure path as the first conversion table and a second conversion detail record To generate the above-mentioned third transfer detail record of a source detail path of the conversion detail record and a destination structure path of the detail detail record. Translation of structured messages as described in Scope Item 5 200521728 6. Application scope Patent management system, in which the conversion template generation module generates a conversion file based on the third conversion table and the third conversion detail record. 7. The structured message conversion file management system as described in item 5 of the scope of patent application, wherein the above definition file is an extensible markup language schema (XML schema) file or a document type definition (DTD) file. 8 · The structured message conversion file management system described in item 6 of the scope of patent application, wherein the conversion file is an extensible style sheet language conversion (XSLT) file. '9. A structured message conversion file management method is executed by an electronic device with a central processing unit. The method includes the following steps: A first definition file and a piece are received, wherein the definition file defines a rule that includes a rule corresponding to the first definition to correspond to the second definition file through a hierarchical inclusion relationship between pixels; a second definition file and a Conversion of textual element format and meta-structured message content, the conversion of the structured information of the conversion document, the conversion of the structured information, the identification code of one of the first definition files, is defined by the second definition File or structure path; ^ in the conversion file, parse out a project from the above conversion file, explain the conversion principle of the mountain i and a source :: the structural path y ,,, and ° corresponding to the above purpose; and 20052Π28 Generate a package of the above-mentioned source identification code, the above-mentioned project, the structure path of the patent application scope, the above-mentioned source structure path, and the above-mentioned: drag :, the above-mentioned project exchange table, and store the above-mentioned conversion table in the above-mentioned storage medium ^ conversion principle-conversion 10. The method of item management as described in item 9 of the scope of patent application, further comprising the following steps: structure the conversion text into the above-mentioned source identification code, the above-mentioned purpose identification code or Yuanxin name avoidance. To the above storage device Search for the above conversion table corresponding to the above-mentioned source identification code, ', from the identification code or the above element name; and ·' ,,; L to display the above conversion table corresponding to the above-mentioned source identification code, the above-mentioned destination identification code or name% Display device. Element 1 1 · The structure described in item 9 of the scope of patent application: management method, | The above definition file is an extensible mark: XML schema file or file type definition (D0Cument t ^ Definition; DTD )file. YPe > 12. According to the structured information described in item 9 of the scope of the patent application (m ::: ', the above conversion file is an extensible style sheet language conversion 1 3-a method for managing the conversion file of structured information, It is executed by an electronic device with a central processing unit. The method includes the following steps: · receiving the first conversion table and the conversion table with a conversion transfer relationship, wherein each of the conversion tables includes a source identification code and an item ^ The identification code and the plural include a destination structure path, a source #structural path, and a conversion rule record of a conversion principle. The above-mentioned identification code is relative to a definition file, and the above-mentioned structure path corresponds to a element in the above-mentioned definition file. 200521728 VI. The scope of the patent application generates a header that includes the above-mentioned header in the first to second conversion table; the source identification code in the conversion table and one of the identification codes in the third conversion table. —The source table of the conversion table has the same source structure and path. Chu Si = = the first conversion and the second conversion detail record; and, the recorded U, and the one / one generates a record containing the corresponding first conversion detail record. Path = and corresponding to the above-mentioned item No .: Conversion detail record, one of the third conversion list, third conversion detail record. Above the road 转换 The conversion of structured information described in item 13 of Erguang patent scope _ I _ / further includes a step of generating a conversion file according to the third conversion table and the second conversion detail record. \ 5 · The method for managing the conversion file of structured information as described in item 13 of the scope of the patent application, wherein the above definition file is an extensible markup language schema (XML schema) file or a file type definition (Documen1: type Def ini tion; DTD) file. 16 · The structured information conversion document management method described in item i 4 of the scope of patent application, wherein the conversion file is an extensible style sheet language conversion (XSLT) file. 1 7 · — A computer-readable storage medium for storing a computer program 'The computer program is used to load into a computer system and cause the computer system to execute any one of the items 9 to 12 of the scope of patent applications The method described. 1 8 · — a computer-readable storage medium for storing a computer program 0213-A40128TWF (Nl); SN0WBAa.ptd Page 32 200521728 0213-A40128TWF (N1); SNOWBALL.ptd Page 33