EP1698969A2 - Erkennung und Konvertierung eines Kommandozeilendatentyps - Google Patents

Erkennung und Konvertierung eines Kommandozeilendatentyps Download PDF

Info

Publication number
EP1698969A2
EP1698969A2 EP06101696A EP06101696A EP1698969A2 EP 1698969 A2 EP1698969 A2 EP 1698969A2 EP 06101696 A EP06101696 A EP 06101696A EP 06101696 A EP06101696 A EP 06101696A EP 1698969 A2 EP1698969 A2 EP 1698969A2
Authority
EP
European Patent Office
Prior art keywords
command
data
acceptable
downstream
upstream
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP06101696A
Other languages
English (en)
French (fr)
Other versions
EP1698969A3 (de
Inventor
Hitesh Raigandhi
Jeffrey D. Jones
Jeffrey P. Snover
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Publication of EP1698969A2 publication Critical patent/EP1698969A2/de
Publication of EP1698969A3 publication Critical patent/EP1698969A3/de
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09F—DISPLAYING; ADVERTISING; SIGNS; LABELS OR NAME-PLATES; SEALS
    • G09F11/00—Indicating arrangements for variable information in which the complete information is permanently attached to a movable support which brings it to the display position
    • G09F11/02—Indicating arrangements for variable information in which the complete information is permanently attached to a movable support which brings it to the display position the display elements being secured to rotating members, e.g. drums, spindles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
    • G06F9/45512—Command shells

Definitions

  • This invention relates to command lines and command-line interfaces.
  • a color printer Assume that the user selects to find and configure a color printer through a graphical user interface. If his company has 127 printers distributed though ten buildings, for instance, a drop down list of available printers may show each of these 127 printers. By reading through properties for each of these listed printers, the user determines that eighteen of these printers can print in color and that one of these eighteen is located in his building. Armed with the name of this color printer, the user may then choose to configure the printer, such as through a graphical user interface. Once complete, the user can send color print jobs to this printer.
  • a command line interface permits a user to find and use information with greater speed, efficiency, or power than a graphical user interface.
  • the user studies properties for 127 printers to find the one he wants. That may take considerable time.
  • a user finds and configures the color printer through a command line interface.
  • a user often has two options in a situation like this. In the first, he enters a first command line (e.g., "get_printer"), reads its output, finds the printer he is looking for, and types another command line with the found information as input to the second command (e.g., "Configure-Printer printername").
  • a first command line e.g., "get_printer”
  • the first command line outputs TEXT-encoded data (which is human readable) with a particular format and that the user has to read through it.
  • the user has to enter a second command and enter the found information in a format and encoding usable by the second command. In many cases, this first option may also take considerable time.
  • a command line interface In the second option, a command line interface, often through its "shell", automates much of the user's actions with script.
  • a user enters a command line comprising the first and second commands (and a new third command) and other information that, in total, is used to find the printer and configure it.
  • the command line might read:
  • Commands are type-specific; they generally accept and output data in a particular type (e.g., encoded and formatted in XML). If the first command “get_printer” generates TEXT-encoded and formatted data but the "Configure-Printer” command does not accept TEXT-encoded and formatted data exactly, the Configure-Printer command will fail.
  • Systems and/or methods are presented that may be used to enable operation of a command line having an upstream command and a downstream command in which an upstream command outputs data of a type that may be unacceptable as input to the downstream command.
  • the systems and/or methods may comprise, for example, a command-line data-stream protocol in which output from an upstream command in a command line is received having a tag sufficient to enable a determination of a data type associated with the output.
  • the associated data may be converted to a data type that is acceptable as input to a downstream command.
  • a command-line data-stream protocol receives output from an upstream command in a command line.
  • the received output has a tag that is sufficient to enable the output's data type to be determined.
  • An acceptable data type of a downstream command in the command line into which the output is to be received as input is also determined. If the output's data type is not compatible with the downstream command's data type, the output's data type is converted to a compatible data type for the downstream command.
  • a command-line shell determines types of data that may be output by an upstream command and types of data acceptable as input by a downstream command. If one of the types of data that may be output is acceptable as input to the downstream command, the shell directs the upstream command to output its data with this type. If, on the other hand, the command-line shell determines that none of the types of data that may be output are acceptable as input to the downstream command, the command-line shell may direct the upstream command to output the data with a type convertible to one of the types of data acceptable as input. The shell may then invoke a conversion command to convert the data type of the output to be one acceptable as input.
  • output from a command is encoded to comprise a tag.
  • This tag may comprise a preamble to the data output containing information sufficient to enable determination of the output's data type, such as it being structured data like Comma Separated Values (CSV) or eXtensible Markup Language (XML) having a particular schema.
  • CSV Comma Separated Values
  • XML eXtensible Markup Language
  • Fig. 1 shows an architecture generally at 100 comprising a computing device 102 and various components within or accessible by the computing device.
  • the computing device comprises one or more processors 104 and computer-readable media 106.
  • the computer-readable media embodies software code that provides a command-line interface 108, a command-line shell 110, commands 112, and converters 114.
  • a plurality of commands 110 are shown having various potential input and output types.
  • a get printer command 116 is capable of accepting and outputting data of TEXT and CSV types
  • a configure printer command 118 is capable of accepting and outputting CSV and XML types
  • a pause printer command 120 is capable of accepting and outputting ASN. and XML types.
  • a plurality of converters 114 are also shown and are capable of converting output of one or more of commands 112 from one data type to another, such as a CSV-to-XML converter 122, an XML-to-CSV converter 124, a TEXT-to-XML converter 126, an ASN.1-to-XML converter 128, and an XML-to-ASN.1 converter 130.
  • the command-line interface receives a command line entry, such as one entered by a user of the computing device, and performs or otherwise executes associated commands.
  • the command-line shell manages commands in the command line, such as by creating processes for each command within the command line and managing input and output between the processes for these commands.
  • the tools described above and below can enable operation of command lines having an upstream command and a downstream command in which the upstream command may output data of a type unacceptable as input to the downstream command.
  • the tools do so through an encoding and conversion protocol.
  • the conversion aspect of the protocol may be invoked within the command line itself or externally, such as by the command-line shell.
  • the tools enable operation without an encoding and conversion protocol.
  • a command line may have a conversion invoked within the command line for one upstream-downstream pair, another conversion invoked by the shell for a second upstream-downstream pair, and input to a downstream command made acceptable automatically by detecting and directing the upstream command's output for a third upstream-downstream pair.
  • a process 200 has an exemplary encoding and conversion protocol in which the conversion is externally invoked.
  • the process 200 is illustrated as a series of blocks representing individual operations or acts performed by elements of the computing device, such as command-line interface 108, command-line shell 110, and converters 114.
  • This and other processes described herein may be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In the case of software and firmware, these processes represent sets of operations implemented as computer-executable instructions.
  • a command line is received.
  • This command line may be received from a user of computing device 102, such as from a user who types a command line into command-line interface 108.
  • the command line may comprise multiple commands, such as one or more upstream commands and one or more downstream commands.
  • a command line is received having the following syntax:
  • the command line has an upstream command of "GET-PRINTER” and a downstream command of "PAUSE-PRINTER". These commands are shown in Figure 1 at 116 and 120.
  • This command line requests data for the printer(s) that are accessible by the computing device having the system name of "PRINTSRV10". In addition, this command requests that the printer(s) be paused.
  • the output of the upstream command (the data for the "PRINTERSRV10" printers) may, if possible, be piped to the pause printer command as input.
  • the default type of output of the get printer command is Comma Separated Values (CSV).
  • CSV Comma Separated Values
  • the pause printer command accepts only ASN.1 (Abstract Syntax Notation One) or XML-type (extensible Markup Language-type) input.
  • the upstream command outputs data having a type that is unacceptable as input to a downstream command.
  • the get printer command found six printers with a system name of "PRINTSRV10" and produced this output in CSV format. If this CSV-type data is fed to the downstream pause printer command, the pause printer command will not accept this data, causing the command line to fail. Encoding and conversion protocols illustrated below, however, may be used to enable the operation of the command line even though the pause printer command does not accept CSV formats.
  • the output of the upstream command is encoded with information sufficient to enable determination of the type of the data output, such as it being CSV or XML.
  • This encoding is within the data stream of the output itself, such as with a data stream tag.
  • the data stream tag comprises a preamble to the data. This preamble may comprise information indicating the type of data and other information about the data, like a schema governing the data and the like.
  • This encoding may be performed in various ways.
  • the upstream command is built or altered such that it automatically encodes its output.
  • the shell receives the output and then encodes that output.
  • command-line shell manages the commands in the command line, such as by breaking the command line into processes for each command and then acting to manage these processes.
  • the shell may, for instance, send the output of each upstream command to a following downstream as input.
  • the output is encoded by the upstream command to comprise the above preamble.
  • This preamble has four lines starting with a number sign ("#"). Each of these lines may comprise information about the data, though it may not necessarily comprise output data itself.
  • the first line of the preamble comprises a number sign followed by a greater-than symbol and a space ("#> ").
  • This three-character syntax indicates to a reader of the output that the next information in this line indicates the data type of the output.
  • the next characters "CSV" indicate that the output is of the comma-separated-value type.
  • the other three lines may also indicate additional information about the data.
  • the second line is:
  • This line indicates that the structure of the CSV data is such that the first column is a printer's location, the second a printer's name, the third a printer's state, the fourth a printer's status, the fifth a share name for the printer, and the sixth a system name of the printer. Looking at the first line of output, this is shown with:
  • the location for the first-listed printer which is in the first column of the first line, is "USA/REDMOND, WA/40/FLOOR2/2015".
  • the name is "PRINTSRV10 ⁇ b40-2015-a”.
  • This printer's state is "0", status is "3”, and share name is "b40-2015-a”.
  • this printer's system name is "PRINTSRV10”.
  • the third of the four lines is:
  • This line indicates that the character types in the columns are strings or integers. This can be useful when determining how to handle this data and is another example of information about the output of the upstream command. Looking at the first line of output, this is shown with:
  • the columns have characters that are, as indicated in the preamble, filled with strings, strings, integer(s), integer(s), strings, and strings for columns one through six, respectively.
  • the fourth line is blank following a number sign, though it may contain additional information in some embodiments.
  • the fifth line is blank and does not have a number sign character to start. This indicates that the next line is data, rather than information about that data.
  • the method determines the data type of the encoded data.
  • the downstream command receiving the data and/or the shell may determine the data type of the encoded data, such as its encoding schema, for instance.
  • the type of data is determined by reading the first line of the preamble of the encoded data. This line indicates that the data's data type is CSV Other information may also be read to determine additional information about the output, here what information is in each column and the types of characters in those columns.
  • downstream command and/or the shell are now aware of the data type of the data intended to be sent to the downstream command as input.
  • acceptable data type(s) of the downstream command are determined. In some cases this is done intrinsically, such as when the downstream command receives the data from the upstream command and compares the data type of that data with what it accepts. The shell may also determine this, such as by comparing the downstream command with a database listing acceptable types of input to commands.
  • the downstream command receives the data and executes at block 212. This is shown with the "Yes" path following decision block 210 to block 212. If the data type is not acceptable to the downstream command, the shell or downstream command proceeds along the "No" path to block 214 or, in some cases, skips block 214 and proceeds to block 216.
  • the shell may determine if a converter is available at block 216 that can convert the upstream data's data type to one accessible by the downstream command and invoke that converter at block 218, thereby skipping from block 210 to block 216. Alternatively, if a converter is not available, it can produce an error message at block 220. When invoking the converter the shell may pass the output of the upstream command to the converter as input and take the output of the converter and pass it to the downstream command.
  • the converters may also be invokable with names or indicators buildable by the downstream command.
  • the downstream command may, for instance, take the name of a data type in the preamble, such as "CSV", and build a command to invoke a converter with this data type name and a name for a type acceptable to it.
  • the downstream command has determined that the upstream command's data is output in CSV. It also knows that it can accept ASN.1 or XML. Thus, it may build a command at block 214 of either:
  • the downstream command or the shell may determine that either of these converters are available at block 216. If one of them is available the downstream command proceeds along the "Yes" path to block 218 to invoke the converter as mentioned above. If neither are available the downstream command or shell proceeds along the "No" path to block 220.
  • the shell or downstream command determines that CSV-to-XML converter 122 of Figure 1 is available. The converter is then invoked at block 218. Its output of converted data is sent to the downstream command (pause printer command 120 of Figure 1).
  • the information in the encoded portion of the upstream command's output may be useful to accurately and/or efficiently convert the output.
  • the preamble as set forth above, may comprise this additional information.
  • the converter may use this information to convert the data into a form acceptable to the next downstream command.
  • it may be useful to know what data is where and the format of the characters therein. If the XML output is to be arranged by each printer's location, name, state, status, share name, and system name, for instance, the encoded information may be used to arrange the data from the upstream command to fit a particular structure.
  • the information may also be useful as an aid to parsing the output to locate parts of the upstream command's output, especially in those cases where only a part of the output data is to be passed to the downstream command.
  • the additional encoded information may enable a more efficient and/or accurate parse of the upstream command's output.
  • the upstream command outputs six printers having a system name of "PRINTSRV10". If the downstream command is to receive the share name for the printer, the information in lines two and three of the preamble may be used to more easily find that share name.
  • the second and third lines of the upstream command's encoded output are:
  • the converter may then, based on this encoding, determine that the fifth column comprises the desired share name and that the characters of that column will be a string.
  • the process ends. If operation of the command line is complete, as is the case in the illustrated embodiment, the process ends. If the downstream command's output is to be used by another, further-downstream command, the process may repeat, or process 300 may be followed.
  • the downstream command (with or without the command-line interface or command-line shell) produces an error message at block 220 indicating that a converter is needed to complete the command line entered by the user.
  • This message may, in some cases, indicate a place on the internet where the converter may be downloaded.
  • a user may wish to invoke a converter within the command line itself. By so doing some of the acts of process 200 may be skipped.
  • a command line is received with the following syntax:
  • the output of the upstream command is CSV, though in this case the user requested that the output be in CSV
  • the command downstream of the upstream command is "CONVERT-CSV-TO-XML", which is shown in Figure 1 at 122.
  • the user chooses the converter, and so likely knows that the final downstream command (pause printer 120) accepts XML data.
  • the shell operates to pass the output of the upstream command in CSV to the converter 122 as input in CSV.
  • the shell may then pass the output of the downstream converter to the pause printer command 120 as input in XML.
  • the information in the encoded portion of the upstream command's data stream may be useful to the converter in converting the output.
  • a sometimes difficult and often error-prone parsing of TEXT-formatted output may be avoided by choosing to output data in a structured format (like CSV).
  • Process 300 enables operation of a command line having an upstream command and a downstream command. It may enable the command line's operation through automatic detection and direction of a data type capable of being output by the upstream command that is acceptable to the downstream command. This may be performed, in some cases, without encoding the upstream command's output.
  • the process 300 is illustrated as a series of blocks representing individual operations or acts performed by elements of the computing device, such as command-line shell 110 and converters 114.
  • the process receives a command line.
  • This command line may be received from a user and may be similarly structured to that described as part of block 202 of Figure 2.
  • command-line shell 110 determines types of data that may be output by an upstream command.
  • the command line received is:
  • Get printer command 116 is capable of accepting and outputting data in TEXT and CSV types.
  • the command-line shell determines this at block 304.
  • the shell determines the input data types acceptable to the downstream command. Continuing the illustrated embodiment, the shell determines that configure printer command 118 is capable of accepting and outputting CSV and XML data types.
  • the shell determines if any of the output types of the upstream command are a type acceptable as input to the downstream command. If so, the shell follows the "Yes" path to block 310. If not, the shell follows the "No" path to block 312.
  • the shell directs the upstream command to output data in a format readable by the downstream command.
  • the shell may automatically enable operation of a command line where the output of an upstream command may not be readable by a downstream command. If the upstream command of get printer outputs TEXT-formatted data by default, for instance, the shell will have enabled operation of the command line where it otherwise may have failed.
  • the shell alters the command line from the one received to instead be:
  • the shell directs the upstream command to output data in a format convertible to a format readable by the downstream command.
  • the shell in this embodiment determines that none of the upstream command's outputs may be of a data type acceptable to the downstream command.
  • get printer command 116 is capable of outputting data in TEXT or CSV format and pause printer command 120 is capable of accepting data in ASN.1 or XML format.
  • the shell directs the upstream command to output data in a format convertible to a format readable by the downstream command. Based on the availability of converter CSV-to-XML 122 shown in Figure 1, the shell directs the upstream command to output data in CSV.
  • the shell invokes the appropriate converter at block 314. Continuing the illustrated embodiment, the shell invokes the CSV-to-XML converter to convert the CSV output to XML.
  • the shell (or another application) may do so without altering the command line or may instead alter the command line, such by changing it to:
  • the output of the upstream command is encoded to enable the CSV-to-XML conversion to operate with a potentially higher degree of accuracy and/or the output to more easily or accurately be parsed.
  • This encoding may be performed in any of the manners described above.
  • the downstream command is executed.
  • the printer is found and paused or found and configured.
  • commands are A, B, C, D, and E.
  • Command A is upstream to command B
  • B is upstream to C
  • the tools may enable operation of the command line, such as a desired result of executing command E with the preceding data generated from A through D.
  • the tools may do so even in a situation where: A defaults an output type not acceptable to B but where the tools direct A to output the data in a type that is acceptable to B; B outputs a type convertible to a type acceptable to C where the tools invoke an encoding of the output of B and convert that output and send it to C; C outputs by default a type readable by D; and D outputs a type to E that is convertible to a type readable by E but where no encoding of the output of D is performed.
  • This example is given to show the flexibility of the tools.
  • the number and complexity of the commands in a command line may be nearly arbitrary and the command line may still operate using the tools set forth herein.
  • the systems and/or methods described above may be used to enable operation of a command line having an upstream command and a downstream command where the upstream command outputs data of a type unacceptable as input to the downstream command. These systems and/or methods may do so through an encoding and conversion protocol or through a process whereby data types output from the upstream command are automatically detected and directed to be of a type acceptable to the downstream command.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)
EP06101696A 2005-03-04 2006-02-15 Erkennung und Konvertierung eines Kommandozeilendatentyps Ceased EP1698969A3 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11/072,095 US8566806B2 (en) 2005-03-04 2005-03-04 Command-line data-type discovery and conversion

Publications (2)

Publication Number Publication Date
EP1698969A2 true EP1698969A2 (de) 2006-09-06
EP1698969A3 EP1698969A3 (de) 2007-11-07

Family

ID=36616871

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06101696A Ceased EP1698969A3 (de) 2005-03-04 2006-02-15 Erkennung und Konvertierung eines Kommandozeilendatentyps

Country Status (5)

Country Link
US (1) US8566806B2 (de)
EP (1) EP1698969A3 (de)
JP (1) JP5037828B2 (de)
KR (1) KR20060096271A (de)
CN (1) CN1828591B (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2924568A1 (de) * 2014-03-28 2015-09-30 Xiaomi Inc. Ausführungsverfahren und Vorrichtung für Programm-String

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7933964B2 (en) * 2006-02-16 2011-04-26 Microsoft Corporation Shell sessions
US7933986B2 (en) * 2006-02-16 2011-04-26 Microsoft Corporation Transferring command-lines as a message
KR101021416B1 (ko) * 2009-08-03 2011-03-14 한국광기술원 파장변환기둥들을 구비하는 발광다이오드 및 이의 제조방법
US9244706B2 (en) * 2010-05-27 2016-01-26 Microsoft Technology Licensing, Llc Command line shell command generation based on schema
JP6115025B2 (ja) * 2012-05-22 2017-04-19 セイコーエプソン株式会社 媒体処理装置、及び、ｐｏｓシステム
CN103455307B (zh) * 2012-05-29 2018-02-23 腾讯科技（深圳）有限公司 对命令行输出的信息进行处理的方法和装置
CN106339272B (zh) * 2015-07-07 2020-10-02 中兴通讯股份有限公司 一种恢复设备数据的方法和装置
US10114907B2 (en) * 2015-11-13 2018-10-30 International Business Machines Corporation Query processing for XML data using big data technology
CN106802882B (zh) * 2016-12-29 2020-03-06 杭州迪普科技股份有限公司 一种检测命令行界面编码方式的方法及装置
US10545737B2 (en) * 2017-06-13 2020-01-28 Microsoft Technology Licensing, Llc Model binding for command line parsers
US11426633B2 (en) * 2019-02-12 2022-08-30 Ifit Inc. Controlling an exercise machine using a video workout program
CN110008003A (zh) * 2019-04-10 2019-07-12 苏州浪潮智能科技有限公司 一种命令行有效性检测方法及相关装置
US20230244464A1 (en) * 2022-01-31 2023-08-03 Hewlett Packard Enterprise Development Lp Environment establishment for a program in a server system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050091586A1 (en) * 2003-10-24 2005-04-28 Snover Jeffrey P. Mechanism for providing data driven command line output

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5987504A (en) * 1996-12-31 1999-11-16 Intel Corporation Method and apparatus for delivering data
US6216152B1 (en) 1997-10-27 2001-04-10 Sun Microsystems, Inc. Method and apparatus for providing plug in media decoders
CN1087454C (zh) * 1998-02-27 2002-07-10 英业达股份有限公司 WinCE作业环境下的数据结构处理方法
CN1146821C (zh) * 2000-02-21 2004-04-21 国际商业机器公司 面向用户的数据库查询方法及系统
JP4752137B2 (ja) 2001-05-28 2011-08-17 ヤマハ株式会社 入力データの変換方法、入力データの変換プログラム、および入力データの変換システム
JP4072381B2 (ja) 2002-06-07 2008-04-09 Ｎｅｃソフト株式会社 グラフィカル・ユーザ・インタフェースの構築方法及びプログラム
US7620959B2 (en) 2003-05-12 2009-11-17 Microsoft Corporation Reflection-based processing of input parameters for commands
US7526770B2 (en) 2003-05-12 2009-04-28 Microsoft Corporation System and method for employing object-based pipelines
US7168063B2 (en) * 2003-06-10 2007-01-23 Microsoft Corporation Systems and methods for employing tagged types in a dynamic runtime environment
US7290012B2 (en) * 2004-01-16 2007-10-30 International Business Machines Corporation Apparatus, system, and method for passing data between an extensible markup language document and a hierarchical database

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050091586A1 (en) * 2003-10-24 2005-04-28 Snover Jeffrey P. Mechanism for providing data driven command line output

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2924568A1 (de) * 2014-03-28 2015-09-30 Xiaomi Inc. Ausführungsverfahren und Vorrichtung für Programm-String
RU2621974C2 (ru) * 2014-03-28 2017-06-08 Сяоми Инк. Способ и устройство для выполнения программной строки
US9740524B2 (en) 2014-03-28 2017-08-22 Xiaomi Inc. Method and terminal device for executing application chain

Also Published As

Publication number Publication date
KR20060096271A (ko) 2006-09-11
US20060197967A1 (en) 2006-09-07
CN1828591B (zh) 2011-07-27
EP1698969A3 (de) 2007-11-07
JP2006244471A (ja) 2006-09-14
CN1828591A (zh) 2006-09-06
JP5037828B2 (ja) 2012-10-03
US8566806B2 (en) 2013-10-22

Similar Documents

Publication Publication Date Title
US8566806B2 (en) Command-line data-type discovery and conversion
JP4540495B2 (ja) データ処理装置、データ処理方法、データ処理プログラム、および記録媒体
US7099958B2 (en) System for designing and performing web application
WO2003081443A1 (fr) Dispositif de formation d'images comportant une fonction de service web
US20090241024A1 (en) Information processing apparatus, information processing method, and printing system
JP2005196751A (ja) プリントサブシステムのデスプーリングバックプレーン
US7861182B2 (en) Dynamic printer driver user interface generation
JP2011086291A (ja) システムランドスケープ対応アプリケーション間通信インフラストラクチャ
US20020147747A1 (en) System for converting data to a markup language
US20130033725A1 (en) Information processing apparatus, control method, and storage medium
US20060271850A1 (en) Method and apparatus for transforming a printer into an XML printer
JP2000155722A (ja) 電子メ―ル送信装置、電子メ―ル送信方法、及び記録媒体
US20040168064A1 (en) System of generating procedure for digital signature and encryption to XML
US20070143666A1 (en) Architecture for arbitrary extensible markup language processing engine
JP2005310171A (ja) プログラム生成処理をコンピュータに行わせるためのコンピュータ読み取り可能なプログラム
JP3831352B2 (ja) プログラム生成処理をコンピュータに行わせるためのコンピュータ読み取り可能なプログラム
US7505170B2 (en) Conversions between spool files and PDL within a pipeline of modular filters
US20050177788A1 (en) Text to XML transformer and method
US8321484B2 (en) Minimizing bandwidth in file path-centric protocol message
JP6372075B2 (ja) 情報処理装置、情報処理方法及びプログラム
JP4715104B2 (ja) 汎用ｇｕｉ装置及び汎用ｇｕｉプログラム
JP4373692B2 (ja) Ｗｅｂサービス機能を有する画像形成装置
JP2000122837A (ja) 情報処理装置、情報処理方法、及びコンピュータ読み取り可能なプログラムが格納された記憶媒体
JP4447373B2 (ja) データ交換計算機
JP7331402B2 (ja) フロー生成装置及びフロー生成プログラム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17P Request for examination filed

Effective date: 20071206

17Q First examination report despatched

Effective date: 20080123

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20170527