JP5409090B2 - Information processing apparatus, information processing method, program, and storage medium - Google Patents

Description

  The present invention relates to an information processing apparatus, an information processing method, a program, and a storage medium.

  Until now, the format of XML data analyzed by an XML parser has generally been a text format. However, since XML data requires redundant data to express the data structure and takes time for a computer to read and write, the binary XML technology has recently attracted attention. Examples of the binary XML technology include W3C standard Efficient XML Interchange and ISO standard Fast Infoset. By using these techniques, vocabularies such as element names and attribute names included in the XML data are encoded by assigning numbers in the order of appearance in the XML data, and the data size can be reduced. A table showing the correspondence between codes and vocabularies is called a coding table. These binary XML data can be read and written at higher speed than conventional XML data in text format.

In addition, the data size can be further reduced by encoding attribute values and element contents using integer-type, floating-point-type, or proprietary compression algorithms instead of conventional string-type data. . In addition, when analyzing such data, the conversion processing from character string data to numerical data by a conventional application is not necessary, so that the processing time for the entire analysis can be further shortened.
Also, KDDI XEUS can efficiently compress XML data by encoding each numerical value for an array of numerical values delimited by commas or the like into attribute values and element contents.
In addition, for a plurality of XML data having the same structure, one common tag list in which tag names are listed is created, and compression is performed by encoding each tag name (Patent Document 1). reference).

JP 2002-163248 A

However, the conventional binary XML parser cannot analyze all binary XML data in an environment where memory resources are limited when long encoding data such as long character string data or image data is included in the encoding table. It was.
FIG. 1 is a diagram showing an example of conventional text-format XML data describing the contents of an address book. The XML data described in the binary XML format is shown in FIGS. FIG. 2 is a diagram illustrating an example of an encoding table in which element names and attribute names included in XML data are encoded. Here, the table of FIG. 2 is called a name table. FIG. 3 is a diagram illustrating an example of an encoding table in which attribute values, element contents, and the like included in XML data are encoded. Here, the table of FIG. 3 is referred to as a value table. FIG. 4 is a diagram showing an example of contents described in a binary XML format by using each code included in the encoding table of FIGS. 2 and 3 for a structured document in a text format. Note that the codes of each event such as the start tag, end tag, attribute, element content, etc. in FIG. 4 are the same as those in FIG. 5, and the codes of these events are known in advance by the application (or defined in advance in the application). ). FIG. 5 is a diagram illustrating an example of a code of each event.

When the binary XML parser analyzes data, the name table of FIG. 2 and the value table of FIG. 3 included in the data are first analyzed, and the contents of each table are stored in the internal memory. The binary XML parser, when analyzing the body part including the structure and values of the binary XML data, uses a set of each code and value stored in its internal memory, so that the tag name and attribute Resolve names, attribute values, and element contents.
However, in an embedded device environment with limited memory resources, if the value table contains large data such as image data as shown in FIG. 3, the image data can be stored in the internal memory. There wasn't. When binary XML data includes such large data, it is common for the binary XML parser to interrupt the subsequent analysis processing and notify the application of an analysis error.

  The present invention has been made in view of such a problem, and even when an object (for example, an encoding table) related to encoding of a structured document contains large-size data, analysis can be performed with a small amount of memory resources. The purpose is to do so.

Therefore, in the information processing apparatus of the present invention, the code included in the encoded document created by encoding the structure information and the value included in the structured document, the value, and the attribute value related to the value correspond to each other. Storage determining means for determining whether or not to store in the memory value data including a value corresponding to the attribute value based on the attribute value of the value data of the value object including a plurality of attached value data; and When it is determined by the storage determination means that the value data including the value corresponding to the attribute value is stored in the memory, the value data including the value is stored in the in-memory value object, and the storage determination means Storage means for storing value data not including the value in a value object in the memory when it is determined not to store in the memory value data including a value corresponding to the attribute value; and the memory A value determination unit that determines whether or not the value data of the value object includes a value; and when the value determination unit determines that the value data of the value object in the memory includes a value, The value is returned to the application, and when the value determination unit determines that the value data of the in-memory value object does not include a value, a notification that returns the code and attribute value included in the value data to the application When a sign of a value to be acquired by the application is received from the means, the value object is analyzed, and a value that is a set of codes matching the sign passed from the application is obtained from the value object. Value acquisition means for acquiring and passing to the application.

  According to the present invention, even when an object (for example, an encoding table) relating to encoding of a structured document includes large-size data, it can be analyzed with a small amount of memory resources.

It is a figure which shows an example of the XML data of the conventional text format which described the content of the address book. It is a figure which shows an example of the encoding table which encoded the element name and attribute name contained in XML data. It is a figure which shows an example of the encoding table which encoded the attribute value, element content, etc. which are contained in XML data. It is a figure which shows an example of the content described in the binary XML format by using each code | symbol contained in the encoding table of FIG. It is a figure which shows an example of the code | symbol of each event. It is a figure which shows an example of the system configuration | structure of the system which concerns on this embodiment. It is a figure which shows an example of the hardware constitutions of PC. It is a flowchart (the 1) which shows an example of the process which analyzes the encoding table contained in binary XML data. FIG. 6 is a diagram (part 1) illustrating an example of a value table stored in an internal memory. It is a flowchart (the 1) which shows an example of the analysis process of a body part. It is a flowchart (the 1) which shows an example of the process which acquires a value. It is a flowchart (the 2) which shows an example of the process which analyzes the encoding table contained in binary XML data. FIG. 10 is a second diagram illustrating an example of a value table stored in an internal memory. It is a flowchart (the 2) which shows an example of the analysis process of a body part. It is a flowchart (the 2) which shows an example of the process which acquires a value.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<Embodiment 1>
In the present embodiment, a process for analyzing binary XML data including large data in an encoding table with a small memory resource will be described.
FIG. 6 is a diagram illustrating an example of a system configuration of the system according to the present embodiment.
The PC 101 is connected to the LAN 102. A digital camera 103, a multifunction peripheral 104, and a file server 105 are connected to the LAN 102.

FIG. 7 is a diagram illustrating an example of a hardware configuration of a PC.
The CPU 201 is a system control unit and controls the entire PC. The ROM 202 stores a control program for the CPU 201 and various fixed data. The RAM 203 is configured by SRAM, DRAM, and the like, and stores program control variables and the like. Various setting parameters and various work buffers are also stored in the RAM 203. The storage unit 204 is configured with a hard disk or the like, and stores various data files such as document data and image data. The operation unit 205 includes a keyboard, a mouse, a touch panel, and the like, and is used for an operator to perform various input operations. The display unit 206 is a television screen that displays an image. The LAN i / f 207 is an interface for connecting to the LAN line 208. The USBi / f 209 is an interface for connecting to the USB line 210.
Note that the hardware configurations of the digital camera 103, the multifunction peripheral 104, and the file server 105 are the same as the hardware configuration of the PC 101 shown in FIG. Part.
The CPU of each device executes processing based on a program (for example, a program corresponding to a binary XML parser (hereinafter simply referred to as a binary XML parser) or an application of the present embodiment) stored in a storage unit or the like. As a result, the function of each device and the processing relating to the flowchart described later are realized. That is, a binary XML parser and an application described later may be mounted on the PC 101, or may be mounted on the digital camera 103, the multifunction peripheral 104, the file server 105, and the like.

FIG. 8 is a flowchart (part 1) illustrating an example of processing for analyzing an encoding table included in binary XML data.
First, the binary XML parser analyzes a name table as shown in FIG. 2 in which names such as element names and attribute names and codes assigned to the names are stored, and sets a pair of each name and code. The data is stored in an internal memory such as the RAM 203 or the storage unit 204 (S102).
Next, when the binary XML parser stores a value table as shown in FIG. 3 in which values such as attribute values, element contents, comment contents, etc., and codes assigned to the values are stored in the internal memory. The restriction information is analyzed (S103). This restriction information includes the upper limit size of each value stored in the internal memory, the type of data that does not need to be stored in the internal memory, and the like. The upper limit size, the type of data that does not need to be stored in the internal memory, and the like are generally set in advance in the binary XML parser by the application before starting analysis. In this embodiment, the upper limit size of each value is 50000 bytes, and the type of data unnecessary for the application is a comment.

The binary XML parser starts to analyze the value table, but first determines whether or not all contents of the value table have been analyzed (S104). If it is determined in S104 that the entire contents of the value table have not been analyzed, the binary XML parser determines the sign, affiliation information (type information) (affiliation), and size information (size) of each value included in the value table. Are stored in the internal memory (S105 to S107). This affiliation information is a code assigned to each event as shown in FIG. 5, and the binary XML parser refers to this code to indicate which value each value such as an attribute value or element content represents. It can be judged.
Based on the value affiliation, the binary XML parser determines (stores determination) whether the value affiliation is a type stored in the internal memory (S108). If it is determined in S108 that the value does not belong to the type stored in the internal memory, the binary XML parser skips reading the value for the size analyzed in S107 without saving it in the internal memory (S109). More specifically, as shown in FIG. 9 to be described later, the binary XML parser internally stores value data (sign + affiliation + size) that does not include a value among value data that is record data constituting the value table. Save (store) it in memory.

  If it is determined in S108 that the value belongs to the type stored in the internal memory, the binary XML parser determines whether the value size is equal to or smaller than the upper limit size stored in the internal memory based on the content analyzed in S103. Whether or not is determined (memory determination) (S110). In S110, when it is determined that the size of the value is not less than or equal to the upper limit value, the binary XML parser skips reading the value for the size analyzed in S107 without saving it in the internal memory (S109). More specifically, as described above, the binary XML parser stores value data (sign + affiliation + size) that does not include a value among value data that is record data constituting the value table in the internal memory ( Remember. In S110, when it is determined that the size of the value is equal to or smaller than the upper limit value, the binary XML parser stores the value in the internal memory (S111).

FIG. 9 shows the value table stored in the internal memory after the value table is analyzed in the process of FIG. FIG. 9 is a diagram (part 1) illustrating an example of a value table stored in the internal memory.
As shown in FIG. 9, in this embodiment, the binary XML parser uses the BASE64 image data of 10000 bytes exceeding the upper limit size of 50000 bytes and the content of the comment based on the restriction information in S103. Not saved in internal memory.

Next, the binary XML parser executes the processing shown in FIG. 10 using the name table and value table stored in the internal memory, and obtains the structure and values of the binary XML data shown in FIG. Analyze the included body part. FIG. 10 is a flowchart (part 1) illustrating an example of the body part analysis process.
The binary XML parser initializes a stack for storing the tag name in the internal memory (S202). Then, the binary XML parser determines whether all body parts have been analyzed (S203). If it is determined in S203 that the body part has not been analyzed, the binary XML parser advances the body part by reading 1 byte and analyzes the event type (S204).
Next, the binary XML parser determines whether or not the event type is a start tag (S205). If it is determined in S205 that the event type is a start tag, the binary XML parser reads the body part by 1 byte and analyzes the tag name using the name table (S206). At that time, the binary XML parser pushes the tag name onto the stack (S207), and passes the tag name to the requesting application as the name of the start tag (S208).

If it is determined in S205 that the event type is not a start tag, the binary XML parser determines whether it is an end tag (S209). If it is determined in S209 that the event type is an end tag, the binary XML parser pops the tag name from the stack (S210), and passes the popped tag name as the end tag name to the requesting application (S211). ).
If it is determined in S209 that the event type is not an end tag, the binary XML parser determines whether the event is an attribute (S212). If it is determined in S212 that the event type is an attribute, the binary XML parser reads the body part by 1 byte and analyzes the attribute name using the name table (S213). The binary XML parser reads the body part by 1 byte and analyzes the attribute value (value) using the value table. At this time, it is determined whether the attribute value is stored in the value table (value determination). (S214). If it is determined in S214 that the attribute value is stored in the value table, the binary XML parser passes the attribute name and attribute value to the requesting application (S215). If it is determined in S214 that the attribute value is not stored in the value table, the binary XML parser passes (notifies) the attribute name, the sign of the attribute value, and the size information to the requesting application ( S216).

If it is determined in S212 that the event type is not an attribute, the binary XML parser determines whether it is element content (S217). If it is determined in S217 that the event type is element content, the binary XML parser reads the body part by 1 byte and analyzes the element content using the value table. At that time, the binary XML parser determines (value determination) whether or not the element contents are stored in the value table (S218). If it is determined in S218 that the element content is stored in the value table, the binary XML parser passes the element content to the requesting application (S219). If it is determined in S218 that the element content is not stored in the value table, the binary XML parser passes (notifies) the code of the element content and the size information to the requesting application (S220).
If it is determined in S212 that the event type is not element content, the binary XML parser determines that the event type is a comment. Then, the binary XML parser advances the body part by reading 1 byte and analyzes the content of the comment. At this time, the binary XML parser determines whether the content of the comment is stored in the value table (value determination) (S221). If it is determined in S221 that the content of the comment is stored in the value table, the binary XML parser passes the content of the comment to the requesting application (S222). In S221, when it is determined that the comment content is not stored in the value table, the binary XML parser passes (notifies) the code of the comment content and the size information to the request source application (S223).
In the present embodiment, based on the value table stored in the internal memory of FIG. 9, the binary XML parser, for the element content of the photo element and the content of the comment, sets the code and size of each to the requesting application. And pass information.

If the application needs to acquire value data skipped by the binary XML parser after the binary XML parser completes the body part analysis in the process shown in FIG. 10, the process of FIG. 11 is executed. Can be obtained. FIG. 11 is a flowchart (part 1) illustrating an example of a process for acquiring a value.
First, the application analyzes the size information acquired together with the sign of the value to be acquired (S302). Then, the application determines whether to acquire the value based on the size information of the value (S303). If it is determined in S303 that the value is acquired, the application passes the sign of the value to the binary XML parser (S304).
When a code is passed from the application, the binary XML parser starts the analysis of the binary XML data again from the top (S305). At this time, since the data that the application wants to acquire is value data, the binary XML parser skips the contents of the name table without saving them in the internal memory.

Next, the binary XML parser determines whether all contents of the value table have been analyzed (S306). In S306, when it is determined that the entire contents of the value table have not been analyzed, the binary XML parser analyzes each code (S307) and determines whether or not it matches the passed code (S308). If it is determined in S308 that the code matches the passed code, the binary XML parser acquires a value that is a set of the code from the value table (value acquisition) and passes the value to the requesting application (S309).
If it is determined in S308 that the code does not match the passed code, the binary XML parser continues to analyze the value table until the code specified by the application appears. If it is determined in S306 that all contents of the value table have been analyzed, the binary XML parser notifies the requesting application that the specified code is not included in the value table (S310).
When passing a value to the requesting application in S309, the binary XML parser may pass not only the value but also value data including the value. Further, in S309, the binary XML parser may transfer the value data in a stream format so that the application can sequentially read the value data instead of transferring the entire value data at once.
With the above processing, binary XML data including large data in the encoding table can be analyzed with a small amount of memory resources.

<Embodiment 2>
In the present embodiment, a description will be given of processing in which an application acquires large-sized data skipped in the encoding table by specifying an offset from the beginning of binary XML data.
FIG. 12 is a flowchart (part 2) illustrating an example of processing for analyzing an encoding table included in binary XML data.
First, the binary XML parser initializes a variable offset that counts the number of bytes from the beginning of the binary XML data (S402). Next, the binary XML parser analyzes a name table storing element names, attribute names, and the like and codes assigned to the names, and sets each name and code in the RAM 203 or the storage unit 204. Save in the memory (S403).

Next, the binary XML parser updates the variable offset at the current analysis position of the binary XML data after the name table analysis. Next, the binary XML parser analyzes restriction information when saving a value table storing values such as attribute values, element contents, and comment contents, and codes assigned to the values in the internal memory ( S404).
The binary XML parser starts to analyze the value table, but first determines whether all contents of the value table have been analyzed (S405). If it is determined in S405 that the entire contents of the value table have not been analyzed, the binary XML parser analyzes the sign, affiliation information, and size information of each value included in the value table and saves them in the internal memory ( S406 to S408).
Then, the binary XML parser updates the variable offset at the position where the size information data starts, and stores the value in the internal memory (S409). The data size of the size information is 4 bytes.

  Then, the binary XML parser determines (stores determination) whether or not the value affiliation is the type stored in the internal memory based on the content analyzed in S404 (S410). If it is determined in S410 that the value affiliation is not a type to be stored in the internal memory, the binary XML parser skips reading the value for the size analyzed in S408 without storing it in the internal memory (S411). More specifically, as described above, the binary XML parser outputs value data (sign + affiliation + size + offset (offset)) that does not include a value among value data that is record data constituting the value table. Save (store) in internal memory. If it is determined in S410 that the value belongs to the type stored in the internal memory, the binary XML parser determines whether the value size is equal to or smaller than the upper limit size stored in the internal memory based on the content analyzed in S408. It is determined (memory determination) (S412). If it is determined in S412 that the size of the value is not less than or equal to the upper limit value, the binary XML parser skips reading without saving the value in the internal memory for the size analyzed in S408 (S411). More specifically, as described above, the binary XML parser outputs value data (sign + affiliation + size + offset (offset)) that does not include a value among value data that is record data constituting the value table. Save (store) in internal memory. If it is determined in S412 that the value size is equal to or smaller than the upper limit value, the binary XML parser stores the value in the internal memory (S413).

FIG. 13 shows the value table stored in the internal memory after the value table is analyzed by the processing of FIG. FIG. 13 is a diagram (part 2) illustrating an example of a value table stored in the internal memory.
As shown in FIG. 13, the binary XML parser stores 100000 bytes of BASE64 image data exceeding the upper limit size of 50000 bytes and the content of the comment in the internal memory based on the restriction information in S404. Not. The binary XML parser stores the start position of the size information in the value table as an offset value.

Next, the binary XML parser executes the processing shown in FIG. 14 using the name table and the value table stored in the internal memory, and obtains the structure and values of the binary XML data shown in FIG. Analyze the included body part. FIG. 14 is a flowchart (part 2) illustrating an example of the body part analysis process.
The binary XML parser initializes a stack for storing the tag name in the internal memory (S502). Then, the binary XML parser determines whether all the body parts have been analyzed (S503). If it is determined in S503 that the entire body part has not been analyzed, the binary XML parser advances the body part by 1 byte and analyzes the event type (S504).
Next, the binary XML parser determines whether or not the event type is a start tag (S505). If it is determined in S505 that the event type is a start tag, the binary XML parser reads the body part by 1 byte and analyzes the tag name using the name table (S506). At that time, the binary XML parser pushes the tag name onto the stack (S507), and passes the tag name to the requesting application as the name of the start tag (S508).

If it is determined in S505 that the event type is not a start tag, the binary XML parser determines whether it is an end tag (S509). If it is determined in S509 that the event type is an end tag, the tag name is popped from the stack (S510), and the popped tag name is passed to the requesting application (S511).
If it is determined in S509 that the event type is not an end tag, the binary XML parser determines whether the event is an attribute (S512). If it is determined in S512 that the event type is an attribute, the binary XML parser reads the body part by 1 byte, and analyzes the attribute name using the name table (S513). The binary XML parser reads the body part by 1 byte and analyzes the attribute value (value) using the value table. At this time, it is determined whether the attribute value is stored in the value table (value determination). (S514). If it is determined in S514 that the attribute value is stored in the value table, the binary XML parser passes the attribute name and attribute value to the requesting application (S515). If it is determined in S514 that the attribute value is not stored in the value table, the binary XML parser passes the attribute name, the offset regarding the position of the attribute value, and the size information of the attribute value to the requesting application. (Notify) (S516).

If it is determined in S512 that the event type is not an attribute, the binary XML parser determines whether the event content is element content (S517). If it is determined in S517 that the event type is element content, the binary XML parser reads the body part by 1 byte, and analyzes the element content using the value table. At that time, the binary XML parser determines (value determination) whether or not the element content is stored in the value table (S518). If it is determined in S518 that the element content is stored in the value table, the binary XML parser passes the element content to the requesting application (S519). In S518, when it is determined that the element contents are not stored in the value table, the binary XML parser passes (notifies) the offset regarding the position of the element contents and the size information of the element contents to the request source application. (S520).
In S512, when it is determined that the event type is not element content, the binary XML parser determines that the event type is a comment. Then, the binary XML parser advances the body part by reading 1 byte and analyzes the content of the comment. At this time, the binary XML parser determines whether the content of the comment is stored in the value table (value determination) (S521). If it is determined in S521 that the content of the comment is stored in the value table, the content of the comment is passed to the request source application (S522). If it is determined in S521 that the content of the comment is not stored in the value table, the binary XML parser passes the offset regarding the position of the content of the comment and the size information of the content of the comment to the requesting application ( (S523).
In the present embodiment, based on the value table stored in the internal memory of FIG. 13, the binary XML parser has an offset regarding the position of the element content of the photo element and the content of the comment in the request source application. And size information.

If the application needs to acquire the value data skipped by the binary XML parser after the binary XML parser completes the body part analysis in the process shown in FIG. 14, the process of FIG. 15 is executed. Can be obtained. FIG. 15 is a flowchart (part 2) illustrating an example of a process for acquiring a value.
First, the application analyzes size information of a value to be acquired (S602). Then, the application determines whether to acquire the value based on the size information of the value (S603). If it is determined in S603 that the value is acquired, the application passes an offset related to the value to the binary XML parser (S604).
When an offset is passed from the application, the binary XML parser starts the analysis of the binary XML data from the top again, and skips the data corresponding to the offset (S605). Then, the binary XML parser analyzes the size information of the value to be acquired (S606), reads the data (value) for the size (value acquisition), and passes it to the requesting application (S607).

In S607, the binary XML parser may pass not only the value but also value data including the value when passing the value to the requesting application. Further, in S309, the binary XML parser may transfer the value data in a stream format so that the application can sequentially read the value data instead of transferring the entire value data at once.
As a result of the above processing, it is possible to acquire large-sized data skipped in the encoding table with less analysis time by designating an offset from the top of the binary XML data by the application.

<Other embodiments>
The object of the above-described embodiment is achieved by the following. That is, a storage medium (or recording medium) in which a program code of software that realizes the functions of the above-described embodiments is recorded is supplied to the system or apparatus. Then, the central processing means (CPU or MPU) of the system or apparatus reads and executes the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the storage medium recording the program code constitutes the above-described embodiment.
In addition, by executing the program code read by the central processing means of the system or apparatus, an operating system (OS) or the like operating on the system or apparatus performs actual processing based on the instruction of the program code. Do some or all. The case where the function of the above-described embodiment is realized by the processing is also included.
Further, it is assumed that the program code read from the storage medium is written in a memory provided in a function expansion card inserted into the system or apparatus or a function expansion unit connected thereto. After that, based on the instruction of the program code, the CPU of the function expansion card or function expansion unit performs part or all of the actual processing, and the function of the above-described embodiment is realized by the processing. It is.
When the above-described embodiment is applied to the storage medium, the storage medium stores program codes corresponding to the flowcharts described above.

  As described above, according to each embodiment described above, even when an object (for example, an encoding table) related to encoding of a structured document includes large-size data, analysis can be performed with a small amount of memory resources. Can do.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

  The value object described in the claims corresponds to, for example, the value table as shown in FIG. 3 described above. As described above, the value table is an attribute related to the code, value, and value included in the encoded document as shown in FIG. 4 created by encoding the structure information and value included in the XML data document (structured document). As an example of the value, a plurality of value data in which affiliation and size are associated are included. The in-memory value object described in the claims corresponds to, for example, a value table stored in the internal memory as shown in FIG. 9 or 13 described above. The value data described in the claims corresponds to, for example, data of one record included in the above-described value table. An information processing apparatus and a computer described in the claims correspond to, for example, the PC 101, the digital camera 103, the multifunction machine 104, the file server 105, or the like described above.

101 PC, 102 LAN, 103, digital camera, 104 MFP

Claims (6)

A value object including a plurality of value data in which a code included in an encoded document created by encoding structure information and a value included in a structured document, the value, and an attribute value related to the value are associated with each other Storage determination means for determining whether or not to store in the memory value data including a value corresponding to the attribute value, based on the attribute value of the value data;
When it is determined by the storage determination means that the value data including the value corresponding to the attribute value is stored in the memory, the value data including the value is stored in the in-memory value object, and the storage determination means When it is determined that the value data including the value corresponding to the attribute value is not stored in the memory, the storage unit stores the value data not including the value in the in-memory value object;
Value determining means for determining whether or not the value data of the in-memory value object includes a value;
If it is determined by the value determination means that the value data of the in-memory value object contains a value, the value is returned to the application, and the value determination means returns a value to the value data of the in-memory value object. Is not included, the notification means for returning the code and attribute value included in the value data to the application,
When a sign of a value to be acquired by the application is passed from the application, the value object is analyzed, and a value that is a set of codes that matches the sign passed from the application is acquired from the value object. A value acquisition means to be passed to the application;
An information processing apparatus.   The information processing apparatus according to claim 1, wherein the attribute value related to the value is a size of the value.   The information processing apparatus according to claim 1, wherein the attribute value related to the value is type information of the value. A value object including a plurality of value data in which a code included in an encoded document created by encoding structure information and a value included in a structured document, the value, and an attribute value related to the value are associated with each other A storage determination step for determining whether or not to store in the memory value data including a value corresponding to the attribute value based on the attribute value of the value data;
When it is determined in the storage determination step that the value data including the value corresponding to the attribute value is stored in the memory, the value data including the value is stored in the in-memory value object, and the storage determination step A storage step of storing the value data not including the value in a value object in the memory if it is determined not to store the value data including the value corresponding to the attribute value in the memory;
A value determination step for determining whether or not a value is included in the value data of the in-memory value object;
If it is determined in the value determination step that the value data of the in-memory value object contains a value, the value is returned to the application, and the value determination step returns a value to the value data of the in-memory value object. A notification step for returning to the application the code and the attribute value included in the value data,
When a sign of a value to be acquired by the application is passed from the application, the value object is analyzed, and a value that is a set of codes that matches the sign passed from the application is acquired from the value object. A value acquisition step to pass to the application;
An information processing method including: Computer
A value object including a plurality of value data in which a code included in an encoded document created by encoding structure information and a value included in a structured document, the value, and an attribute value related to the value are associated with each other Storage determination means for determining whether or not to store in the memory value data including a value corresponding to the attribute value, based on the attribute value of the value data;
When it is determined by the storage determination means that the value data including the value corresponding to the attribute value is stored in the memory, the value data including the value is stored in the in-memory value object, and the storage determination means When it is determined that the value data including the value corresponding to the attribute value is not stored in the memory, the storage unit stores the value data not including the value in the in-memory value object;
Value determining means for determining whether or not the value data of the in-memory value object includes a value;
If it is determined by the value determination means that the value data of the in-memory value object contains a value, the value is returned to the application, and the value determination means returns a value to the value data of the in-memory value object. Is not included, the notification means for returning the code and attribute value included in the value data to the application,
When a sign of a value to be acquired by the application is passed from the application, the value object is analyzed, and a value that is a set of codes that matches the sign passed from the application is acquired from the value object. A value acquisition means to be passed to the application;
Program to function as.   A computer-readable storage medium storing the program according to claim 5.

Images