JP7011029B2 - Condensation of XML file - Google Patents

Description

XML (extensible markup language) is used to encode documents in a format that can be read by both machines and humans. XML-encoded documents often do nothing to the computer in their own right, but coupled with an application designed to interpret the XML document, the XML document gives the application specific functionality. It is possible to execute, display specific information, use a specific format, and so on. As a result, the XML standard has been developed to facilitate communication between applications and devices in a device-independent format. The standard can specify specific keywords or "tags" that trigger the execution of specific functions. Such functions can then be performed on the device and / or application in a manner suitable for the device and / or application.

Illustrative files and data structures for condensing XML files are shown. A flowchart of an exemplary process for condensing an XML file is shown. Another flowchart of the exemplary process for condensing an XML file is shown. An exemplary print container for the condensation of XML files is shown. Shown is an exemplary printer for condensing XML files. Another exemplary printer for XML file condensation is shown. Illustrative systems, methods, and exemplary printers capable of operating their equivalents are shown.

This application will be more fully understood with respect to the following detailed description given with reference to the accompanying drawings. Throughout the figure, similar symbols mean similar components.

Describes systems, methods, and their equivalents for condensing XML files. In various embodiments, it may be desirable to store the XML file on a device or item that does not have a large amount of available memory. Such items may be designed to be low cost, and therefore it is not practical to include a larger storage space without affecting the manufacturing cost of such items. For example, print containers (eg, ink cartridges) are mass market products, and the pricing of the print containers is highly competitive, so it is wasteful to employ memory resources that have more space than necessary. There can be unnecessarily expensive.

As a result, the XML file stored in the print container can be condensed to help reduce the memory impact of the XML file. It may take some time for the printer to decondense the file when the print container is installed on the printer, but this processing time is mostly associated with printing on the printer's machine. It is negligible in view of the fact that it revolves around moving parts. Although embodiments with a print container will be described, the techniques described herein can be used in other fields and / or applications.

Therefore, a method of condensing the XML file to store the XML file is disclosed. Ultimately, the XML file can be stored as a set of indexes on the XML file and a condensed version of the XML file. The index can be created by dividing the text of the XML file into three types of indexes (tags, attributes, and values). It is then possible to transform the XML file according to the index. The index and the condensed XML file can then be stored, for example, in a print container. When the print container is inserted into the printer, the printer uses the index to decondense the condensed XML file back into the original XML file, and the printer uses the XML file to decondense the XML. It is possible to execute the action described in the file.

FIG. 1 shows an exemplary file and data structure for the condensation of XML files. It will be appreciated that the items shown in FIG. 1 are exemplary embodiments, and that many different files, data structures, XML file condensation techniques, etc. can operate according to various embodiments. FIG. 1 shows XML file 100. The XML file 100 is shown as having 11 lines L00-L10. The XML file 100 shown here is composed of three element types: a tag, an attribute, and a value.

As used herein, a tag generally refers to an instruction that defines an action to be performed. In XML file 100, for example, <defaults>, <spit ... /> (spit), and <routines> (routines) are examples of tags. Tags can include other nested tags. XML file 100 shows two tag syntaxes. The <defaults> tag starts at line L00, ends at line L10 with the close tag </ defaults>, and the <spit ... /> tag starts and ends at the same line. .. In this example, each tag is shown on a different line for the sake of explanation, but it is possible to write multiple tags on the same line.

Tags can also contain attributes. “Mode”, “frequency” and “granularity” in XML file 100 are examples of attributes. As used herein, tag attributes can be used to specify parameters for unique actions triggered by the tag. Furthermore, it is possible to assign a value to the attribute. In XML file 100, "1", "normal" and "thermal_mode" are examples of values. As used herein, the value can be used with respect to an attribute to specify a parameter for a unique action triggered by the tag that the attribute qualifies. For example, the <wiper-action ... /> tag (wiper-action) has a "speed" attribute set to the value "1". Thus, by using the "speed" attribute with the <wiper-action ... /> tag, you can make the behavior of the action associated with the <wiper-action ... /> tag a particular aspect. It will be possible. For example, the <wiper-action ... /> tag can turn on the wiper associated with the printer, and the "speed" attribute is the speed at which the wiper is activated (in this case "1"). Can be used to define.

In order to facilitate the particular condensation and compression techniques described above, it may be desirable for the XML file 100 to have a particular set of known syntax. This set of syntax can be a subset of the possible XML syntax. For example, XML can support values that contain space characters, but it may be desirable for values in XML file 100 to use underscores or dashes instead of space characters (eg, in line L03). Value "thermal_mode", value "action-defaults" in line L02 (default behavior). Condensation of XML File 100 by using a subset of constructs to ensure that there are no conflicts due to condensing two phrases with two different constructs into the same condensed phrase. , Compression, decompression, and decondensation can be performed more easily and / or more efficiently.

As mentioned above, it may be desirable to store the XML file 100 in a condensed format. The illustrated XML file 100 can be unreasonably short for condensation, but for longer XML files with more detailed instructions containing more iterations of tags, attributes, and values, condensation is desirable. There is. To condense the XML file 100, it is possible to first create an index 110. This can be achieved by identifying the tags, attributes, and values in XML file 100 and separating them into separate categories. Here, the XML file 100 contains 8 tags, 5 attributes, and 6 values. In various embodiments, it may be desirable to further sort the tags, attributes and values to help condense and / or later compress the XML file 100. Here, the tags, attributes, and values are sorted first by the frequency of those terms and then alphabetically. For example, the attribute "mode" appears in rows L03 and L09, and the attribute "frequency" appears only in rows L03. Similarly, the tag <defaults> appears in lines L00, L10, and the tag <progress ... /> (progress) appears only in line L08.

We have shown one way to index tags, attributes, and values, but other methods can be used instead. For example, in index 110, tags, attributes, and values all use index numbers 1-8 in the same range. In another embodiment, it is possible to optionally design the index so that tags, attributes, and values are each assigned a unique index range. Other index assignments may be appropriate.

Once the index 110 is created, it is possible to initiate encoding of the index into the encoded index 115 and the condensation of the XML file 100 into the condensed XML file 120. FIG. 1 shows one possible version of the encoded index 115. Items enclosed in square brackets are capable of representing a special identifier within the encoded index 115 used to indicate the separation between the plurality of components of the index 110. In one embodiment, the separator indicating the separation can be, for example, characters such as spaces, punctuation marks, combinations, and known values. In the exemplary encoded index 115, there are five separators: [tag_start] to indicate the start of the tag index, [attribute_start] (attribute start) to indicate the start of the attribute index, and the start of the value index. The [value_start] to indicate, the [separator] to indicate the separation between the components of index 110, and the [index_end] to indicate the end of the encoded index 115 are used. If the encoded index 115 and the condensed XML file 120 are stored as a single item, the separator [index_end] can also indicate the start of the condensed XML file 120. Furthermore, some of the separators can be represented by the same special identifier.

As mentioned above, in the illustrated exemplary index 110, the tags, attributes, and values each use the same index range, the index range starting with a known value. Therefore, the encoded index 115 does not need to identify the index values of the tags, attributes, and keys within the encoded index 115. Alternatively, this information can be reconstructed as part of the process of decondensing the condensed XML file 120. In embodiments where various indexes are assigned to tags, attributes, and values, the information can also be stored within the encoded index 115.

It is possible to transform XML file 100 according to index 110 to create condensed XML file 120. Here, the XML file 100 is transformed so that each pair of characters (eg, "T2") in the condensed XML file 120 corresponds to a particular tag, attribute, or value of the XML file 100. This correspondence can be understood by examining the index 110. Specifically, the first <defaults> tag is identified as having index 2 at index 110. Therefore, the first T2 in the condensed XML file 120 corresponds to the first <defaults> tag in the XML file 100. This is because the T2 is the tag number 2 (indicated by T) at the index 110. Similarly, the phrase <spit frequency = "6000" mode = "thermal_mode" /> from line L03 of XML file 100 spans the first and second lines of condensed XML file 120 "T7 A2 V2 A1 V6 TE". Corresponds to the part that can be read. The condensed XML file 120 and the encoded index 115 may have more or less characters depending on the mode in which such item is created, including additional symbols that can serve a variety of purposes. It is worth keeping in mind that it is possible.

This exemplary version of the condensed XML file 120 uses a special symbol to indicate the end of the tag. This symbol, represented as "TE", is used to indicate to the application interpreting the condensed XML file 120 that the most recently opened tag should be closed here. For example, the last "TE" in the condensed XML file 120 corresponds to closing the </ defaults> tag on line L10 of XML file 100. In various embodiments, the use of TE tags is desirable because the more character iterations there are, the more efficient the compression of a particular form. This is also the reason for sorting the tag indexes by the frequency of terms, because the higher the usage rate of the same index, the more the compression efficiency can be improved.

As a result, the XML file 100 is condensed into an encoded index 115 and a condensed XML file 120 (the combination thereof is referred to as a converted file), and the converted file uses compression techniques. This makes it possible to further reduce the size. Which compression technique to use depends on how the encoded index 115 and the condensed XML file 120 are created, which is designed so that the creation of those items is optimal for a particular data compression technique. Because it is possible to do.

Whether or not the converted file is further compressed, the converted file is then stored in the memory of the item with which the XML file 100 is associated. One exemplary item in which condensation of this type of XML file 100 may be desirable is a print container containing a source of print material. The print material and / or print container can be designed to work with a particular type of printer. The printer can be a two-dimensional printer, such as a desktop printer designed for home or office use, an industrial scale printer capable of outputting thousands of items per hour, and the like. The printer can also be a three-dimensional printer. As mentioned above, those techniques involving the condensation of XML files can also be applied outside the printing industry.

Depending on the type of printer associated with the print container, the print material can include inks, toners, cleaning fluids, modeling materials for 3D printers, and the like. Therefore, in this embodiment, the XML file 100 can include instructions for the printer to which the print container is attached. Such instructions can instruct the printer how to operate efficiently using the print material. Accordingly, such instructions can relate to cleaning the printer, providing other services to the printer, printing with printing materials, and the like. In this way, it is possible to convey other information (eg, security information, general update information) to the printer.

When the print container is installed in the printer, the printer removes the converted file from the memory of the print container, decondenses the converted file, and returns it to the XML file 100. The method by which the file is decompressed depends on the compression technique used. Decondensing the converted file can be performed in the reverse order of creating the condensed XML file. Since the syntax is limited to a set of known syntaxes, XML file 100 is rewritten by filling in the syntax based on the specific order of tags, attributes, and values in the condensed XML file 120. It is possible to create. After decondensing the converted file into XML file 100, the printer then uses the instructions to perform the functions described by the XML file 100 (eg, cleaning the printer, servicing the printer). It is possible to print using the materials provided in the print container.

In some embodiments, after decompressing and decondensing the converted file and returning it to XML file 100, the printer can combine the instructions from the XML file 100 with a set of stored instructions. be. Such stored instructions shall be a set of default instructions that can be used by the printer, regardless of which print material is incorporated, unless overridden by instructions from an XML file such as XML file 100. It is possible.

It will be appreciated that the following description provides a number of specific details to provide a complete understanding of this embodiment. However, it will be appreciated that this example can be practiced without limitation to such particular details. In some embodiments, the method and structure will not be described in detail in order to avoid unnecessarily obscuring the description of the embodiment. Moreover, such a plurality of embodiments can be used in combination with each other.

As used herein, a "module" is hardware, firmware, software stored on a computer-readable medium, or software running on a machine, and / or a combination thereof, one or more. Includes, but is not limited to, the combination for performing a function or one or more actions of, and / or producing a function or operation from another module, method, and / or system. Modules can include software controlled microprocessors, discrete modules, analog circuits, digital circuits, programmed module devices, memory devices containing instructions, and the like. Modules can include gates, combinations of multiple gates, or other circuit elements. When describing a plurality of logic modules, it is possible to incorporate the plurality of logic modules into one physical module. Similarly, when describing a single logical module, it is possible to distribute the single logical module among a plurality of physical modules.

FIG. 2 shows an exemplary method 200 related to the condensation of XML files. Method 200 can be implemented on a non-transitory computer-readable medium that stores instructions that can be executed by the processor. The instruction can cause the processor to perform method 200 when executed by the processor. In another embodiment, the method 200 can reside within a logic gate and / or RAM of an application-specific integrated circuit.

Method 200 involves generating an index from an XML file in action 210. In various embodiments, the XML file can contain instructions that control the operation of the printer. The XML file can contain instructions that control the operation of the printer based on the type of printing material stored in the printing material container (eg, ink cartridge). For example, different materials may affect printer components in different ways, creating different maintenance needs for such components. Therefore, the XML file associated with the print container that stores a particular print material can control the printer to perform various functions suitable for that particular print material (including maintenance functions). .. The XML file may also contain other instructions related to, for example, printer cleaning, printer services, printing with printing materials, and the like.

A set of indexes can include several indexes, including a tag index, an attribute index, and a value index. The tag index can index the terms of the tags used in the XML file. Attribute indexes can index attribute terms in XML files. A value index can index a term of a value in an XML file. In some embodiments, the terms in the tag index, attribute index, and value index can be ordered in their respective indexes according to the frequency of those terms in the XML file. It may be desirable to order the indexes according to the frequency of the terms, as certain compression techniques achieve higher compression ratios as more terms are repeated. Therefore, when the range of indexes overlaps, repeated use of those indexes contributes to the realization of a higher compression ratio.

In various embodiments, the XML file can contain instructions that control the operation of the printer. The XML file can contain instructions that control the operation of the printer based on the type of printing material stored in the printing material container (eg, ink cartridge). For example, different materials can affect printer components in different ways, creating different maintenance needs for such components. Therefore, the XML file associated with the print container that stores a particular print material can control the printer to perform various functions suitable for that particular print material (including maintenance functions). .. The XML file may also contain other instructions related to, for example, printer cleaning, printer services, printing with printing materials, and the like.

Method 200 also includes, in action 220, condensing the XML file into a condensed version of the XML file. The condensed version of the XML file can be condensed by transforming the XML file according to the index. In some embodiments, the XML file contains a known subset of XML syntax to facilitate indexing in action 210, condensation of the XML file in action 220, and possible decondensation of the XML file later. It is possible to use it. Such a syntax can be preselected, for example, for any two different XML statements so that the two such statements in a condensed version are different. Similarly, the syntax can be selected so that for any given two different condensed statements, the decondensed version of such statement is also different.

Method 200 also involves generating a converted file. The converted file can consist of a set of indexes created by action 210 and a condensed version of the XML file created by action 220. For example, it is possible to concatenate the index and the condensed version of the XML file into a single file to create the converted file.

FIG. 3 shows method 300 for condensing XML files. Method 300 includes several actions similar to those described above for Method 200 (FIG. 2). For example, method 300 generates a set of indexes from an XML file in action 310, condenses the XML file into a condensed version of the XML file in action 320, and in action 330 the set of indexes and said condensation. Includes generating a converted file, including a version of the XML file.

Method 300 also includes compressing the converted file in action 340. The compression of the converted file can further reduce the total file size of the converted file. Method 300 also includes storing the converted file in memory in action 350. In an embodiment where the XML file contains instructions that control the operation of the printer in relation to the printing material, the converted file can be stored in the memory of the printing material container that holds the source of the printing material. .. This makes it possible to specifically configure the printer to use various printing materials without storing such information in the printer itself. This is desirable, for example, when configuring the printer to use new printing materials, saving memory space in the printer, and so on.

FIG. 4 shows a print container 400 related to the condensation of XML files. The print container 400 includes a source of print material 410. The printing material 410 can be, for example, ink, a cleaning liquid, or the like. The print container 400 also includes a print material distributor 420. The print material distributor 420 can take many forms depending on how the printer into which the print container 400 is inserted is designed to work. For example, if the printer draws the print material from the print container 400 and ejects it onto a print medium elsewhere, the print material distributor 420 contacts the printer mechanism to draw the print material 410 from the print container 400. Is possible. Alternatively, if the print container is a cartridge designed to eject the print material 410 directly onto the print medium, the print material distributor 420 is capable of directly distributing the print material 410.

The print container also contains a memory 430. Memory 430 includes tag index 432. The tag index 432 can include a list of tag terms from the XML file. Tag terms can be organized according to the frequency of tag terms in the XML file. Memory 430 also includes attribute index 434. The attribute index 434 can contain a list of attribute terms from the XML file. The attribute terms can be organized within the attribute index 434 according to the frequency of the attribute terms in the XML file. Memory 430 also includes a value index 436. The value index 436 can include a list of terms of values from the XML file. The value terms can be organized within the value index 436 according to the frequency of the value terms in the XML file.

Memory 430 also contains condensed XML file 438. A condensed version of the XML file 438 can be created by transforming the XML file according to the tag index, attribute index, and value index. In some embodiments, the tag index 432, the attribute index 434, the value index 436, and the condensed XML file 438 can be stored in memory 430 in compressed format. In various embodiments, the printer into which the print container 400 is inserted can use the tag index, attribute index, value index, and condensed version of the XML file to recreate the XML file. As a result, the recreated XML file can control the operation of the printer in relation to one or more of the print material 410, the print container 400, the print material distributor 420, and the like.

FIG. 5 shows a printer 500 related to the condensation of XML files. The printer 500 includes a housing 510. The housing 510 is capable of receiving a print container 599 that has a source of print material. The printing material can be, for example, ink, toner, cleaning liquid, or the like.

The printer 500 also includes a communication module 520. Communication module 520 is capable of retrieving a set of indexes and condensed XML files from print container 599. The condensed XML file can be created from the set of indexes as well as the original XML file not stored on the print container 599. In various embodiments, the communication module 520 is capable of retrieving the set of indexes and condensed XML files from memory on the print container 599. As a result, in this embodiment, the housing 510 and the print container 599 may include suitable electronic connecting means to facilitate communication between the communication module 520 and the memory on the print container 599. It is possible.

The printer 500 also includes an extraction module 530. Extraction module 530 is capable of generating decondensed XML files. The decondensed XML file can be generated by transforming the condensed XML file according to a set of indexes.

The printer 500 also includes a control module 540. The control module 540 can control the operation of the printer 500 according to the instructions extracted from the decondensed XML file. In various embodiments, the control module 540 can control one or more of the cleaning of printer components, the service of printer components, printing using the printing material contained in the print container 599, and the like. Is.

FIG. 6 shows a printer 600 related to the condensation of XML files. The printer 600 includes several items similar to those described above for the printer 500. For example, the printer 600 includes a housing 610 that receives a print container 699 having a source of print material, a communication module 620, an extraction module 630, and a control module 640.

The printer 600 also includes a decompression module 650. The decompression module 650 is capable of decompressing a set of indexes and a condensed XML file. The decompression of the condensed XML file and the index is when those items are stored in the memory of the print container 699 in compressed form to further reduce the amount of data stored on the print container 699. It is possible to execute.

The printer 600 also includes a memory 660. The memory 660 can store a set of default instructions. As a result, the control module 640 can control the printer operation according to the instructions extracted from the decondensed XML file when the decondensed XML file modifies the default instructions. Become. As described above, the operation of the printer can be related to printer cleaning, printer service, printing using printing materials, and the like.

FIG. 7 shows an exemplary system and method as well as an exemplary computer on which its equivalents can operate. The exemplary computer can include components such as a processor 710 and memory 720 connected by bus 730. Computer 700 also includes an XML file condensing module 740. The XML file condensing module 740, alone or in combination with other components, is capable of performing the various functions described above with respect to the above exemplary systems, methods, devices and the like. In various embodiments, the XML file condensing module 740 is a non-temporary computer-readable medium containing processor executable instructions in hardware, software, firmware, application-specific integrated circuits, and / or a combination thereof. , It is possible to carry out.

The instruction can be presented to the computer 700 as data 750 and / or process 760, which is temporarily stored in memory 720 and then executed by processor 710. Processor 710 can be a variety of processors, including dual microprocessors and other multiprocessor architectures. The memory 720 can include a non-volatile memory (eg, ROM) and / or a volatile memory (eg, RAM). The memory 720 can also be, for example, a magnetic disk drive, a solid state disk drive, a floppy disk drive, a tape drive, a flash memory card, an optical disk, or the like. Therefore, the memory 720 can store the process 760 and / or the data 750. The computer 700 can also be associated with other devices, including computers, printers, peripherals, etc., in a number of configurations (not shown).

It will be appreciated that the above description of embodiments of the present disclosure is provided to allow one of ordinary skill in the art to create or use the present disclosure. Various modifications to these embodiments are self-evident to those of skill in the art, and the general principles defined herein can be applied to other embodiments without departing from the ideas or scope of the present disclosure. Is. Therefore, this disclosure is not intended to be limited to the embodiments presented herein, and should be acknowledged to the broadest extent consistent with the principles and novel features disclosed herein.

In the following, an exemplary embodiment consisting of a combination of various constituent elements of the present invention will be shown.
1. 1. A tag index that generates a set of indexes from an XML (extensible markup language) file, and the set of indexes indexes the terms of tags used in the XML file, and the terms of attributes in the XML file. Includes an attribute index to index and a value index to index the value term in the XML file.
Condensing the XML file into a condensed version of the XML file by transforming the XML file according to the index, and
A method of generating a converted file containing the set of indexes and the compressed version of the XML file.
2. 2. The method according to item 1 above, wherein the XML file contains instructions for controlling the operation of the printer based on the type of printing material stored in the printing material container.
3. 3. 2. The method according to item 2 above, comprising storing the converted file in a memory associated with the printing material container.
4. The method according to item 3 above, which comprises compressing the converted file.
5. The instructions that control the operation of the printer control one or more of cleaning the printer, servicing the printer, and printing using the printing material. The method according to 2.
6. The method according to paragraph 1 above, wherein the XML file uses a known subset of XML syntax.
7. 8. The method according to paragraph 1 above, wherein the tag term, the attribute term, and the value term are ordered in their respective indexes according to the frequency of the terms in the XML file. It's a print container
The source of printing materials and
With a print material distributor,
Equipped with memory,
The memory
A tag index containing a list of tag terms from the XML file, organized according to the frequency of the tag terms in the XML file.
An attribute index containing a list of attribute terms from the L file, organized according to the frequency of the attribute terms in the XML file.
A value index containing a list of value terms from the XML file, organized according to the frequency of the value terms in the XML file.
A print container containing a condensed version of the XML file created by transforming the XML file according to the tag index, the attribute index, and the value index.
9. 8. The print container according to item 8 above, wherein the printer to which the print container is attached recreates the XML file using the tag index, the attribute index, the value index, and the condensed version of the XML file. ..
10. 9. The print container according to item 9, wherein the recreated XML file controls the operation of the printer in relation to at least one of the print material, the print material distributor, and the print container.
11. 8. The print container according to item 8, wherein the tag index, the attribute index, the value index, and the condensed version of the XML file are stored in the memory in a compressed format.
12. A housing that accepts a print container that has a source of print material,
A communication module that obtains a set of indexes and a condensed XML file created from the indexes from the memory on the print container.
An extraction module that produces a decondensed XML file from the condensed XML file by transforming the condensed XML file according to the set of indexes.
A printer comprising a control module that controls the operation of the printer according to an instruction extracted from the decondensed XML file.
13. Containing a memory containing a set of default instructions, and according to the instructions taken by the control module from the decondensed XML file if the decondensed XML file modifies the default instructions. The printer according to item 12 above, which controls the operation of the printer.
14. The control module controls at least one of cleaning the components of the printer, servicing the components of the printer, and printing using the printing material. The printer described in.
15. 12. The printer according to item 12 above, which includes the set of indexes and a decompression module for decompressing the condensed XML file.

Claims (13)

The source of printing materials and
With a print material distributor,
A print container with memory
The memory
A tag index containing a list of the tag terms from the XML file , ordered according to the frequency of the tag terms in the XML (extensible markup language) file .
An attribute index containing a list of the attribute terms from the XML file , ordered according to the frequency of the attribute terms in the XML file.
A value index containing a list of the value terms from the XML file , ordered according to the frequency of the value terms in the XML file.
Stores a condensed version of the XML file created by transforming the XML file according to the tag index, the attribute index, and the value index.
Each of the tag term, the attribute term, and the value term uses the same index value range starting from a known index value.
The tag index, the attribute index, the value index, and the condensed version of the XML file are compressed and stored in the memory as a single file in compressed format.
Print container. The printer to which the print container is attached recreates the XML file using the tag index, the attribute index, the value index, and the condensed version of the XML file, and the recreated XML file. The print container according to claim 1, wherein the printer controls the operation of the printer in relation to at least one of the print material, the print material distributor, and the print container. The tag section of the tag index refers to an instruction that defines the action performed by the printer.
The attribute section of the attribute index is used to specify the parameters of the action triggered by the tag term.
The value term of the value index is used with respect to the attribute term to specify the parameter of the action triggered by the tag term that the attribute term will modify.
The print container according to claim 2. The XML file is associated with a print container that stores a particular print material, and the XML file is for controlling the printer to perform maintenance functions suitable for the particular print material. The print container according to claim 2 or claim 3. Claims 1 to use the XML file to ensure that there are no conflicts due to condensing two phrases with two different syntaxes into the same condensed phrase. The print container according to any one of claims 4. The print container according to any one of claims 1 to 5, wherein the index value is not identified in the memory. Claim 1 to claim that the condensed version of the XML file contains a symbol indicating to the application interpreting the condensed version of the XML file that the most recently opened tag in the XML file should be closed. Item 6. The print container according to any one of items 6. It ’s a printer,
A housing that accepts a print container that has a source of print material,
From the memory on the print container
A tag index containing a list of the tag terms from the XML file, ordered according to the frequency of the tag terms in the XML file.
An attribute index containing a list of the attribute terms from the XML file, ordered according to the frequency of the attribute terms in the XML file.
A set of indexes, including a value index containing a list of the value terms from the XML file, ordered according to the frequency of the value terms in the XML file , the tag term, the attribute term. , And a set of indexes, each of which uses the same index value range starting from a known index value .
A communication module that obtains a condensed XML file created by transforming the XML file according to the set of indexes .
An extraction module that produces a decondensed XML file from the condensed XML file by inversely transforming the condensed XML file according to the set of indexes.
It includes a control module that controls the operation of the printer according to the instructions extracted from the decondensed XML file.
The set of indexes and the condensed XML file are compressed and stored in the memory of the print container as a single file in a compressed format.
Printer. Containing a memory containing a set of default instructions, and according to the instructions taken by the control module from the decondensed XML file if the decondensed XML file modifies the default instructions. The printer according to claim 8 , which controls the operation of the printer. The extraction module reconstructs the index values of the tag term, the attribute term, and the value term from the set of indexes, and the index value is not identified in the memory of the print container. The printer according to claim 8 or 9 . The printer according to any one of claims 8 to 10 , comprising the set of indexes and a decompression module for decompressing the condensed XML file. The XML file uses a known set of XML syntax, and the extraction module fills in the syntax based on the order of the tag section, the attribute section, and the value section in the condensed XML file. The printer according to claim 11 , wherein the decondensed XML file is generated from the decompressed set of indexes and the condensed XML file. The tag section of the tag index refers to an instruction that defines the action performed by the printer.
The attribute section of the attribute index is used to specify the parameters of the action triggered by the tag term.
The value term of the value index is used with respect to the attribute term to specify the parameter of the action triggered by the tag term that the attribute term will modify.
The printer according to any one of claims 8 to 12 .

Images