From charles.hemstreet at hp.com Thu Jan 16 07:49:31 2003 From: charles.hemstreet at hp.com (HEMSTREET,CHARLES (HP-Vancouver,ex1)) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Notes from Open printing meeting 01/09/03 Message-ID: <6D805D4C4567D411AF32009027B683510DF685EB@xvan02.vcd.hp.com> Linux Open Printing Meeting 01/09/03, 8-9am PST (actual 8:00 - 9:12am PST) Attendees: Norm Jacobs Bob Taylor Shawn Pratt Claudia Alimpich Till Kamppeter Pete Zannucci Mark Hamzy Ira McDonald Charles Hemstreet Glen Petrie Agenda: 1. Discuss next face-to-face meeting. Are people interested in meeting at LinuxWorld? Washington DC is the next PWG meeting in May. It cost something like $40-$45/day to host the meeting. Till suggested face-to-face engineering time. Till also suggested that companies sponsor the event. We WILL NOT have a face-to-face at LinuxWorld. Shawn will make sure that there is enough notice for everyone to have sufficient time to prepare. 2. Where does the architecture meeting need to pick up? 3. Norm will put a proposal on the mail list printing-discuss call in PAPI query what's plumbed - it was put out and everyone agreed that is was fine. 4. Profiles - Ira and Tom will post prelim on printing-discuss profiles for basic printing and basic query. All functions must be minimally stubbed out. Run time "op not supported" would not be a problem. Still need to iterate what things are optional. If you do PAPI - you get everything. Suggests close the action item, not do profiles, lightly clarify the introduction to the PAPI spec to make clear that the min functionality that must be implemented is the query. There are libraries that implement query and print, or just print. 5. What is the state of PAPI? Nothing has changed since 0.9 except for the two new functions that were sent out. Shawn - are there any test suites for PAPI? Not at this time. Ira - PSI is doing a public beta, and once the beta is baked, it will be called 1.0. What if we do something like that for PAPI? It does mean that PAPI may not turn 1.0 very soon. Ira - IPP did three "bake-offs", the first two were six months apart. Shawn will make a statement at LinuxWorld that 0.9, which the working group considers a release candidate for 1.0. A roadmap would be created that show what future progress will be like. We will harden what we have, except bug fixes. 6. Ira - Need a testing lead. Shawn is sending out a couple of emails, one regarding testing, the other regarding requirements. Shawn is working on getting us some resources. 7. Norm - where do we put interoperable information out? Shawn - working on getting it going. If anyone has interest in getting the site going, Shawn would be happy to accept. Norm volunteered to help Shawn. 8. We'll have a meeting next week, but the meeting of the 23rd Agenda for next meeting (1/16/03): 1. No meeting for 1/23/03 Action items # What Owner Status Action items from 01/03/09 1 Work with Shawn to report back to pwg Charles 2 Can the executive board provide grants for travel to sumits Shawn 3 Email people to notify that we will not have a face-to-face meeting at LinuxWorld Shawn 4 Release to printing announce, prerelease message for LinuxWorld regarding to PAPI Shawn Action items from 11/21/02 1 Send out an announcement that the meeting will not be held next week. Charles Done 2 Claudia will write down the sequences that she described on the teleconference - narrative in plain text (terse) Claudia Action items from 11/14/02 1 Work with Mark Hamzy to find HP people to work on PDC Charles 2 Post agenda items query on architecture list Charles Done Action items from 11/07/02 none Action items from 10/31/02 1 Contact Robert Kravitz to find out if he can make it an hour later Till Done 2 Talk to Shawn about moving his meeting to another day Charles Done 3 Mailing lists are not behaving probably, contact Shawn Till Done 4 Need bidirectional arrows for bubbles A, B, C, and D Action items from 10/24/02 1 Change the list so that subscribers can post, moderate the unsubscribed Charles Done 2 Move Charles to be the moderator of the discussion list, and printing meetingnotes Charles In Progress 3 Change archival from 90 days to 1 year of printing-meetingnotes list Charles In Progress 4 Follow up with Michael Sweet to see if new time is doable. Ira Done 5 Follow up with Michael Sweet to find out what morning time would work for him Ira Done 6 Send out demo information for Webex so users can be comfortable with it before the next meeting Charles 7 Find out if there is a netmeeting client for Linux Charles In Progress Action items from 10/17/02 1 Take discussion list forum and move to meeting minutes forum Shawn Done 2 Move architecture discussions to new time slot, moving from the Thursday morning time slot. Charles In progress. (Related to AI#3) 3 Michael, Tom and Robert Krawitz to suggest a time for the architecture teleconference. Michael, Tom, Robert - (Ira and Till will follow up) In Progress 4 Put the overview template out in the architecture directory (fsg/pwg) Claudia 5 Update the web site with Claudia's template Shawn In Progress Action items from 10/10/02 1 Find out if we can use WebEx Shawn Pratt/Charles Hemstreet started 2 example documentation for Job Ticket API (from overview diagram) Claudia Claudia will provide by 10/14 3 Post to web and to discussion group for review. (Discussion groups - done, web - not yet, ran into some server issues) Shawn / Alan 4 Make note to other distribution lists to review this spec with objective to get agreement. (Done - am planning to do a reminder). Shawn 5 Broadcast message to application developers to review spec. Work to get applications to adopt the capabilities methodology. Shawn to general app groups, participants to their own company app groups (ongoing) Ongoing 6 Provide a starting point with the Device object definition Ira 7 Start reviewing and comment on areas of discrepancies and areas for mapping. All In progress 8 Completion of the architecture diagram and wording. All In progress 9 Requirements document (Shawn to establish an outline, need input to fill in the info All 10 Get feedback to Mark Hamzy on how to get Japan more involved in OpenPrinting before 10/16/02 All In progress 11 Issue next version of PAPI spec, version 0.6, candidate for functionally frozen 1.0. Add summary info from above as well as a print-by-reference function. Targeted for 9/20/02. Alan Done From charles.hemstreet at hp.com Wed Jan 29 14:14:17 2003 From: charles.hemstreet at hp.com (HEMSTREET,CHARLES (HP-Vancouver,ex1)) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Meeting notes from 01/16/03 Message-ID: <6D805D4C4567D411AF32009027B683510FC63691@xvan02.vcd.hp.com> Linux Open Printing Meeting 01/16/03, 8-9am PST (actual 8:00 - 9:12am PST) Attendees: Norm Jacobs Pete Zannucci Mark Hamzy Ira McDonald Charles Hemstreet Claudia Alimpich Glen Petrie Till Kamppeter Agenda for next meeting (1/16/03): 1. No meeting for 1/23/03 2. What is the goal of this forum? Originally discuss overall architecture for printing on Linux/Unix, and the interfaces that we have identified, how they interact, and their commonalities. Sequences were put out by Claudia, comments came back from Tom. This was posted beginning of December. Those sequences were put out on the mailing list. Claudia could repost. There have been a couple of different drawings, high level and more detailed level. We covered front end and job ticketing. We needed to look at how a spooler works, and how a back end device works. PAPI and Job Ticket are topics that need to come to this forum to be talked about resolving content and schedules. "Should we do this since PAPI is not doing this in 1.0?" Another significant area that hasn't been done in PAPI is notifications. 3. Ira - call with Tom and Michael Sweet. Cups 1.2 will support email notifications (LPR has email notification), protocol uses the IPP envelop - IPP Notification Delivery Protocol (INDP) - has its own port (pending), and In-band (Tom and Ira working on this) notifications that is done by polling by the IPP client - server meters job flow. 4. Mandrake re-filing? Next distro will be 9.1. Sounds like there is still a lot of energy. http://www.mandrakesoft.com/company/press/briefs?n=/mandrakesoft/news/2405 5. Next items - Need to start work on the PDC (the printer driver subgroup). There has been no progress. We need to work on a standard that supports the other two standards. We need David Suffield to start working with us. The Gimp Print developers. Glen would like to be involved. Robert Kravitz should be involved. This is high on the Japanese working group priority list. We need to start speaking a common language. Drivers currently speak different languages. There is another group, "Semantic model" - well formed XML structures. Centered on PP as a list of options. They list options and point to the standards that support them. They make XML structures that enclose those options. Home page on PWG - Semantic model, and one more link the zip file for model. (http://www.pwg.org/sm/index.html). In addition to taking a look at the semantic model, we should take a look at the PSI specification (http://www.pwg.org/ps/index.html). The discussion is when we will have an interoperability event. 6. The low level architecture diagram is out there with input from Michael Sweet. That is on the PWG site. It's dated 12/13. 7. Meeting at PWG in Washington D.C. end of March 31st - April 4th. PWG.org has the meeting schedule. What are we going to try and accomplish? The announcement was sent out, subscribe to the PWG mailing list. 8. Charles will be at LinuxWorld - stop by the HP printing booth and say "hi". 9. Next meeting will be 1/30/03. Agenda for next meeting (1/23/03): 1. No meeting for 1/23/03 Action items # What Owner Status Action items from 01/16/03 1 None From charles.hemstreet at hp.com Thu Jan 30 09:14:55 2003 From: charles.hemstreet at hp.com (HEMSTREET,CHARLES (HP-Vancouver,ex1)) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Notes from 20030130 architecture meeting. . . Message-ID: <6D805D4C4567D411AF32009027B683510FC636BB@xvan02.vcd.hp.com> Linux Open Printing Meeting 01/30/03, 8-9am PST (actual 8:00 - 9:12am PST) Attendees: Charles Hemstreet Norm Jacobs Ira McDonald Claudia Alimpich Mark Hamzy Glen Petrie Till Kamppeter Agenda for meeting (1/30/03): * We need to choose what we are going to focus on next o We need to think most driver, and driver interfaces. We need to get driver people engaged. Robert Kravitz - Gimp Print, David Suffield (HP), and Glen Petrie, anyone else? o David Suffield (HP), Raph Levien (Ghostscript), Glen Petrie, Robert Kravitz (Gimp-Print). o Commonality between PDC and IJS. We need to sync up between how we are going to do it between the two groups. o Bring the driver folks into the group - and then spin them off. o Look at getting buy-in attempting to come up with architecture - rendering system and driver. o Not excluding CUPS but not relying on CUPS too. Plug-in rendered - how to generate a backend of a spool system. o Rendering API or Rendering DataStream? o There are currently one or two formats out there - postscript and PDF. o Is the renderer part of the printer driver discussion? The renderer and the driver offset each other. o Renderer/driver interface/API - how to hook it together. o PDC needs to be scalable so that it can operate on small footprint devices. o The interface between renderer and driver is a piping interface - licensing ramifications. A lot of companies will want to support a binary to hide IP. The communication is via pipe. Can it be put in a protocol or message? Probably not. Pipes are one-way - there is no back channel. o IJS is bi-directional. How do you abort the job? How do you keep status of that job? What do you do when you cancel a job o For small devices we might need band printing o We need to tie into the work that is going on in Japan. Are they looking at the notifications that CUPS provides? * Claudia's sequence diagram - covering the front end - need to understand what happens at the backend. o The comments have been incorporated. o We've gone through the submission part - what happens after that? o We need someone to fill in what happens when it gets to the spooler? Can Pete take a look at this? o The latest greatest scenario, there is a mail note on the 16th. Just add to the text to it. * Till brought up the need to discuss the face-to-face meeting for PWG in March/April. UPnP is occurring one of those days. Shawn needs to contact Harry Lewis, Chair of PWG, to coordinate. Ira - there is a straw-man out there for schedules. Agenda for next meeting (2/6/03): * Preliminary discussion - Meeting in March - face to face - we need to decide what we want to talk about - We need to set the date - half day or whole day? * Driver folks to join us * Claudia's sequence diagram for the back end. Action items # What Owner Status Action items from 01/30/03 1 Charles to talk Shawn about getting us a date for face to face meeting at PWG Charles/Shawn 2 Ira to check dates at PWG and report back Ira Action items from 01/16/03 1 None Action items from 01/09/03 1 Work with Shawn to report back to pwg Charles Complete 2 Can the executive board provide grants for travel to summits Shawn 3 Email people to notify that we will not have a face-to-face meeting at LinuxWorld Shawn 4 Release to printing announce, prerelease message for LinuxWorld regarding to PAPI Shawn From imcdonald at sharplabs.com Thu Jan 30 09:44:59 2003 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Joint FSG/PWG face-to-face 31 March to 4 April 2003 Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE9E@mailsrvnt02.enet.sharplabs.com> Hi folks, [Harry Lewis (IBM/PWG Chair) - please touch base with Shawn Pratt (HP/FSG Open Printing) - thanks] At today's FSG Open Printing Architecture telecon we briefly discussed having at least two days of FSG Open Printing face-to-face meetings in Washington, DC this spring - the same week as the Printer Working Group (IEEE/ISTO PWG). The tentative PWG schedule (from their Web site just now) is as follows (note that there is not a PWG UPDF session): Mon 31 March - Character Repertoires (CR) - Web-based Device Management Tue 1 April - PWG Plenary - IPPFAX WG Wed 2 April - UPnP (requires UPnP membership) Thu 3 April - PWG Semantic Model (SM) (XML schemas of printing operations and attributes - used by PSI) Fri 4 April - Print Services Interface (PSI) (WSDL/SOAP/HTTP print services using the PWG SM schemas) A possible FSG Open Printing meeting schedule: Mon 31 March - FSG OP Plenary FSG OP PAPI Tue 1 April - FSG OP JTAPI FSG OP Printer Driver/Renderer Wed 2 April - FSG other (TBD) Comments? Cheers, - Ira McDonald High North Inc From shawn_pratt at hp.com Thu Jan 30 09:44:29 2003 From: shawn_pratt at hp.com (PRATT,SHAWN (HP-Boise,ex1)) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Notes from 20030130 architecture meet ing. . . Message-ID: 1. Commenting on the driver work. The Japan group has a keen interest in the bi-di and PDL support areas of openprinting. They have started two task groups from their side who are focusing on these respective areas. Please make sure we are working for alignment with these groups. We have a print driver distribution list that I will ensure the Japan group uses for their discussion as well (there may need to be some translation work on their side). As well, I will get a bi-di distribution list going as well so those discussions can occur. 2. Action item on Face-to-face meeting: I have had a couple of emails with Harry Lewis on this. I will get this finalized by next week. 3. Sourceforge. There is a sourceforge project for Openprinting. It can be reached at www.sourceforge.net/projects/openprinting. If you wish to be a member of this project please send me your name and email address (use the process provided in sourceforge). I will get your names added. I will be adding the website to the project but I need to have the latest files in the CVS system so we can access them. Remember on files to display in the website, you need to have it's original name listed (for archival reasons) and then a copy of the file with the addition of "-latest" at the end. I will link to the "*-latest" file which will allow each of you to update the site automatically. For example, the PAPI doc should have a file for each release as well as PAPI-latest.pdf for the most resent version (which will be linked from the website). - Shawn -----Original Message----- From: HEMSTREET,CHARLES (HP-Vancouver,ex1) [mailto:charles.hemstreet@hp.com] Sent: Thursday, January 30, 2003 10:15 AM To: 'printing-meetingnotes@freestandards.org' Subject: [printing-meetingnotes] Notes from 20030130 architecture meeting. . . Linux Open Printing Meeting 01/30/03, 8-9am PST (actual 8:00 - 9:12am PST) Attendees: Charles Hemstreet Norm Jacobs Ira McDonald Claudia Alimpich Mark Hamzy Glen Petrie Till Kamppeter Agenda for meeting (1/30/03): * We need to choose what we are going to focus on next o We need to think most driver, and driver interfaces. We need to get driver people engaged. Robert Kravitz - Gimp Print, David Suffield (HP), and Glen Petrie, anyone else? o David Suffield (HP), Raph Levien (Ghostscript), Glen Petrie, Robert Kravitz (Gimp-Print). o Commonality between PDC and IJS. We need to sync up between how we are going to do it between the two groups. o Bring the driver folks into the group - and then spin them off. o Look at getting buy-in attempting to come up with architecture - rendering system and driver. o Not excluding CUPS but not relying on CUPS too. Plug-in rendered - how to generate a backend of a spool system. o Rendering API or Rendering DataStream? o There are currently one or two formats out there - postscript and PDF. o Is the renderer part of the printer driver discussion? The renderer and the driver offset each other. o Renderer/driver interface/API - how to hook it together. o PDC needs to be scalable so that it can operate on small footprint devices. o The interface between renderer and driver is a piping interface - licensing ramifications. A lot of companies will want to support a binary to hide IP. The communication is via pipe. Can it be put in a protocol or message? Probably not. Pipes are one-way - there is no back channel. o IJS is bi-directional. How do you abort the job? How do you keep status of that job? What do you do when you cancel a job o For small devices we might need band printing o We need to tie into the work that is going on in Japan. Are they looking at the notifications that CUPS provides? * Claudia's sequence diagram - covering the front end - need to understand what happens at the backend. o The comments have been incorporated. o We've gone through the submission part - what happens after that? o We need someone to fill in what happens when it gets to the spooler? Can Pete take a look at this? o The latest greatest scenario, there is a mail note on the 16th. Just add to the text to it. * Till brought up the need to discuss the face-to-face meeting for PWG in March/April. UPnP is occurring one of those days. Shawn needs to contact Harry Lewis, Chair of PWG, to coordinate. Ira - there is a straw-man out there for schedules. Agenda for next meeting (2/6/03): * Preliminary discussion - Meeting in March - face to face - we need to decide what we want to talk about - We need to set the date - half day or whole day? * Driver folks to join us * Claudia's sequence diagram for the back end. Action items # What Owner Status Action items from 01/30/03 1 Charles to talk Shawn about getting us a date for face to face meeting at PWG Charles/Shawn 2 Ira to check dates at PWG and report back Ira Action items from 01/16/03 1 None Action items from 01/09/03 1 Work with Shawn to report back to pwg Charles Complete 2 Can the executive board provide grants for travel to summits Shawn 3 Email people to notify that we will not have a face-to-face meeting at LinuxWorld Shawn 4 Release to printing announce, prerelease message for LinuxWorld regarding to PAPI Shawn _______________________________________________ printing-meetingnotes mailing list printing-meetingnotes@freestandards.org http://freestandards.org/mailman/listinfo/printing-meetingnotes From harryl at us.ibm.com Thu Jan 30 13:59:02 2003 From: harryl at us.ibm.com (Harry Lewis) Date: Thu Jul 12 13:10:36 2007 Subject: FW: [printing-meetingnotes] Joint FSG/PWG face-to-face 31 March t o 4 April 2003 In-Reply-To: Message-ID: Shawn... I'm stuck! I really want to collocate a meeting... BUT... how does it do us any good if the meetings run in parallel? Then someone has to miss something and the likely resolution is that "FSGers" will go to FSG and "PWGers" will go to PWG and we might as well not have combined. I know I would have a very hard time choosing! Ideally, we'd collocate but not run parallel. This would mean spanning a weekend... but this may not "sit" well with people (travel, time, extra expenses over the weekend). Another alternative is to book the weekend, or the Sunday before and Saturday after. Again... folks grumbling... but we've got to get the work done somehow! As far as logistics... we will put up a URL for people to register their intent to join the meeting. We spread the cost of meeting facilities across the group so everyone ends up being charged $45-$65/day (depending on location etc.). We already have a hotel booked and would have to expand the room block, meeting space, catering etc. I'm willing to do this... but we need to decide on the above, quickly!! Yes, everyone is responsible for their own reservations. We do negotiate a rate (and a room block) at the hotel where the meeting is held... but some people will get better rates at nearby hotels according to their corporate arrangements. Can you estimate how many people you would have coming to the f2f? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "PRATT,SHAWN (HP-Boise,ex1)" 01/30/2003 11:03 AM To: Harry Lewis/Boulder/IBM@IBMUS cc: Subject: FW: [printing-meetingnotes] Joint FSG/PWG face-to-face 31 March t o 4 April 2003 Harry: We have discussed this to some extent back in December. With the PWG meetings last week over, I would like to see what I need to do to get connected to the PWG meetings in Washington DC. At today's Open Printing meeting, this is the proposed schedule we established. Is it possible to fit into those timeframes? Do you have a process that I can explain to folks on what they need to do to register (hotel, meetings, etc.). I am assuming I handle the meeting registration for the open printing discussions. I am also assuming each person needs to book their own hotel registration. How do you cover the cost of the conference rooms? Is this added to the person's hotel bill? Thanks, Shawn Pratt FSG OpenPrinting Chair -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, January 30, 2003 10:45 AM To: 'printing-meetingnotes@freestandards.org'; 'pwg@pwg.org' Subject: [printing-meetingnotes] Joint FSG/PWG face-to-face 31 March to 4 April 2003 Hi folks, [Harry Lewis (IBM/PWG Chair) - please touch base with Shawn Pratt (HP/FSG Open Printing) - thanks] At today's FSG Open Printing Architecture telecon we briefly discussed having at least two days of FSG Open Printing face-to-face meetings in Washington, DC this spring - the same week as the Printer Working Group (IEEE/ISTO PWG). The tentative PWG schedule (from their Web site just now) is as follows (note that there is not a PWG UPDF session): Mon 31 March - Character Repertoires (CR) - Web-based Device Management Tue 1 April - PWG Plenary - IPPFAX WG Wed 2 April - UPnP (requires UPnP membership) Thu 3 April - PWG Semantic Model (SM) (XML schemas of printing operations and attributes - used by PSI) Fri 4 April - Print Services Interface (PSI) (WSDL/SOAP/HTTP print services using the PWG SM schemas) A possible FSG Open Printing meeting schedule: Mon 31 March - FSG OP Plenary FSG OP PAPI Tue 1 April - FSG OP JTAPI FSG OP Printer Driver/Renderer Wed 2 April - FSG other (TBD) Comments? Cheers, - Ira McDonald High North Inc _______________________________________________ printing-meetingnotes mailing list printing-meetingnotes@freestandards.org http://freestandards.org/mailman/listinfo/printing-meetingnotes -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/printing-meetingnotes/attachments/20030130/2f76b3b3/attachment.html From toratani.yasumasa at canon.co.jp Mon Feb 17 01:23:32 2003 From: toratani.yasumasa at canon.co.jp (Yasumasa TORATANI) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Notes from 20030130 architecture meet ing. . . In-Reply-To: References: Message-ID: <20030217181934.F32F.TORATANI.YASUMASA@canon.co.jp> Dear All, Sorry for the lack of response from the Japan side WG to the US discussion and Shawn's comment, but I had a pretty pressing work since the beginning of this year. I received some comments from the following members in Japan about the new printing framework including CUPS and the new bi-di plug-in API, etc, and had some discussion about them. Osamu MIHARA (FUJI XEROX) Akira YOSHIYAMA (Debian, NEC) Masaji TAKEYAMA (KDE) Kazuo NOMURA (EPSON) Jun Adachi (OKI Data) And our conclusion was, a) CUPS is already the standard and will be the standard for years. So, we should not make the standard which exclude CUPS, and we should make the standard which can cover CUPS as well as other printing systems not to rely on the single system. b) PPD file is not enough to handle the printer capabilities despite the obvious standard under the Linux/UNIX printing framework. So, we should not rely on the single capabilities file format, but have a standard API which can cover several printer capabilities. I'd like to add that the API for b) between applications and the printing system is the Capabilities API. And the API between the device handling module which opens the device port (e.g. the CUPS backend) and device is the bi-di plug-in API. The bi-di plug-in will handle the printer information including asynchronous events from the printer, which will be the source of the notification message, as well as the dynamic printer capabilities, without submitting jobs. Thanks, Yasumasa TORATANI. On Thu, 30 Jan 2003 12:44:29 -0500 "PRATT,SHAWN (HP-Boise,ex1)" wrote: > 1. Commenting on the driver work. The Japan group has a keen interest in > the bi-di and PDL support areas of openprinting. They have started two task > groups from their side who are focusing on these respective areas. Please > make sure we are working for alignment with these groups. We have a print > driver distribution list that I will ensure the Japan group uses for their > discussion as well (there may need to be some translation work on their > side). As well, I will get a bi-di distribution list going as well so those > discussions can occur. > > 2. Action item on Face-to-face meeting: I have had a couple of emails with > Harry Lewis on this. I will get this finalized by next week. > > 3. Sourceforge. There is a sourceforge project for Openprinting. It can > be reached at www.sourceforge.net/projects/openprinting. If you wish to be > a member of this project please send me your name and email address (use the > process provided in sourceforge). I will get your names added. I will be > adding the website to the project but I need to have the latest files in the > CVS system so we can access them. Remember on files to display in the > website, you need to have it's original name listed (for archival reasons) > and then a copy of the file with the addition of "-latest" at the end. I > will link to the "*-latest" file which will allow each of you to update the > site automatically. For example, the PAPI doc should have a file for each > release as well as PAPI-latest.pdf for the most resent version (which will > be linked from the website). > > - Shawn > > -----Original Message----- > From: HEMSTREET,CHARLES (HP-Vancouver,ex1) [mailto:charles.hemstreet@hp.com] > > Sent: Thursday, January 30, 2003 10:15 AM > To: 'printing-meetingnotes@freestandards.org' > Subject: [printing-meetingnotes] Notes from 20030130 architecture meeting. . > . > > Linux Open Printing Meeting > 01/30/03, 8-9am PST (actual 8:00 - 9:12am PST) > > Attendees: > Charles Hemstreet > Norm Jacobs > Ira McDonald > Claudia Alimpich > Mark Hamzy > Glen Petrie > Till Kamppeter > > > Agenda for meeting (1/30/03): > > * We need to choose what we are going to focus on next > o We need to think most driver, and driver interfaces. We need to get > driver people engaged. Robert Kravitz - Gimp Print, David Suffield (HP), > and Glen Petrie, anyone else? > o David Suffield (HP), Raph Levien (Ghostscript), Glen Petrie, Robert > Kravitz (Gimp-Print). > o Commonality between PDC and IJS. We need to sync up between how we > are going to do it between the two groups. > o Bring the driver folks into the group - and then spin them off. > o Look at getting buy-in attempting to come up with architecture - > rendering system and driver. > o Not excluding CUPS but not relying on CUPS too. Plug-in rendered - > how to generate a backend of a spool system. > o Rendering API or Rendering DataStream? > o There are currently one or two formats out there - postscript and > PDF. > o Is the renderer part of the printer driver discussion? The renderer > and the driver offset each other. > o Renderer/driver interface/API - how to hook it together. > o PDC needs to be scalable so that it can operate on small footprint > devices. > o The interface between renderer and driver is a piping interface - > licensing ramifications. A lot of companies will want to support a binary > to hide IP. The communication is via pipe. Can it be put in a protocol or > message? Probably not. Pipes are one-way - there is no back channel. > o IJS is bi-directional. How do you abort the job? How do you keep > status of that job? What do you do when you cancel a job > o For small devices we might need band printing > o We need to tie into the work that is going on in Japan. Are they > looking at the notifications that CUPS provides? > > * Claudia's sequence diagram - covering the front end - need to > understand what happens at the backend. > o The comments have been incorporated. > o We've gone through the submission part - what happens after that? > o We need someone to fill in what happens when it gets to the spooler? > Can Pete take a look at this? > o The latest greatest scenario, there is a mail note on the 16th. > Just add to the text to it. > > * Till brought up the need to discuss the face-to-face meeting for PWG > in March/April. UPnP is occurring one of those days. Shawn needs to > contact Harry Lewis, Chair of PWG, to coordinate. Ira - there is a > straw-man out there for schedules. > > > Agenda for next meeting (2/6/03): > > * Preliminary discussion - Meeting in March - face to face - we need > to decide what we want to talk about - We need to set the date - half day or > whole day? > * Driver folks to join us > * Claudia's sequence diagram for the back end. > > > > Action items > # What Owner Status > Action items from 01/30/03 > 1 Charles to talk Shawn about getting us a date for face to face > meeting at PWG Charles/Shawn > 2 Ira to check dates at PWG and report back Ira > Action items from 01/16/03 > 1 None > Action items from 01/09/03 > 1 Work with Shawn to report back to pwg Charles Complete > 2 Can the executive board provide grants for travel to summits > Shawn > 3 Email people to notify that we will not have a face-to-face meeting > at LinuxWorld Shawn > 4 Release to printing announce, prerelease message for LinuxWorld > regarding to PAPI Shawn > > _______________________________________________ > printing-meetingnotes mailing list > printing-meetingnotes@freestandards.org > http://freestandards.org/mailman/listinfo/printing-meetingnotes > > _______________________________________________ > printing-meetingnotes mailing list > printing-meetingnotes@freestandards.org > http://freestandards.org/mailman/listinfo/printing-meetingnotes ----------------------------------------- Yasumasa TORATANI Computer Technology Development Dept. 12 CANON INC. Shimomaruko Office Phone: +81-3-5732-8338 From charles.hemstreet at hp.com Fri Mar 7 13:12:16 2003 From: charles.hemstreet at hp.com (HEMSTREET,CHARLES (HP-Vancouver,ex1)) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Architecture notes 20030306 Message-ID: Linux Open Printing Meeting 03/06/03, 8-9am PST (actual 8:00 - 9:00am PST) Attendees: Charles Hemstreet Ira McDonald Shawn Pratt Till Kamppeter Peter Zannucci Agenda for meeting (03/06/03): 1. Shawn Pratt - FSG Meeting in Washington DC - Shawn currently has 11 people targeted to come to this meeting (most of whom are not part of the regular Thursday architecture meeting). The PSI person (Bob Taylor) will be at FSG. If everyone agrees to the proposed agenda, Shawn will type it up and submit it. a. FSG is looking for some money to be able to help us out. b. What are we working on, what are we missing? What areas do we need to have work done? c. Ira - put up high level diagrams with color coding - (lots of work/little work - White space designates that there has been no work done. d. Sourceforge open printing website is now available - openprinting.sourceforge.net. 2. Ira - FSG visitors, block rate ends at the hotel on March 10th. Get your rooms ASAP if you haven't already. 3. Claudia - proposal for an agenda for the FSG meeting in Washington DC - covered in Shawn's topic. See #1 and proposed agenda below. 4. Mark Hamzy - driver subgroup - Mark was not able to make it. 5. Other? Agenda for next meeting (3/13/03): * ?? Proposed FSG Meeting agenda (Tuesday, April 1, 2003) Following is a proposed agenda for the FSG meeting: --------------------------------------------------------- 8:00-9:00 AM - Plenary (60 minutes = 15 minutes for coffee + 45 minutes for meeting) Presenters: Shawn Pratt/Charles Hemstreet Agenda a. Coffee b. Business meeting 9:00-9:30 AM - Architecture Overview (30 minutes = 20 minutes for presentation + 10 minutes for questions) Presenters: Charles Hemstreet/Mark Hamzy a. High level architecture diagram b. Identify major pieces of the architecture and which are: 1. Work in progress (percentage complete) 2. Not much activity, need more work c. Questions 9:30-9:45 AM - Break (15 minutes) 9:45-10:45 AM - JTAPI (60 minutes = 40 minutes for presentation + 20 minutes for questions) Presenter: Claudia Alimpich For the agenda guidelines, see the *note below 10:45-11:45 AM - PAPI (60 minutes = 40 minutes for presentation + 20 minutes for questions) Presenter: Michael Sweet? For the agenda guidelines, see the *note below 11:45 AM -1:00 PM - Lunch (75 minutes) 1:00-1:30 PM - Capabilities (30 minutes) Presenter: ??? For the agenda guidelines, see the *note below 1:30-2:00 PM - Notification (30 minutes) Presenter: Tom Hastings For the agenda guidelines, see the *note below 2:00-3:00 PM - Printer Driver Renderer (60 minutes) Presenter: Glen Petrie/Mark Hamzy For the agenda guidelines, see the *note below 3:00-3:15 PM - Break (15 minutes) 3:15-5:15 PM - Architecture details (120 minutes) Presenter: Charles Hemstreet/Mark Hamzy a. Low level architecture diagram b. Resolve problems/issues identified during earlier sessions c. Resolve open problems/issues 5:15-7:00 PM - Dinner (105 minutes) 7:00-9:00 PM - Overflow (120 minutes) Any items that were identified during the previous sessions need to be covered. The agenda will be determined as the day progresses. *note - The following format should be followed for the slide presentation: a. Introduction/Purpose b. Status - Milestones (previous and future) c. Details - Whatever slides are needed to describe the details d. Issues e. Information about this working group 1. Active participants 2. Meeting day, time, call in information 3. Websites - Mailing list and archives - Other documents pertaining to this working group f. Q&A and discussion Action items # What Owner Status Action items from 03/06/03 1 Check to see if there is a good polycon conference phone to FSG meeting Shawn 2 Check to see if there is a good polycon conference phone to FSG meeting Ira Action items from 02/27/03 1 It would be nice if we could get a translation or running summary (one sentence) of the discussions that happen on the printing-japan discussion list Charles Action items from 01/30/03 1 Charles to talk Shawn about getting us a date for face to face meeting at PWG Charles/Shawn Done 2 Ira to check dates at PWG and report back Ira Action items from 01/16/03 1 None Action items from 01/09/03 1 Work with Shawn to report back to pwg Charles Complete 2 Can the executive board provide grants for travel to summits Shawn 3 Email people to notify that we will not have a face-to-face meeting at LinuxWorld Shawn 4 Release to printing announce, prerelease message for LinuxWorld regarding to PAPI Shawn Action items from 11/21/02 1 Send out an announcement that the meeting will not be held next week. Charles Done 2 Claudia will write down the sequences that she described on the teleconference - narrative in plain text (terse) Claudia Action items from 11/14/02 1 Work with Mark Hamzy to find HP people to work on PDC Charles 2 Post agenda items query on architecture list Charles Done Action items from 11/07/02 none Action items from 10/31/02 1 Contact Robert Kravitz to find out if he can make it an hour later Till Done 2 Talk to Shawn about moving his meeting to another day Charles Done 3 Mailing lists are not behaving probably, contact Shawn Till Done 4 Need bidirectional arrows for bubbles A, B, C, and D Action items from 10/24/02 1 Change the list so that subscribers can post, moderate the unsubscribed Charles Done 2 Move Charles to be the moderator of the discussion list, and printing meetingnotes Charles In Progress 3 Change archival from 90 days to 1 year of printing-meetingnotes list Charles In Progress 4 Follow up with Michael Sweet to see if new time is doable. Ira Done 5 Follow up with Michael Sweet to find out what morning time would work for him Ira Done 6 Send out demo information for Webex so users can be comfortable with it before the next meeting Charles 7 Find out if there is a netmeeting client for Linux Charles In Progress Action items from 10/17/02 1 Take discussion list forum and move to meeting minutes forum Shawn Done 2 Move architecture discussions to new time slot, moving from the Thursday morning time slot. Charles In progress. (Related to AI#3) 3 Michael, Tom and Robert Krawitz to suggest a time for the architecture teleconference. Michael, Tom, Robert - (Ira and Till will follow up) In Progress 4 Put the overview template out in the architecture directory (fsg/pwg) Claudia 5 Update the web site with Claudia's template Shawn In Progress Action items from 10/10/02 1 Find out if we can use WebEx Shawn Pratt/Charles Hemstreet started 2 example documentation for Job Ticket API (from overview diagram) Claudia Claudia will provide by 10/14 3 Post to web and to discussion group for review. (Discussion groups - done, web - not yet, ran into some server issues) Shawn / Alan 4 Make note to other distribution lists to review this spec with objective to get agreement. (Done - am planning to do a reminder). Shawn 5 Broadcast message to application developers to review spec. Work to get applications to adopt the capabilities methodology. Shawn to general app groups, participants to their own company app groups (ongoing) Ongoing 6 Provide a starting point with the Device object definition Ira 7 Start reviewing and comment on areas of discrepancies and areas for mapping. All In progress 8 Completion of the architecture diagram and wording. All In progress 9 Requirements document (Shawn to establish an outline, need input to fill in the info All 10 Get feedback to Mark Hamzy on how to get Japan more involved in OpenPrinting before 10/16/02 All In progress 11 Issue next version of PAPI spec, version 0.6, candidate for functionally frozen 1.0. Add summary info from above as well as a print-by-reference function. Targeted for 9/20/02. Alan Done From imcdonald at sharplabs.com Thu Mar 20 09:07:16 2003 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] FW: Thur 20 March 10am PST - PWG SM Telecon [Document object revi ew] Message-ID: <116DB56CD7DED511BC7800508B2CA53735CF3C@mailsrvnt02.enet.sharplabs.com> Hi folks, For those interested in listening to the IPP Document object review, below is the dial-in and webex information. Below that is Tom Hasting's note with the document URLs (various formats) and the 18 issues (most of which are resolved by email already, tentatively). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, March 17, 2003 12:17 PM To: PWG Semantic Model WG (E-mail) Subject: SM> Thur 20 Mar Semantic Model Telecon > All, > > This Thursday at 1pm EDT is the Semantic Model teleconference. This > week's teleconference will be dedicated to the Document Object > > The teleconference is one hour long. It will be run using phone and > Webex. Anyone that does not yet have Webex installed > should do that before Thursday. Information for the phone and > Webex are included below. > > The agenda for the Semantic Model teleconference is : > > 1) Adjust agenda > 2) Walk through Document Object Specification Tom Hastings will send out link to specification under separate cover 3) Check out the latest changes to the Semantic Model Specification We will use the version with revision marks. > ftp://ftp.pwg.org/pub/pwg/Semantic-Model/wd-sm10-20030317.pdf ftp://ftp.pwg.org/pub/pwg/Semantic-Model/wd-sm10-20030317-rev.pdf > 3) Next Steps > > > Pete > All, > > > > Peter Zehler > XEROX > Xerox Architecture Center > Email: PZehler@crt.xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-8871 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-30E > Webster NY, 14580-9701 > > > ________________________________________________________ > > Dial in Info: > Phone Number: (877) 776-6306 > (Phone Number for Xerox Employees: 8*594-0576) > PARTICIPANT PASSCODE: 437874# > ________________________________________________ > webex info: > We will also use an on line tool called webex, > if you have not used this before, setup up by > following the First Time Users instructions. > Do this in advance of the meeting. > > ------------------------- > FIRST TIME USERS > ------------------------- > For fully interactive meetings, including the ability > to present your documents and applications, a one-time > setup takes less than 10 minutes. Click this URL to set up now: > > http://hp.webex.com > > Then click New User. > ------------------------- > > On Thursday use: > https://hp.webex.com/join/ > > Then click join unlisted meeting. > Use the info below: > ------------------------- > Webex MEETING SUMMARY ------------------------- Name: PWG Semantic Model Date: 3/20/2003 Time: 1:00PM, (GMT -04:00) Eastern Time, USA & Canada (Daylight Time) 10:00AM, (GMT -07:00) Pacific Time, USA & Canada (Daylight Time) Meeting Number: 21366675 Meeting Password: pwg_sm Host: Bob Taylor (HP) > ___________________________________________________ > > For some reason the sizes of the clean version of the .PDF file is huge (3 Mb) while the revision marked .pdf was much smaller. And of course the .doc files are always huge. However, zipping all of them separately helped a lot. Those who have to down load over a phone line this savings is significant. So I've down loaded individual .zip files for each of the four flavors: ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314-pdf.zip ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314-doc.zip ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314-rev-pdf.zip ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314-rev-doc.zip .pdf .doc -rev.pdf -rev.doc which are: 1152KB, 290KB, 694KB, and 307KB, respectively, compared to: 2786KB, 1925KB, 865KB, and 2007KB, respectively. ratio: 59%, 85%, 85%, 20%, respectively Tom -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Monday, March 17, 2003 16:12 To: sm@pwg.org Subject: SM> IPP Document object specification, March 14 2003 version, is available for SM 3/20 telecon I've stored the 14 March 2003 version of the IPP Document object on the PWG server at: ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-latest.pdf ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-latest.doc which are the same as: ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314.pdf ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314.doc The version with revision marks is available at: ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314-rev.pdf ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/wd-ippdoc10-20030314-rev.doc The rest of the email message contains the 18 issues followed by the change log summary. The 14 March 2003 version contains the agreements reached at the last PWG face to face meeting in Maui and on subsequent SM telecons and email threads. This version also aligns with the 17 March 2003 version of the Semantic Model that Pete just posted. The issues will be reviewed during the PWG Semantic Model telecon, Thursday, March 20. There are 18 issues, mostly minor or just making sure you approve of the specific updates. However, issue #9 is significant. Here are the issues that are also embedded in the document: ISSUE 00: Or should we just delete "input-document-number" operation attribute when we republish pwg5100.4 without "document-overrides? ISSUE 01: OK: OK to rename Send-Data to Send-Document-Data to reflect the object on which it operates? ISSUE 02: OK to add Close-Job operation and to REQUIRE a Printer to support it, since PSI is using it? ISSUE 03: Should we make "job-mandatory-attributes" a REQUIRED attribute for a Printer to support (if it supports the Document object)? Otherwise, clients won't support it and will be stuck with the "ipp-attribute-fidelity" attribute? ISSUE 04: The "document-overrides" attribute is also useful in combination with the "pages-per-subset" attribute (see [pwg5100.4]) which divides up the Input Page stream concatenated across the Input Documents into separate Output Documents. For example, making every 10 Input Pages be a separate Output Document but the client only wants to staple the first Output Document. ISSUE 04: But what about Subset Finishing? Can we it be done without "document-overrides"? ISSUE 05: OK that when a Printer supports Page Overrides, that we REQUIRE the Printer to continue to support the "page-overrides" as an operation attribute in Send-Document and Send-URI as well as a Document Template attribute? ISSUE 06: OK that "document-container-summary" is only one level deep? ISSUE 07: Is the description of "document-container-summary" attribute OK? ISSUE 08: Are the conformance requirements for the "document-container-summary" attributes OK? ISSUE: 09: How can a Printer indicate which combinations of document-creator-application-name (name(MAX)), document-creator-application-version (text(127)), document-creator-os-name (name(40)), document-creator-os-version (text(40)), document-format-device-id (text(127)), document-format-version (text(127), document-format (mimeMediaType) and "document-natural-language (naturalLanguage) are supported? ISSUE 10: OK that "document-format-version" is REQUIRED for a Printer to support? ISSUE: 11: The problem with separating "document-format" and "document-format-version" is how can a Printer describe what versions are supported, since the versions have to be associated with the document format. ISSUE 12: 'PDF/X-1:2001': From the ISO standard that specifies PDF/X. ISSUE 12: Or should the official ISO standard number, part number and date, be used instead, e.g., "ISO nnnnn.n-2001"? ISSUE 13: The definition of "document-natural-language" in [rfc2911] ?3.2.1.1 and [pwg5100.4] ?5.1.7 is single-valued. OK that this Document Description attribute isn't 1setOf? Or should we extend "document-natural-language" to 1setOf naturalLanguage) and keep the same name? Or change the name to "document-natural-languages"? ISSUE 14: TBD - Need to add the "xxx-default" and "xxx-supported" to Table 14 that go with the Document Template attributes. ISSUE 15: TBD - Need to add the xxx-default and xxx-supported for each xxx in the IANA Registration of Document Template attributes. ISSUE 16: TBD - Need to add the xxx-default and xxx-supported for each xxx in the IANA Registration of Job Template attributes being defined. ISSUE 17: TBD - Need to list the keyword attribute values in the IANA Registration section. Do so by reference to the values registered for corresponding attributes. Here is the Change Log: Version 0.7, 14 March 2003, agreements from the Maui January PWG meeting and subsequent telecons: 1. Fixed up the file naming and numbering to agree with the latest PWG process agreements. 2. Updated the Abstract and Introduction to reflect the additions. 3. Fixed cross references to use the standard numbers as agreed, rather than mnemonic references. 4. Deprecated the "input-document-number" operation attribute ([pwg5100.4] section 9.2.1 in the Create-Document Requests 5. Renamed Send-Data to Send-Document-Data to more clearly reflect the scope of the operation. 6. Added the REQUIRED Close-Job operation to close a job that contains Document objects. Using "last-document" still works too and the Printer MUST support both ways. 7. Retained the idea that the Printer MUST NOT copy down any attributes supplied in the Job Creation operation to the Document object as observable in Document object query responses. Document objects inherit that effect from the Job object. 8. Added the following operation and Document Description attributes: document-container-summary (collection), document-creator-application-name (name(MAX)), document-creator-application-version (text(127)), document-creator-os-name (name(40)), document-creator-os-version (text(40)), document-format-device-id (text(127)), document-format-version (text(127). The "document-container-summary" collection attribute may contain them, plus "document-format" and "document-natural-language". 9. REQUIRED Printers to support "document-format-version" Document Description. 10. Deprecated "document-overrides" and indicated that the agreement is to re-issue [pwg5100.4] without "document-overrides". 11. Prefixed the following three Document Description attributes that are copies of Job Description attributes with "document-" so that no Document attribute has a "job-" prefix: "job-printer-uri" becomes "document-job-printer-uri", "job-uri" becomes "document-job-uri", and "job-id" becomes "document-job-id". 12. Added the encoding for the "document-attributes-tag" as 0x09. 13. Updated the IANA Registration section, but still needs more work. Send any comments to the SM mailing list. Thanks, Tom From info at governmentgrantsandloansforsmallbusiness.com Thu May 15 03:58:51 2003 From: info at governmentgrantsandloansforsmallbusiness.com (Canadian Publications) Date: Thu Jul 12 13:10:36 2007 Subject: [printing-meetingnotes] Government Subsidies, Grants and Loans Message-ID: CANADIAN SUBSIDY DIRECTORY 4865 HWY 138,R.R 1 ST-ANDREWS WEST ONTARIO, KOC 2A0 PRESS RELEASE CANADIAN SUBSIDY DIRECTORY YEAR 2003 EDITION Legal Deposit-National Library of Canada ISBN 2-922870-05-7 The new revised edition of the Canadian Subsidy Directory 2003 is now available. The new edition is the most complete and affordable reference for anyone looking for financial support. It is deemed to be the perfect tool for new or existing businesses, individual ventures, foundations and associations. This Publication contains more than 2000 direct and indirect financial subsidies, grants and loans offered by government departments and agencies, foundations, associations and organisations. In this new 2003 edition all programs are well described. The Canadian Subsidy Directory is the most comprehensive tool to start up a business, improve existent activities, set up a business plan, or obtain assistance from experts in fields such as: Industry, transport, agriculture, communications, municipal infrastructure, education, import-export, labor, construction and renovation, the service sector, hi-tech industries, research and development, joint ventures, arts, cinema, theatre, music and recording industry, the self employed, contests, and new talents. Assistance from and for foundations and associations, guidance to prepare a business plan, market surveys, computers, and much more! The Canadian Subsidy Directory is sold $ 49.95, to obtain a copy please call: Canadian Publications: (866) 322-3376