From Norm.Jacobs at Sun.COM Wed Jan 28 13:02:10 2004 From: Norm.Jacobs at Sun.COM (Norm Jacobs) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI v0.91 Message-ID: <40182352.15D98AC9@Sun.COM> For those of you that have been chomping at the bit for an updated PAPI specification, Today is your lucky day. I have placed an updated version of the PAPI spec on the PWG ftp site. The document can be found at ftp://ftp.pwg.org/pub/pwg/fsg/spool/papi-v0.91.pdf I tried to incorporate the comments that were in the mail logs and some additional comments that I received internally. I did incorporate the information from the profiles and the capabilities extension documents from about a year ago. The Change log at the end of the document highlights some of the changes that I have incorporated. There are still a few formatting and numbering issues that I hope to work out. Since we have agreed to make an attempt at addressing document support and more administrative functionality, I know that this is not the last pre-1.0 revision. Hopefully, it is very close to the last one before 1.0. Please post any issues, comments, suggestions to the printing-spool@freestandards.org mail list where they can be discussed, resolved, and archived. -Norm From Norm.Jacobs at Sun.COM Fri Feb 6 13:17:55 2004 From: Norm.Jacobs at Sun.COM (Norm Jacobs) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI Source code on SourceForge Message-ID: <40240483.B2A8686@Sun.COM> FWIW I have imported a bunch of PAPI source code into CVS on SourceForge under the "openprinting" project. You can get to the SourceForge openprinting project page via http://sourceforge.net/projects/openprinting from there you can browse the CVS repository and/or get complete instructions on how to download code. The short version is that $ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/openprinting login $ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/openprinting co papi should get you a copy of code. Since Shawn Pratt is the only listed project administrator for the openprinting project on SourceForge and his email bounced, I have initiated a "takeover" request for the project so that I can administrate it (add administrators/developers/content/...). In the meantime, here are some specifics about what I have delivered. I have dropped two PAPI library implementations and a client implementation into CVS. papi/papi-lib-dynamic This library implements all of the functions in v0.91 of the specification, but doesn't communicate with a particular backend print service or protocol. It provides naming lookup support for printer configuration and dynamically redirects PAPI calls to the configured backend PAPI implementation. The naming support uses the name service switch on Solaris and does a crude emulation of it on "other" platforms. It also supports the use of URI style printer names (lpd://server/queue, ipp://server/printers/queue, etc.). In the event that a URI is used, the uri scheme is used to dynamically load the backend PAPI implementation. Without additional PAPI implementations installed, this module is of no real interest other than an example or skeleton to build a PAPI implementation from. The papi-lib-dynamic code was contributed by Sun Microsystems, Inc. papi/papi-lib-cups This library appears to implement v0.9 of the specification over libcups (mostly the IPP support in libcups). It was originally written on top of libipp (an offshoot of libcups that IBM was working on). I was unable to locate a copy of libipp, so I made a few modifications to the code to build under libcups. I also fixed a couple of minor bugs and added some of the v0.91 interface calls to the code. I have been able to use this module to communicate with a CUPS server as well as the IPP server Apache module that I have implemented on Solaris. The papi-lib-cups code was contributed by by IBM. papi/papi-clients-bsd-sysv This part of the tree implements support for the BSD and SYSV end-user printing commands on top of the PAPI. The implemented commands include lpr(1b), lpq(1b), lprm(1b), lpc(1M), lp(1), lpstat(1), cancel(1), accept(1M), reject(1M), enable(1M), disable(1M), and in.lpd(1M). The implementations are reasonably complete and should be pretty good examples of how to the the PAPI. The in.lpd(1M) implementation is still missing some functionality. The papi-clients-bsd-sysv code was contributed by Sun Microsystems, Inc. All of the code uses Autoconf/Automake/Libtool to build. You should be able to build/install with: $ sh ./autogen.sh --prefix=/opt/papi $ make install build and install a library first, then the clients. I have built/installed on Solaris and Linux. Things appear to be working, but I'm sure that there are issues to be addressed. We have an IPP listening service on top of the PAPI implemented as an Apache module. We are planning on dropping that code into CVS soon. Also, we are finishing up a PAPI implementation on top of RFC-1179 that doesn't require applications to have special privilege to use (mere mortals can contact a remote RFC-1179 based print service via a reserved port). PAPI over IPP is in the plan and will likely use the IPP support from the Apache IPP listener module, but we need to find an http library to use first. Anyway, I will send out another email when the SourceForge issue is resolved. I had hoped to get this all done yesterday afternoon, but there are never enough hours in the day and there is an issue with the CVS server right now, so the CVS repository wasn't available for web browsing or anonymous pserver access until about 10 minutes ago. -Norm From mike at easysw.com Fri Feb 6 14:17:06 2004 From: mike at easysw.com (Michael Sweet) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI Source code on SourceForge In-Reply-To: <40240483.B2A8686@Sun.COM> References: <40240483.B2A8686@Sun.COM> Message-ID: <40241262.20401@easysw.com> Norm Jacobs wrote: > ... > Since Shawn Pratt is the only listed project administrator for the > openprinting project on SourceForge and his email bounced, I have > initiated a "takeover" request for the project so that I can > administrate it (add administrators/developers/content/...). In the > meantime, here are some specifics about what I have delivered. Great, I've sent several requests to Shawn to be added to the project with no response; it will be nice to actually start developing the code again... > ... > port). PAPI over IPP is in the plan and will likely use the IPP support > from the Apache IPP listener module, but we need to find an http library > to use first. I'd like to (again) volunteer the CUPS HTTP and IPP code; it is fast, stable, supports TLS and SSL, and it substantially smaller than any other code I've seen. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Printing Software for UNIX http://www.easysw.com From Norm.Jacobs at Sun.COM Fri Feb 6 14:35:34 2004 From: Norm.Jacobs at Sun.COM (Norm Jacobs) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-announce] Re: [printing-spool] PAPI Source code onSourceForge References: <40240483.B2A8686@Sun.COM> <40241262.20401@easysw.com> Message-ID: <402416B6.DFABCB00@Sun.COM> Michael Sweet wrote: > > Norm Jacobs wrote: > > ... > > Since Shawn Pratt is the only listed project administrator for the > > openprinting project on SourceForge and his email bounced, I have > > initiated a "takeover" request for the project so that I can > > administrate it (add administrators/developers/content/...). In the > > meantime, here are some specifics about what I have delivered. > > Great, I've sent several requests to Shawn to be added to the > project with no response; it will be nice to actually start > developing the code again... Shawn just contacted me and if he gives me admin access, I will add you as a developer. > > > ... > > port). PAPI over IPP is in the plan and will likely use the IPP support > > from the Apache IPP listener module, but we need to find an http library > > to use first. > > I'd like to (again) volunteer the CUPS HTTP and IPP code; it is > fast, stable, supports TLS and SSL, and it substantially smaller > than any other code I've seen. > This sound good to me. I would love to see a fast, stable, MT-safe PAPI implementation over IPP. -Norm From Norm.Jacobs at Sun.COM Mon Feb 16 20:41:20 2004 From: Norm.Jacobs at Sun.COM (Norm Jacobs) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI status report Message-ID: <40319B70.9FAD984A@Sun.COM> PAPI status can be found at ftp://ftp.pwg.org/pub/pwg/fsg/status_reports/PAPI_WG_Status_13Feb2004.txt -Norm From imcdonald at sharplabs.com Tue Feb 17 07:57:15 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] RE: [Printing-architecture] PAPI status report [IPP System Admin issue] Message-ID: Hi Norm, We have a problem looming on the horizon for PAPI. Here's an excerpt from your PAPI monthly status: "Moving forward * Take feedback on v0.91 of PAPI spec and incorporate it into a new draft. * Work on draft interface additions for Administration and Document interfaces for next draft. (review via email through printing-spool list)" After recent discussions with Carl-Uno Manros (IETF IPP WG chair) and Tom Hastings (primary IPP editor), we've decided to abandon the IPP System Admin spec (draft-ietf-ipp-ops-set2-03.txt) as an IETF 'standards track' RFC. Rationale: If IPP System Admin spec is published as an IETF Proposed Standard, it's implied that it will be implemented and interop tested. But (except for CUPS??) there are no announced implementations. Background: The IESG is again closing down older WGs. Carl-Uno wants to move any remaining IPP specs to IEEE/ISTO PWG if possible. The IPP notifications specs have been abandoned in the IETF. PWG WBMM is designing a simpler subset over SOAP in XML schema. PWG WBMM is also designing a SOAP-based set of system admin operations equivalent to former IPP System Admin in XML schema. Michael Sweet - has CUPS implemented some/all of the IPP System Admin extension operations? Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Norm Jacobs [mailto:Norm.Jacobs@Sun.COM] Sent: Monday, February 16, 2004 11:41 PM To: printing-architecture@freestandards.org; printing-spool@freestandards.org Subject: [Printing-architecture] PAPI status report PAPI status can be found at ftp://ftp.pwg.org/pub/pwg/fsg/status_reports/PAPI_WG_Status_13Feb2004.txt -Norm _______________________________________________ Printing-architecture mailing list Printing-architecture@freestandards.org http://freestandards.org/mailman/listinfo/printing-architecture From mike at easysw.com Tue Feb 17 08:33:38 2004 From: mike at easysw.com (Michael Sweet) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Re: [Printing-architecture] PAPI status report [IPP System Admin issue] In-Reply-To: References: Message-ID: <40324262.5080108@easysw.com> McDonald, Ira wrote: > ... > Michael Sweet - has CUPS implemented some/all of the IPP System > Admin extension operations? CUPS has implemented some of the operations (in most cases using our own extension operations, since the CUPS ops came first) since v1.0; here is a quick table: Admin Spec Op CUPS Op ----------------------------------- ----------------------- Enable-Printer CUPS-Accept-Jobs Disable-Printer CUPS-Reject-Jobs Pause-Printer-After-Current-Job N/A * Hold-New-Jobs N/A * Release-Held-New-Jobs N/A * Deactivate-Printer N/A Activate-Printer N/A Restart-Printer N/A Shutdown-Printer N/A Startup-Printer N/A Reprocess-Job N/A ** Cancel-Current-Job Cancel-Job with job-id=0 Suspend-Current-Job N/A Resume-Job N/A Promote-Job N/A * Schedule-Job-After N/A * * = planned for future CUPS releases ** = planned for future CUPS releases, similar to Restart-Job FWIW, the Hold-New-Jobs and Release-Held-New-Jobs operations are somewhat problematic in the current definitions, since there is no "job-admin-held" job-state-reasons value or "admin" job-hold-until value to differentiate between a user-held job and a job that is held via Hold-New-Jobs. That makes implementation of Release-Held-New-Jobs somewhat challenging and makes it impossible for an admin to know which jobs will be released. In any case, the current spec covers both admin and operator operations for both printers and jobs, so it might be useful to break it up into functional documents published by the PWG instead... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Printing Software for UNIX http://www.easysw.com From imcdonald at sharplabs.com Tue Feb 17 09:38:54 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] RE: [Printing-architecture] PAPI status report [IPP System Admin issue] Message-ID: Hi, I've just spoken with Harry Lewis (IBM) and Tom Hastings (Xerox) about this IPP System Admin spec (they are co-authors, along with Carl Kugler, IBM). We think we should do a PWG IPP System Admin spec as _one_ spec, but delete or fix any 'broken' operations (see below). If we leave this spec on the IETF 'standards track', it will be late 2005 at the earliest before it's published as an RFC (the typical delay for a no-issues spec is 18 months at present). If we move it to IEEE/ISTO PWG, it can be taken to 'last call' within a month or two (it already _passed_ an IETF IPP WG 'last call'). Tom has already made the (trivial) security changes requested by Ned Free (our IETF Applications Area Director) in summer 2001. I've found other minor typos (and sent them to Tom). We need a volunteer to be principal editor of the PWG conversion of the spec (into IEEE/ISTO format in MS Word). I would volunteer to be co-editor. Because of issues such as Michael raises below, a few operations must be deleted or fixed (new parameters or new state reasons). If this spec rapidly advanced, then PWG WBMM (which has XML schema for most of these operations) could continue to have Normative references to the IPP operation semantics. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Michael Sweet [mailto:mike@easysw.com] Sent: Tuesday, February 17, 2004 11:34 AM To: McDonald, Ira Cc: 'Norm Jacobs'; printing-architecture@freestandards.org; printing-spool@freestandards.org; Hastings, Tom N; 'carl@manros.com'; Zehler, Peter; 'Harry Lewis' Subject: Re: [Printing-architecture] PAPI status report [IPP System Admin issue] McDonald, Ira wrote: > ... > Michael Sweet - has CUPS implemented some/all of the IPP System > Admin extension operations? CUPS has implemented some of the operations (in most cases using our own extension operations, since the CUPS ops came first) since v1.0; here is a quick table: Admin Spec Op CUPS Op ----------------------------------- ----------------------- Enable-Printer CUPS-Accept-Jobs Disable-Printer CUPS-Reject-Jobs Pause-Printer-After-Current-Job N/A * Hold-New-Jobs N/A * Release-Held-New-Jobs N/A * Deactivate-Printer N/A Activate-Printer N/A Restart-Printer N/A Shutdown-Printer N/A Startup-Printer N/A Reprocess-Job N/A ** Cancel-Current-Job Cancel-Job with job-id=0 Suspend-Current-Job N/A Resume-Job N/A Promote-Job N/A * Schedule-Job-After N/A * * = planned for future CUPS releases ** = planned for future CUPS releases, similar to Restart-Job FWIW, the Hold-New-Jobs and Release-Held-New-Jobs operations are somewhat problematic in the current definitions, since there is no "job-admin-held" job-state-reasons value or "admin" job-hold-until value to differentiate between a user-held job and a job that is held via Hold-New-Jobs. That makes implementation of Release-Held-New-Jobs somewhat challenging and makes it impossible for an admin to know which jobs will be released. In any case, the current spec covers both admin and operator operations for both printers and jobs, so it might be useful to break it up into functional documents published by the PWG instead... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Printing Software for UNIX http://www.easysw.com From hamzy at us.ibm.com Thu Feb 26 12:47:24 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Need slides for steering committee meeting Message-ID: We are going to present high level status and low level architecture/implementation detail for your group. Will the group leaders please prepare a set of slides that have: - high level overview - technical content of implementation - architectural issues/concerns of what other groups must do to support your code - what needs to be done in the future For the architecture group, will everyone prepare some information for us? The deadline for this is March 4th. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040226/5d52a1b7/attachment.htm From hamzy at us.ibm.com Fri Mar 12 12:19:00 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Status reports due by March 16th Message-ID: Please submit your monthly status reports by Tuesday March 16th. Thanks, Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040312/0c2188a2/attachment.htm From glen.petrie at eitc.epson.com Thu Mar 18 17:27:35 2004 From: glen.petrie at eitc.epson.com (Petrie, Glen) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Final Version of Slides for March 24, 04 FSG -Japan/US available Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB04A3346@eitc220.eitc.epson.com> Job-Ticket ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _JT_20040324-final.ppt ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _JT_20040324-final.pdf Architecture ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _Arch_20040324-final.ppt ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _Arch_20040324-final.pdf Print Driver ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _PD_20040324-final.ppt ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _PD_20040324-final.pdf PAPI ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _PAPI_20040324-final.sxi ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint _PAPI_20040324-final.pdf Rgds, Glen W. Petrie Epson Imaging Technology Center 150 River Oaks Parkway, Suite 200 San Jose, CA, 95134 Voice: 408.576.4131 Fax: 408.474.0511 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040318/b70adf43/attachment.htm From mihara.osamu at fxpsc.co.jp Thu Mar 18 21:32:33 2004 From: mihara.osamu at fxpsc.co.jp (Osamu MIHARA) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Re: [Printing-sc] Final Version of Slides for March 24, 04 FSG -Japan/US available In-Reply-To: <2F7D63A21DB2C74EB8EB8C09AF667DB04A3346@eitc220.eitc.epson.com> References: <2F7D63A21DB2C74EB8EB8C09AF667DB04A3346@eitc220.eitc.epson.com> Message-ID: <405A85F1.7060907@fxpsc.co.jp> Hi, all I have placed the vector driver spec and presentation. ftp://ftp.pwg.org/pub/pwg/fsg/vector/VectorPrinterDriverAPI-0.2en.pdf ftp://ftp.pwg.org/pub/pwg/fsg/vector/VectorPrinterDriverAPI-0.2en.sxw ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint_Vector_20040324-final.pdf ftp://ftp.pwg.org/pub/pwg/fsg/March2004_Japan-US_meeting_slides/FSGOpenPrint_Vector_20040324-final.ppt Regards, -- Osamu MIHARA // Fuji Xerox Printing Systems Co., Ltd. From hamzy at us.ibm.com Tue Apr 13 14:07:29 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Monthly status reports are due Message-ID: The monthly status reports are due by friday. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040413/e607611d/attachment.htm From hamzy at us.ibm.com Mon Apr 19 13:47:41 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Post status reports ASAP Message-ID: The status report was due on Friday and I am missing status reports from the PAPI, Vector, and Status Monitoring groups. Please put your report on the ftp site as soon as possible. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040419/22bc5681/attachment.htm From hamzy at us.ibm.com Tue May 11 12:19:54 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Please submit your status reports ASAP Message-ID: There is a FSG board meeting where status will be presented. No date was given, but a request was made to send status as quickly as possible. Remember - Funding and contributions to Workgroups are directly related to the visibility of your efforts. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040511/aa987dab/attachment.htm From Norm.Jacobs at Sun.COM Thu May 13 10:44:44 2004 From: Norm.Jacobs at Sun.COM (Norm Jacobs) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Please submit your status reports ASAP In-Reply-To: References: Message-ID: <40A3B40C.6050004@Sun.COM> Mark Hamzy wrote: > There is a FSG board meeting where status will be presented. No date was > given, but a request was made to send status as quickly as possible. > > Remember - Funding and contributions to Workgroups are directly related > to the visibility of your efforts. > Done From hamzy at us.ibm.com Wed Jun 16 09:28:55 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Monthly status reports are due Message-ID: Your monthly status report that covers work completed, ongoing work and planned work. Remember - Funding and contributions to Workgroups are directly related to the visibility of your efforts. Your entire report will go into the monthly Executive Director's report to the Board of Directors. Elements of your report are used in communications with current members, selling membership to non member companies, conference and trade show presentations, the bimonthly FSG public newsletter and even external, third party publications. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040616/cb5f1143/attachment.htm From glen.petrie at eitc.epson.com Mon Jun 28 14:12:49 2004 From: glen.petrie at eitc.epson.com (Petrie, Glen) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Slides for Libre ready for review - due Wednesday Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB06EF8D6@eitc220.eitc.epson.com> Hello All, I have completed my pass of the slides for Libre (sorry for the late date). I would like each team/member to review the slides and provide comments. I will only be able to accept comments up to Wednesday morning (pacific standard time) due to my travel arrangements. Please note there may appear to be too many slides but I am not planning to discussion all of them in detail. You will also note that some slides have a LOT of information or very detailed information on them but again, I will not talk to the details; the slide details are to illustrate what has been completed and the level of completion. Slides are located at: ftp://ftp.pwg.org/fsg/July2004_Libre-Conference/ FSGOpenPrint_Libre_2004-0706.ppt ftp://ftp.pwg.org/fsg/July2004_Libre-Conference/FSGOpenPrint_Libre_2004-0706 .pdf Rgds, Glen W. Petrie Epson Imaging Technology Center 150 River Oaks Parkway, Suite 200 San Jose, CA, 95134 Voice: 408.576.4131 Fax: 408.474.0511 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040628/b6ddeeae/attachment.htm From hamzy at us.ibm.com Tue Jul 13 11:42:32 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Monthly status reports are due Message-ID: This month's deadline is July 16 - Friday. Please submit your monthly status report that covers work completed, ongoing work and planned work. Funding and contributions to Workgroups are directly related to the visibility of your efforts. Your entire report will go into the monthly Executive Director's report to the Board of Directors. Elements of your report are used in communications with current members, selling membership to non member companies, conference and trade show presentations, the bimonthly FSG public newsletter and even external, third party publications. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20040713/7f24cadd/attachment.htm From jacobs at snapcon.com Thu Jul 29 15:39:12 2004 From: jacobs at snapcon.com (Norm Jacobs) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI v1.0 final functionality Message-ID: <1091140751.645.180.camel@speedy> I am proposing that we add content to cover the following areas prior to finalizing v1.0 of the spec. Creation of a Document object Administrative operations Add/Remove destination (printer/queue) (modify is already in the spec. but may need a more complete description.) Enable/Disable destination (printer/queue) Enable/Disable job creation on a particular destination. Promote Job make a job the next one to process. If there is anything else that others would like to add, please bring it up now. I would like to finalize the content of PAPI v1.0 in the next few weeks so that there is some small chance that it can be completed this fall. -Norm More detail on document object interfaces will follow next week (I hope), but I propose that the additions for new administrative operations be as follows. papi_status_t papiPrinterAdd(papi_service_t handle, char *printer_name, papi_attribute_t **attributes, papi_printer_t *printer); INPUTS handle - Handle to the print service on which to create the printer object. name - Name or URI of the printer to be created attrs - Attributes to associate with the printer object being created. OUTPUTS printer - The printer object created on the print service. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; papi_attribute_t **attrs = NULL; papi_printer_t printer = NULL; ... papiAttributeListAddString(&attrs, PAPI_EXCL, "device-uri", "socket://printer:9100"); papiAttributeListAddString(&attrs, PAPI_ATTR_APPEND, "document-format-supported", "application/ps"); papiAttributeListAddString(&attrs, PAPI_ATTR_APPEND, "document-format-supported", "text/plain"); papiAttributeListAddInteger(&attrs, PAPI_EXCL, "copies-default", 3); ... status = papiPrinterAdd(svc, "ipp://server/printers/triplicate", attrs, &result); papiAttributeListFree(attrs); if (status != PAPI_OK) { /* report a failure */ } if (result != NULL) { /* dump the printer info */ papiPrinterFree(result); } ... papiServiceDestroy(svc); papi_status_t papiPrinterRemove(papi_service_t handle, char *printer_name); INPUTS handle - Handle to the print service from which to remove the printer object. name - Name or URI of the printer to be removed. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterRemove(svc, "ipp://server/printers/triplicate"); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); papi_status_t papiPrinterEnable(papi_service_t handle, char *printer_name); INPUTS handle - Handle to the print service on which to enable job creation for the printer object. name - Name or URI of the printer to be enabled RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterEnable(svc, "ipp://server/printers/triplicate"); if (status != PAPI_OK) { /* report a failure */ } Dis. papiServiceDestroy(svc); papi_status_t papiPrinterDisable(papi_service_t handle, char *printer_name, char *message); INPUTS handle - Handle to the print service on which to disable job creation for the printer object. name - Name or URI of the printer to be disabled message - an optional reason for disabling the print queue. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterDisable(svc, "ipp://server/printers/triplicate", "because it's Tuesday"); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); papi_status_t papiJobPromote(papi_service_t handle, char *printer_name, int32_t job_id); INPUTS handle - Handle to the print service on which the job resides. name - Name or URI of the printer associated with the job. job_id - Id number of the job to promote. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiJobPromote(svc, "ipp://server/printers/triplicate", 12); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); From imcdonald at sharplabs.com Thu Jul 29 17:29:08 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI v1.0 final functionality Message-ID: Hi Norm, Note that (even as I write) the IESG is moving to approve the final edits to the IPP Admin spec. Given that the IEEE/ISTO PWG has already approved IPP Document Object (PWG 5100.5) last fall, we have solid 'standard-track' references for these bits of functionality (finally). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: printing-spool-bounces@base3.freestandards.org [mailto:printing-spool-bounces@base3.freestandards.org]On Behalf Of Norm Jacobs Sent: Thursday, July 29, 2004 6:39 PM To: printing-spool@freestandards.org; printing-architecture@freestandards.org Subject: [printing-spool] PAPI v1.0 final functionality I am proposing that we add content to cover the following areas prior to finalizing v1.0 of the spec. Creation of a Document object Administrative operations Add/Remove destination (printer/queue) (modify is already in the spec. but may need a more complete description.) Enable/Disable destination (printer/queue) Enable/Disable job creation on a particular destination. Promote Job make a job the next one to process. If there is anything else that others would like to add, please bring it up now. I would like to finalize the content of PAPI v1.0 in the next few weeks so that there is some small chance that it can be completed this fall. -Norm More detail on document object interfaces will follow next week (I hope), but I propose that the additions for new administrative operations be as follows. papi_status_t papiPrinterAdd(papi_service_t handle, char *printer_name, papi_attribute_t **attributes, papi_printer_t *printer); INPUTS handle - Handle to the print service on which to create the printer object. name - Name or URI of the printer to be created attrs - Attributes to associate with the printer object being created. OUTPUTS printer - The printer object created on the print service. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; papi_attribute_t **attrs = NULL; papi_printer_t printer = NULL; ... papiAttributeListAddString(&attrs, PAPI_EXCL, "device-uri", "socket://printer:9100"); papiAttributeListAddString(&attrs, PAPI_ATTR_APPEND, "document-format-supported", "application/ps"); papiAttributeListAddString(&attrs, PAPI_ATTR_APPEND, "document-format-supported", "text/plain"); papiAttributeListAddInteger(&attrs, PAPI_EXCL, "copies-default", 3); ... status = papiPrinterAdd(svc, "ipp://server/printers/triplicate", attrs, &result); papiAttributeListFree(attrs); if (status != PAPI_OK) { /* report a failure */ } if (result != NULL) { /* dump the printer info */ papiPrinterFree(result); } ... papiServiceDestroy(svc); papi_status_t papiPrinterRemove(papi_service_t handle, char *printer_name); INPUTS handle - Handle to the print service from which to remove the printer object. name - Name or URI of the printer to be removed. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterRemove(svc, "ipp://server/printers/triplicate"); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); papi_status_t papiPrinterEnable(papi_service_t handle, char *printer_name); INPUTS handle - Handle to the print service on which to enable job creation for the printer object. name - Name or URI of the printer to be enabled RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterEnable(svc, "ipp://server/printers/triplicate"); if (status != PAPI_OK) { /* report a failure */ } Dis. papiServiceDestroy(svc); papi_status_t papiPrinterDisable(papi_service_t handle, char *printer_name, char *message); INPUTS handle - Handle to the print service on which to disable job creation for the printer object. name - Name or URI of the printer to be disabled message - an optional reason for disabling the print queue. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterDisable(svc, "ipp://server/printers/triplicate", "because it's Tuesday"); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); papi_status_t papiJobPromote(papi_service_t handle, char *printer_name, int32_t job_id); INPUTS handle - Handle to the print service on which the job resides. name - Name or URI of the printer associated with the job. job_id - Id number of the job to promote. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiJobPromote(svc, "ipp://server/printers/triplicate", 12); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); _______________________________________________ printing-spool mailing list printing-spool@mail.freestandards.org http://mail.freestandards.org/mailman/listinfo/printing-spool From imcdonald at sharplabs.com Thu Jul 29 17:29:08 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] PAPI v1.0 final functionality Message-ID: Hi Norm, Note that (even as I write) the IESG is moving to approve the final edits to the IPP Admin spec. Given that the IEEE/ISTO PWG has already approved IPP Document Object (PWG 5100.5) last fall, we have solid 'standard-track' references for these bits of functionality (finally). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: printing-spool-bounces@base3.freestandards.org [mailto:printing-spool-bounces@base3.freestandards.org]On Behalf Of Norm Jacobs Sent: Thursday, July 29, 2004 6:39 PM To: printing-spool@freestandards.org; printing-architecture@freestandards.org Subject: [printing-spool] PAPI v1.0 final functionality I am proposing that we add content to cover the following areas prior to finalizing v1.0 of the spec. Creation of a Document object Administrative operations Add/Remove destination (printer/queue) (modify is already in the spec. but may need a more complete description.) Enable/Disable destination (printer/queue) Enable/Disable job creation on a particular destination. Promote Job make a job the next one to process. If there is anything else that others would like to add, please bring it up now. I would like to finalize the content of PAPI v1.0 in the next few weeks so that there is some small chance that it can be completed this fall. -Norm More detail on document object interfaces will follow next week (I hope), but I propose that the additions for new administrative operations be as follows. papi_status_t papiPrinterAdd(papi_service_t handle, char *printer_name, papi_attribute_t **attributes, papi_printer_t *printer); INPUTS handle - Handle to the print service on which to create the printer object. name - Name or URI of the printer to be created attrs - Attributes to associate with the printer object being created. OUTPUTS printer - The printer object created on the print service. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; papi_attribute_t **attrs = NULL; papi_printer_t printer = NULL; ... papiAttributeListAddString(&attrs, PAPI_EXCL, "device-uri", "socket://printer:9100"); papiAttributeListAddString(&attrs, PAPI_ATTR_APPEND, "document-format-supported", "application/ps"); papiAttributeListAddString(&attrs, PAPI_ATTR_APPEND, "document-format-supported", "text/plain"); papiAttributeListAddInteger(&attrs, PAPI_EXCL, "copies-default", 3); ... status = papiPrinterAdd(svc, "ipp://server/printers/triplicate", attrs, &result); papiAttributeListFree(attrs); if (status != PAPI_OK) { /* report a failure */ } if (result != NULL) { /* dump the printer info */ papiPrinterFree(result); } ... papiServiceDestroy(svc); papi_status_t papiPrinterRemove(papi_service_t handle, char *printer_name); INPUTS handle - Handle to the print service from which to remove the printer object. name - Name or URI of the printer to be removed. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterRemove(svc, "ipp://server/printers/triplicate"); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); papi_status_t papiPrinterEnable(papi_service_t handle, char *printer_name); INPUTS handle - Handle to the print service on which to enable job creation for the printer object. name - Name or URI of the printer to be enabled RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterEnable(svc, "ipp://server/printers/triplicate"); if (status != PAPI_OK) { /* report a failure */ } Dis. papiServiceDestroy(svc); papi_status_t papiPrinterDisable(papi_service_t handle, char *printer_name, char *message); INPUTS handle - Handle to the print service on which to disable job creation for the printer object. name - Name or URI of the printer to be disabled message - an optional reason for disabling the print queue. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiPrinterDisable(svc, "ipp://server/printers/triplicate", "because it's Tuesday"); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); papi_status_t papiJobPromote(papi_service_t handle, char *printer_name, int32_t job_id); INPUTS handle - Handle to the print service on which the job resides. name - Name or URI of the printer associated with the job. job_id - Id number of the job to promote. RETURNS If successful, a value of PAPI_OK is returned. Otherwise an appropriate failure value is returned. EXAMPLE papi_status_t status; papi_service_t svc = NULL; ... status = papiJobPromote(svc, "ipp://server/printers/triplicate", 12); if (status != PAPI_OK) { /* report a failure */ } ... papiServiceDestroy(svc); _______________________________________________ printing-spool mailing list printing-spool@mail.freestandards.org http://mail.freestandards.org/mailman/listinfo/printing-spool From glen.petrie at eitc.epson.com Thu Oct 7 07:52:50 2004 From: glen.petrie at eitc.epson.com (Petrie, Glen) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Proposed Agenda for PWG/FSG Meeting In San Antonio Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB0A7B326@eitc220.eitc.epson.com> All, I believe this was the tentative scheduled agreed upon for the Joint PWG/FSG Meeting in San Antonio. Monday November 15, 2004 Time Meeting/Presentation 8:00 8:15 Introduction and Agenda Check 8:15 9:15 Job Ticket (status / Plans) 9:15 10:15 PAPI (status / Plans) 10:15 10:30 Break 10:30 11:30 Print Control Manager (PCM) (Status / Plans) 11:30 12:30 Lunch 12:30 13:30 Status Monitoring (Status / Plans) 13:30 15:30 Architecture (Status / Plans / Working Session) 15:30 15:45 Break 15:45 17:30 Driver / Raster #1 (Status / Plans / Working Session) Tuesday November 16, 2004 Time Meeting/Presentation 8:00 8:15 Agenda Check 8:15 10:15 Driver / Raster #2 (Status / Plans / Working Session) 10:15 10:30 Break 10:30 11:30 Start of FSG Steering Committee Meeting 11:30 12:30 Lunch 12:30 17:30 FSG Steering Committee Meeting < Breaks as requested > Wednesday November 17, 2004 Time Meeting/Presentation Morning Joint PWG / FSG Meeting Rgds, Glen W. Petrie Epson Imaging Technology Center 150 River Oaks Parkway, Suite 200 San Jose, CA, 95134 Voice: 408.576.4131 Fax: 408.474.0511 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20041007/04dec0bd/attachment.htm From harryl at us.ibm.com Thu Oct 7 07:58:01 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Re: Proposed Agenda for PWG/FSG Meeting In San Antonio In-Reply-To: <2F7D63A21DB2C74EB8EB8C09AF667DB0A7B326@eitc220.eitc.epson.com> Message-ID: Glen, this looks great. Please let the FSG know that we'd like to plan a joint brainstorm Tuesday evening. This will be a venue for anyone to introduce new topics, issues, projects etc that they feel either FSG, PWG or jointly we should focus on. This will be a better chance to "rub elbows" than the joint Plenary which will be mostly reporting. If we get feedback that most people want to join this effort, I plan to just hold the conference room through the evening and we'll just pass the hat for pizza, sandwiches etc. ---------------------------------------------- Harry Lewis IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- "Petrie, Glen" 10/07/2004 08:52 AM To "'printing-meetingnotes@mail.freestandards.org'" , Harry Lewis/Boulder/IBM@IBMUS cc "'printing-jobticket@mail.freestandards.org'" , "'printing-japan@mail.freestandards.org'" , "'printing-architecture@mail.freestandards.org'" , printing-driver@freestandards.org, printing-spool@freestandards.org, printing-announce@base3.freestandards.org, printing-sc@freestandards.org Subject Proposed Agenda for PWG/FSG Meeting In San Antonio All, I believe this was the tentative scheduled agreed upon for the Joint PWG/FSG Meeting in San Antonio. Monday November 15, 2004 Time Meeting/Presentation 8:00 8:15 Introduction and Agenda Check 8:15 9:15 Job Ticket (status / Plans) 9:15 10:15 PAPI (status / Plans) 10:15 10:30 Break 10:30 11:30 Print Control Manager (PCM) (Status / Plans) 11:30 12:30 Lunch 12:30 13:30 Status Monitoring (Status / Plans) 13:30 15:30 Architecture (Status / Plans / Working Session) 15:30 15:45 Break 15:45 17:30 Driver / Raster #1 (Status / Plans / Working Session) Tuesday November 16, 2004 Time Meeting/Presentation 8:00 8:15 Agenda Check 8:15 10:15 Driver / Raster #2 (Status / Plans / Working Session) 10:15 10:30 Break 10:30 11:30 Start of FSG Steering Committee Meeting 11:30 12:30 Lunch 12:30 17:30 FSG Steering Committee Meeting < Breaks as requested > Wednesday November 17, 2004 Time Meeting/Presentation Morning Joint PWG / FSG Meeting Rgds, Glen W. Petrie Epson Imaging Technology Center 150 River Oaks Parkway, Suite 200 San Jose, CA, 95134 Voice: 408.576.4131 Fax: 408.474.0511 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments/20041007/edb9ca1e/attachment.htm From imcdonald at sharplabs.com Thu Oct 7 08:30:44 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Re: Proposed Agenda for PWG/FSG Meeting In S an Antonio Message-ID: Hi Glen, = Also, the PWG conference track meetings will only happen on Monday afternoon (and they're tentative topics that may some or all be cancelled), so having FSG working meetings on Monday morning will give an opportunity for potential overlap in attendance. = As I've mentioned before in FSG/OP Steering Committee meetings, I'll be in PWG WIMS on the Tuesday (although we can rearrange our WIMS schedule to let me get free for several hours in the afternoon, probably). = Cheers, - Ira = Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com = -----Original Message----- From: printing-spool-bounces@base3.freestandards.org [mailto:printing-spool-bounces@base3.freestandards.org]On Behalf Of Harry Lewis Sent: Thursday, October 07, 2004 10:58 AM To: Petrie, Glen Cc: printing-driver@freestandards.org; 'printing-architecture@mail.freestandards.org'; printing-spool@freestandards.org; 'printing-japan@mail.freestandards.org'; printing-sc@freestandards.org; 'printing-meetingnotes@mail.freestandards.org'; printing-announce@base3.freestandards.org; 'printing-jobticket@mail.freestandards.org' Subject: [printing-spool] Re: Proposed Agenda for PWG/FSG Meeting In San Antonio Glen, this looks great. Please let the FSG know that we'd like to plan a joint brainstorm Tuesday evening. This will be a venue for anyone to introduce new topics, issues, projects etc that they feel either FSG, PWG or jointly we should focus on. This will be a better chance to "rub elbows" than the joint Plenary which will be mostly reporting. If we get feedback that most people want to join this effort, I plan to just hold the conference room through the evening and we'll just pass the hat for pizza, sandwiches etc. = ---------------------------------------------- = Harry Lewis = IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems = http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- = "Petrie, Glen" = 10/07/2004 08:52 AM = To "'printing-meetingnotes@mail.freestandards.org'" , Harry Lewis/Boulder/IBM@IBMUS = cc "'printing-jobticket@mail.freestandards.org'" , "'printing-japan@mail.freestandards.org'" , "'printing-architecture@mail.freestandards.org'" , printing-driver@freestandards.org, printing-spool@freestandards.org, printing-announce@base3.freestandards.org, printing-sc@freestandards.org = Subject Proposed Agenda for PWG/FSG Meeting In San Antonio = All, = I believe this was the tentative scheduled agreed upon for the Joint PWG/FSG Meeting in San Antonio. = Monday November 15, 2004 = Time Meeting/Presentation = 8:00 8:15 Introduction and Agenda Check = 8:15 9:15 Job Ticket (status / Plans) = 9:15 10:15 PAPI (status / Plans) = 10:15 10:30 Break = 10:30 11:30 Print Control Manager (PCM) (Status / Plans) = 11:30 12:30 Lunch = 12:30 13:30 Status Monitoring (Status / Plans) = 13:30 15:30 Architecture (Status / Plans / Working Session) = 15:30 15:45 Break = 15:45 17:30 Driver / Raster #1 (Status / Plans / Working Session) = Tuesday November 16, 2004 = Time Meeting/Presentation = 8:00 8:15 Agenda Check = 8:15 10:15 Driver / Raster #2 (Status / Plans / Working Session) = 10:15 10:30 Break = 10:30 11:30 Start of FSG Steering Committee Meeting = 11:30 12:30 Lunch = 12:30 17:30 FSG Steering Committee Meeting = < Breaks as requested > = Wednesday November 17, 2004 = Time Meeting/Presentation = Morning Joint PWG / FSG Meeting = Rgds, Glen W. Petrie Epson Imaging Technology Center 150 River Oaks Parkway, Suite 200 San Jose, CA, 95134 Voice: 408.576.4131 Fax: 408.474.0511 = -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments= /20041007/b776299b/attachment.htm From imcdonald at sharplabs.com Thu Oct 7 08:30:44 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Re: Proposed Agenda for PWG/FSG Meeting In S an Antonio Message-ID: Hi Glen, = Also, the PWG conference track meetings will only happen on Monday afternoon (and they're tentative topics that may some or all be cancelled), so having FSG working meetings on Monday morning will give an opportunity for potential overlap in attendance. = As I've mentioned before in FSG/OP Steering Committee meetings, I'll be in PWG WIMS on the Tuesday (although we can rearrange our WIMS schedule to let me get free for several hours in the afternoon, probably). = Cheers, - Ira = Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com = -----Original Message----- From: printing-spool-bounces@base3.freestandards.org [mailto:printing-spool-bounces@base3.freestandards.org]On Behalf Of Harry Lewis Sent: Thursday, October 07, 2004 10:58 AM To: Petrie, Glen Cc: printing-driver@freestandards.org; 'printing-architecture@mail.freestandards.org'; printing-spool@freestandards.org; 'printing-japan@mail.freestandards.org'; printing-sc@freestandards.org; 'printing-meetingnotes@mail.freestandards.org'; printing-announce@base3.freestandards.org; 'printing-jobticket@mail.freestandards.org' Subject: [printing-spool] Re: Proposed Agenda for PWG/FSG Meeting In San Antonio Glen, this looks great. Please let the FSG know that we'd like to plan a joint brainstorm Tuesday evening. This will be a venue for anyone to introduce new topics, issues, projects etc that they feel either FSG, PWG or jointly we should focus on. This will be a better chance to "rub elbows" than the joint Plenary which will be mostly reporting. If we get feedback that most people want to join this effort, I plan to just hold the conference room through the evening and we'll just pass the hat for pizza, sandwiches etc. = ---------------------------------------------- = Harry Lewis = IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems = http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- = "Petrie, Glen" = 10/07/2004 08:52 AM = To "'printing-meetingnotes@mail.freestandards.org'" , Harry Lewis/Boulder/IBM@IBMUS = cc "'printing-jobticket@mail.freestandards.org'" , "'printing-japan@mail.freestandards.org'" , "'printing-architecture@mail.freestandards.org'" , printing-driver@freestandards.org, printing-spool@freestandards.org, printing-announce@base3.freestandards.org, printing-sc@freestandards.org = Subject Proposed Agenda for PWG/FSG Meeting In San Antonio = All, = I believe this was the tentative scheduled agreed upon for the Joint PWG/FSG Meeting in San Antonio. = Monday November 15, 2004 = Time Meeting/Presentation = 8:00 8:15 Introduction and Agenda Check = 8:15 9:15 Job Ticket (status / Plans) = 9:15 10:15 PAPI (status / Plans) = 10:15 10:30 Break = 10:30 11:30 Print Control Manager (PCM) (Status / Plans) = 11:30 12:30 Lunch = 12:30 13:30 Status Monitoring (Status / Plans) = 13:30 15:30 Architecture (Status / Plans / Working Session) = 15:30 15:45 Break = 15:45 17:30 Driver / Raster #1 (Status / Plans / Working Session) = Tuesday November 16, 2004 = Time Meeting/Presentation = 8:00 8:15 Agenda Check = 8:15 10:15 Driver / Raster #2 (Status / Plans / Working Session) = 10:15 10:30 Break = 10:30 11:30 Start of FSG Steering Committee Meeting = 11:30 12:30 Lunch = 12:30 17:30 FSG Steering Committee Meeting = < Breaks as requested > = Wednesday November 17, 2004 = Time Meeting/Presentation = Morning Joint PWG / FSG Meeting = Rgds, Glen W. Petrie Epson Imaging Technology Center 150 River Oaks Parkway, Suite 200 San Jose, CA, 95134 Voice: 408.576.4131 Fax: 408.474.0511 = -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-spool/attachments= /20041007/b776299b/attachment-0001.htm From toratani.yasumasa at canon.co.jp Thu Nov 11 07:19:51 2004 From: toratani.yasumasa at canon.co.jp (TORATANI Yasumasa) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Slides for the meeting in San Antonio Message-ID: <20041111231346.15A2.TORATANI.YASUMASA@canon.co.jp> Hi, I've uploaded the draft slides for the PWG/FSG joint meeting in San Antonio. http://www2s.biglobe.ne.jp/~papadon/OpenPrinting/Presentation/FSGOpenPrint_Plugin_SM_20041115-5.pdf And I believe other members will upload the draft slides soon. Actually, Japan side members could not have enough time to discuss both the PCM and SM in detail, and we focused on studying of PCM these days, so, we would like to have a long time for the discussion of PCM issues than SM in the meeting. Ide-san from EPSON will make a presentation of PCM first, and next, I'd like to discuss the PCM Plug-in which deals with the PCM's device/protocol dependent functionalities, and lastly, discuss shortly SM as just an idea. So, please arrange 12:30-13:30 of 15th mainly for PCM Plug-in and shortly SM. > 10:30 11:30 Print Control Manager (PCM) (Status / Plans) > 11:30 12:30 Lunch > 12:30 13:30 Status Monitoring (Status / Plans) Kindly regards TORATANI ---------------------------------------------------------------- ????? PCM????????????????? I/F???????????? I/F?? ???????????????????????????US??????? ??????????? http://www2s.biglobe.ne.jp/~papadon/OpenPrinting/Presentation/FSGOpenPrint_Plugin_SM_20041115-5.pdf ??????????????????????? ???????????? ----------------------------------------- TORATANI Yasumasa Computer Technology Development Dept. 12 CANON INC. Shimomaruko Office, Japan From toratani.yasumasa at canon.co.jp Fri Nov 12 06:59:11 2004 From: toratani.yasumasa at canon.co.jp (TORATANI Yasumasa) Date: Thu Jul 12 13:10:49 2007 Subject: [printing-spool] Final slides for PCM Plug-in and SM Message-ID: <20041112234910.12C0.TORATANI.YASUMASA@canon.co.jp> I've uploaded the final slides; http://www2s.biglobe.ne.jp/~papadon/OpenPrinting/Presentation/FSGOpenPrint_2004-Nov-Plugin_SM.pdf http://www2s.biglobe.ne.jp/~papadon/OpenPrinting/Presentation/FSGOpenPrint_2004-Nov-Plugin_SM.ppt Kindly regards, ---- ??????????????????? ?????????????????? ??????????????????????? ??????????? ----------------------------------------- TORATANI Yasumasa Computer Technology Development Dept. 12 CANON INC. Shimomaruko Office, Japan