JP6163853B2 - Program and data conversion method - Google Patents

Description

  The present invention relates to a program and a data conversion method.

  For the purpose of improving the overall work efficiency and reducing the work cost, a print job conversion method for automatically transmitting / receiving and converting a print job between a plurality of printing systems having different functions is conventionally known (for example, Patent Document 1).

  A program using work instruction data such as a job ticket can be linked with other programs using the work instruction data. However, a program that uses work instruction data may have different settings that can be used in the work instruction data from other programs. In addition, a program that uses work instruction data may change settings that can be used in the work instruction data, such as when upgrading.

  As described above, when a program using work instruction data is to be linked with another program, it is not easy to manage settings that can be used in the work instruction data.

  An embodiment of the present invention has been made in view of the above points, and an object thereof is to provide a program and a data conversion method that can easily cope with a change in settings that can be used in work instruction data.

In order to achieve the above object, claim 1 of the present application claims that the first work instruction data of the first work instruction data is obtained from setting information that describes use conditions for setting the first work instruction data that causes a computer to coordinate processing among a plurality of programs. First setting candidate acquisition means for acquiring setting candidates that can be used in a transmission destination program; first setting for acquiring all settings from second work instruction data having a data format different from that of the first work instruction data Of the settings acquired from the acquisition means, the second work instruction data, the settings included in the setting candidates that can be used in the transmission destination program of the first work instruction data are the first work instruction data. set between the first first work instruction data generating means for generating a work order data, the second setting acquisition hand to get all the settings from the first work instruction data , Second setting candidate acquisition means for acquiring setting candidates usable in the program that is the source of the second work instruction data from the setting information, and among the settings acquired from the first work instruction data, the first The second work instruction for generating the second work instruction data is set as the setting of the second work instruction data as a setting included in the setting candidates that can be used in the second work instruction data receiving source program. It is a program for functioning as data generation means .

  According to one embodiment of the present invention, it is possible to easily cope with a change in settings available in work instruction data.

It is a hardware block diagram of an example of the computer system which concerns on this embodiment. It is a figure explaining an example of the data flow between the application programs which concern on this embodiment. It is a figure explaining an example of the edit mode of the application program which concerns on this embodiment. It is a figure explaining an example of the job ticket classified by edit mode. It is a processing block diagram of an example of the computer system which started the application program concerning this embodiment. FIG. 10 is a sequence diagram illustrating an example of processing when a job ticket is input to an application program. It is a figure explaining an example of a setting file. It is a figure explaining an example of each attribute and attribute value of a setting file. FIG. 10 is a sequence diagram illustrating an example of processing when a job ticket is output from an application program. It is an example flowchart showing the set value candidate acquisition process of steps S3 and S13.

Next, modes for carrying out the present invention will be described based on the following embodiments with reference to the drawings.
[First Embodiment]
FIG. 1 is a hardware configuration diagram of an example of a computer system according to the present embodiment. The computer system 500 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, and the like, which are mutually connected via a bus B.

  The input device 501 includes a keyboard, a mouse, a touch panel, and the like, and is used by a user to input each operation signal. The display device 502 includes a display and the like, and displays a processing result by the computer system 500.

  The communication I / F 507 is an interface that connects the computer system 500 to a network (not shown). Thereby, the computer system 500 can perform data communication via the communication I / F 507.

  An HDD (Hard Disk Drive) 508 is a non-volatile storage device that stores programs and data. Examples of the stored programs and data include an OS (Operating System) that is a basic program for controlling the entire computer system 500 and application programs that provide various functions on the OS. The HDD 508 manages stored programs and data by a predetermined file system and / or DB (database).

  The external I / F 503 is an interface with an external device. The external device includes a recording medium 503a. Accordingly, the computer system 500 can read and / or write the recording medium 503a via the external I / F 503. Examples of the recording medium 503a include a flexible disk, a compact disk, a DVD (Digital Versatile Disk), and the like. The recording medium 503a includes an SD (Secure Digital) memory card, a USB (Universal Serial Bus) memory, and the like.

  A ROM (Read Only Memory) 505 is a nonvolatile semiconductor memory (storage device) that can hold programs and data even when the power is turned off. The ROM 505 stores programs and data such as BIOS (Basic Input / Output System), OS settings, and network settings that are executed when the computer system 500 is started.

  A RAM (Random Access Memory) 504 is a volatile semiconductor memory (storage device) that temporarily stores programs and data. A CPU (Central Processing Unit) 506 is an arithmetic device that implements control and functions of the entire computer system 500 by reading programs and data from a storage device such as the ROM 505 and the HDD 508 onto the RAM 504 and executing the processing.

  By operating on the hardware configuration of such a computer system 500, an application program described later can realize various processes described later.

  FIG. 2 is a diagram for explaining an example of a data flow between application programs according to the present embodiment. FIG. 2 shows an application program 10 and two related application programs 11 and 12 as an example of the application program.

  An application program (hereinafter simply referred to as an application) 10 is, for example, prepress software. The app 10 cooperates with the related apps 11 and 12 to generate a workflow having one or more processing steps. For the cooperation between the application 10 and the related applications 11 and 12, a job ticket (JDF in FIG. 2) and document data (PDF in FIG. 2) are used.

  The job ticket is an example of print instruction data. The job ticket is expressed by JDF as an example of a data format. JDF is described in, for example, an XML format. The document data is an example of content data.

  It is assumed that the application 10 manages settings that cannot be expressed by a job ticket using RJF as an example of a unique data format. Assume that the related applications 11 and 12 manage settings that can be expressed by job tickets using JDF. For example, when the function of the application 10 precedes the functions of the related applications 11 and 12, it is conceivable to manage the settings using different data formats.

  The application 10 and the related applications 11 and 12 use a job ticket API described later. For example, the setting range that can be expressed by the job ticket differs depending on the version of the job ticket API. As described above, the application 10 and the related applications 11 and 12 have different settings that can be used in the job ticket depending on the version of the job ticket API used.

  Since the application 10 manages settings that cannot be expressed by the job ticket using the RJF, it is necessary to consider settings that cannot be used by the related applications 11 and 12 when generating the job ticket. Therefore, the application 10 automatically converts the job ticket transmitted / received to / from the related applications 11 and 12 according to the related applications 11 and 12 of the transmission destination so as to compensate for the functional difference between the related applications 11 and 12. To do.

  When the application 10 transmits / receives a job ticket to / from the related applications 11 and 12, conversion between RJF and JDF is automatically performed as described later. Therefore, the user does not need to be aware of the functional difference between the application 10 and the related applications 11 and 12. The application 10 can reflect settings that cannot be expressed in JDF among settings that can be expressed in RJF, as will be described later, in the document data (PDF).

  FIG. 3 is a diagram for explaining an example of the editing mode of the application program according to the present embodiment. The application 10 has a JDF mode and an old version compatible mode as job ticket editing modes.

  In the JDF mode, functions that cannot be used by the related applications 11 and 12 are limited. Therefore, in the JDF mode, among the settings expressed in RJF, settings that can be reflected in JDF (can be expressed in JDF) are reflected in the job ticket. On the other hand, the old version compatibility mode can use all the functions of the application 10. Therefore, in the JDF mode, settings that can be reflected in the JDF among the settings expressed in the RJF are reflected in the job ticket, and settings that cannot be reflected in the JDF are reflected in the PDF as described later.

  The application 10 needs to switch the job ticket to be generated depending on the job ticket editing mode and the version of the job ticket API of the related applications 11 and 12 of the transmission destination.

  FIG. 4 is a diagram for explaining an example of a job ticket for each editing mode. FIG. 4A is an image diagram of a job ticket when the aggregation setting can be used in the destination related applications 11 and 12 in the JDF mode. Aggregation settings are reflected in the job ticket in FIG.

  FIG. 4B is an image diagram of a job ticket when the aggregation setting cannot be used in the destination related applications 11 and 12 in the old version compatibility mode. In the job ticket of FIG. 4B, the aggregation setting is not reflected, but is reflected in the document data (PDF).

<Software configuration>
The computer system 500 implements the processing blocks shown in FIG. 5, for example, by executing a program such as the application 10. FIG. 5 is a processing block diagram of an example of a computer system that starts an application program according to the present embodiment. A computer system 500 in which a program such as the application 10 is activated has a higher module 21, a job ticket input / output module 22, a job ticket API 23, and a setting file 24. In FIG. 5, processing blocks related to job ticket input / output are shown, and processing blocks not used in the description of the present embodiment are omitted.

  The upper module 21 is located above the job ticket input / output module 22 and makes a job ticket input request and a job ticket creation request to the job ticket input / output module 22.

  The job ticket input / output module 22 has a role of converting internal data (RJF) and job ticket (JDF) of the application 10. In response to a job ticket input request, the job ticket input / output module 22 converts the job ticket into internal data. The job ticket input / output module 22 converts internal data into a job ticket in response to a job ticket creation request. At this time, the job ticket input / output module 22 uses the job ticket API 23 to read a setting (setting value) from the job ticket and generate a job ticket.

  The job ticket API 23 provides functions such as reading settings from a job ticket, generating job ticket settings, and generating job tickets. The setting file 24 absorbs available settings that differ depending on the job ticket editing mode and the version of the job ticket API 23 as described later.

  When the job ticket API 23 is upgraded, available settings often change, so the job ticket input / output module 22 of the application 10 cannot easily manage the settings available for the related applications 11 and 12. In the present embodiment, the use of the setting file 24 facilitates management of setting values that can be used in the job ticket.

  FIG. 6 is a sequence diagram illustrating an example of processing when a job ticket is input to the application program.

  In step S <b> 1, the upper module 21 issues a job ticket input request to the job ticket input / output module 22. The job ticket input request includes a job ticket and edit mode information.

  In step S <b> 2, the job ticket input / output module 22 reads all settings from the job ticket using the job ticket API 23. In step S3, the job ticket input / output module 22 acquires setting value candidates from the setting file 24 as follows.

  The job ticket input / output module 22 acquires the correspondence between the job ticket setting keyword, the editing mode, and the version of the job ticket API 23 from the setting file 24. A keyword for setting a job ticket that matches the version of the edit mode and the job ticket API 23 is a set value candidate.

  FIG. 7 is a diagram for explaining an example of a setting file. The setting file in FIG. 7 is described in the XML format. The setting file 24 includes an object “Object” used in the job ticket API 23 and an object attribute “Attribute”. Each attribute and attribute value are as shown in FIG.

  FIG. 8 is a diagram for explaining an example of each attribute and attribute value of the setting file. As shown in FIG. 8, the attribute “Class” is an object type defined by the job ticket API 23.

  The attribute “Name” is an attribute name defined in the job ticket API 23 and is a keyword for setting a job ticket. The attribute “FunctionKey” is an attribute name defined in internal data (RJF) corresponding to the setting of the job ticket. The attribute “Class” is an attribute type defined in the internal data.

  The attribute “JtapiVersion” is a version of the job ticket API 23 that can use the setting. A plurality of attributes “JtapiVersion” can be set by separating them with a semicolon. The attribute “EditMode” is a job ticket editing mode in which settings can be used. The attribute “EditMode” can set “JDFMode” representing the JDF mode or “MRMode” representing the old version compatibility mode as the job ticket editing mode. A plurality of attributes “EditMode” can be set by separating them with a semicolon.

  For example, in the setting file of FIG. 7, when “JDFMode” is set in the attribute “EditMode”, it means that the setting of the job ticket becomes a setting value candidate when the edit mode is the JDF mode. .

  Returning to step S4 in FIG. 6, the job ticket input / output module 22 converts the settings included in the setting value candidates acquired in step S3 out of all the settings acquired in step S2 into internal data.

  FIG. 9 is a sequence diagram illustrating an example of processing when a job ticket is output from an application program.

  In step S <b> 11, the upper module 21 makes a job ticket creation request to the job ticket input / output module 22. The job ticket creation request includes internal data (RJF), editing mode information, and job ticket API 23 version information.

  In step S12, the job ticket input / output module 22 reads all settings from the internal data. The job ticket input / output module 22 converts the settings read from the internal data into job ticket settings. In step S13, the job ticket input / output module 22 acquires setting value candidates from the setting file 24 in the same manner as in step S3.

  In step S14, the job ticket input / output module 22 generates a setting value by using the setting included in the setting value candidate acquired in step S13 among all the settings converted from the internal data in step S12. To do. The job ticket input / output module 22 excludes the settings that are not included in the setting value candidates acquired in step S13 from all the settings converted from the internal data in step S12. The excluded setting is reflected in the document data (PDF) as described above.

  In step S15, the job ticket input / output module 22 uses the job ticket API 23 to generate a job ticket reflecting the setting generated in step S14. The generated job ticket is output to the upper module 21.

  FIG. 10 is a flowchart illustrating an example of setting value candidate acquisition processing in steps S3 and S13.

  In step S21, the job ticket input / output module 22 loads the setting file 24 described in the XML format, and acquires a setting value candidate list. In step S <b> 22, the job ticket input / output module 22 selects a setting value candidate having the same attribute “Name” from the setting value candidate list.

  In step S22, the job ticket input / output module 22 selects a setting value candidate having the same attribute “JtapiVersion” from the setting value candidate list selected in step S22. In step S23, the job ticket input / output module 22 selects a setting value candidate having the same attribute “EditMode” from the setting value candidate list selected in step S23.

  The set value candidates selected in step S23 are set value candidates acquired from the setting file 24 in step S3. Note that the setting value candidates not selected in steps S21 to S23 are excluded from the setting value candidates acquired from the setting file 24 in step S3.

<Summary>
The application 10 according to the present embodiment can change job ticket settings depending on conditions such as the job ticket editing mode and the version of the job ticket API 23. The application 10 first acquires all the settings from the setting file 24, and then selects the setting value of the job ticket to be actually used according to the conditions (use conditions) as shown in FIG.

  In this embodiment, since the conditions shown in FIG. 10 are described in the external setting file 24, it is possible to easily cope with job ticket changes such as addition and deletion of settings when the job ticket API 23 is upgraded.

  In this embodiment, the application 10 to which a job ticket is input can select a setting that can be used according to the job ticket editing mode and the version of the job ticket API 23 from the setting of the job ticket.

  In the present embodiment, the application 10 that outputs a job ticket can select settings that can be used by the related applications 11 and 12 of the transmission destination according to the job ticket editing mode and the version of the job ticket API 23.

  As described above, in the present embodiment, when the application 10 and the related applications 11 and 12 try to cooperate with each other with a job ticket, it is possible to easily cope with a change in settings that can be used with the job ticket.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

  Note that the first work instruction data described in the claims corresponds to a job ticket (JDF). The second work instruction data corresponds to internal data (RJF). The first setting candidate acquisition unit and the first setting unit correspond to the job ticket input / output module 22. The first work instruction data generation unit corresponds to the job ticket API 23. The setting information corresponds to the setting file 24. The reception source program corresponds to the application 10.

  The second setting acquisition unit corresponds to the job ticket API 23. The second setting candidate acquisition unit and the second work instruction data generation unit correspond to the job ticket input / output module 22. The version information of the first work instruction data generation unit corresponds to the version of the job ticket API 23. The first editing mode corresponds to the JDF mode. The second editing mode corresponds to the old version compatibility mode.

10 Application Program 11, 12 Related Application Program 21 Upper Module 22 Job Ticket Input / Output Module 23 Job Ticket API
24 setting file 500 computer system 501 input device 502 display device 503 external I / F
503a Recording medium 504 RAM
505 ROM
506 CPU
507 Communication I / F
508 HDD
B bus

JP 2007-156671 A

Claims (4)

Computer
A first setting candidate that can be used in a transmission destination program of the first work instruction data is obtained from setting information that describes use conditions for setting the first work instruction data for linking processes between a plurality of programs. Setting candidate acquisition means,
First setting acquisition means for acquiring all settings from second work instruction data having a data format different from that of the first work instruction data;
Of the settings acquired from the second work instruction data, a setting included in a setting candidate that can be used in the transmission program of the first work instruction data is set as the first work instruction data setting. First work instruction data generating means for generating the first work instruction data ;
Second setting acquisition means for acquiring all settings from the first work instruction data;
Second setting candidate acquisition means for acquiring setting candidates that can be used in the program from which the second work instruction data is received from the setting information;
Among the settings acquired from the first work instruction data, a setting included in a setting candidate that can be used in the program from which the second work instruction data is received is set as the second work instruction data setting. A program for functioning as second work instruction data generating means for generating the second work instruction data . The first setting candidate acquisition unit is configured to calculate the first work instruction data editing mode, the version information of the first work instruction data generation unit, and the setting candidates from the setting information in association with each other. claim 1 Symbol placement program and obtains the setting candidate corresponding to the version information of the edit mode and the first work instruction data generating means of the first work instruction data. A first editing mode in which a setting that can be expressed by the first work instruction data among the settings expressed by the second work instruction data is reflected in the first work instruction data; and the second work instruction data Secondly, the setting that can be expressed by the first work instruction data is reflected in the first work instruction data, and the setting that cannot be expressed by the first work instruction data is reflected in the content data. Edit mode, and
The program according to claim 2 , further causing a computer to function as content data editing means for reflecting, in the second editing mode, settings that cannot be expressed by the first work instruction data in the content data. A data conversion method executed by a computer,
A first setting candidate that can be used in a transmission destination program of the first work instruction data is obtained from setting information that describes use conditions for setting the first work instruction data for linking processes between a plurality of programs. A setting candidate acquisition step;
A first setting acquisition step of acquiring all settings from second work instruction data having a data format different from that of the first work instruction data;
Of the settings acquired from the second work instruction data, a setting included in a setting candidate that can be used in the transmission program of the first work instruction data is set as the first work instruction data setting. A first work instruction data generation step for generating the first work instruction data ;
A second setting acquisition step of acquiring all settings from the first work instruction data;
A second setting candidate acquisition step of acquiring a setting candidate usable in the program of the reception source of the second work instruction data from the setting information;
Among the settings acquired from the first work instruction data, a setting included in a setting candidate that can be used in the program from which the second work instruction data is received is set as the second work instruction data setting. And a second work instruction data generation step for generating the second work instruction data .

Images