JP2002259194A - Document data encoding method and system - Google Patents

Abstract

(57) Abstract: A document data encoding method and system capable of encoding an extensible text description language and performing document processing without decoding encoded data into document data. provide. An encoding step of encoding document data described in an extensible text format description language using a conversion table described in an extensible text format description language, and using the conversion table. The conversion table defines link information of another conversion table, and can be specified for an element name, an element value of the element name, and the element name. And a code length and a code assigned to the item of the attribute name, the attribute value of the attribute name, and a code length and a code indicating the parent-child relationship between the first element name and the second element name. is there.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a method and system for encoding document data.

[0002]

2. Description of the Related Art Conventionally, there is a method of encoding and decoding document data in order to reduce the amount of data to be transmitted.
To realize this method, each of the transmitting device and the receiving device needs to have a conversion table. The conversion table associates the description language with the code data on a one-to-one basis. The transmitting device encodes the document data into encoded data based on the conversion table. On the other hand, the receiving device decodes the code data into document data based on the conversion table.

[0003] Such a method is particularly effective for the Internet. For example, if the web server uses HTML (HyperText
It transmits coded data obtained by encoding document data described in a text markup language such as Markup Language. On the other hand, the client decodes the received encoded data into document data, and displays the document data on the browser. At this time, by transmitting the document data as coded data, the amount of transmitted data can be reduced.

[0004] Encoding document data on the Internet is also effective from the viewpoint of security. This is because a client having no conversion table cannot decode the code data.

FIG. 1 shows a conventional document data encoding and decoding method. According to FIG. 1, document data 12 in HTML format is encoded 10 using a conversion table 11.
On the other hand, the code data is decoded 20 using the conversion table 21. Thereby, the document data 22 in the HTML format is restored. Further, the document data 22 is analyzed by the parser 23 for the logical structure of the element, and is displayed using the browser 24. According to FIG. 1, a conversion table 11 used in encoding and a conversion table 21 used in decoding
Must be the same table.

[0006]

However, in recent years, document data transmitted by a Web server is extensible text that not only defines the display of information like HTML but also can define the structure of information. There are more formal marking languages. This language is, for example, XML (eXtens
ible Markup Language) or SGML (Standard Generalized)
Markup Language).

For example, according to the conventional encoding and decoding method as shown in FIG. 1, when the document data is extended, the conversion table must be extended.

Further, since the markup language defines the logical structure of elements, it is necessary to always decode code data into document data and analyze and process the logical structure of the document data with a parser.

Therefore, the present invention provides a document data encoding method and system capable of encoding an extensible text description language and performing document processing without decoding encoded data into document data. The purpose is to provide.

[0010]

According to the code processing method of the present invention, a document described in an extensible text format description language using a conversion table described in an extensible text format description language. An encoding step of encoding data into encoded data, and a document processing step of performing document processing of encoded data as document data using a conversion table, wherein the conversion table defines link information of another conversion table. , An element name, an element value of the element name, an attribute name that can be specified for the element name, a code length and a code assigned to the item of the attribute value of the attribute name, The element name 2 defines a code length and a code indicating a logical structure having a parent-child relationship.

[0011] Thus, since the conversion table itself can be expanded, it is possible to cope with expandable document data. Further, since the logical structure can be included in the code data by the conversion table, the document processing can be directly performed without decoding and parsing the document data. Such an effect has an effect that a processing load is small for a receiving device having only a low processing capability, such as a mobile phone.

According to another embodiment of the encoding processing method of the present invention, the items defined in the conversion table used in the document processing step are the subsets of the items defined in the conversion table used in the encoding step. May be in a relationship.

For example, it is assumed that one receiving device has only a certain portion of the conversion table, and the other receiving device has only another portion of the conversion table. Then, the transmitting device distributes encoded data obtained by encoding one document data to a plurality of receiving devices. As a result, only one portion of the document data is displayed on one receiving device, and only the other portion of the document data is displayed on the other receiving device. Even if the code data to be distributed is the same, the display processed by the document is different depending on the conversion table possessed by the receiving device. Such a function is effective also from the viewpoint of security.

According to another embodiment of the encoding method of the present invention, the encoding step includes adding, to the document data, an element name, an element value which does not exist in the conversion table and another conversion table linked to the conversion table, When there is an attribute name and an attribute value, it is preferable that the element name, the element value, the attribute name, and the attribute value are not encoded.

This makes it possible to avoid that the entire document data cannot be encoded because a part of the document data cannot be encoded.

According to another embodiment of the code processing method of the present invention, the encoding step adds an occupied data length of a portion encoded using the conversion table to a code designating the conversion table, and Add the occupied data length of the part occupied by the element name to the sign of the element name, add the occupied data length of the part occupied by the element value to the sign of the element value, and / or add the occupied data length occupied by the attribute name. In addition to the code of the attribute name, the document processing step includes, when a code not defined in the conversion table exists in the code data, the code data at a position where the occupied data length is skipped without performing the document processing on the code. It is also preferable to perform document processing from.

This makes it possible to skip portions of the code data that are not subjected to document processing.

According to the code processing system of the present invention, a server that transmits document data described in an extensible text format description language, and encodes the received document data into code data using a conversion table. An encoding server;
A client having means for processing the received coded data by using the conversion table, and the conversion table is described in an extensible text format description language, and defines link information of other conversion tables. And an element name, an element value of the element name, an attribute name that can be specified for the element name, a code length and a code assigned to the attribute value of the attribute name, and a second element for the first element name. Defines a code length and a code indicating a logical structure having a parent-child relationship.

Thus, the existing server can be used as it is.

According to another embodiment of the code processing system of the present invention, the items defined in the conversion table used in the encoding server are related to a subset of the items defined in the conversion table used in the client. It is also preferred.

According to another embodiment of the code processing system of the present invention, the encoding server stores, in the document data, another conversion table not defined in the conversion table, an element name, an element value, an attribute name, and an attribute value. It is also preferable that the element name, the element value, the attribute name and the attribute value are not coded when.

According to another embodiment of the code processing system of the present invention, the coding server adds an occupied data length of a portion coded using the conversion table to a code indicating the conversion table, and Adds the occupied data length of the portion occupied by to the code of each item, and if a code not defined in the conversion table is present in the code data, the client does not process the code and performs a document processing on the occupied data length. It is also preferable to perform the document processing from the code data at the position where is skipped.

[0023]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 2 shows a document data encoding method according to the present invention. According to FIG. 2, the document data 12 is extended by a plurality of document data 120 and 121. On the other hand, the conversion table 11 also defines link information of a plurality of conversion tables 110 and 111 corresponding to the extended document data. Thus, the document data 12 in the XML format is encoded 10 using the conversion table 11.

According to FIG. 2, the code data is directly subjected to document processing 30 using the conversion table 21 and displayed on the browser 24. According to the present invention, the code data also includes the logical structure of the element. Therefore, there is no need to decode the document data, and there is no need to analyze the logical structure by the parser 23.

FIG. 3 shows a sample of document data. FIG. 4 shows encoded data obtained by encoding the document data shown in FIG. 5A to 5D are conversion tables of the document data in FIG. In the following, referring to FIGS. 3 and 4, FIGS.
The conversion table of d will be described.

The conversion table is described in XML,
It is divided into a header part <head> (1) in FIG. 5A and a body part <body> (8) in FIGS. 5B to 5C. The header part describes the prefix. In the body part, the logical structure of the document and the conversion code are described.

According to FIG. 5A, 2 bits are assigned to the header portion as the code length (2) of the prefix. As a prefix, a code “00” (3) is assigned to the element name and the attribute name. If the contents of the element value and the attribute value are numerical values, the code “01” (4) is assigned, and if the content is a character string, the code “10” (5) is assigned.

Further, since the element name SVG is defined in FIG. 3, according to FIG. 5A, 3 bit “0” is added to the start of the element name “SVG”.
00 "(6) is assigned, and 3 bits" 011 "(7) are assigned at the end.

FIG. 5B shows that the element name SVG is first defined below (9). Also, this element name SVG
It is defined that a 2-bit code length is assigned to the attribute name attached to (10). The code "10" is assigned to the attribute name width (11), and the code "11" is assigned to the attribute name height (13).
The attribute value of the attribute name width is represented by an unsigned integer 10 bits (12), and the attribute value of the attribute name height is also an unsigned integer 10 bi.
It is represented by t (14).

Next, it is defined that elements having a child relationship of the element name SVG are represented by a code length of 3 bits (15). And the element name SV
Define element name rect as a child element of G (16). Element name rec
The sign "001" is assigned to the start of t and the sign "0" is assigned to the end.
11 "is assigned (17). Also, an element name text is defined as a child element of the element name SVG (18). The code" 010 "is assigned to the start of the element name text and the code" 011 "is added to the end. Is assigned (19).

FIG. 5C shows that the element name rect is defined below (20). Also, this element name re
Assign a code length of 3 bits to the attribute name attached to ct (21)
Define that. Assign a code "100" to the attribute name x (2
2), the attribute value of attribute name x is represented by a signed integer 10 bits (2
3). Also, a code "101" is assigned to the attribute name y (24), and the attribute value of the attribute name y is represented by a signed integer 10 bits (25). The attribute name width is assigned a code "110" (26), and the attribute name wi is assigned.
The attribute value of dth is represented by an unsigned integer 10 bits (27). Finally, a code "111" is assigned to the attribute name height (28), and the attribute value of the attribute name width is represented by an unsigned integer 10 bits (29).

FIG. 5D shows that the element name text is defined as follows (30). Also, this element name te
Assign 2 bit code length to attribute name attached to xt (31)
Define that. Assign a code "10" to the attribute name x (3
2), the attribute value of attribute name x is represented by a signed integer 10 bits (3
3). Further, a code "11" is assigned to the attribute name y (34), and the attribute value of the attribute name y is represented by a signed integer 10 bits (35).

Next, the element value of the element text is defined below.
(36) is shown. Here, it indicates that the element value is in the Shift-JIS format (37).

FIG. 6 is an example of a conversion table defining link information of a plurality of conversion tables. The description language targeted by the present invention is an extensible text format description language. Therefore, just as the document data is extended,
The translation table also needs to be extended. According to FIG. 6, it is only necessary to define link information of a plurality of conversion tables in the header part, and there is no need to recreate the conversion tables. In the header part, meta information for extending a plurality of conversion tables is defined. The meta information is the code / code length of the prefix code, the designation of the element, the designation of the namespace, and the link information to the conversion table.

FIG. 7 shows the occupied data length occupied by the element.
This is embedded in the code data of FIG. Thus, when a code that is not defined in the conversion table owned by the code data exists in the code data, the client that performs the document processing does not perform the document processing on the code, and performs the document processing from the code data at the position where the occupied data length is skipped. can do.

FIG. 8 is a system configuration diagram of the first embodiment of the present invention. According to FIG. 8, the server 4 transmits the conversion table to the clients A and B in advance. In this case, the conversion tables a and b which are a subset of the items of the conversion table possessed by the server 4 are transmitted. After that, the server 4 transmits the encoded data obtained by encoding the document data to the clients A and B. Each of the clients A and B receiving the code data performs document processing, but the information actually displayed on the browser can be different.

FIG. 9 is a system configuration diagram including the encoding server 6. The server 4 transmits the XML document data to the encoding server 6. The encoding server 6 encodes the document data using the conversion table received from the conversion table server 7. The code data is transmitted to the client 5. The client 5 performs document processing using the conversion table received from the conversion table server 7. According to FIG. 9, the encoding server can be used as a proxy server without changing an existing server that transmits XML-format document data.

FIG. 10 is a flowchart of the document processing. For example, a description will be given of a document process in which the code data of FIG. 4 is performed based on the conversion table of FIG.

(S1) Conversion table <head><prefix bit
According to = "2">, since the header code length is 2 bits, 2 bits are read from the code data. Since it is "00" according to FIG. 4, it is determined that it is a code indicating "name". (S2) Next, the conversion table <head><root name = "svg" b
According to it = "3" code = "000"/>, it is the root element "svg" and reads the next 3 bits. Since the sign is "000", it is interpreted as the start of the element svg. (S3) A header code length of 2 bits is read from the code data. (S4) According to FIG. 4, it is "00", and <hea
It is determined that “00” is a code indicating “name” from d>. (S5) Code length of attribute name <attlist bit = 2>, code length of child element name <children bit = 3>, end tag <end name = "/ svg" b
It reads only 2 bits for the shortest code length in it = 3 code = "011"/>. (S6) According to FIG. 4, since it is "10", it is confirmed that it matches the attribute name width. (S7) If they do not match, the next shorter code length
Read 3 bits and return to S6 again. (S8) Since it matches "10", it is interpreted as the attribute name width. (S9) The next 3 bits are the end tag <end name = "/ svg" bit = 3
Check that code = "011"/> is not set. If it is an end tag, the process ends. If it is not an end tag, the process returns to S3.

(S3) Code length of header from code data "
2 "bits are read. (S4) According to FIG. 4, it is" 01 ", and the conversion table <head>
According to <number_prefix code = "01"/>, it is determined that "01" is a code indicating "numerical value". (S10) Conversion table <number bit = "10" data = "UI" q
According to t = "1"/>, since the attribute value of the attribute name width is an unsigned integer of 10 bits, 10 bits are read. (S11) Since it is "0111110100", it is interpreted as the attribute value "500". Then, the process returns to S3 again.

As described above, by repeating the flowchart of FIG. 10, it becomes possible to directly perform document processing without decoding the code data.

According to the above-described various embodiments of the document data encoding method and system of the present invention, various changes, corrections, and omissions in the technical idea and scope of the present invention can be made.
Those skilled in the art can easily carry out the above. The foregoing description is merely an example, and is not intended to be limiting. The invention is limited only as defined by the following claims and equivalents thereof.

[0044]

As described in detail above, according to the present invention, it is possible to encode document data described in an extensible text format description language. Since such encoding can reduce the amount of data transmission,
This is effective for a communication system with a low transmission speed such as wireless.

Further, according to the present invention, the document data described in the extensible text format can be simply replaced with the conversion table without changing the encoding device.
Encoding suitable for each document data can be performed. Further, even when the document data is extended, the encoding table for the original document data is not changed, and encoding suitable for the extended document data is performed only by preparing an encoding table for only the extended portion. be able to.

Further, according to the present invention, by mounting the document-specific processing engine on the decoding-side device, it is not necessary to restore the original document data from the received encoded data, and the processing load on the decoding-side device is small. effective.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram of a conventional basic encoding and decoding method.

FIG. 2 is an explanatory diagram of a code document processing method according to the present invention.

FIG. 3 is a sample of XML format document data.

FIG. 4 is an example of code data of the document data of FIG. 3;

FIG. 5A is a conversion table for converting the document data of FIG. 3 into the code data of FIG. 4; Particularly, it is a table of a header portion.

FIG. 5B is a conversion table for converting the document data of FIG. 3 into the code data of FIG. 4; Especially the table of the root element.

5C is a conversion table for converting the document data of FIG. 3 into the code data of FIG. Particularly, it is a table of the first child element.

FIG. 5D is a conversion table for converting the document data of FIG. 3 into the code data of FIG. 4; Particularly, it is a table of the second child element.

FIG. 6 is a conversion table including link information of another conversion table.

FIG. 7 shows code data to which an occupation data length occupied by each element is added for each element.

FIG. 8 is a system configuration diagram of the first embodiment of the present invention.

FIG. 9 is a system configuration diagram of a second embodiment of the present invention.

FIG. 10 is a flowchart of document processing according to the present invention.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 10 Encoding 11, 21, 110, 111, 210, 211 Conversion table 12, 22, 120, 121 Text format document data 23 Parser 24 Browser display screen 30 Document processing 4 Existing server 5 Client 6 Code data 7 Conversion table Server 8 Internet

Claims (8)

[Claims] An encoding step of encoding document data described in an extensible text format description language into code data using a conversion table described in an extensible text format description language; A document processing step of performing document processing on the code data as the document data using a conversion table, wherein the conversion table defines link information of another conversion table, and includes an element name and an element of the element name. A value, an attribute name that can be specified for the element name, a code length and a code assigned to the item of the attribute value of the attribute name, and a second element name for the first element name.
A code length and a code indicating a logical structure having a parent-child relationship with the element name of the document data. 2. The method according to claim 1, wherein the items defined in the conversion table used in the document processing step are in a relationship of a subset of the items defined in the conversion table used in the encoding step. Code processing method for document data described in 1. 3. The encoding step, when the document data includes an element name, an element value, an attribute name, and an attribute value that do not exist in the conversion table and another conversion table linked to the conversion table. 3. The method according to claim 1, wherein the element name, the element value, the attribute name, and the attribute value are not encoded. 4. The encoding step adds an occupied data length of a portion encoded using the conversion table to a code indicating the conversion table, and adds an occupied data length of a portion occupied by each of the items. In the document processing step, when a code not defined in the conversion table exists in the code data, the position where the occupied data length is skipped without document processing the code. 4. The document data encoding method according to claim 1, wherein the document processing is performed from the encoded data. 5. A server for transmitting document data described in an extensible text format description language; an encoding server for encoding the received document data into encoded data using a conversion table; A client having means for processing the code data by using a conversion table, wherein the conversion table is described in an extensible text format description language and defines link information of another conversion table. And an element name, an element value of the element name, an attribute name that can be specified for the element name, a code length and a code assigned to the attribute value of the attribute name, and a second element for the first element name. Wherein the element name defines a code length and a code indicating a logical structure having a parent-child relationship. 6. The method according to claim 5, wherein the items defined in the conversion table used by the encoding server are in a relation of a subset of the items defined in the conversion table used by the client. Document data encoding system. 7. The encoding server according to claim 1, wherein the document data includes another conversion table, an element name, an element value, an attribute name, and an attribute value that are not defined in the conversion table. 7. The document data encoding system according to claim 5, wherein values, attribute names, and attribute values are not encoded. 8. The encoding server adds an occupied data length of a portion encoded using the conversion table to a code indicating the conversion table, and adds an occupied data length of a portion occupied by each of the items. In the case where a code that is not defined in the conversion table exists in the code data, the client does not perform a document process on the code and skips the occupied data length. 8. The document data encoding system according to claim 5, wherein document processing is performed from the data.