JP4296775B2 - Device and program for displaying XML data - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to outputting XML data via a network.
[0002]
[Prior art]
In a system in which a plurality of devices are connected via a network (for example, a LAN), when one device stores information about the device as HTML data, the HTML data is displayed (viewed) from another device. , Printing, etc.). HTML (HyperText Markup Language) is a language born to write web pages. For example, even in a system in which a device such as an image forming apparatus is used via a network, if the device stores the information (for example, device management information) as HTML data, another device (for example, a personal computer terminal) ) Can be obtained and displayed by a web browser. For example, communication of error information such as a multi-function device (MFP) using data in HTML format is described in Japanese Patent Laid-Open No. 2001-186301.
[0003]
Browsing HTML data via a network has problems such as network load due to transmission in units of pages, and inability to reuse data. Therefore, it is conceivable to adopt XML and create data in XML. XML (eXtensible Markup Language) is a markup language with an extended function. Since XML itself does not define a layout, the display (viewing, printing, etc.) of data described in XML (hereinafter referred to as XML data) is performed using a style sheet language (for example, XSL (eXtensible Stylesheet Language) or CSS (Cascading Style Sheet)). Use the style sheet described in. In the style sheet, a display / print area, a font name, a character size, and the like are specified. Moreover, XSLT (XSL Transformations) etc. are used for the language of the part which performs the conversion process of XSL data.
[0004]
[Patent Document 1]
Japanese Patent Laid-Open No. 2001-186301
[Problems to be solved by the invention]
A client terminal connected to the network is provided with an application (such as a web browser) for displaying (browsing, printing, etc.) via the network. If this application supports XML, the XML data can be displayed based on the XML data and the style sheet. However, at present, applications do not necessarily support XML. However, it is desirable to enable display of XML data at the client terminal regardless of whether the client terminal application supports XML.
[0006]
An object of the present invention is to display XML data regardless of whether or not an application for display supports XML when displaying XML data stored in a device connected via a network. Is to make it possible.
[0007]
[Means for Solving the Problems]
The device according to the present invention is a device connected to a client terminal and a server apparatus via a network. This device comprises storage means for holding XML data describing data relating to the device itself and a style sheet for displaying the data. When the application of the client terminal requests XML data, the determination unit determines whether or not the application has an XML analysis unit . Data transmission means, when the front Kia application of the client terminal is the determination means does not have an XML analyzing means determines, sends the XML data to the server device, before Symbol X ML data from the server device to send incorporating information to get the instruction before Kia application. This makes it possible to display XML data even in an application that does not include XML analysis means.
[0008]
Before Kide vice, for example, an image forming apparatus, the data for the previous SL device itself is data indicating the internal state of the image forming apparatus.
[0009]
Before Kide vice preferably further comprises a web server means for providing a pre-Symbol X ML data. When the application requests the XML data from the web server unit, the determination unit determines whether the application has an XML analysis unit, and the data transmission unit includes the web server unit. To transmit the XML data.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.
As shown in FIG. 1, a plurality of shared devices 100 (image forming apparatuses such as multi-function devices, printers, and digital copying machines), a device management apparatus 200 that manages the shared device 100 to be managed, and a client terminal 300 ( For example, a personal computer) is connected to a network (LAN, etc.) 400. Here, when a request is received from the external client terminal 300, the device 100 creates XML data describing management data, which is data representing the internal state of the device 100, and a style sheet for displaying the XML data. To provide through. Thereby, the client terminal 300 (300C) can display XML data with an application (for example, web browser), for example. Specifically, the application (web browser) of the client terminal 300 specifies a URI by HTTP (Hypertext Transfer Protocol) and sends a request to the web server. The web server provides data in response to a request by HTTP. The web browser analyzes and displays the received data. In this embodiment, the application converts the received XML data into, for example, HTML data and performs display (viewing, printing, etc.).
[0012]
When displaying based on XML data and an XSLT stylesheet, an XML analysis application called an XML parser (or an XML processor) that decomposes an XML statement into an element that supports XML (for example, a web browser) Use modules. However, if the application of the client terminal 300 (for example, 300a, 300b) does not include the XML analysis module, the XML data cannot be displayed. Therefore, in order to be able to display in such a case, the application of the client terminal 300 decodes the XML data and its style sheet to another server (for example, the device management apparatus 200) connected via the network. An XML analysis module that converts data into a format that can be used (in this case, HTML data) is provided. When the device 100 determines that the application of the client terminal 300 that has sent the HTTP request does not include the XML analysis module, the device 100 sends the XML data describing the management data and its style sheet to the device management apparatus 200. Therefore, the XML analysis module in the device management apparatus 200 analyzes the XML data and converts it into HTML data that can be decoded by the application of the client terminal 300. At the same time, the device 100 creates an HTML file described so as to automatically access the HTML data of the device management apparatus 200 and sends it to the client terminal 300. In response to this, the application of the client terminal 300 automatically accesses the device management apparatus 200 and displays the analysis result (management data in HTML format). Therefore, the client terminal 300 can display XML data even in an application that does not have an XML analysis module.
[0013]
FIG. 2 shows an example of management information. In the document type declaration part of the XML document, the storage location of the style sheet file for displaying the XML data can be designated, and thereby the style sheet for the XML data is designated. In this example, in the second sentence, the storage location of the style sheet file is specified after href =, and the style sheet type is specified after type =. According to this management information (data representing the internal state of the device), the product name of this multi-function device is abc-001. The document tray is installed. The paper tray is mounted, its name is Tray 1, the paper size is letter, the paper is plain paper, the paper transport direction is short side, the paper capacity is 250 sheets, Is stored in a tray. FIG. 3 is an example of a style sheet specified by the XML data of FIG.
[0014]
Next, each device connected to the network 400 will be specifically described. A multi-function device (hereinafter referred to as MFP) which is one of the shared devices 100 is a device that functions as a printer, a scanner, or the like. For example, as illustrated in FIG. 4, the MFP 100 includes a scanner device 102 that reads an image of a document, a print engine unit 104 that receives print data and prints it on paper, and a controller 106 that controls them. The controller 106 is connected to the operation panel unit 108, the communication device 110 including a network interface connected to the external network 400, and the like. When functioning as a printer, when print data is received from the outside via the communication device 110, raster data is created and printing is performed by controlling the print engine unit 104. Further, the controller 106 creates management data for the MFP itself based on settings via the operation panel 108 and output results of various sensors (not shown), and provides them when requested.
[0015]
Specifically, the controller 106 of the MFP includes a CPU 120, a storage device (HDD) 122, an image processing unit 124, an image memory 126, and the like. The storage device 122 is, for example, a rewritable semiconductor memory or hard disk device. In addition to the control program 130 that controls the MFP and communicates via the network, the state management unit 132 that manages the state of the MFP, and the state management unit An XML data generation unit 134 that converts the management data received from 132 into XML, and a web server 136 that transmits XML data generated by the XML data generation unit 134 in response to a request from the client terminal 300 are stored. In addition, an XML data storage unit 138 that stores the generated XML data and a transfer destination storage unit 140 that stores a transfer destination of the XML data are provided.
[0016]
As will be described later, when there is a management data display request from the client terminal 300, the web server 136 checks whether or not the client terminal 300 has an XML analysis program. If the XML analysis program is provided, the XML file and the style sheet are transferred to the client terminal 300. If the XML analysis program is not provided, the transfer destination stored in the transfer destination storage unit 140 ( Here, the XML file and the style sheet are transferred to the URI notified from the device management apparatus 200.
[0017]
The device management apparatus 200 is a server apparatus using, for example, a workstation or a personal computer. As shown in FIG. 5, the CPU 202, an input device 204 such as a keyboard, a display device 206, a storage device (HDD) 208, and a network A communication device 210 including a network interface connected to the network 400 is provided. The storage device 208 stores an OS program (not shown), a device management program 220, a web server 222, and an XML analysis program 224. When the device management program 220 searches the network 400 and finds the device 100, the device management program 220 assigns an IP address and notifies the MFP 100 of the URI of the web server 222 that the device management program 220 has. In response to this, the MFP 100 stores the URI in the transfer destination storage unit 140.
[0018]
The client terminal 300 is, for example, a personal computer (PC). The personal computer is, for example, a CPU 302 that controls the whole, an input device 304 such as a keyboard, a display device 306, and a storage device (HDD) 308 as shown in FIG. And a communication device 310 including a network interface connected to the network 400. The storage device 308 stores an OS program (not shown) and the like, a web browser 320 that is an application for displaying XML data, and the like. The web browser 320 of the client terminal 300 may or may not have the XML analysis unit 322.
[0019]
In this network environment, the user of the client terminal 300 can request management information by accessing the web server 136 of the device (MFP) 100 using the web browser 320. This management information is XML data. In MFP 100, upon receiving a management information request from terminal 300, XML data generation unit 134 generates an XML file from the management data received from status management unit 132. Further, the name / version of the web browser 320 of the client terminal 300 is acquired from the HTTP request header, and based on this, it is determined whether or not the web browser 320 includes the XML analysis program 322. When the MFP 100 determines that the web browser 320 has the XML analysis unit program 322, the MFP 100 transfers the XML data and the style sheet to the web browser 320 of the client terminal 300 as they are. Thereby, the web browser 320 analyzes the XML data, converts it into, for example, HTML data, and displays it.
[0020]
On the other hand, if the MFP 100 determines that the web browser 320 does not have the XML analysis program 322, the MFP 100 generates an HTML file that describes to automatically access the URI of the device management apparatus 200, and sends it to the client terminal 300. Return it. At this time, the URI of the XML file generated by the MFP 100 is described in the HTML file.
[0021]
FIG. 7 is an example of an HTML file generated by the MFP 100. Here, “150.17.40.10” described in the fourth sentence is the URI of the web server 222 of the device management apparatus 200, and “150.17.40.20” is the URI of the MFP (XML file).
[0022]
When the HTML file is returned, the web browser 320 of the client terminal 300 automatically accesses the web server 222 of the device management apparatus 200 based on the IP address described in the HTML file. The device management apparatus 200 acquires XML data from the MFP 100 in response to a request from the web browser 222 and converts it into an HTML file using the XML analysis program 224 (that is, converts it into a format that can be displayed by the web browser 320 of the client terminal 300). Return to the web browser 320. In the client terminal 300, the web browser 320 displays device management information as an HTML file. Thereby, even if the application of the terminal 300 does not have the XML analysis unit, the XML file can be displayed on the terminal 300.
[0023]
The control flow of each component device that implements the above-described processing is as follows. FIG. 8 shows a flow of processing related to communication of the controller of the device (MFP) 100. When there is a request for browsing management data from the web browser 320 of the client terminal 300 to the web server 136 (YES in S100), the management data received from the state management unit 132 is converted to XML (S102). Next, it is determined whether the web browser 320 is equipped with the XML analysis program 322 based on the data transmitted when the management data browsing request is made (S104). This determination is made based on, for example, the browser name and version. If it is determined that the web browser 320 of the client terminal 300 is equipped with the XML analysis program 322 (NO in S104), XML data is sent to the web browser 320 (S106). However, if it is determined that the web browser 320 is not equipped with the XML analysis program 322 (YES in S104), the URI of the web server 222 of the device management apparatus 200 held in the transfer destination storage unit 140 is automatically accessed. The HTML file described above is created (S108), and the web server 136 transmits the HTML file to the client terminal (S110). Next, when there is a request for XML data from the device management apparatus 200 to the web server 136, the web server 136 transmits the XML data to the device management apparatus 200 (S112). Note that the program executed on the server can be implemented in various forms such as a script and an external program, as is known to those skilled in the art.
[0024]
FIG. 9 shows a flow of XML data generation and transfer of the management program 220 of the device management apparatus 200. Although not shown, the management program 220 assigns an IP address when a new device 100 is found.
[0025]
When there is an XML data request from the web browser 320 of the client terminal 300 (YES in S200), the IP address of the device (MFP) 100 is acquired, and management data that is XML data is received from the MFP 100 (S202).
[0026]
Next, if it is determined that XML data has been acquired from the MFP 100 (YES in S204), the XML data is converted into HTML data (S206), and the web server 222 is caused to return the HTML data to the web browser 320 of the terminal 300 ( S208). On the other hand, if it is determined that the XML data cannot be acquired from the MFP 100 (NO in S204), an error is displayed on the MFP 100 (S210).
[0027]
As described above, when there is a request for browsing management data from an application on the client terminal, MFP 100 converts the management data into XML. When the client terminal application determines that it can handle the XML data, it sends the generated XML data. However, if it is determined that the XML cannot be handled, the XML data is sent to another server device connected via the network, and an HTML file described to automatically access this server device is created. The HTML file is transmitted to the client terminal. The server device converts the received XML data into data in a format that can be displayed by the application of the client terminal, and sends the data when accessed from the client device. Thereby, the application of the client terminal can display management data even if it does not support XML.
[0028]
In the above, the display by an application that does not support XML data has been described as a case where the client terminal cannot directly handle the data format generated by the device. However, as another example, the device (MFP, printer, etc.) When the usage status data (one of the management data) of the number of prints at the client is tabulated and managed at the client terminal, the spreadsheet software as the client application may not be able to handle the HTML format but may be able to handle the CSV format. is there. In such a case, the device transmits data in HTML format to another server device (for example, a device management device). The server device converts the HTML format into the CSV format and transmits the generated CSV format data to the client terminal. Thus, spreadsheet software that cannot handle HTML format data can be handled as CSV format data.
[0029]
More generally, when the client terminal cannot directly handle the data format generated by the device, it is sent to another apparatus equipped with a means for analyzing the data, where it can be used in the client terminal. After conversion, it may be transmitted to the client terminal. Specifically, when an application of a client terminal requests data related to the device itself, it is determined whether or not the application can directly handle the data. When it is determined that the application does not include XML analysis means, the data is transmitted to another device having analysis means for converting the data into a format that can be decoded by the application, while an instruction for acquiring the data from the device is transmitted. The embedded information is transmitted to the client terminal application. This allows the application to access the device and display the converted data. That is, data in a format that cannot be handled by the client terminal is received after being converted into a usable format, so that it can be processed by the client terminal.
[0030]
【The invention's effect】
Even if the display application installed in the client terminal cannot handle the data format generated by the device, the data can be displayed.
[Brief description of the drawings]
1 is a block diagram of a network system. FIG. 2 is a diagram of an example of XML data of management information. FIG. 3 is a diagram of an example of a style sheet. FIG. 4 is a block diagram of a multi-function device. Block diagram of the apparatus [Fig. 6] Block diagram of the client terminal [Fig. 7] Diagram of an example of HTML data generated by the device [Fig. 8] Flow chart of the XML data generation unit of the device [Fig. Flow chart [Explanation of symbols]
100 device (MFP etc.) 100, 106 controller, 110 communication device, 114 CPU, 116 storage device (HDD), 120 state management program, 122 web browser, 136 web server, 140 transfer destination storage unit, 200 device management device, 202 CPU, 208 storage device, 210 communication device, 220 management program, 222 web server, 224 XML analysis unit, 300 client terminal, 302 CPU, 308 storage device, 310 communication device, 320 web browser, 322 XML analysis unit, 400 network.

Claims (3)

A device connected to a client terminal and a server device via a network,
Storage means for holding XML data describing data relating to the device itself and a style sheet for displaying the data;
When an application of the client terminal requests the XML data, determination means for determining whether or not the application has XML analysis means;
When the determination unit determines that the application of the client terminal does not include an XML analysis unit, the XML data is transmitted to the server device having an analysis unit that converts the XML data into a format that can be decoded by the application. And a data transmission means for transmitting information incorporating a command for acquiring the XML data from the server device to the application.   The device according to claim 1, wherein the device is an image forming apparatus, and the data relating to the device itself is data representing an internal state of the image forming apparatus. Furthermore, it comprises web server means for providing the XML data,
When the application requests the XML data from the web server means, the determination means determines whether the application has an XML analysis means,
The device according to claim 1, wherein the data transmission unit causes the web server unit to transmit the XML data.

Images