JP4447067B2 - Document type definition converter - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention relates to a document type definition conversion apparatus that reduces the data amount of a document when transmitting a document created by the document type definition.
[0002]
[Prior art]
  When a document is used for information processing such as data transmission, information processing is performed in a manner that clearly shows the structure of the document. In this method, the document structure is SGML (Standard Generalized Markup Language) according to the ISO (International Standards Organization International Standardization Organization) standard, or XML (extensive Markup Language D), which is a language that uses the D language (eXtensible Markup Language). Definition). This DTD defines the name of the component of the document and the structural relationship between the components.
[0003]
  A document created by this DTD includes a tag in which a tag name indicating the content, characteristics, etc. of a character string is inserted between the symbols “<” and “>”, and is called a tagged document. . In such a tagged document, since information common to each document can be easily extracted using the tag as a mark, it is effective in storing, processing, transmitting, etc. a large number of documents.
[0004]
  However, when such a tagged document is applied to EDI (Electronic Data Interchange Electronic Data Exchange) and the like, and data exchange is repeated many times, a common tag is repeatedly transmitted in each document. Become.
[0005]
[Problems to be solved by the invention]
  Conventionally, as described above, in EDI and the like, since a common tag is repeatedly transmitted in each document created by DTD, there is a problem that the entire data transmission amount is increased and the communication cost is increased. .
[0006]
  The present invention has been made to solve the above-described problems, and an object of the present invention is to obtain a document type definition conversion apparatus that shortens the data amount of a document to be transmitted and reduces the communication cost.
[0007]
[Means for Solving the Problems]
  A document type definition conversion apparatus according to the present invention includes a syntax element extraction unit that extracts a syntax element from a document type definition that defines a document structure, and a syntax element analysis unit that analyzes a syntax element extracted by the syntax element extraction unit A tag name memory for storing a short tag name corresponding to a tag name indicating the content of the character string included in the syntax element as a tag name correspondence table, and the tag name and its tag name.Attached toIf the tag name is included in the attribute name memory that stores the short tag name corresponding to the attribute name and the short attribute name as an attribute name correspondence table, and the syntax element analyzed by the syntax element analysis unit, the tag When the name memory is searched and the tag name is converted to the short tag name, and the syntax element analyzed by the syntax element analysis unit includes the tag name to which the attribute name is added, the attribute A syntax element conversion unit that searches the name memory and converts the tag name and the attribute name into the short tag name and the short attribute name, and the short tag name and the short attribute name converted by the syntax element conversion unit An output unit that combines the syntax elements configured by the above and outputs an abbreviated document type definition. When the syntax element conversion unit searches the tag name memory, the searched tag name is not stored in the tag name memory. If, to generate a short tag name corresponding to the tag name, stored in the tag name memoryIf the searched tag name and attribute name are not stored in the attribute name memory when the syntax element conversion unit searches the attribute name memory, it corresponds to the short tag name corresponding to the tag name and the attribute name. A short attribute name to be generated is generated and stored in the attribute name memory.
[0008]
  In the document type definition conversion apparatus according to the present invention, the syntax element analysis unit uses an element type declaration composed of a comment without a tag name or a tag name without an attribute name added to the extracted component. This is to analyze whether there is an attribute list type declaration composed of a tag name to which an attribute name is added.
[0009]
DETAILED DESCRIPTION OF THE INVENTION
  An embodiment of the present invention will be described below.
Embodiment 1 FIG.
  FIG. 1 is a diagram showing a configuration of a document conversion apparatus according to the first embodiment. In the figure, 1 is a document conversion device, 2 is a document type definition matching document created by document type definition (DTD), 3 is a shortened document type definition matching document converted by the document conversion device 1, and 4 is document type definition matching. Tag name correspondence table 5 showing correspondence between tag names indicating the contents of character strings used in document 2 and the abbreviated abbreviated tag names, 5 is a tag name used in document type definition matching document 2, And an attribute name correspondence table showing correspondence between attribute names attached to the tag names, shortened shortened tag names, and shortened shortened attribute names.
[0010]
  In the document conversion apparatus 1 of FIG. 1, 11 is a tag name memory in which the tag name correspondence table 4 is stored, 12 is an attribute name memory in which the attribute name correspondence table 5 is stored, and 13 is a document type definition matching document. A syntax element extracting unit 14 extracts a syntax element from 2, and a syntax element analyzing unit 14 analyzes the syntax element extracted by the syntax element extracting unit 13. 15 is a syntax element conversion unit that searches the tag name memory 11 and the attribute name memory 12 based on the tag name and attribute name in the syntax element, and converts the tag name and attribute name to the short tag name and short attribute name. This is an output unit that combines the syntax elements converted by the syntax element conversion unit 15 and outputs the combined result as the short document type definition matching document 3.
[0011]
  FIG. 2 is a diagram showing an example of the document type definition matching document 2 used in EDI or the like. In the figure, “<? Xml version ...>” of 101 is version information, “<! DOCTYPE estimate request information SYSTEM ...... >>” is a document type declaration, and “<quote request information> …… </ quote request” of 103 “Information>” indicates a part in which the text of the document type definition matching document 2 is described, and “m_irai.dtd” 104 indicates a file name.
[0012]
  In FIG. 2, “Quote Request Information”, “Quotation Request Number”, “Quotation Request Date”, “Quantity”, and “Product Number” are the tag names, and “Year”, “Month”, “Day” are 106. "Is an attribute name, 107 is" year = ... month = ... day = ... "is an attribute list, 108 is" <...> "is a syntax element, 109 is" <tag name 105> "is a tag. As described above, the tag name 105 is information indicating the contents, features, properties, and the like of the character string, and the attribute name 106 indicates an index for identifying the tag name 105. The version information 101 does not include the tag name 105, but the document type declaration 102 includes the tag name 105.
[0013]
  FIG. 3 is a diagram showing the tag name correspondence table 4, in which 115 is a shortened tag name corresponding to each tag name 105. As shown in FIG. 3, the tag name correspondence table 4 describes abbreviated tag names 115 corresponding to the tag names 105 and is stored in the tag name memory 11.
[0014]
  FIG. 4 is a diagram showing the attribute name correspondence table 5, in which 116 is a shortened attribute name corresponding to the attribute name 106. As shown in FIG. 4, the attribute name correspondence table 5 describes the short tag name 115 corresponding to each tag name 105 and the short attribute name 116 corresponding to the attribute name 106 and is stored in the attribute name memory 12. ing.
[0015]
  Next, the operation will be described.
  FIG. 5 is a flowchart showing processing of the document conversion apparatus 1. In step ST11, the syntax element extraction unit 13 extracts the syntax element 108 from the document type definition matching document 2 shown in FIG. That is, one “<...>” In FIG. In step ST12, the syntax element analysis unit 14 checks whether or not the extracted syntax element 108 is the document type declaration 102.
[0016]
  If the extracted syntax element 108 is not the document type declaration 102 in step ST12, the syntax element analysis unit 14 checks whether the extracted syntax element 108 is the tag 109 in step ST13. That is, it is checked whether the syntax element 108 is “<tag name 105>”.
[0017]
  If the extracted syntax element 108 is not the tag 109 in step ST13, for example, in the case of the version information 101 shown in FIG. 2, the syntax element conversion unit 15 outputs the extracted syntax element 108 as it is in step ST14. In step ST15, it is checked whether or not the document type definition matching document 2 has the next syntax element 108. If the next syntax element 108 exists, the processes in and after step ST11 are performed.
[0018]
  In step ST15, when the document type definition matching document 2 does not have the next syntax element 108, in step ST16, the output unit 16 combines the syntax elements 108 output by the syntax element conversion unit 15, and shortens the document type. Output as definition matching document 3.
[0019]
  When the extracted syntax element 108 is the tag 109 in step ST13, for example, in the case of “<estimation request number>” illustrated in FIG. 2, the syntax element analysis unit 14 includes the tag 109 in step ST17. It is checked whether the attribute list 107 exists.
[0020]
  If the attribute list 107 is not included in the tag 109 in step ST17, for example, in the case of “<estimation request number>” shown in FIG. 2, the syntax element conversion unit 15 in step ST18 causes the tag 109 in the tag 109 to The tag name memory 11 is searched by the name 105, and the short tag name 115 corresponding to the tag name 105 is extracted. For example, “B” corresponding to “estimation request number” is extracted.
[0021]
  In step ST19, the syntax element conversion unit 15 converts the tag name 105 into the abbreviated tag name 115, for example, converts “estimation request number” into “B”, and performs the processing after step ST14.
[0022]
  If the attribute list 107 is included in the tag 109 in step ST17, for example, if “<estimation request date year =“ 1998 ”month =“ 7 ”day =“ 28 ”>” shown in FIG. 2, step ST20 2, the syntax element conversion unit 15 searches the attribute name memory 12 using the tag name 105 and the attribute name 106 in the tag 109, and shortens the tag name 115 corresponding to the tag name 105 and the abbreviation corresponding to the attribute name 106. The attribute name 116 is extracted. For example, “C” corresponding to “estimation request date”, “C1” corresponding to “year”, “C2” corresponding to “month”, and “C3” corresponding to “day” are extracted.
[0023]
  In step ST21, the syntax element conversion unit 15 converts the tag name 105 into the abbreviated tag name 115, converts the attribute name 106 into the abbreviated attribute name 116, and converts, for example, “estimation request date” into “C”. The “year” is converted to “C1”, the “month” is converted to “C2”, and the “day” is converted to “C3”, and the processes after step ST14 are performed.
[0024]
  If the extracted syntax element 108 is the document type declaration 102 in step ST12, for example, if “<! DOCTYPE estimate request information SYSTEM ...” in the document type declaration 102 shown in FIG. 2, the syntax element is determined in step ST22. The conversion unit 15 searches the tag name memory 11 using the tag name 105 in the tag 109 and extracts the short tag name 115 corresponding to the tag name 105. For example, “A” corresponding to “quotation request information” is extracted.
[0025]
  In step ST23, the syntax element conversion unit 15 converts the tag name 105 into the abbreviated tag name 115, for example, converts “quotation request information” into “A”. In step ST24, the syntax element conversion unit 15 converts the file name 104 in the document type declaration 102, for example, converts “m_irai.dtd” in the document type declaration 102 to “m_irai_c.dtd”. Processes after ST14 are performed.
[0026]
  In the above processing, for example, “ABCD0001” other than “<...>” In “<estimation request number> ABCD0001 </ quote>” shown in FIG. 2 is output as it is.
[0027]
  FIG. 6 is a diagram showing the abbreviated document type definition matching document 3 converted by the document conversion apparatus 1. The tag name 105 and the attribute name 106 are the abbreviated tag name 115 and the document name definition matching document 2 of FIG. The short attribute name 116 is converted, and the file name 104 is converted to 114. The data amount of the document type definition matching document 2 shown in FIG. 2 is 302 bytes, but the data amount of the shortened document type definition matching document 3 shown in FIG. 6 is 157 bytes, and the data amount is reduced to almost ½. ing. In this way, by using a shortened document with a reduced data amount for EDI, the data transmission amount is reduced.
[0028]
  The receiving side that receives the transmitted short document type definition matching document 3 has the same tag name correspondence table 4 and attribute name correspondence table 5 as the transmission side, so that the transmitted short document type definition matching document 3 is stored. Can be read as the original document type definition consistent document 2.
[0029]
  Further, by providing a document conversion device equivalent to the document conversion device 1 on the receiving side, it is possible to automatically convert the transmitted shortened document type definition consistent document 3 to the original document type definition consistent document 2. It is. For example, in the configuration of FIG. 1, the document type definition matching document 2 and the short document type definition matching document 3 are replaced, and the syntax element conversion unit 15 uses the short tag name 115 and the short attribute name 116 to change the tag name memory 11 and the attribute name. The memory 12 may be searched and converted into the tag name 105 and the attribute name 106.
[0030]
  As described above, according to the first embodiment, when a small amount of data exchange such as EDI is repeated many times, the syntax element conversion unit 15 converts the tag name 105 and the attribute name 106 into the short tag name 115, By converting to the shortened attribute name 116, it is possible to reduce the amount of data to be transmitted and to reduce the communication cost.
[0031]
Embodiment 2. FIG.
  FIG. 7 is a diagram showing a document type definition conversion apparatus 6 according to the second embodiment. In the figure, reference numeral 6 denotes a document type definition conversion apparatus that automatically generates and updates the tag name correspondence table 4 and the attribute name correspondence table 5 in the first embodiment. 7 is a document type definition (DTD) used in sentence EDI and the like, and 8 is a shortened document type definition converted by the document type definition conversion device 6.
[0032]
  In the document type definition conversion apparatus 6 of FIG. 7, 61 is a tag name memory for storing the tag name 105, 62 is an attribute name memory for storing the attribute name 106, and 63 is a syntax for extracting syntax elements from the document type definition 7. An element extraction unit 64 is a syntax element analysis unit that analyzes the syntax elements extracted by the syntax element extraction unit 63. A syntax element conversion unit 65 searches the tag name memory 61 and the attribute name memory 62 based on the tag name 105 and the attribute name 106 in the syntax element and converts them into the short tag name 115 and the short attribute name 116.
[0033]
  Further, in FIG. 7, reference numeral 66 denotes a shortened tag name generating unit that generates a shortened tag name 115 corresponding to the tag name 105 not stored in the tag name memory 61 according to an instruction from the syntax element converting unit 65. An abbreviated attribute name generation unit 68 generates a tag name 105, an abbreviated tag name 115 corresponding to the attribute name 106, and an abbreviated attribute name 116 which are not stored in the attribute name memory 62 according to an instruction from the element conversion unit 65. This is an output unit that combines the syntax elements converted by the element conversion unit 65 and outputs them as a shortened document type definition 8.
[0034]
  FIG. 8 is a diagram showing an example of the document type definition 7. In the figure, 201 “<!-Quotation request DTD example…>” is a comment, 202 “<! ELEMENT ...>” is an element type declaration, 203 “<! ATTLIST ...>” is an attribute list declaration, 204 “(...)” Indicates a content model, and 205 “EMPTYTY”, “CDATA”, and “#PCDATA” indicate system definitions. The tag name 105, attribute name 106, and syntax element 108 are the same as those in FIG. 2 of the first embodiment.
[0035]
  Next, the operation will be described.
  FIG. 9 is a flowchart showing processing of the document type definition conversion apparatus 6. In step ST31, the syntax element extraction unit 63 extracts the syntax element 108 from the document type definition 7 shown in FIG. That is, one “<...>” In FIG. 8 is extracted. In step ST <b> 32, the syntax element analysis unit 64 checks whether or not the extracted syntax element 108 is the element type declaration 202.
[0036]
  If the extracted syntax element 108 is not the element type declaration 202 in step ST32, the syntax element analysis unit 64 checks in step ST33 whether the extracted syntax element 108 is the attribute list declaration 203.
[0037]
  In step ST33, if the extracted syntax element 108 is not the attribute list declaration 203, for example, in the case of the comment 201 shown in FIG. 8, in step ST34, the syntax element conversion unit 65 uses the extracted syntax element 108 as it is. In step ST35, it is checked whether or not the next syntax element 108 exists in the document type definition 7. If the next syntax element 108 exists, the processing after step ST31 is performed.
[0038]
  In step ST35, if the document type definition 7 does not include the next syntax element 108, in step ST36, the output unit 68 combines the syntax elements 108 output by the syntax element conversion unit 65, and shortens the document type definition. 8 is output.
[0039]
  If the extracted syntax element 108 is the element type declaration 202 in step ST32, for example, “<! ELEMENT estimate request information ...>” in 202 shown in FIG. 8, the syntax element conversion unit in step ST37. 65 searches the tag name memory 61 using the tag name 105 in the element type declaration 202, extracts the short tag name 115 corresponding to the tag name 105, for example, “A” corresponding to “estimation request information” The syntax element conversion unit 65 converts the tag name 105 into the short tag name 115, for example, converts “quotation request information” into “A”.
[0040]
  In step ST38, the syntax element analysis unit 64 checks whether or not the content model 204 “(...)” Is included in the extracted element type declaration 202. If there is no content model 204, for example, FIG. In the case of “<! ELEMENT estimate request date EMPTY>” in the element type declaration 202, the processing after step ST34 is performed.
[0041]
  In step ST38, if the content model 204 is present, in step ST39, the syntax element analysis unit 64 checks whether the content model 204 has a system definition 205. If the system definition 205 is present, for example, If “<! ELEMENT estimate request number (#PCDATA)>” in the element type declaration 202 in FIG. 8, the processing after step ST34 is performed.
[0042]
  If there is no system definition 205 in step ST39, for example, if it is “<! ELEMENT estimate request information (estimate request number estimate request date quantity product number)>” of the element type declaration 202 of FIG. In step ST40, the syntax element conversion unit 65 searches the tag name memory 61 using the tag name 105 in the content model 204, extracts the short tag name 115 corresponding to the tag name 105, for example, “quotation request number” "B", "C" corresponding to "Quotation request date", "D" corresponding to "Quantity", and "E" corresponding to "Product number" are extracted, and the syntax element conversion unit 65 , Tag name 105 is converted to abbreviated tag name 115, for example, “quotation request number” is “B”, “quotation request date” is “C”, “quantity” is “D”, and “product number” is “E”. To Processes after step ST34 are performed.
[0043]
  If the extracted syntax element 108 is the attribute list declaration 203 in step ST33, for example, if it is “<! ATTLIST estimate request date year CDATA month CDATA date CDATA)>” shown in FIG. The syntax element conversion unit 65 searches the attribute name memory 62 by using the tag name 105 and the attribute name 106 in the attribute list declaration 203, and shortens the tag name 115 and the shortened attribute corresponding to the tag name 105 and the attribute name 106. The name 116 is extracted, for example, “C” corresponding to “estimation request date”, “C1, C2, C3” corresponding to “year, month, day” are extracted, and the syntax element conversion unit 65 selects the tag name 105 is converted to an abbreviated tag name 115, and attribute name 106 is converted to an abbreviated attribute name 116. Is converted to "C1, C2, C3", it performs the steps ST34 and subsequent steps.
[0044]
  FIG. 10 is a flowchart showing the conversion process to the short tag name 115 in steps ST37 and ST40 shown in FIG. In step ST51, the syntax element conversion unit 65 searches the tag name memory 61 based on the tag name 105 in the element type declaration 202. In step ST52, the syntax element conversion unit 65 converts the tag name memory 61 into the tag name memory 61. It is checked whether the tag name 105 is stored.
[0045]
  If the tag name 105 to be converted is not stored in the tag name memory 61 in step ST52, the abbreviated tag name generation unit 66 converts in accordance with an instruction from the syntax element conversion unit 65 in step ST53. Tag name 105 and the short tag name 115 corresponding to the tag name 105 are generated. In step ST54, the short tag name generation unit 66 generates the generated tag name 105 and the short tag name 115 corresponding to the tag name 105. Is stored in the tag name memory 61.
[0046]
  In step ST55, the syntax element conversion unit 65 converts the tag name 105 into the short tag name 115 generated by the short tag name generation unit 66. If the tag name 105 to be converted is stored in the tag name memory 61 in step ST52, the process of step ST55 is performed.
[0047]
  FIG. 11 is a flowchart showing the conversion process of the short tag name 115 and the short attribute name 116 in step ST41 shown in FIG. In step ST61, the syntax element conversion unit 65 searches the attribute name memory 62 using the tag name 105 and the attribute name 106 in the attribute list declaration 203. In step ST62, the syntax element conversion unit 65 searches for the attribute name memory 62. It is checked whether the tag name 105 and the attribute name 106 to be converted are stored.
[0048]
  If the tag name 105 and the attribute name 106 to be converted are not stored in the attribute name memory 62 in step ST62, the short attribute name generation unit 67 instructs the syntax element conversion unit 65 in step ST63. Thus, the tag name 105 and attribute name 106 to be converted, and the abbreviated tag name 115 and the abbreviated attribute name 116 corresponding to the tag name 105 and the attribute name 106 are generated. In step ST64, the abbreviated attribute name generation unit 67 The generated tag name 105 and attribute name 106, and the short tag name 115 and short attribute name 116 corresponding to the tag name 105 and attribute name 106 are stored in the attribute name memory 62.
[0049]
  In step ST65, the syntax element conversion unit 65 converts the tag name 105 and the attribute name 106 into the short tag name 115 and the short attribute name 116 generated by the short tag name generation unit 66. If the tag name 105 and the attribute name 106 to be converted are stored in the attribute name memory 62 in step ST62, the process of step ST65 is performed.
[0050]
  FIG. 12 is a diagram showing the abbreviated document type definition 8 converted by the document type definition conversion device 6. The tag name 105 and the attribute name 106 are the abbreviated tag name 115 and the abbreviated attribute for the document type definition 7 of FIG. 8. It is converted into the name 116, and a comment 201a is added. The shortened document type definition 8 shown in FIG. 12 is not used for individual data transmission in EDI or the like, but is used to check whether there is an error in the shortened document type definition matching document 3 in the first embodiment.
[0051]
  In this way, by generating the short tag name 115 and the short attribute name 116 corresponding to the tag name 105 and the attribute name 106 from the document type definition 7, the tag name correspondence table 4 and the attribute name correspondence table 5 are automatically generated. By generating, updating and storing in the tag name memory 11 and the attribute name memory 12 of the first embodiment, the shortened document type definition matching document 3 used for individual data transmission in actual EDI or the like can be created. it can.
[0052]
  As described above, according to the second embodiment, since the document type definition 7 can be automatically converted into the shortened document type definition 8, the shortened document type definition matching used for individual data transmission in actual EDI or the like is performed. There is an effect that it is possible to collate whether there is an error in the document 3.
[0053]
  Further, according to the second embodiment, from the document type definition 7, the short tag name generation unit 66 and the short attribute name generation unit 67 perform the short tag name 115 and the short attribute name corresponding to the tag name 105 and the attribute name 106. By generating 116, the tag name correspondence table 4 and the attribute name correspondence table 5 can be automatically created and updated. Therefore, the shortened document type definition matching document 3 used for individual data transmission in actual EDI or the like is created. The tag name correspondence table 4 and the attribute name correspondence table 5 can be efficiently generated.
[0054]
【The invention's effect】
  As described above, according to the present invention, when the syntax element conversion unit includes a tag name in the syntax element, the syntax element conversion unit searches the tag name memory and converts the tag name to the short tag name. If a tag name with an attribute name added is included, the document type definition is automatically determined by searching the attribute name memory and converting the tag name and attribute name to the short tag name and short attribute name. Therefore, there is an effect that it is possible to collate whether there is an error in the shortened document type definition matching document used for individual data transmission.
  When the searched tag name is not stored in the tag name memory when the syntax element conversion unit searches the tag name memory, a short tag name corresponding to the tag name is generated and stored in the tag name memory. As a result, the tag name correspondence table can be automatically generated and updated, and the tag name correspondence table can be efficiently generated when creating a short document type definition matching document used for individual data transmission. There is.
  Furthermore, when the syntax element conversion unit searches the attribute name memory and the searched tag name and attribute name are not stored in the attribute name memory, it corresponds to the short tag name corresponding to the tag name and the attribute name. By creating a short attribute name and storing it in the above attribute name memory, the attribute name correspondence table can be automatically created and updated, so attributes when creating a short document type definition consistent document used for individual data transmission There is an effect that the name correspondence table can be generated efficiently.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a document conversion apparatus according to Embodiment 1 of the present invention.
FIG. 2 is a diagram illustrating an example of a document type definition matching document used in EDI or the like.
FIG. 3 is a diagram showing a tag name correspondence table according to Embodiment 1 of the present invention.
FIG. 4 shows an attribute name correspondence table according to the first embodiment of the present invention.
FIG. 5 is a flowchart showing processing of the document conversion apparatus according to Embodiment 1 of the present invention.
FIG. 6 is a diagram showing an example of a shortened document type definition matching document according to the first embodiment of the present invention.
FIG. 7 is a diagram showing a configuration of a document type definition conversion apparatus according to Embodiment 2 of the present invention.
FIG. 8 is a diagram illustrating an example of a document type definition used in EDI or the like.
FIG. 9 is a flowchart showing processing of the document type definition conversion apparatus according to the second embodiment of the present invention.
FIG. 10 is a flowchart showing processing of the document type definition conversion apparatus according to the second embodiment of the present invention.
FIG. 11 is a flowchart showing processing of the document type definition conversion apparatus according to the second embodiment of the present invention.
FIG. 12 is a diagram showing an example of a shortened document type definition according to the second embodiment of the present invention.
[Explanation of symbols]
  1 Document conversion device, 2 Document type definition consistent document, 3 Short document type definition consistent document, 4 Tag name correspondence table, 5 Attribute name correspondence table, 6 Document type definition conversion device, 7 Document type definition, 8 Short document type definition, 11, 61 Tag name memory, 12, 62 Attribute name memory, 13, 63 Syntax element extraction unit, 14, 64 Syntax element analysis unit, 15, 65 Syntax element conversion unit, 16, 68 Output unit.

Claims (2)

A syntax element extractor that extracts syntax elements from a document type definition that defines the structure of the document;
A syntax element analysis unit for analyzing the syntax element extracted by the syntax element extraction unit;
A tag name memory for storing, as a tag name correspondence table, a shortened tag name corresponding to a tag name indicating the content of the character string included in the syntax element;
An attribute name memory storing the short tag name and short attribute name corresponding to the tag name and the attribute name attached to the tag name as an attribute name correspondence table;
When the tag name is included in the syntax element analyzed by the syntax element analysis unit, the tag name memory is searched to convert the tag name to the short tag name, and the syntax element analysis unit When the analyzed syntax element includes a tag name to which the attribute name is added, the attribute name memory is searched and the tag name and the attribute name are converted into the short tag name and the short attribute name. A syntax element converter to convert;
An output unit that combines the syntax element formed by the short tag name and the short attribute name converted by the syntax element conversion unit and outputs the combined short element name as a short document type definition;
When the syntax element conversion unit searches the tag name memory and the searched tag name is not stored in the tag name memory, a short tag name corresponding to the tag name is generated and stored in the tag name memory. Store and
When the syntax element conversion unit searches the attribute name memory and the searched tag name and attribute name are not stored in the attribute name memory, it corresponds to the short tag name corresponding to the tag name and the attribute name. A document type definition conversion apparatus characterized in that a short attribute name to be generated is generated and stored in the attribute name memory . The syntax element analysis section is a comment without a tag name, an element type declaration composed of a tag name without an attribute name, or a tag with an attribute name added to the extracted component 2. The document type definition conversion apparatus according to claim 1 , wherein whether or not the attribute list type declaration is constituted by a name is analyzed.

Images