JP2007122278A - Document processing device and method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that an XML parser which is only capable of analyzing canonical XML cannot ensure equipment compatibility. <P>SOLUTION: A document processing device has a canonical DOM parser part 502 for analyzing canonical XML documents, a canonicalization part 504 for converting noncanonical XML documents into canonical XML documents and supplying them to the canonical DOM parser part 502, and a grammar violation information recognition part 503 for identifying whether or not input documents are at least canonical XML documents. XML documents identified as noncanonical XML documents are converted into canonical XML documents by the canonicalization part 504 and analyzed by the canonical DOM parser part 502. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a document processing apparatus, method, and program for processing the document structure of a structured document.

  In recent years, XML (Extensible Markup Language / Non-patent Document 1) has been used to ensure data compatibility between devices. Since XML is text-based, it has a feature that it has a high degree of freedom in character encoding and format. On the other hand, since the degree of freedom is higher than that of binary data depending on conventional devices, an XML parser for analyzing information becomes complicated. In order to avoid the complexity of the XML parser, it is necessary to limit the XML format.

As one method for restricting the XML format, it can be considered that data exchanged between devices is described in normalized XML (Canonical XML / Non-patent Document 2). This normalized XML is a specification that limits the format with a high degree of freedom in XML to one format and can express information equivalent to XML, and is originally used for electronic signatures and the like. If all data exchanged between networks can be limited to normalized XML, the analysis capability required for the XML parser can be greatly reduced, and the XML parser can be reduced in weight and speed.
"Extensible Markup Language (XML) 1.0 (Third Edition)", W3C, 2004, http://www.w3.org/TR/REC-XML/ "Canonical XML Version 1.0", W3C, 2001, http://www.w3.org/TR/XML-c14n

  In the case of a local network, connection destination devices are also limited, and thus the above-described restrictions can be applied to all devices. However, given the connection with devices on a wide area network, it is impossible to apply the above restrictions to an unspecified number of devices, and an XML parser that has the ability to analyze only normalized XML can be used between devices. Interoperability cannot be ensured.

  An object of the present invention is to solve the above-mentioned conventional problems.

  A feature of the present invention is to provide a technique for efficiently analyzing a structured document.

In order to achieve the above object, a document processing apparatus according to an aspect of the present invention has the following arrangement. That is,
A document processing device for analyzing an input structured document,
Normalized XML analysis means for analyzing the normalized XML document;
Normalization means for converting an unnormalized XML document into a normalized XML document and supplying the normalized XML document to the normalized XML analysis means;
Identification means for identifying whether the input document is at least a normalized XML document, and an XML document identified by the identification means as not being a normalized XML document is normalized XML document by the normalization means And the analysis is performed by the normalized XML analysis means.

In order to achieve the above object, a document processing method according to an aspect of the present invention includes the following steps. That is,
A document processing method for inputting and analyzing a structured document,
A normalized XML analysis step of analyzing the normalized XML document;
A normalization step of converting a non-normalized XML document into a normalized XML document and supplying it to the normalized XML analysis step;
An identification step for identifying whether or not the input document is at least a normalized XML document, and an XML document identified as not being a normalized XML document in the identification step is converted into a normalized XML document by the normalization step. It converts, and it analyzes by the said normalization XML analysis process, It is characterized by the above-mentioned.

  According to the present invention, a minimum document analysis function and a normalization function for converting a general-purpose description into a minimum grammar rule can be used separately. This makes it possible to efficiently perform analysis processing by adding necessary resources to a denormalized XML document with a minimum amount of resources and time for a normalized XML document.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The following embodiments do not limit the present invention according to the claims, and all combinations of features described in the present embodiments are essential to the solution means of the present invention. Not exclusively.

<Embodiment 1>
In the first embodiment of the present invention, an example in which a normalized XML document, a denormalized XML document, and a non-XML document are analyzed using a DOM parser will be described.

  FIG. 1 is a block diagram illustrating a schematic configuration of the information processing apparatus according to the present embodiment.

  In FIG. 1, reference numeral 101 denotes a central control unit (hereinafter referred to as CPU) that controls the entire information processing apparatus. The ROM 102 stores programs, parameters, and various data that do not need to be changed. The RAM 103 temporarily stores programs and data supplied from an external device or the like. The storage unit 104 is a hard disk or memory card that is fixedly installed in a device, an optical disk such as a removable flexible disk (FD) or Compact Disk (CD), a magnetic or optical card, an IC card, a memory card, or the like. Including an external storage device. An OS and various application programs are installed in the storage unit 104, and these programs are loaded into the RAM 103 at the time of execution and executed under the control of the CPU 101. The operation unit 105 includes an input device such as a pointing device and a keyboard for inputting data in response to a user operation and other hardware keys and a touch panel, and an interface thereof. The display unit 106 includes a monitor for displaying data held by the apparatus and supplied data, and an interface thereof.

  Here, a document to be analyzed is stored in the storage unit 104 in advance. This document storage procedure is out of the scope of the present invention and will not be described. The stored document is read and each process is performed, and the document is stored in the storage unit 104 as necessary after the process.

A program executed by the CPU 101 includes an XML parser that analyzes a normalized XML document and a normalization that converts an input XML document into a normalized XML document in accordance with 14 normalization conversion rules defined in Non-Patent Document 2. Including Among the normalization conversion rules, the following are characteristic.
(1) The line feed character is “#xA” (meaning the Ath character in hexadecimal notation, equivalent to “10” in decimal notation, and so on).
(2) Delete XML declaration, DTD declaration, and comment (3) Replace empty element tag with a set of start and end tags (4) Unify attribute value enclosure symbol to """(1) The normalization unit reads the input XML document in order from the top and searches for symbols (#xA, #xD) used for line feed characters. There are three types of patterns that are used as a single line feed character in a general-purpose XML document: “#xA” only, “#xD” only, and “#xD #xA”. The normalization unit sequentially checks to which pattern the input line feed character applies, replaces all patterns with “#xA”, and outputs the result as a normalization result.

  In order to realize (2), the normalization unit searches for an XML declaration part, a DTD declaration part, and a part corresponding to a comment from the input XML document. However, no normalization result is output.

  In order to realize (3), the normalization unit searches for the symbol “<” indicating the start, end, and head of the empty element tag. Since each tag has a grammar of “<element name attribute attribute ...>”, “</ element name>”, and “<element name attribute attribute ... />”, the normalization unit has a grammar of each. Switch the normalization method while recognizing. First, it is confirmed whether or not the next character is “/”. If it is “/”, information of a normal end tag is output as an end tag. On the other hand, if it is a character that can be used as an element name other than that, the element name is output while taking a copy of the part corresponding to the element name, assuming that it is either a start or an empty element tag. Furthermore, if there is a description of the attribute, it is output as it is without making a copy. When ">" appears at the end, it recognizes that it was a start tag, discards the copied information, and outputs ">" as a normal start tag.

  On the other hand, if “/>” can be confirmed, it is recognized as an empty element tag. If the tag is recognized as an empty element tag, immediately after closing the start tag by outputting “>”, an end tag having the copied element name is output. Then, an end tag for closing the output start tag is added to the normalized XML document. By following such a process, all empty element tags are normalized to a set of start and end tags.

  In order to realize (4), the normalization unit confirms the enclosing symbol of the attribute value of the input XML document. The attribute format is either “attribute name =“ attribute value ”” or “attribute name = 'attribute value'”. If the normalization unit confirms “” after “=”, the format has already been normalized, and the attribute information is output to the end without any processing.

  On the other hand, when the normalization unit confirms "'" after "=", it outputs "" "instead, and confirms that the subsequent characters are not" "" or "'" Sequentially input characters are output as they are. If "" "is input," "" "" that is an entity reference meaning "" "is output, and" "" is not output as an attribute value.

  On the other hand, when “′” is input, it is recognized that the declaration of the attribute value is completed, and ““ ”is output. Then, the process proceeds to the process of searching for the next attribute declaration or tag closing symbol.

  By combining the above processing, the normalization unit can convert the XML document into a normalized XML document.

  Each of FIG. 2 to FIG. 4 is a diagram illustrating an example of a normalized XML document, a non-normalized XML document, and a non-XML document to be analyzed in the present embodiment.

  FIG. 2 is described according to the specification of normalized XML. FIG. 3 shows an example in which a symbol (') that is recognized in XML but not allowed in normalized XML is used as an enclosure symbol for an attribute value. Further, FIG. 4 is also out of the category of XML document because there is no surrounding symbol for attribute values. In these figures, line numbers, line feeds, and white space characters are added as appropriate for explanation.

  FIG. 5 is a block diagram showing a functional configuration of the DOM parser 501 according to the first embodiment. The specific hardware configuration of the DOM parser 501 is the same as that shown in FIG.

  The DOM parser 501 has a normalized DOM parser unit 502 having a function of analyzing a normalized XML document. The normalized DOM parser unit 502 analyzes the normalized XML document and discriminates between the normalized XML document and the non-normalized XML document. The document to be analyzed is acquired from the storage unit 508, and the analysis result is transmitted to the application 509 via the output interface (I / F) unit 507. The storage unit 508 stores a plurality of documents to be analyzed. The stored document is sent to the normalized DOM parser unit 502 via the input I / F unit 506.

  When the normalized DOM parser unit 502 finds a grammatical violation in the analyzed document, it generates grammatical violation information and transmits it to the grammatical violation information confirmation unit 503. Thereby, the grammar violation information confirmation unit 503 determines whether or not the grammar violation information received from the database 505 storing the grammar violation information confirmation table is generated at the time of denormalized XML document analysis. The normalization unit 504 normalizes the document that failed to be analyzed and sends it to the normalized DOM parser unit 502.

FIG. 6 is a flowchart for explaining a processing procedure in the DOM parser 501 according to the first embodiment of the present invention. A processing procedure for analyzing a document to be analyzed (FIGS. 2 to 4) will be described below. A program for executing the processing shown in this flowchart is stored in the RAM 103 at the time of execution, and is executed under the control of the CPU 101.
(A) A case where the normalized XML document shown in FIG. 2 is acquired from the storage unit 508 will be described.

The DOM parser 501 acquires the normalized XML document shown in FIG. 2 via the input I / F unit 506. First, in step S601, the normalized DOM parser unit 502 analyzes the document. In this case, the normalized DOM parser 502 ends the analysis without detecting a grammatical violation until the end, and builds a DOM tree therein. Accordingly, since there is no grammatical violation in step S602, it is determined that the XML document to be analyzed is a normalized XML document. In step S603, the DOM tree built in the normalized DOM parser 502 is used as a final analysis result, and is transmitted to the application 509 via the output I / F unit 507. In step S604, the analysis of the normalized XML document ends normally.
(B) A case where the denormalized XML document shown in FIG. 3 is acquired from the storage unit 508 will be described.

  In this case, in the analysis process by the normalized DOM parser unit 502 in step S601, grammatical violation information for the enclosing symbol of the attribute value described in the second line of FIG. 3 is generated. Accordingly, the analysis is not successful in step S602, and it is determined that the document to be analyzed is a non-normalized XML document or a non-XML document, and the process proceeds to step S605. At this time, the DOM tree constructed halfway in the normalized DOM parser unit 502 is discarded, and the generated grammatical violation information is transmitted to the grammatical violation information confirmation unit 503. Thereby, the grammar violation information confirmation unit 503 determines whether or not the grammar violation information received from the grammar violation information confirmation table 505 shown in FIG. 7 is generated at the time of denormalized XML document analysis.

  FIG. 7 is a diagram showing a specific example of the grammatical violation information correspondence table 505 according to Embodiments 1 and 2 of the present invention.

  Here, “error content” determined as an error as a result of analysis and “error generated because it is a non-XML document” or “error generated because it is a denormalized document” as the cause Is described. Note that FIG. 7 is merely an example of a specific example, and other error items and error causes may be included.

  In the case of the document in FIG. 3, grammatical violation information that the symbol “′” appears after the symbol “=” during attribute analysis is received. This corresponds to the error content indicated by 700 in FIG. As a result, it is determined that there is a possibility that the document to be analyzed is a denormalized XML document. As a result, the process proceeds from step S606 to step S608, and normalization is performed by the normalization unit 504 for the document that failed to be analyzed. In step S609, if no error occurs, the process advances to step S610, and the normalized XML document is supplied again to the normalized DOM parser 502 for analysis. If no grammatical violation is detected in step S611, the process advances to step S612 to determine that the analysis target document is a denormalized XML document, and notify the application 509 of the DOM tree generated as a result of the second analysis. To do. Thus, in step S613, the process for the denormalized XML document is normally terminated.

On the other hand, if a grammatical violation is detected in step S609 or step S611, the document is determined to be a non-XML document, and the process proceeds to step S614. .
(C) A case where the non-XML document shown in FIG. 4 is analyzed will be described.

  When the document shown in FIG. 4 is analyzed, the normalized DOM parser unit 502 generates grammatical violation information indicating that there is a symbol other than ““ ”and“ ′ ”next to the symbol“ = ”during attribute analysis. As a result, in step S606, it is determined that the error content is generated only in the case of a non-XML document, and the process proceeds to step S607. To do.

  As described above, according to the first embodiment, the normalized XML document and the non-normalized XML document are combined with the normalized DOM parser unit 502 corresponding to only the normalized XML document and the normalizing unit 504 as appropriate. A DOM parser 501 that can be analyzed together can be provided. By using this DOM parser, an input document can be analyzed at an optimal cost.

<Embodiment 2>
Next, a second embodiment of the present invention will be described. The hardware configuration of the DOM parser according to the second embodiment is the same as that of the first embodiment shown in FIG.

  In the second embodiment, an example in which a normalized XML document, a non-normalized XML document, and a non-XML document are analyzed using a SAX parser unit will be described. The second embodiment is different from the first embodiment in that the normalized DOM parser unit 502 is changed to a normalized SAX parser unit 802.

  FIG. 8 is a block diagram showing a functional configuration of the DOM parser 801 according to the second embodiment of the present invention. Components common to the configuration of the first embodiment are indicated by the same symbols, and description thereof is omitted. The specific hardware configuration of the DOM parser 801 is the same as that shown in FIG.

  The SAX parser 801 acquires the analysis target document shown in FIGS. 2 to 4 from the storage unit 508, as in the first embodiment. Unlike the DOM parser 501 according to the first embodiment, the SAX parser 801 notifies the application 509 of the analysis results sequentially as the analysis process proceeds.

FIG. 9 is a flowchart for explaining a processing procedure in the DOM parser 801 according to the second embodiment of the present invention. A processing procedure for analyzing a document to be analyzed (FIGS. 2 to 4) will be described below. A program for executing the processing shown in this flowchart is stored in the RAM 103 at the time of execution, and is executed under the control of the CPU 101.
(A) A case where the normalized XML document shown in FIG. 2 is analyzed will be described.

In this case, since the grammatical violation is not resolved by the normalized SAX parser 802, the analysis is performed in steps S901 to S904 as in the first embodiment. When the analysis is completed, the process proceeds from step S904 to step S905, and the normalization is performed. The XML document analysis process ends normally.
(B) A case where the non-normalized XML document shown in FIG. 3 is analyzed will be described.

As in the first embodiment, when a grammatical violation is detected in step S902, grammatical violation information is generated and the process proceeds to step S906. In step S906, unlike the first embodiment, the application 509 is notified of the analysis results up to that point. Thereby, before moving to the processing (S906 to 907) of the grammatical violation information confirmation unit 503, it is possible to notify the application 509 of information for invalidating the analysis result so far. Subsequent steps S907 to S915 are the same as steps S605 to S614 in the first embodiment. However, in the second embodiment, after the XML document is normalized by the normalization unit 504 in step S910, the error determination process in step S609 is omitted, and in step S911, the normalization SAX parser 802 performs the normalization. Analyzing the generated XML document. When the analysis is successful and the analysis ends in step S914, the analysis processing of the normalized XML document is normally ended in step S915. If an analysis error occurs, the process ends abnormally in step S909.
(C) A case where the non-XML document shown in FIG. 4 is analyzed will be described.

  In this case, an error occurs in step S902, and the process advances to step S906 to notify the application 509 of the analysis result so far, unlike the first embodiment. Thereby, before moving to the processing (S906 to 907) of the grammatical violation information confirmation unit 503, it is possible to notify the application 509 of information for invalidating the analysis result so far. In step S908, since the error does not occur in the denormalized document, the process proceeds to step S909, and the abnormal termination process for the non-XML document is performed.

  As described above, according to the second embodiment, the SAX parser 801 also combines the normalized SAX parser unit 802 and the normalization unit 504 corresponding only to the normalized XML document, and performs analysis processing at an optimal cost. It can be performed.

<Embodiment 3>
Next, a third embodiment of the present invention will be described. In the third embodiment, an example in which a normalized XML document, a denormalized XML document, and a non-XML document are analyzed using the parser according to the third embodiment will be described. In the third embodiment, unlike the first and second embodiments, the normalization unit 504 first analyzes the analysis target document (FIGS. 2 to 4). The normalized parser unit 1002 may use either the normalized DOM parser unit 502 or the normalized SAX parser unit 802, or may use another parser having a function of analyzing a normalized XML document. Good.

  FIG. 10 is a block diagram for explaining the configuration of the parser 1001 according to the third embodiment of the present invention, in which parts common to the configuration of the above-described embodiment (FIG. 5) are indicated by the same symbols. The specific hardware configuration of the parser 1001 is the same as that shown in FIG.

  In FIG. 10, the input document is first input to the normalization unit 504 and normalized, and then sent to the normalization parser unit 1002 at the subsequent stage.

  FIG. 11 is a flowchart illustrating a processing procedure in parser 1001 according to Embodiment 3 of the present invention. A processing procedure for analyzing a document to be analyzed (FIGS. 2 to 4) will be described below. A program for executing the processing shown in this flowchart is stored in the RAM 103 at the time of execution, and is executed under the control of the CPU 101.

First, in step S1101, the analysis target document acquired from the storage unit 508 is first normalized by the normalization unit 504.
(A) A case where the normalized XML document shown in FIG. 2 is analyzed will be described.

  In this case, since no grammatical violation is detected when normalization is performed, an error does not occur in step S1102, and the normalization unit 504 determines that the analysis target sentence is a normalized XML document and proceeds to step S1103. In step S1103, the normalized XML document is analyzed by the normalized parser 1002. If the analysis is successful in step S1104, the process advances to step S1105 to notify the application 509 of the result of the analysis processing.

If the application 509 requires a determination result as to whether or not it is normalized XML, in step S1106, the normalization unit 504 uses information regarding the presence / absence of character replacement before and after the normalization process, and determines the determination result. I can tell you. That is, if character replacement is performed in step S1106, the process proceeds to step S1107, and the process ends normally as a denormalized XML document. If no character replacement is performed in step S1106, the process proceeds to step S1108, where the process ends normally as a normalized XML document.
(B) A case where the non-normalized XML document shown in FIG. 3 is analyzed will be described.

Also in this case, the normalization processing is executed in the normalization unit 504 as in the case of FIG. In steps S1102 to S1106, processing is performed in the same manner as the normalized XML document shown in FIG. 2 based on the normalization result. In this way, the analysis result can be transmitted to the application 509.
(C) A case where the non-XML document shown in FIG. 4 is analyzed will be described.

  If the normalization unit 504 or the normalization XML parser unit 1002 detects a grammatical violation (S1102, S1104), the process proceeds to step S1109 to notify the application 509 of the fact and abnormally terminates as a non-XML document.

  As described above, according to the third embodiment, the analysis using the normalized parser 1002 can be efficiently performed even in an environment in which many unnormalized XML documents are analyzed.

<Embodiment 4>
In the fourth and fifth embodiments, an example of a node that includes the parser according to the present embodiment and exchanges XML documents via a network will be described. First, the fourth embodiment will be described in the case where a normalization function is provided on the node side.

  FIG. 12 is a diagram for explaining a network to which nodes having parsers according to Embodiment 4 of the present invention are connected.

  Each of the normalized XML corresponding nodes 1213 to 1215 and 1223 to 1224 includes the parser according to the fourth embodiment. Also, these nodes always output a normalized XML document when sending an XML document to other nodes. On the other hand, the general-purpose XML compatible nodes 1331 to 1234 have a general parser, and output a general-purpose XML document to other nodes. In addition, the parser possessed by the general-purpose XML compatible nodes 1331 to 1234 has a function of analyzing an unnormalized XML document.

  These nodes are connected to the respective LANs 1211, 1221, and 1231, and are connected to a common WAN 1201 through gateways 1212, 1222, and 1232, respectively. All nodes have unique identifiers on the networks 1201, 1211, 1221, and 1231, respectively. All nodes secure communication paths for exchanging data with each other via the LANs 1211, 1221, 1231, gateways 1212, 1222, 1232, and WAN 1201.

  FIG. 13 is a block diagram showing a configuration of a normalized XML compatible node 1213 according to the fourth embodiment. Since the hardware configuration of this node is the same as the configuration of the first embodiment, the description thereof is omitted.

  This normalized XML compatible node 1213 has a parser unit 1301, an input I / F unit 1302 for receiving an XML document via the LAN, and whether or not the input XML document is a normalized XML document. And a normalization determination unit 1303. Other components are the same as those in the above-described embodiment. Also, the other normalized XML compatible nodes 1214 to 1215 and 1223 to 1224 have the same configuration.

  The normalization determination unit 1303 acquires a correspondence table of the normalized XML compatible node on the network and the network address of the corresponding node in advance. Information indicating a plurality of nodes such as a domain, a subnet address, and a gateway address can be used as a network address. In the fourth embodiment, it is assumed that a normalized XML compatible node is designated for each LAN using this subnet address.

  If the normalization determination unit 1303 is an XML document from a normalized XML compatible node, the normalization determination unit 1303 sends the document to the normalization parser unit 1002 and outputs the document to the application 509 via the output interface unit 507. On the other hand, if it is not an XML document from the normalized XML compatible node, the received XML document is sent to the normalization unit 504 to normalize, and the result is sent to the normalization parser unit 1002, and the application is sent via the output interface unit 507. Output to 509.

  In FIG. 12, the LAN 1211 and the LAN 1221 are composed of normalized XML compatible nodes, and the normalized XML compatible nodes can be designated by using the subnet address corresponding to each LAN.

  FIG. 14 is a flowchart illustrating a processing procedure in parser unit 1301 according to the fourth embodiment. Hereinafter, a processing procedure for analyzing an XML document received from another node will be described. A program for executing the processing shown in this flowchart is stored in the RAM 103 at the time of execution, and is executed under the control of the CPU 101.

  When the normalized XML compatible node 1213 receives the XML document via the network, first, in step S1401, the normalization determination unit 1303 is used to confirm the address of the source node of the XML document. In step S1402, if the source address is included in the subnet corresponding to the normalized XML node, it is determined that the received XML document is a normalized XML document, and the process advances to step S1406. In step S1406, the XML document is output to the normalization parser unit 1002 and analyzed. In step S1407, it is determined whether the analysis is successful. If successful, the process advances to step S1408, and the result analyzed by the normalization parser unit 1002 is notified to the application. In step S1409, the process ends normally. On the other hand, if it is determined in step S1407 that the analysis is not successful, the process proceeds to step S1405 and ends abnormally.

  In the fourth embodiment, the nodes 1214 to 1215 and 1223 to 1224 connected to the LAN 1211 and the LAN 1221 are determined as normalized XML compatible nodes from the subnet address information. Accordingly, the XML documents received from these nodes are all determined as normalized XML documents, and are analyzed by the normalization parser unit 1002 without performing normalization processing.

  On the other hand, if the source address is other than the subnet address to which the normalized XML node belongs, it is determined in step S1402 that the document is an XML document transmitted from the general-purpose XML compatible node. In this case, the process proceeds to step S1403, and the document is sent to the normalization unit 504 to perform normalization processing. If no error occurs, the process proceeds to step S1406, where the normalization parser unit 1002 analyzes and notifies the application of the result (S1406 to 1408). If an error occurs, the process ends abnormally in step S1405.

  As described above, according to the fourth embodiment, it is possible to provide a parser that performs normalization only when necessary and uses only a fast and lightweight normalized XML portion for a normalized XML document. . By using this parser, analysis processing can be performed at an optimal cost for each received data.

  Even when the normalization determination unit 1303 does not have correspondence information between the addresses on the network and the normalized and non-normalized networks, the parsers described in the above first to third embodiments are included in the normalized XML compatible node. The parser unit 1301 is used. Then, the XML document can be exchanged efficiently with the normalization / general-purpose XML compatible node.

<Embodiment 5>
The fifth embodiment shows an example in which a normalization function is provided on the gateway side, and a set of general-purpose parsers is configured with the gateway and the node. Unlike the above-described fourth embodiment, the normalization XML compatible node does not include the normalization determination unit 1303 and the normalization unit 504, and the normalization determination is performed on the gateway 1212 and 1222 side that manages the LAN to which the normalization XML compatible node belongs. Unit 1303 and normalization unit 504.

  FIG. 15 is a block diagram showing the configuration of the gateway 1501 according to the fifth embodiment of the present invention. The parts common to those in FIG.

  The WAN interface unit 1502 is an interface unit that connects the WAN 1201 and the gateway 1501. The normalization determination unit 1303 determines whether the document input from the WAN interface unit 1502 is a normalized XML document. If the document is a normalized XML document, the normalization determination unit 1303 outputs the document to the LAN 1211 via the LAN interface unit 1503. On the other hand, if it is not a normalized XML document, the received XML document is sent to the normalization unit 504 for normalization, and the result is output to the LAN 1211 via the LAN interface unit 1503.

  FIG. 16 is a block diagram illustrating the configuration of the node 1601 according to the fifth embodiment. Portions that are the same as those in FIGS.

  A gateway 1501 shown in FIG. 15 includes a normalization determination unit 1303 inside, and determines normalized and non-normalized XML documents by the same method as in the fourth embodiment. The normalizing unit 504 performs the same processing as that of the normalizing unit of the fourth embodiment.

  A normalized XML corresponding node 1601 shown in FIG. 16 includes a normalized parser unit 1002 inside, and this also performs the same processing as in the fourth embodiment.

  FIG. 17 is a flowchart showing a processing procedure of the gateway 1501 according to the fifth embodiment of the present invention. A program for executing the processing shown in this flowchart is stored in the RAM 103 at the time of execution, and is executed under the control of the CPU 101.

  When XML documents are exchanged between nodes in the LAN 1211, the normalized XML documents are exchanged directly between the nodes because they do not go through the gateway 1212. Although this processing procedure is not shown, for example, when a message is sent from the normalized XML compatible node 1214 to the normalized XML compatible node 1213, the normalized XML compatible node 1214 outputs only the normalized XML document. For this reason, the document is analyzed by the normalization parser unit 1002 provided in the XML corresponding node 1213, and the content of the message is transmitted to the application 509 (FIG. 16).

  On the other hand, for example, when the normalized XML compatible node 1214 receives a message from the normalized XML compatible node 1223 belonging to another LAN 1221, this message is forwarded to the gateways 1222 and 1212 in order. The gateway 1222 transfers the message transferred from the LAN 1221 in the direction of the WAN 1201 without processing anything. On the other hand, the gateway 1212 performs normalization determination similar to that in the above-described fourth embodiment with respect to the message transferred from the WAN 1201 to the LAN 1211. Since this time the message is sent from the normalized XML compatible node 1223, it is determined to be a normalized XML document (S1702), and transferred to the LAN 1211 as it is (S1706). The normalization-compatible node 1214 also analyzes the received message as it is as a normalized XML document and notifies the application 509 of the contents.

  Further, for example, when the normalized XML compatible node 1214 receives a message from the general-purpose XML compatible node 1233 belonging to another LAN 1231, the gateways 1232 and 1212 are sequentially transferred. Since the gateway 1232 is a normal gateway, the message is transferred from the LAN 1231 to the WAN 1201 without any processing. The gateway 1212 performs normalization determination similar to that in the above-described fourth embodiment with respect to the message transferred from the WAN 1201 to the LAN 1211. Since this time the message is sent from the general-purpose XML-compatible node 1233, it is determined in step S1702 that the document is a denormalized XML document. Accordingly, the process proceeds to step S1703, and after normalization by the normalization unit 504, the process proceeds to step S1706, and the normalized XML document is transferred to the LAN 1211. Since the received message has already been normalized, the normalization corresponding node 1214 analyzes it as a normalized XML document as it is and notifies the application 509 of the contents.

  As described above, according to the fifth embodiment, only the normalized XML document is transferred inside the LAN to which the normalized XML compatible node belongs. Therefore, the normalization determination unit and the normalization unit provided in the normalized XML compatible node in the fourth embodiment are not necessary, and the normalized XML compatible node can be implemented with a very light and high speed. .

  On the other hand, although the load on the gateway side increases, it can be more costly than a node that requires features such as small size and light weight. In addition, it is not something that is directly touched by the user, and is not strongly demanded for a small size and light weight, so it is easy to cope with the load. Therefore, by concentrating resources necessary for normalization processing from each node to the gateway, it is possible to improve performance in a comprehensive manner.

  In the fifth embodiment, the gateway has the normalization determination unit 1303. However, the data itself to be transferred is analyzed instead of the host information to determine whether the document is a normalized document or a non-normalized document. You can also. In that case, the normalization determination unit can have grammatical information required as normalization XML, and a method of comparing with transfer data can be used.

  FIG. 18 is a block diagram showing a configuration of a gateway 1501 that is a modification of the fifth embodiment of the present invention. As shown in FIG. 18, the normalization determination unit 1303 shown in FIG. 15 may be eliminated, and all the XML documents transferred from the WAN 1201 to the LAN may be normalized. Even if the XML document that has been normalized is further normalized, the result is not affected. Therefore, as in the case where the gateway shown in FIG. 15 is used, an environment in which only the normalized XML document is used on the LAN is maintained. There is an effect.

(Other embodiments)
The embodiment of the present invention has been described in detail above. However, the present invention may be applied to a document processing system including a plurality of devices or a document processing apparatus including a single device. good.

  In the present invention, a software program that implements the functions of the above-described embodiments is supplied directly or remotely to a system or apparatus, and the computer of the system or apparatus reads and executes the supplied program. Can also be achieved. In the above embodiment, the program corresponds to the flowcharts of FIGS. 5 to 7 and FIGS. 9 to 13. In that case, as long as it has the function of a program, the form does not need to be a program. Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. That is, the claims of the present invention include the computer program itself for realizing the functional processing of the present invention. In this case, the program may be in any form as long as it has a program function, such as an object code, a program executed by an interpreter, or script data supplied to the OS.

  Various recording media for supplying the program can be used. For example, floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD- R).

  As another program supply method, the program can be supplied by connecting to a home page on the Internet using a browser of a client computer and downloading the program from the home page to a recording medium such as a hard disk. In this case, the computer program itself of the present invention or a compressed file including an automatic installation function may be downloaded. It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the claims of the present invention.

  Further, the program of the present invention may be encrypted, stored in a storage medium such as a CD-ROM, and distributed to users. In that case, a user who has cleared a predetermined condition is allowed to download key information to be decrypted from a homepage via the Internet, and using the key information, the encrypted program can be executed on a computer in a format that can be executed. To be installed.

  Further, the present invention can be realized in a form other than the form in which the functions of the above-described embodiments are realized by the computer executing the read program. For example, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Furthermore, the program read from the recording medium may be written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. In this case, thereafter, based on the instructions of the program, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing. .

It is a block diagram explaining the schematic structure of the information processing apparatus which concerns on embodiment of this invention. It is a figure which shows an example of the normalization XML document which is the analysis object in this Embodiment. It is a figure which shows an example of the denormalized XML document which is the analysis object in this Embodiment. It is a figure which shows an example of the non-XML document of the analysis object in this Embodiment. It is a block diagram which shows the function structure of the DOM parser which concerns on Embodiment 1 of this invention. It is a flowchart explaining the process sequence in the DOM parser which concerns on Embodiment 1 of this invention. It is a figure which shows the specific example of the grammar violation information corresponding | compatible table which concerns on Embodiment 1-2 of this invention. It is a block diagram which shows the function structure of the DOM parser which concerns on Embodiment 2 of this invention. 12 is a flowchart for explaining a processing procedure in the DOM parser according to the second embodiment. It is a block diagram explaining the structure of the parser which concerns on Embodiment 3 of this invention. 10 is a flowchart illustrating a processing procedure in a parser according to Embodiment 3. It is a figure explaining the network with which the node which has a parser concerning Embodiment 4 and 5 of this invention was connected. It is a block diagram which shows the structure of the normalization XML corresponding | compatible node which concerns on this Embodiment 4. 14 is a flowchart illustrating a processing procedure in a parser unit according to the fourth embodiment. It is a block diagram which shows the structure of the gateway which concerns on Embodiment 5 of this invention. FIG. 10 is a block diagram illustrating a configuration of a node according to a fifth embodiment. It is a flowchart which shows the process sequence of the gateway which concerns on Embodiment 5 of this invention. It is a block diagram which shows the structure of the gateway which is a modification of Embodiment 5 of this invention.

Claims (11)

A document processing device for analyzing an input structured document,
Normalized XML analysis means for analyzing the normalized XML document;
Normalization means for converting an unnormalized XML document into a normalized XML document and supplying the normalized XML document to the normalized XML analysis means;
Identification means for identifying whether the input document is at least a normalized XML document,
A document processing apparatus characterized in that an XML document identified as not being a normalized XML document by the identifying means is converted into a normalized XML document by the normalizing means and analyzed by the normalized XML analyzing means. The identification means has a database for storing grammatical rule information of the XML document,
The grammar of the input document is identified with reference to the database, and the input document is classified into any one of a denormalized XML document, a normalized XML document, and a non-XML document. 1. The document processing apparatus according to 1.   2. The processing according to claim 1, wherein when the input document is determined to be a normalized XML document by the identification unit, the input document is processed based on a result of analysis by the normalized XML analysis unit. 2. The document processing apparatus according to 2. A document processing device for analyzing an input structured document,
Normalized XML analysis means for analyzing the normalized XML document;
Normalization means for converting the input document into a normalized XML document and supplying the normalized XML document to the normalized XML analysis means;
And a discriminating unit that discriminates a document that cannot be normalized by the normalizing unit as a non-XML document.   The document processing apparatus according to claim 1, wherein the identification unit identifies based on an identifier of the input document. A document processing method for inputting and analyzing a structured document,
A normalized XML analysis step of analyzing the normalized XML document;
A normalization step of converting a non-normalized XML document into a normalized XML document and supplying it to the normalized XML analysis step;
An identification step for identifying whether the input document is at least a normalized XML document,
A document processing method, wherein an XML document identified as not a normalized XML document in the identifying step is converted into a normalized XML document by the normalizing step and analyzed in the normalized XML analyzing step.   The identifying step identifies a grammar of the input document with reference to a database storing grammatical rule information of the XML document, and the input document is classified into a denormalized XML document, a normalized XML document, and a non-XML document. The document processing method according to claim 6, wherein the document processing method is classified into any one of the above.   7. The processing according to claim 6, wherein when the input document is determined to be a normalized XML document in the identification step, the input document is processed based on a result of analysis by the normalization XML analysis step. 8. The document processing method according to 7. A document processing method for inputting and analyzing a structured document,
A normalized XML analysis step of analyzing the normalized XML document;
A normalization step of converting the input document into a normalization XML document and supplying the normalization XML document to the normalization XML analysis step;
And a determination step of determining a document that cannot be normalized by the normalization step as a non-XML document.   10. The document processing method according to claim 6, wherein in the identification step, identification is performed based on an identifier of the input document.   A program for executing the document processing method according to any one of claims 6 to 9.

Images