CN115204114A

CN115204114A - XML description document standardization method and device based on ontology model

Info

Publication number: CN115204114A
Application number: CN202210749318.4A
Authority: CN
Inventors: 包佳
Original assignee: Individual
Current assignee: Individual
Priority date: 2022-06-29
Filing date: 2022-06-29
Publication date: 2022-10-18

Abstract

The invention provides a method and a device for standardizing an XML description document based on an ontology model, which comprises the following steps: the ontology model generating module generates a corresponding standard ontology model according to an XSD document with specified standards, and provides standard node names and structures of the XML description document; the XML description document analysis method module analyzes the node information of the transmitted XML description document to acquire semantic information; the node matching and converting module analyzes the similarity between the XML description document node and the ontology model concept according to the semantic information of the XML description document, matches the corresponding node and concept according to the value of the similarity, and standardizes the node which does not meet the standard after matching is finished; and the verification module verifies the nodes of the converted XML description document, adds node information which is not contained in the standard ontology model into the ontology model as a supplementary concept, and completes the standard ontology model. The invention can convert the XML description document which does not conform to the standard into the standard document.

Description

XML description document standardization method and device based on ontology model

Technical Field

The invention relates to the field of industrial information, in particular to an XML description document standardization method and device based on an ontology model.

Background

With the development of social informatization and the change of industrialization, the scale and the application requirements of software are continuously enlarged, and the nonstandard XML description document of a heterogeneous platform cannot meet the huge requirements of people on information interaction and software reuse. In order to realize the standardization of the XML description document, a standard XML Schema document describing the program specification can be specified, and the semantic information interaction between heterogeneous platforms can be realized more efficiently and conveniently by taking the standard XML document as a platform-independent middleware.

However, in a plurality of platforms for writing and running the program, the XML description document of the program is actually written according to the specification of the platform, and a plurality of different description modes for the same program control are possible. For a program, information interaction and code reuse between different platforms need to be converted from one standard to another, and the actual conversion process is equivalent to converting a non-standard XML description document into an XML document conforming to the standard of the current platform.

Therefore, how to standardize the XML description document becomes a problem worthy of exploration.

The existing standardization method of the XML description document does not form a general technical specification, and the mainstream method is that a professional person written by a program manually converts the XML document in a heterogeneous platform into a format which accords with the standard in the whole process. The main drawbacks of this solution are as follows: the conversion efficiency is low; the skilled person needs to be familiar with the code specification and standardized document specification of the current platform; the human resource consumption is large, and the conversion is almost completely performed manually by technicians; the error correction difficulty is high, once an error occurs, manual troubleshooting is needed, the next error is difficult to avoid, and the correction cost is high.

In summary, how to design an XML description document standardization method based on an ontology model so as to convert a non-standard XML description document of a heterogeneous software platform into an XML description document conforming to a specified standard is a technical problem to be solved in the field.

Disclosure of Invention

In order to solve the technical problems in the prior art, the invention provides an XML description document standardization method and device based on an ontology model, wherein a corresponding standard ontology model is generated by giving a standard XSD document, so that semantic information of the standard document is stored to the maximum extent; similarity calculation and matching are carried out on the non-standard XML description document and the standard ontology model, so that the non-standard nodes are mapped to the ontology model concept with the same semantic information, and the standardization process of the non-standard nodes is efficiently and accurately realized.

In order to overcome the defects in the prior art, the technical scheme of the invention is as follows:

an XML description document standardization method based on an ontology model at least comprises the following steps:

step S1: generating a corresponding standard ontology model according to an XSD document with specified standards so as to provide standard node names and structures of the XML description document;

step S2: acquiring a nonstandard XML description document, and analyzing semantic information of the XML description document;

and step S3: according to semantic information of the XML description document, the similarity between nodes of the XML description document and the ontology model concept is analyzed, corresponding nodes and the concept are matched according to the value of the similarity, and after the matching is completed, nodes which do not meet the standard are subjected to standardization processing to generate the standard XML description document.

As a further improvement, the method further comprises the following steps:

and step S4: and checking the nodes of the converted XML description document, and adding node information which is not contained in the standard ontology model into the ontology model as a supplementary concept so as to perfect the standard ontology model.

As a further improvement, step S1 includes the following steps:

s101: importing an XSD document with specified standards, analyzing the standard document, and analyzing the node element names and node structures in the XSD document;

s102: converting the acquired node information to generate a standard ontology model according to a conversion rule from XSD to OWL;

s103: and checking whether the generated ontology model conforms to the universal rule of OWL.

As a further improvement, step S2 includes:

acquiring a non-standard XML description document in the heterogeneous software platform, traversing and analyzing each node in the non-standard XML description document, and analyzing the name, structure and type of the node.

As a further improvement, step S3 includes the following steps:

s301: traversing all concepts in a standard ontology model for each node in a non-standard XML description document, and synthesizing the name similarity, the structure similarity and the type similarity to obtain the similarity between the node and the concepts;

s302: pairing the nodes with the highest similarity with the concepts, wherein the mapping relations between the nodes and the concepts are one-to-one mapping, one-to-many mapping and many-to-one mapping;

s303: converting the node name and the structure of the non-standard document into the name and the structure of the standard ontology model concept according to the obtained mapping relations;

s304: and after the conversion of all mapping relations is completed, obtaining a target standard XML description document.

As a further improvement, the method for obtaining the similarity between the node and the concept by integrating the name similarity, the type similarity and the structure similarity comprises the following steps:

obtaining semantic similarity of names among nodes through WordNet, and then calculating the editing distance similarity of the names among the nodes; weighting and summing the semantic similarity and the edit distance similarity to obtain the name similarity of the nodes;

obtaining the type similarity between the nodes according to the data type matching table;

respectively calculating comprehensive similarity according to the leaf nodes or non-leaf nodes of the node structure;

for leaf nodes, the comprehensive similarity is the weighted sum of the name similarity and the type similarity of the nodes;

for the non-leaf nodes, the comprehensive similarity is the average value of the comprehensive similarities of all the descendant leaf nodes.

As a further improvement, step S4 includes the following steps:

s401: importing a target XML description document, and analyzing the target XML description document into a form of a target node tree;

s402: checking the nodes in the target node tree according to the source non-standard XML description document, adjusting and recording the nodes which do not conform to the semantic information of the source document after conversion;

s403: and checking semantic information which does not exist in the standard ontology model in the unsuccessfully converted node, and if the generic rules of OWL are met, supplementing the semantic information to the standard ontology model to further improve the ontology model.

The invention also discloses an XML description document standardization device based on the ontology model, which comprises an ontology model generation module, an XML description document analysis module, a node matching and conversion module and a verification module, wherein,

the ontology model generating module is used for generating a corresponding standard ontology model according to the specified standard XSD document so as to provide standard node names and structures of the XML description document;

the XML description document analysis module is used for acquiring a nonstandard XML description document and analyzing semantic information of the XML description document;

the node matching and converting module is used for analyzing the similarity between the XML description document node and the ontology model concept according to the semantic information of the XML description document, matching the corresponding node and the concept according to the value of the similarity, and standardizing the node which does not meet the standard after the matching is finished to generate the standard XML description document;

the verification module is used for verifying the nodes of the converted XML description document and adding node information which is not contained in the standard ontology model into the ontology model as a supplementary concept so as to perfect the standard ontology model.

As a further improvement scheme, the ontology model generating module generates a standard ontology model from a specified standard XML Schema file, and each concept in the ontology model corresponds to a node of the standard file.

As a further improvement scheme, the XML description document analysis module is used for uniformly analyzing the document according to the transmitted non-standard XML description document, and transmitting the node information of the document to the node matching and converting module after the analysis is finished.

In the above technical solution, the obtaining of the similarity between the node and the concept by synthesizing the name similarity, the type similarity, and the structure similarity includes:

firstly, semantic similarity of names among nodes is obtained through WordNet, and then the editing distance similarity of the names among the nodes is calculated. And weighting and summing the semantic similarity and the editing distance similarity to obtain the name similarity of the nodes. And secondly, obtaining the type similarity between the nodes according to the data type matching table. And then, respectively calculating the comprehensive similarity according to the leaf nodes or the non-leaf nodes of the node structure. For leaf nodes, the comprehensive similarity is the weighted sum of the name similarity and the type similarity of the nodes; for non-leaf nodes, the integrated similarity is the average of the integrated similarities of all descendant leaf nodes.

Compared with the prior art, the invention has the following technical effects:

1. and generating a corresponding standard ontology model by giving a standard XSD document. According to the format of the target document to be obtained, a standard XSD document can be specified, and a standard ontology model is generated through the conversion rule from XSD to OWL, so that the semantic information of the standard document is stored to the maximum extent.

2. And performing similarity calculation and matching on the non-standard XML description document and the standard ontology model. And comprehensively analyzing semantic information contained in the non-standard XML description document by integrating the name similarity, the type similarity and the structure similarity. And matching the nodes and the concepts according to the comprehensive similarity obtained by weighted summation, so that the nonstandard nodes are mapped to the ontology model concepts with the same semantic information, and the standardization process of the nonstandard nodes is efficiently and accurately realized.

3. And (5) checking the converted node information and perfecting a standard ontology model. And analyzing the converted nodes again by adding a verification module, and adding non-standard XML node information which is not included by the standard ontology model into the current standard ontology model, thereby realizing the self-learning process of the standard ontology model. The continuous improvement of the body model effectively increases the semantic information which can be converted through the body model, thereby realizing more accurate and complete standardization of the non-standard XML document.

Drawings

In order to more clearly and completely illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be described in further detail below.

The drawings in the following description are illustrative of some embodiments of the invention and can be similarly generalized by those skilled in the art without inventive faculty.

FIG. 1 is a flowchart illustrating an XML description document normalization method based on an ontology model according to an embodiment of the present invention.

Fig. 2 is a schematic block diagram of a connection structure between modules according to an embodiment of the present invention.

Fig. 3 is a schematic flow chart of the ontology model generating module according to an embodiment of the present invention.

FIG. 4 is a schematic flow chart of a node matching and converting module according to an embodiment of the present invention;

fig. 5 is a code fragment of customer. Xml, according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of customer.xml according to an embodiment of the present invention;

FIG. 7 is a schematic diagram illustrating a node similarity calculation principle according to an embodiment of the present invention;

FIG. 8 is a flow chart of a verification module according to an embodiment of the invention;

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear and complete, the technical solutions in the embodiments of the present invention will be described below clearly and completely with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

FIG. 1 is a flow chart of a method for standardizing an XML description document based on an ontology model, which comprises the following steps:

s1: the ontology model generating module generates a corresponding standard ontology model according to an XSD document with specified standards, and provides standard node names and structures of the XML description document;

s2: acquiring a nonstandard XML description document, and analyzing semantic information of the XML description document by using an XML description document analysis module;

s3: according to semantic information of the XML description document, the node matching and converting module analyzes the similarity between nodes of the non-standard XML description document and the ontology model concept, matches corresponding nodes and concepts according to the value of the similarity, and standardizes the nodes which do not meet the standard after matching is completed;

s4: the verification module verifies the nodes of the converted XML description document, adds node information which is not contained in the standard ontology model into the ontology model as a supplementary concept, and completes the standard ontology model.

Fig. 2 is a schematic block diagram of a connection structure between modules according to an embodiment of the present invention. Firstly, importing a standard XSD document specified by a target document into an ontology model generating module to generate a standard ontology model. And secondly, acquiring a non-standard XML description document of the heterogeneous platform, and acquiring semantic information of the node through an XML description document analysis module. And then, calculating the similarity of the non-standard XML description document nodes and the concept of the body model through a node matching and converting module, and pairing the nodes with the same semantic information according to the obtained comprehensive similarity, thereby standardizing the non-standard nodes and generating the standard XML description document. And finally, the converted XML description document is checked through a checking module, semantic information which is not contained in the body model is supplemented into the standard body model, and the body model is perfected.

FIG. 3 is a schematic flow chart of an ontology model generating module, comprising the following steps:

s101: and importing an XSD document with specified standard, analyzing the standard document, and analyzing the node element name and the node structure in the XSD document.

S102: and converting the acquired node information according to the XSD-to-OWL conversion rule to generate a standard ontology model.

In step S1, a standard ontology model is generated from an XSD document specifying a standard, and is verified to conform to the universal rules of OWL. OWL is a language suitable for ontology model description, and has three different versions, namely OWL Lite, OWL DL and OWL Full. Compared with OWL Lite and OWL Full, OWL DL has stronger description capability, supports the reasoning of semantic information, and has moderate consumption of calculated amount. Therefore, the ontology model standard in the present invention is described using owldl.

In step S2, a non-standard XML description document of the heterogeneous software platform needs to be obtained. And analyzing the name, structure and type of each node in the non-standard XML description document through traversal analysis. And carrying out next matching and conversion on the nodes of the non-standard document according to the analysis result.

As shown in fig. 4, taking customer.xml as an example, traversal is started from a root node of a non-standard document, and a name of the root node is obtained as the customer, an attribute customerid is "1", and the root node is a complex node. And sequentially accessing the child nodes through depth traversal, wherein the names of the nodes are firstname, lastname and homephone respectively, and the child nodes are simple nodes. Thus, a schematic diagram of the structure of the non-standard XML description document can be obtained, as shown in FIG. 5.

Fig. 6 is a schematic flow chart of the node matching and converting module, which includes the following steps:

s301: for each node in the non-standard XML description document, traversing all concepts in the standard ontology model, and synthesizing the name similarity, the structure similarity and the type similarity to obtain the similarity between the node and the concepts. The principle of node similarity calculation is shown in fig. 7.

S302: and pairing the nodes with the highest similarity with the concepts, wherein the mapping relations between the nodes and the concepts are one-to-one mapping, one-to-many mapping and many-to-one mapping.

S303: and converting the node name and the structure of the non-standard document into the name and the structure of the standard ontology model concept according to the obtained mapping relations.

S304: and after the conversion of all mapping relations is completed, obtaining a target XML description document.

Fig. 7 is a schematic diagram illustrating a principle of calculating node similarity according to an embodiment of the present invention. For the mapping relationship between the node and the concept, the name of the node contains main semantic information, so the similarity of the name is considered firstly. In an XML description document, nodes are divided into an atomic type and a complex type. In the atom type, different similarity values need to be given to the node types according to four conditions that two node types are consistent, two node types are inconsistent but can be converted, and two node types are inconsistent and can not be converted.

For the source node tree corresponding to the source XML description document, the leaf node only contains the node information of the leaf node, and the non-leaf node contains the node information of all the descendant nodes. Therefore, a final comprehensive similarity result needs to be obtained according to the structural information of the nodes during matching.

The specific steps of calculating the comprehensive similarity between the nodes and the concepts comprise:

And obtaining a mapping matching relation library according to the calculated comprehensive similarity of the nodes and the concepts. In the relational database, the nodes and concepts labeled as the optimal mapping relationship are the matching objects. And the node matching and converting module correspondingly converts the names and the structures of the nodes of the non-standard XML description document.

XML describes the name and structure conversion of document node based on the node tree generated by the schema diagram, and the process can be realized by setting a group of node conversion operations. The set of node transformation operations includes copy, insert, delete, rename, split, merge, change types. The conversion of the source XML description document node into a standard node can be realized by a series of operations in the operation set.

Fig. 8 is a schematic flowchart of a verification module according to an embodiment of the invention. Because the standard ontology model is completely obtained from the specified standard XSD document, the semantic information specifications of various heterogeneous software platforms cannot be completely included, and the situation that no corresponding standard node exists may occur in the conversion process from the non-standard document to the standard document. Aiming at the situation, the invention adds a check module to adjust all nodes which can not be converted accurately, saves the semantic information which is not converted successfully, adds the semantic information into the standard ontology model in the form of a supplementary item, and further improves the ontology model. The specific flow of the checking module comprises the following steps:

s401: and importing a target XML description document, and analyzing the target XML description document into a target node tree form.

S402: and checking the nodes in the target node tree according to the source non-standard XML description document, adjusting and recording the nodes which do not conform to the semantic information of the source document after conversion.

S403: and checking semantic information which does not exist in the standard ontology model in the unsuccessfully converted node, if the semantic information accords with the universal rule of OWL, supplementing the semantic information to the standard ontology model, and further improving the ontology model.

The above description of the embodiments is only intended to facilitate the understanding of the method of the invention and its core ideas. It should be noted that a person skilled in the art could make several modifications and adaptations to the present invention without departing from the principle of the present invention, and such modifications and adaptations are also within the scope of the present invention as set forth in the following claims.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments may be made by those skilled in the art, and may be made in other embodiments without departing from the scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An XML description document standardization method based on an ontology model is characterized by at least comprising the following steps:

2. The method for standardizing an XML description document based on an ontology model as recited in claim 1, further comprising:

and step S4: and checking the nodes of the converted XML description document, and adding node information which is not contained in the standard ontology model into the ontology model as a complementary concept so as to perfect the standard ontology model.

3. The method for standardizing an XML description document based on an ontology model according to claim 2, wherein the step S1 comprises the steps of:

s102: converting the acquired node information to generate a standard ontology model according to the XSD-to-OWL conversion rule;

4. The method for standardizing an XML description document based on an ontology model according to claim 2, wherein the step S2 comprises:

5. The method for standardizing an XML description document based on an ontology model according to claim 2, wherein the step S3 comprises the steps of:

6. The method of claim 5, wherein the step of obtaining the similarity between the node and the concept by combining the name similarity, the type similarity and the structure similarity comprises:

for non-leaf nodes, the integrated similarity is the average of the integrated similarities of all descendant leaf nodes.

7. The method for standardizing an XML description document based on an ontology model according to claim 2, wherein the step S4 comprises the steps of:

8. An XML description document standardization device based on an ontology model is characterized in that: comprises a body model generating module, an XML description document analyzing module, a node matching and converting module and a checking module, wherein,

9. The apparatus for standardizing XML description document based on ontology model according to claim 8, wherein: the ontology model generating module generates a standard ontology model from a specified standard XML Schema file, wherein each concept in the ontology model corresponds to a node of the standard file.

10. The apparatus for standardizing XML description document based on ontology model according to claim 8, wherein: and the XML description document analysis module is used for uniformly analyzing the document according to the transmitted non-standard XML description document and transmitting the node information of the document to the node matching and converting module after the analysis is finished.