Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Till Kamppeter]

Great, I think we can go this way. Feel free to add this information to 
the ideas page:

https://www.linux-foundation.org/en/Google_Summer_of_Code

This way we can start having job ticket functionality in 
Linux/Unix/Embedded printing environments and make the application and 
printing system developers start supporting job tickets with our 
standard API. If we have enough consumers of the JTAPI once, we will 
more easily be able to find the man power for developing a JDF backand 
and so all apps will be able to send jobs to professional printing services.

Lars, would you like to do this task?

    Till


Petrie, Glen wrote:
> Till,
> 
>  
> 
> Any feedback – good or bad on the proposal below.
> 
>  
> 
> glen
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* Petrie, Glen
> *Sent:* Wednesday, March 19, 2008 12:35 PM
> *To:* Petrie, Glen; Ira McDonald; Norm Jacobs; Claudia Alimpich; Amanda 
> McPherson; Markus Rex; Jim Zemlin; Dan Kohn; Jeff Licquia; Wichmann, 
> Mats D; Susanne Oberhauser; Theodore Ts'o; Till Kamppeter
> *Subject:* Google Summer of Code 2008: JTAPI Library Project
> 
>  
> 
> Hello All,
> 
>  
> 
> I am going to the mentor for the JTAPI implementation under the Google 
> Summer of Code 2008.  With only three months for the project, the 
> project needs to be scoped to fit within the time frame.   Therefore, I 
> am sending the following proposal to the group for comments and general 
> approval for the group.
> 
>  
> 
> ***Project:
> 
> JTAPI – Library
> 
>  
> 
> ***Objective:
> 
> Using the header files created by the Open-Printing Job-Ticket Working 
> Group develop a platform independent C library for the reading-of, 
> modification-of and storage-of a print job ticket for the Printer 
> Working Group’s (PWG’s) Micro-Job-Ticket (MJT).
> 
>  
> 
> ***Approach:
> 
> 1.   Review OP/JTWG Job-Ticket Application Programming Interface (JTAPI) 
> header documents
> 
> 2.   Review PWG/MJT specification.
> 
> 3.   Create Test MJT’s
> 
> a.   Manually create a minimum of 3 representative MJTs (text files) to 
> be used for testing and evaluation
> 
> 4.   Define the command-line Test Application to exercise the JTAPIs; 
> include an initial set of commands
> 
> 5.   Create Thin-Thread implementation of the individual JTAPIs and the 
> Test Application.
> 
> a.   This will be the first demonstrational implementation and the start 
> code for detailed development.
> 
> b.   This will include minimum documentation on how to use the Test 
> Application
> 
> 6.   Enhance individual JTAPIs and the Test Application to provide full 
> functionality.
> 
> a.   Provided update documentation as required.
> 
> 7.   Project Demonstration.
> 
>  
> 
> ***Code License:
> 
> MIT
> 
>  
> 
> ***Coding Language:
> 
> Platform Independent C
> 
> (No platform or vendor-specific extensions)
> 
>  
> 
> ***Coding Document:
> 
>             In-line commenting must be sufficient to understand the flow 
> and any section requiring extended understanding.
> 
>  
> 
> ***Operating System:
> 
> Student’s choice – Linux or Windows (non-gui for either)
> 
>  
> 
> ***Interface:
> 
> Command Line – GUI not required unless very simple (due to project time 
> constraint)
> 
>  
> 
> ***Document:
> 
>             Minimum:
> 
> 1.   How to build the JTAPI library.
> 
> 2.   How to build the Test Application
> 
> 3.   The Test Application command-line instructions
> 
> 4.   Three examples of using the Test Application and exercising the JTAPIs
> 
>  
> 
>  
> 
> ==============
> 
> 
>       *JTAPI implementation*
> 
> Job tickets are extended descriptions for print jobs. They tell which 
> documents should be printed, on which type of paper, which resolution 
> and quality, whether there should be sheets inserted between the 
> documents, ..., and even information like delivery address, payment, ... 
> A job ticket accompanies a print job from its submission to its 
> delivery. Job tickets come from the professional printing world. In 
> former times they were a paper form with instructions what everyone 
> involved in the printing process has to do. Nowadays they are 
> standardized files <http://en.wikipedia.org/wiki/Job_Definition_Format> 
> which are used by print servers, printers, and production printing 
> machines. These job tickets do not only make sense for large-scale 
> production printing, they are also useful for mobile devices, home 
> desktops, workgroup printers, ... Also access to print services on the 
> internet directly from the desktop applications simply via a print queue 
> would be possible.
> 
> To allow desktop applications, printing systems, and printer drivers to 
> easily create, edit, and read job tickets without needing to deal with 
> the actual job ticket format, the job ticket application programming 
> interface (JTAPI 
> <https://www.linux-foundation.org/en/OpenPrinting/JTAPI>) was developed 
> by OpenPrinting. A complete specification 
> <ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec/fsg-openprinting-job-ticket-api-v0100-20050315.pdf> 
> is published.
> 
> The next step to do is the actual implementation of the JTAPI library 
> and its integration in applications, the CUPS printing system, drivers, 
> filters, ... This will be the task of the student in this Google Summer 
> of Code project.
> 
> Mentor: Glen Petrie, Epson
> 
> Desired knowledge: C Programming
> 
>  
> 

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Ira McDonald]

Hi Glen,

Thanks so much for volunteering to mentor this JTAPI Implementation Project!

Your description above looks very good.

Cheers,
- Ira

On Thu, Mar 20, 2008 at 3:00 PM, Till Kamppeter
<till.kamppeter@gmail.com> wrote:
> Great, I think we can go this way. Feel free to add this information to
>  the ideas page:
>
>  https://www.linux-foundation.org/en/Google_Summer_of_Code
>
>  This way we can start having job ticket functionality in
>  Linux/Unix/Embedded printing environments and make the application and
>  printing system developers start supporting job tickets with our
>  standard API. If we have enough consumers of the JTAPI once, we will
>  more easily be able to find the man power for developing a JDF backand
>  and so all apps will be able to send jobs to professional printing services.
>
>  Lars, would you like to do this task?
>
>     Till
>
>
>  Petrie, Glen wrote:
>  > Till,
>  >
>  >
>  >
>  > Any feedback – good or bad on the proposal below.
>  >
>  >
>  >
>  > glen
>  >
>  >
>  >
>  > ------------------------------------------------------------------------
>  >
>  > *From:* Petrie, Glen
>  > *Sent:* Wednesday, March 19, 2008 12:35 PM
>  > *To:* Petrie, Glen; Ira McDonald; Norm Jacobs; Claudia Alimpich; Amanda
>  > McPherson; Markus Rex; Jim Zemlin; Dan Kohn; Jeff Licquia; Wichmann,
>  > Mats D; Susanne Oberhauser; Theodore Ts'o; Till Kamppeter
>  > *Subject:* Google Summer of Code 2008: JTAPI Library Project
>
>
> >
>  >
>  >
>  > Hello All,
>  >
>  >
>  >
>  > I am going to the mentor for the JTAPI implementation under the Google
>  > Summer of Code 2008.  With only three months for the project, the
>  > project needs to be scoped to fit within the time frame.   Therefore, I
>  > am sending the following proposal to the group for comments and general
>  > approval for the group.
>  >
>  >
>  >
>  > ***Project:
>  >
>  > JTAPI – Library
>  >
>  >
>  >
>  > ***Objective:
>  >
>  > Using the header files created by the Open-Printing Job-Ticket Working
>  > Group develop a platform independent C library for the reading-of,
>  > modification-of and storage-of a print job ticket for the Printer
>  > Working Group's (PWG's) Micro-Job-Ticket (MJT).
>  >
>  >
>  >
>  > ***Approach:
>  >
>  > 1.   Review OP/JTWG Job-Ticket Application Programming Interface (JTAPI)
>  > header documents
>  >
>  > 2.   Review PWG/MJT specification.
>  >
>  > 3.   Create Test MJT's
>  >
>  > a.   Manually create a minimum of 3 representative MJTs (text files) to
>  > be used for testing and evaluation
>  >
>  > 4.   Define the command-line Test Application to exercise the JTAPIs;
>  > include an initial set of commands
>  >
>  > 5.   Create Thin-Thread implementation of the individual JTAPIs and the
>  > Test Application.
>  >
>  > a.   This will be the first demonstrational implementation and the start
>  > code for detailed development.
>  >
>  > b.   This will include minimum documentation on how to use the Test
>  > Application
>  >
>  > 6.   Enhance individual JTAPIs and the Test Application to provide full
>  > functionality.
>  >
>  > a.   Provided update documentation as required.
>  >
>  > 7.   Project Demonstration.
>  >
>  >
>  >
>  > ***Code License:
>  >
>  > MIT
>  >
>  >
>  >
>  > ***Coding Language:
>  >
>  > Platform Independent C
>  >
>  > (No platform or vendor-specific extensions)
>  >
>  >
>  >
>  > ***Coding Document:
>  >
>  >             In-line commenting must be sufficient to understand the flow
>  > and any section requiring extended understanding.
>  >
>  >
>  >
>  > ***Operating System:
>  >
>  > Student's choice – Linux or Windows (non-gui for either)
>  >
>  >
>  >
>  > ***Interface:
>  >
>  > Command Line – GUI not required unless very simple (due to project time
>  > constraint)
>  >
>  >
>  >
>  > ***Document:
>  >
>  >             Minimum:
>  >
>  > 1.   How to build the JTAPI library.
>  >
>  > 2.   How to build the Test Application
>  >
>  > 3.   The Test Application command-line instructions
>  >
>  > 4.   Three examples of using the Test Application and exercising the JTAPIs
>  >
>  >
>  >
>  >
>  >
>  > ==============
>  >
>  >
>  >       *JTAPI implementation*
>  >
>  > Job tickets are extended descriptions for print jobs. They tell which
>  > documents should be printed, on which type of paper, which resolution
>  > and quality, whether there should be sheets inserted between the
>  > documents, ..., and even information like delivery address, payment, ...
>  > A job ticket accompanies a print job from its submission to its
>  > delivery. Job tickets come from the professional printing world. In
>  > former times they were a paper form with instructions what everyone
>  > involved in the printing process has to do. Nowadays they are
>  > standardized files <http://en.wikipedia.org/wiki/Job_Definition_Format>
>
> > which are used by print servers, printers, and production printing
>  > machines. These job tickets do not only make sense for large-scale
>  > production printing, they are also useful for mobile devices, home
>  > desktops, workgroup printers, ... Also access to print services on the
>  > internet directly from the desktop applications simply via a print queue
>  > would be possible.
>  >
>  > To allow desktop applications, printing systems, and printer drivers to
>  > easily create, edit, and read job tickets without needing to deal with
>  > the actual job ticket format, the job ticket application programming
>  > interface (JTAPI
>  > <https://www.linux-foundation.org/en/OpenPrinting/JTAPI>) was developed
>
> > by OpenPrinting. A complete specification
>  > <ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec/fsg-openprinting-job-ticket-api-v0100-20050315.pdf>
>
> > is published.
>  >
>  > The next step to do is the actual implementation of the JTAPI library
>  > and its integration in applications, the CUPS printing system, drivers,
>  > filters, ... This will be the task of the student in this Google Summer
>  > of Code project.
>  >
>  > Mentor: Glen Petrie, Epson
>  >
>  > Desired knowledge: C Programming
>  >
>  >
>  >
>
>  _______________________________________________
>  Printing-architecture mailing list
>  Printing-architecture@lists.linux-foundation.org
>  https://lists.linux-foundation.org/mailman/listinfo/printing-architecture
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
 579 Park Place Saline, MI 48176
 734-944-0094
summer:
 PO Box 221 Grand Marais, MI 49839
 906-494-2434

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Lars Uebernickel]

On Thu, 2008-03-20 at 20:00 +0100, Till Kamppeter wrote:
> Great, I think we can go this way. Feel free to add this information to 
> the ideas page:
> 
> https://www.linux-foundation.org/en/Google_Summer_of_Code
> 
> This way we can start having job ticket functionality in 
> Linux/Unix/Embedded printing environments and make the application and 
> printing system developers start supporting job tickets with our 
> standard API. If we have enough consumers of the JTAPI once, we will 
> more easily be able to find the man power for developing a JDF backand 
> and so all apps will be able to send jobs to professional printing services.
> 
> Lars, would you like to do this task?

Yes, I would definitely like to do it! Thank you, Glen, for the detailed
description - the way you outlined the project sounds very reasonable to
me for a three months time frame.

  Lars


> 
> Petrie, Glen wrote:
> > Till,
> > 
> >  
> > 
> > Any feedback – good or bad on the proposal below.
> > 
> >  
> > 
> > glen
> > 
> >  
> > 
> > ------------------------------------------------------------------------
> > 
> > *From:* Petrie, Glen
> > *Sent:* Wednesday, March 19, 2008 12:35 PM
> > *To:* Petrie, Glen; Ira McDonald; Norm Jacobs; Claudia Alimpich; Amanda 
> > McPherson; Markus Rex; Jim Zemlin; Dan Kohn; Jeff Licquia; Wichmann, 
> > Mats D; Susanne Oberhauser; Theodore Ts'o; Till Kamppeter
> > *Subject:* Google Summer of Code 2008: JTAPI Library Project
> > 
> >  
> > 
> > Hello All,
> > 
> >  
> > 
> > I am going to the mentor for the JTAPI implementation under the Google 
> > Summer of Code 2008.  With only three months for the project, the 
> > project needs to be scoped to fit within the time frame.   Therefore, I 
> > am sending the following proposal to the group for comments and general 
> > approval for the group.
> > 
> >  
> > 
> > ***Project:
> > 
> > JTAPI – Library
> > 
> >  
> > 
> > ***Objective:
> > 
> > Using the header files created by the Open-Printing Job-Ticket Working 
> > Group develop a platform independent C library for the reading-of, 
> > modification-of and storage-of a print job ticket for the Printer 
> > Working Group’s (PWG’s) Micro-Job-Ticket (MJT).
> > 
> >  
> > 
> > ***Approach:
> > 
> > 1.   Review OP/JTWG Job-Ticket Application Programming Interface (JTAPI) 
> > header documents
> > 
> > 2.   Review PWG/MJT specification.
> > 
> > 3.   Create Test MJT’s
> > 
> > a.   Manually create a minimum of 3 representative MJTs (text files) to 
> > be used for testing and evaluation
> > 
> > 4.   Define the command-line Test Application to exercise the JTAPIs; 
> > include an initial set of commands
> > 
> > 5.   Create Thin-Thread implementation of the individual JTAPIs and the 
> > Test Application.
> > 
> > a.   This will be the first demonstrational implementation and the start 
> > code for detailed development.
> > 
> > b.   This will include minimum documentation on how to use the Test 
> > Application
> > 
> > 6.   Enhance individual JTAPIs and the Test Application to provide full 
> > functionality.
> > 
> > a.   Provided update documentation as required.
> > 
> > 7.   Project Demonstration.
> > 
> >  
> > 
> > ***Code License:
> > 
> > MIT
> > 
> >  
> > 
> > ***Coding Language:
> > 
> > Platform Independent C
> > 
> > (No platform or vendor-specific extensions)
> > 
> >  
> > 
> > ***Coding Document:
> > 
> >             In-line commenting must be sufficient to understand the flow 
> > and any section requiring extended understanding.
> > 
> >  
> > 
> > ***Operating System:
> > 
> > Student’s choice – Linux or Windows (non-gui for either)
> > 
> >  
> > 
> > ***Interface:
> > 
> > Command Line – GUI not required unless very simple (due to project time 
> > constraint)
> > 
> >  
> > 
> > ***Document:
> > 
> >             Minimum:
> > 
> > 1.   How to build the JTAPI library.
> > 
> > 2.   How to build the Test Application
> > 
> > 3.   The Test Application command-line instructions
> > 
> > 4.   Three examples of using the Test Application and exercising the JTAPIs
> > 
> >  
> > 
> >  
> > 
> > ==============
> > 
> > 
> >       *JTAPI implementation*
> > 
> > Job tickets are extended descriptions for print jobs. They tell which 
> > documents should be printed, on which type of paper, which resolution 
> > and quality, whether there should be sheets inserted between the 
> > documents, ..., and even information like delivery address, payment, ... 
> > A job ticket accompanies a print job from its submission to its 
> > delivery. Job tickets come from the professional printing world. In 
> > former times they were a paper form with instructions what everyone 
> > involved in the printing process has to do. Nowadays they are 
> > standardized files <http://en.wikipedia.org/wiki/Job_Definition_Format> 
> > which are used by print servers, printers, and production printing 
> > machines. These job tickets do not only make sense for large-scale 
> > production printing, they are also useful for mobile devices, home 
> > desktops, workgroup printers, ... Also access to print services on the 
> > internet directly from the desktop applications simply via a print queue 
> > would be possible.
> > 
> > To allow desktop applications, printing systems, and printer drivers to 
> > easily create, edit, and read job tickets without needing to deal with 
> > the actual job ticket format, the job ticket application programming 
> > interface (JTAPI 
> > <https://www.linux-foundation.org/en/OpenPrinting/JTAPI>) was developed 
> > by OpenPrinting. A complete specification 
> > <ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec/fsg-openprinting-job-ticket-api-v0100-20050315.pdf> 
> > is published.
> > 
> > The next step to do is the actual implementation of the JTAPI library 
> > and its integration in applications, the CUPS printing system, drivers, 
> > filters, ... This will be the task of the student in this Google Summer 
> > of Code project.
> > 
> > Mentor: Glen Petrie, Epson
> > 
> > Desired knowledge: C Programming
> > 
> >  
> > 

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Petrie, Glen]

Lars,

(Sorry for the late reply - took a day off - need those once in while.)

I am glad you are interested in the JTAPI project.  I think you'll find it
fun and it will provide JTAPI the chance to become a main stream part of
Linux printing.

Thanks again for your interest in the JTAPI project.  I look forward to
working with you.

Glen


> -----Original Message-----
> From: Lars Uebernickel [mailto:larsuebernickel@gmx.de]
> Sent: Thursday, March 20, 2008 4:01 PM
> To: Till Kamppeter
> Cc: Petrie, Glen; 'printing-architecture@lists.freestandards.org'
> Subject: Re: Google Summer of Code 2008: JTAPI Library Project
> 
> On Thu, 2008-03-20 at 20:00 +0100, Till Kamppeter wrote:
> > Great, I think we can go this way. Feel free to add this information to
> > the ideas page:
> >
> > https://www.linux-foundation.org/en/Google_Summer_of_Code
> >
> > This way we can start having job ticket functionality in
> > Linux/Unix/Embedded printing environments and make the application and
> > printing system developers start supporting job tickets with our
> > standard API. If we have enough consumers of the JTAPI once, we will
> > more easily be able to find the man power for developing a JDF backand
> > and so all apps will be able to send jobs to professional printing
> services.
> >
> > Lars, would you like to do this task?
> 
> Yes, I would definitely like to do it! Thank you, Glen, for the detailed
> description - the way you outlined the project sounds very reasonable to
> me for a three months time frame.
> 
>   Lars
> 
> 
> >
> > Petrie, Glen wrote:
> > > Till,
> > >
> > >
> > >
> > > Any feedback - good or bad on the proposal below.
> > >
> > >
> > >
> > > glen
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> --
> > >
> > > *From:* Petrie, Glen
> > > *Sent:* Wednesday, March 19, 2008 12:35 PM
> > > *To:* Petrie, Glen; Ira McDonald; Norm Jacobs; Claudia Alimpich;
> Amanda
> > > McPherson; Markus Rex; Jim Zemlin; Dan Kohn; Jeff Licquia; Wichmann,
> > > Mats D; Susanne Oberhauser; Theodore Ts'o; Till Kamppeter
> > > *Subject:* Google Summer of Code 2008: JTAPI Library Project
> > >
> > >
> > >
> > > Hello All,
> > >
> > >
> > >
> > > I am going to the mentor for the JTAPI implementation under the Google
> > > Summer of Code 2008.  With only three months for the project, the
> > > project needs to be scoped to fit within the time frame.   Therefore,
> I
> > > am sending the following proposal to the group for comments and
> general
> > > approval for the group.
> > >
> > >
> > >
> > > ***Project:
> > >
> > > JTAPI - Library
> > >
> > >
> > >
> > > ***Objective:
> > >
> > > Using the header files created by the Open-Printing Job-Ticket Working
> > > Group develop a platform independent C library for the reading-of,
> > > modification-of and storage-of a print job ticket for the Printer
> > > Working Group's (PWG's) Micro-Job-Ticket (MJT).
> > >
> > >
> > >
> > > ***Approach:
> > >
> > > 1.   Review OP/JTWG Job-Ticket Application Programming Interface
> (JTAPI)
> > > header documents
> > >
> > > 2.   Review PWG/MJT specification.
> > >
> > > 3.   Create Test MJT's
> > >
> > > a.   Manually create a minimum of 3 representative MJTs (text files)
> to
> > > be used for testing and evaluation
> > >
> > > 4.   Define the command-line Test Application to exercise the JTAPIs;
> > > include an initial set of commands
> > >
> > > 5.   Create Thin-Thread implementation of the individual JTAPIs and
> the
> > > Test Application.
> > >
> > > a.   This will be the first demonstrational implementation and the
> start
> > > code for detailed development.
> > >
> > > b.   This will include minimum documentation on how to use the Test
> > > Application
> > >
> > > 6.   Enhance individual JTAPIs and the Test Application to provide
> full
> > > functionality.
> > >
> > > a.   Provided update documentation as required.
> > >
> > > 7.   Project Demonstration.
> > >
> > >
> > >
> > > ***Code License:
> > >
> > > MIT
> > >
> > >
> > >
> > > ***Coding Language:
> > >
> > > Platform Independent C
> > >
> > > (No platform or vendor-specific extensions)
> > >
> > >
> > >
> > > ***Coding Document:
> > >
> > >             In-line commenting must be sufficient to understand the
> flow
> > > and any section requiring extended understanding.
> > >
> > >
> > >
> > > ***Operating System:
> > >
> > > Student's choice - Linux or Windows (non-gui for either)
> > >
> > >
> > >
> > > ***Interface:
> > >
> > > Command Line - GUI not required unless very simple (due to project
> time
> > > constraint)
> > >
> > >
> > >
> > > ***Document:
> > >
> > >             Minimum:
> > >
> > > 1.   How to build the JTAPI library.
> > >
> > > 2.   How to build the Test Application
> > >
> > > 3.   The Test Application command-line instructions
> > >
> > > 4.   Three examples of using the Test Application and exercising the
> JTAPIs
> > >
> > >
> > >
> > >
> > >
> > > ==============
> > >
> > >
> > >       *JTAPI implementation*
> > >
> > > Job tickets are extended descriptions for print jobs. They tell which
> > > documents should be printed, on which type of paper, which resolution
> > > and quality, whether there should be sheets inserted between the
> > > documents, ..., and even information like delivery address, payment,
> ...
> > > A job ticket accompanies a print job from its submission to its
> > > delivery. Job tickets come from the professional printing world. In
> > > former times they were a paper form with instructions what everyone
> > > involved in the printing process has to do. Nowadays they are
> > > standardized files
> <http://en.wikipedia.org/wiki/Job_Definition_Format>
> > > which are used by print servers, printers, and production printing
> > > machines. These job tickets do not only make sense for large-scale
> > > production printing, they are also useful for mobile devices, home
> > > desktops, workgroup printers, ... Also access to print services on the
> > > internet directly from the desktop applications simply via a print
> queue
> > > would be possible.
> > >
> > > To allow desktop applications, printing systems, and printer drivers
> to
> > > easily create, edit, and read job tickets without needing to deal with
> > > the actual job ticket format, the job ticket application programming
> > > interface (JTAPI
> > > <https://www.linux-foundation.org/en/OpenPrinting/JTAPI>) was
> developed
> > > by OpenPrinting. A complete specification
> > > <ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec/fsg-openprinting-
> job-ticket-api-v0100-20050315.pdf>
> > > is published.
> > >
> > > The next step to do is the actual implementation of the JTAPI library
> > > and its integration in applications, the CUPS printing system,
> drivers,
> > > filters, ... This will be the task of the student in this Google
> Summer
> > > of Code project.
> > >
> > > Mentor: Glen Petrie, Epson
> > >
> > > Desired knowledge: C Programming
> > >
> > >
> > >

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Petrie, Glen]

All,

During April I have an unusual amount travel and I want to provide my
schedule.

April 7th to April 11th - Linux Foundation Summit Meeting.

April 15th to April 18th - PWG Face-to-Face Meeting.

Glen


> -----Original Message-----
> From: Petrie, Glen
> Sent: Monday, March 24, 2008 7:19 AM
> To: Lars Uebernickel; Till Kamppeter
> Cc: Petrie, Glen; 'printing-architecture@lists.freestandards.org'
> Subject: RE: Google Summer of Code 2008: JTAPI Library Project
> 
> Lars,
> 
> (Sorry for the late reply - took a day off - need those once in while.)
> 
> I am glad you are interested in the JTAPI project.  I think you'll find it
> fun and it will provide JTAPI the chance to become a main stream part of
> Linux printing.
> 
> Thanks again for your interest in the JTAPI project.  I look forward to
> working with you.
> 
> Glen
> 
> 
> > -----Original Message-----
> > From: Lars Uebernickel [mailto:larsuebernickel@gmx.de]
> > Sent: Thursday, March 20, 2008 4:01 PM
> > To: Till Kamppeter
> > Cc: Petrie, Glen; 'printing-architecture@lists.freestandards.org'
> > Subject: Re: Google Summer of Code 2008: JTAPI Library Project
> >
> > On Thu, 2008-03-20 at 20:00 +0100, Till Kamppeter wrote:
> > > Great, I think we can go this way. Feel free to add this information
> to
> > > the ideas page:
> > >
> > > https://www.linux-foundation.org/en/Google_Summer_of_Code
> > >
> > > This way we can start having job ticket functionality in
> > > Linux/Unix/Embedded printing environments and make the application and
> > > printing system developers start supporting job tickets with our
> > > standard API. If we have enough consumers of the JTAPI once, we will
> > > more easily be able to find the man power for developing a JDF backand
> > > and so all apps will be able to send jobs to professional printing
> > services.
> > >
> > > Lars, would you like to do this task?
> >
> > Yes, I would definitely like to do it! Thank you, Glen, for the detailed
> > description - the way you outlined the project sounds very reasonable to
> > me for a three months time frame.
> >
> >   Lars
> >
> >
> > >
> > > Petrie, Glen wrote:
> > > > Till,
> > > >
> > > >
> > > >
> > > > Any feedback - good or bad on the proposal below.
> > > >
> > > >
> > > >
> > > > glen
> > > >
> > > >
> > > >
> > > > --------------------------------------------------------------------
> --
> > --
> > > >
> > > > *From:* Petrie, Glen
> > > > *Sent:* Wednesday, March 19, 2008 12:35 PM
> > > > *To:* Petrie, Glen; Ira McDonald; Norm Jacobs; Claudia Alimpich;
> > Amanda
> > > > McPherson; Markus Rex; Jim Zemlin; Dan Kohn; Jeff Licquia; Wichmann,
> > > > Mats D; Susanne Oberhauser; Theodore Ts'o; Till Kamppeter
> > > > *Subject:* Google Summer of Code 2008: JTAPI Library Project
> > > >
> > > >
> > > >
> > > > Hello All,
> > > >
> > > >
> > > >
> > > > I am going to the mentor for the JTAPI implementation under the
> Google
> > > > Summer of Code 2008.  With only three months for the project, the
> > > > project needs to be scoped to fit within the time frame.
> Therefore,
> > I
> > > > am sending the following proposal to the group for comments and
> > general
> > > > approval for the group.
> > > >
> > > >
> > > >
> > > > ***Project:
> > > >
> > > > JTAPI - Library
> > > >
> > > >
> > > >
> > > > ***Objective:
> > > >
> > > > Using the header files created by the Open-Printing Job-Ticket
> Working
> > > > Group develop a platform independent C library for the reading-of,
> > > > modification-of and storage-of a print job ticket for the Printer
> > > > Working Group's (PWG's) Micro-Job-Ticket (MJT).
> > > >
> > > >
> > > >
> > > > ***Approach:
> > > >
> > > > 1.   Review OP/JTWG Job-Ticket Application Programming Interface
> > (JTAPI)
> > > > header documents
> > > >
> > > > 2.   Review PWG/MJT specification.
> > > >
> > > > 3.   Create Test MJT's
> > > >
> > > > a.   Manually create a minimum of 3 representative MJTs (text files)
> > to
> > > > be used for testing and evaluation
> > > >
> > > > 4.   Define the command-line Test Application to exercise the
> JTAPIs;
> > > > include an initial set of commands
> > > >
> > > > 5.   Create Thin-Thread implementation of the individual JTAPIs and
> > the
> > > > Test Application.
> > > >
> > > > a.   This will be the first demonstrational implementation and the
> > start
> > > > code for detailed development.
> > > >
> > > > b.   This will include minimum documentation on how to use the Test
> > > > Application
> > > >
> > > > 6.   Enhance individual JTAPIs and the Test Application to provide
> > full
> > > > functionality.
> > > >
> > > > a.   Provided update documentation as required.
> > > >
> > > > 7.   Project Demonstration.
> > > >
> > > >
> > > >
> > > > ***Code License:
> > > >
> > > > MIT
> > > >
> > > >
> > > >
> > > > ***Coding Language:
> > > >
> > > > Platform Independent C
> > > >
> > > > (No platform or vendor-specific extensions)
> > > >
> > > >
> > > >
> > > > ***Coding Document:
> > > >
> > > >             In-line commenting must be sufficient to understand the
> > flow
> > > > and any section requiring extended understanding.
> > > >
> > > >
> > > >
> > > > ***Operating System:
> > > >
> > > > Student's choice - Linux or Windows (non-gui for either)
> > > >
> > > >
> > > >
> > > > ***Interface:
> > > >
> > > > Command Line - GUI not required unless very simple (due to project
> > time
> > > > constraint)
> > > >
> > > >
> > > >
> > > > ***Document:
> > > >
> > > >             Minimum:
> > > >
> > > > 1.   How to build the JTAPI library.
> > > >
> > > > 2.   How to build the Test Application
> > > >
> > > > 3.   The Test Application command-line instructions
> > > >
> > > > 4.   Three examples of using the Test Application and exercising the
> > JTAPIs
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ==============
> > > >
> > > >
> > > >       *JTAPI implementation*
> > > >
> > > > Job tickets are extended descriptions for print jobs. They tell
> which
> > > > documents should be printed, on which type of paper, which
> resolution
> > > > and quality, whether there should be sheets inserted between the
> > > > documents, ..., and even information like delivery address, payment,
> > ...
> > > > A job ticket accompanies a print job from its submission to its
> > > > delivery. Job tickets come from the professional printing world. In
> > > > former times they were a paper form with instructions what everyone
> > > > involved in the printing process has to do. Nowadays they are
> > > > standardized files
> > <http://en.wikipedia.org/wiki/Job_Definition_Format>
> > > > which are used by print servers, printers, and production printing
> > > > machines. These job tickets do not only make sense for large-scale
> > > > production printing, they are also useful for mobile devices, home
> > > > desktops, workgroup printers, ... Also access to print services on
> the
> > > > internet directly from the desktop applications simply via a print
> > queue
> > > > would be possible.
> > > >
> > > > To allow desktop applications, printing systems, and printer drivers
> > to
> > > > easily create, edit, and read job tickets without needing to deal
> with
> > > > the actual job ticket format, the job ticket application programming
> > > > interface (JTAPI
> > > > <https://www.linux-foundation.org/en/OpenPrinting/JTAPI>) was
> > developed
> > > > by OpenPrinting. A complete specification
> > > > <ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec/fsg-
> openprinting-
> > job-ticket-api-v0100-20050315.pdf>
> > > > is published.
> > > >
> > > > The next step to do is the actual implementation of the JTAPI
> library
> > > > and its integration in applications, the CUPS printing system,
> > drivers,
> > > > filters, ... This will be the task of the student in this Google
> > Summer
> > > > of Code project.
> > > >
> > > > Mentor: Glen Petrie, Epson
> > > >
> > > > Desired knowledge: C Programming
> > > >
> > > >
> > > >

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Petrie, Glen]

[-- Attachment #1: Type: text/plain, Size: 5860 bytes --]

Lars,

 

During your design phase of the JTAPI I would like you to consider what the
original intent of the JTAPI is and, what I believe it another use of the
JTAPI.    The original intent is two fold (if memory service correctly).
The first, and I believe the primary intent, was to have library (tools)
that could create different Job-Ticket formats (JDF, MJT, proprietary-JT)
from a common set of API's, objects and attributes without the
user/developer having to know anything about the final job-ticket format.
The second intent was that by the addition of a "front-end" module one
job-ticket format could be inputted and parsed into the JTAPI common
objects/attributes; then using the JTAPIs, a different job-ticket format
could be generated ---- that is a job-ticket translation service. 

 

I see the third use of the JTAPI as either a common interface or front-end
translation service to an internal job-ticket object (a C data struct in
this case since JTAPI is to be coded in C) representation.  That is, a
developer uses JTAPI as an input portal to an internal object definition and
may never create an actual JDF, MJT or proprietary-JT formatted job-ticket.
In this case the job-ticket info (struct) is directly passed on to the next
print processing module.   I actually see this as the big potential use of
JTAPI and its associated objects/attributes definitions.

 

Thus, during your design and development phase of the internal component of
the JTAPI, please pay extra attention to how you design and document the
internal job-ticket objects.

 

Glen

 

 

  _____  

From: Petrie, Glen 
Sent: Wednesday, March 19, 2008 12:35 PM
To: Petrie, Glen; Ira McDonald; Norm Jacobs; Claudia Alimpich; Amanda
McPherson; Markus Rex; Jim Zemlin; Dan Kohn; Jeff Licquia; Wichmann, Mats D;
Susanne Oberhauser; Theodore Ts'o; Till Kamppeter
Subject: Google Summer of Code 2008: JTAPI Library Project

 

Hello All,

 

I am going to the mentor for the JTAPI implementation under the Google
Summer of Code 2008.  With only three months for the project, the project
needs to be scoped to fit within the time frame.   Therefore, I am sending
the following proposal to the group for comments and general approval for
the group.

 

***Project: 

JTAPI - Library

 

***Objective: 

Using the header files created by the Open-Printing Job-Ticket Working Group
develop a platform independent C library for the reading-of, modification-of
and storage-of a print job ticket for the Printer Working Group's (PWG's)
Micro-Job-Ticket (MJT).

 

***Approach:

1.   Review OP/JTWG Job-Ticket Application Programming Interface (JTAPI)
header documents

2.   Review PWG/MJT specification.

3.   Create Test MJT's 

a.   Manually create a minimum of 3 representative MJTs (text files) to be
used for testing and evaluation

4.   Define the command-line Test Application to exercise the JTAPIs;
include an initial set of commands

5.   Create Thin-Thread implementation of the individual JTAPIs and the Test
Application.

a.   This will be the first demonstrational implementation and the start
code for detailed development.

b.   This will include minimum documentation on how to use the Test
Application

6.   Enhance individual JTAPIs and the Test Application to provide full
functionality.

a.   Provided update documentation as required.

7.   Project Demonstration.

 

***Code License: 

MIT

 

***Coding Language: 

Platform Independent C

(No platform or vendor-specific extensions)

 

***Coding Document:

            In-line commenting must be sufficient to understand the flow and
any section requiring extended understanding.

 

***Operating System: 

Student's choice - Linux or Windows (non-gui for either)

 

***Interface: 

Command Line - GUI not required unless very simple (due to project time
constraint) 

 

***Document:

            Minimum:

1.   How to build the JTAPI library.

2.   How to build the Test Application

3.   The Test Application command-line instructions

4.   Three examples of using the Test Application and exercising the JTAPIs

 

 

==============


JTAPI implementation


Job tickets are extended descriptions for print jobs. They tell which
documents should be printed, on which type of paper, which resolution and
quality, whether there should be sheets inserted between the documents, ...,
and even information like delivery address, payment, ... A job ticket
accompanies a print job from its submission to its delivery. Job tickets
come from the professional printing world. In former times they were a paper
form with instructions what everyone involved in the printing process has to
do. Nowadays they are standardized files
<http://en.wikipedia.org/wiki/Job_Definition_Format>  which are used by
print servers, printers, and production printing machines. These job tickets
do not only make sense for large-scale production printing, they are also
useful for mobile devices, home desktops, workgroup printers, ... Also
access to print services on the internet directly from the desktop
applications simply via a print queue would be possible. 

To allow desktop applications, printing systems, and printer drivers to
easily create, edit, and read job tickets without needing to deal with the
actual job ticket format, the job ticket application programming interface
(JTAPI <https://www.linux-foundation.org/en/OpenPrinting/JTAPI> ) was
developed by OpenPrinting. A complete specification
<ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec/fsg-openprinting-job-tic
ket-api-v0100-20050315.pdf>  is published. 

The next step to do is the actual implementation of the JTAPI library and
its integration in applications, the CUPS printing system, drivers, filters,
... This will be the task of the student in this Google Summer of Code
project. 

Mentor: Glen Petrie, Epson 

Desired knowledge: C Programming 

 


[-- Attachment #2: Type: text/html, Size: 25460 bytes --]

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Lars Uebernickel]

Petrie, Glen wrote:
> Lars,
> 
>  
> 
> During your design phase of the JTAPI I would like you to consider what the
> original intent of the JTAPI is and, what I believe it another use of the
> JTAPI.    The original intent is two fold (if memory service correctly).
> The first, and I believe the primary intent, was to have library (tools)
> that could create different Job-Ticket formats (JDF, MJT, proprietary-JT)
> from a common set of API's, objects and attributes without the
> user/developer having to know anything about the final job-ticket format.
> The second intent was that by the addition of a "front-end" module one
> job-ticket format could be inputted and parsed into the JTAPI common
> objects/attributes; then using the JTAPIs, a different job-ticket format
> could be generated ---- that is a job-ticket translation service. 

I agree, these were the two uses I had in mind.

> I see the third use of the JTAPI as either a common interface or front-end
> translation service to an internal job-ticket object (a C data struct in
> this case since JTAPI is to be coded in C) representation.  That is, a
> developer uses JTAPI as an input portal to an internal object definition and
> may never create an actual JDF, MJT or proprietary-JT formatted job-ticket.
> In this case the job-ticket info (struct) is directly passed on to the next
> print processing module.   I actually see this as the big potential use of
> JTAPI and its associated objects/attributes definitions.

This could speed up the print process quite a bit - the job ticket need 
only be parsed and interpreted once and could be used throughout the 
print processing chain. But this would only work for modules in the same 
process, right? Otherwise, the data has to be serialized in some way to 
pipe it to the next processing module.

> Thus, during your design and development phase of the internal component of
> the JTAPI, please pay extra attention to how you design and document the
> internal job-ticket objects.

I will. Thanks for your ideas!

   Lars

Re: [Printing-architecture] Google Summer of Code 2008: JTAPI Library Project

[Ira McDonald]

Hi Lars,

You've got it - works only in a single process - if the data has to be
serialized, well
that's the *purpose* of Job Ticket formats - we should NOT develop a new JTAPI
private serialization of the internal C structures - the MJT encoding
is sufficient
and structured.

My two cents,
- Ira

On Tue, Apr 1, 2008 at 12:33 PM, Lars Uebernickel
<larsuebernickel@gmx.de> wrote:
> Petrie, Glen wrote:
>  > Lars,
>  >
>  >
>  >
>  > During your design phase of the JTAPI I would like you to consider what the
>  > original intent of the JTAPI is and, what I believe it another use of the
>  > JTAPI.    The original intent is two fold (if memory service correctly).
>  > The first, and I believe the primary intent, was to have library (tools)
>  > that could create different Job-Ticket formats (JDF, MJT, proprietary-JT)
>  > from a common set of API's, objects and attributes without the
>  > user/developer having to know anything about the final job-ticket format.
>  > The second intent was that by the addition of a "front-end" module one
>  > job-ticket format could be inputted and parsed into the JTAPI common
>  > objects/attributes; then using the JTAPIs, a different job-ticket format
>  > could be generated ---- that is a job-ticket translation service.
>
>  I agree, these were the two uses I had in mind.
>
>
>  > I see the third use of the JTAPI as either a common interface or front-end
>  > translation service to an internal job-ticket object (a C data struct in
>  > this case since JTAPI is to be coded in C) representation.  That is, a
>  > developer uses JTAPI as an input portal to an internal object definition and
>  > may never create an actual JDF, MJT or proprietary-JT formatted job-ticket.
>  > In this case the job-ticket info (struct) is directly passed on to the next
>  > print processing module.   I actually see this as the big potential use of
>  > JTAPI and its associated objects/attributes definitions.
>
>  This could speed up the print process quite a bit - the job ticket need
>  only be parsed and interpreted once and could be used throughout the
>  print processing chain. But this would only work for modules in the same
>  process, right? Otherwise, the data has to be serialized in some way to
>  pipe it to the next processing module.
>
>
>  > Thus, during your design and development phase of the internal component of
>  > the JTAPI, please pay extra attention to how you design and document the
>  > internal job-ticket objects.
>
>  I will. Thanks for your ideas!
>
>    Lars
>  _______________________________________________
>  Printing-architecture mailing list
>  Printing-architecture@lists.linux-foundation.org
>  https://lists.linux-foundation.org/mailman/listinfo/printing-architecture
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
 579 Park Place Saline, MI 48176
 734-944-0094
summer:
 PO Box 221 Grand Marais, MI 49839
 906-494-2434