JP2001325248A - Document data processor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document data processor having improved processing efficiency in contrast to a conventional document data processor which has a problem that the processing efficiency is low since the processing of an HTML parser is performed after the processing of an XML parser is performed. SOLUTION: In this document data processor, a CPU 11 reads document data and performs the processing as the XML parser. At the time of detecting a tag which is not an XML tag during the processing of the XML parser, the start tag processing part or end tag processing part of the HTML parser is activated and the pertinent part is processed. Further, at the time of finding the tag related to CDATA or a pre-format, a corresponding processing is performed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document data processing apparatus for displaying structured document data and the like.
In particular, XML (Extensible Markup Language) and HTM
The present invention relates to a document data processing device capable of supporting both L (HyperText Markup Language).

[0002]

2. Description of the Related Art In recent years, there is a markup language called HTML as a format of document data widely used on the Internet. HTML is SGML (Standard General
It is described in accordance with a meta-language grammar called "ized Markup Language". However, in the processing of a document described in SGML, various kinds of designation processing can be performed, but the processing becomes complicated. Therefore, a simplified language called XML is being formulated. In addition, the XML can include attributes of the document and data to be subjected to specific processing (data not directly displayed but used by the processing device) in the document.

[0003] Document data described in XML is acquired and processed in the same manner as HTML. However, a personal computer including a Web browser as a conventional document data processing apparatus cannot directly process the XML. After the acquired XML document is converted into HTML, the process is performed again as an HTML document.

In XML and SGML, a syntax is declared by setting a DTD (Data Type Definition) in a document file or another file referred to by the document file, and the document data is processed according to the declaration. .

For example, in SGML, a tag for marking (data surrounding content to be subjected to a specific process) can be defined using DTD. In this SGML, the DTD is used so that the tag indicating the end can be omitted and described.
You can create a definition using When processing document data in which the end tag is omitted in this way, it is necessary to determine whether or not the content is for the tag, and if content that is not found is found, it is necessary to process the content as if there was an end tag. is there. Specifically, <D> (start tag of paragraph) in HTML can be defined by using DTD to omit the corresponding end tag (</ P>). In SGML,
It is also possible to define that a required start tag can be omitted in the document data.

On the other hand, in XML, the types of the start tag and the end tag are restricted, and the type of the content is more limited than the SGML in relation to the reference data and the tag. That is, in SGML, PCDATA (Parsed Character Data) for processing tags and reference data (with respect to image data and the like) in content, and RCDATA (RaplPlatform) for processing only reference data ignoring tags.
ACEable Character Data) and CDATA (Characte) that can handle both tags and reference data as simple character strings.
r Data), but in XML, PCDA
Only TA is available. Here, CDATA is used not for the purpose of display and printing, but for description of a script program in JavaScript.

For this reason, in a conventional document data processing apparatus, in order to support both XML and HTML, an XML
The L data is processed and converted into HTML data, and then the converted HTML data is processed.

[0008]

As described above, in the conventional document data processing apparatus, an XML parser is executed to convert XML to HTML, and an HTML parser is executed based on the processing result of the parser. Therefore, the processing load increases. In addition, many existing HTML documents do not have a DTD definition associated with them.
The ML parser may not operate properly. Further, in many existing HTML documents, the end tag is omitted in many cases, and there is a problem that the XML parser cannot process normally as it is.

Further, recent HTML document data includes:
A <SCRIPT> tag for JavaScript, a <STYLE> tag for designating a style sheet, and the like are set, and some of them are based on the assumption that the content is processed as CDATA. Furthermore, there is a method that uses a tag called a <PRE> tag to display a space or a line feed according to the content. These document data cannot be processed normally by the XML parser.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and has as its object to provide a document data processing apparatus capable of normally processing XML data mixed in HTML and improving processing efficiency.

[0011]

According to a first aspect of the present invention, there is provided a document data processing apparatus, comprising: a partial document data described in HTML and a partial document data described in XML; A document data processing apparatus for processing tagged document data including at least one of partial document data, comprising: HTML parser means for processing and outputting predetermined partial document data as an HTML document; The document data is sequentially analyzed for each partial document data, and an operation of activating the HTML parser means according to a result of the analysis and an operation of processing the analyzed partial document data as an XML document are selectively performed. And an XML parser for performing the processing.

By this XML parsing means, the document data of the HTML portion detected during the parsing of the XML parser is processed by the HTML parser, so that the processing efficiency can be improved. According to a second aspect of the present invention, there is provided a document data processing apparatus, comprising: means for acquiring a data type attribute of tagged document data to be processed; Means for acquiring a default data type definition defined in advance in association with the data type attribute, wherein the XML parser performs processing according to the acquired default data type definition. As a result, the default DTD can be applied to document data to which no DTD definition is associated, and the document data can be processed normally.

Further, it is preferable that the XML parsing means performs the processing according to the acquired default data type definition only when the tagged document data to be processed does not have an XML declaration.

According to a fourth aspect of the present invention, there is provided a document data processing apparatus as set forth in the first aspect, wherein the tagged document data to be processed includes: Means for obtaining a data type definition associated with the document data; means for obtaining a data type attribute of the tagged document data; and a default data type definition previously defined in association with the data type attribute. Acquiring means, wherein the XML parsing means performs processing according to the acquired data type definition and the default data type definition.

According to a fifth aspect of the present invention, there is provided a document data processing apparatus as set forth in any one of the first to fourth aspects, wherein each special tag is assigned to the special tag. A parser for processing related partial document data; a unit for setting at least one set of information of the special tag and a parser corresponding to the special tag; wherein the XML parser analyzes the tagged document data. When the special tag is detected as a result of the analysis,
It is characterized in that parser means corresponding to the special tag is activated.

It is preferable that the special tag includes at least one of a tag related to CDATA and a tag related to preformat.

According to a seventh aspect of the present invention, there is provided a document data processing apparatus as set forth in any one of the first to sixth aspects, further comprising information on omission availability of each tag. , Wherein the XML
When the parser detects a tag set to be omissible, the parser analyzes whether or not the tag is omitted. If the tag is omitted based on a result of the analysis, the parser complements the omitted tag. And processing the document data. As a result, normal processing can be performed on document data from which tags have been omitted.

An invention according to claim 8 for solving the problem of the conventional example is a document data processing apparatus, wherein
A document data processing apparatus for processing document data including at least one of partial document data described in accordance with the first rule and partial document data described in accordance with the second rule. A first parser for processing and outputting according to the rules, an operation of sequentially analyzing the document data to be processed for each partial document data, and activating the first parser in accordance with the result of the analysis; And second parser means for selectively performing one of the following operations on the partial document data according to the second rule.

[0019]

Embodiments of the present invention will be described with reference to the drawings. A document data processing device according to an embodiment of the present invention is a personal computer,
Specifically, as shown in FIG.
It basically includes an OM 12, a RAM 13, a hard disk 14, a display 15, an operation unit 16, a LAN interface 17, and an external storage device 18.

The CPU 11 starts the boot RO immediately after the power is turned on.
An initialization process for loading the program stored in M12 onto the RAM 13 and executing the program is performed. By this initialization process, the CPU 11 loads the operating system stored in the hard disk 14 onto the RAM 13 and
Start processing. Then, the CPU 11 loads a browser for processing document data from the hard disk 14 onto the RAM 13 according to an instruction input from the operation unit 16 and performs processing. This browser processing will be described later in detail.

The boot ROM 12 stores programs related to the initialization processing of the CPU 11. RAM 13
Operates as a work memory of the CPU 11. The hard disk 14 stores various programs processed by the CPU 11. Also, this hard disk 14 has a CP
Data necessary for the processing of U11 (for example, a default DTD set in advance) is stored.

The display 15 displays and outputs various data according to an instruction input from the CPU 11. The operation unit 16 is a keyboard, a mouse, or the like, and transmits contents of an operation performed by the user to the CPU 11. The LAN interface 17 is connected to a Web server via a LAN (Local Area Network) or the Internet.
According to an instruction input from the PU 11, data is transmitted via the network, and data arriving via the network is received and output to the CPU 11.

The external storage device 18 holds data optically or electromagnetically, such as a floppy (registered trademark) disk or a magneto-optical disk, reads data from a computer-readable recording medium or the like, and outputs the data to the CPU 11. The CPU 11 installs the data read from the external storage device 18 on the hard disk 14 as a processing program.

Here, the document data processing of the CPU 11 will be described. As shown in FIG. 2, a browser program for document data processing processed by the CPU 11 according to the present embodiment includes a TCP / IP
It comprises an ML parse unit 22, an HTML parse unit 23, a browser core unit 24, and a drawing unit 25. The HTML parse unit 23 includes a pre-format processing unit 31, a CDATA processing unit 32, and a start tag processing unit 33.
And an end tag processing unit 34. Here, the XML parse unit 22 corresponds to the XML parser unit or the second parser unit of the present invention, and the HTML parse unit 23 corresponds to the HTML parser unit or the first parser unit of the present invention. Also, the preformat processing unit 31 and the CD
The ATA processing unit 32 corresponds to parser means corresponding to the special tag of the present invention, and the document data to be pre-formatted is associated with the special tag “<PRE>”
Is a special tag such as “<SCRIPT>”.

The TCP / IP protocol processing unit 21
The document data is acquired via the network by the CP / IP protocol and output to the XML parse unit 22.
Here, the document data acquired by the TCP / IP protocol processing unit 21 is specifically as shown in FIG.
In FIG. 3, a part (for example, <HTML> at the head) surrounded by characters “<” and “>” is called a tag. In addition, among these tags, those that start with “</” are end tags, and those that do not are start tags. As shown in FIG. 3, the document data assumed in the document data processing apparatus according to the present embodiment has a nested basic structure including a start tag, content data, and an end tag. That is, start tag <HTML> and end tag </ HTML
The content between <> includes content surrounded by a start tag <BODY> and an end tag </ BODY>, and the content also includes a plurality of basic structures. In the document data of FIG. 3, an end tag corresponding to, for example, a “<BR>” tag is omitted, as in the case of a large number of HTML documents.

Although not shown in FIG. 3, in XML, tags ending with "/>" are generally treated as end tags for convenience.

Here, the XM which the CPU 11 performs on the document data acquired by the TCP / IP protocol processing unit 21
The processing as the L parse unit 22 will be described with reference to FIG. In the following description, it is assumed that an operation parameter and a default DTD corresponding to a default data type definition are set and stored in the hard disk 14 in advance. Here, the operation parameter is a pointer (A) to the start tag processing unit 33 as shown in FIG.
, A pointer (B) to the end tag processing unit 34, and the CDA
Pointer (C) to TA processing unit 32, array (D) of tag names to be processed as CDATA, pointer (E) to preformat processing unit 31, and tag name to be processed by preformat processing unit 31 (F) is associated with a flag (G) indicating whether or not the end tag can be omitted. The default DTD includes an element declaration and an attribute declaration. As shown in FIG. 5, an identifier (H), a tag name (I), a type (J), a flag (K) indicating whether or not a start tag and an end tag can be omitted, and a tag that may be included in the content. The list (L) is associated with the list (L). As shown in FIG. 6B, the attribute declaration associates an identifier (M), a tag name (N), an attribute name (O), and an attribute value type (P). When the attribute value type is an enumeration, an array of possible values (Q) is further associated. In these FIGS. 5 and 6, the end of the array is identified by NULL, as is generally widely known.

As shown in FIG. 4, the CPU 11 first loads operation parameters from the hard disk 14 as a process of the XML parse unit 22 (S1).
The TD is loaded from the hard disk 14 (S2). Then, the document data is read (S3), and it is determined whether or not the document data has been completed (S4).

In step S4, if it is not completed (if No), it is checked whether the read document data is an XML tag (S5). Here, the XML tag is a special tag starting with “<!” Or “<?”. Such tags include, for example, comments beginning with "<!-". In this process S5, if the tag is an XML tag (Yes), the process of the XML tag is executed (S5).
6) Return to the process S3 to continue the process (A). On the other hand, X
If it is not an ML tag (if No), it is further checked whether it is a start tag (S7), and if it is a start tag (Yes)
Then, the default DTD is referred to using the tag name of the start tag as a key, a pointer to the start tag processing unit 33 is obtained, and the start tag processing unit 33 is activated using the read document data as an argument (S8). This start tag processing unit 33
The operation of will be described later.

When the processing of the start tag processing section 33 is completed, the CPU 11 resumes the processing of the XML parser,
It is checked whether or not the start tag processed in step S8 is a tag to be processed as CDATA with reference to the operation parameter (S9). If the tag is to be processed as CDATA (if Yes), the CDATA processing is performed. The unit 32 is started (S10). The CPU 11 controls the CDATA processing unit 32
As an operation of, processing is performed as CDATA until the corresponding end tag is read, and processing for adding to the tree structure is performed. When the operation of the CDATA processing unit 32 is completed, the CPU 11 returns to the processing S3 and continues the processing of the XML parser.

On the other hand, in step S9, if the tag is not a tag to be processed as CDATA (if No), it is further checked whether or not the start tag is a tag to be preformatted by referring to the operation parameters. (S11),
If the tag is to be preformatted (Yes), the preformat processing unit 31 is started (S1).
2). Then, the CPU 11 executes the preformat processing unit 3
As a process 1, while the end tag corresponding to the tag is read, a process of adding it to the tree structure as PCDATA is performed. When the pre-format processing unit 31 detects a line feed code, the pre-format processing unit 31 performs a process of replacing the line feed code with a line feed tag <BR>. Then, the CPU 11 executes the preformat processing unit 3
Upon completion of the process 1, the process returns to the process S3 to continue the process of the XML parser. If it is determined in step S11 that the tag is not to be preformatted, the process proceeds to step S3.
And the processing of the XML parser is continued.

Further, in step S7, if it is not the start tag (if No), the CPU 11 checks whether or not the read document data is the end tag (S13).
If it is an end tag (if Yes), the end tag processing unit 34 is started (S14), and end tag processing is performed.
The process returns to step S3 and continues. Here, the processing contents of the end tag processing unit 34 will be described later.

In step S13, if the tag is not the end tag (if No), the process is performed as normal content (S15), and the process returns to step S3 to continue the process.

Here, the operation of the start tag processing section 33 performed by the CPU 11 will be described. The CPU 11 activates the start tag processing unit 33 with the read document data as an argument, and first adds the read tag element one level below the element currently pointed to in the tree structure, and adds the added element. Is newly pointed as the current element. If the tag is the first tag (if there is no tree structure), the first tag is registered as the first level (root) of the tree structure, and the root is pointed as the current element.

Specifically, for the document data shown in FIG.
The CPU 11 forms the tree structure shown in FIG. That is, <HTML> on the first line of the document data in FIG. 4 is recognized as a start tag, and the “HTM
"L" is set as the root of the tree structure and pointed (X), and then <HEAD> on the second line is recognized as a start tag, and "HEAD" is one level lower than the element (HTML) currently pointed to. "Element (Y), and this" HEAD "
To point. Further, since "TITLE" on the third line is also a start tag, an element of "TITLE" is further added one level lower, and the subsequent "HOME PAGE" is added as PCDATA (Z).

Here, the operation of the end tag processing unit 34 performed by the CPU 11 will be described. The CPU 11 starts the end tag processing unit 34 with the read document data and the element currently pointed in the tree structure as arguments, and
The element of the ML tree structure is analyzed as HTML, the element is converted into an HTML document and stored in the RAM 13, and the position pointed in the tree structure is set one level higher, and newly created. Points to the current element.
Specifically, in FIGS. 4 and 7, “</ TITLE>” after PCDATA “HOME PAGE” (Z) added to the “TITLE” element is recognized as an end tag, and a start tag “<TITLE” is recognized.
LE>"to the end tag"</TITLE>"
E> HOME PAGE </ TITLE> ”as an HTML document,
It is stored in the RAM 13 as an HTML document. And
The processing of the end tag is completed by pointing to “HEAD” (Y) one level higher than “TITLE”. In this way, the HTML document obtained as a result of the processing of the end tag processing unit 34 is converted into a line structure as shown in FIG.

The CPU 11 further includes an XML parse unit 22
Is completed, the browser core unit 24 is activated,
HTML documents stored in the RAM 13 (HTML and X
XML parse unit 22 and HTM from document with mixed ML
The document is converted to HTML by the operation of the L parser unit 23), and based on the HTML document, the drawing unit 25
To output the drawing instruction. The drawing unit 25 displays the absolute coordinates and size of each line of the document, the text and the image portion, the absolute coordinates and size, the font for the text, the URL (Uniform Resource Locators) as information for referring to the image, and the like. Displays the contents of the document data as a drawing result.

In the above description, the default DTD is loaded in advance. However, when the tag “<! DOCTYPE” that declares the data type is detected in the XML tag processing, the data type is not loaded. Default DTD only if is a specific one (eg HTML 3.2)
May be loaded. Also, as an operation of the start tag processing unit 33, when the “<HTML>” tag is detected,
The default DTD may be loaded only when the DTD declaration (“<! DOCTYPE”) has not been detected by then.

Further, if there is a DTD that is referred to in the document data or from the document data in relation to the read document data, the CPU 11 executes the DTD.
Is preferably used in the processing of the XML parse unit 22 in place of the default DTD or together with the default DTD.

When a flag indicating whether or not the end tag can be omitted is set in the operation parameter so that a specific tag can be omitted, the CPU 11 reads the start tag and adds it to the tree structure. The next higher element is obtained, and the loaded DTD is referred to.
When it can be omitted, if the type is EMPTY (a tag ending with "/>") or it is a tag that is not EMPTY but is not in the list of tags that may be included in the content in the element declaration Then, the end tag processing unit 34 is activated assuming that the end tag is omitted.

When the tag cannot be omitted,
If the tag is not EMPTY and is in the list of tags that may be included in the element declaration content, the tag is added to the tree structure and the start tag processing unit 33 is started.

[0042]

According to the present invention, the XML parse means comprises:
Since the HTML parse means is activated as needed, the document data can be processed efficiently.

According to the present invention, since the default data type definition is used, document data not associated with the data type definition can be normally processed.

Furthermore, according to the present invention, when there is a tag that can be omitted, the end tag is complemented and processed, so that normal processing can be performed even if the tag is omitted.

[Brief description of the drawings]

FIG. 1 is a configuration block diagram of a document data processing device according to an embodiment of the present invention.

FIG. 2 is a configuration block diagram illustrating a structure of browser software processed by a CPU 11;

FIG. 3 is an explanatory diagram illustrating an example of document data.

FIG. 4 is a flowchart illustrating a process performed by the CPU 11 as an XML parser.

FIG. 5 is an explanatory diagram illustrating an example of an operation parameter.

FIG. 6 is an explanatory diagram illustrating an example of a DTD.

FIG. 7 is an explanatory diagram illustrating an example of a tree structure.

FIG. 8 is an explanatory diagram illustrating an example of a row structure.

[Explanation of symbols]

11 CPU, 12 Boot ROM, 13 RAM, 1
4 hard disk, 15 display, 16 operation unit, 17 LAN interface, 18 external storage device, 21 TCP / IP protocol analysis unit, 22 XM
L parse part, 23 HTML parse part, 24 browser core part, 25 drawing part, 31 pre-format processing part,
32 CDATA processing unit, 33 start tag processing unit, 34
End tag processing unit.

Claims (9)

[Claims] 1. A document data processing apparatus for processing tagged document data including at least one of partial document data described in HTML and partial document data described in XML, wherein predetermined document data is converted to HTML. HTML parser means for processing and outputting as a document, and an operation of sequentially analyzing the tagged document data to be processed for each partial document data, and activating the HTML parser means according to the result of the analysis. XML parser means for selectively performing one of the following: an operation of processing the partial document data as an XML document. 2. The document data processing apparatus according to claim 1, further comprising: means for acquiring a data type attribute of the tagged document data to be processed; Means for acquiring a defined default data type definition, wherein the XML parser performs processing according to the acquired default data type definition. 3. The document data processing apparatus according to claim 2, wherein the XML parser means according to the acquired default data type definition only when there is no XML declaration in the tagged document data to be processed. A document data processing device for performing processing. 4. The document data processing apparatus according to claim 1, wherein: a means for acquiring tagged document data to be processed and a data type definition associated with the document data; Means for acquiring a data type attribute of the document data; and means for acquiring a default data type definition predefined in association with the data type attribute, wherein the XML parser means comprises: And a default data type definition. 5. The document data processing apparatus according to claim 1, wherein for each special tag, parser means for processing partial document data related to the special tag, information on the special tag, Means for setting at least one set of parser means corresponding to the special tag, wherein the XML parser means analyzes the tagged document data and detects the special tag as a result of the analysis. A document data processing apparatus for activating a parser means for performing the processing. 6. The document data processing apparatus according to claim 5, wherein the special tag includes at least one of a tag related to CDATA and a tag related to preformat. Processing equipment. 7. The document data processing apparatus according to claim 1, further comprising: means for storing omissibility information for each tag, wherein said XML parser means is set to be omissible. When a tag is detected, it is analyzed whether or not the tag is omitted, and when the tag is omitted based on the result of the analysis, the document data is processed by complementing the omitted tag. Document data processing device. 8. A document data processing apparatus for processing document data including at least one of partial document data described according to a first rule and partial document data described according to a second rule, comprising: A first parser for processing and outputting the document data according to the first rule; and sequentially analyzing the document data to be processed for each partial document data, and activating the first parser according to the result of the analysis. And an operation of selectively processing the analyzed partial document data in accordance with a second rule. 9. A document data processing program for processing document data including at least one of partial document data described according to a first rule and partial document data described according to a second rule, comprising: A first parser module for processing and outputting document data in accordance with the first rule, and sequentially analyzing document data to be processed for each partial document data, and activating the first parser module in accordance with a result of the analysis And a second parser module for selectively performing one of an operation of processing the analyzed partial document data in accordance with a second rule and a second parser module. A readable recording medium.