From don at lexmark.com Tue Feb 12 15:40:04 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:05 2009 Subject: PS> Test Message-ID: <200202122040.PAA16588@interlock2.lexmark.com> This is the first message. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances & Standards * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** From alan_berkema at hp.com Tue Feb 12 17:04:58 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> Test Message-ID: <499DC368E25AD411B3F100902740AD650587B14C@xrose03.rose.hp.com> Got it. -----Original Message----- From: don@lexmark.com [mailto:don@lexmark.com] Sent: Tuesday, February 12, 2002 12:40 PM To: ps@pwg.org Subject: PS> Test This is the first message. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances & Standards * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** From alan_berkema at hp.com Thu Feb 14 13:36:01 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: Telecon 2/19/02 CANCELLED, next 2/26, F2F minutes Message-ID: <499DC368E25AD411B3F100902740AD650587B16A@xrose03.rose.hp.com> All, I will be travelling next week so I need to cancel the 19th teleconference. Teleconference details 2002: Date: Tuesdays Tuesday 26 (USA) (No meeting February 19, Travelling) Through February 26 USA) Time: 8 AM (US PST) 650-690-9354 (T348-9354) ID: 55605 See Minutes attached. Thanks Lee. In addition I believe we opted for Tuesday the 16 for the F2F meeting date. Thanks, Alan > <> -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI Meeting Notes 020802.pdf Type: application/octet-stream Size: 16847 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020214/1220823a/PSIMeetingNotes020802.obj From KOcke at crt.xerox.com Thu Feb 21 10:45:43 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:05 2009 Subject: PS> Editor or Secretary Message-ID: All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From melinda_grant at hp.com Thu Feb 21 11:59:27 2002 From: melinda_grant at hp.com (GRANT,MELINDA (HP-Vancouver,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> Editor or Secretary Message-ID: <6D805D4C4567D411AF32009027B683510855601B@xvan02.vcd.hp.com> Hi Kirk et al, I was assuming the role of secretary included the function of editor when I offered my name as secretary. (I suffer from the same write-and-think disability you mentioned ;-) I'd love to abdicate the note-taking role, but, like you, would like to act as an editor. Is this a role that can effectively be shared? Thanks, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 7:46 AM To: 'ps@pwg.org' Subject: PS> Editor or Secretary All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From KOcke at crt.xerox.com Thu Feb 21 14:02:18 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:05 2009 Subject: PS> Editor or Secretary Message-ID: Melinda, et. al., I'm certainly willing to share the role if that is an acceptable practice. I would still prefer to be an editor, but am willing to do the mundane work if needed. I already know I will not be able to attend the April face to face since we have a baby due any moment now, so even if I was the secretary I'd need to have someone else take the role in April. Kirk -----Original Message----- From: GRANT,MELINDA (HP-Vancouver,ex1) [mailto:melinda_grant@hp.com] Sent: Thursday, February 21, 2002 11:59 AM To: 'ps@pwg.org' Subject: RE: PS> Editor or Secretary Hi Kirk et al, I was assuming the role of secretary included the function of editor when I offered my name as secretary. (I suffer from the same write-and-think disability you mentioned ;-) I'd love to abdicate the note-taking role, but, like you, would like to act as an editor. Is this a role that can effectively be shared? Thanks, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 7:46 AM To: 'ps@pwg.org' Subject: PS> Editor or Secretary All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From melinda_grant at hp.com Thu Feb 21 17:18:55 2002 From: melinda_grant at hp.com (GRANT,MELINDA (HP-Vancouver,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> Editor or Secretary Message-ID: <6D805D4C4567D411AF32009027B68351085560D4@xvan02.vcd.hp.com> Oh, er, poop, I saw the 'ps' and some faulty mental synapse made the mapping to 'xp'... I didn't mean to be signing up for any psi role; my comments were wrt the xhtml-print wg. Forgive the noise, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 11:02 AM To: 'GRANT,MELINDA (HP-Vancouver,ex1)'; 'ps@pwg.org' Subject: RE: PS> Editor or Secretary Melinda, et. al., I'm certainly willing to share the role if that is an acceptable practice. I would still prefer to be an editor, but am willing to do the mundane work if needed. I already know I will not be able to attend the April face to face since we have a baby due any moment now, so even if I was the secretary I'd need to have someone else take the role in April. Kirk -----Original Message----- From: GRANT,MELINDA (HP-Vancouver,ex1) [mailto:melinda_grant@hp.com] Sent: Thursday, February 21, 2002 11:59 AM To: 'ps@pwg.org' Subject: RE: PS> Editor or Secretary Hi Kirk et al, I was assuming the role of secretary included the function of editor when I offered my name as secretary. (I suffer from the same write-and-think disability you mentioned ;-) I'd love to abdicate the note-taking role, but, like you, would like to act as an editor. Is this a role that can effectively be shared? Thanks, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 7:46 AM To: 'ps@pwg.org' Subject: PS> Editor or Secretary All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From harryl at us.ibm.com Mon Feb 25 12:26:46 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:05 2009 Subject: PS> Informal Tally of PS and XHTML formation charter voting Message-ID: I will ask Cindy to confirm the following, officially. At close of voting on Friday we had PS - 11 Approve, Approve (w/comment), 0 Disapprove, 19 no vote. XHTML - 11 Approve, 1 Disapprove (w/comment), 19 no vote. Thus, I believe both charters "pass" and these groups will be formed, possibly with some minor modifications to the charter based on comments. If modified, the charters will be reviewed as a first order of business within the working groups. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- From alan_berkema at hp.com Fri Mar 1 17:36:43 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: Next Teleconference 3/5/02 Message-ID: <499DC368E25AD411B3F100902740AD650587B1B4@xrose03.rose.hp.com> Welcome to PSI, if you would like to join this group please attend the teleconference. In the future we will only send this to the ps list. Agenda: 1) Introductions 2) PSI Overview Presentation 3) Questions PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday February 5 (USA) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 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/join/ Then click New User. ------------------------- On Tuesday use: http://hp.webex.com/join/ Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/5/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Mon Mar 4 18:16:01 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> RE: PWG-ANNOUNCE> [PSI]: Next Teleconference 3/5/02 Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1964@mailsrvnt02.enet.sharplabs.com> Hi folks, At the PWG FTP server, there's a subdirectory for PSI: ftp://ftp.pwg.org/pub/pwg/ps/ In that directory are the following files: -rw-r--r-- 1 pwg staff 52 Feb 12 15:34 Print Services Directory.txt -rw-r--r-- 1 pwg staff 15017 Feb 27 12:35 PSI-Charter-02.pdf -rw-r--r-- 1 pwg staff 66472 Mar 1 18:26 psi_requirements06.pdf -rw-r--r-- 1 pwg staff 452608 Mar 4 13:13 psi-spec22.doc -rw-r--r-- 1 pwg staff 105205 Mar 4 17:39 psi-spec22.pdf I just picked up the 'psi-spec22.doc' (MS Word) and used Acrobat Distiller to convert it to 'psi-spec22.pdf' for the convenience of a wider audience. Cheers, - Ira McDonald High North Inc PS - I included PWG announce on this reply, to make sure people knew about the Word and PDF versions of the work-in-progress PSI spec. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, March 01, 2002 4:37 PM To: 'ps@pwg.org' Cc: 'pwg-announce@pwg.org' Subject: PWG-ANNOUNCE> [PSI]: Next Teleconference 3/5/02 Welcome to PSI, if you would like to join this group please attend the teleconference. In the future we will only send this to the ps list. Agenda: 1) Introductions 2) PSI Overview Presentation 3) Questions PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday February 5 (USA) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 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/join/ Then click New User. ------------------------- On Tuesday use: http://hp.webex.com/join/ Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/5/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Mar 5 17:08:12 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> RE: PWG-ANNOUNCE> Print Services Web Page Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1969@mailsrvnt02.enet.sharplabs.com> Hi Gail, Here are some links to add to the Related Links section of PSI Home Page: Simple Object Access Protocol (SOAP) 1.1 W3C Note 08 May 2000 http://www.w3.org/TR/SOAP/ SOAP Version 1.2 Part 0: Primer W3C Working Draft 17 December 2001 http://www.w3.org/TR/soap12-part0/ SOAP Version 1.2 Part 1: Messaging Framework W3C Working Draft 17 December 2001 http://www.w3.org/TR/soap12-part1/ SOAP Version 1.2 Part 2: Adjuncts W3C Working Draft 17 December 2001 http://www.w3.org/TR/soap12-part2/ Web Services Description Language (WSDL) 1.1 W3C Note 15 March 2001 http://www.w3.org/TR/wsdl Web Services Inspection Language (WS-Inspection) 1.0 http://www-106.ibm.com/developerworks/library/ws-wsilspec.html Cheers, - Ira McDonald High North Inc -----Original Message----- From: Gail Songer [mailto:gsonger@netreon.com] Sent: Monday, March 04, 2002 6:32 PM To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> Print Services Web Page Hi All, I have just uploaded the initial version of the Print Services web page and added a link to it on the main page http://www.pwg.org. If you have any other links/information that you think should be on the page or would useful for the working group, please send them to me and I'll get them on the page. Gail From alan_berkema at hp.com Fri Mar 8 16:55:05 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: Next Teleconference 3/12/02 Message-ID: <499DC368E25AD411B3F100902740AD650587B1EC@xrose03.rose.hp.com> PSI Introduction Slides are on http://www.pwg.org/ps/index.html Agenda: 1) PSI Spec Review PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday March 12 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 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 Tuesday use: http://hp.webex.com The click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/12/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Wed Mar 13 18:05:46 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: minutes 3/12/02, next 3/19 Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF5D@xrose03.rose.hp.com> Agenda: 1) PSI Spec Review PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday March 19 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 3/12/02 Minutes: Attendees: Dave Hall Peter Zehler Kirk Ocke Don Wright Ira Mcdonald Peter Mierau Alan Berkema Dave Hall walked us through the current document and Rose diagrams. These will be posted to the ps site. Peter M. suggested that when the PS creates a URL to a formatted tempory file, we need a way to tell the PS it has been printed. Could refine this with other ideas like: delete immediate, save for xx time for additional prints etc. of course the PS policy may override the request to save for xx days? At the previous call we talked about SOAPv1.1 vs. SOAPv1.2. The concensus was that while SOAPv1.2 may have useful features all current toolkits only support v1.1 (with various degrees of sucess). At this point we will stick with v1.1 unless it becomes apperant that the industry and toolkits roll to v1.2. Talked about use of WSIL. At this meeting Ira stated that WSIL may also be imature and it's usefullness is deminished by lack of deployment. Suggest that PSI needs it's own built in mechanism to find well known named interfaces. Started a list of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- webex oinfo 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/19/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Mon Mar 18 10:00:55 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: Canceled 3/19/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF72@xrose03.rose.hp.com> Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From alan_berkema at hp.com Tue Mar 19 11:26:15 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]:Time change? Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF82@xrose03.rose.hp.com> All, I have had a request to schedule the PSI meetings later in the morning. Originally the meetings were early Pacific time to accommodate Europe. I don't think we have had a lot of European participation so I am open to consider change. If we make it 9:00AM that is noon on the east. Is this an issue for those in the east? Thanks, Alan -----Original Message----- From: Alain Regnier [mailto:alain@tpo.ussj.ricoh.com] Sent: Monday, March 18, 2002 6:54 PM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI]: Canceled 3/19/02 Hi, Would it be possible to schedule the PSI meetings later than 8am PCT? Alain Regnier Ricoh Corp -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, March 18, 2002 7:01 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: Canceled 3/19/02 Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From harryl at us.ibm.com Tue Mar 19 11:50:41 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]:Time change? Message-ID: If it only goes 1 hr. I can accommodate that. Else, I bump into a conflict after the first hr. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "BERKEMA,ALAN C (HP-Roseville,ex1)" Sent by: owner-ps@pwg.org 03/19/2002 09:26 AM To: "'Alain Regnier'" , "BERKEMA,ALAN C (HP-Roseville,ex1)" , "'a PSI pwg.org'" cc: Subject: RE: PS> [PSI]:Time change? All, I have had a request to schedule the PSI meetings later in the morning. Originally the meetings were early Pacific time to accommodate Europe. I don't think we have had a lot of European participation so I am open to consider change. If we make it 9:00AM that is noon on the east. Is this an issue for those in the east? Thanks, Alan -----Original Message----- From: Alain Regnier [mailto:alain@tpo.ussj.ricoh.com] Sent: Monday, March 18, 2002 6:54 PM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI]: Canceled 3/19/02 Hi, Would it be possible to schedule the PSI meetings later than 8am PCT? Alain Regnier Ricoh Corp -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, March 18, 2002 7:01 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: Canceled 3/19/02 Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From imcdonald at sharplabs.com Tue Mar 19 15:49:27 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]:Time change? Message-ID: <116DB56CD7DED511BC7800508B2CA5370A198B@mailsrvnt02.enet.sharplabs.com> Hi, An hour later is fine by me. Harry - the PSI telecons are only supposed to run for 1 hour, so you should have slack anyway. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Tuesday, March 19, 2002 10:51 AM To: BERKEMA,ALAN C (HP-Roseville,ex1) Cc: 'Alain Regnier'; 'a PSI pwg.org' Subject: RE: PS> [PSI]:Time change? If it only goes 1 hr. I can accommodate that. Else, I bump into a conflict after the first hr. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "BERKEMA,ALAN C (HP-Roseville,ex1)" Sent by: owner-ps@pwg.org 03/19/2002 09:26 AM To: "'Alain Regnier'" , "BERKEMA,ALAN C (HP-Roseville,ex1)" , "'a PSI pwg.org'" cc: Subject: RE: PS> [PSI]:Time change? All, I have had a request to schedule the PSI meetings later in the morning. Originally the meetings were early Pacific time to accommodate Europe. I don't think we have had a lot of European participation so I am open to consider change. If we make it 9:00AM that is noon on the east. Is this an issue for those in the east? Thanks, Alan -----Original Message----- From: Alain Regnier [mailto:alain@tpo.ussj.ricoh.com] Sent: Monday, March 18, 2002 6:54 PM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI]: Canceled 3/19/02 Hi, Would it be possible to schedule the PSI meetings later than 8am PCT? Alain Regnier Ricoh Corp -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, March 18, 2002 7:01 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: Canceled 3/19/02 Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From alan_berkema at hp.com Thu Mar 21 12:44:25 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF9B@xrose03.rose.hp.com> All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Thu Mar 21 12:48:29 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A198D@mailsrvnt02.enet.sharplabs.com> Hi Alan, Will there be a revised version of the PSI protocol spec available _before_ the meeting week after next (2 April)? Could you expand on the topic 'Off-Ramp Identifier' a little in email, please? Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 11:44 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 4/2 8:00AM Pacific All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Thu Mar 21 16:44:09 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACFA0@xrose03.rose.hp.com> Ira and all, For Off-Ramp identifier the editors (and I) worked on a proposal that encodes these as XML. Also, the editors have some actions to work on the documents. I believe Kirk said he would not be unable to do his part until next week. Goal is to get the latest posted before the 4/2 meeting. I know this will help folks that can't do webex. Editors please try to send something out by around Thursday 3/28/02. Thanks, Alan -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, March 21, 2002 9:48 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: next 4/2 8:00AM Pacific Hi Alan, Will there be a revised version of the PSI protocol spec available _before_ the meeting week after next (2 April)? Could you expand on the topic 'Off-Ramp Identifier' a little in email, please? Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 11:44 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 4/2 8:00AM Pacific All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Mon Apr 1 12:18:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19B0@mailsrvnt02.enet.sharplabs.com> Hi all, Just a reminder that there's a PSI telecon tomorrow (Tues 2 April) at 8am PST / 11am EST. Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 3:44 PM To: 'McDonald, Ira'; BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: RE: PS> [PSI]: next 4/2 8:00AM Pacific Ira and all, For Off-Ramp identifier the editors (and I) worked on a proposal that encodes these as XML. Also, the editors have some actions to work on the documents. I believe Kirk said he would not be unable to do his part until next week. Goal is to get the latest posted before the 4/2 meeting. I know this will help folks that can't do webex. Editors please try to send something out by around Thursday 3/28/02. Thanks, Alan -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, March 21, 2002 9:48 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: next 4/2 8:00AM Pacific Hi Alan, Will there be a revised version of the PSI protocol spec available _before_ the meeting week after next (2 April)? Could you expand on the topic 'Off-Ramp Identifier' a little in email, please? Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 11:44 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 4/2 8:00AM Pacific All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From dhall at hp.com Tue Apr 2 11:08:59 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> XML Updates Message-ID: <77261E830267D411BD4D00902740AC2507F2A058@xvan01.vcd.hp.com> Hi guys - I snipped the XML updates out of the doc. Dave 1.1 OffRampIdentifier The OffRampIdentifier is an XML document. Example OffRampIdentifiers follow: See bluetooth definitions for additional identifier attributes... The idea is to not only define the identifier for the offramp, but also everything you need to know in order to establish a connection with the identifier. Have a separate XML DTD for each OffRampIdentifier Type. UNC <\\server\share> Port 9100 IP PORT user password FAX phone <\\server\share> number and other stuff Offramp JobControl Soap Endpoint http://a/b/c 1.2 Reference The reference passed into AddContentReference is an XML document. Example References follow: Also defined in bluetooth URL definition... Document URL http://a/b/c Secure Document URL https://a/b/c Document via FTP hostname or ip username password \a\b\c\d\e.doc Another possibility is to simply pass these parameters on the URL. We would need to be sure and define the schemas with a DTD... From alan_berkema at hp.com Mon Apr 8 12:09:51 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: next 4/9 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACFF6@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F Agenda Topic 3.1) Off-RampIdentfier- SOAP endpoint preferred. PORT 9100 & UNC legacy. Add an SNMP endpoint. Responsibility of the PS to contact he Off-Ramp and get it device attributes. Method varies based on Off-RampIdentfier. 3.2) Document reference - Add in BPP reference attributes. OBEX has doc type in header in the mime type filed. Need to add this to document reference. 3.3) IPP to PSI mapping. Purpose: A) Insure that we have not missed anything B) Semantic Alignment C) Leverage back. This section of the spec is like a work sheet to help us work through details of PSI. It may remain as an Appendix. 3.4) RUI or not? 3.5) Get JOBs operation. Functionality & methods 3.6) Persistence policy List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Apr 9 12:36:26 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: minutes 4/9 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACFF8@xrose03.rose.hp.com> Here are the raw notes from todays call. I'll clean it up some for the F2F. See ya on Tuesday Alan PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below Attendees: Alan Berkema Paul Tukodi Dave Hall Jerry Thasher Harry Lewis Ira Mcdonald Kirk Ocke Peter Zehler Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F Agenda Topic 3.1) Off-RampIdentfier- SOAP endpoint preferred. PORT 9100 & UNC legacy. Add an SNMP endpoint. Responsibility of the PS to contact the Off-Ramp and get its device attributes. Method varies based on Off-RampIdentfier. 3.2) Document reference - Add in BPP reference attributes. OBEX has doc type in header in the mime type field. Need to add this to document reference. 3.3) IPP to PSI mapping. Purpose: A) Insure that we have not missed anything B) Semantic Alignment C) Leverage back. This section of the spec is like a work sheet to help us work through details of PSI. It may remain as an Appendix. 3.4) RUI or not? 3.5) Get JOBs per user or all jobs operation. Functionality & methods 3.6) Persistence policy. PS needs to know when the job is actually printed. Keep job record for history. Job itself should hang around for some default time 30 secs/60 seconds. Use Job MIB example. 3.7) Really web based job control. Extensible attributes, via browser. 3.8) Programmatic method for extended attributes. How does client know if the Off-Ramp supports these extended attributes? And then know if some attributes are or are not supported. Meta data -Name, syntax, legal values, text description of what the legal values do. Make it the standard way for all attributes as well as extended attributes. Name required rest optional. 3.9 Mechanism for mapping between PS, Off-Ramp & Client. Knowing what PS the client should talk to. PS to printer mappings. 3.10) Attributes move from object to XML. Combine Base and extended. Name space for base, use different name space for vendor specific. Allows for greater flexibility and works with current tool kits. Also works better with concepts introduced in 3.8. Caveat is that it places the burden of validation on the receiving device. Group felt this was a reasonable trade off, the receiving device needs to be aware that a sending device could send bad attributes (or values). List of known work items: 1) Query Interface for extensibility needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev RequiremntsRequirements doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Apr 9 12:46:53 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: minutes 4/9 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19C6@mailsrvnt02.enet.sharplabs.com> Hi Alan, Looks fine - you captured the two points about: (a) Job MIB (RFC 2707) reference for mimimum job persistence; and (b) the XML declaration of an attribute (or most of it) _is_ the attribute metadata returned by GetJobAttributes (with Name the required minimum returned). Thanks, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Tuesday, April 09, 2002 11:36 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: minutes 4/9 8:00:am Pacific Here are the raw notes from todays call. I'll clean it up some for the F2F. See ya on Tuesday Alan PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below Attendees: Alan Berkema Paul Tukodi Dave Hall Jerry Thasher Harry Lewis Ira Mcdonald Kirk Ocke Peter Zehler Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F Agenda Topic 3.1) Off-RampIdentfier- SOAP endpoint preferred. PORT 9100 & UNC legacy. Add an SNMP endpoint. Responsibility of the PS to contact the Off-Ramp and get its device attributes. Method varies based on Off-RampIdentfier. 3.2) Document reference - Add in BPP reference attributes. OBEX has doc type in header in the mime type field. Need to add this to document reference. 3.3) IPP to PSI mapping. Purpose: A) Insure that we have not missed anything B) Semantic Alignment C) Leverage back. This section of the spec is like a work sheet to help us work through details of PSI. It may remain as an Appendix. 3.4) RUI or not? 3.5) Get JOBs per user or all jobs operation. Functionality & methods 3.6) Persistence policy. PS needs to know when the job is actually printed. Keep job record for history. Job itself should hang around for some default time 30 secs/60 seconds. Use Job MIB example. 3.7) Really web based job control. Extensible attributes, via browser. 3.8) Programmatic method for extended attributes. How does client know if the Off-Ramp supports these extended attributes? And then know if some attributes are or are not supported. Meta data -Name, syntax, legal values, text description of what the legal values do. Make it the standard way for all attributes as well as extended attributes. Name required rest optional. 3.9 Mechanism for mapping between PS, Off-Ramp & Client. Knowing what PS the client should talk to. PS to printer mappings. 3.10) Attributes move from object to XML. Combine Base and extended. Name space for base, use different name space for vendor specific. Allows for greater flexibility and works with current tool kits. Also works better with concepts introduced in 3.8. Caveat is that it places the burden of validation on the receiving device. Group felt this was a reasonable trade off, the receiving device needs to be aware that a sending device could send bad attributes (or values). List of known work items: 1) Query Interface for extensibility needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev RequiremntsRequirements doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From don at lexmark.com Fri Apr 12 16:10:23 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:05 2009 Subject: PS> WSDL for Printing Message-ID: <200204122010.QAA14339@interlock2.lexmark.com> I am representing Lexmark on the Web Services Design Language working group of the W3C. The group is working to fix errors and deficiencies in WSDL 1.1. Has anyone encountered any deficiencies in WSDL 1.1 in the course of PSI or other application of WSDL related to printing that I should identify to the group? If so, please send me a written description. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances and Standards * * Lexmark International * * 740 New Circle Rd C14/082-3 * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** From gsonger at peerless.com Mon Apr 15 11:20:56 2002 From: gsonger at peerless.com (Gail Songer) Date: Wed May 6 14:02:05 2009 Subject: PS> Updated Website Message-ID: Hi! I've just updated the web site with the latest versions of the specifications. Enjoy. Gail From imcdonald at sharplabs.com Mon Apr 15 13:18:42 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> Latest PSI docs on PWG server Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19CF@mailsrvnt02.enet.sharplabs.com> Hi folks, I just fixed up a few PSI document filenames, as follows: 1) Changed underscores to hyphens, because underscores CANNOT be seen in highlighted (underlined) Web links 2) Converted Kirk's IPP mapping (MS Word) to PDF, and fixed filenames. 3) Renamed 'psi.doc/pdf' to 'psi-model-view.doc/pdf' (for clarity). 4) Renamed 'psi.mdl' to 'psi-model.mdl' (Rational Rose model of PSI). Here's a directory listing of the current PSI docs at: ftp://ftp.pwg.org/pub/pwg/ps/ ftp> ls -ltr 200 PORT command successful. 150 Opening ASCII mode data connection for file list. -rw-r--r-- 1 pwg staff 52 Feb 12 15:34 Print Services Directory. txt -rw-r--r-- 1 pwg staff 15017 Feb 27 12:35 PSI-Charter-02.pdf -rw-r--r-- 1 pwg staff 66472 Mar 1 18:26 psi-requirements06.pdf -rw-r--r-- 1 pwg staff 452608 Mar 4 13:13 psi-spec22.doc -rw-r--r-- 1 pwg staff 105205 Mar 4 17:39 psi-spec22.pdf -rw-r--r-- 1 pwg staff 83876 Mar 5 18:30 psi_intro.pdf -rw-r--r-- 1 pwg staff 449536 Mar 13 20:38 psi-spec23.doc -rw-r--r-- 1 pwg staff 4979 Apr 15 11:05 attributes.xsd -rw-r--r-- 1 pwg staff 79360 Apr 15 11:06 psi-ipp-mapping.doc -rw-r--r-- 1 pwg staff 46080 Apr 15 11:06 psi-model-view.doc -rw-r--r-- 1 pwg staff 50176 Apr 15 11:06 psi1.doc -rw-r--r-- 1 pwg staff 412399 Apr 15 11:07 psi-model.mdl -rw-r--r-- 1 pwg staff 142986 Apr 15 11:07 psi-model-view.pdf -rw-r--r-- 1 pwg staff 156414 Apr 15 11:07 psi-requirements07.pdf -rw-r--r-- 1 pwg staff 410112 Apr 15 11:08 psi-spec25.doc -rw-r--r-- 1 pwg staff 193686 Apr 15 11:08 psi-spec25.pdf -rw-r--r-- 1 pwg staff 20621 Apr 15 12:52 psi-ipp-mapping.pdf And below is Alan Berkema's note from last Friday (12 April). Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, April 12, 2002 12:00 PM To: 'Don Levinstone'; 'Ira McDonald'; 'Jerry Thrasher'; 'Kirk Ocke'; 'Peter Mierau'; 'Peter Zehler'; 'Lee Farrell'; 'Paul@intermate-us.com' Subject: FW: PSI docs Importance: High This doesn't seem to be getting out. Here it is just in case. Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, April 12, 2002 8:52 AM To: 'Harry Lewis' Cc: 'Don Wright' Subject: FW: PSI reqs Importance: High Harry, We sent this stuff out a few days ago. Course it is to big for the reflector. Gail does not seem to be around. Can you put it on the ps web site. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Thursday, April 11, 2002 2:33 PM To: 'Gail Songer' Subject: PSI reqs Gail, Can you post these docs and send a note to the reflector. Thanks, see ya in Boston From imcdonald at sharplabs.com Mon Apr 15 13:39:36 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> Updated Website Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19D1@mailsrvnt02.enet.sharplabs.com> Hi, See my note a little after Gail's. Some of the specs had utterly opaque names. I renamed them. I also converted to the IPP mapping (Kirk Ocke's work) to PDF for easier access by all. Gail - thanks for posting the latest specs. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Gail Songer [mailto:gsonger@peerless.com] Sent: Monday, April 15, 2002 10:21 AM To: ps@pwg.org Subject: PS> Updated Website Hi! I've just updated the web site with the latest versions of the specifications. Enjoy. Gail From don at lexmark.com Mon Apr 15 13:42:27 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:05 2009 Subject: PS> Latest PSI docs on PWG server Message-ID: <200204151742.NAA10246@interlock2.lexmark.com> I have undone what Ira did so the links from the Web page work. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances and Standards * * Lexmark International * * 740 New Circle Rd C14/082-3 * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** "McDonald, Ira" on 04/15/2002 01:18:42 PM To: "'BERKEMA,ALAN C (HP-Roseville,ex1)'" , "'ps@pwg.org'" cc: (bcc: Don Wright/Lex/Lexmark) Subject: PS> Latest PSI docs on PWG server Hi folks, I just fixed up a few PSI document filenames, as follows: 1) Changed underscores to hyphens, because underscores CANNOT be seen in highlighted (underlined) Web links 2) Converted Kirk's IPP mapping (MS Word) to PDF, and fixed filenames. 3) Renamed 'psi.doc/pdf' to 'psi-model-view.doc/pdf' (for clarity). 4) Renamed 'psi.mdl' to 'psi-model.mdl' (Rational Rose model of PSI). Here's a directory listing of the current PSI docs at: ftp://ftp.pwg.org/pub/pwg/ps/ ftp> ls -ltr 200 PORT command successful. 150 Opening ASCII mode data connection for file list. -rw-r--r-- 1 pwg staff 52 Feb 12 15:34 Print Services Directory. txt -rw-r--r-- 1 pwg staff 15017 Feb 27 12:35 PSI-Charter-02.pdf -rw-r--r-- 1 pwg staff 66472 Mar 1 18:26 psi-requirements06.pdf -rw-r--r-- 1 pwg staff 452608 Mar 4 13:13 psi-spec22.doc -rw-r--r-- 1 pwg staff 105205 Mar 4 17:39 psi-spec22.pdf -rw-r--r-- 1 pwg staff 83876 Mar 5 18:30 psi_intro.pdf -rw-r--r-- 1 pwg staff 449536 Mar 13 20:38 psi-spec23.doc -rw-r--r-- 1 pwg staff 4979 Apr 15 11:05 attributes.xsd -rw-r--r-- 1 pwg staff 79360 Apr 15 11:06 psi-ipp-mapping.doc -rw-r--r-- 1 pwg staff 46080 Apr 15 11:06 psi-model-view.doc -rw-r--r-- 1 pwg staff 50176 Apr 15 11:06 psi1.doc -rw-r--r-- 1 pwg staff 412399 Apr 15 11:07 psi-model.mdl -rw-r--r-- 1 pwg staff 142986 Apr 15 11:07 psi-model-view.pdf -rw-r--r-- 1 pwg staff 156414 Apr 15 11:07 psi-requirements07.pdf -rw-r--r-- 1 pwg staff 410112 Apr 15 11:08 psi-spec25.doc -rw-r--r-- 1 pwg staff 193686 Apr 15 11:08 psi-spec25.pdf -rw-r--r-- 1 pwg staff 20621 Apr 15 12:52 psi-ipp-mapping.pdf And below is Alan Berkema's note from last Friday (12 April). Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, April 12, 2002 12:00 PM To: 'Don Levinstone'; 'Ira McDonald'; 'Jerry Thrasher'; 'Kirk Ocke'; 'Peter Mierau'; 'Peter Zehler'; 'Lee Farrell'; 'Paul@intermate-us.com' Subject: FW: PSI docs Importance: High This doesn't seem to be getting out. Here it is just in case. Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, April 12, 2002 8:52 AM To: 'Harry Lewis' Cc: 'Don Wright' Subject: FW: PSI reqs Importance: High Harry, We sent this stuff out a few days ago. Course it is to big for the reflector. Gail does not seem to be around. Can you put it on the ps web site. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Thursday, April 11, 2002 2:33 PM To: 'Gail Songer' Subject: PSI reqs Gail, Can you post these docs and send a note to the reflector. Thanks, see ya in Boston From imcdonald at sharplabs.com Wed Apr 17 15:27:46 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> FW: New I-D for Internationalized Resource Identifiers Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19DF@mailsrvnt02.enet.sharplabs.com> Hi, FYI - latest version of IRIs (fully internationalized UTF-8 based URIs). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Martin Duerst [mailto:duerst@w3.org] Sent: Wednesday, April 17, 2002 2:41 AM To: www-international@w3.org Subject: New I-D for Internationalized Resource Identifiers Dear Web Internationalizers, I have just submitted draft-w3c-i18n-iri-00.txt to the Internet Drafts editor. This draft replaces draft-masinter-url-i18n-08.txt. It should be published in a few hours/days. In the mean time it is available at http://www.w3.org/International/2002/draft-w3c-i18n-iri-00.txt. Based on discussions at the W3C Technical Plenary in February, and in particular on input from Larry Masinter, we have made some changes in the responsibilities for the Internationalized Resource Identifiers (IRI) draft, as follows: - The W3C I18N WG is taking on responsibility for carefully reviewing the current draft and bringing it to maturity for submission to the IESG. - Larry is glad to step down as a co-editor, and Michel Suignard has volunteered to become a new co-editor. Many thanks to Larry for his work as co-author of many earlier versions of this document. This has resulted in the name change. The document will still be handled as an individual submission from the point of view of the IETF. We hope to take this document to IETF/W3C Last Call in May, after some more work. Please review draft-w3c-i18n-iri-00.txt and send comments to w3c-i18n-comments@w3.org (publicly archived at http://lists.w3.org/Archives/Public/www-i18n-comments/). Regards, Martin. From alan_berkema at hp.com Fri Apr 19 12:45:53 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: teleconference 4/23 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD030@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 29? (In Barcelona) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Will work on an agenda: See webex info below ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 21690293 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Fri Apr 19 16:24:56 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: requirements ver 0.071 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD035@xrose03.rose.hp.com> Only editorial changes. Don if you do not get this twice can you inform Graydon that I sent it at ~1:25 PST Thanks, Alan From KOcke at crt.xerox.com Mon Apr 22 10:08:44 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: teleconference 4/23 8:00:am Pacific Message-ID: As many of you may have noticed I did not make the Boston meeting. My sincere apologies. I was unfortunately not able to make the four hour drive from on Tuesday due to illness. "See" you at the teleconference. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, April 19, 2002 12:46 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: teleconference 4/23 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 29? (In Barcelona) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Will work on an agenda: See webex info below ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 21690293 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Apr 23 16:54:52 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: teleconference 4/30 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD057@xrose03.rose.hp.com> -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, April 19, 2002 9:46 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: teleconference 4/23 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Dave Hall will lead and set the agenda. He will also send out webex info. At the 4/23 meeting we spent the entire session reviewing Kirks IPP to PSI mapping document. The next revision will reflect the changes. Will also modify the PSI spec to add some of the attributes of IPP. Actions from F2F: Define Off-Ramp Identifier Schema - Dave & Kirk Add Document Reference as discussed to next rev of spec. - Dave Send out class attribute structure - Peter Send out Status schema - Peter Define Job Attributes for Get Jobs - Peter Look at UPDF for Extended Attribute Definition - all Actions from call - IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave From alan_berkema at hp.com Thu Apr 25 18:10:43 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: New docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD075@xrose03.rose.hp.com> Hey All, I just posted psi042204.pdf and psi-spec26.pdf to the PS ftp site. Thanks, Alan From don at lexmark.com Fri Apr 26 10:30:06 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: New docs Message-ID: <200204261431.KAA02197@interlock2.lexmark.com> All: So that the Web Site points to the latest versions without requiring changes to the site for each new version, I have changed the names of Alan's files as follows: psi042204.pdf ---> psi-model-view.pdf psi-spec26.pdf ---> psi-spec-latest.pdf In order to have an archive of these files as we move forward, we should always upload the files with the version number or date included in the file name and then upload the same files with the generic name. Happy hunting!! ********************************************** Don Wright don@lexmark.com Member, IEEE SA Standards Board Member, IEEE-ISTO Board of Directors f.wright@ieee.org / f.wright@computer.org Director, Alliances & Standards Lexmark International 740 New Circle Rd Lexington, Ky 40550 859-825-4808 (phone) 603-963-8352 (fax) ********************************************** "BERKEMA,ALAN C (HP-Roseville,ex1)" on 04/25/2002 06:10:43 PM To: "'a PSI pwg.org'" cc: (bcc: Don Wright/Lex/Lexmark) Subject: PS> [PSI]: New docs Hey All, I just posted psi042204.pdf and psi-spec26.pdf to the PS ftp site. Thanks, Alan From dhall at hp.com Tue Apr 30 10:56:40 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> FW: Meeting Invitation from David Hall Message-ID: <77261E830267D411BD4D00902740AC2507F2A2E8@xvan01.vcd.hp.com> Subject: Meeting Invitation from David Hall David Hall, David Hall has invited you to join a meeting on the Web, using WebEx. ------------------------- TO JOIN THE MEETING ------------------------- On 4/30/2002, at 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time), click this URL: https://hp.webex.com/webex/e.php?AT=JE&EventID=74715997&UUID=4434397 The password is: mypsi ------------------------- 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. To set up now, go to: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: psi Date: 4/30/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 28519863 Meeting Password: mypsi Teleconference: None Agenda: Host: David Hall 1(360)212x4228 mailto:dhall@hp.com http://www.webex.com We've got to start meeting like this(TM) From imcdonald at sharplabs.com Tue Apr 30 14:04:20 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> FW: Registration of new charsets: UTF-32, UTF-32BE, UTF-32LE Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19EF@mailsrvnt02.enet.sharplabs.com> Hi folks, Below are the registrations for the three labels for UTF-32 (UCS-4 restricted to the 'UTF-16 accessible' first million codepoints). Cheers, - Ira McDonald High North Inc -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Friday, April 12, 2002 11:54 AM To: Martin Duerst; Mark Davis Cc: Harald Tveit Alvestrand; ietf-charsets@iana.org Subject: RE: Registration of new charsets: UTF-32, UTF-32BE, UTF-32LE Martin and Mark, Big apologies for the delay. The following have been added to the Character Sets registry: Name: UTF-32 [Davis] MIBenum: 1017 Source: Alias: None Name: UTF-32BE [Davis] MIBenum: 1018 Source: Alias: None Name: UTF-32LE [Davis] MIBenum: 1019 Source: Alias: None Please see: Please let me know if anything appears incorrectly or if you have any questions. Thank you, Michelle S. Cotton IANA Administrator From imcdonald at sharplabs.com Tue Apr 30 14:06:38 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> FW: New IANA 'character-sets' directory Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19F0@mailsrvnt02.enet.sharplabs.com> Hi folks, New home for the IANA Charsets Registry. Tom Hastings - please note for upcoming IPP documents References sections edits. Cheers, - Ira McDonald High North Inc -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Thursday, April 18, 2002 1:47 PM To: Martin Duerst; Harald Tveit Alvestrand Cc: ietf-charsets@iana.org Subject: RE: Fixing redirects for 'character-sets' directory Martin and Harald, I have made some changes to the Character Set information that is linked from the IANA page at http://www.iana.org/numbers.htm. These changes include the following: I have added: This now replaces the isi.edu page. At: I have updated the registrations that include pointers to registration templates to now point to www.iana.org Please let me know if you see anything that appears incorrect. Michelle IANA From Lee.Farrell at cda.canon.com Wed May 1 22:47:00 2002 From: Lee.Farrell at cda.canon.com (Farrell, Lee) Date: Wed May 6 14:02:05 2009 Subject: PS> PSI Meeting Notes -- Apr '02 Message-ID: <> =========================== Lee Farrell Canon Development Americas 110 Innovation Drive Irvine, CA 92612 (949) 856-7163 - voice (949) 856-7510 - fax lee.farrell@cda.canon.com =========================== -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI Meeting Notes 020416.pdf Type: application/octet-stream Size: 20065 bytes Desc: PSI Meeting Notes 020416.pdf Url : http://www.pwg.org/archives/ps/attachments/20020501/bfa36e82/PSIMeetingNotes020416.obj From imcdonald at sharplabs.com Mon May 6 17:25:53 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:05 2009 Subject: PS> I-D Guidelines for XML in IETF Protocols Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19FB@mailsrvnt02.enet.sharplabs.com> Hi folks, RECOMMENDED reading For anyone interested in XML-based protocols - Bob Herriot, Dave Hall, Kirk Ocke, and other PWG editors. In the IETF repository 'ftp://ftp.ietf.org/internet-drafts/' see: "Guidelines for the Use of XML within IETF Protocols", by Scott Hollenbeck (VeriSign), Marshall Rose (Dover Beach), Larry Masinter (Adobe). (29 April 2002) As noted below, this document is intended to become an IETF BCP (Best Current Practice) RFC. Cheers, - Ira McDonald High North Inc ---------------------------------------- Abstract The Extensible Markup Language (XML) is a framework for structuring data. While it evolved from SGML -- a markup language primarily focused on structuring documents -- XML has evolved to be a widely- used mechanism for representing structured data. There are a wide variety of Internet protocols being developed; many have need for a representation for structured data relevant to their application. There has been much interest in the use of XML as a representation method. This document describes basic XML concepts, analyzes various alternatives in the use of XML, and provides guidelines for the use of XML within IETF standards-track protocols. Intended Publication Status It is the goal of the authors that this draft (when completed and then approved by the IESG) be published as a Best Current Practice (BCP). Conventions Used In This Document This document recommends, as policy, what specifications for Internet protocols -- and, in particular, IETF standards track protocol documents -- should include as normative language within them. The capitalized keywords "SHOULD", "MUST", "REQUIRED", etc. are used in the sense of how they would be used within other documents with the meanings as specified in RFC 2119 [1]. ---------------------------------------- Table of Contents 1. Introduction and Overview . . . . . . . . . . . . . . . . . 4 1.1 Intended Audience . . . . . . . . . . . . . . . . . . . . . 4 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 XML Evolution . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 XML Users, Support Groups, and Additional Information . . . 5 2. XML Selection Considerations . . . . . . . . . . . . . . . . 6 3. XML Alternatives . . . . . . . . . . . . . . . . . . . . . . 8 4. XML Use Considerations and Recommendations . . . . . . . . . 10 4.1 XML Declarations . . . . . . . . . . . . . . . . . . . . . . 10 4.2 XML Processing Instructions . . . . . . . . . . . . . . . . 10 4.3 Well-Formedness . . . . . . . . . . . . . . . . . . . . . . 11 4.4 Validity and Extensibility . . . . . . . . . . . . . . . . . 11 4.5 Namespaces . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.5.1 Namespaces and Attributes . . . . . . . . . . . . . . . . . 13 4.6 Element and Attribute Design Considerations . . . . . . . . 13 4.7 Binary Data . . . . . . . . . . . . . . . . . . . . . . . . 15 4.8 Incremental Processing . . . . . . . . . . . . . . . . . . . 15 5. Internationalization Considerations . . . . . . . . . . . . 16 5.1 Character Sets and Encodings: UTF-8 and UTF-16 . . . . . . . 16 5.2 Language Declaration . . . . . . . . . . . . . . . . . . . . 16 5.3 Other Considerations . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 Normative References . . . . . . . . . . . . . . . . . . . . 21 Informative References . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 24 A. Appendix A: Change History . . . . . . . . . . . . . . . . . 26 Full Copyright Statement . . . . . . . . . . . . . . . . . . 28 From dhall at hp.com Mon May 6 18:28:56 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> No PSI meeting tomorrow Message-ID: <77261E830267D411BD4D00902740AC2507F2A3C6@xvan01.vcd.hp.com> I haven't had any time to update docs, and Alan won't be available.. See you next week! David Hall HP From alan_berkema at hp.com Fri May 10 16:00:48 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD08A@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From PZehler at crt.xerox.com Mon May 13 12:26:36 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:05 2009 Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: All, Attached is a class hierarchy for operational attributes. I have shown them in a PWG semantic model specific way. I used CreateJob for InvokeJob, AddDocument for AddContent Post and Reference. I used the GetJobs, GetJobAttributes and GetPrinterAttributes for all the status and attribute calls in PSI. It does demonstrate that classes are dderive form a base clas and are specialized for job creation, content addition, queries and query lists (i.e. list of jobs/documents). I only have the IPP specific ways of identifying a target. I assume that when PSI defines the offramp identifier it will be another choice in the "Target" complex type. I will send the XML schema under separate cover. Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, May 10, 2002 4:01 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: OperationalAttributes.pdf Type: application/octet-stream Size: 130729 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020513/6b04fa11/OperationalAttributes.obj From PZehler at crt.xerox.com Mon May 13 12:29:24 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: All, The XML Schema demonstrating operational attributes. Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, May 10, 2002 4:01 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: PsiOperational.xsd Type: application/octet-stream Size: 6538 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020513/55b81342/PsiOperational.obj From alan_berkema at hp.com Tue May 14 11:01:29 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> RE: [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD091@xrose03.rose.hp.com> Meeting Number: 21248466 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, May 10, 2002 1:01 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: teleconference 5/14 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue May 14 14:50:05 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/14, next 5/21 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD099@xrose03.rose.hp.com> *Note new phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 21 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Tom Hastings 05/21/02 Agenda 1) review updated doc with first pass at including attributes expected 5/16 PM. 05/14/02 Agenda: 1) Review Peter's attribute document. Minutes: Spent the entire meeting talking about what should be a method parameter vs. an attribute. Great discussion on how to partition things for interoperability. One extreme is that we just have a goForIt method with all the operation details in XML another is that all operation choices are parameters. I think we achieved consensus to minimize parameters, keeping those that optimize PSI and keep the majority in XML for interoperable extensibility. Dave & Kirk & Alan will take a first pass at merging Peter's doc into the PSI spec. Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Wed May 15 18:36:41 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: New docs 05/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD09F@xrose03.rose.hp.com> All, Updated web site as follows: added both sets of these files: psi051502.pdf ---> psi-model-view.pdf psi-spec27.pdf ---> psi-spec-latest.pdf As well as: attributes051502.xsd reference051502.xsd targetdevice051502.xsd Thanks, Alan From alan_berkema at hp.com Thu May 16 18:36:27 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: More New docs 05/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD0B1@xrose03.rose.hp.com> Ftp'd another one from Kirk offramp051402.xsd Alan ---- -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Wednesday, May 15, 2002 3:37 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: New docs 05/15/02 All, Updated web site as follows: added both sets of these files: psi051502.pdf ---> psi-model-view.pdf psi-spec27.pdf ---> psi-spec-latest.pdf As well as: attributes051502.xsd reference051502.xsd targetdevice051502.xsd Thanks, Alan From alan_berkema at hp.com Tue May 21 16:32:29 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD0C8@xrose03.rose.hp.com> *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 28 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Don Wright Bob Taylor Don Levinstone Lee Farrell Ira McDonald 05/28/02 Agenda 1) review template attributes 2) review Target Device Identifier and Reference schema 3) Review actions 05/21/02 Agenda: 1) Review Latest Selected Logical View Report (psi051505). Minutes: 1) Reviewed how Peter's IPP attributes document relates to PSI. Most map to attributes, however, last document takes the place of invoke complete as a Boolean parameter. Attributes schemas: Job Attributes - Apply to the entire Job and all the documents Document Attributes - Overall general characteristics of a document Template Attribute - Name is a left over from IPP. We think processing attributes might be a better name. These a things like number of copies, N-up etc. Requested Attributes - inherit from Job & Template attributes Exception Attributes - List of attributes and values that the device does not support. 2) Dave did a quick review of the latest PSI spec (psi_spec051502). Group agreed to and accept changes/revisions from previous reviews. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From PZehler at crt.xerox.com Thu May 23 08:47:24 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:06 2009 Subject: PS> PWG Semantic Model Message-ID: All, The Print semantics that we defined in IPP are being used throughout the industry. The print system may be less functional (e.g. UPnP) or much more complex (e.g. JDF DigitalPrinting). The important point is that whenever possible the semantics are being reused. The reuse is a great benefit to Printer manufacturers. It simplifies the logic necessary to incorporate our devices into these various network environments. It speeds the definition of printing protocols/systems since the semantics of common features need not be reargued. One of the barriers to the use of the PWG print model is its tight association with IPP. In the definition of IPP we clearly separated the model from the protocol. RFC2911 covers the base semantics. We also have extensions to the model defined in some Internet Drafts and IEEE-ISTO PWG standards. I believe we should split the IPP semantic model from the IPP protocol. Using the "PWG Semantic Model" in discussions around industry wide agreed upon print semantics avoids the "IPP baggage". I believe the separation will foster reuse in various network printing environments and standards. The separation will not affect compatibility with IPP. To begin the conversation I though we might start with the definition of a "PrintJob Ticket". The existing semantics has the Job Template Attributes that cover most of a PrintJob Ticket. These cover the semantics of the production instructions. There are some additional descriptive and control attributes that are required. Examples include "jobName", "jobRequestingUserName" and "attributeFidelity". These attributes are normally held in an operation's Operational Attributes. Often there is a direct mapping to a Job's Description Attribute as with "jobName". There are cases where the mapping is simple between the Operational Attribute and the Description Attribute as with "JobRequestingUserName" mapping to "JobOriginatingUserName". We even have cases where there is no mapping such as with "attributeFidelity". We have already agreed on the semantics. We need to work out what a freestanding PrintJob Ticket will look like for the PWG. I have uploaded an XML schema definition for RFC2911. The schema includes some types (e.g. rangeOfInteger), a Job and the elements that compose a Job, namely Job Description and Job Template elements. Included is a sample PrintJob Ticket based on the Job Template. I thought a conversation around a Print Job and a PrintJob Ticket would be appropriate. Some rules I used in the schema mapping: 1) Data types are simplified where ever possible. ( "nameWithLanguage" becomes "string" with a length restriction) 2) For attributes (and operations) the '-' character is dropped and the following character is capitalized. ("job-name" becomes "jobName") 3) Attribute value strings remain the same. ("job-state-reasons"='job-printing' becomes "jobStateReasons"='job-printing') 4) Any attribute with the string "ipp" has the "ipp" string removed. ("ipp-attribute-fidelity" becomes "attributeFidelity") 5) All IPP attributes are represented as XML elements. 6) All attribute groups are represented as an ordered set of elements (i.e. sequence) 7) All enums are represented as strings using the string associated with the integer value. ("job-state"='3' becomes "jobState"="pending") 8) All type 1 enumes are represented as a "string" type with an enumerations restriction. (i.e. can not be extended) 9) All type 2 and 3 are represented as a "string". The standardized values are captured as appinfo annotations. (i.e. allows vendor and site extensions) 10) Multivalue attributes are represented as a single instance of an element that contains a sequence of elements (see "finishings" in sample PrintJobTicket or JobTemplate schema) 11) shema allows addition of new elements via "xsd:any" and places no restriction on namespace of addition. Some PWG specific types: "ftp://pwg.org/pub/pwg/Semantic_model/typesPWG.xsd" The Job: "ftp://pwg.org/pub/pwg/Semantic_model/Job.xsd" The Job Description attributes(i.e. XML elements) for the Job: "ftp://pwg.org/pub/pwg/Semantic_model/JobDescription.xsd" The Job Template attributes(i.e. XML elements) for the Job: "ftp://pwg.org/pub/pwg/Semantic_model/JobDescription.xsd" A Sample Print Job Ticket based on Job Template attributes: "ftp://pwg.org/pub/pwg/Semantic_model/PrintJobTicket.xml" I also have a 21 page PWG Semantic Model Overview document that I will send out tomorrow. This version is limited to RFC2911. It is a very concise semantic guide for those of us who are not IPP experts. It describes the model, objects, attributes and actions as briefly as possible. It contains references to RFC2911 sections for those who want the bloody details. Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 Though the printer is part of the schema I thought we would start with the Job and "PrintJobTicket" discussion. I have uploaded a version of a Printer Schema. I also have done some work modeling the operations and their associated messages. They are not ready to be shared yet. The Printer: "ftp://pwg.org/pub/pwg/Semantic_model/Printer.xsd" The Printer Description attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterDescription.xsd" The Printer's Job Template attributes are represented in the schema as the combination of PrinterDefaults, PrinterSupported and PrinterReady: The PrinterDefaults attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterDefaults.xsd" The PrinterSupported attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterSupported.xsd" The PrinterReady attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterReady.xsd" From KOcke at crt.xerox.com Tue May 28 08:13:01 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific Message-ID: All, I will not be able to make today's teleconference; I have another commitment. So, we can either delay the reference and offramp schema discussion, or you can begin to tear them apart and forward me the results; I'm fine with either approach. Sorry for the late notice about not being able to attend. Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Tuesday, May 21, 2002 4:32 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 28 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Don Wright Bob Taylor Don Levinstone Lee Farrell Ira McDonald 05/28/02 Agenda 1) review template attributes 2) review Target Device Identifier and Reference schema 3) Review actions 05/21/02 Agenda: 1) Review Latest Selected Logical View Report (psi051505). Minutes: 1) Reviewed how Peter's IPP attributes document relates to PSI. Most map to attributes, however, last document takes the place of invoke complete as a Boolean parameter. Attributes schemas: Job Attributes - Apply to the entire Job and all the documents Document Attributes - Overall general characteristics of a document Template Attribute - Name is a left over from IPP. We think processing attributes might be a better name. These a things like number of copies, N-up etc. Requested Attributes - inherit from Job & Template attributes Exception Attributes - List of attributes and values that the device does not support. 2) Dave did a quick review of the latest PSI spec (psi_spec051502). Group agreed to and accept changes/revisions from previous reviews. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue May 28 12:16:00 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A17@mailsrvnt02.enet.sharplabs.com> Hi folks, Sorry - I also had to miss this morning's telecon. Will there be a telecon next Tuesday (5 June)? Cheers, - Ira McDonald -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, May 28, 2002 8:13 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific All, I will not be able to make today's teleconference; I have another commitment. So, we can either delay the reference and offramp schema discussion, or you can begin to tear them apart and forward me the results; I'm fine with either approach. Sorry for the late notice about not being able to attend. Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Tuesday, May 21, 2002 4:32 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 28 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Don Wright Bob Taylor Don Levinstone Lee Farrell Ira McDonald 05/28/02 Agenda 1) review template attributes 2) review Target Device Identifier and Reference schema 3) Review actions 05/21/02 Agenda: 1) Review Latest Selected Logical View Report (psi051505). Minutes: 1) Reviewed how Peter's IPP attributes document relates to PSI. Most map to attributes, however, last document takes the place of invoke complete as a Boolean parameter. Attributes schemas: Job Attributes - Apply to the entire Job and all the documents Document Attributes - Overall general characteristics of a document Template Attribute - Name is a left over from IPP. We think processing attributes might be a better name. These a things like number of copies, N-up etc. Requested Attributes - inherit from Job & Template attributes Exception Attributes - List of attributes and values that the device does not support. 2) Dave did a quick review of the latest PSI spec (psi_spec051502). Group agreed to and accept changes/revisions from previous reviews. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From PZehler at crt.xerox.com Wed May 29 16:03:43 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:06 2009 Subject: PS> PWG Semantic Model Overview Message-ID: All, As promised here is a pointer to an initial version of a PWG Semantic Model Overview document. This version is limited to RFC2911. It is a very concise semantic guide for those of us who are not IPP experts. It describes the model, objects, attributes and actions as briefly as possible. It contains references to RFC2911 sections for those who want the bloody details. The pdf version of the PWG Semantic Model Overview document can be found at: "ftp://pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-Overview.pdf" Please use this version for any comments since it has line numbers. An MS Word version of the document is available in the same directory with a similar file name (.doc instead of .pdf). Comments welcomed, Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 From alan_berkema at hp.com Thu May 30 17:24:18 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD0FB@xrose03.rose.hp.com> *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Sat Jun 1 18:42:39 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> RFC 3282 - Content Language Header Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A19@mailsrvnt02.enet.sharplabs.com> Hi folks, For HTTP and other protocols, here's the Content-Language header definition. Available at: ftp://ftp.isi.edu/in-notes/rfc3282.txt Cheers, - Ira McDonald High North Inc --------------------------------------------------------- [from RFC 3282] Abstract This document defines a "Content-language:" header, for use in cases where one desires to indicate the language of something that has RFC 822-like headers, like MIME body parts or Web documents, and an "Accept-Language:" header for use in cases where one wishes to indicate one's preferences with regard to language. From imcdonald at sharplabs.com Sun Jun 2 12:38:41 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> UDDI LDAP Schema I-D v0.1 (31 May 2002) Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A1A@mailsrvnt02.enet.sharplabs.com> Hi folks, A set of attributes and classes (see excerpts below) for UDDI (Universal Description, Discovery, and Integration) business and service objects stored in LDAP directories. Worth reading. ftp://ftp.ietf.org/internet-drafts/draft-bergeson-uddi-ldap-schema-01.txt Cheers, - Ira McDonald High North Inc ---------------------------- [excerpts] 5. Attribute Type Definitions The following attribute types are defined in this document: uddiBusinessKey uddiAuthorizedName uddiOperator uddiName uddiDescription uddiDiscoveryURLs uddiUseType uddiPersonName uddiPhone uddiEMail uddiSortCode uddiTModelKey uddiAddressLine uddiIdentifierBag uddiCategoryBag uddiKeyedReference uddiServiceKey uddiBindingKey uddiAccessPoint uddiHostingRedirector uddiInstanceDescription uddiInstanceParms uddiOverviewDescription uddiOverviewURL uddiFromKey uddiToKey uddiUUID uddiIsHidden 6. Object Class Definitions The following object classes are defined in this document: uddiBusinessEntity uddiContact uddiAddress uddiBusinessService uddiBindingTemplate uddiTModelInstanceInfo uddiTModel uddiPublisherAssertion From KOcke at crt.xerox.com Tue Jun 4 09:47:21 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: offramp.xsd Type: application/octet-stream Size: 4760 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020604/14b8df3d/offramp.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 3325 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020604/14b8df3d/reference.obj From KOcke at crt.xerox.com Tue Jun 4 12:27:14 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 2982 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020604/ab3cd1c5/reference.obj From imcdonald at sharplabs.com Wed Jun 5 13:43:25 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A1D@mailsrvnt02.enet.sharplabs.com> Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From KOcke at crt.xerox.com Thu Jun 6 08:58:10 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: Ira, good comments. The "type" attribute was related to the document format, not the FTP transfer mode, and it was removed since "document-format" is specified elsewhere. However, you make a good point, namely, that if the client knows that the transfer mode should be text or binary it would be useful to specify it. So, I propose adding a "type" attribute to the "ftp" element with those semantics (will not include directory lookup since that is not applicable). I'm not sure that the IANA Charset is needed. I think simply allowing a client to specify text/binary is sufficient. Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From KOcke at crt.xerox.com Thu Jun 6 10:31:20 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> Updated offramp and reference schemas Message-ID: All, here are the latest updates. The changes include Ira's recent feedback (see below), addition of some annotations, changing all references to ipAddress to host and changing ipAddressType to hostType. Questions: the pathType has an attribute that specifies the OS. Is there a well defined (preferably IANA) list of OS's or file systems that would be appropriate here? Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: offramp.xsd Type: application/octet-stream Size: 4757 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020606/53009ddd/offramp.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 3972 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020606/53009ddd/reference.obj From imcdonald at sharplabs.com Thu Jun 6 13:32:56 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A23@mailsrvnt02.enet.sharplabs.com> Hi Kirk, OK - the IANA charset (on reflection) is conveyed in the 'charset' parameter of the MIME media type specified in the 'document-format' attribute (and defaults if omitted to implementation defined charset guessing - which is not very good). What if PSI tightened up and said the 'charset' parameter SHOULD be specified (whenever known by the invoking client)? Cheers, - Ira McDonald High North Inc -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, June 06, 2002 8:58 AM To: 'McDonald, Ira'; Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Ira, good comments. The "type" attribute was related to the document format, not the FTP transfer mode, and it was removed since "document-format" is specified elsewhere. However, you make a good point, namely, that if the client knows that the transfer mode should be text or binary it would be useful to specify it. So, I propose adding a "type" attribute to the "ftp" element with those semantics (will not include directory lookup since that is not applicable). I'm not sure that the IANA Charset is needed. I think simply allowing a client to specify text/binary is sufficient. Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Thu Jun 6 13:46:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> Updated offramp and reference schemas [OS names] Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A24@mailsrvnt02.enet.sharplabs.com> Hi Kirk, Yes, there's an IANA registry of operating system names. It is now referenced in the IPP Driver Install spec: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipp-install-04.txt The IPP Driver Install spec defines a composite Printer attribute named "client-print-support-files-supported", which in turn defines the 'field': "os-type" One or more REQUIRED comma-separated LOWER-CASE 'keyword' strings identifying the operating system types supported by this set of Client Print Support Files. Valid values are the operating system names defined in the IANA document [os-names] and the special keyword value: 'unknown'. Although the IANA registry requires that the names be all upper-case, the values MUST be all lower case in this field (plus hyphen-minus (-), period (.), and slash (/)). Examples: 'linux', 'linux-2.2', 'os/2', 'sun-os-4.0', 'unix', 'unix-bsd', 'win32', 'windows-95', 'windows-98', 'windows-ce', 'windows-nt', 'windows-nt-4', 'windows-nt-5', 'unknown'. Here's a note from IANA on this topic: The Operating System Names registry has moved to the following: http://www.iana.org/assignments/operating-system-names For all registries, please see the following: http://www.iana.org/numbers.htm Cheers, - Ira McDonald High North Inc -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, June 06, 2002 10:31 AM To: 'a PSI pwg.org' Subject: PS> Updated offramp and reference schemas All, here are the latest updates. The changes include Ira's recent feedback (see below), addition of some annotations, changing all references to ipAddress to host and changing ipAddressType to hostType. Questions: the pathType has an attribute that specifies the OS. Is there a well defined (preferably IANA) list of OS's or file systems that would be appropriate here? Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Fri Jun 7 12:13:16 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: Updated docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD128@xrose03.rose.hp.com> psi060602.pdf == psi-model-view.pdf psi-spec28.pdf == psi-spec-latest.pdf reference060502.xsd offramp060502.xsd cheers, Alan From alan_berkema at hp.com Fri Jun 7 13:30:22 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: next 6/11 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD12C@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 11 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 06/11/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Fri Jun 7 17:17:28 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 6/4/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD131@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler *Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell *Don Wright *Kirk Ocke * = attendance 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions Minutes: 1) Review Reference Schema Spent the entire time working on this schema. Kirk updated the previous version to include all of the Bluetooth attribute except for new_sheet and billing_code since these are covered in other attributes. on[status_code] was also not included since there is no way to specify on* in a schema. Would need to list all onxxx codes individually and this did not seem worthwhile, we can add more if we need them. Some discussion on why we are specifying attributes vs. just saying URL is all you need, add if you need attributes, URLs already allow for syntax to include anything that is needed. Overall the group decided to keep this more explicit reference schema since it provides guidelines for what is actually intended. Also since a URL is allowed it does not preclude the other method. Kirk has updated the schema based on this discussion. Question on the time, does it include the Time Zone? I think that for time to be useful we should mandate a time zone. Thanks, Alan 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. Status: Done. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Status: Done Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave From alan_berkema at hp.com Mon Jun 10 17:44:00 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]:Time Zone next 6/11 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD13B@xrose03.rose.hp.com> From: http://www.w3.org/TR/xmlschema-2/#dateTime dateTime3.2.7 dateTime dt_dateTime[Definition:] dateTime represents a specific instant of time. The ?value space? of dateTime is the space of Combinations of date and time of day values as defined in ? 5.4 of [ISO 8601] . dateTime_lexical_repr3.2.7.1 Lexical representation A single lexical representation, which is a subset of the lexical representations allowed by [ISO 8601] , is allowed for dateTime. This lexical representation is the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e the format ss.ss... with any number of digits after the decimal point is supported. The fractional seconds part is optional; other parts of the lexical form are not optional. To accommodate year values greater than 9999 additional digits can be added to the left of this representation. Leading zeros are required if the year value would otherwise have fewer than four digits; otherwise they are forbidden. The year 0000 is prohibited. The CCYY field must have at least four digits, the MM, DD, SS, hh, mm and ss fields exactly two digits each (not counting fractional seconds); leading zeroes must be used if the field would otherwise have too few digits. This representation may be immediately followed by a "Z" to indicate Coordinated Universal Time (UTC) or, to indicate the time zone, i.e. the difference between the local time and Coordinated Universal Time, immediately followed by a sign, + or -, followed by the difference from UTC represented as hh:mm (note: the minutes part is required). See ISO 8601 Date and Time Formats (?D) for details about legal values in the various fields. If the time zone is included, both hours and minutes must be present. For example, to indicate 1:20 pm on May the 31st, 1999 for Eastern Standard Time which is 5 hours behind Coordinated Universal Time (UTC), one would write: 1999-05-31T13:20:00-05:00. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, June 07, 2002 10:30 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: next 6/11 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 11 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 06/11/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Jun 11 13:06:19 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> IPP Event Notification Subscription and Delivery documents Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A2F@mailsrvnt02.enet.sharplabs.com> Hi folks, Per our brief topic of printer/job event notifications during today's PSI Telecon, below are references for the related IPP documents: Cheers, - Ira McDonald High North Inc --------------------------------------------------------------------------- [list of IPP Printer and Job events] printer-state-changed printer-restarted printer-shutdown printer-stopped printer-config-changed printer-media-changed printer-finishings-changed printer-queue-order-changed job-state-changed job-created job-completed job-stopped job-config-changed job-progress [page level events] --------------------------------------------------------------------------- "Internet Printing Protocol (IPP): IPP Event Notifications and Subscriptions", J. Martin, T. Hastings, R. Herriot, S. Isaacson, R deBry, R. Bergman, Michael Shepherd, 11/28/2001, [defines the IPP Subscription object and the Subscription Attributes group for IPP "job creation" operations] "Internet Printing Protocol (IPP): Job Progress Attributes", T. Hastings, R Bergman, R. Bergman, 07/23/2001, [defines the page-level job events, which should only be delivered via a low-latency protocol] "Internet Printing Protocol (IPP): The 'mailto:' Delivery Method for Event Notifications", T. Hastings, R. Herriot, Carl-Uno Manros, Henrik Holst, 07/23/2001, [defines new Subscription attributes for email and the packaging of IPP email event notifications - in plaintext with optional additional MIME body parts] "Internet Printing Protocol (IPP):The 'indp' Delivery Method for Event Notifications and Protocol/1.0", T. Hastings, Hugo Parra, 07/23/2001, [defines a low-latency event delivery method using 'reverse HTTP' (client acts as mini-HTTP-server and receives incoming connections from Printer or Event Notification Server for delivery of events.] All of the above are available from the IETF server in the directory ftp://ftp.ietf.org/internet-drafts/ and the PWG Server in the directory ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ ONLY on the PWG server, also see 'ippget' (strangely, only this _one_ IPP I-D was just deleted from the I-D directory last week, although it is currently under IESG consideration): "Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications", R. Herriot, T. Hastings, C. Kugler, 11/19/2001, [defines an in-band event delivery method, where client either polls Printer when directed (with server next-poll hints) OR (optional) uses "long" operations with multiple HTTP Responses (for a server to client stream of events)] --------------------------------------------------------------------------- [excerpt from the IPP Notifications spec table of contents] 5 Subscription Object.............................................16 5.1 Rules for Support of Subscription Template Attributes.........17 5.2 Rules for Processing Subscription Template Attributes.........18 5.3 Subscription Template Attributes..............................22 5.3.1 notify-recipient-uri (uri) OR notify-pull-method (type2 keyword)...............................................25 5.3.1.1 notify-recipient-uri (uri)................................25 5.3.1.2 notify-pull-method (type2 keyword)........................25 5.3.2 notify-events (1setOf type2 keyword)........................26 5.3.2.1 Standard Values for Subscribed Events.....................26 5.3.2.1.1 No Events...............................................27 5.3.2.1.2 Subscribed Printer Events...............................27 5.3.2.1.3 Subscribed Job Events...................................29 5.3.2.2 Rules for Matching of Subscribed Events...................30 5.3.2.2.1 Rules for Matching of Printer Events....................30 5.3.2.2.2 Rules for Matching of Job Events........................31 5.3.2.2.3 Special Cases for Matching Rules........................31 5.3.3 notify-attributes (1setOf type2 keyword)....................32 5.3.4 notify-user-data (octetString(63))..........................34 5.3.5 notify-charset (charset)....................................34 5.3.6 notify-natural-language (naturalLanguage)...................35 5.3.7 notify-lease-duration (integer(0:67108863)).................35 5.3.8 notify-time-interval (integer(0:MAX)).......................36 5.4 Subscription Description Attributes...........................38 5.4.1 notify-subscription-id (integer (1:MAX))...................38 5.4.2 notify-sequence-number (integer (0:MAX))....................39 5.4.3 notify-lease-expiration-time (integer(0:MAX))...............39 5.4.4 notify-printer-up-time (integer(1:MAX)).....................40 5.4.5 notify-printer-uri (uri)....................................41 5.4.6 notify-job-id (integer(1:MAX))..............................41 5.4.7 notify-subscriber-user-name (name(MAX)).....................42 6 Printer Description Attributes Related to Notification..........42 6.1 printer-state-change-time (integer(1:MAX))....................43 6.2 printer-state-change-date-time (dateTime).....................43 7 New Values for Existing Printer Description Attributes..........43 7.1 operations-supported (1setOf type2 enum)......................43 8 Attributes Only in Event Notifications..........................44 8.1 notify-subscribed-event (type2 keyword).......................44 8.2 notify-text (text(MAX)).......................................45 9 Event Notification Content......................................45 9.1 Content of Machine Consumable Event Notifications.............48 9.1.1 Event Notification Content Common to All Events.............48 9.1.2 Additional Event Notification Content for Job Events........50 9.1.3 Additional Event Notification Content for Printer Events....51 9.2 Content of Human Consumable Event Notification................51 9.2.1 Event Notification Content Common to All Events.............52 9.2.2 Additional Event Notification Content for Job Events........54 9.2.3 Additional Event Notification Content for Printer Events....55 From alan_berkema at hp.com Tue Jun 11 15:49:49 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: next 6/18 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD142@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 18 (USA) No Call June 25 (F2F June 26) Through June USA) No Call July 2 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 06/18/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Jun 11 16:49:32 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 6/11/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD144@xrose03.rose.hp.com> Apologies for missing Ira last week. PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson *Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone *Lee Farrell Don Wright *Kirk Ocke *Ira Mcdonald * = attendance 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions Minutes: 1) Review Reference Schema passwd and User could apply to any of the "choice" elements Kirk will think about elevating these to be reference attributes instead of at the child element level. Ira mentioned the need for a security "certificate" attribute. Time attribute - discussion started around time zone and lead to -> should this actually be a duration time instead. Actual time should be handeled at higher application layers. Could even be detrimental at the reference layer if devices are out of sync. Talked about adding additional elements for e-mail Kirk to investigate IMAP RFC 2192, SMTP RFC 2368 and POP3 RFC 2384 2) Review psi specs. Decided to adopt the new methods: InvokeJobWithContentByReference InvokeJobWithContentByValue Except that we decided to remove the last_document paramater. This discussion raised the topic of event notification. Will PSI address this? Needs further investigation. IPP is strugelling with too many optional notfication methods need to scale this down if it will be used with PSI. Subscription for events can occuur at the: o Printer Level o Job level o Job page level, this (if included) should not use high latency methods. Also need to consider existing industry methods such as JMS 0) Job Control Interface starting to stabilize Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security Finish all that and PSI is done :) New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thouts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave Thanks, Alan From imcdonald at sharplabs.com Wed Jun 12 14:48:27 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> Thoughts on Discovery for PSI Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A34@mailsrvnt02.enet.sharplabs.com> Hi folks, It seems to me that PSI usage scenarios that require discovery (essentially all of them) separate into two broad classes, just like discovery for IPP: 1) Discovery of available 'public' print services (for example, while staying in a hotel) - public registries of services like UDDI (the future practice, not the current state of deployment) would work well here - but UDDI doesn't give any help solving the 'locality of reference' problem (that is, you don't want to find a 'public' print service in Timbuktoo - you want one _very_ close to your roaming handheld geographically) - SLPv2 (RFC 2608) with Gateway Directory Agents (an extension currently under development at Columbia University) would also work (if widely deployed in the future) 2) Discovery of available 'private' print services (within a single administrative domain - for example, an enterprise LAN) - SLPv2 (RFC 2608) would work well (using the existing 'printer' SLP schema) - LDAPv3 would work well (using the existing 'printer' LDAP schema, which is technically aligned with the SLP 'printer' schema) - DNS SRV (service) records would also work well (but they burden the enterprise DNS and administrators much more than SLPv2 does) - dozens of proprietary discovery services, like Microsoft SSDP, would also probably work (but they're usually impossible to successfully deploy across a heterogenous enterprise LAN). For those interested learning more about remote discovery via SLPv2 see: ftp://ftp.ietf.org/internet-drafts/draft-zhao-slp-remote-da-discovery-03.txt (26 March 2002) Cheers, - Ira McDonald High North Inc From harryl at us.ibm.com Fri Jun 14 16:05:03 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:06 2009 Subject: PS> Alternative JDF derived Job Ticket Message-ID: Peter recently posted a PWG Job Ticket proposal derived from IPP attributes. While I wholeheartedly support establishing and leveraging the PWG Semantic Model (and deriving it largely from IPP)... I want to bring to the attention of PWG members that there is already a robust XML Job Ticket defined by the CIP4 JDF working group. http://www.cip4.org/ JDF has it's roots in Graphic Arts and Workflow and , in it's full definition, the JDF JT is not as simple as what Peter is proposing. The JDF JT incorporates aspects of the Adobe Portable Job Ticket Format and addresses things like order of operations, has longevity and facilitates job tracking and accounting. Nonetheless, the JDF Job Ticket can be reduced and simplified. Because the JDF job ticket is already gaining acceptance in some industry segments and overlaps with our goals to a degree, I suggest we consider either basing our Job Ticket definition on JDF (see link to simple example, below) or, at least, assure a simple mechanical XSLT mapping between the two. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020614/5334d6e1/attachment.html From alan_berkema at hp.com Fri Jun 14 17:31:22 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> Another view of the PWG semantic model Message-ID: <499DC368E25AD411B3F100902740AD650E6AD156@xrose03.rose.hp.com> Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From imcdonald at sharplabs.com Sun Jun 16 16:43:32 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> [PDF version] Another view of the PWG semantic model Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A39@mailsrvnt02.enet.sharplabs.com> Hi folks, I distilled this MS Word file (see below) and converted it to PDF and stored it in the same directory at: ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.pdf (I just tested the above link, to make sure it works correctly) Comments on Alan's alternative proposal will probably be easier to correlate it they reference the line-numbered PDF version above. Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From pmierau at adobe.com Mon Jun 17 12:37:58 2002 From: pmierau at adobe.com (Peter Mierau) Date: Wed May 6 14:02:06 2009 Subject: PS> Alternative JDF derived Job Ticket In-Reply-To: Message-ID: <4.3.2.7.2.20020617093432.01d14a50@mailsj.corp.adobe.com> Harry, I agree with you that JDF job tickets can be quite suitable for enterprise printing such as PSI. And if there happen to be any deficiencies, a "psi" namespace could be used to add functionality to it. I'm sure the CIP4 would also entertain changing the JDF spec to better suit the PSI needs, too. Like you mentioned, though, the JDF spec is quite large and can be daunting to absorb, even though we'd only be interested in a fraction of it for enterprise printing. At 02:05 PM 6/14/2002 -0600, Harry Lewis wrote: >Peter recently posted a PWG Job Ticket proposal derived from IPP >attributes. While I wholeheartedly support establishing and leveraging the >PWG Semantic Model (and deriving it largely from IPP)... I want to bring >to the attention of PWG members that there is already a robust XML Job >Ticket defined by the CIP4 JDF working group. >http://www.cip4.org/ > >JDF has it's roots in Graphic Arts and Workflow and , in it's full >definition, the JDF JT is not as simple as what Peter is proposing. The >JDF JT incorporates aspects of the Adobe Portable Job Ticket Format and >addresses things like order of operations, has longevity and facilitates >job tracking and accounting. Nonetheless, the JDF Job Ticket can be >reduced and simplified. > >Because the JDF job ticket is already gaining acceptance in some industry >segments and overlaps with our goals to a degree, I suggest we consider >either basing our Job Ticket definition on JDF (see link to simple >example, below) or, at least, assure a simple mechanical XSLT mapping >between the two. > >ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml >---------------------------------------------- >Harry Lewis >IBM Printing Systems >---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020617/1f613167/attachment.html From PZehler at crt.xerox.com Mon Jun 17 14:29:01 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:06 2009 Subject: PS> PWG semantic model document version for PWG meeting Message-ID: All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" MS Word version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc" Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From alan_berkema at hp.com Tue Jun 18 18:08:57 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> RE: [PSI]: minutes 6/11/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD167@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema Gail Songer *Dave Hall *Jerry Thasher Harry Lewis Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone *Lee Farrell *Don Wright *Kirk Ocke *Ira Mcdonald * = attendance 06/18/02 Agenda 1) Review Target Device Identifier and Reference schema 2) Review PWG Semantic model with consideration for PSI Minutes: 1) Review Target Device Identifier and Reference schema Postponed to F2F 2) Review PWG Semantic model with consideration for PSI Spent most of the meeting talking about the PWG Semantic model using rev 06-020617. Started with Figure 5. Is this just an example of how Attributes could be used or is this the actual model? PSI is very close to this except that PSI has separated out Job and Content Objects. Talked about 3 levels of the Semantic Model 1) Base Attribute Definitions 2) Structure Definitions 3) Base Operational Model For PSI JobAttributes, ContentAttributes, RenderingAttributes, FinishingAttributes and ImpositionAttributes are all Base Level Attribute groupings. The Base Attributes are defined within each of these. Job and Processing are structures which import the Base Level Attribute groupings. General discussion on grouping indicated a desire for the appropriate level of granularity. One extreme would be no grouping at all, just attribute defs like words in a dictionary, while this has some value since we would all have the same definitions, it does not move the model forward for interoperability and reuse. It looses the semantic meaning. Another extreme is to group them all together. This would be too much for some applications and might still not be enough for others. Need a compromise that could allow profiles to structure the Base level groupings in a way that suits the application. Also decided that Fidelity should be part of Job as well as Content. See ya next week, Alan ---- 0) Job Control Interface starting to stabilize Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security Finish all that and PSI is done :) New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thouts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave Thanks, Alan From alan_berkema at hp.com Thu Jun 20 15:46:04 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> PSI Minutes from -- Apr '02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD171@xrose03.rose.hp.com> Lee sent this a while back while I was in Barcelona, just remembered to pass them along. Will also post. Thanks Lee! Will need a volunteer for next week. Alan -----Original Message----- From: Farrell, Lee [mailto:Lee.Farrell@cda.canon.com] Sent: Wednesday, May 01, 2002 7:47 PM To: PSI (E-mail) Subject: PS> PSI Meeting Notes -- Apr '02 <> =========================== Lee Farrell Canon Development Americas 110 Innovation Drive Irvine, CA 92612 (949) 856-7163 - voice (949) 856-7510 - fax lee.farrell@cda.canon.com =========================== -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI Meeting Notes 020416.pdf Type: application/octet-stream Size: 20065 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020620/5cc01cf3/PSIMeetingNotes020416.obj From hastings at cp10.es.xerox.com Thu Jun 20 19:37:02 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:06 2009 Subject: PS> Comments on the PWG Semantic Model document version 0.06, dated J une 17, 2002 Message-ID: <918C79AB552BD211A2BD00805F15CE8506DF43A4@x-crt-es-ms1.cp10.es.xerox.com> Here are my comments on the document. Unfortunately, I won't be able to be at either the PSI or the PWG meeting to discuss. Have a good meeting. 1. The WG should consider whether the 10-page summary of the attributes in section 2.3 (pages 14 through 23) should be moved back to the appendix where the summary of the actions is. Then section 2 will be reduced from 18 pages to 9 pages (pages 6-14) on the Data Class attributes. The figures in section 2 give the names of the attributes and how they are grouped which gives the reader a good overview of the attribute and object part of the model. With such a move, section 3 Actions and 4 status codes combined will be roughly the same size at 6 pages (pages 24-29) as section 2 (9 pages). This was Melinda Grant's suggestion which was put into version 0.2, 5/23/02. 2. The use of the term "Content" instead of "Document" in attribute and object names seems a step backwards and will lead to confusion with the existing standards that have already incorporated IPP semantics into them, such as IPP, UPnPv1, Bluetooth, and the OMG Print Facility, and the implementations of these standards. Also ISO DPA used the term Document. The PWG will look silly progressing a Semantic Model that covers a lot of existing and future practice, if we change the commonly used terminology. If the reason for the change is to allow other types of electronic representation to be submitted in a print job, such as fonts, forms, logos, etc., we can add a "DocumentType" attribute which indicates the type as: 'printable', 'font', 'form', 'logo', etc. This is what ISO DPA did. 3. Page 9, section 2.2, Page 12, section 2.2.2 Figure 8, and page 15, section 2.3.2 Job Attribute: The Job attributes that a client supplies the values for should not be grouped with the Job attributes that the Printer alone sets. The latter could be called Job Description attributes, as in IPP and the former called just Job Attributes. More comments later. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, June 17, 2002 11:29 To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; ps@pwg.org; pwg@pwg.org Subject: PS> PWG semantic model document version for PWG meeting All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" MS Word version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc" Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From KOcke at crt.xerox.com Fri Jun 21 10:12:51 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> NEW reference.xsd and targetDevice.xsd Message-ID: Alan, et. al., here are the promised updated to the schemas. I have not put detailed annotations into the schemas yet, but the new elements have names that are taken directly from the standards they refer to (e.g., uid element in imap element in reference.xsd taken directly from uid definition in IMAP RFC). I'll add annotations post the face to face meeting. Kirk From KOcke at crt.xerox.com Fri Jun 21 10:28:45 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:06 2009 Subject: PS> NEW reference.xsd and targetDevice.xsd Message-ID: With attachments this time ;-) -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Friday, June 21, 2002 10:13 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: PS> NEW reference.xsd and targetDevice.xsd Alan, et. al., here are the promised updated to the schemas. I have not put detailed annotations into the schemas yet, but the new elements have names that are taken directly from the standards they refer to (e.g., uid element in imap element in reference.xsd taken directly from uid definition in IMAP RFC). I'll add annotations post the face to face meeting. Kirk -------------- next part -------------- A non-text attachment was scrubbed... Name: targetDevice.xsd Type: application/octet-stream Size: 6165 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020621/cea6a91f/targetDevice.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 6598 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020621/cea6a91f/reference.obj From alan_berkema at hp.com Fri Jun 21 17:21:15 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> PSI Agenda 6/26/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD179@xrose03.rose.hp.com> All: Here is a proposed agenda for the PSI F2F on Wednesday I. Introductions II. Review and Approve minutes from April (ftp://ftp.pwg.org/pub/pwg/ps/PSIMeetingNotes020416.pdf) III. Review Agenda III. Review Action Items IV. New PSI Overview Diagram (slide and in rev29 spec.) V. Review PSI Selected Logical View (ftp://ftp.pwg.org/pub/pwg/ps/psi062102.pdf) VI. Review PSI Spec (ftp://ftp.pwg.org/pub/pwg/ps/psi-spec29.pdf) VII. Review reference schema (ftp://ftp.pwg.org/pub/pwg/ps/reference062102.xsd) VIII. Review targetDevice schema (ftp://ftp.pwg.org/pub/pwg/ps/targetDevice062102.xsd) IX. Discuss Attributes X. Discuss New Work Items X1. Plan Forward & teleconference schedule with respect to Holidays & Vacations (Thanks for the format Don :) Alan From hastings at cp10.es.xerox.com Tue Jun 25 11:45:47 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:06 2009 Subject: PS> Rest of my comments on the Message-ID: <918C79AB552BD211A2BD00805F15CE8506DF444D@x-crt-es-ms1.cp10.es.xerox.com> Here are the rest of my comments on the PWG Semantic Model in version 0.06, dated June 17, 2002, "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" 2. (continued) Here are some more arguments in support of using the term "Document", instead of "Content": In the late 1960, there was a fad in system design to invent entirely new terms so that no one could possibly be mis-led into thinking that a term carried along some assumptions from some other usage. However, the result was that no one really understood anyone else, since learning an entirely new vocabulary was much too hard. Bernie Galler from the University of Michigan wrote a letter to the Communications of the ACM, strongly urging system designers to abandon this fad of inventing new terms. Instead, he said use the terms that have a common understanding. Put an adjective in front if you really want to distinguish your term from the common usage. Live with the term including the adjective for a while and see if you still really need the adjective. If you don't, drop the adjective. Either way, be sure to put the term into a terminology section and describe the specifics of the use of the term in your specification. So if the reason for changing the word from "Document" (which all print standards have used) to "Content" is to avoid some kind of unwarranted assumptions or confusions about "Document", just define what is meant by "Document" in the PWG Semantic Model. A Document can be any electronic form of representation that is represented by a MIME Media type, including a text document, an XML representation, an image, etc. If you want to distinguish between the electronic form that is submitted in a print job from the hardcopy form that the Printer produces, you could add adjectives in front of Document. For example, Input Document and Output Document, respectively, as has been done for the Document and Page Overrides specification for IPP. [Comments 1, initial 2, and 3 are below in the earlier email message.] 4. Page 5, section 1, Model Overview, the third sentence, says: "The PWG model describes the device as a Printer object." We also need to clarify, as in RFC 2911, that the communication can be between a desktop and a spooler, a desktop and a printing device, or between a spooler and a printing device. One fix would be to replace the third sentence with something like: The PWG Model represents the entity that accepts print requests as a Printer object. The Printer object can represent a printing device, a spooler, or both. Such a spooler may control one or more devices and spools jobs before forwarding them to one of the printing device. 5. Page 5, bottom of the page. Add the terms "Printer", "Client", "Document" to the list of terms. I suggest capitalizing the first letter when the special term is intended. 6. Page 8, section 2.1.3 "Job Processing" Printer Attributes: I agree that the term "Job Processing" attributes is probably a better term than the IPP Semantic Model "Job Template" attributes term, so this is an OK terminology change (but needs to be added to the IPP mapping appendix). 7. Page 8, Table 1, JobPriority, the "xxxSupported syntax: Change "Integer (MAX value)" to "Integer (number of priority levels)". 8. Page 14, Table 2, Sides: Delete the two last values: 'two-sided-long-edge' [duplicate] and 'tumble' [not defined]. 9. Page 15, Table 2, Media: The reference should be to [RFC2911] "media" appendix, not pwg5101.1. The example should be something like: 'na-letter-white that is defined in RFC 2911. The next two attributes (MediaSize and MediaType) correctly refer to pwg5101.1. 10. Page 25-26, section 3.2.1 PrintJob and PrintUri, could be eliminated and then add a note that some protocols may combine CreateJob and SendDocument into a single operation, called PrintJob and combine CreateJob and SendUri into a single operation, called PrintUri. This will reduce the number of actions in the document (while still covering both IPP and PSI which do have the combined action). 11. Page 31, Appendix - IPP Mapping Change the title of this appendix, so that it is just specifying more detail for the actions as part of the Model. This appendix could eliminate 7.2.1 PrintJob and 7.2.2 PrintUri. Move the details of 7.2.1 PrintJob into 7.2.3 CreateJob. 12. Add a separate (much shorter) appendix that indicates the IPP Mapping to the Model. Either in this Appendix also indicate the PSI Mapping to the PWG Model, or in a separate Appendix. The advantage of having in the same appendix, is that it will be easier to compare the IPP Semantic Model and the PSI semantics. For example, a single table might contain three columns: PWG Model, IPP Semantics, and PSI Semantics. Tom -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Thursday, June 20, 2002 16:37 To: Zehler, Peter; 'BERKEMA,ALAN C (HP-Roseville,ex1)' Cc: ps@pwg.org; pwg@pwg.org Subject: PWG> Comments on the PWG Semantic Model document version 0.06, dated J une 17, 2002 Here are my comments on the document. Unfortunately, I won't be able to be at either the PSI or the PWG meeting to discuss. Have a good meeting. 1. The WG should consider whether the 10-page summary of the attributes in section 2.3 (pages 14 through 23) should be moved back to the appendix where the summary of the actions is. Then section 2 will be reduced from 18 pages to 9 pages (pages 6-14) on the Data Class attributes. The figures in section 2 give the names of the attributes and how they are grouped which gives the reader a good overview of the attribute and object part of the model. With such a move, section 3 Actions and 4 status codes combined will be roughly the same size at 6 pages (pages 24-29) as section 2 (9 pages). This was Melinda Grant's suggestion which was put into version 0.2, 5/23/02. 2. The use of the term "Content" instead of "Document" in attribute and object names seems a step backwards and will lead to confusion with the existing standards that have already incorporated IPP semantics into them, such as IPP, UPnPv1, Bluetooth, and the OMG Print Facility, and the implementations of these standards. Also ISO DPA used the term Document. The PWG will look silly progressing a Semantic Model that covers a lot of existing and future practice, if we change the commonly used terminology. If the reason for the change is to allow other types of electronic representation to be submitted in a print job, such as fonts, forms, logos, etc., we can add a "DocumentType" attribute which indicates the type as: 'printable', 'font', 'form', 'logo', etc. This is what ISO DPA did. 3. Page 9, section 2.2, Page 12, section 2.2.2 Figure 8, and page 15, section 2.3.2 Job Attribute: The Job attributes that a client supplies the values for should not be grouped with the Job attributes that the Printer alone sets. The latter could be called Job Description attributes, as in IPP and the former called just Job Attributes. More comments later. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, June 17, 2002 11:29 To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; ps@pwg.org; pwg@pwg.org Subject: PS> PWG semantic model document version for PWG meeting All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" MS Word version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc" Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From hastings at cp10.es.xerox.com Tue Jun 25 11:45:44 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:06 2009 Subject: PS> RE: PWG> Agenda for Thursday Plenary - Portland [there's a later PWG Semantic Model] Message-ID: <918C79AB552BD211A2BD00805F15CE8506DF444C@x-crt-es-ms1.cp10.es.xerox.com> Harry, Peter posted a later PWG Semantic Model on 6/17, building on Alan Berkima's version (which built on Peter's previous version). So the agenda should show: ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc (Peter made a typo in the file name: "Mode" instead of "Model", but that is how it is stored.) Thanks, Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, June 17, 2002 11:29 To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; ps@pwg.org; pwg@pwg.org Subject: PS> PWG semantic model document version for PWG meeting All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf MS Word version is available at ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan * -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Friday, June 21, 2002 15:26 To: pwg@pwg.org Subject: PWG> Agenda for Thursday Plenary - Portland MORNING 1. Standard Plenary reports 1.1 IPP Update - Harry Lewis 1.2 Printer MIB Update - Harry Lewis 1.3 XHTML-Print Status - Don Wright 1.4 PSI Status - Alan Berkema 1.5 UPDF Status - Norbert Schade 1.6 IPP-FAX Status - Gail Songer 1.7 Misc and Related - As needed 2. Linux and Free Software Group Update 2.1 CUPS, PAPI ftp://ftp.pwg.org/pub/pwg/Related/Linux/papi.pdf 2.1.1 IPP Job Ticket and Capabilities Object Extension ftp://ftp.pwg.org/pub/pwg/ipp/new_JTCO/JTCO_RoughDraft.pdf 2.2 Job Ticket API ftp://ftp.pwg.org/pub/pwg/Related/FSGOpen/ 2.2.1 PWG Job Ticket ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrintJobTicket.xml 2.2.2 JDF Job Ticket ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml 2.2.3 Job Ticket Type supported attribute 3. PWG Semantic Model (Overview and Charter) 3.1 Role Of PWG 3.2 Other groups, other models 3.3 Role of Job Ticket, Capabilities Object ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-Charter-Proposal .pdf ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-Overview.pdf AFTERNOON 4. Adobe Presentation 4.1 TIFF-FX vs. PDF as a common PDL 4.2 Applicability to IETF IFAX, IPP-FAX, other 4.3 Licensing 5. PWG Semantic Model (Review) ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.pdf 5.1 Correlation 5.1.1 IPP, IPP-FAX, UPDF, PSI, XHTML-Print ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020625/83b68ded/attachment.html From imcdonald at sharplabs.com Tue Jul 2 13:43:42 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> RFC 3288 - SOAP over BEEP (Proposed Standard) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CCE9@mailsrvnt02.enet.sharplabs.com> Hi folks, This RFC was written by W3C folks to specify a (simple, but complete) mapping of W3C Simple Object Access Protocol (SOAP) over the recent IETF Blocks Extensible Exchange Protocol (BEEP), RFC 3080 (March 2001). Note that SOAP over BEEP would be dramatically faster than SOAP over HTTP/1.1, due to BEEPs efficient channel management (versus HTTP). Worth looking at. Cheers, - Ira McDonald High North Inc From alan_berkema at hp.com Mon Jul 8 09:45:19 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> NO PSI Call 7/9/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD181@xrose03.rose.hp.com> Dave and I are both out. regards, Alan From norbertschade at attbi.com Mon Jul 8 10:32:20 2002 From: norbertschade at attbi.com (Norbert Schade) Date: Wed May 6 14:02:06 2009 Subject: PS> Semantic model: media handling Message-ID: <001a01c2268c$4544aa00$a8948018@ne1.client2.attbi.com> I have problems to follow two different ways to specify media handling and UPDF would have problems to support that. I'm fine with the specification of single media attributes like size, type, etc. I agree that there should exist a media instance a level higher, which is a media element with a number of media attributes. The number of attributes can vary. In one sample it may be just size and type, in another it may be something like the IPP media collection. My point is that the attributes a media is described by may vary. There should not be a predefined media collection in a common Semantic Model representing one implementation. Feel free to check the composite feature definition we have in UPDF. Open the UPDF.xsd schema to do this and follow the path down to PrintCapabilities.Features. The current sample description xml of an imaginary LJ9000 has a 'Media' composite feature. We can compose any number of features to a new feature, be it Media, Quality or anything else. This is a very flexible structure and is expected to be used frequently. We got very positive feedback once we finished it last year. We'd appreciate if the Semantic Model does something down that path. Otherwise the spec is ambiguous. Another statement: We've seen the current schema of the Semantic Model. We know there are a number of ways to write schemas. The UPDF group made the experience that working with attributes instead of assigning text to elements directly has advantages. Validation is easier and we can define constraints (these are really constraints and not dependencies) for attributes. You may think that over. Regards Norbert Schade 69 Prescott Drive North Chelmsford, MA 01863 978-251-1017 norbertschade@attbi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020708/ea976b89/attachment.html From alan_berkema at hp.com Sun Jul 14 11:43:40 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: next 7/23 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD184@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 23 (USA) No Call July 16 Through August 6 No Call July 2 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/23/02 Agenda TBD ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From hastings at cp10.es.xerox.com Mon Jul 15 19:12:38 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: next 7/23 8:00:am Pacific Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F90806F914@x-crt-es-ms1.cp10.es.xerox.com> Alan, Is there a call August 6 or not? Thanks, Tom -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Sunday, July 14, 2002 08:44 To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 7/23 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 23 (USA) No Call July 16 Through August 6 No Call July 2 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/23/02 Agenda TBD ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From robert_b_taylor at hp.com Tue Jul 16 23:13:37 2002 From: robert_b_taylor at hp.com (TAYLOR,BOB (HP-Vancouver,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> Semantic model: media handling Message-ID: <6D805D4C4567D411AF32009027B683510B40FFA6@xvan02.vcd.hp.com> Hi Norbert, all, One of the things we (HP) have been suggesting for the semantic model is the separation of the raw "attribute/element" definitions from the structures/model that pull them together for a particular use. As you not, UPDF has done this structuring in a different way than IPP - which is also somewhat different than UPnP & PSI, etc. I'm not sure we want to try codify any one structure as part of the core semantic model - these will tend to vary by market segment and domain, and I'm not sure we can do this one-size-fits-all. What we would like to see, though, is common definition of the core "attributes/elements" - this seems much more reusable across models & domains. It does make sense, though, to publish some of the "common models" as at least examples of structural models - IPP, UPDF, etc. are likely candidates for this. This exposes some of useful constructs (such as the composite feature you describe below) for reuse. thanks, bt --------------------------------------------------- Bob Taylor Senior Architect IPG Strategic Technology Development Hewlett-Packard Co. mailto:robertt@vcd.hp.com phone: 360.212.2625/T212.2625 fax: 208.730-5111 --------------------------------------------------- -----Original Message----- From: Norbert Schade [mailto:norbertschade@attbi.com] Sent: Monday, July 08, 2002 7:32 AM To: Print Services group Cc: UPD group Subject: PS> Semantic model: media handling I have problems to follow two different ways to specify media handling and UPDF would have problems to support that. I'm fine with the specification of single media attributes like size, type, etc. I agree that there should exist a media instance a level higher, which is a media element with a number of media attributes. The number of attributes can vary. In one sample it may be just size and type, in another it may be something like the IPP media collection. My point is that the attributes a media is described by may vary. There should not be a predefined media collection in a common Semantic Model representing one implementation. Feel free to check the composite feature definition we have in UPDF. Open the UPDF.xsd schema to do this and follow the path down to PrintCapabilities.Features. The current sample description xml of an imaginary LJ9000 has a 'Media' composite feature. We can compose any number of features to a new feature, be it Media, Quality or anything else. This is a very flexible structure and is expected to be used frequently. We got very positive feedback once we finished it last year. We'd appreciate if the Semantic Model does something down that path. Otherwise the spec is ambiguous. Another statement: We've seen the current schema of the Semantic Model. We know there are a number of ways to write schemas. The UPDF group made the experience that working with attributes instead of assigning text to elements directly has advantages. Validation is easier and we can define constraints (these are really constraints and not dependencies) for attributes. You may think that over. Regards Norbert Schade 69 Prescott Drive North Chelmsford, MA 01863 978-251-1017 norbertschade@attbi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020716/0568c4ca/attachment.html From harryl at us.ibm.com Wed Jul 17 11:34:40 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:06 2009 Subject: PS> Semantic model: media handling Message-ID: I like Bob's analysis. I think the Semantic Model will be most useful taking this approach. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "TAYLOR,BOB (HP-Vancouver,ex1)" Sent by: owner-ps@pwg.org 07/16/2002 09:13 PM To: Norbert Schade , Print Services group cc: UPD group Subject: RE: PS> Semantic model: media handling Hi Norbert, all, One of the things we (HP) have been suggesting for the semantic model is the separation of the raw "attribute/element" definitions from the structures/model that pull them together for a particular use. As you not, UPDF has done this structuring in a different way than IPP - which is also somewhat different than UPnP & PSI, etc. I'm not sure we want to try codify any one structure as part of the core semantic model - these will tend to vary by market segment and domain, and I'm not sure we can do this one-size-fits-all. What we would like to see, though, is common definition of the core "attributes/elements" - this seems much more reusable across models & domains. It does make sense, though, to publish some of the "common models" as at least examples of structural models - IPP, UPDF, etc. are likely candidates for this. This exposes some of useful constructs (such as the composite feature you describe below) for reuse. thanks, bt --------------------------------------------------- Bob Taylor Senior Architect IPG Strategic Technology Development Hewlett-Packard Co. mailto:robertt@vcd.hp.com phone: 360.212.2625/T212.2625 fax: 208.730-5111 --------------------------------------------------- -----Original Message----- From: Norbert Schade [mailto:norbertschade@attbi.com] Sent: Monday, July 08, 2002 7:32 AM To: Print Services group Cc: UPD group Subject: PS> Semantic model: media handling I have problems to follow two different ways to specify media handling and UPDF would have problems to support that. I'm fine with the specification of single media attributes like size, type, etc. I agree that there should exist a media instance a level higher, which is a media element with a number of media attributes. The number of attributes can vary. In one sample it may be just size and type, in another it may be something like the IPP media collection. My point is that the attributes a media is described by may vary. There should not be a predefined media collection in a common Semantic Model representing one implementation. Feel free to check the composite feature definition we have in UPDF. Open the UPDF.xsd schema to do this and follow the path down to PrintCapabilities.Features. The current sample description xml of an imaginary LJ9000 has a 'Media' composite feature. We can compose any number of features to a new feature, be it Media, Quality or anything else. This is a very flexible structure and is expected to be used frequently. We got very positive feedback once we finished it last year. We'd appreciate if the Semantic Model does something down that path. Otherwise the spec is ambiguous. Another statement: We've seen the current schema of the Semantic Model. We know there are a number of ways to write schemas. The UPDF group made the experience that working with attributes instead of assigning text to elements directly has advantages. Validation is easier and we can define constraints (these are really constraints and not dependencies) for attributes. You may think that over. Regards Norbert Schade 69 Prescott Drive North Chelmsford, MA 01863 978-251-1017 norbertschade@attbi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020717/1623e816/attachment.html From alan_berkema at hp.com Mon Jul 22 12:36:42 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: NEW WEBEX Info & Docs - next 7/23 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD188@xrose03.rose.hp.com> New WEBEX meeting number and passwd below. Also new docs posted psi071802.pdf == psi-model-view.pdf psi-spec30.pdf == psi-spec-latest.pdf psi071802.mdl PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday July 23 (USA) No Call July 16 Through August 6 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/23/02 Agenda 1) Review psi-spec30.pdf ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 28877789 Meeting Password: newpsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Jul 23 12:41:56 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: next 7/30 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD18F@xrose03.rose.hp.com> * Webex and phone number same as last week. * PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday July 30 (USA) No Call July 16 Through August 6 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/30/02 Agenda 1) Review psi-spec31.pdf and continue discussions from 7/23 ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 28877789 Meeting Password: newpsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Jul 23 18:58:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> Basic notification events and included attributes Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD07@mailsrvnt02.enet.sharplabs.com> Hi folks, Tuesday (23 July 2002) Per my action item from today's PSI Telecon, here's some information on the basic event notification model from IPP. For more info please see: ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-not-spec-09.txt Cheers, - Ira McDonald High North Inc ---------------------------------------- Printer Event Conformance printer-state-changed REQUIRED printer-restarted OPTIONAL printer-shutdown OPTIONAL printer-stopped REQUIRED printer-config-changed OPTIONAL printer-media-changed OPTIONAL printer-finishings-changed OPTIONAL printer-order-queue-changed OPTIONAL ---------------------------------------- Job Event Conformance job-state-changed REQUIRED job-created REQUIRED job-completed REQUIRED job-stopped OPTIONAL job-config-changed OPTIONAL job-progress OPTIONAL ---------------------------------------- Table 5 - Attributes in Event Notification Content Source Value Sends Source Object notify-subscription-id (integer(1:MAX)) MUST Subscription notify-printer-uri (uri) MUST Subscription notify-subscribed-event (type2 keyword) MUST Event Notification printer-up-time (integer(MIN:MAX)) MUST Printer printer-current-time (dateTime) * MUST Printer notify-sequence-number (integer (0:MAX)) SHOULD Subscription notify-charset (charset) SHOULD Subscription notify-natural-language (naturalLanguage) SHOULD Subscription notify-user-data (octetString(63)) ** SHOULD Subscription notify-text (text) SHOULD Event Notification attributes from the "notify-attributes" MAY Printer attribute *** attributes from the "notify-attributes" MAY Job attribute *** attributes from the "notify-attributes" MAY Subscription attribute *** *A Printer MUST send this value only if and only if it supports the Printer's "printer-current-time" attribute. ** If the Subscription Object does not contain a "notify-user-data" attribute and the Delivery Method Document REQUIRES the Printer to send the "notify-user-data" source value in the Event Notification, the Printer MUST send an octet-string of length 0. *** The last three rows represent additional attributes that a client MAY request via the "notify-attributes" attribute. A Printer MAY support the "notify-attributes" attribute. The Delivery Method MUST say that the Printer MUST, SHOULD, MAY, MUST NOT, SHOULD NOT, or NEED NOT support the "notify-attributes" attribute and specific values of this attribute. The Delivery Method MAY say that support for the "notify-attributes" is conditioned on support of the attribute by the Printer or it MAY say that Printer MUST support the "notify- attributes" attribute if the Printer supports the Delivery Method. ---------------------------------------- Table 6 - Additional Event Notification Content for Job Events Source Value Sends Source Object job-id (integer(1:MAX)) MUST Job job-state (type1 enum) MUST Job job-state-reasons (1setOf type2 keyword) MUST Job job-impressions-completed (integer(0:MAX)) * MUST Job * The Printer MUST send the "job-impressions-completed" attribute in an Event Notification only for the combinations of Events and Subscribed Events shown in Table 7. ---------------------------------------- Table 7 - Combinations of Events and Subscribed Events for "job-impressions-completed" Job Event Subscribed Job Event 'job-progress' 'job-progress' 'job-completed' 'job-completed' 'job-completed' 'job-state-changed' ---------------------------------------- Table 8 - Additional Event Notification Content for Printer Events Source Value Sends Source Object printer-state (type1 enum) MUST Printer printer-state-reasons (1setOf type2 keyword) MUST Printer printer-is-accepting-jobs (boolean) MUST Printer ---------------------------------------- From alan_berkema at hp.com Thu Jul 25 13:12:20 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 7/23/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1A0@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright *Kirk Ocke *Ira Mcdonald *Amir Shahindoust * = attendance 07/23/02 Agenda 1) Review psi-spec30.pdf Minutes: 1) Review psi-spec30.pdf Ira asked about minutes from the Portland F2F. Unfortunately we do not have a secratary yet and while Jim Sommer volunteered he was only able to attend half of the meeting. He did give his notes for the first half. I while try to provide an overview of the meeting, however, most of the real details of the discussion were captured in psi-spec30.pdf. We still need a secratary for Santa Fe! Started out with a review of psi-spec30.pdf, focusing on unfinished work from the F2F. Since we are aligning with the PWG semantic model Pete said that he would have a new rev of the document and new schemas for us to review in Santa Fe. Next we looked at GetServiceAttributes and exactly what this should return? This folded into GetSelfDescribingServiceAttributes which we decided was better named GetServiceAttributeMetaData. Discussion on whether the return should be an instance document or a schema and do we need both methods? Can we align the two so we do have two different methods with different levels of return values. Decieded that if we return a Schema we can have only one method and for PSI 1.0 it would return a Schema with base level attributes. The Schema could be extended with Meta Data (self decribing type of features) in the future (beyond PSI 1.0). What is UPDFs role in this? How will UPDF harmonize with the semantic model? Talked about the PSI dependency on the semantic model vs. the PSI schedule. Decided that the amount of work involved with the semantic model and it's similar schedule will not add an unreasonable risk to PSI. Determined that formal notification/eventing methods will not be included in the PSI 1.0 spec. Could be considered in a following revision. Security came up again. The goal of PSI is to facilitate existing security methods by including credentials needed by existing methods in appropriate PSI schemas. We do need to consider privilege roles: o End User o Operator o Administrator For example we would not want to allow End Users to cancel other users jobs. When we reviewed the Target Interface we observed that PostStatus, PostJobStatus, PostDocumentStatus are really a lot like a Notifications. We could call these simple notifications and include a Boolean in CreateJob that indicates whether or not the notifications were desired. Formal Notifications, that we decided were post PSI 1.0, would include Notification subscriptions and Cancel subscription methods that add complexity. However if we model our post status as simple notifications then they would naturally fit with the Formal notifications in the future. Simple notifications would only be associated with the life of a CreateJob . Ira took an action to provide information about what IPP uses for notification payload, things like JobState, JobStateReasons and various counters. Simple notifications will limit the payload values. Alan ---- 0) Job Control Interface starting to stabilize Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security Finish all that and PSI is done :) New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thougts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave Thanks, Alan From alan_berkema at hp.com Fri Jul 26 18:53:47 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> June Meeting Minutes Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1AB@xrose03.rose.hp.com> The unapproved minutes from the June Meeting are attached and now available at: ftp://ftp.pwg.org/ps/MinutesJune2602.pdf Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: MinutesJune2602.pdf Type: application/octet-stream Size: 59535 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020726/0dc1d1fb/MinutesJune2602.obj From alan_berkema at hp.com Tue Jul 30 12:17:29 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: minutes 7/30/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1C1@xrose03.rose.hp.com> Please see attached -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI minutes 73002.pdf Type: application/octet-stream Size: 39708 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020730/1e549b0c/PSIminutes73002.obj From alan_berkema at hp.com Wed Jul 31 17:11:04 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]: next call 08/06/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1D4@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday August 6 (USA) Through August 6 (USA) (No Call August 13) New Number after this Time: 8 AM (US PST) Number: 650-690-9360(T348-9360) ID: 55605 Agenda: 1) Review work in progress 2) Review new Schemas (Kirk?) WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 8/6/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From imcdonald at sharplabs.com Tue Aug 6 15:35:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> SMB Reference Info - SMB URL I-D Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD30@mailsrvnt02.enet.sharplabs.com> Hi folks, Per today's PSI telecon question (from Kirk Ocke) about the content of an SMB reference, see "SMB Filesharing URL Scheme": ftp://ftp.ietf.org/internet-drafts/draft-crhertel-smb-url-03.txt Abstract The Server Message Block (SMB) protocol is one of the most widely used network filesystem protocols in existence. This document describes a format for an SMB Uniform Resource Locator. The SMB URL can be used to indicate SMB workgroups, servers, shares, files, inter-process communications pipes, print queues, and devices; the objects in the SMB network filesystem space. This is an excellent spec, with good references. That said, the complexities of an SMB reference (and how to resolve one for NetBIOS names to and from DNS names and IP addresses) are sufficient that I propose we (PSI) punt and just use URL forms for SMB references. Cheers, - Ira McDonald High North Inc ------------------------------------------------------------------- [some excerpts] Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. URL Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1 NBT Transport. . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1.1 nbt_name . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.2 ntdomain . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.3 nbt_context. . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Relative SMB URLs. . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Fragments. . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.4. Use of the 'port' Field. . . . . . . . . . . . . . . . . . . . 7 3. Relationship Between the URL and the UNC Formats. . . . . . . . . . 7 4. Authentication and Security Considerations. . . . . . . . . . . . . 7 5. SMB URL Semantics . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Character Encoding Issues . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 9. Author's Address. . . . . . . . . . . . . . . . . . . . . . . . . .10 Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 1. Introduction The Server Message Block protocol (SMB) was created in the 1980's by Dr. Barry Feigenbaum at IBM Corporation. It was later extended by IBM, 3Com, Intel, and Microsoft. SMB is now also known by the name CIFS, which stands for Common Internet FileSystem. SMB was originally carried via a proprietary network transport, the interface to which was called NetBIOS (Network Basic Input Output System). Two Internet RFCs ([RFC1001], [RFC1002]) were published which describe a mechanism for implementing the NetBIOS API on top of TCP and UDP. Those RFCs are now known collectively as Internet Standard #19 (STD 19), and the protocol they describe is known as NBT (for NetBIOS over TCP). SMB is intended to be transport independent. In addition to transport via NBT, SMB may be carried directly on TCP/IP without the intervening NetBIOS emulation layer. Several attempts have been made to document and even standardize the SMB protocol ([XOPENSMB], [ONET], [SNIACIFS]), yet the further development of SMB remains under the control of Microsoft. Despite its proprietary nature, the workings of SMB are sufficiently well known that SMB filesharing has been successfully implemented by several third-party commercial vendors, and in Open Source. SMB server and client software is available for a wide variety of operating system platforms. The very large number of systems which support this form of filesharing make an SMB URL scheme both practical and desirable. 1.1. Purpose This document does not attempt to describe the implementation of the SMB protocol itself. The goal is to present the syntax of the SMB URL, and explain how it maps to the features of SMB. 2. URL Definition An SMB URL may begin with one of two protocol prefixes: "smb" or "cifs". Both are considered to be equivalent. The following grammar defines the syntax of the SMB URL. It is based upon the grammar given in Appendix A of [RFC2396], as amended by [RFC2732]. Refer to those RFCs for any token definitions missing from the grammar below. smb_URL = ( SMB_absURL | SMB_relURL ) [ "#" fragment ] smb_absURL = scheme "://" [ smb_net_path ] [ "?" [ nbt_context ] ] smb_relURL = abs_path | rel_path scheme = "smb" | "cifs" smb_net_path = smb_server [ abs_path ] smb_server = [ smb_userinfo "@" ] smb_srv_name [ ":" port ] smb_srv_name = nbt_name | host nbt_name = netbiosname [ "." scope_id ] netbiosname = 1*( netbiosnamec ) *( netbiosnamec | "*" ) netbiosnamec = ( alphanum | escaped | ":" | "=" | "+" | "$" | "," | "-" | "_" | "!" | "~" | "'" | "(" | ")" ) scope_id = domainlabel *( "." domainlabel ) smb_userinfo = [ ntdomain ";" ] username [ ":" password ] ntdomain = *( unreserved | escaped | "&" | "=" | "+" | "$" | "," ) username = *( unreserved | escaped | "&" | "=" | "+" | "$" | "," ) password = *( unreserved | escaped | "&" | "=" | "+" | "$" | "," ) nbt_context = nbt_param *(";" nbt_param ) nbt_param = ( ( "NBNS=" | "WINS=" ) host ) | ( "CALLED=" netbiosname ) | ( "CALLING=" netbiosname ) | ( ( "WORKGROUP=" | "NTDOMAIN=" ) nbt_name ) From imcdonald at sharplabs.com Tue Aug 6 15:52:05 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> FW: IPP (Job/Doc) Object Attributes work-in-progress Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD32@mailsrvnt02.enet.sharplabs.com> Hi folks, Per Alan's question about progress on the PWG Semantic Model at today's PSI Telecon: Tom Hastings (Xerox) has added a real Document object to the IPP Model (for addition to the PWG Semantic Model by Pete Zehler) - see the URL below for the PDF version. Tom and Pete and I spent quite a while on the phone over this the last two weeks, so it's a pretty good effort (we hope). Cheers, - Ira McDonald, High North Inc -----Original Message----- From: McDonald, Ira Sent: Sunday, August 04, 2002 2:30 PM To: 'Hastings, Tom N'; printing-spool@freestandards.org; printing-cap@freestandards.org; 'ipp@pwg.org' Cc: Zehler, Peter; McDonald, Ira Subject: RE: RESEND: PAPI Chapter 9 ISSUE: Reference to a document which lists all attributes Hi folks, I posted Tom's Acrobat (PDF) file to the requested URL: ftp://ftp.pwg.org/pub/pwg/fsg/spool/IPP-Object-Attributes.pdf After six tries, I still can't FTP transfer the (large) MS Word source file to the PWG server without the PWG server dropping the connection before it completes. No matter - the PDF file should be used for comments anyway. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Saturday, August 03, 2002 8:33 PM To: printing-spool@freestandards.org; printing-cap@freestandards.org Cc: Zehler, Peter; McDonald, Ira at Sharp Subject: RESEND: PAPI Chapter 9 ISSUE: Reference to a document which lists all attributes I misspelled the spool and cap DLs. Sorry for the resend. Tom -----Original Message----- From: Hastings, Tom N Sent: Saturday, August 03, 2002 16:53 To: 'spool@freestandards.org' Cc: printing-jobticket@freestandards.org; 'cap@freestandards.org'; 'ipp@pwg.org'; Zehler, Peter Subject: PAPI Chapter 9 ISSUE: Reference to a document which lists all attributes Alan, Chapter 9 of the FSG Print API (PAPI) spec, version V0.4 (ftp://ftp.pwg.org/pub/pwg/fsg/spool/papi_v0.4.pdf) has the following: Chapter 9. Attributes * ISSUE: Waiting for reference to single document from Tom H. I assume that this PAPI reference should be to a short document that lists all attributes and points to the specifications where they are described in detail, right? ISSUE: We need to discuss whether this short document should be to the PWG Semantic Model or to a more IPP specific document which contains references to all of the IPP attributes with the same IPP spellings and attribute syntaxes. I'm also copying this mail note to the FSG jobticket mailing list, since the job ticket API should provide mappings to the appropriate Job and Document attributes in the attached document. I'm also copying this mail note to the FSG cap (capabilities) mailing list, since the Capabilities API should provide mappings to the appropriate Printer attributes in the attached document. To see a draft of the PWG Semantic Model see: See ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc or later If the short document that the PAPI reference in Chapter 9 should be more IPP-specific, I've attached such a document. It only lists IPP WG approved IPP attributes, plus a few additions for a Document object proposal being worked on as part of the PWG Semantic Model and as an extension to IPP. The Document object proposal mostly re-uses job level attributes at the document level. Peter Zehler is incorporating all these attributes into the PWG Semantic Model and schema. Please send any comments to the mailing list. I'm in the process of registering with IANA those attributes in this document that have been published in RFCs. Unfortunately, I was unable to down load this file to the PWG FTP server: ftp://ftp.pwg.org/pub/pwg/fsg/spool/IPP-Object-Attributes.pdf ftp://ftp.pwg.org/pub/pwg/fsg/spool/IPP-Object-Attributes.doc so I've attached them as a single .zip file. I hope that it makes it through the freestandards mail system, since there is some limits to the size of attachments. Could somebody down load them to the above URLs this week? I'm leaving on vacation tomorrow (Sunday) and will return Thursday, August 15. Peter, If you want them in the PWG Semantic_model directory, please down load them there too. Thanks, Tom From alan_berkema at hp.com Sat Aug 10 10:26:00 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> [PSI]:NEW Number next call 08/20/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1FE@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday August 20 (USA) (No Call August 28) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) F2F Prep 2) TBD WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 8/20/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From imcdonald at sharplabs.com Wed Aug 14 13:00:00 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:06 2009 Subject: PS> FW: [Srvloc-discuss] Zeroconf and SLP BoF at Linux-Kongress [5 Se pt 2002] Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD3F@mailsrvnt02.enet.sharplabs.com> Hi folks, FYI - a BoF on Zeroconf and SLP at Linux-Kongress 2002 in Cologne (Koln) Germany on Thursday (5 September 2002). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Brad Hards [mailto:bhards@bigpond.net.au] Sent: Tuesday, August 13, 2002 7:04 PM To: openslp-devel@lists.sourceforge.net; zeroconf@merit.edu; srvloc-discuss@lists.sourceforge.net Cc: Erik Guttman Subject: [Srvloc-discuss] [OT] zeroconf and SLP BoF at Linux-Kongress -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have arranged a BoF session for Linux-Kongress 2002 on automatic networking technology implementation. A full description of what is planned is on line at http://www.linux-kongress.org/2002/bofs/index.html#zeroconf The BoF will be held Thursday 5-September-2002, in Cologne (Koln), Germany. The BoF will officially start at 1430, and run until 1600 (local time). However I will try to be at the room from about 1400 to welcome people and have informal discussions. We may have to vacate the room after (depends on other BoFs that are still to be scheduled) and find a pub or coffee house if it runs a bit long. Erik Guttman and I (well, mostly Erik, I guess) will be moderating it. I already have some expressions of interest from CUPS developers who will be at the conference, but if anyone else with an interest in this area can make, it'd be great to see you there. Full conference details are on their web-site (see above). I strongly encourage you to register (even if only for the day), although it is not absolutely mandatory if you only want to attend the BoF. If you don't register, you can't go to the official talks and wont get any coffee in the breaks etc. and no printed proceedings. You can attend the exhibition though. Sorry if this is too off-topic, but a get-together for a few hours can often overcome weeks of emails, so this might be a good chance to progress things. Brad - -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9WZBUW6pHgIdAuOMRAmypAJ9iamNZoKOr/SVrKTTD6YDnodh7PwCgrBcc RZ1Yo1s+UCIImE6YHJkE/fM= =Fa+r -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Srvloc-discuss mailing list Srvloc-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/srvloc-discuss From alan_berkema at hp.com Mon Aug 19 21:37:30 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:06 2009 Subject: PS> RE: [PSI]:NEW Docs NEW Number next call 08/20/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD206@xrose03.rose.hp.com> Hey all (especially Ira), I put a new psi-spec32.doc == psi-spec-latest.pdf on the web site. OK if you just want to follow along with webex. Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Saturday, August 10, 2002 7:26 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]:NEW Number next call 08/20/02 Teleconference details: Date: Tuesdays, Next: Tuesday August 20 (USA) (No Call August 28) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) F2F Prep 2) TBD WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 8/20/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Tue Aug 20 18:33:56 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: next call 09/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD219@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: (No Call September 3, day after holiday after F2F) Tuesday Septemebr 10 (USA) (No Call Septemebr 24?) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) Continue F2F Topics and actions 2) TBD WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 9/10/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Thu Aug 22 14:01:30 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD22D@xrose03.rose.hp.com> Hey all, I posted pdf files with line numbers to psi-spec & the selected logical view on the ps page. Alan From alan_berkema at hp.com Thu Aug 22 16:37:59 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: [PSI]: F2F Agenda 8/28/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD233@xrose03.rose.hp.com> All: Here is a proposed agenda for the PSI F2F on Wednesday I. Introductions II. Review and Approve minutes from June (ftp://ftp.pwg.org/pub/pwg/ps/MinutesJune2602.pdf) III. Review Agenda IV. Review Action Items V. Topics from Phone Conferences Print Service Interface name change to something like QueryInterfaceEndpoints. This is the interface in the spec. not renaming the spec. itself. Discuss Discovery Strategy Notification Name Change Seperate Credential Schema? VI. Review Attribute Structure Object Schemas (ftp://ftp.pwg.org/pub/pwg/ps/Job.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/JobAttibutes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Document.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/DocumentAttributes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Processing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Finishing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Rendering.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Imposition.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/typesPWG.xsd) VII. Review reference schema (ftp://ftp.pwg.org/pub/pwg/ps/reference080502.xsd) VIII. Review targetDevice schema (ftp://ftp.pwg.org/pub/pwg/ps/targetDevice080502.xsd) IX. Review PSI Spec & Selected Logical View (ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf) (ftp://ftp.pwg.org/pub/pwg/ps/psi-model-view.pdf) X. Plan Forward & teleconference schedule with respect to Holidays & Vacations Alan From hastings at cp10.es.xerox.com Thu Aug 22 16:52:17 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:07 2009 Subject: PS> First Draft IPP Document Object spec down-loaded Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F9080702FC@x-crt-es-ms1.cp10.es.xerox.com> Peter Zehler posted the next draft (0.07) of the PWG Semantic Model on August 16 at: ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-07-020816.pdf The PWG Semantic Model document is intended to be short and to refer to other documents for the details (mostly IPP documents). The PWG Semantic Model is also intended to be used by other groups that are developing print semantics in order to make any API, protocol, and job ticket semantics as similar as possible, such as those being developed by other PWG sub-groups and other groups, such as the sub-groups in the Free Standards Group OpenPrinting WG. The PWG Semantic Model adds a new Document object to the model. It re-uses most of the existing Job attributes for the Document object. However, the detailed specification for the Document object, operations, attributes, and values is needed for the Semantic Model to reference. This mail note announces a first draft of such a 36-page document. Its available at: ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/document-object-v094.pdf 200Kb ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/document-object-v094.doc 1000Kb ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/document-object-v094.zip 140Kb - just the .doc The .doc file is 1Mbyte, probably because of the two Visio state diagrams, or maybe the tables. This IPP Document Object specification is intended to give a common semantic model for the Document object for use by IPP (ipp@pwg.org), the PWG Semantic Model (sm@pwg.org), the PWG Print Services Interface (PSI) (ps@pwg.org), and the Free Software Group (FSG) PAPI (printing-spool@freestandards.org) and Job Ticket APIs (printing-jobticket@freestandards.org). For more info on the 3 PWG sub-groups, visit http://www.pwg.org For more info on the 2 FSG sub-groups, visit http://www.freestandards.org/openprinting The PWG is meeting next week in Santa Fe: Monday Aug 26: Internet FAX Tuesday Aug 27: PWG Plenary/XHTML-print Wednesday, Aug 28: Print Services Interface (PSI) (Thursday UPnP). There are 9 issues (included below) in the document that would be good to handle at some point in the agenda. And any other issues raised by reading the spec would be good too. Since there are 5 groups working on this (see To list), I suggest that any comments be sent to all lists as a reply all. Here is the Abstract: This document is an IPP extension proposal to extend the IPP/PWG semantics to include a Document object. The Job object is said to contain one or more Document objects which are passive objects operated on by the Job. The Document object is created by the existing Send-Document and Send-URI operations. However, a client can supply additional Document Template attributes with each document and new Document Description attributes are defined. Also there are seven new operations defined for Documents once they have been created. The purpose for specifying the Document object, is so that we can have a common specification for use in IPP, the PWG Semantic Model, the PWG PSI project, and the Free Standards Group Job Ticket API which all have a Document object. Here are the 9 issues: ISSUE 01: Should we publish this document as an IETF standards track document or as an IEEE-ISTO standard? If the former, since the IETF IPP WG is in the process of being closed down when all the current specifications are published, Peter and Tom will propose the specification as individual authors standards track contribution (after PWG review). If the latter, it will be published as one more IEEE-ISTO standard in the 5100.n series. --------------------------- According to [coll], the "document-overrides" (collection) attribute MAY be supplied by the client in a Send-Document or Send-URI request as an Operation attribute to apply document overrides to this and/or subsequent documents in the job. See the "document-overrides" Job Template attribute in Table 3 for the listing of the member attributes. However, with the introduction of the Document object, the "document-overrides" (collection) attribute SHOULD NOT be used (either as a Job Template attribute or an Operation attribute). Instead, the client simply supplies the Document Template attributes (see Table 3) for each Document Creation request (in a new Document Template attribute group) without needing a collection. ISSUE 02: What do we want to do with the "document-overrides" collection attributes when supporting the Document object, which is no longer needed as either a Job Template, Document Template, or operation attribute in Job and Document Creation requests? --------------------------- Similarly, according to [coll], the "page-overrides" (collection) attribute MAY be supplied by the client in a Send-Document or Send-URI request as an Operation attribute to apply page overrides to this and/or subsequent documents in the job. See the "page-overrides" Job Template attribute in Table 3 for the listing of the member attributes. However, with the introduction of the Document object, the "page-overrides" (collection) attribute SHOULD be more simply supplied as one of the Document Template attributes for this document only. ISSUE 03: What do we want to do with the "page-overrides" collection attributes when supporting the Document object, which is still needed as a Job Template and Document Template attribute for overriding attributes in specified page ranges, but is not needed as an operation attribute on Document Creation requests? --------------------------- ISSUE 04: Is the following query behavior for Job and Document objects OK? Job Template and Document Template attributes are OPTIONAL for a Printer to support and for a client to supply in a Job Creation or Document Creation request or a Document Overrides or Page Overrides. If a Printer supports a Job Template or Document Template attribute, then it MUST copy the supplied attribute to the Job or Document object, respectively so that a client MAY query the attributes in subsequent Get-Job-Attributes/Get-Jobs and Get-Document-Attributes/Get-Documents operations, respectively. The effect of Job Template Attributes supplied in Job Creation requests are inherited by the Document objects, unless the Document Creation operation supplies the attribute with a different value. However, the Printer MUST NOT propagate Job Template attributes supplied in Job Creation operations to the Document object. Similarly, the Printer MUST NOT promote Document Template attributes up to the Job object when no corresponding Job Template attribute was supplied in the Job Creation operation. Thus the Printer returns in queries only Job Template and Document Template attributes that were actually supplied by a client. --------------------------- [job-] indicates an attribute that shouldn't have had a "job-" prefix in its name in [RFC2911], so that the same attribute could also apply to the Document object as a Document Description attribute. Note: For the PWG Semantic Model, the "job-" prefix is proposed to be dropped. ISSUE 05: Should we sort the attributes ignoring the [job-]? Current the "job-" is used in the sort for attributes. ISSUE 06: How will we register these attributes with IANA, since they will be registered for IPP use, with the "job-" prefix. Do we add the ones without "job-" as aliases to the IANA registry as is done for charset registrations? --------------------------- [job-] indicates a state reason keyword value that shouldn't have had a "job-" prefix in its name in [RFC2911], so that the same value could also apply at the Document level as a "document-state-reasons" attribute value. Note: For the PWG Semantic Model, the "job-" prefix will be dropped. For purposes of sorting in Table 6, the "[job-]" prefix is ignored, since the PWG Semantic Model name is proposed without the prefix. ISSUE 07: Should we sort the attributes values including the [job-]? Currently the "job-" is ignored in the sort for attribute values. ISSUE 08: How will we register these attribute values with IANA, since they will be registered for IPP use, with the "job-" prefix. Do we add the ones without "job-" as aliases to the IANA registry as is done for charset registrations? --------------------------- TBD - one to list the Document Template keyword attribute names supported. ISSUE 09: What other Printer Description attributes are needed, if any? Send comments to the mailing lists. Thanks, Tom From PZehler at crt.xerox.com Fri Aug 23 10:09:49 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: [PSI]: F2F Agenda 8/28/02 Message-ID: All, I would like to modify the proposed agenda for the upcoming PSI face to face. Based on input from our last meeting and the mailing list I have updated the schemas referenced in section VI. There is now a "master list" of all the semantic elements(and types) defined by the PWG Semantic model (See i). These semantic elements and groups are referenced from the other files. There is a single file that defines the grouping of processing attributes into the 4 groups finishing, rendering, imposition and job-level (See ii). The document, job and printer are described in the remaining files. VI. Review Attribute Structure Object Schemas i. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PwgAttr.xsd ii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/ProcessingAttributes.xsd iii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Document.xsd iv. ftp://ftp.pwg.org/pub/pwg/Semantic_model/DocumentAttributes.xsd v. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Job.xsd vi. ftp://ftp.pwg.org/pub/pwg/Semantic_model/JobAttributes.xsd vii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Printer.xsd viii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrinterAttributes.xsd Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, August 22, 2002 4:38 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> RE: [PSI]: F2F Agenda 8/28/02 All: Here is a proposed agenda for the PSI F2F on Wednesday I. Introductions II. Review and Approve minutes from June (ftp://ftp.pwg.org/pub/pwg/ps/MinutesJune2602.pdf) III. Review Agenda IV. Review Action Items V. Topics from Phone Conferences Print Service Interface name change to something like QueryInterfaceEndpoints. This is the interface in the spec. not renaming the spec. itself. Discuss Discovery Strategy Notification Name Change Seperate Credential Schema? VI. Review Attribute Structure Object Schemas (ftp://ftp.pwg.org/pub/pwg/ps/Job.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/JobAttibutes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Document.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/DocumentAttributes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Processing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Finishing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Rendering.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Imposition.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/typesPWG.xsd) VII. Review reference schema (ftp://ftp.pwg.org/pub/pwg/ps/reference080502.xsd) VIII. Review targetDevice schema (ftp://ftp.pwg.org/pub/pwg/ps/targetDevice080502.xsd) IX. Review PSI Spec & Selected Logical View (ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf) (ftp://ftp.pwg.org/pub/pwg/ps/psi-model-view.pdf) X. Plan Forward & teleconference schedule with respect to Holidays & Vacations Alan From hastings at cp10.es.xerox.com Mon Aug 26 20:50:28 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:07 2009 Subject: PS> Terminology comment: "Job Attributes" and "Document Attributes" Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F9080703C1@x-crt-es-ms1.cp10.es.xerox.com> Peter, I don't have any problem with the PWG Semantic Model improving on the terminology from IPP, such as the term "Processing Attributes" instead of "Job Template Attributes". I also think that the Processing Attributes are a combination of the IPP Job Template attributes and the Job Creation operation attributes, and the concept of operation attributes has disappeared, right? However, where the IPP terminology is OK, I suggest we stick with it. For example, the term "Job Attributes" (section 2.2.1, Figure 5 and Section 4.2 Table 4) is equivalent to the IPP Job Description Attributes. I suggest that we stick with the term "Job Description Attributes" in the PWG Semantic Model, i.e., attributes that the Printer produces the values for. Another reason is that the term Job Attributes should mean all of the attributes of the Job object, not a subset. The Processing Attributes are really Job Attributes too, since the client supplies them, but the Printer copies them to the Job object. So I suggest that a Job object contains Job Attributes which consist of Processing Attributes supplied by the client and Job Description attribute supplied by the Printer. Same for the term "Document Attributes" (section 2.3.1, Figure 7, section 4.3, Table 5). The term should be "Document Description Attributes". So a Document object contains Document Attributes which consist of Processing Attributes supplied by the client and Document Description attribute supplied by the Printer. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Saturday, August 24, 2002 18:05 To: 'sm@pwg.org' Subject: SM> Semantic documernts All, Sorry if this as a repeat for you. I apparently was not subscribed to the sm mailing list for some unknown reason. Therefore I have missed any traffic. In preparation for the meeting in Santa Fe a new version of the Semantic Model document was posted on the PWG site. The URL is " ". We will use this document with line numbers as the basis for our conversation at the PWG meeting. I have updated the XML schema files based on input and the new semantic document. There is now a "master list" of all the semantic elements(and types) defined by the PWG Semantic model (See i). These semantic elements and groups are referenced from the other files. There is a single file that defines the grouping of processing attributes into the 4 groups finishing, rendering, imposition and job-level (See ii). The document, job and printer are described in the remaining files. VI. Review Attribute Structure Object Schemas i. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PwgAttr.xsd ii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/ProcessingAttributes.xsd iii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Document.xsd iv. ftp://ftp.pwg.org/pub/pwg/Semantic_model/DocumentAttributes.xsd v. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Job.xsd vi. ftp://ftp.pwg.org/pub/pwg/Semantic_model/JobAttributes.xsd vii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Printer.xsd viii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrinterAttributes.xsd Pete From hastings at cp10.es.xerox.com Tue Aug 27 17:03:47 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New docs [watch out: web page != ftp directory] Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F908070423@x-crt-es-ms1.cp10.es.xerox.com> Alan, The psi-spec32.doc file that you posted as ftp://ftp.pwg.org/pub/pwg/ps/psi-spec32.doc on August 19, has Revision number 0.32 and a date in the document of August 19. However, the .PDF versions that you posted as ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf on August 22, has a Revision number of 0.30 and a date in the document of July 18 and doesn't have line numbers. Also the Model View file that you posted on August 22 as ftp://ftp.pwg.org/pub/pwg/ps/psi-model-view.pdf on August 22, has an internal generated date of April 22, 2002. However, if you go to the web page, you do get the intended .pdf file with a version of 0.32 that agree with the .doc. Is there anyway to keep the ftp available files synchronized with the web page available files? What about all of the schema xsd files that appear both on the web page and the FTP directory with a date of August 22? Are they the same files? Thanks, Tom -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, August 22, 2002 11:02 To: 'a PSI pwg.org'; BERKEMA,ALAN C (HP-Roseville,ex1) Subject: PS> [PSI]: New docs Hey all, I posted pdf files with line numbers to psi-spec & the selected logical view on the ps page. Alan From hastings at cp10.es.xerox.com Tue Aug 27 17:11:13 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:07 2009 Subject: PS> Terminology comment: "Job Attributes" and "Document Attri butes" Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F908070424@x-crt-es-ms1.cp10.es.xerox.com> PSI WG, I should have said that this comment on terminology was for both the PWG Semantic Model and the PSI Specification, since terms in question are nicely aligned between PSI Spec and the PWG Semantic Model. Tom -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Monday, August 26, 2002 17:50 To: 'sm@pwg.org' Cc: ps@pwg.org Subject: PS> Terminology comment: "Job Attributes" and "Document Attributes" Peter, I don't have any problem with the PWG Semantic Model improving on the terminology from IPP, such as the term "Processing Attributes" instead of "Job Template Attributes". I also think that the Processing Attributes are a combination of the IPP Job Template attributes and the Job Creation operation attributes, and the concept of operation attributes has disappeared, right? However, where the IPP terminology is OK, I suggest we stick with it. For example, the term "Job Attributes" (section 2.2.1, Figure 5 and Section 4.2 Table 4) is equivalent to the IPP Job Description Attributes. I suggest that we stick with the term "Job Description Attributes" in the PWG Semantic Model, i.e., attributes that the Printer produces the values for. Another reason is that the term Job Attributes should mean all of the attributes of the Job object, not a subset. The Processing Attributes are really Job Attributes too, since the client supplies them, but the Printer copies them to the Job object. So I suggest that a Job object contains Job Attributes which consist of Processing Attributes supplied by the client and Job Description attribute supplied by the Printer. Same for the term "Document Attributes" (section 2.3.1, Figure 7, section 4.3, Table 5). The term should be "Document Description Attributes". So a Document object contains Document Attributes which consist of Processing Attributes supplied by the client and Document Description attribute supplied by the Printer. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Saturday, August 24, 2002 18:05 To: 'sm@pwg.org' Subject: SM> Semantic documernts All, Sorry if this as a repeat for you. I apparently was not subscribed to the sm mailing list for some unknown reason. Therefore I have missed any traffic. In preparation for the meeting in Santa Fe a new version of the Semantic Model document was posted on the PWG site. The URL is " ". We will use this document with line numbers as the basis for our conversation at the PWG meeting. I have updated the XML schema files based on input and the new semantic document. There is now a "master list" of all the semantic elements(and types) defined by the PWG Semantic model (See i). These semantic elements and groups are referenced from the other files. There is a single file that defines the grouping of processing attributes into the 4 groups finishing, rendering, imposition and job-level (See ii). The document, job and printer are described in the remaining files. VI. Review Attribute Structure Object Schemas i. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PwgAttr.xsd ii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/ProcessingAttributes.xsd iii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Document.xsd iv. ftp://ftp.pwg.org/pub/pwg/Semantic_model/DocumentAttributes.xsd v. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Job.xsd vi. ftp://ftp.pwg.org/pub/pwg/Semantic_model/JobAttributes.xsd vii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Printer.xsd viii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrinterAttributes.xsd Pete From alan_berkema at hp.com Wed Sep 4 19:17:41 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: Proposed mins 8/28/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD263@xrose03.rose.hp.com> please see attached will also post later comments/corrections welcome Thanks, Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI minutes 82802.pdf Type: application/octet-stream Size: 79281 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020904/9ae1dd9e/PSIminutes82802.obj From alan_berkema at hp.com Thu Sep 5 12:51:58 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New Docs from 08/28/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD269@xrose03.rose.hp.com> With modifications from F2F psi-spec33.doc = psi-spec-latest.pdf psi082802.doc = psi-model-view.pdf psi082802.mdl = no link yet Thanks, Alan From alan_berkema at hp.com Tue Sep 10 13:14:58 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: next call 09/17/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD29F@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday Septemebr 17 (USA) (No Call Septemebr 24???) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) Continue TargetDeviceSupport Interface & Basic Notification Discussion 2) PWG Sematic Model Attribute Alignment WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 9/17/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Thu Sep 12 17:24:26 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: minutes 9/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD2C0@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema Gail Songer *Dave Hall Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke Ira Mcdonald Amir Shahindoust * = attendance 09/10/02 Agenda 1) Review the PSI schedule 2) Review the targetDeviceSupport interface Minutes: Thinly attended, however it was still a very productive meeting. 1) Review the PSI schedule See schedule attached. By the end of September we will attempt to get the spec to rev 0.9. This will include the spec. and the logical view in a single document. We need to resolve all the outsatnding issues or jetison the feature to Post 1.0. It will also add the WSDL/SOAP for the methods. I realize this is aggresive, however, we definately won't make it if don't try for it. When we post .9 we have a few phone conferences to continue to work on it. On October 22 we will post the revisions as a .93 spec, two week before the Novemebr F2F. .93 is the candidate .95 spec. We will review this and changes will become the .94 spec. Apx. two weeks after this I will call for a vote to promote this to 0.95. The philosophy behind setting an aggressive schedule in the charter was to enable a base level of PSI functionality to test it and attempt to foster early market adoption, rather than work on a spec for multiple years that covers everything. 2) Review the targetDeviceSupport interface associateTargetDevice(), does this belong in 1.0? Ira commented that this isn't specified well enough and "a mircle needs to happen" for this to work. Take a look and we will revisit at the next call. The postStatus methods were changed to sendServiceNotifications sendJobNotifications sendDocumentNotifications sendServiceNotifications includes jobState, jobStateReasons and an eventID. These are all simple noticiations that do not involve subscriptions. The above conclusion was reached via an involved discussion about notifications in general, subscriptions, and why are we doing notifications at all and why are we doing them in the targetDeviceSupport interface? Conclusion is that the targetDeviceSupport interface is primarlly used when the targetDevice is behind a firewall and the PS cannot do a getJobAttributes. We need a boolean that tells the targetDevice if the PS wants notifications or not. We previously thought that this would go in the createJob, however since the notifications are only used with the tagetDeviceSupport interface we deiced to put the boolean in the getNextJob. Is it also in getNextDcoument? forgot where we landed. Discussion about getKnowTargetDevices, does this belong in the targetDeviceSupport? I think we decided to move this to jobControl? that is all, Alan From alan_berkema at hp.com Fri Sep 13 16:16:53 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: [PSI]: Updated minutes 9/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD2D0@xrose03.rose.hp.com> I forgot to include Ira as an attendee. Alan ---- PSI Working Group: *Alan Berkema Gail Songer *Dave Hall Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 09/10/02 Agenda 1) Review the PSI schedule 2) Review the targetDeviceSupport interface Minutes: Thinly attended, however it was still a very productive meeting. 1) Review the PSI schedule See schedule attached. By the end of September we will attempt to get the spec to rev 0.9. This will include the spec. and the logical view in a single document. We need to resolve all the outsatnding issues or jetison the feature to Post 1.0. It will also add the WSDL/SOAP for the methods. I realize this is aggresive, however, we definately won't make it if don't try for it. When we post .9 we have a few phone conferences to continue to work on it. On October 22 we will post the revisions as a .93 spec, two week before the Novemebr F2F. .93 is the candidate .95 spec. We will review this and changes will become the .94 spec. Apx. two weeks after this I will call for a vote to promote this to 0.95. The philosophy behind setting an aggressive schedule in the charter was to enable a base level of PSI functionality to test it and attempt to foster early market adoption, rather than work on a spec for multiple years that covers everything. 2) Review the targetDeviceSupport interface associateTargetDevice(), does this belong in 1.0? Ira commented that this isn't specified well enough and "a mircle needs to happen" for this to work. Take a look and we will revisit at the next call. The postStatus methods were changed to sendServiceNotifications sendJobNotifications sendDocumentNotifications sendServiceNotifications includes jobState, jobStateReasons and an eventID. These are all simple noticiations that do not involve subscriptions. The above conclusion was reached via an involved discussion about notifications in general, subscriptions, and why are we doing notifications at all and why are we doing them in the targetDeviceSupport interface? Conclusion is that the targetDeviceSupport interface is primarlly used when the targetDevice is behind a firewall and the PS cannot do a getJobAttributes. We need a boolean that tells the targetDevice if the PS wants notifications or not. We previously thought that this would go in the createJob, however since the notifications are only used with the tagetDeviceSupport interface we deiced to put the boolean in the getNextJob. Is it also in getNextDcoument? forgot where we landed. Discussion about getKnowTargetDevices, does this belong in the targetDeviceSupport? I think we decided to move this to jobControl? that is all, Alan From imcdonald at sharplabs.com Thu Sep 19 09:57:41 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> FW: IPP> FW: Errata in RFC 2911: "Internet Printing Protocol/1.1: Model an d Semantics" Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDA7@mailsrvnt02.enet.sharplabs.com> Hi folks, Please note the following minor errata to IPP/1.1 (RFC 2911). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Wednesday, September 18, 2002 3:12 PM To: ipp@pwg.org Subject: IPP> FW: Errata in RFC 2911: "Internet Printing Protocol/1.1: Model an d Semantics" This very minor RFC 2911 Errata has been posted finally. To see any RFC Errata, go to: http://www.rfc-editor.org/rfcsearch.html Then bug on the RFC Errata box. They are sorted in reverse order by RFC number. If you've looked before, make sure you tell your Browser to refresh or you won't find the latest Errata. Tom -----Original Message----- From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: Wednesday, September 18, 2002 10:13 To: rfc-editor@rfc-editor.org; hastings@cp10.es.xerox.com Cc: hastings@cp10.es.xerox.com; carl@manros.com Subject: Re: FW: IPP> Errata in RFC 2911: "Internet Printing Protocol/1.1: Mod el and Semantics" Tom, We apologize for the delay. We have updated our errata page to refelct the errors indicated below. Thank you. RFC Editor > From: "Hastings, Tom N" > To: rfc-editor@rfc-editor.org > Cc: "Hastings, Tom" , "Manros, Carl-Uno" > Subject: FW: IPP> Errata in RFC 2911: "Internet Printing Protocol/1.1: Mod el and Semantics" > Date: Tue, 3 Sep 2002 13:32:16 -0700 > MIME-Version: 1.0 > > I submitted this Errata in July. It hasn't been posted yet. Is there > anything more that I have to do? Does it have to be approved by anyone, > such as our AD? > > Its not critical, though a recent I-D that is going through last call is > assuming that the errata is true and accepted, so it would be good to post > the errata. > > Thanks, > Tom > > -----Original Message----- > From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] > Sent: Wednesday, July 17, 2002 17:52 > To: rfc-editor@rfc-editor.org > Cc: ipp@pwg.org > Subject: IPP> Errata in RFC 2911: "Internet Printing Protocol/1.1: Model > and Se mantics" > > > This note points out two errata in RFC 2911 regarding the ranges of status > codes. > > Section 13, which is "APPENDIX B: Status Codes and Suggested Status Code > Messages" has: > > "redirection" - 0x0200 to 0x02FF > > which should be: > > "redirection" - 0x0300 to 0x03FF > > and has: > > The top half (128 values) of each range (0x0n40 to 0x0nFF, for n = 0 > to 5) is reserved for vendor use within each status code class. > > which should be: > > The top half (128 values) of each range (0x0n80 to 0x0nFF, for n = 0 > to 5) is reserved for vendor use within each status code class. > > Thank you, > > Tom Hastings > IPP WG Editor From harryl at us.ibm.com Thu Sep 19 12:21:32 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:07 2009 Subject: PS> Throwing exceptions Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/e5d349de/attachment.html From dhall at hp.com Thu Sep 19 12:33:01 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: Throwing exceptions Message-ID: <77261E830267D411BD4D00902740AC250B5970F7@xvan01.vcd.hp.com> We are rapidly approaching a working PSI prototype that will be able to "throw exceptions" from the method calls. They are known as "soap faults"... Our current methods don't "throw exceptions" in the XML string parameters that are returned, it was an unfortunate naming of the return paramater - "ExceptionAttributes" that is now named "UnsupportedAttributes". Returning "UnsupportedAttributes" does not mean that an error has occured, rather that some requested attributes are not supported by the service. We will be throwing "faults" from the soap calls... Hopefully this is clearer now.. :) Dave -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, September 19, 2002 9:22 AM To: HALL,DAVID (HP-Vancouver,ex1) Cc: ps@pwg.org; alan_berkema@hp.com Subject: Throwing exceptions How to throw an exception form a SOAP method. I see this in the spec as a question ... "DHall - define exactly how to throw an exception from a SOAP method" section 5.3.1. Our current definition packages exceptions as a multi XML string parm set in the return. Is this our conscious resolution to PSI exceptions? Have we considered throwing exceptions, independently, across the web services interface? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/9c062e0f/attachment.html From harryl at us.ibm.com Thu Sep 19 16:47:37 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: Throwing exceptions Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/3c600b89/attachment.html From dhall at hp.com Thu Sep 19 17:12:37 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: Throwing exceptions Message-ID: <77261E830267D411BD4D00902740AC250B597110@xvan01.vcd.hp.com> Hey Harry... I believe that the polling scenario is indeed the correct model. For this particular method, we may not have it exactly right. We could overload the JobID == 0 to mean that no job is available, but that doesn't quite feel right. Throwing an exception in this case is really our way of informing the client (targetdevice) that no job is available for it yet. Dave Pseudo code: Boolean bJobAvailable = false; String JobID = ""; while (!bJobAvailable) { try { JobID = PrintService.TargetDeviceSupportInterface.GetNextJob("myTargetDeviceIdentifi er"); bJobAvailable = true; } catch (Exception e) { if (e == InvalidTargetDeviceIdentifier) { exit(InvalidTargetDeviceIdentifier); } elseif (e == TargetDeviceNotSupported) { exit(TargetDeviceNotSupported); } elseif (e == NoJobAvaliable) { // OK, keep polling } } } // Now we have a JobID, continue processing... -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, September 19, 2002 1:48 PM To: HALL,DAVID (HP-Vancouver,ex1) Cc: BERKEMA,ALAN C (HP-Roseville,ex1); HALL,DAVID (HP-Vancouver,ex1); ps@pwg.org Subject: RE: Throwing exceptions OK, thanks for that clarification. Related question... In the TargetDeviceSupportInterface the operation GetNextJob "throws and exception" if no job is available for the target device. I assume, then, this is a SOAP "fault"? If so, is this really what we want? The design is polling from target device to print service. In this case won't "no job available" be the more likely case? Or, are we suggesting (via the scenarios) that the target device isn't expected to poll unless having been asked to out of band by a client (implying there SHOULD be a job present... thus the "fault")? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "HALL,DAVID (HP-Vancouver,ex1)" 09/19/2002 10:33 AM To: Harry Lewis/Boulder/IBM@IBMUS, "HALL,DAVID (HP-Vancouver,ex1)" cc: ps@pwg.org, "BERKEMA,ALAN C (HP-Roseville,ex1)" Subject: RE: Throwing exceptions We are rapidly approaching a working PSI prototype that will be able to "throw exceptions" from the method calls. They are known as "soap faults"... Our current methods don't "throw exceptions" in the XML string parameters that are returned, it was an unfortunate naming of the return paramater - "ExceptionAttributes" that is now named "UnsupportedAttributes". Returning "UnsupportedAttributes" does not mean that an error has occured, rather that some requested attributes are not supported by the service. We will be throwing "faults" from the soap calls... Hopefully this is clearer now.. :) Dave -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, September 19, 2002 9:22 AM To: HALL,DAVID (HP-Vancouver,ex1) Cc: ps@pwg.org; alan_berkema@hp.com Subject: Throwing exceptions How to throw an exception form a SOAP method. I see this in the spec as a question ... "DHall - define exactly how to throw an exception from a SOAP method" section 5.3.1. Our current definition packages exceptions as a multi XML string parm set in the return. Is this our conscious resolution to PSI exceptions? Have we considered throwing exceptions, independently, across the web services interface? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/ecbc911d/attachment.html From alan_berkema at hp.com Fri Sep 20 14:13:22 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New Docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD306@xrose03.rose.hp.com> psi-spec35.doc = psi-spec-latest.pdf psi091902.doc = psi-model-view.pdf psi091902.mdl = no link yet Thanks, Alan From imcdonald at sharplabs.com Mon Sep 23 11:21:07 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> FW: Unicode text editor mined 2000 release 4 Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDB1@mailsrvnt02.enet.sharplabs.com> Hi folks, FYI - a native Unicode text editor for all UNIX/DOS/Windows platforms. Cheers, - Ira McDonald High North Inc -----Original Message----- From: thomas@towo.net [mailto:thomas@towo.net] Sent: Sunday, September 22, 2002 7:13 PM To: linux-utf8@nl.linux.org; Subject: Unicode text editor mined 2000 release 4 ANNOUNCEMENT mined 2000 release 4 An editor that is small and easy to use but yet full of capabilities. Runs in plain text mode terminals. Supports Unicode. Provides mouse control and menus. Runs on Unix and DOS/Windows platforms. Short description Good interactive features * an intuitive user interface * command control and pull-down menus available * control and function key or mouse control Many useful text editing features * extensive Unicode support, including double-width and combining characters * many text editing capabilities, e.g. paragraph wrapping, smart quotes, multi-line support in search and replacement patterns * program editing features, HTML support and syntax highlighting, identifier search * systematic text and file handling safety, avoiding loss of data "Small-footprint" operation and portability * plain text mode (terminal) operation * instant start-up * cross-platform operation (Unix, DOS/Windows) More information (with screenshots and change log) and download are available from the mined web page at http://towo.net/mined/ ---------------------------------------------------------------------------- - Thomas Wolff mined@towo.net -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/ From dhall at hp.com Tue Sep 24 09:57:24 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> PSI Meeting Info for 9-24 Message-ID: <77261E830267D411BD4D00902740AC250B597175@xvan01.vcd.hp.com> Hi All... Sorry for the late meeting notice info... Dave Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 ------------------------- MEETING SUMMARY ------------------------- Name: PSI Date: 9/24/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 22021870 Meeting Password: newpsi From PZehler at crt.xerox.com Tue Sep 24 13:08:37 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:07 2009 Subject: PS> Server side Stub generation Message-ID: Dave, I think it was you that asked about tools that support the generation of server-side skeletons as well as client-side stubs from a WSDL file. I know that Microsoft .NET, Sun ONE, SYSINET WASP and Ximian SOUP support it. And I believe OpenSource FSU GSOAP also does. Pete 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 From imcdonald at sharplabs.com Tue Sep 24 15:34:44 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> Valid XML - ISO DSDL and RELAX NG Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDB5@mailsrvnt02.enet.sharplabs.com> Hi folks, Per my action item from today's PSI telecon, some info on RELAX NG, which is the OASIS developed successor to RELAX and is soon to be published part 2 of ISO 19757. For more info on RELAX NG see the OASIS site at: http://www.oasis-open.org/committees/relax-ng/ For more info on RELAX NG tools go to: http://www.oasis-open.org/committees/relax-ng/#tools I just stored several files on the PWG FTP server: ftp://ftp.pwg.org/pub/pwg/ps/dsdl/iso-cd-19757-0-DSDL-Overview.pdf - ISO/IEC CD 19757-0 Document Description and Processing Languages - Document Schema Definition Language (DSDL) - Part 0 - Overview - CD = Committee Draft (i.e., working document) ftp://ftp.pwg.org/pub/pwg/ps/dsdl/iso-dis-19757-2-RELAX-NG.pdf - ISO/IEC DIS 19757-2 Document Description and Processing Languages - Document Schema Definition Language (DSDL) - Part 2 - Grammar-Based Validation - RELAX NG - DIS = Draft International Standard (now in balloting) ftp://ftp.pwg.org/pub/pwg/ps/dsdl/xmloperator-2.0-supports-RELAX-NG.txt - text of a mail note from the RELAX-NG mailing list this morning Cheers, - Ira McDonald High North Inc From alan_berkema at hp.com Fri Sep 27 11:36:02 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD31C@xrose03.rose.hp.com> psi-spec37.doc = psi-spec-latest.pdf psi092602.doc = psi-model-view.pdf reference.xsd targetDevice.xsd interfaceIdentifer.xsd Thanks, Alan From alan_berkema at hp.com Mon Sep 30 12:05:48 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: next call 10/01/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD320@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday October 1 (USA) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) Continue TargetDeviceSupport Interface & Basic Notification Discussion 2) PWG Sematic Model Attribute Alignment WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 10/1/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Mon Sep 30 13:41:43 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: WSDL on the web Message-ID: <499DC368E25AD411B3F100902740AD650E6AD326@xrose03.rose.hp.com> Hi all, Checkout the PSI WSDL files: ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.TargetDeviceSupportInterface.w sdl AND ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.TargetDeviceSupportInterface.w sdl Thanks Dave, Alan From Lee.Farrell at cda.canon.com Mon Sep 30 14:32:31 2002 From: Lee.Farrell at cda.canon.com (Farrell, Lee) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: WSDL on the web Message-ID: Uhh... is there any comment/explanation/comparison about the difference(s) of these two sets of files that anyone would care to offer? At the very least, why two? -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, September 30, 2002 10:42 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: WSDL on the web Hi all, Checkout the PSI WSDL files: ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.ServiceCapabilitiesInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.TargetDeviceSupportInterface.wsdl AND ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.ServiceCapabilitiesInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.TargetDeviceSupportInterface.wsdl Thanks Dave, Alan From dhall at hp.com Mon Sep 30 15:35:22 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: WSDL on the web Message-ID: <77261E830267D411BD4D00902740AC250B59721F@xvan01.vcd.hp.com> Lee.. Nope, not yet - the main difference is that one was generated by the Axis toolkit, the other by the Wasp toolkit. We are leaning towards the Axis version, as it appears to be simplier, and the Wasp toolkit generates some dependencies on Wasp supporting libraries / types. We are in the middle of generating server and client code from the WSDL, and this will probably give us a definitive answer as to which we go with. Also, the WSDL may require a bit of hand tweaking, but I hope not.. Dave -----Original Message----- From: Farrell, Lee [mailto:Lee.Farrell@cda.canon.com] Sent: Monday, September 30, 2002 11:33 AM To: ps@pwg.org Cc: alan_berkema@hp.com Subject: RE: PS> [PSI]: WSDL on the web Uhh... is there any comment/explanation/comparison about the difference(s) of these two sets of files that anyone would care to offer? At the very least, why two? -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, September 30, 2002 10:42 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: WSDL on the web Hi all, Checkout the PSI WSDL files: ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.TargetDeviceSupportInterface.w sdl AND ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.TargetDeviceSupportInterface.w sdl Thanks Dave, Alan From alan_berkema at hp.com Tue Oct 1 16:27:07 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New docs & Java code Message-ID: <499DC368E25AD411B3F100902740AD650E6AD32D@xrose03.rose.hp.com> psi-spec90.doc = psi-spec-latest.pdf - latest clean version psi-spec38.doc = psi-spec38.pdf - Changes from the past on java89/org.pwg.psi.zip - java code version of the methods Thanks, Alan From imcdonald at sharplabs.com Wed Oct 2 13:51:02 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: New docs Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDBE@mailsrvnt02.enet.sharplabs.com> Hi Alan, Something's not quite right. See the excerpt from an FTP listing of the PSI directory below. Cheers, - Ira McDonald High North Inc -------------------------- -rw-r--r-- 1 ftp ftp 344763 Oct 1 16:19 psi-spec38.pdf -rw-r--r-- 1 ftp ftp 328520 Oct 1 16:20 psi-spec-latest.pdf -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, September 27, 2002 11:36 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: New docs psi-spec37.doc = psi-spec-latest.pdf psi092602.doc = psi-model-view.pdf reference.xsd targetDevice.xsd interfaceIdentifer.xsd Thanks, Alan From alan_berkema at hp.com Mon Oct 7 11:50:49 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: next call 10/08/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD348@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday October 8 (USA) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) GetServiceAttributes 2) PSI Attribute Mandatory Optional? WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 10/1/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From harryl at us.ibm.com Tue Oct 8 02:01:56 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:07 2009 Subject: PS> Question about DocumentTypeSupportQuery Message-ID: In the ServiceCapabilities interface, the DocumentTypeSupportQuery has two parameters documentType:String targetDeviceIdentifier:String The targetDeviceIdentifier may be null or empty if the client only wishes to test whether the print service supports a particular documentType. What exactly does this mean? (What is the utility?) I'm thinking that a print service will support conversions "from and to" and it may be meaningless to ask the print service if it supports one side of the transform. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021008/cee1a897/attachment.html From harryl at us.ibm.com Tue Oct 8 02:02:04 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:07 2009 Subject: PS> Redundant operations in JobControl vs. TargetDeviceSupport interfaces? Message-ID: I had a task to write up a new use case and flow diagram. I got hung up as you can see below and need some explanation about the two ways for a client to associate a target device with a job and specify the document type transform. 1. Job is submitted to a printer via IPP or some other ?legacy? protocol a. Job is in some document format the printer does not support natively b. Printer will behave as both client and target device to engage print (transform) service. c. Printer does not want to poll to know when the print service has completed the transform and is ready to deliver the job 2. Using the TargetDeviceSupported Interface on the print service, Printer registers with print service as Target Device a. targetDeviceSupportInterface i. registerTargetDevice ii. deliveryMethod ? ?push? 3. Using the JobControl Interface on the print service, Printer (acting as client) defines targetDevice, specifies ?deliver? and requests a data type to translate to (of course the Printer will request the correct document format for itself? the whole point of this exercise). a. jobControlInterface i. createJob 1. targetDeviceIdentifier 2. deliverToTargetDevice = true 3. requestedTargetDeviceDataType OK HERE?S (ONE PLACE) WHERE I?M LOST 4. Using the targetDeviceSupportedInterface on the print service, Printer COULD associate the target device with the UID acquired during createJob (right?) and also request the target device data type a. targetDeviceSupportInterface i. associateTargetDevice 1. jobURI 2. userID 3. targetDeviceIdentifier 4. requestedTargetDeviceDataType What am I missing? Why do I feel like (3) and (4) are mostly redundant? Is one supposed to represent a longer term relationship between client and print service while the other should be thought of more as a ?per job? specification? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021008/181d58c0/attachment.html From alan_berkema at hp.com Tue Oct 8 12:57:34 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: next call 10/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD34E@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday October 15 (USA) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) To Do & Action Progress 2) Get Service Capabilities 3) Mandatory Optional Attributes WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 10/1/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From imcdonald at sharplabs.com Wed Oct 9 13:21:26 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> FW: W3C WG on Internationalization of Web Services Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDE7@mailsrvnt02.enet.sharplabs.com> Hi, Note the following (and see complete text of note below): - The Web Services (WS) Task Force is investigating the needs and problems in the area of internationalization of Web Services, in particular the dependency of Web Services on language, culture, region, and locale-related contexts. The chair of the Web Services Task Force is Addison Phillips, webMethods. See http://www.w3.org/International/ws for how you can participate. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Martin Duerst [mailto:duerst@w3.org] Sent: Thursday, October 03, 2002 9:21 AM To: www-international@w3.org Subject: Call for participation: I18N Activity WG Task Forces Dear Internationalizers, As announced at the International Unicode Conference in San Jose the W3C Internationalization Activity has recently been restructured, and the Internationalization Working Group (WG) and Interest Group (IG) have been re-chartered. We are sure that this will provide you with increased possibilities to contribute to Web Internationalization in the widest sense, and are looking forward to your participation. More information can be found at http://www.w3.org/International/about and in the WG charter http://www.w3.org/2002/05/i18n-recharter/WG-charter. The Working Group now consists of three Task Forces (see below) - The Core Task Force is continuing previous work: completing the Character Model for the World Wide Web and the Internationalized Resource Identifiers (IRIs) specifications, and continuing reviewing specifications produced by other W3C Working Groups. The chair of the WG and the Core Task Force is Misha Wolf, Reuters. See http://www.w3.org/International/core for how you can participate. - The Web Services (WS) Task Force is investigating the needs and problems in the area of internationalization of Web Services, in particular the dependency of Web Services on language, culture, region, and locale-related contexts. The chair of the Web Services Task Force is Addison Phillips, webMethods. See http://www.w3.org/International/ws for how you can participate. - The GEO (Guidelines, Education & Outreach) Task Force is helping to get the internationalization aspects of W3C technology better understood and more widely and consistently used. The chair of the GEO Task Force is Richard Ishida, W3C. See http://www.w3.org/International/geo/howto-join-geo for how you can participate. This list will be used for general public discussion on Web Internationalization, but with increased technical focus. Regards, Martin. #-#-# Martin J. Du"rst, I18N Activity Lead, World Wide Web Consortium #-#-# mailto:duerst@w3.org http://www.w3.org/People/D%C3%BCrst From alan_berkema at hp.com Wed Oct 9 18:49:48 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: [PSI]: minutes 10/08/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD36D@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald *Amir Shahindoust * = attendance 10/08/02 Agenda 1) Review Harry's e-mail questions 2) Review the use of port 3700 3) Review ToDo list 4) Call for action Minutes: As a prelude Ira suggested that we move PSI defined schemas into a seperate directory. Dave mentioned that the spec already calls for them to be ps/0.95 so we will put them there. Action: Move them Owner: Alan Status: Open 1) Review Harry's e-mail questions The first question revolves around the use of DocumentTypeSupportQuery and what it means if the TargetDeviceidentifier is NULL and is this useful? After much good discussion we decided that we can really do this same thing with GetServiceAttributes as long as we explicitly provide an example of how to do it. So DocumentTypeSupportQuery will be removed from the spec. Action: Write up some examples for GetServiceAttributes Owner: Dave Status: Open Harry's other question was around his new use case, which we agreed was illustrated as Use model 5 in the requirements doc. The question was about RegisterTargetDevice vs. AssociateTargetDevice. These are not intended to used together and enable the different use models we have. Action: Write up a an Applicability statement for AssociateTargetDevice useful in firewall scenario etc. and is redundant otherwise. Owner: Dave Status: Open As we looked at use model % in the requirements doc, we noticed that numbering on the arrows were off. Action: Fix Numbers and post Owner: Alan Status: Open 2) Review the use of port 3700 PSI has proposed asking IAN for a static port assignment we are calling port 3700 (IANA will probably dictate what actually get). We debated this vs. just using a dynamic port. Ira had some valid reasons for a static port in data aggregation scenarios with routers and gateways. Decided that a static port will be used for QueryInterafceEndpoints. Other discovery protocols will be used to get the hostname and could return a dynamic port. If a port is provide further queries will use that dynamic port. Otherwise the static port will be used. Doesn't this still open us up to the problems with dynamic ports? Action: Provide a brief write that explains why dynamic ports have issues. Also could get a brief write up on why overloading port 80 is not a good idea. Owner: Ira Status: Open 3) Review ToDo list Dave walked us through the ToDo list see spec 0.90 an the seem to be under control. 4) Call for action We are currently at rev 0.90 and it's time to do your homework and to take a close look at the spec. Harry set a good example with his e-mail questions. We will post intervening revs and a 0.94 candidate 2 weeks before the F2F. Fixes from the F2F will be incorporate into the 0.95 candidate. Action: Review the spec. Owner: All Status: Open Thanks, Alan From PZehler at crt.xerox.com Thu Oct 10 06:51:22 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:07 2009 Subject: PS> Java Print Service APIs Message-ID: All, Has any consideration been given to existing Java print APIs (based on IPP) and their relationship to PSI? http://java.about.com/gi/dynamic/offsite.htm?site=http://java.sun.com/j2se/1 .4/docs/guide/jps/index.html Pete 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021010/af39467f/attachment.html From imcdonald at sharplabs.com Fri Oct 11 14:09:18 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> PWG Parameters for MIME types ("document-format" values) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDEA@mailsrvnt02.enet.sharplabs.com> Hi folks, Friday (11 October 2002) Per my action item from Tuesday's PSI Telecon: Below are four proposed PWG standard optional parameters for MIME types, all extracted directly from the attributes (so-called SNMP 'objects') defined in the InterpreterTable of the Printer MIB (see comments below). Any of these PWG parameters MAY be appended (unordered) to any MIME type value of the IPP/PWG SM "document-format" attribute, for example: application/vnd.hp-pcl;pwg-pdl-resolution="400,400,dpi" These PWG parameters are specified in Augmented Backus-Naur Form (ABNF, RFC 2234). Every element used in one of these PWG parameter ABNF productions is defined in an excerpt from ABNF (RFC 2234), MIME Part One (RFC 2045), or Internet Message Format (RFC 2822) at the end of this note. According to RFC 2045: (1) Parameters MUST be ignored when unrecognized; (2) Parameters MUST be ignored when comparing values of MIME types; (3) MIME type names MUST be treated as case-insensitive; (4) MIME parameter names MUST be treated as case-insensitive; (5) MIME parameter values MUST be treated as case-sensitive. Each parameter name begins with a "pwg-" (namespace) prefix, to ensure that it is safely ignored by existing MIME-enabled software and systems. ; prtInterpreterLangLevel OCTET STRING ; - not supported in IPP/PWG SM pdl-level = "pwg-pdl-level" ; PDL language level "=" quoted-string ; e.g., "5e" for HP PCL ; or "2" for Adobe PostScript ; prtInterpreterLangVersion OCTET STRING ; - not supported in IPP/PWG SM pdl-version = "pwg-pdl-version" ; PDL version or date code "=" quoted-string ; e.g., "4027" for PostScript ; prtInterpreterDescription PrtLocalizedDescriptionStringTC ; - not supported in IPP/PWG SM pdl-desc = "pwg-pdl-desc" ; PDL description "=" quoted-string ; e.g., "Adobe PostScript..." ; prtInterpreterFeedAddressability Integer32, ; prtInterpreterXFeedAddressability Integer32, ; - see "printer-resolution" in IPP/PWG SM pdl-res = "pwg-pdl-resolution" ; PDL resolution "=" quoted-string ; cross-feed "," feed "," units ; cross-feed = 1*DIGIT ; feed = 1*DIGIT ; units = "dpi" / "dpcm" ; dots/inch or dots/centimeter ; e.g., "300,600,dpi" means ; 300 cross-feed X 600 feed DPI The following Interpreter attributes from the Printer MIB are omitted (for the reasons noted below): ; prtInterpreterLangFamily PrtInterpreterLangFamilyTC, ; - see "document-format" in IPP/PWG SM ; prtInterpreterVersion OCTET STRING, ; - redundant with prtInterpreterLangVersion ; prtInterpreterDefaultOrientation PrtPrintOrientationTC, ; - see "orientation-requested-default" in IPP/PWG SM ; prtInterpreterDefaultCharSetIn IANACharset, ; - see "charset-configured" in IPP/PWG SM ; prtInterpreterDefaultCharSetOut IANACharset, ; - not supported in IPP/PWG SM - only useful for softcopy output ; prtInterpreterTwoWay PrtInterpreterTwoWayTC ; - not supported in IPP/PWG SM - bidirectional print channel Cheers, - Ira McDonald, co-editor of Printer MIB v2 High North Inc ------------------------------------------------------------------------ [from "MIME Part Two: Media Types", RFC 2046] > Parameters are modifiers of the media subtype, and as such do not > fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their > defining media type or subtype or they may be optional. MIME > implementations must also ignore any parameters whose names they do > not recognize. ------------------------------------------------------------------------ [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] DIGIT = %x30-39 DQUOTE = %x22 ------------------------------------------------------------------------ [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] parameter = attribute "=" value attribute = token ; Matching of attributes ; is ALWAYS case-insensitive. value = token / quoted-string token = 1* tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values ------------------------------------------------------------------------ [from "Internet Message Format", RFC 2822] quoted-string = [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS] A quoted-string is treated as a unit. That is, quoted-string is identical to atom, semantically. Since a quoted-string is allowed to contain FWS, folding is permitted. Also note that since quoted-pair is allowed in a quoted-string, the quote and backslash characters may appear in a quoted-string so long as they appear as a quoted-pair. Semantically, neither the optional CFWS outside of the quote characters nor the quote characters themselves are part of the quoted-string; the quoted-string is what is contained between the two quote characters. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS/CFWS that appears within the quoted-string are semantically "invisible" and therefore not part of the quoted-string either. <...> CFWS = *([FWS] comment) (([FWS] comment) / FWS) FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space obs-FWS ctext = NO-WS-CTL / ; Non white space controls %d33-39 / ; The rest of the US-ASCII %d42-91 / ; characters not including "(", %d93-126 ; ")", or "\" ccontent = ctext / quoted-pair / comment comment = "(" *([FWS] ccontent) [FWS] ")" Throughout this standard, where FWS (the folding white space token) appears, it indicates a place where header folding, as discussed in section 2.2.3, may take place. Wherever header folding appears in a message (that is, a header field body containing a CRLF followed by any WSP), header unfolding (removal of the CRLF) is performed before any further lexical analysis is performed on that header field according to this standard. That is to say, any CRLF that appears in FWS is semantically "invisible." A comment is normally used in a structured field body to provide some human readable informational text. Since a comment is allowed to contain FWS, folding is permitted within the comment. Also note that since quoted-pair is allowed in a comment, the parentheses and backslash characters may appear in a comment so long as they appear as a quoted-pair. Semantically, the enclosing parentheses are not part of the comment; the comment is what is contained between the two parentheses. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS that appears within the comment are semantically "invisible" and therefore not part of the comment either. Runs of FWS, comment or CFWS that occur between lexical tokens in a structured field header are semantically interpreted as a single space character. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Fri Oct 11 14:26:04 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> Port for PSI - Static vs Dynamic issues Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDEB@mailsrvnt02.enet.sharplabs.com> Hi, Per my action item from Tuesday's PSI Telecon: PSI interfaces SHOULD have a static port (IANA-registered by vendor 'PWG') that is always the PSI listen port. PSI interfaces SHOULD NOT use dynamic ports (even by protocol agreement during PSI WSDL sessions), because: 1) Firewalls and NAT (Network Address Translator) systems assume that all protocols allowed to pass (traverse the domain boundary) use static IANA-registered ports (permission rules are normally based on a specific application protocol over a specific numbered port). Firewalls/NATs often implement ALGs (Application Layer Gateways) that enforce fine-grained permission rules. But the premise is always that the protocol on a given port is INVARIANT, and is determined by the port number (FTP proxies are fundamentally dangerous, for this reason). Dynamic ports completely defeat ALGs and firewall permissions (thus destroying the 'security perimeter' of the firewall). (There are a series of horrible exceptions in ALGs around HTTP port 80, due to other 'hidden' application protocols - PSI should not go there...) 2) Boundary routers (between enterprise and public networks) and core routers (within the Internet backbone) manage quality of service and packet delivery by 'aggregating' destinations (host/port pairs) for routing decisions. Dynamic ports completely defeat traffic 'aggregation' (because the router has no way to know that the alternate port traffic is associated with the original static port traffic). Routers also block all ports that are not specifically authorized to cross a domain boundary (in one direction or the other - not necessarily both) in their permission rules. Dynamic ports simply won't work in the general case. Hope this helps. Cheers, - Ira McDonald High North Inc From alan_berkema at hp.com Tue Oct 15 18:00:12 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: minutes 10/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD38C@xrose03.rose.hp.com> Lots of new actions folks, scan for your name! PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson *Peter Mierau Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 10/15/02 Agenda 1) To Do & Action Progress 2) Get Service Capabilities 3) Mandatory Optional Attributes 10/15/02 Minutes: See updated status and new discussion in line. 1) To Do & Action Progress Walked through the previous actions and covered the second agenda item as one of the actions. > 10/08/02 Minutes: > As a prelude Ira suggested that we move PSI defined schemas > into a seperate > directory. Dave mentioned that the spec already calls for > them to be ps/0.95 > so we will put them there. > > Action: Move them > Owner: Alan Status: Done > > 1) Review Harry's e-mail questions > The first question revolves around the use of DocumentTypeSupportQuery > and what it means if the TargetDeviceidentifier is NULL and > is this useful? > After much good discussion we decided that we can really do > this same thing > with > GetServiceAttributes as long as we explicitly provide an > example of how to > do it. > So DocumentTypeSupportQuery will be removed from the spec. > > Action: Write up some examples for GetServiceAttributes > Owner: Dave Status: Started Dave reviewed the examples he started with. GetServiceAttributes passes in requestedAttributes which is an XML instance document using that conforms to pwgAttr.xsd. snippet: 4 If an empty element is used, the response is all of the values that a service or the targetDevice supports. In the case of copies the response might be 1 throught 99. In the case of duplex, if this is a boolean ine the pwgAttr schema it might be True or False etc. If an element has a value than the printer or service indicates whether or not it can accomodate the specific value. What actually gets returned here? How about 4 - Means yes, and or Means No? More details on the examples revelaed in next rev. of the spec. In GetServiceAttributes is the targetDeviceIdentfier mandatory? Yes, though what if the Service knows about mant targets? Could someone respond with the discussion on why the answer is still Yes. I recall bits of the discussion though my note taking while hold the phone up to my ear was lacking. Next we looked for exactly what the "type" of element DocumentFormat is? Need to ask at SM meeting. Action: Discuss Document Format at SM meeting 10/17/02 Owner: Ira, Peter Z., Dave (I may not make this meeting) Status: Open Action: Write up some examples for a document type support query Owner: Dave Status: Open Action: Discuss Non ambiguous element names at SM meeting 10/17/02 Owner: Ira, Peter Z., Dave (I may not make this meeting) Status: Open Action: Have something to share on alternatives to returning a Schema in GetServiceAttributes by the next call. Owner: Bob Status: Open Action: Add an additional parameter for natural language & char set Owner: Dave Status: Open > > Harry's other question was around his new use case, which we agreed > was illustrated as Use model 5 in the requirements doc. The > question was > about > RegisterTargetDevice vs. AssociateTargetDevice. These are not > intended to > used > together and enable the different use models we have. > > Action: Write up a an Applicability statement for > AssociateTargetDevice > useful in firewall scenario etc. and is redundant otherwise. > Owner: Dave > Status: Open > > As we looked at use model 5 in the requirements doc, we noticed that > numbering on the > arrows were off. > > Action: Fix Numbers and post > Owner: Alan > Status: Open Action: Include trace diagram for use model 5 in the requirements doc Owner: Dave Status: Done, the example uses PSI in a dynamic nature Action: Include trace diagram for use model 5 in the requirements doc that shows pre configuration Owner: Dave Status: Open Discussion on how JobID works in above use model. Did we get an action out of this? Spec need some discussion on the way this should be handled? Action: Ask IANA for PSI port number Owner: Harry Status: Done, expect one in 30 days, likely not 3700 This is about as far as we got touched on the next one, though may want to discuss some more. Likely that we will not allow dynamic ports at any time. > > 2) Review the use of port 3700 > PSI has proposed asking IAN for a static port assignment we > are calling port > 3700 (IANA will probably dictate what actually get). > We debated this vs. just using a dynamic port. Ira had some > valid reasons > for > a static port in data aggregation scenarios with routers and gateways. > Decided that a static port will be used for QueryInterafceEndpoints. > Other discovery protocols will be used to get the hostname > and could return > a dynamic port. If a port is provide further queries will use > that dynamic > port. > Otherwise the static port will be used. > Doesn't this still open us up to the problems with dynamic ports? > > Action: Provide a brief write that explains why dynamic ports > have issues. > Also could get a brief write up on why overloading port 80 is > not a good > idea. > Owner: Ira > Status: Open > > 3) Review ToDo list > Dave walked us through the ToDo list see spec 0.90 an the > seem to be under control. > > 4) Call for action > We are currently at rev 0.90 and it's time to do your homework and to > take a close look at the spec. Harry set a good example with > his e-mail > questions. We will post intervening revs and a 0.94 candidate > 2 weeks before the F2F. Fixes from the F2F will be > incorporate into the > 0.95 candidate. > > Action: Review the spec. > Owner: All > Status: Open > > Thanks, > Alan From imcdonald at sharplabs.com Tue Oct 15 18:43:06 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> FW: LISA Forum Europe - November 4-7, 2002 in Heidelberg, German y Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDF7@mailsrvnt02.enet.sharplabs.com> Hi, FYI - a good conference on localization coming up 4-7 November. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Michael Anobile [mailto:lisa@lisa.org] Sent: Tuesday, October 15, 2002 2:55 PM To: imcdonald@sharplabs.com Subject: LISA Forum Europe - November 4-7, 2002 in Heidelberg, Germany * Agenda Update * THE LISA FORUM EUROPE Multilingual Content Authoring, Web-Services, Workflow and your Company's ROI 4-7 November 2002 * Heidelberg, Germany REGISTER http://www.lisa.org/events/2002europe/registration.html AGENDA http://www.lisa.org/events/2002europe/agenda.html PARTICIPANTS http://www.lisa.org/events/2002europe/participants_list.html WORKSHOPS http://www.lisa.org/events/2002europe/workshops/ ------------------------------------------------------------------------ LISA's 44th international conference and exhibition focuses on the optimization of technologies and standards in global web services. Through workshops, discussion groups, case studies and panels, you will learn from clients and end-users how standards in technology and business are providing unprecedented ROI and strategic advantage in today's increasingly competitive global marketplace. The program will feature: * Localizing Europe's air travel industry - An Amadeus Corporation Case Study * The business case for enterprise terminology - A Cisco Systems ROI presentation * Improving the ROI of the Authoring Environment and CMS - A Philip Morris Case Study * Clients and Developers measure customer satisfaction and MT's ROI * The Scope, Challenges and Oulook of Today's Translation Industry * OSCAR Survey Results: Analyzing content authoring and content localization * Standards in the GILT industry - what's working, what isn't, and why? * Special sessions: SME Profiles - Terminology - XML and Localization * LISA WORKSHOPS - Managing Localization Projects - Reducing Localization Costs with XML-based Technology - Evaluating Website Globalization Systems - L10n & I18n Testing - Internationalization: Preparing Software and Web Sites for Translation -- Workgroup leaders, speakers and invited guests include -- Acrolinx * Amadeus * Belga News Agency * Cisco Systems * Corporate Language Services * Comprendium Technologies * The Economist * Euro RSCG Wnek Gosper * GlobalSight * Herald Tribune International * Hewlett-Packard * i18N Inc * IAI Saarbrucken * IBM * Interverbum * IP Options * Isogen International * JD Edwards * LionBridge * Logitech * Logos Group * OASIS * Philip Morris International * RWS Group * SAP * SDL International * Software AG * STAR Group * Trados * USAF Research Lab * Venturi Partners * Wall Street Journal * Welocalize * WH&P * Xplanation * AUTOMATED WORKFLOW TOOLS AND LOCALIZATION SERVICES EXHIBITION The industry's leading technology developers for automated language processing systems, web-services, internationalization, translation and localization suppliers will demonstrate their products and services. LISA Forum Exhibitors SDL * Star Group * Trados * GlobalSight * ISOGEN * Xplanation * Comprendium * Telelingua * PASS Engineering * Connect Global Solutions * Translate.IT LISA Forum Europe Hosts and Member Sponsors SAP AG * WH&P - Wegwitz, Hoser & Partners * IBM * Hewlett Packard * SMP Marketing SarL * with the collaboration of * OASIS * Logos SpA * Donau University ================================================ - Notices - ================================================ LISA is the premier organization providing the mechanisms, services and networking for professionals interested in sharing information on the development of globalization and localization processes, tools, web services and international business models. Formed in 1990, today LISA members comprise 210 companies employing over 400,000 people in 65 countries. * We apologize if you received duplicates of this announcement. * If you would like to UNSUBSCRIBE please go to http://www.lisa.org/interact/announce.html ======================================================================== From imcdonald at sharplabs.com Mon Oct 21 16:21:05 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> FW: [Comments on PSI Requirements Spec] Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE02@mailsrvnt02.enet.sharplabs.com> Hi, I got these as personal mail from Anubhav Saxena. Forwarded for the experts to respond to... Cheers, - Ira McDonald High North Inc PS - Anubhav - To post to the list, send mail to 'ps@pwg.org'. -----Original Message----- From: Anubhav Saxena [mailto:anubhav.saxena@wipro.com] Sent: Monday, October 21, 2002 8:11 AM To: McDonald Ira Subject: RE: PS> FW: LISA Forum Europe - November 4-7, 2002 in Heidelberg, Germany Hi, I am Anubhav from Wipro, India. I am interested in your specification of PSI and I am subscribed to the mailing list as well. I am sorry if I am not supposed to post in message on PSI to you this way, however I assure you that once I know the protocol, I will stick to it. Following is my comment on the Requirement Specs of PSI. After reading the speicification document I see a note on page 17. This is actually an issue "How does the mobile device know that it can use Model 3 instead of needing use model 2". I see the following options: a) Model 2 is one, wherein the mobile device is 1. more capable than in model 3 (hence is probably costlier) b) Model 2 is one, wherein the print service is 1. capable of handling lesser channels of simultaneous communications than in model 3 2. for some reason not able to talk to printer Hence i feel that a mobile will need to take a decision to go in for 2/3 based on 1. Existing protocol support on the mobile itself 2. May be depending of the level of support provided by the print services 3. Current load on the mobile/print service However I am not sure about other issues that may be underlying this. Best Regards, Anubhav. -------------- next part -------------- **************************Disclaimer************************************************** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. **************************************************************************************** From dhall at hp.com Mon Oct 21 18:46:14 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> WEBEX info for 10/22 - #22188390 newpsi Message-ID: <77261E830267D411BD4D00902740AC250DB4BB14@xvan01.vcd.hp.com> Hey All.. Here is the WEBEX info for tomorrows meeting.. Dave ------------------------- 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: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Date: 10/22/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 22188390 Meeting Password: newpsi Teleconference: None. Agenda: Host: David Hall 1(360)212x4228 mailto:dhall@hp.com http://www.webex.com We've got to start meeting like this(TM) From dhall at hp.com Tue Oct 22 11:00:32 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> WEBEX info for 10/22 - #22188390 newpsi 404-348-2002 #556 05 Message-ID: <77261E830267D411BD4D00902740AC250DB4BB26@xvan01.vcd.hp.com> -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Monday, October 21, 2002 3:46 PM To: 'ps@pwg.org' Subject: PS> WEBEX info for 10/22 - #22188390 newpsi Hey All.. Here is the WEBEX info for tomorrows meeting.. Dave ------------------------- 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: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Date: 10/22/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 22188390 Meeting Password: newpsi Teleconference: None. Agenda: Host: David Hall 1(360)212x4228 mailto:dhall@hp.com http://www.webex.com We've got to start meeting like this(TM) From dhall at hp.com Tue Oct 22 13:55:45 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> PSI WSDL Interface Specification - To strongly type or not? Message-ID: <77261E830267D411BD4D00902740AC250DB4BB2B@xvan01.vcd.hp.com> Hey All... We currently have our parameters in PSI defined mostly as Strings, (jobProcessingAttributes for example), and are relying on the PWG SM schemas to provide the strong typing for the structure that the string contains.. One option is to strongly type the parameters as a complex type rather than a string... I hate to open up this can of worms, but... So far, I've heard of 3 different approaches for this... I've tried to summarize the advantages / disadvantages for each of the approaches. Please add your thoughts to the discussion.. Dave Strongly Typed WSDL Parameters Discussion One of the discussions that has been going on is around our WSDL definition of the PSI interfaces. There are three possibilities that have presented themselves: 1) The parameters (for example, jobProcessingAttributes) should be encoded as a string defined by a schema. Extensions are added within the XML document... 2) The parameters should be encoded as a strongly typed complex type, extensions are added as new, vendor defined elements. 3) The parameters should be encoded as a strongly typed complex type, where the last parameter is a string[] of structures. There are a number of advantages and dis-advantages to each which I have tried to capture here: 1) String parameters defined by schema: This is the current model for the PSI interface specification.. Advantages: * Easily (understandably) extensible at the element level by the application. * Clients can code up only the elements that they wish to deal with. * Allows name-space extensions to the interfaces through the QueryEndPoints mechanism. (ie, give me the JobControlInterface that understands the pwg common semantic model, and give me the JobControlInterface that understands the Digital Imaging semantic model.) * Interoperability between toolkits. The simple types are readily encoded / decoded by the toolkits. * A 1.0 server (think existing printer that talks 1.0 psi) would be able to interpret a 2.0 clients request. (Assuming the method signatures didn't change - it would simply ignore the elements it did not understand.) * A 2.0 server (Think new print service) could interpret a 1.0 client request (Assuming no new mandatory elements were added...) * A reference to the schema that defines the parameters can simply be made in the interface documentation. Disadvantages: * We need to hand generate the serializers / deserializers * Interoperability between devices is not enforced by a strongly typed interface. 2) Complex type parameters Advantages: * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. * Aligns with UPnP direction Disadvantages: * How to deal with the #any extensions in the toolkits? (Thought is that you inherit from the toolkit generated serializer, and add extensibility yourself) * Toolkit incompatibilities (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server, the burden would be on the client to also be able to talk the 1.0 interface specification. 3) Complex type parameters with string[] of structures element at the end Advantages: * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. Disadvantages: * Toolkit incompatibilities - structures within structures have been problematic in the past. (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server (assuming new elements are added to the base definition), the burden would be on the client to also be able to talk the 1.0 interface specification. From dhall at hp.com Tue Oct 22 14:05:26 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> PSI WSDL Interface Specification - To strongly type or no t? Message-ID: <77261E830267D411BD4D00902740AC250DB4BB2C@xvan01.vcd.hp.com> Ouch, we lost our formatting.. Here is an easier to read version: Hey All... We currently have our parameters in PSI defined mostly as Strings, (jobProcessingAttributes for example), and are relying on the PWG SM schemas to provide the strong typing for the structure that the string contains.. One option is to strongly type the parameters as a complex type rather than a string... I hate to open up this can of worms, but... So far, I've heard of 3 different approaches for this... I've tried to summarize the advantages / disadvantages for each of the approaches. Please add your thoughts to the discussion.. Dave Strongly Typed WSDL Parameters Discussion: One of the discussions that has been going on is around our WSDL definition of the PSI interfaces. There are three possibilities that have presented themselves: 1) The parameters (for example, jobProcessingAttributes) should be encoded as a string defined by a schema. Extensions are added within the XML document... 2) The parameters should be encoded as a strongly typed complex type, extensions are added as new, vendor defined elements. 3) The parameters should be encoded as a strongly typed complex type, where the last parameter is a string[] of structures. There are a number of advantages and dis-advantages to each which I have tried to capture here: 1) String parameters defined by schema: This is the current model for the PSI interface specification.. Advantages: ---------------------- * Easily (understandably) extensible at the element level by the application. * Clients can code up only the elements that they wish to deal with. * Allows name-space extensions to the interfaces through the QueryEndPoints mechanism. (ie, give me the JobControlInterface that understands the pwg common semantic model, and give me the JobControlInterface that understands the Digital Imaging semantic model.) * Interoperability between toolkits. The simple types are readily encoded / decoded by the toolkits. * A 1.0 server (think existing printer that talks 1.0 psi) would be able to interpret a 2.0 clients request. (Assuming the method signatures didn't change - it would simply ignore the elements it did not understand.) * A 2.0 server (Think new print service) could interpret a 1.0 client request (Assuming no new mandatory elements were added...) * A reference to the schema that defines the parameters can simply be made in the interface documentation. Disadvantages: ---------------------- * We need to hand generate the serializers / deserializers * Interoperability between devices is not enforced by a strongly typed interface. 2) Complex type parameters Advantages: ---------------------- * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. * Aligns with UPnP direction Disadvantages: ---------------------- * How to deal with the #any extensions in the toolkits? (Thought is that you inherit from the toolkit generated serializer, and add extensibility yourself) * Toolkit incompatibilities (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server, the burden would be on the client to also be able to talk the 1.0 interface specification. 3) Complex type parameters with string[] of structures element at the end Advantages: ---------------------- * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. Disadvantages: ---------------------- * Toolkit incompatibilities - structures within structures have been problematic in the past. (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server (assuming new elements are added to the base definition), the burden would be on the client to also be able to talk the 1.0 interface specification. From imcdonald at sharplabs.com Wed Oct 23 19:10:37 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> Revised PWG std MIME parameters ABNF (23 Oct 2002) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE09@mailsrvnt02.enet.sharplabs.com> Hi folks, Wednesday (23 October 2002) [Per my action item from the PWG PSI Telecon on 8 October 2002)] After talking with Tom Hastings about CIP4 JDF needs, some revised ABNF for IEEE/ISTO "IPP: PWG Standard MIME Parameters for Document Formats". All but one of these parameters were derived from the InterpreterTable defined in Printer MIB [RFC 1759]. Problem Statement: Registered MIME types (for example, used as values of the 'document-format' Job attribute in IPP/1.1 [RFC 2910, RFC 2911]) are imprecise. PWG PSI, CIP4 JDF, FSG PAPI, and FSG Job Ticket working groups have all identified a requirement for document format metadata. Rejected Solution: A data structure with the required metadata - works well within a given interface - but incompatible with 'cut-and-paste'. Proposed Solution: PWG standard optional MIME parameters - may be appended to _any_ registered MIME type to add the required metadata - compatible with 'cut-and-paste' across all applications (because the parameters are actually _part of_ the same MIME type "word" in the source text). Tom Hastings and I plan to write IEEE/ISTO 5100.10 "IPP: PWG Standard MIME Parameters for Document Formats". Watch for an announcement. Cheers, - Ira McDonald, co-editor of Printer MIB v2 High North Inc ------------------------------------------------------------------------ [PWG Standard MIME Parameters] In the printer industry, a document format MIME type is one of: (a) PDL - page description language (e.g., HTML or Adobe PostScript) (b) JCL - job control language (e.g., HP PJL) (c) JDL - job definition language (e.g., CIP4 JDF) (d) text - plaintext, richtext, HTML, SGML, XML, etc. Any PWG standard MIME parameter MAY be appended (unordered) to any document format, for example: application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (HP PCL 400x400 dpi) These PWG parameters are specified in Augmented Backus-Naur Form (ABNF, RFC 2234). Every element used in one of these PWG parameter ABNF productions is defined in an excerpt from ABNF (RFC 2234), MIME Part One (RFC 2045), or Internet Message Format (RFC 2822) at the end of this note. Each parameter name begins with a "pwg-" (namespace) prefix, to ensure that it is safely ignored by existing MIME-enabled software and systems. According to RFC 2045: (1) Parameters MUST be ignored when unrecognized; (2) Parameters MUST be ignored when comparing values of MIME types; (3) MIME type names MUST be treated as case-insensitive; (4) MIME parameter names MUST be treated as case-insensitive; (5) MIME parameter values MUST be treated as case-sensitive. document-format = type "/" subtype *[parameter] *[pwg-parameter] ; MIME type (plus optional parameters) pwg-parameter = ";" pl-level / pl-build / pl- prof / pl-desc / pl-res ; PWG standard parameter with a 'quoted-string' value Desc: Document format See: Section 5.1 in MIME Part One [RFC 2045] for ABNF definition of 'type', 'subtype', and 'parameter' See: Section 4.1.9 in IPP/1.1 Model and Semantics [RFC 2911] for definition of 'mimeMediaType' syntax pl-level = "pwg-lang-level" "=" quoted-string Desc: Language level (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterLangLevel' Examples: application/postscript;pwg-lang-level="2" (Adobe PostScript Level 2) application/vnd.hp-pcl;pwg-lang-level="5e" (HP PCL 5e) application/vnd.cip4-jdf+xml;pwg-lang-level="1.1" (CIP4 JDF 1.1) pl-prof = "pwg-lang-profile" "=" quoted-string Desc: Language profile (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' Examples: application/pdf;pwg-lang-profile="ISO-15930-3" (PDF-X3:2002) pl-build = "pwg-lang-build" "=" quoted-string Desc: This implementation's build ID (i.e., date code or version). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterLangVersion' Examples: application/vnd.hp-pcl;pwg-lang-build="20021025" (HP PCL) application/postscript;pwg-lang-build="AP4027.45..3" (Adobe PS) pdl-lang-res = "pwg-lang-resolution" "=" res-value res-value = DQUOTE res-xfeed "," res-feed "," res-units DQUOTE ; quoted string res-xfeed = 1*DIGIT ; cross-feed direction resolution res-feed = 1*DIGIT ; feed direction resolution res-units = "dpi" / "dpcm" ; resolution units of dots/inch or dots/centimeter Desc: Language resolution, expressed as "xfeed,feed,units". Human-readable information, suitable for client UI and debug. Also suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 4.2.12 in IPP/1.1 Model and Semantics [RFC 2911] for definition of 'printer-resolution' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterXFeedAddressability' and 'prtInterpreterFeedAddressability' See: Section 14 'The Marker Group' in Printer MIB [RFC 1759] for definition of 'prtMarkerAddressabilityUnit' Examples: application/postscript;pwg-lang-res="300,600,dpi" (300x600 dpi) application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (400x400 dpi) pl-desc = "pwg-lang-desc" "=" quoted-string Desc: Language description. Human-readable information, suitable for client UI and debug. Not suitable for use by automata. Note: This parameter should be _last_, since embedded whitespace may terminate 'cut-and-paste'. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterDescription' Examples: application/postscript;pwg-lang-desc="Adobe PostScript Level 2" application/vnd.hp-pcl;pwg-lang-desc="HP PCL Level 5e - 25 Oct 2002" The following Interpreter attributes from the Printer MIB are omitted (for the reasons noted below): 'prtInterpreterLangFamily' - language family (i.e., simple MIME type) - see 'document-format' in IPP/1.1 Model [RFC 2911] 'prtInterpreterVersion' - more free-form interpreter language version info - redundant with 'prtInterpreterLangVersion' in Printer MIB 'prtInterpreterDefaultOrientation' - default orientation (portrait or landscape) - see "orientation-requested-default" in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetIn' - default input charset (to avoid charset 'guessing') - see 'charset-configured' in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetOut' - default output charset, - only useful for softcopy output (i.e., 'print-to-file') - not supported in IPP/1.1 Model [RFC 2911] 'prtInterpreterTwoWay' - indicates support for bidirectional print channel - not supported in IPP/1.1 Model [RFC 2911] ------------------------------------------------------------------------ [from "MIME Part Two: Media Types", RFC 2046] > Parameters are modifiers of the media subtype, and as such do not > fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their > defining media type or subtype or they may be optional. MIME > implementations must also ignore any parameters whose names they do > not recognize. ------------------------------------------------------------------------ [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] DIGIT = %x30-39 DQUOTE = %x22 ------------------------------------------------------------------------ [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] parameter = attribute "=" value attribute = token ; Matching of attributes ; is ALWAYS case-insensitive. value = token / quoted-string token = 1* tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values ------------------------------------------------------------------------ [from "Internet Message Format", RFC 2822] quoted-string = [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS] A quoted-string is treated as a unit. That is, quoted-string is identical to atom, semantically. Since a quoted-string is allowed to contain FWS, folding is permitted. Also note that since quoted-pair is allowed in a quoted-string, the quote and backslash characters may appear in a quoted-string so long as they appear as a quoted-pair. Semantically, neither the optional CFWS outside of the quote characters nor the quote characters themselves are part of the quoted-string; the quoted-string is what is contained between the two quote characters. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS/CFWS that appears within the quoted-string are semantically "invisible" and therefore not part of the quoted-string either. <...> CFWS = *([FWS] comment) (([FWS] comment) / FWS) FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space obs-FWS ctext = NO-WS-CTL / ; Non white space controls %d33-39 / ; The rest of the US-ASCII %d42-91 / ; characters not including "(", %d93-126 ; ")", or "\" ccontent = ctext / quoted-pair / comment comment = "(" *([FWS] ccontent) [FWS] ")" Throughout this standard, where FWS (the folding white space token) appears, it indicates a place where header folding, as discussed in section 2.2.3, may take place. Wherever header folding appears in a message (that is, a header field body containing a CRLF followed by any WSP), header unfolding (removal of the CRLF) is performed before any further lexical analysis is performed on that header field according to this standard. That is to say, any CRLF that appears in FWS is semantically "invisible." A comment is normally used in a structured field body to provide some human readable informational text. Since a comment is allowed to contain FWS, folding is permitted within the comment. Also note that since quoted-pair is allowed in a comment, the parentheses and backslash characters may appear in a comment so long as they appear as a quoted-pair. Semantically, the enclosing parentheses are not part of the comment; the comment is what is contained between the two parentheses. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS that appears within the comment are semantically "invisible" and therefore not part of the comment either. Runs of FWS, comment or CFWS that occur between lexical tokens in a structured field header are semantically interpreted as a single space character. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Fri Oct 25 21:29:27 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE11@mailsrvnt02.enet.sharplabs.com> Hi folks, Friday (25 October 2002) [Per my action item from the PWG PSI Telecon on 8 October 2002)] Further revised ABNF for three PWG parameters for MIME document formats. Two of these parameters (pwg-lang-level and pwg-lang-desc) were derived from the InterpreterTable defined in Printer MIB [RFC 1759]. The other parameter (pwg-lang-profile) was suggested by Tom Hastings. Problem Statement: Registered MIME types (for example, used as values of the 'document-format' Job attribute in IPP/1.1 [RFC 2910, RFC 2911]) are imprecise. PWG PSI, CIP4 JDF, FSG PAPI, and FSG Job Ticket working groups have all identified a requirement for document format metadata. Rejected Solution: A data structure with the required metadata - works well within a given interface - but incompatible with 'cut-and-paste'. Proposed Solution: PWG standard optional MIME parameters - may be appended to _any_ registered MIME type to add the required metadata - compatible with 'cut-and-paste' across all applications (because the parameters are actually _part of_ the same MIME type "word" in the source text). Tom Hastings and I plan to write a proposal for "IPP: PWG Standard MIME Parameters for Document Formats". Watch for an announcement. Cheers, - Ira McDonald, co-editor of Printer MIB v2 High North Inc ------------------------------------------------------------------------ [PWG Standard MIME Parameters] In the printer industry, a document format MIME type is one of: (a) PDL - page description language (e.g., HTML or Adobe PostScript) (b) JCL - job control language (e.g., HP PJL) (c) JDL - job definition language (e.g., CIP4 JDF) (d) text - plaintext, richtext, HTML, SGML, XML, etc. Any PWG standard MIME parameter MAY be appended (unordered) to any document format, for example: application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (HP PCL 400x400 dpi) These PWG parameters are specified in Augmented Backus-Naur Form (ABNF, RFC 2234). Every element used in one of these PWG parameter ABNF productions is defined in an excerpt from ABNF (RFC 2234), MIME Part One (RFC 2045), or Internet Message Format (RFC 2822) at the end of this note. Each parameter name begins with a "pwg-" (namespace) prefix, to ensure that it is safely ignored by existing MIME-enabled software and systems. According to RFC 2045: (1) Parameters MUST be ignored when unrecognized; (2) Parameters MUST be ignored when comparing values of MIME types; (3) MIME type names MUST be treated as case-insensitive; (4) MIME parameter names MUST be treated as case-insensitive; (5) MIME parameter values MUST be treated as case-sensitive. document-format = type "/" subtype *[parameter] *[pwg-parameter] ; MIME type (plus optional parameters) pwg-parameter = ";" pl-level / pl-build / pl- prof / pl-desc / pl-res ; PWG standard parameter with a 'quoted-string' value Desc: Document format See: Section 5.1 in MIME Part One [RFC 2045] for ABNF definition of 'type', 'subtype', and 'parameter' See: Section 4.1.9 in IPP/1.1 Model and Semantics [RFC 2911] for definition of 'mimeMediaType' syntax pl-level = "pwg-lang-level" "=" quoted-string Desc: Language level and/or version (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterLangLevel' Examples: application/postscript;pwg-lang-level="2" (Adobe PostScript Level 2) application/vnd.hp-pcl;pwg-lang-level="5e" (HP PCL 5e) application/vnd.cip4-jdf+xml;pwg-lang-level="1.1" (CIP4 JDF 1.1) pl-prof = "pwg-lang-profile" "=" quoted-string Desc: Language profile or subset (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' Examples: application/pdf;pwg-lang-profile="PDF-X3" (ISO-15930-3:2002) pl-desc = "pwg-lang-desc" "=" quoted-string Desc: Language description. Human-readable information, suitable for client UI and debug. Not suitable for use by automata. Note: This parameter should be _last_, since embedded whitespace may terminate 'cut-and-paste'. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterDescription' Examples: application/postscript;pwg-lang-desc="Adobe PostScript Level 2" application/vnd.hp-pcl;pwg-lang-desc="HP PCL Level 5e - 25 Oct 2002" The following Interpreter attributes from the Printer MIB are omitted (for the reasons noted below): 'prtInterpreterLangFamily' - language family (i.e., simple MIME type) - see 'document-format' in IPP/1.1 Model [RFC 2911] 'prtInterpreterLangVersion' - language version - ambiguous in actual usage with 'prtInterpreterLangLevel' 'prtInterpreterVersion' - interpreter implementation build version info - not applicable for MIME types 'prtInterpreterDefaultOrientation' - default orientation (portrait or landscape) - see "orientation-requested-default" in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetIn' - default input charset (to avoid charset 'guessing') - see 'charset-configured' in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetOut' - default output charset, - only useful for softcopy output (i.e., 'print-to-file') - not supported in IPP/1.1 Model [RFC 2911] 'prtInterpreterTwoWay' - indicates support for bidirectional print channel - not supported in IPP/1.1 Model [RFC 2911] ------------------------------------------------------------------------ [from "MIME Part Two: Media Types", RFC 2046] > Parameters are modifiers of the media subtype, and as such do not > fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their > defining media type or subtype or they may be optional. MIME > implementations must also ignore any parameters whose names they do > not recognize. ------------------------------------------------------------------------ [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] DIGIT = %x30-39 DQUOTE = %x22 ------------------------------------------------------------------------ [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] parameter = attribute "=" value attribute = token ; Matching of attributes ; is ALWAYS case-insensitive. value = token / quoted-string token = 1* tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values ------------------------------------------------------------------------ [from "Internet Message Format", RFC 2822] quoted-string = [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS] A quoted-string is treated as a unit. That is, quoted-string is identical to atom, semantically. Since a quoted-string is allowed to contain FWS, folding is permitted. Also note that since quoted-pair is allowed in a quoted-string, the quote and backslash characters may appear in a quoted-string so long as they appear as a quoted-pair. Semantically, neither the optional CFWS outside of the quote characters nor the quote characters themselves are part of the quoted-string; the quoted-string is what is contained between the two quote characters. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS/CFWS that appears within the quoted-string are semantically "invisible" and therefore not part of the quoted-string either. <...> CFWS = *([FWS] comment) (([FWS] comment) / FWS) FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space obs-FWS ctext = NO-WS-CTL / ; Non white space controls %d33-39 / ; The rest of the US-ASCII %d42-91 / ; characters not including "(", %d93-126 ; ")", or "\" ccontent = ctext / quoted-pair / comment comment = "(" *([FWS] ccontent) [FWS] ")" Throughout this standard, where FWS (the folding white space token) appears, it indicates a place where header folding, as discussed in section 2.2.3, may take place. Wherever header folding appears in a message (that is, a header field body containing a CRLF followed by any WSP), header unfolding (removal of the CRLF) is performed before any further lexical analysis is performed on that header field according to this standard. That is to say, any CRLF that appears in FWS is semantically "invisible." A comment is normally used in a structured field body to provide some human readable informational text. Since a comment is allowed to contain FWS, folding is permitted within the comment. Also note that since quoted-pair is allowed in a comment, the parentheses and backslash characters may appear in a comment so long as they appear as a quoted-pair. Semantically, the enclosing parentheses are not part of the comment; the comment is what is contained between the two parentheses. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS that appears within the comment are semantically "invisible" and therefore not part of the comment either. Runs of FWS, comment or CFWS that occur between lexical tokens in a structured field header are semantically interpreted as a single space character. ------------------------------------------------------------------------ From alan.berkema at hp.com Wed Oct 30 21:11:14 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: Docs for F2F Message-ID: <499DC368E25AD411B3F100902740AD650E6AD3F3@xrose03.rose.hp.com> Hi all, I have been having ftp problems, looks like it is on our end. Firewall? Anyway, the docs I tried to post last Thursday are finally out there, thanks to Harry. psi-spec92.doc == psi-spec92.pdf == psi-spec-latest.pdf Also, have a look at ps/samplecode/92 F2F agenda will be out tomorrow. Thanks, Alan From dhall at hp.com Thu Oct 31 02:03:32 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: Docs for F2F Message-ID: <77261E830267D411BD4D00902740AC250DB4BC66@xvan01.vcd.hp.com> The latest sample code can be found at: ftp://ftp.pwg.org/pub/pwg/ps/samplecode/Code92b/psi.zip Also, we've updated the ps home page: http://www.pwg.org/ps/index.html If anyone has additional suggestions for links / documents we need to publish, let us know.. Dave and Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Wednesday, October 30, 2002 6:11 PM To: 'a PSI pwg.org' Subject: PS> [PSI]: Docs for F2F Hi all, I have been having ftp problems, looks like it is on our end. Firewall? Anyway, the docs I tried to post last Thursday are finally out there, thanks to Harry. psi-spec92.doc == psi-spec92.pdf == psi-spec-latest.pdf Also, have a look at ps/samplecode/92 F2F agenda will be out tomorrow. Thanks, Alan From alan.berkema at hp.com Thu Oct 31 17:42:11 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: F2F Agenda Message-ID: <499DC368E25AD411B3F100902740AD650E6AD3FD@xrose03.rose.hp.com> Hi All, Please have a look at the attached agenda proposal. Any input? Thanks, Alan <> -------------- next part -------------- A non-text attachment was scrubbed... Name: agenda_110602.pdf Type: application/octet-stream Size: 116029 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021031/50b2857e/agenda_110602.obj From alan.berkema at hp.com Thu Oct 31 19:01:59 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: Slides from 10/29 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD400@xrose03.rose.hp.com> Hey All, An enhanced version of the slides I showed at the last telecon are available on the web site under: QueryInterfaceEndPoints Examples later, Alan From imcdonald at sharplabs.com Fri Nov 1 13:48:04 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE18@mailsrvnt02.enet.sharplabs.com> Hi Bob, Apologies for my slow reply. I was off the map travelling most of this week. My comments are inline below in your note. Cheers, - Ira McDonald High North Inc -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) [mailto:bobt@hp.com] Sent: Monday, October 28, 2002 7:58 PM To: 'McDonald, Ira'; 'ps@pwg.org'; 'hastings@cp10.es.xerox.com' Cc: SIMPSON,SHELL (HP-Boise,ex1) Subject: RE: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Hi Ira, Tom, all, Some comments/questions: - We understand the rational for the "cut and paste" vs. "structure" objectives, but should PSI have a structure for this? As we'll mention in a bit, there is probably more information we need to capture here, and continual extension of the MIME string doesn't seem to scale well/reliably with too many parameters. For reference (I think we've already shared this), attached is a simple xsd we're using for this. Agreed - the continual extension of the MIME type string does _not_ work very well. - The proposal explicitly states in several places "Human-readable information, suitable for client UI and debug. Not suitable for use by automata". Given that we do need to use content type information for automata, is it assumed that something else (e.g., a "structure" definition) must be defined as well? The proposal _notes_ the current definition of the proposed information in Printer MIB v1 (RFC 1759, March 1995) as "human-readable". But PSI shouldn't solve this problem without a clear IPP binding of whatever the "solution" is. (I can now almost hear myself suggesting an IPP binding based on "document-format-col (1setOf collection)" - yuck! - an awful solution for IPP). A good long-term solution for IPP would be to use the proposed generic Resource object and (just as we've proposed for "media" as a _much_ better solution than the "media-col" attributes) define a Document Format type of Resource. - To be deterministic about what the format actually is (or what formats are supported by a service), we think there are a few additional things necessary: language -- Human language for which the data format is defined. Some word processing applications defined different data formats for different locales--even though the version for the data format remained the same (e.g. early versions of MS Word). Here, we should use IETF RFC 3066 conformant "language-tags". platform -- Operating system for which the data format is defined. Some applications (e.g. MS Word) defined different data formats for different operating systems (e.g. Windows and the Mac) even though the version for the data format remained the same. Here, we're in serious trouble. The (now languishing) IPP device driver installation spec needed a better list of operating systems than the current IANA registry, but creation of such a registry by the PWG is unacceptable to most people. model -- Target device for which the data was created. PDLs (such as Postscript or PCL) can include printer model specific information. (Each printer model has its own specific language specification.) Can you suggest a deterministic, portable way to enumerate printer models that interoperates across software and hardware vendors? Again, a PWG registry is an unacceptable (and unworkable) solution, I believe. container -- Describes embedded content types, such as those embedded within a ZIP file. In the XML domain (not the MIME multipart domain), the best way to describe embedded content types that I know of is the "Manifest" that's an optional part of an XML Digital Signature (RFC 3275, March 2002). Again, needs major work for some kind of IPP binding. - I noticed that pdl-lang-res is missing from the revised proposal. We actually think this is the right answer (i.e., it does not belong here), but wanted to make sure this was intentional and not accidental. Tom Hastings convinced me to remove pwg-lang-res (resolution), because it "opened the barn door to inappropriate parameters". I will note that my own experience at Xerox and Sharp has been that client apps folks do read the Interpreter Table in the Printer MIB to determine the MAXIMUM resolution supported by a given PDL interpreter. No point in sending images at higher resolution, for example. thanks, bt --------------------------------------------------- Bob Taylor Senior Architect IPG Strategic Technology Development Hewlett-Packard Co. mailto:robertt@vcd.hp.com phone: 360.212.2625/T212.2625 fax: 208.730-5111 --------------------------------------------------- > -----Original Message----- > From: McDonald, Ira [mailto:imcdonald@sharplabs.com] > Sent: Friday, October 25, 2002 6:29 PM > To: McDonald, Ira; 'ps@pwg.org'; 'hastings@cp10.es.xerox.com' > Subject: PS> Further Revised PWG std MIME parameters ABNF (25 > Oct 2002) > > > Hi folks, Friday (25 > October 2002) > > [Per my action item from the PWG PSI Telecon on 8 October 2002)] > > Further revised ABNF for three PWG parameters for MIME > document formats. > > Two of these parameters (pwg-lang-level and pwg-lang-desc) > were derived > from the InterpreterTable defined in Printer MIB [RFC 1759]. > The other > parameter (pwg-lang-profile) was suggested by Tom Hastings. > > > Problem Statement: Registered MIME types (for example, used as values > of the 'document-format' Job attribute in IPP/1.1 [RFC 2910, > RFC 2911]) > are imprecise. PWG PSI, CIP4 JDF, FSG PAPI, and FSG Job > Ticket working > groups have all identified a requirement for document format metadata. > > > Rejected Solution: A data structure with the required > metadata - works > well within a given interface - but incompatible with 'cut-and-paste'. > > > Proposed Solution: PWG standard optional MIME parameters - may be > appended to _any_ registered MIME type to add the required metadata - > compatible with 'cut-and-paste' across all applications (because the > parameters are actually _part of_ the same MIME type "word" in the > source text). > > > Tom Hastings and I plan to write a proposal for "IPP: PWG > Standard MIME > Parameters for Document Formats". Watch for an announcement. > > Cheers, > - Ira McDonald, co-editor of Printer MIB v2 > High North Inc > > -------------------------------------------------------------- > ---------- > [PWG Standard MIME Parameters] > > > In the printer industry, a document format MIME type is one of: > > (a) PDL - page description language (e.g., HTML or Adobe PostScript) > (b) JCL - job control language (e.g., HP PJL) > (c) JDL - job definition language (e.g., CIP4 JDF) > (d) text - plaintext, richtext, HTML, SGML, XML, etc. > > Any PWG standard MIME parameter MAY be appended (unordered) to any > document format, for example: > > application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (HP PCL > 400x400 dpi) > > These PWG parameters are specified in Augmented Backus-Naur > Form (ABNF, > RFC 2234). Every element used in one of these PWG parameter ABNF > productions is defined in an excerpt from ABNF (RFC 2234), > MIME Part One > (RFC 2045), or Internet Message Format (RFC 2822) at the end of this > note. > > Each parameter name begins with a "pwg-" (namespace) prefix, to ensure > that it is safely ignored by existing MIME-enabled software > and systems. > > According to RFC 2045: > > (1) Parameters MUST be ignored when unrecognized; > (2) Parameters MUST be ignored when comparing values of MIME types; > (3) MIME type names MUST be treated as case-insensitive; > (4) MIME parameter names MUST be treated as case-insensitive; > (5) MIME parameter values MUST be treated as case-sensitive. > > > > > > document-format = type "/" subtype *[parameter] *[pwg-parameter] > ; MIME type (plus optional parameters) > > pwg-parameter = ";" pl-level / pl-build / pl- prof / > pl-desc / pl-res > ; PWG standard parameter with a 'quoted-string' value > > Desc: Document format > > See: Section 5.1 in MIME Part One [RFC 2045] > for ABNF definition of 'type', 'subtype', and 'parameter' > See: Section 4.1.9 in IPP/1.1 Model and Semantics [RFC 2911] > for definition of 'mimeMediaType' syntax > > > > > > pl-level = "pwg-lang-level" "=" quoted-string > > Desc: Language level and/or version (not applicable for > 'text/plain'). > Human-readable information, suitable for client UI and debug. > Not suitable for use by automata. > > See: Section 3.2.5 of Internet Message Formats [RFC 2822] > for ABNF definition of 'quoted-string' > See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] > for definition of 'prtInterpreterLangLevel' > > Examples: > > application/postscript;pwg-lang-level="2" (Adobe PostScript Level 2) > > application/vnd.hp-pcl;pwg-lang-level="5e" (HP PCL 5e) > > application/vnd.cip4-jdf+xml;pwg-lang-level="1.1" (CIP4 JDF 1.1) > > > > > > pl-prof = "pwg-lang-profile" "=" quoted-string > > Desc: Language profile or subset (not applicable for 'text/plain'). > Human-readable information, suitable for client UI and debug. > Not suitable for use by automata. > > See: Section 3.2.5 of Internet Message Formats [RFC 2822] > for ABNF definition of 'quoted-string' > > Examples: > > application/pdf;pwg-lang-profile="PDF-X3" (ISO-15930-3:2002) > > > > > pl-desc = "pwg-lang-desc" "=" quoted-string > > Desc: Language description. > Human-readable information, suitable for client UI and debug. > Not suitable for use by automata. > > Note: This parameter should be _last_, since embedded whitespace may > terminate 'cut-and-paste'. > > See: Section 3.2.5 of Internet Message Formats [RFC 2822] > for ABNF definition of 'quoted-string' > See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] > for definition of 'prtInterpreterDescription' > > Examples: > > application/postscript;pwg-lang-desc="Adobe PostScript Level 2" > > application/vnd.hp-pcl;pwg-lang-desc="HP PCL Level 5e - 25 Oct 2002" > > > > > The following Interpreter attributes from the Printer MIB are omitted > (for the reasons noted below): > > 'prtInterpreterLangFamily' > - language family (i.e., simple MIME type) > - see 'document-format' in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterLangVersion' > - language version > - ambiguous in actual usage with 'prtInterpreterLangLevel' > > 'prtInterpreterVersion' > - interpreter implementation build version info > - not applicable for MIME types > > 'prtInterpreterDefaultOrientation' > - default orientation (portrait or landscape) > - see "orientation-requested-default" in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterDefaultCharSetIn' > - default input charset (to avoid charset 'guessing') > - see 'charset-configured' in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterDefaultCharSetOut' > - default output charset, > - only useful for softcopy output (i.e., 'print-to-file') > - not supported in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterTwoWay' > - indicates support for bidirectional print channel > - not supported in IPP/1.1 Model [RFC 2911] > > > -------------------------------------------------------------- > ---------- > [from "MIME Part Two: Media Types", RFC 2046] > > > Parameters are modifiers of the media subtype, and as such do not > > fundamentally affect the nature of the content. The set of > meaningful parameters depends on the media type and subtype. Most > parameters are associated with a single specific subtype. > However, a > given top-level media type may define parameters which are > applicable > to any subtype of that type. Parameters may be required by their > > defining media type or subtype or they may be optional. MIME > > implementations must also ignore any parameters whose names they do > > not recognize. > > > -------------------------------------------------------------- > ---------- > [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] > > DIGIT = %x30-39 > > DQUOTE = %x22 > > > -------------------------------------------------------------- > ---------- > [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] > > parameter = attribute "=" value > > attribute = token > ; Matching of attributes > ; is ALWAYS case-insensitive. > > value = token / quoted-string > > token = 1* or tspecials> > > tspecials = "(" / ")" / "<" / ">" / "@" / > "," / ";" / ":" / "\" / <"> > "/" / "[" / "]" / "?" / "=" > ; Must be in quoted-string, > ; to use within parameter values > > > -------------------------------------------------------------- > ---------- > [from "Internet Message Format", RFC 2822] > > quoted-string = [CFWS] > DQUOTE *([FWS] qcontent) [FWS] DQUOTE > [CFWS] > > A quoted-string is treated as a unit. That is, quoted-string is > identical to atom, semantically. Since a quoted-string is > allowed to > contain FWS, folding is permitted. Also note that since > quoted-pair > is allowed in a quoted-string, the quote and backslash > characters may > appear in a quoted-string so long as they appear as a quoted-pair. > > Semantically, neither the optional CFWS outside of the quote > characters nor the quote characters themselves are part of the > quoted-string; the quoted-string is what is contained > between the two > quote characters. As stated earlier, the "\" in any > quoted-pair and > the CRLF in any FWS/CFWS that appears within the quoted-string are > semantically "invisible" and therefore not part of the > quoted-string > either. > > <...> > > CFWS = *([FWS] comment) (([FWS] comment) / FWS) > > FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space > obs-FWS > > ctext = NO-WS-CTL / ; Non white space controls > > %d33-39 / ; The rest of the US-ASCII > %d42-91 / ; characters not > including "(", > %d93-126 ; ")", or "\" > > ccontent = ctext / quoted-pair / comment > > comment = "(" *([FWS] ccontent) [FWS] ")" > > Throughout this standard, where FWS (the folding white space token) > appears, it indicates a place where header folding, as discussed in > section 2.2.3, may take place. Wherever header folding > appears in a > message (that is, a header field body containing a CRLF followed by > any WSP), header unfolding (removal of the CRLF) is > performed before > any further lexical analysis is performed on that header field > according to this standard. That is to say, any CRLF that > appears in > FWS is semantically "invisible." > > A comment is normally used in a structured field body to > provide some > human readable informational text. Since a comment is allowed to > contain FWS, folding is permitted within the comment. > Also note that > since quoted-pair is allowed in a comment, the parentheses and > backslash characters may appear in a comment so long as they appear > as a quoted-pair. Semantically, the enclosing parentheses are not > part of the comment; the comment is what is contained > between the two > parentheses. As stated earlier, the "\" in any quoted-pair and the > CRLF in any FWS that appears within the comment are semantically > "invisible" and therefore not part of the comment either. > > Runs of FWS, comment or CFWS that occur between lexical tokens in a > structured field header are semantically interpreted as a single > space character. > > -------------------------------------------------------------- > ---------- > From imcdonald at sharplabs.com Mon Nov 4 13:58:35 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE1D@mailsrvnt02.enet.sharplabs.com> Hi Bob, See some replies inline below. Thanks very much for thinking hard about these issues. High level comment - I'm ready to throw in the towel and declare that for machine-readable and machine-actionable needs the addition of parameters to MIME types is a non-solution. So I think we're back to a structure/object for PSI, SM, IPP, etc. Cheers, - Ira McDonald High North Inc -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) [mailto:bobt@hp.com] Sent: Monday, November 04, 2002 1:19 AM To: McDonald, Ira; 'ps@pwg.org'; 'hastings@cp10.es.xerox.com' Cc: SIMPSON,SHELL (HP-Boise,ex1) Subject: RE: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Hi Ira, See a couple of specific comments below - with large chunks trimmed since I agreed and wanted to make it more readable. bt > -----Original Message----- > From: McDonald, Ira [mailto:imcdonald@sharplabs.com] > > - The proposal explicitly states in several places "Human-readable > information, > suitable for client UI and debug. Not suitable for use by automata". > Given > that we do need to use content type information for automata, is it > assumed > that something else (e.g., a "structure" definition) must > be defined as > well? > > > The proposal _notes_ the current definition of the proposed > information > in Printer MIB v1 (RFC 1759, March 1995) as "human-readable". > > But PSI shouldn't solve this problem without a clear IPP binding of > whatever the "solution" is. > > (I can now almost hear myself suggesting an IPP binding based on > "document-format-col (1setOf collection)" - yuck! - an awful > solution for IPP). > > A good long-term solution for IPP would be to use the > proposed generic > Resource object and (just as we've proposed for "media" as a _much_ > better solution than the "media-col" attributes) define a > Document Format > type of Resource. > Agreed - but our (HP) interest is primarily in PSI & SM, where we can use the structural flexibility of XML. I don't have a problem with defining an IPP structure for this, but we need to define something quickly for PSI and SM, so I'd advocate maybe doing these first on this one. I agree that we need some solution very quickly for PSI and SMI. But I started on this problem because it was identified for FSG PAPI and FSG Job Ticket (both of which HP is certainly interested in, too). I'm OK with pursuing an XML structure solution for PSI and SM first. But I'd like to aggressively work on how to pass this in either IPP Printer object attributes or IPP (new Resource) object attributes, so that Free Software Group Open Printing isn't at a disadvantage. > > model -- Target device for which the data was created. > PDLs (such as > Postscript or PCL) can include printer model specific > information. > (Each > printer model has its own specific language specification.) > > > Can you suggest a deterministic, portable way to enumerate > printer models > that interoperates across software and hardware vendors? Again, a PWG > registry is an unacceptable (and unworkable) solution, I believe. > Could we just spec that standard IEEE1284 DeviceIDs be used? I believe these are already deterministic, and also can declare "compatible" models to provide hints on what other models may understand a datastream. Yes, IEEE1284 DeviceID is probably a good solution for device model. And it's a stable registry that we (PWG) don't have to maintain. From imcdonald at sharplabs.com Mon Nov 4 14:03:40 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> FW: DHCP Option for SNMP Notifications Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE1E@mailsrvnt02.enet.sharplabs.com> Hi folks, Mark Bakke (Cisco) has been doing some good work to define a new DHCP boot option that tells a device where to send SNMP traps (i.e., addresses of SNMP Notification Receivers, network management stations). Definitely applicable for printer devices. Cheers, - Ira McDonald High North Inc PS - Mark Bakke co-wrote the SLP MIB with me last year. -----Original Message----- From: Mark Bakke [mailto:mbakke@cisco.com] Sent: Monday, November 04, 2002 10:17 AM To: dhcwg@ietf.org; snmpv3@lists.tislabs.com; mibs@ops.ietf.org Subject: DHCP Option for SNMP Notifications Hi- I've submitted a new DHCP Option for SNMP Notifications draft, after attempting to incorporate the feedback I received on the first one. Until it pops out of the I-D queue, it's available at: ftp://ftpeng.cisco.com/mbakke/ips/dhcp/draft-bakke-dhc-snmp-trap-01.txt Thanks to everyone who contributed and helped me get the SNMP security stuff figured out. I just realized that I forgot to update some of the acknowledgements; Randy Presuhn and David Perkins also helped with this. I also need to spend more time on the references; I realized that these sections are still not up-to-date. Comments? Thanks, -- Mark A. Bakke Cisco Systems mbakke@cisco.com 763.398.1054 From imcdonald at sharplabs.com Wed Nov 6 17:57:57 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: Line length of ornamented MIME type names Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE22@mailsrvnt02.enet.sharplabs.com> Hi Harry, As of my note yesterday to Bob Taylor (HP), I've _abandoned_ my idea for the PWG standard MIME parameters. A few Printer MIB-derived text parameters are feasible (although line length may well become a problem in some cut-and-paste interfaces). But _none_ of the interoperable machine-readable parameters that HP and others have asked for are practical. I believe we should leave unchanged the simple (unornamented) MIME types currently deployed in IPP/1.x implementations. For the PWG SM and PWG PSI interfaces, we should define an XML structured element (such as the suggested "document-type") with as many new details as we need. For the IPP binding, we need to figure out the best solution. I vastly prefer an IPP Resource-based solution, but we _could_ kludge these in with something like "document-type-col" (a collection). Adding a new ordered IPP Printer attribute that is directly parallel to the "document-format-supported" is possible, but a TERRIBLE idea. Cheers, - Ira McDonald High North Inc PS - I copied PSI and IPP lists on this reply to make sure others see my answer to your question promptly. -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Wednesday, November 06, 2002 12:37 PM To: imcdonald@sharplabs.com Subject: In the MIME type definitions standard where you are embellishing... for better description of document types... is there any thought given to resulting length and how this works (or not) with various protocols (ex. SNMP, SMTP, etc.). Question came up at f2f today. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- From alan.berkema at hp.com Thu Nov 7 18:21:21 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> [PSI]: Call for Intellectual Property Message-ID: <499DC368E25AD411B3F100902740AD65149EF264@xrose03.rose.hp.com> > This is a call for Patents that are relevant to the IEEE ISTO PWG PSI > specification. > I'm not sure if the ISTO has their own procedures. To me it would seem > safe to use > the policy and procedures of the IEEE since the ISTO is an affiliate. > The IEEE call, is for essential Patents, though, it may not always be > clear what is > essential. > > If you believe you have IP in the PSI space you are encouraged to file an > LOA, > see below. > > If you know of a company that has IP in this space, that does participate > in the > working group, please let me know and I will send them the appropriate > letter asking > them to file an LOA. > > Also, if there is a more appropriate procedure, please let me know. > > Thanks, > Alan > > -------------------------------------------------------------------------- > --------------------------------------- > From: don@lexmark.com > Sent: Tuesday, December 18, 2001 5:46 AM > To: stds-msc@majordomo.ieee.org > Subject: PatCom Guide and LoA Form - now available > > Attached is a note with the latest information about Patents and the IEEE. > Working group chairs should read, understand and apply the PatCom Guide. > > ********************************************** > * Don Wright don@lexmark.com * > * * > * Chair, IEEE MSC * > * Member, IEEE SA Board of Governors * > * Member, IEEE-ISTO Board of Directors * > * * > * Director, Alliances & Standards * > * Lexmark International * > * 740 New Circle Rd * > * Lexington, Ky 40550 * > * 859-825-4808 (phone) 603-963-8352 (fax) * > ********************************************** > > ---------------------- Forwarded by Don Wright/Lex/Lexmark on 12/18/2001 > 08:44 > AM --------------------------- > > d.ringle%ieee.org@interlock.lexmark.com on 12/17/2001 02:38:49 PM > > To: std-liaison-reps@ieee.org > cc: (bcc: Don Wright/Lex/Lexmark) > Subject: PatCom Guide and LoA Form - now available > > All, > > There are some new Patent Committee documents available for your use. > > 1. Patent Letter of Assurance (LoA) Form > > This form can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link on the right-hand side for Entire Package > (http://standards.ieee.org/board/pat/july_2001.zip). In the package, > there > is an LoA form. > > This LoA form is the preferred format for letters of assurance. All > responses received on the Form can be easily reviewed (and accepted) by > PatCom. As of 1 January 2002, it is required that this be the only form > sent to potential patent holders when seeking a letter of assurance. > > {If the patent holder does not complete the form and, instead, sends in a > free-form letter, PatCom will take appropriate actions.} > > 2. PatCom Guide - "Understanding Patent Issues During IEEE Standards > Development" > > This guide can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link for 'Understanding Patent Issues During IEEE Standards > Development' (http://standards.ieee.org/board/pat/guide.html). > > > If you have any questions, let me know. > > Regards, > ************************************************************************** > ******** > > > David L. Ringle > PatCom Administrator > IEEE Standards Activities Dept. > > 445 Hoes Lane PH: +1 732 562 3806 > PO Box 1331 FX: +1 732 562 > 1571 > Piscataway, NJ 08855-1331 d.ringle@ieee.org > ************************************************************************** > ******** From alan.berkema at hp.com Tue Nov 12 12:08:28 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> RE: No meeting? Message-ID: <499DC368E25AD411B3F100902740AD650E6AD422@xrose03.rose.hp.com> Sorry all, I snoozed, took Monday off and got out of sync. Think we are OK since we just got back from the F2F and need some time to re-group anyway. We'll do it next week, I'll send out the meeting info later. Alan -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, November 12, 2002 8:13 AM To: 'Harry Lewis'; alan_berkema@hp.com; HALL,DAVID (HP-Vancouver,ex1) Subject: RE: No meeting? Not that I can tell! I haven't heard from Alan.. D -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Tuesday, November 12, 2002 8:05 AM To: alan_berkema@hp.com; dhall@hp.com Subject: No meeting? I wasn't able to get the webx or phone nums that I have for the call to work this morning. I'm guessing it's too soon after the f2f and we decided not to have a call. Looking forward to updated docs. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021112/20a10e73/attachment.html From dhall at hp.com Tue Nov 12 12:33:01 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:07 2009 Subject: PS> New specification document available Message-ID: <77261E830267D411BD4D00902740AC250DB4BEE5@xvan01.vcd.hp.com> psi-spec93b.doc = psi-spec-latest.pdf - latest clean version Thanks, Alan and Dave From alan.berkema at hp.com Thu Nov 14 11:32:53 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 11/19/02 - New Number Message-ID: <499DC368E25AD411B3F100902740AD650E6AD444@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday November 19 (USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Look at the WSDL with the strong typing mechanism discussed at the F2F 2) Discovery - What do we need to enable each protocol Assign action owners WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 11/19/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Thu Nov 14 16:31:59 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> Updated Number [PSI]: next call 11/19/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD455@xrose03.rose.hp.com> The tool missed my first date: Here is the number for the 19th 650-690-9362(T348-9362) ID 55605 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, November 14, 2002 8:33 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: next call 11/19/02 - New Number Teleconference details: Date: Tuesdays, Next: Tuesday November 19 (USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Look at the WSDL with the strong typing mechanism discussed at the F2F 2) Discovery - What do we need to enable each protocol Assign action owners WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 11/19/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Mon Nov 18 19:13:17 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: F2F Minutes 11/06/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD47B@xrose03.rose.hp.com> proposed minutes attached, Thanks to Jerry for capturing the meeting, Alan <> -------------- next part -------------- A non-text attachment was scrubbed... Name: psi_minutes_110602.pdf Type: application/octet-stream Size: 96747 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021118/dc396379/psi_minutes_110602.obj From alan.berkema at hp.com Wed Nov 20 10:19:23 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 12/03/02 - NO Call 11/26 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD489@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday November 19 (USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Look at the WSDL with the strong typing mechanism discussed at the F2F 2) Discovery - What do we need to enable each protocol Assign action owners WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 11/19/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From dhall at hp.com Wed Nov 27 09:35:00 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> Updated Documents Message-ID: <77261E830267D411BD4D00902740AC250DB4C051@xvan01.vcd.hp.com> Hey All! We've updated the specification document to 94a: ftp://ftp.pwg.org/pub/pwg/ps/psi-spec94a.doc This version of the document has made a stab at getting the mandatory / optional definitions into each of the methods comments section. For the AddDocumentByReference, this was modified to return an array of DocumentURI's, as a reference can refer to potentially more than one document. (For example, an email reference...) Also, we have successfully updated the sample code to utilize the strongly typed interfaces, and have made some soap calls with the new interfaces as well! The latest code can is linked from the web page. We have a couple of road blocks to overcome however - the current version of the Axis toolkit has problems with the following constructs within the semantic model: 1) Union - the way we are utilizing union to merge KWV and a pattern cause Axis to generate no code for the element. 2) NMTOKEN for enumerations. Axis also doesn't appear to support this. To address these two problems for the current sample code, I've taken a snapshot of the PWG semantic model schemas, removed the Union declarations (by simply defining the types directly as KWV), and changed the NMTOKEN enumerations to string enumerations. I don't believe that we should change NMTOKEN's to string in the semantic model schemas, rather we should add support for NMTOKEN enumerations into the Axis toolkit. However, the union of KWV and string extension definition has me a bit concerned that this is probably way beyond current toolkits capabilities. Mainly because this would require that in the entity objects that the toolkits generate, they would need to perform some sort of type checking when a client tried to set the member variables to see if any restrictions were violated. Perhaps we could do the following: Declare the elements that need to either be a keyword or a string extension to have two sub elements - one defined by the KWV, and the other being a string... Any thoughts / suggestions? Have a great Thanksgiving! Dave Hall HP From imcdonald at sharplabs.com Fri Nov 29 15:09:16 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> SLP/LDAP for PSI Discovery - details and examples Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE2C@mailsrvnt02.enet.sharplabs.com> Hi folks, Friday (29 November 2002) Per my action item at last week's PSI Telecon (19 November 2002), below are some examples and details for PSI discovery via SLPv2 (RFC 2608) and LDAPv3 (RFC 2251). Note that the definition of standard PSI URL scheme names (see below) will allow the use of SLPv2 and LDAPv3 for PSI discovery without ANY additions to the existing standard printer schemas. Cheers, - Ira McDonald, co-editor of SLPv2 and LDAPv3 Printer Schemas High North Inc imcdonald@sharplabs.com ------------------------------------------------------------------------ PSI URL Schemes --------------- Since PSI Print Services and PSI Target Devices MUST use the (future) IANA-registered PSI port and MUST NOT use "http:" port 80 for their WSDL/SOAP interface, it follows that we need to define standard URL scheme names for them. URL scheme registration in the IETF tree (without embedded hyphen '-') is EXTREMELY slow (currently several YEARS before acceptance and RFC publication). Therefore, I suggest we do NOT register the following two PSI URL scheme names, but instead use an unregistered alternative tree (with a "pwg-" prefix). Conformant to "Registration Procedures for URL Scheme Names" (RFC 2717): pwg-psips: - PSI Print Service pwg-psitd: - PSI Target Device PSI URLs should be converted to underlying HTTP URLs by substitution of the "http:" scheme name and insertion of the PSI standard port. Printer Schema Locations ------------------------ The IANA-registered SLPv2 Printer Template v2.0 is in the directory: ftp://ftp.iana.org/assignments/svrloc-templates/ in the file: printer.2.0.en (8 March 2000) The current draft of LDAPv3 Printer Schema v1.0 is in the directory: ftp://ftp.ietf.org/internet-drafts/ in the file: draft-fleming-ldap-printer-schema-02.txt (30 June 2002) Note: The content and OIDs of the standard LDAPv3 Printer Schema v1.0 have been stable for three years. IBM and other vendors have been shipping implementations for over two years. Although not yet published as an RFC, the LDAPv3 Printer Schema v1.0 is entirely safe to deploy (the OIDs are assigned in the IBM namespace, NOT in the IETF namespace). If the LDAPv3 Printer Schema v1.0 continues to be delayed by the IETF, we plan to adopt and publish it as an IEEE/ISTO PWG standard in early calendar 2003. SLPv2 Discovery --------------- For PSI discovery, we can use the IANA-registered standard SLPv2 Printer Template v2.0 (without ANY extensions), by specifying SLPv2 service URLs of the form: service:printer:pwg-psips://hostport[abs_path] service:printer:pwg-psitd://hostport[abs_path] hostport = host [ ":" port ] host = IPv6reference / IPv4address / hostname port = *DIGIT abs_path = "/" path_segments SLPv2 Service Request --------------------- To locate available PSI Print Service(s), a PSI Client, acting in the role of an SLPv2 User Agent (UA), should use an SLPv2 Service Request (see section 8.1 of SLPv2, RFC 2608) of the form: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Service Location header (function = SrvRqst = 1) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of predicate string | Service Request \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of string | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The should be "service:printer:pwg-psips", to locate available PSI Print Service providers. Note that the final ":" MUST NOT be included in the . The (without explicit configuration) should be "DEFAULT" (the standard SLPv2 scope). Note that SLPv2 scope names are always case-sensitive, so "DEFAULT" must be in uppercase. The (not needed) MAY specify any LDAPv3 search filter (see "The String Representation of LDAP Search Filters", RFC 2254). To find a PSI Print Service provider that has SLPv2 registered with a different base URL (for example a "service:printer:ipp" URL), use a that specifies a substring search for "pwg-psips" in the "printer-xri-supported" attribute. For example an LDAPv3 filter of: "printer-xri-supported=*pwg-psips*" SLPv2 Service Reply ------------------- When operating in a zero config environment (without infrastructure), an available PSI Print Service(s), acting in the role of an SLPv2 Service Agent (UA), will DIRECTLY reply to the PSI Client. When operating in a managed environment (with infrastructure), an SLPv2 Directory Agent (DA) will reply to the PSI Client (on behalf of the registered appropriate SLPv2 SAs). The presence of the network infrastructure is completely transparent to the PSI Client - SLPv2 discovery uses identical SLPv2 requests and responses in either case. The SLPv2 Service Reply will be of the form: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Service Location header (function = SrvRply = 2) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Error Code | URL Entry count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Each returned PSI Print Service URL MUST specify either an IPv4/IPv6 address (directly usable) or a hostname (which must be resolved by DNS or mDNS lookup). SLPv2 DA Discovery ------------------ The DHCP option (decimal) 78 may be used, to find an SLPv2 Directory Agent (DA), per "DHCP Options for Service Location Protocol" (RFC 2610). LDAPv3 Discovery ---------------- For PSI discovery, we can use the standard LDAPv3 Printer Schema v1.0 (without ANY extensions), by searching for the LDAPv3 object class "printerService" (a base class) or "printerServiceAuxClass" (may be attached, for example, to a DMTF CIM printer object class - same content as "printerService") to find printer URLs (values of the "printer-uri" attribute) of the form: pwg-psips://hostport[abs_path] pwg-psitd://hostport[abs_path] Also, an LDAPv3 search filter may be used (as with SLPv2) to find the substring "pwg-psips" or "pwg-psitd" in the "printer-xri-supported" attribute. LDAPv3 DSA Discovery -------------------- The DHCP option (decimal) 95 may be used, to find an LDAPv3 Directory Service Agent (DSA). See the definition in the directory: ftp://ftp.iana.org/assignments/bootp-dhcp-extensions/ DNS Server Discovery -------------------- The DHCP option (decimal) 6 may be used to find a DNS server address. See "DHCP Options and BOOTP Vendor Extensions" (RFC 2132). The DHCP option (decimal) 117 may also be used to find a DNS server. See "The Name Service Search Option for DHCP" (RFC 2937). From imcdonald at sharplabs.com Fri Nov 29 16:05:11 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> [PDF posted] Updated Documents Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE2E@mailsrvnt02.enet.sharplabs.com> Hi Dave, I distilled the MS Word source and just posted: ftp://ftp.pwg.org/pub/pwg/ps/psi-spec94a.pdf and (for the Web page link) ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf Cheers, - Ira McDonald High North Inc -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Wednesday, November 27, 2002 8:35 AM To: 'ps@pwg.org' Subject: PS> Updated Documents Hey All! We've updated the specification document to 94a: ftp://ftp.pwg.org/pub/pwg/ps/psi-spec94a.doc This version of the document has made a stab at getting the mandatory / optional definitions into each of the methods comments section. For the AddDocumentByReference, this was modified to return an array of DocumentURI's, as a reference can refer to potentially more than one document. (For example, an email reference...) Also, we have successfully updated the sample code to utilize the strongly typed interfaces, and have made some soap calls with the new interfaces as well! The latest code can is linked from the web page. We have a couple of road blocks to overcome however - the current version of the Axis toolkit has problems with the following constructs within the semantic model: 1) Union - the way we are utilizing union to merge KWV and a pattern cause Axis to generate no code for the element. 2) NMTOKEN for enumerations. Axis also doesn't appear to support this. To address these two problems for the current sample code, I've taken a snapshot of the PWG semantic model schemas, removed the Union declarations (by simply defining the types directly as KWV), and changed the NMTOKEN enumerations to string enumerations. I don't believe that we should change NMTOKEN's to string in the semantic model schemas, rather we should add support for NMTOKEN enumerations into the Axis toolkit. However, the union of KWV and string extension definition has me a bit concerned that this is probably way beyond current toolkits capabilities. Mainly because this would require that in the entity objects that the toolkits generate, they would need to perform some sort of type checking when a client tried to set the member variables to see if any restrictions were violated. Perhaps we could do the following: Declare the elements that need to either be a keyword or a string extension to have two sub elements - one defined by the KWV, and the other being a string... Any thoughts / suggestions? Have a great Thanksgiving! Dave Hall HP From imcdonald at sharplabs.com Tue Dec 3 15:39:23 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> Multiple filenames per Job/Document Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE39@mailsrvnt02.enet.sharplabs.com> Hi folks, Tuesday (3 December 2002) At today's PSI Telecon, we proposed that both simple Jobs (in the Free Software Group's PAPI/1.0) and Documents (in future PWG Semantic Model and FSG Job Ticket API/2.0) should support an attribute that's a list of filenames that "comprise the _single_ document (when concatenated), for purposes of page exceptions". Note that PAPI says the printer should do page breaks and separator sheets between the files. That's not faithful to the model we agreed upon in FSG Job Ticket API telecons: the running input text is simply contatenated and subsequently repaginated in the output document format (input filenames could have MS Word, PostScript, PDF, etc. extensions). FSG PAPI reference implementation is CUPS over IPP/1.1 with extensions. This semantic ambiguity should be resolved or the CUPS implementation of the (future) IPP Job creation operation attribute "file-names" may become broken. Pete and Tom: In FSG PAPI v0.9, this attribute is called "file_names", which would become "file-names" for Job/Doc in IPP/1.x and "jobFileNames" and "documentFileNames" in PWG Semantic Model, right? Or just always (on Job or Document object) "document-file-names" in PWG SM and IPP? Note that "document-file-names" is then orthogonal to the single-valued "document-format" (because given document formats are _implied_ by the filename extensions by universal convention). Opinions? Cheers, - Ira McDonald High North Inc ------------------------------------------------------------------------ ftp://ftp.pwg.org/pub/pwg/fsg/spool/papi-v0.9.pdf (18 November 2002) [Extracted from section 7.2 "papiJobSubmitByReference" of PAPI/0.9, the description of the input operation parameter "file_names"] file_names NULL terminated list of pointers to names of files to print. If more than one file is specified, the files will be treated by the print system as separate "documents" for things like page breaks and separator sheets, but they will be scheduled and printed together as one job and the specified attributes will apply to all the files. These file names may contain absolute path names, relative path names or URIs ([RFC1738], [RFC2396]). The implementation SHOULD NOT copy the referenced data unless (or until) it is no longer feasible to maintain the reference. Feasibility limitations may arise out of security issues, namespace issues, and/or protocol or printer limitations. Implementations MUST support the absolute path, relative path, and "file:" URI scheme. Use of other URI schemes could result in a PAPI_URI_SCHEME error, depending on the implementation. The semantics explained in the preceding paragraphs allows for flexibility in the PAPI implementation. For example: (1) PAPI on top of a local service to maintain the reference for the life of the job, if the local service supports it. (2) PAPI on top of IPP to send a reference when the server can access the referenced data and copy it when it is not accessible to the server. (3) PAPI on top of network printing protocols that don't support references to copy the data on the way out to the remote server. From imcdonald at sharplabs.com Wed Dec 4 15:27:23 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> RE: URI GUID example Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE3E@mailsrvnt02.enet.sharplabs.com> Hi Dave, Take a look at "A UUID URN Namespace": ftp://ftp.ietf.org/internet-drafts/draft-mealling-uuid-urn-00.txt (Note that this registration comes from the ISO JTC1 folks, this is solid). Numerous examples, and implementation details. Cheers, - Ira McDonald High North Inc ------------------------------------------------------------------ [exerpts from "A UUID URN Namespace" draft] Abstract This specification defines a Uniform Resource Name namespace for UUIDs ( (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and if generated according to the one of the mechanisms in this document, is either guaranteed to be different from all other UUIDs/GUIDs generated until 3400 A.D. or extremely likely to be different (depending on the mechanism chosen). UUIDs were originally used in the Network Computing System (NCS) [1] and later in the Open Software Foundation's (OSF) Distributed Computing Environment [2]. This specification is derived from the latter specification with the kind permission of the OSF. The original version of this document was written by Paul Leach and Rich Salz but was unpublished for several years. This is an updated version incorporated as part of the URN registration document. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Namespace Registration Template . . . . . . . . . . . . . . 4 4. Specification . . . . . . . . . . . . . . . . . . . . . . . 7 4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1.1 Variant . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1.2 UUID Layout . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1.3 Version . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.4 Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.5 Clock sequence . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.6 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.7 Nil UUID . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2 Algorithms for creating a time-based UUID . . . . . . . . . 12 4.2.1 Basic algorithm . . . . . . . . . . . . . . . . . . . . . . 12 4.2.2 Reading stable storage . . . . . . . . . . . . . . . . . . . 13 4.2.3 System clock resolution . . . . . . . . . . . . . . . . . . 13 4.2.4 Writing stable storage . . . . . . . . . . . . . . . . . . . 14 4.2.5 Sharing state across processes . . . . . . . . . . . . . . . 14 4.2.6 UUID Generation details . . . . . . . . . . . . . . . . . . 14 4.3 Algorithm for creating a name-based UUID . . . . . . . . . . 15 5. Algorithms for creating a UUID from truly random or pseudo-random numbers . . . . . . . . . . . . . . . . . . . 16 6. Byte order of UUIDs . . . . . . . . . . . . . . . . . . . . 17 7. Node IDs when no IEEE 802 network card is available . . . . 17 8. Obtaining IEEE 802 addresses . . . . . . . . . . . . . . . . 19 9. Community Considerations . . . . . . . . . . . . . . . . . . 19 10. Security Considerations . . . . . . . . . . . . . . . . . . 20 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 Normative References . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21 A. Appendix A - UUID Sample Implementation . . . . . . . . . . 21 B. Appendix B - Sample output of utest . . . . . . . . . . . . 33 C. Appendix C - Some name space IDs . . . . . . . . . . . . . . 33 Full Copyright Statement . . . . . . . . . . . . . . . . . . 35 -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Wednesday, December 04, 2002 10:47 AM To: 'McDonald, Ira' Subject: URI GUID example Hey Ira... We're moving forward with the sample implementation, and are having a hard time figuring out what a String representation of a GUID would be... Do you have a link to, or can you make some examples? Would it look like this:? GUID://myserver.mydomain/{12321-23123-231adfe-321f} Thanks! Dave From alan.berkema at hp.com Thu Dec 5 12:21:49 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 12/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4CB@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday December 10 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From dhall at hp.com Tue Dec 10 10:55:21 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 12/10/02 Message-ID: <77261E830267D411BD4D00902740AC250DB4C155@xvan01.vcd.hp.com> Morning Alan - The meeting number / password is complaining on WebEx this morning... Dave -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, December 05, 2002 9:22 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: next call 12/10/02 Teleconference details: Date: Tuesdays, Next: Tuesday December 10 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From dhall at hp.com Tue Dec 10 11:10:09 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 12/10/02 Message-ID: <77261E830267D411BD4D00902740AC250DB4C156@xvan01.vcd.hp.com> New meeting ID & password 21410551, newpsi2 -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, December 10, 2002 7:55 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: RE: PS> [PSI]: next call 12/10/02 Morning Alan - The meeting number / password is complaining on WebEx this morning... Dave -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, December 05, 2002 9:22 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: next call 12/10/02 Teleconference details: Date: Tuesdays, Next: Tuesday December 10 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From dhall at hp.com Tue Dec 10 12:08:51 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> 12/10 Minutes Message-ID: <77261E830267D411BD4D00902740AC250DB4C157@xvan01.vcd.hp.com> PSI Meeting Minutes 1) WSDL with strong typing - Discussed element defined by union - Unioned restrictions should have the same type to make sense for the base element. PSI is OK with the existing semantic model definitions - with the exception of DocumentFormatWKV - since this needs to be a string, other restriction needs to be a string, not NMTOKEN. 2) Discovery update - Ira discussed Mobile Addhock Network - issues a Service Request rather than a Route Request. SLP service types. Nokia is developing the specification. ietf home page www.ietf.org - working groups mana... This would be deployed in smaller ad-hock networks in accesspoints, etc.. Could this be deployed in an enterprise? A big enterprise would run into problems... Mane give a route as well as a URL.. - Last week, discussed the possibility of having a PrintService published during DHCP configuration. 3) Review 0.94a Mandatory/Optional - QueryEndPointsInterface - Client - Mandatory unless administratively pre-configured - QueryInterfaceEndPoint & QueryInterfaceWSDL - Client One is mandatory unless administratively pre-configured - QueryInterfaceWSDL - this method returns a URL that refers to the WSDL that defines what the service ACTUALLY supports, not simply the standard PWG definition. - For example, target devices could return a URL to the WSDL that is hosted by the manufacturer, and not on the printer, or to the WSDL that is configured by the administrator. - ServiceCapabilitiesInterface - GetTargetDeviceElements - Discussion around making a TargetDevice validate the targetDeviceIdentifier, and throw an exception (New exception - InvalidTargetDeviceIdentifier) if not correct. - TargetDeviceIdentifier - Client to TargetDevice - Mandatory - requestedElements - If NULL, returns all elements supported - JobControlInterface Client - Conditionally mandatory - If you want to create a job, must use the interface. CreateJob Method TargetDeviceIdentifier - same as above deliverToTargetDevice - Client to TargetDevice - Mandatory, must be TRUE requestedTargetDeviceDataType - Client to TargetDevice - optional. If provided, validated Pick up on AddDocumentByReference next time. From dhall at hp.com Tue Dec 10 12:39:24 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <77261E830267D411BD4D00902740AC250DB4C159@xvan01.vcd.hp.com> During today's meeting, we discussed the QueryInterfacWSDL method, and came up with the following statement: - For example, target devices could return a URL to the WSDL that is hosted by the manufacturer, and not on the printer, or to the WSDL that is configured by the administrator. I don't think that this will actually work however. The WSDL typically has a service binding within it, and this couldn't be returned generically - The whole point of calling this method was to figure out what URL path to bind to for the interface you are requesting. We could change the meaning of the method to be "retrieve a WSDL that describes the interface" - but the client MUST use QueryInterfaceEndPoint to get the end point to bind to... Thoughts? Dave From dhall at hp.com Tue Dec 10 12:55:12 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <77261E830267D411BD4D00902740AC250DB4C15A@xvan01.vcd.hp.com> That could work - We could even combine the two methods - QueryInterfaceEndPoint and QueryInterfaceWSDL, into a single method QueryInterfaceDefinition - it would return two URL's - One to the EndPoint, the second to the WSDL.. The client must bind to the EndPoint provided, regardless of what the WSDL states. D -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) Sent: Tuesday, December 10, 2002 9:53 AM To: HALL,DAVID (HP-Vancouver,ex1); 'ps@pwg.org' Subject: RE: PS> QueryInterfaceWSDL discussion Yep - I think we forgot the "two halves" of WSDL. Could we modify QueryInterfaceWSDL to pass back both the URL the the WSDL AND the endpoint that the target device binds to that WSDL? bt > -----Original Message----- > From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] > Sent: Tuesday, December 10, 2002 9:39 AM > To: 'ps@pwg.org' > Subject: PS> QueryInterfaceWSDL discussion > > > During today's meeting, we discussed the QueryInterfacWSDL > method, and came > up with the following statement: > > - For example, target devices could return a > URL to the WSDL > that is hosted by the manufacturer, and not on the printer, > or to the WSDL > that is configured by the administrator. > > I don't think that this will actually work however. The WSDL > typically has > a service binding within it, and this couldn't be returned > generically - The > whole point of calling this method was to figure out what URL > path to bind > to for the interface you are requesting. > > > > binding="intf:org.pwg.psi.JobControlInterfaceSoapBinding"> > location="http://127.0.0.1/org.pwg.psi.JobControlInterface"/> > > > > We could change the meaning of the method to be "retrieve a WSDL that > describes the interface" - but the client MUST use > QueryInterfaceEndPoint to > get the end point to bind to... > > Thoughts? > > Dave > From imcdonald at sharplabs.com Tue Dec 10 12:56:28 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE4B@mailsrvnt02.enet.sharplabs.com> Hi David, You said it at the end below: 1) QueryInterfaceWSDL returns "a WSDL that describes the interface" (and NOT a specific WSDL endpoint identifier) 2) QueryInterfaceEndPoint - Client MUST use this to discover the actual WSDL endpoint OK? Cheers, - Ira McDonald High North Inc -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, December 10, 2002 11:39 AM To: 'ps@pwg.org' Subject: PS> QueryInterfaceWSDL discussion During today's meeting, we discussed the QueryInterfacWSDL method, and came up with the following statement: - For example, target devices could return a URL to the WSDL that is hosted by the manufacturer, and not on the printer, or to the WSDL that is configured by the administrator. I don't think that this will actually work however. The WSDL typically has a service binding within it, and this couldn't be returned generically - The whole point of calling this method was to figure out what URL path to bind to for the interface you are requesting. We could change the meaning of the method to be "retrieve a WSDL that describes the interface" - but the client MUST use QueryInterfaceEndPoint to get the end point to bind to... Thoughts? Dave From imcdonald at sharplabs.com Tue Dec 10 12:58:12 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE4C@mailsrvnt02.enet.sharplabs.com> Hi, Good simplification - I agree. Cheers, - Ira McDonald High North Inc -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, December 10, 2002 11:55 AM To: TAYLOR,BOB (HP-Vancouver,ex1); 'ps@pwg.org' Subject: RE: PS> QueryInterfaceWSDL discussion That could work - We could even combine the two methods - QueryInterfaceEndPoint and QueryInterfaceWSDL, into a single method QueryInterfaceDefinition - it would return two URL's - One to the EndPoint, the second to the WSDL.. The client must bind to the EndPoint provided, regardless of what the WSDL states. D -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) Sent: Tuesday, December 10, 2002 9:53 AM To: HALL,DAVID (HP-Vancouver,ex1); 'ps@pwg.org' Subject: RE: PS> QueryInterfaceWSDL discussion Yep - I think we forgot the "two halves" of WSDL. Could we modify QueryInterfaceWSDL to pass back both the URL the the WSDL AND the endpoint that the target device binds to that WSDL? bt > -----Original Message----- > From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] > Sent: Tuesday, December 10, 2002 9:39 AM > To: 'ps@pwg.org' > Subject: PS> QueryInterfaceWSDL discussion > > > During today's meeting, we discussed the QueryInterfacWSDL > method, and came > up with the following statement: > > - For example, target devices could return a > URL to the WSDL > that is hosted by the manufacturer, and not on the printer, > or to the WSDL > that is configured by the administrator. > > I don't think that this will actually work however. The WSDL > typically has > a service binding within it, and this couldn't be returned > generically - The > whole point of calling this method was to figure out what URL > path to bind > to for the interface you are requesting. > > > > binding="intf:org.pwg.psi.JobControlInterfaceSoapBinding"> > location="http://127.0.0.1/org.pwg.psi.JobControlInterface"/> > > > > We could change the meaning of the method to be "retrieve a WSDL that > describes the interface" - but the client MUST use > QueryInterfaceEndPoint to > get the end point to bind to... > > Thoughts? > > Dave > From alan.berkema at hp.com Sun Dec 15 12:04:41 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: FW: PS> [PSI]: next call 12/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4E1@xrose03.rose.hp.com> Hey all, Sorry I missed the last call I got caught up in the BlueTooth unplug fest and developers conference and forgot what day it was. Hope you had the call anyway. Alan ---- Teleconference details: NEXT: Tuesday December 17 (USA) NO CALL: - Tuesday December 24 (USA) NO CALL: - Tuesday December 31 (USA) NEXT: Tuesday January 7 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: TBD? 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Sun Dec 15 12:12:50 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 12/17/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4E3@xrose03.rose.hp.com> Fixed date in subject. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Sunday, December 15, 2002 9:05 AM To: 'a PSI pwg.org' Subject: FW: PS> [PSI]: next call 12/10/02 Hey all, Sorry I missed the last call I got caught up in the BlueTooth unplug fest and developers conference and forgot what day it was. Hope you had the call anyway. Alan ---- Teleconference details: NEXT: Tuesday December 17 (USA) NO CALL: - Tuesday December 24 (USA) NO CALL: - Tuesday December 31 (USA) NEXT: Tuesday January 7 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: TBD? 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Sun Dec 15 12:50:24 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: minutes 12/03/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4E4@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema Gail Songer *Dave Hall *Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 12/02/02 Agenda 1) Call for IP New Form attached 2) Discovery per Ira's action results 3) Strong Typed WSDL and tool kits with SM Schemas 4) Spec rev 0.94a mandatory/optional 12/02/02 Minutes: Action: Provide actuall examples of SSDP discovery Owner: Alan Status: Open Action: Provide actuall examples of mDNS-SD discovery Owner: Dave Status: Open Action: Register for mDNS-SD discovery, can we use the same names as SLPv2? Owner: Ira Status: Open Action: Register pwg- as an alternate SLPv2 tree root. Owner: Harry Status: Open Ira walked us through his SLPv2 and LDAPv3 examples. SLPv2 discovery requests are sent to an IANA registered multicast address using UDP/IP. Talked about allowing predicate to filter for PSI while sending discovery request to service:Printer Decided it would be better to always use service:Printer:pwg-psixx since this will make the SLPv2 Reply clear as to exactly what the discovered URL should be. Dave mentioned that DHCP would be a nice way to discovery the Print Service at the same time as other DHCP discovered values. Make this a consideration for future action since it will likely take some time. LDAPv3 may be a two step process? Action: Determine if we can get request attributes directly Owner: Ira Status: Open From alan.berkema at hp.com Tue Dec 17 10:48:53 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: PWG Form Call for Intellectual Property Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4F7@xrose03.rose.hp.com> Attached is the PWG version of the IEEE form. I think the other docs and procedures the PatCom uses still apply. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, November 07, 2002 3:21 PM To: a PSI pwg.org Subject: PS> [PSI]: Call for Intellectual Property > This is a call for Patents that are relevant to the IEEE ISTO PWG PSI > specification. > I'm not sure if the ISTO has their own procedures. To me it would seem > safe to use > the policy and procedures of the IEEE since the ISTO is an affiliate. > The IEEE call, is for essential Patents, though, it may not always be > clear what is > essential. > > If you believe you have IP in the PSI space you are encouraged to file an > LOA, > see below. > > If you know of a company that has IP in this space, that does participate > in the > working group, please let me know and I will send them the appropriate > letter asking > them to file an LOA. > > Also, if there is a more appropriate procedure, please let me know. > > Thanks, > Alan > > -------------------------------------------------------------------------- > --------------------------------------- > From: don@lexmark.com > Sent: Tuesday, December 18, 2001 5:46 AM > To: stds-msc@majordomo.ieee.org > Subject: PatCom Guide and LoA Form - now available > > Attached is a note with the latest information about Patents and the IEEE. > Working group chairs should read, understand and apply the PatCom Guide. > > ********************************************** > * Don Wright don@lexmark.com * > * * > * Chair, IEEE MSC * > * Member, IEEE SA Board of Governors * > * Member, IEEE-ISTO Board of Directors * > * * > * Director, Alliances & Standards * > * Lexmark International * > * 740 New Circle Rd * > * Lexington, Ky 40550 * > * 859-825-4808 (phone) 603-963-8352 (fax) * > ********************************************** > > ---------------------- Forwarded by Don Wright/Lex/Lexmark on 12/18/2001 > 08:44 > AM --------------------------- > > d.ringle%ieee.org@interlock.lexmark.com on 12/17/2001 02:38:49 PM > > To: std-liaison-reps@ieee.org > cc: (bcc: Don Wright/Lex/Lexmark) > Subject: PatCom Guide and LoA Form - now available > > All, > > There are some new Patent Committee documents available for your use. > > 1. Patent Letter of Assurance (LoA) Form > > This form can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link on the right-hand side for Entire Package > (http://standards.ieee.org/board/pat/july_2001.zip). In the package, > there > is an LoA form. > > This LoA form is the preferred format for letters of assurance. All > responses received on the Form can be easily reviewed (and accepted) by > PatCom. As of 1 January 2002, it is required that this be the only form > sent to potential patent holders when seeking a letter of assurance. > > {If the patent holder does not complete the form and, instead, sends in a > free-form letter, PatCom will take appropriate actions.} > > 2. PatCom Guide - "Understanding Patent Issues During IEEE Standards > Development" > > This guide can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link for 'Understanding Patent Issues During IEEE Standards > Development' (http://standards.ieee.org/board/pat/guide.html). > > > If you have any questions, let me know. > > Regards, > ************************************************************************** > ******** > > > David L. Ringle > PatCom Administrator > IEEE Standards Activities Dept. > > 445 Hoes Lane PH: +1 732 562 3806 > PO Box 1331 FX: +1 732 562 > 1571 > Piscataway, NJ 08855-1331 d.ringle@ieee.org > ************************************************************************** > ******** -------------- next part -------------- A non-text attachment was scrubbed... Name: pwg-loa.doc Type: application/msword Size: 28672 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021217/f5c03dc0/pwg-loa.doc From alan.berkema at hp.com Tue Dec 17 10:57:40 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: New webex Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4F9@xrose03.rose.hp.com> > Meeting number 23402009 > passwd newpsi > > http://hp.webex.com > > From don at lexmark.com Tue Dec 17 11:01:22 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: PWG Form Call for Intellectual Property Message-ID: Just to be sure everyone is aware, the completed form should be sent to: Secretariat, Printer Working Group c/o IEEE-ISTO 445 Hoes Lane Piscataway, NJ 08855 USA FAX (+651-318-7292) with a copy to Alan. ********************************************** Don Wright don@lexmark.com Member, IEEE SA Standards Board PatCom Chair, SCC Liaison Member, IEEE-ISTO Board of Directors f.wright@ieee.org / f.wright@computer.org Director, Alliances & Standards Lexmark International 740 New Circle Rd Lexington, Ky 40550 859-825-4808 (phone) 603-963-8352 (fax) ********************************************** "BERKEMA,ALAN C (HP-Roseville,ex1)" @pwg.org on 12/17/2002 10:48:53 AM Sent by: owner-ps@pwg.org To: "a PSI pwg.org" cc: Subject: PS> [PSI]: PWG Form Call for Intellectual Property Attached is the PWG version of the IEEE form. I think the other docs and procedures the PatCom uses still apply. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, November 07, 2002 3:21 PM To: a PSI pwg.org Subject: PS> [PSI]: Call for Intellectual Property > This is a call for Patents that are relevant to the IEEE ISTO PWG PSI > specification. > I'm not sure if the ISTO has their own procedures. To me it would seem > safe to use > the policy and procedures of the IEEE since the ISTO is an affiliate. > The IEEE call, is for essential Patents, though, it may not always be > clear what is > essential. > > If you believe you have IP in the PSI space you are encouraged to file an > LOA, > see below. > > If you know of a company that has IP in this space, that does participate > in the > working group, please let me know and I will send them the appropriate > letter asking > them to file an LOA. > > Also, if there is a more appropriate procedure, please let me know. > > Thanks, > Alan > > -------------------------------------------------------------------------- > --------------------------------------- > From: don@lexmark.com > Sent: Tuesday, December 18, 2001 5:46 AM > To: stds-msc@majordomo.ieee.org > Subject: PatCom Guide and LoA Form - now available > > Attached is a note with the latest information about Patents and the IEEE. > Working group chairs should read, understand and apply the PatCom Guide. > > ********************************************** > * Don Wright don@lexmark.com * > * * > * Chair, IEEE MSC * > * Member, IEEE SA Board of Governors * > * Member, IEEE-ISTO Board of Directors * > * * > * Director, Alliances & Standards * > * Lexmark International * > * 740 New Circle Rd * > * Lexington, Ky 40550 * > * 859-825-4808 (phone) 603-963-8352 (fax) * > ********************************************** > > ---------------------- Forwarded by Don Wright/Lex/Lexmark on 12/18/2001 > 08:44 > AM --------------------------- > > d.ringle%ieee.org@interlock.lexmark.com on 12/17/2001 02:38:49 PM > > To: std-liaison-reps@ieee.org > cc: (bcc: Don Wright/Lex/Lexmark) > Subject: PatCom Guide and LoA Form - now available > > All, > > There are some new Patent Committee documents available for your use. > > 1. Patent Letter of Assurance (LoA) Form > > This form can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link on the right-hand side for Entire Package > (http://standards.ieee.org/board/pat/july_2001.zip). In the package, > there > is an LoA form. > > This LoA form is the preferred format for letters of assurance. All > responses received on the Form can be easily reviewed (and accepted) by > PatCom. As of 1 January 2002, it is required that this be the only form > sent to potential patent holders when seeking a letter of assurance. > > {If the patent holder does not complete the form and, instead, sends in a > free-form letter, PatCom will take appropriate actions.} > > 2. PatCom Guide - "Understanding Patent Issues During IEEE Standards > Development" > > This guide can be found at http://standards.ieee.org/board/pat/index.html . > Click on the link for 'Understanding Patent Issues During IEEE Standards > Development' (http://standards.ieee.org/board/pat/guide.html). > > > If you have any questions, let me know. > > Regards, > ************************************************************************** > ******** > > > David L. Ringle > PatCom Administrator > IEEE Standards Activities Dept. > > 445 Hoes Lane PH: +1 732 562 3806 > PO Box 1331 FX: +1 732 562 > 1571 > Piscataway, NJ 08855-1331 d.ringle@ieee.org > ************************************************************************** > ******** (See attached file: pwg-loa.doc) -------------- next part -------------- A non-text attachment was scrubbed... Name: pwg-loa.doc Type: application/msword Size: 28672 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021217/3bfeef48/pwg-loa.doc From alan.berkema at hp.com Wed Dec 18 11:59:15 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: next call 01/07/03 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD50B@xrose03.rose.hp.com> Teleconference details: NEXT: Tuesday January 7 2003 (USA) NO CALL: - Tuesday December 24 (USA) NO CALL: - Tuesday December 31 (USA) NEXT: Tuesday January 14 2003 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Discovery - Finalize: SLPv2 and LDAPv3 examples for spec, SSDP examples for spec. 2) Look at mDNS-SD examples 3) Spec review topics WebEx info: ------------------------- 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: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 21643883 Meeting Password: newpsi Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Wed Dec 18 18:13:45 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:08 2009 Subject: PS> [PSI]: minutes 12/17/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD513@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Dave Hall Gail Songer *Jerry Thasher *Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 12/17/02 Agenda 1) New LOA for Call for IP sent to reflector 2) SSDP Example walk through 3) QueryInterface discussion 4) Few spec changes 5) Spec rev 0.94a mandatory/optional - left off at addDocumentByReference 12/17/02 Minutes: 0) Rev 0.94x (candidate for 0.95) will be delivered on the morning of January 13 2003. This gives us a week to review before the start of the week of PWG F2F meetings. Planning page turner review at PSI F2F January 24 2003. 1) Done. 2) Walked through SSDP example attached. We talked ourselves into the need for a psi:rootdevice, I believe for some type of compatibility. A day later I am have trouble seeing why this makes sense. Still seems like things would work fine with out it? Can anyone describe the reasons for why we added it? 3) I think we adopted the following: QueryInterfaceEndPoint and QueryInterfaceWSDL, into a single method QueryInterfaceDefinition - it would return two URL's - One to the EndPoint, the second to the WSDL.. The client must bind to the EndPoint provided, regardless of what the WSDL states. 4) Will come out as part of the next rev. 5) Did not get this far. -------------- next part -------------- A non-text attachment was scrubbed... Name: psi SSDP.pdf Type: application/octet-stream Size: 91873 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021218/c73e46a8/psiSSDP.obj From imcdonald at sharplabs.com Thu Dec 19 14:34:51 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:08 2009 Subject: PS> RFC 3391 - The MIME Application/Vnd.pwg-multiplexed Content-Type Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE5C@mailsrvnt02.enet.sharplabs.com> Hi folks, Finally, Bob Herriot's work has been published. Relevant to XHTML-Print, PWG PSIv1, FSG PAPIv1, UPnPv2, and others. Please note the "IESG Note" at the beginning (see below). Cheers, - Ira McDonald High North Inc ----------------------------------------------------------------------- IESG Note The IESG believes use of this media type is only appropriate in situations where the producer is fully aware of the capabilities and limitations of the consumer. In particular, this mechanism is very dependent on the producer knowing when the consumer will need a particular component of a multipart object. But consumers potentially work in many different ways and different consumers may need different things at different times. This mechanism provides no means for a producer to determine the needs of a particular consumer and how they are to be accommodated. Alternative mechanisms, such as a protocol based on BEEP which is capable of bidirectional communication between the producer and consumer, should be considered when the capabilities of the consumer are not known by the producer. Abstract The Application/Vnd.pwg-multiplexed content-type, like the Multipart/Related content-type, provides a mechanism for representing objects that consist of multiple components. An Application/Vnd.pwg-multiplexed entity contains a sequence of chunks. Each chunk contains a MIME message or a part of a MIME message. Each MIME message represents a component of the compound object, just as a body part of a Multipart/Related entity represents a component. With a Multipart/Related entity, a body part and its reference in some other body part may be separated by many octets. With an Application/Vnd.pwg-multiplexed entity, a message and its reference in some other message can be made quite close by chunking the message containing the reference. For example, if a long message contains references to images and the producer does not know of the need for each image until it generates the reference, then Application/Vnd.pwg-multiplexed allows the consumer to process the reference to the image and the image before it consumes the entire long message. This ability is important in printing and scanning applications. This document defines the Application/Vnd.pwg- multiplexed content-type. It also provides examples of its use. From don at lexmark.com Tue Feb 12 15:40:04 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> Test Message-ID: <200202122040.PAA16588@interlock2.lexmark.com> This is the first message. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances & Standards * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** From alan_berkema at hp.com Tue Feb 12 17:04:58 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> Test Message-ID: <499DC368E25AD411B3F100902740AD650587B14C@xrose03.rose.hp.com> Got it. -----Original Message----- From: don@lexmark.com [mailto:don@lexmark.com] Sent: Tuesday, February 12, 2002 12:40 PM To: ps@pwg.org Subject: PS> Test This is the first message. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances & Standards * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** From alan_berkema at hp.com Thu Feb 14 13:36:01 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: Telecon 2/19/02 CANCELLED, next 2/26, F2F minutes Message-ID: <499DC368E25AD411B3F100902740AD650587B16A@xrose03.rose.hp.com> All, I will be travelling next week so I need to cancel the 19th teleconference. Teleconference details 2002: Date: Tuesdays Tuesday 26 (USA) (No meeting February 19, Travelling) Through February 26 USA) Time: 8 AM (US PST) 650-690-9354 (T348-9354) ID: 55605 See Minutes attached. Thanks Lee. In addition I believe we opted for Tuesday the 16 for the F2F meeting date. Thanks, Alan > <> -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI Meeting Notes 020802.pdf Type: application/octet-stream Size: 16847 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020214/1220823a/PSIMeetingNotes020802-0001.obj From KOcke at crt.xerox.com Thu Feb 21 10:45:43 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:13 2009 Subject: PS> Editor or Secretary Message-ID: All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From melinda_grant at hp.com Thu Feb 21 11:59:27 2002 From: melinda_grant at hp.com (GRANT,MELINDA (HP-Vancouver,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> Editor or Secretary Message-ID: <6D805D4C4567D411AF32009027B683510855601B@xvan02.vcd.hp.com> Hi Kirk et al, I was assuming the role of secretary included the function of editor when I offered my name as secretary. (I suffer from the same write-and-think disability you mentioned ;-) I'd love to abdicate the note-taking role, but, like you, would like to act as an editor. Is this a role that can effectively be shared? Thanks, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 7:46 AM To: 'ps@pwg.org' Subject: PS> Editor or Secretary All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From KOcke at crt.xerox.com Thu Feb 21 14:02:18 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:13 2009 Subject: PS> Editor or Secretary Message-ID: Melinda, et. al., I'm certainly willing to share the role if that is an acceptable practice. I would still prefer to be an editor, but am willing to do the mundane work if needed. I already know I will not be able to attend the April face to face since we have a baby due any moment now, so even if I was the secretary I'd need to have someone else take the role in April. Kirk -----Original Message----- From: GRANT,MELINDA (HP-Vancouver,ex1) [mailto:melinda_grant@hp.com] Sent: Thursday, February 21, 2002 11:59 AM To: 'ps@pwg.org' Subject: RE: PS> Editor or Secretary Hi Kirk et al, I was assuming the role of secretary included the function of editor when I offered my name as secretary. (I suffer from the same write-and-think disability you mentioned ;-) I'd love to abdicate the note-taking role, but, like you, would like to act as an editor. Is this a role that can effectively be shared? Thanks, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 7:46 AM To: 'ps@pwg.org' Subject: PS> Editor or Secretary All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From melinda_grant at hp.com Thu Feb 21 17:18:55 2002 From: melinda_grant at hp.com (GRANT,MELINDA (HP-Vancouver,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> Editor or Secretary Message-ID: <6D805D4C4567D411AF32009027B68351085560D4@xvan02.vcd.hp.com> Oh, er, poop, I saw the 'ps' and some faulty mental synapse made the mapping to 'xp'... I didn't mean to be signing up for any psi role; my comments were wrt the xhtml-print wg. Forgive the noise, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 11:02 AM To: 'GRANT,MELINDA (HP-Vancouver,ex1)'; 'ps@pwg.org' Subject: RE: PS> Editor or Secretary Melinda, et. al., I'm certainly willing to share the role if that is an acceptable practice. I would still prefer to be an editor, but am willing to do the mundane work if needed. I already know I will not be able to attend the April face to face since we have a baby due any moment now, so even if I was the secretary I'd need to have someone else take the role in April. Kirk -----Original Message----- From: GRANT,MELINDA (HP-Vancouver,ex1) [mailto:melinda_grant@hp.com] Sent: Thursday, February 21, 2002 11:59 AM To: 'ps@pwg.org' Subject: RE: PS> Editor or Secretary Hi Kirk et al, I was assuming the role of secretary included the function of editor when I offered my name as secretary. (I suffer from the same write-and-think disability you mentioned ;-) I'd love to abdicate the note-taking role, but, like you, would like to act as an editor. Is this a role that can effectively be shared? Thanks, Melinda -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, February 21, 2002 7:46 AM To: 'ps@pwg.org' Subject: PS> Editor or Secretary All, I would like to propose adding my name as one of the editors. If the role of secretary does not require copious note taking during the face to face meetings I may be willing to volunteer for the role. Unfortunately I can't write and think at the same time, so I usually avoid this role at all cost. Anyone out there want to tell me what the secretary is responsible for? Kirk From harryl at us.ibm.com Mon Feb 25 12:26:46 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:13 2009 Subject: PS> Informal Tally of PS and XHTML formation charter voting Message-ID: I will ask Cindy to confirm the following, officially. At close of voting on Friday we had PS - 11 Approve, Approve (w/comment), 0 Disapprove, 19 no vote. XHTML - 11 Approve, 1 Disapprove (w/comment), 19 no vote. Thus, I believe both charters "pass" and these groups will be formed, possibly with some minor modifications to the charter based on comments. If modified, the charters will be reviewed as a first order of business within the working groups. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- From alan_berkema at hp.com Fri Mar 1 17:36:43 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: Next Teleconference 3/5/02 Message-ID: <499DC368E25AD411B3F100902740AD650587B1B4@xrose03.rose.hp.com> Welcome to PSI, if you would like to join this group please attend the teleconference. In the future we will only send this to the ps list. Agenda: 1) Introductions 2) PSI Overview Presentation 3) Questions PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday February 5 (USA) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 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/join/ Then click New User. ------------------------- On Tuesday use: http://hp.webex.com/join/ Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/5/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Mon Mar 4 18:16:01 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> RE: PWG-ANNOUNCE> [PSI]: Next Teleconference 3/5/02 Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1964@mailsrvnt02.enet.sharplabs.com> Hi folks, At the PWG FTP server, there's a subdirectory for PSI: ftp://ftp.pwg.org/pub/pwg/ps/ In that directory are the following files: -rw-r--r-- 1 pwg staff 52 Feb 12 15:34 Print Services Directory.txt -rw-r--r-- 1 pwg staff 15017 Feb 27 12:35 PSI-Charter-02.pdf -rw-r--r-- 1 pwg staff 66472 Mar 1 18:26 psi_requirements06.pdf -rw-r--r-- 1 pwg staff 452608 Mar 4 13:13 psi-spec22.doc -rw-r--r-- 1 pwg staff 105205 Mar 4 17:39 psi-spec22.pdf I just picked up the 'psi-spec22.doc' (MS Word) and used Acrobat Distiller to convert it to 'psi-spec22.pdf' for the convenience of a wider audience. Cheers, - Ira McDonald High North Inc PS - I included PWG announce on this reply, to make sure people knew about the Word and PDF versions of the work-in-progress PSI spec. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, March 01, 2002 4:37 PM To: 'ps@pwg.org' Cc: 'pwg-announce@pwg.org' Subject: PWG-ANNOUNCE> [PSI]: Next Teleconference 3/5/02 Welcome to PSI, if you would like to join this group please attend the teleconference. In the future we will only send this to the ps list. Agenda: 1) Introductions 2) PSI Overview Presentation 3) Questions PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday February 5 (USA) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 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/join/ Then click New User. ------------------------- On Tuesday use: http://hp.webex.com/join/ Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/5/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Mar 5 17:08:12 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> RE: PWG-ANNOUNCE> Print Services Web Page Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1969@mailsrvnt02.enet.sharplabs.com> Hi Gail, Here are some links to add to the Related Links section of PSI Home Page: Simple Object Access Protocol (SOAP) 1.1 W3C Note 08 May 2000 http://www.w3.org/TR/SOAP/ SOAP Version 1.2 Part 0: Primer W3C Working Draft 17 December 2001 http://www.w3.org/TR/soap12-part0/ SOAP Version 1.2 Part 1: Messaging Framework W3C Working Draft 17 December 2001 http://www.w3.org/TR/soap12-part1/ SOAP Version 1.2 Part 2: Adjuncts W3C Working Draft 17 December 2001 http://www.w3.org/TR/soap12-part2/ Web Services Description Language (WSDL) 1.1 W3C Note 15 March 2001 http://www.w3.org/TR/wsdl Web Services Inspection Language (WS-Inspection) 1.0 http://www-106.ibm.com/developerworks/library/ws-wsilspec.html Cheers, - Ira McDonald High North Inc -----Original Message----- From: Gail Songer [mailto:gsonger@netreon.com] Sent: Monday, March 04, 2002 6:32 PM To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> Print Services Web Page Hi All, I have just uploaded the initial version of the Print Services web page and added a link to it on the main page http://www.pwg.org. If you have any other links/information that you think should be on the page or would useful for the working group, please send them to me and I'll get them on the page. Gail From alan_berkema at hp.com Fri Mar 8 16:55:05 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: Next Teleconference 3/12/02 Message-ID: <499DC368E25AD411B3F100902740AD650587B1EC@xrose03.rose.hp.com> PSI Introduction Slides are on http://www.pwg.org/ps/index.html Agenda: 1) PSI Spec Review PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday March 12 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 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 Tuesday use: http://hp.webex.com The click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/12/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Wed Mar 13 18:05:46 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: minutes 3/12/02, next 3/19 Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF5D@xrose03.rose.hp.com> Agenda: 1) PSI Spec Review PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday March 19 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 3/12/02 Minutes: Attendees: Dave Hall Peter Zehler Kirk Ocke Don Wright Ira Mcdonald Peter Mierau Alan Berkema Dave Hall walked us through the current document and Rose diagrams. These will be posted to the ps site. Peter M. suggested that when the PS creates a URL to a formatted tempory file, we need a way to tell the PS it has been printed. Could refine this with other ideas like: delete immediate, save for xx time for additional prints etc. of course the PS policy may override the request to save for xx days? At the previous call we talked about SOAPv1.1 vs. SOAPv1.2. The concensus was that while SOAPv1.2 may have useful features all current toolkits only support v1.1 (with various degrees of sucess). At this point we will stick with v1.1 unless it becomes apperant that the industry and toolkits roll to v1.2. Talked about use of WSIL. At this meeting Ira stated that WSIL may also be imature and it's usefullness is deminished by lack of deployment. Suggest that PSI needs it's own built in mechanism to find well known named interfaces. Started a list of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- webex oinfo 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 3/19/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Mon Mar 18 10:00:55 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: Canceled 3/19/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF72@xrose03.rose.hp.com> Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From alan_berkema at hp.com Tue Mar 19 11:26:15 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]:Time change? Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF82@xrose03.rose.hp.com> All, I have had a request to schedule the PSI meetings later in the morning. Originally the meetings were early Pacific time to accommodate Europe. I don't think we have had a lot of European participation so I am open to consider change. If we make it 9:00AM that is noon on the east. Is this an issue for those in the east? Thanks, Alan -----Original Message----- From: Alain Regnier [mailto:alain@tpo.ussj.ricoh.com] Sent: Monday, March 18, 2002 6:54 PM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI]: Canceled 3/19/02 Hi, Would it be possible to schedule the PSI meetings later than 8am PCT? Alain Regnier Ricoh Corp -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, March 18, 2002 7:01 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: Canceled 3/19/02 Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From harryl at us.ibm.com Tue Mar 19 11:50:41 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]:Time change? Message-ID: If it only goes 1 hr. I can accommodate that. Else, I bump into a conflict after the first hr. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "BERKEMA,ALAN C (HP-Roseville,ex1)" Sent by: owner-ps@pwg.org 03/19/2002 09:26 AM To: "'Alain Regnier'" , "BERKEMA,ALAN C (HP-Roseville,ex1)" , "'a PSI pwg.org'" cc: Subject: RE: PS> [PSI]:Time change? All, I have had a request to schedule the PSI meetings later in the morning. Originally the meetings were early Pacific time to accommodate Europe. I don't think we have had a lot of European participation so I am open to consider change. If we make it 9:00AM that is noon on the east. Is this an issue for those in the east? Thanks, Alan -----Original Message----- From: Alain Regnier [mailto:alain@tpo.ussj.ricoh.com] Sent: Monday, March 18, 2002 6:54 PM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI]: Canceled 3/19/02 Hi, Would it be possible to schedule the PSI meetings later than 8am PCT? Alain Regnier Ricoh Corp -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, March 18, 2002 7:01 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: Canceled 3/19/02 Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From imcdonald at sharplabs.com Tue Mar 19 15:49:27 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]:Time change? Message-ID: <116DB56CD7DED511BC7800508B2CA5370A198B@mailsrvnt02.enet.sharplabs.com> Hi, An hour later is fine by me. Harry - the PSI telecons are only supposed to run for 1 hour, so you should have slack anyway. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Tuesday, March 19, 2002 10:51 AM To: BERKEMA,ALAN C (HP-Roseville,ex1) Cc: 'Alain Regnier'; 'a PSI pwg.org' Subject: RE: PS> [PSI]:Time change? If it only goes 1 hr. I can accommodate that. Else, I bump into a conflict after the first hr. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "BERKEMA,ALAN C (HP-Roseville,ex1)" Sent by: owner-ps@pwg.org 03/19/2002 09:26 AM To: "'Alain Regnier'" , "BERKEMA,ALAN C (HP-Roseville,ex1)" , "'a PSI pwg.org'" cc: Subject: RE: PS> [PSI]:Time change? All, I have had a request to schedule the PSI meetings later in the morning. Originally the meetings were early Pacific time to accommodate Europe. I don't think we have had a lot of European participation so I am open to consider change. If we make it 9:00AM that is noon on the east. Is this an issue for those in the east? Thanks, Alan -----Original Message----- From: Alain Regnier [mailto:alain@tpo.ussj.ricoh.com] Sent: Monday, March 18, 2002 6:54 PM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI]: Canceled 3/19/02 Hi, Would it be possible to schedule the PSI meetings later than 8am PCT? Alain Regnier Ricoh Corp -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, March 18, 2002 7:01 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: Canceled 3/19/02 Hi All, Really don't have any agenda items for today. Think we need to catch up on our work items. Thanks, Alan From alan_berkema at hp.com Thu Mar 21 12:44:25 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACF9B@xrose03.rose.hp.com> All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Thu Mar 21 12:48:29 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A198D@mailsrvnt02.enet.sharplabs.com> Hi Alan, Will there be a revised version of the PSI protocol spec available _before_ the meeting week after next (2 April)? Could you expand on the topic 'Off-Ramp Identifier' a little in email, please? Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 11:44 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 4/2 8:00AM Pacific All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Thu Mar 21 16:44:09 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACFA0@xrose03.rose.hp.com> Ira and all, For Off-Ramp identifier the editors (and I) worked on a proposal that encodes these as XML. Also, the editors have some actions to work on the documents. I believe Kirk said he would not be unable to do his part until next week. Goal is to get the latest posted before the 4/2 meeting. I know this will help folks that can't do webex. Editors please try to send something out by around Thursday 3/28/02. Thanks, Alan -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, March 21, 2002 9:48 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: next 4/2 8:00AM Pacific Hi Alan, Will there be a revised version of the PSI protocol spec available _before_ the meeting week after next (2 April)? Could you expand on the topic 'Off-Ramp Identifier' a little in email, please? Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 11:44 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 4/2 8:00AM Pacific All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Mon Apr 1 12:18:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: next 4/2 8:00AM Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19B0@mailsrvnt02.enet.sharplabs.com> Hi all, Just a reminder that there's a PSI telecon tomorrow (Tues 2 April) at 8am PST / 11am EST. Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 3:44 PM To: 'McDonald, Ira'; BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: RE: PS> [PSI]: next 4/2 8:00AM Pacific Ira and all, For Off-Ramp identifier the editors (and I) worked on a proposal that encodes these as XML. Also, the editors have some actions to work on the documents. I believe Kirk said he would not be unable to do his part until next week. Goal is to get the latest posted before the 4/2 meeting. I know this will help folks that can't do webex. Editors please try to send something out by around Thursday 3/28/02. Thanks, Alan -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, March 21, 2002 9:48 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: next 4/2 8:00AM Pacific Hi Alan, Will there be a revised version of the PSI protocol spec available _before_ the meeting week after next (2 April)? Could you expand on the topic 'Off-Ramp Identifier' a little in email, please? Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, March 21, 2002 11:44 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 4/2 8:00AM Pacific All, Time will stay the same. This has worked in the past and alternate times had conflicts for some of the core group that has been participating. Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F plans PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call March 26 (Spring Break) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From dhall at hp.com Tue Apr 2 11:08:59 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> XML Updates Message-ID: <77261E830267D411BD4D00902740AC2507F2A058@xvan01.vcd.hp.com> Hi guys - I snipped the XML updates out of the doc. Dave 1.1 OffRampIdentifier The OffRampIdentifier is an XML document. Example OffRampIdentifiers follow: See bluetooth definitions for additional identifier attributes... The idea is to not only define the identifier for the offramp, but also everything you need to know in order to establish a connection with the identifier. Have a separate XML DTD for each OffRampIdentifier Type. UNC <\\server\share> Port 9100 IP PORT user password FAX phone <\\server\share> number and other stuff Offramp JobControl Soap Endpoint http://a/b/c 1.2 Reference The reference passed into AddContentReference is an XML document. Example References follow: Also defined in bluetooth URL definition... Document URL http://a/b/c Secure Document URL https://a/b/c Document via FTP hostname or ip username password \a\b\c\d\e.doc Another possibility is to simply pass these parameters on the URL. We would need to be sure and define the schemas with a DTD... From alan_berkema at hp.com Mon Apr 8 12:09:51 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: next 4/9 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACFF6@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 2 (USA) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F Agenda Topic 3.1) Off-RampIdentfier- SOAP endpoint preferred. PORT 9100 & UNC legacy. Add an SNMP endpoint. Responsibility of the PS to contact he Off-Ramp and get it device attributes. Method varies based on Off-RampIdentfier. 3.2) Document reference - Add in BPP reference attributes. OBEX has doc type in header in the mime type filed. Need to add this to document reference. 3.3) IPP to PSI mapping. Purpose: A) Insure that we have not missed anything B) Semantic Alignment C) Leverage back. This section of the spec is like a work sheet to help us work through details of PSI. It may remain as an Appendix. 3.4) RUI or not? 3.5) Get JOBs operation. Functionality & methods 3.6) Persistence policy List of known work items: 1) Query Interface for extensability needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev Requiremnts doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Apr 9 12:36:26 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: minutes 4/9 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6ACFF8@xrose03.rose.hp.com> Here are the raw notes from todays call. I'll clean it up some for the F2F. See ya on Tuesday Alan PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below Attendees: Alan Berkema Paul Tukodi Dave Hall Jerry Thasher Harry Lewis Ira Mcdonald Kirk Ocke Peter Zehler Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F Agenda Topic 3.1) Off-RampIdentfier- SOAP endpoint preferred. PORT 9100 & UNC legacy. Add an SNMP endpoint. Responsibility of the PS to contact the Off-Ramp and get its device attributes. Method varies based on Off-RampIdentfier. 3.2) Document reference - Add in BPP reference attributes. OBEX has doc type in header in the mime type field. Need to add this to document reference. 3.3) IPP to PSI mapping. Purpose: A) Insure that we have not missed anything B) Semantic Alignment C) Leverage back. This section of the spec is like a work sheet to help us work through details of PSI. It may remain as an Appendix. 3.4) RUI or not? 3.5) Get JOBs per user or all jobs operation. Functionality & methods 3.6) Persistence policy. PS needs to know when the job is actually printed. Keep job record for history. Job itself should hang around for some default time 30 secs/60 seconds. Use Job MIB example. 3.7) Really web based job control. Extensible attributes, via browser. 3.8) Programmatic method for extended attributes. How does client know if the Off-Ramp supports these extended attributes? And then know if some attributes are or are not supported. Meta data -Name, syntax, legal values, text description of what the legal values do. Make it the standard way for all attributes as well as extended attributes. Name required rest optional. 3.9 Mechanism for mapping between PS, Off-Ramp & Client. Knowing what PS the client should talk to. PS to printer mappings. 3.10) Attributes move from object to XML. Combine Base and extended. Name space for base, use different name space for vendor specific. Allows for greater flexibility and works with current tool kits. Also works better with concepts introduced in 3.8. Caveat is that it places the burden of validation on the receiving device. Group felt this was a reasonable trade off, the receiving device needs to be aware that a sending device could send bad attributes (or values). List of known work items: 1) Query Interface for extensibility needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev RequiremntsRequirements doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Apr 9 12:46:53 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: minutes 4/9 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19C6@mailsrvnt02.enet.sharplabs.com> Hi Alan, Looks fine - you captured the two points about: (a) Job MIB (RFC 2707) reference for mimimum job persistence; and (b) the XML declaration of an attribute (or most of it) _is_ the attribute metadata returned by GetJobAttributes (with Name the required minimum returned). Thanks, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Tuesday, April 09, 2002 11:36 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: minutes 4/9 8:00:am Pacific Here are the raw notes from todays call. I'll clean it up some for the F2F. See ya on Tuesday Alan PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 16 (F2F meeting) Through April 23 USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 See webex info below Attendees: Alan Berkema Paul Tukodi Dave Hall Jerry Thasher Harry Lewis Ira Mcdonald Kirk Ocke Peter Zehler Agenda: 1) Off-Ramp Identifier 2) PSI IPP mapping 3) F2F Agenda Topic 3.1) Off-RampIdentfier- SOAP endpoint preferred. PORT 9100 & UNC legacy. Add an SNMP endpoint. Responsibility of the PS to contact the Off-Ramp and get its device attributes. Method varies based on Off-RampIdentfier. 3.2) Document reference - Add in BPP reference attributes. OBEX has doc type in header in the mime type field. Need to add this to document reference. 3.3) IPP to PSI mapping. Purpose: A) Insure that we have not missed anything B) Semantic Alignment C) Leverage back. This section of the spec is like a work sheet to help us work through details of PSI. It may remain as an Appendix. 3.4) RUI or not? 3.5) Get JOBs per user or all jobs operation. Functionality & methods 3.6) Persistence policy. PS needs to know when the job is actually printed. Keep job record for history. Job itself should hang around for some default time 30 secs/60 seconds. Use Job MIB example. 3.7) Really web based job control. Extensible attributes, via browser. 3.8) Programmatic method for extended attributes. How does client know if the Off-Ramp supports these extended attributes? And then know if some attributes are or are not supported. Meta data -Name, syntax, legal values, text description of what the legal values do. Make it the standard way for all attributes as well as extended attributes. Name required rest optional. 3.9 Mechanism for mapping between PS, Off-Ramp & Client. Knowing what PS the client should talk to. PS to printer mappings. 3.10) Attributes move from object to XML. Combine Base and extended. Name space for base, use different name space for vendor specific. Allows for greater flexibility and works with current tool kits. Also works better with concepts introduced in 3.8. Caveat is that it places the burden of validation on the receiving device. Group felt this was a reasonable trade off, the receiving device needs to be aware that a sending device could send bad attributes (or values). List of known work items: 1) Query Interface for extensibility needs work. 2) Off-Ramp Identifier needs to be defined 3) Security Model needs work 4) Job Status & Content Status needs to be defined. 5) Need to rev RequiremntsRequirements doc. 6) PSI overview section needs to be filled out ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From don at lexmark.com Fri Apr 12 16:10:23 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> WSDL for Printing Message-ID: <200204122010.QAA14339@interlock2.lexmark.com> I am representing Lexmark on the Web Services Design Language working group of the W3C. The group is working to fix errors and deficiencies in WSDL 1.1. Has anyone encountered any deficiencies in WSDL 1.1 in the course of PSI or other application of WSDL related to printing that I should identify to the group? If so, please send me a written description. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances and Standards * * Lexmark International * * 740 New Circle Rd C14/082-3 * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** From gsonger at peerless.com Mon Apr 15 11:20:56 2002 From: gsonger at peerless.com (Gail Songer) Date: Wed May 6 14:02:13 2009 Subject: PS> Updated Website Message-ID: Hi! I've just updated the web site with the latest versions of the specifications. Enjoy. Gail From imcdonald at sharplabs.com Mon Apr 15 13:18:42 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> Latest PSI docs on PWG server Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19CF@mailsrvnt02.enet.sharplabs.com> Hi folks, I just fixed up a few PSI document filenames, as follows: 1) Changed underscores to hyphens, because underscores CANNOT be seen in highlighted (underlined) Web links 2) Converted Kirk's IPP mapping (MS Word) to PDF, and fixed filenames. 3) Renamed 'psi.doc/pdf' to 'psi-model-view.doc/pdf' (for clarity). 4) Renamed 'psi.mdl' to 'psi-model.mdl' (Rational Rose model of PSI). Here's a directory listing of the current PSI docs at: ftp://ftp.pwg.org/pub/pwg/ps/ ftp> ls -ltr 200 PORT command successful. 150 Opening ASCII mode data connection for file list. -rw-r--r-- 1 pwg staff 52 Feb 12 15:34 Print Services Directory. txt -rw-r--r-- 1 pwg staff 15017 Feb 27 12:35 PSI-Charter-02.pdf -rw-r--r-- 1 pwg staff 66472 Mar 1 18:26 psi-requirements06.pdf -rw-r--r-- 1 pwg staff 452608 Mar 4 13:13 psi-spec22.doc -rw-r--r-- 1 pwg staff 105205 Mar 4 17:39 psi-spec22.pdf -rw-r--r-- 1 pwg staff 83876 Mar 5 18:30 psi_intro.pdf -rw-r--r-- 1 pwg staff 449536 Mar 13 20:38 psi-spec23.doc -rw-r--r-- 1 pwg staff 4979 Apr 15 11:05 attributes.xsd -rw-r--r-- 1 pwg staff 79360 Apr 15 11:06 psi-ipp-mapping.doc -rw-r--r-- 1 pwg staff 46080 Apr 15 11:06 psi-model-view.doc -rw-r--r-- 1 pwg staff 50176 Apr 15 11:06 psi1.doc -rw-r--r-- 1 pwg staff 412399 Apr 15 11:07 psi-model.mdl -rw-r--r-- 1 pwg staff 142986 Apr 15 11:07 psi-model-view.pdf -rw-r--r-- 1 pwg staff 156414 Apr 15 11:07 psi-requirements07.pdf -rw-r--r-- 1 pwg staff 410112 Apr 15 11:08 psi-spec25.doc -rw-r--r-- 1 pwg staff 193686 Apr 15 11:08 psi-spec25.pdf -rw-r--r-- 1 pwg staff 20621 Apr 15 12:52 psi-ipp-mapping.pdf And below is Alan Berkema's note from last Friday (12 April). Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, April 12, 2002 12:00 PM To: 'Don Levinstone'; 'Ira McDonald'; 'Jerry Thrasher'; 'Kirk Ocke'; 'Peter Mierau'; 'Peter Zehler'; 'Lee Farrell'; 'Paul@intermate-us.com' Subject: FW: PSI docs Importance: High This doesn't seem to be getting out. Here it is just in case. Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, April 12, 2002 8:52 AM To: 'Harry Lewis' Cc: 'Don Wright' Subject: FW: PSI reqs Importance: High Harry, We sent this stuff out a few days ago. Course it is to big for the reflector. Gail does not seem to be around. Can you put it on the ps web site. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Thursday, April 11, 2002 2:33 PM To: 'Gail Songer' Subject: PSI reqs Gail, Can you post these docs and send a note to the reflector. Thanks, see ya in Boston From imcdonald at sharplabs.com Mon Apr 15 13:39:36 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> Updated Website Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19D1@mailsrvnt02.enet.sharplabs.com> Hi, See my note a little after Gail's. Some of the specs had utterly opaque names. I renamed them. I also converted to the IPP mapping (Kirk Ocke's work) to PDF for easier access by all. Gail - thanks for posting the latest specs. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Gail Songer [mailto:gsonger@peerless.com] Sent: Monday, April 15, 2002 10:21 AM To: ps@pwg.org Subject: PS> Updated Website Hi! I've just updated the web site with the latest versions of the specifications. Enjoy. Gail From don at lexmark.com Mon Apr 15 13:42:27 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> Latest PSI docs on PWG server Message-ID: <200204151742.NAA10246@interlock2.lexmark.com> I have undone what Ira did so the links from the Web page work. ********************************************** * Don Wright don@lexmark.com * * * * Member, IEEE SA Standards Board * * Member, IEEE-ISTO Board of Directors * * f.wright@ieee.org / f.wright@computer.org * * * * Director, Alliances and Standards * * Lexmark International * * 740 New Circle Rd C14/082-3 * * Lexington, Ky 40550 * * 859-825-4808 (phone) 603-963-8352 (fax) * ********************************************** "McDonald, Ira" on 04/15/2002 01:18:42 PM To: "'BERKEMA,ALAN C (HP-Roseville,ex1)'" , "'ps@pwg.org'" cc: (bcc: Don Wright/Lex/Lexmark) Subject: PS> Latest PSI docs on PWG server Hi folks, I just fixed up a few PSI document filenames, as follows: 1) Changed underscores to hyphens, because underscores CANNOT be seen in highlighted (underlined) Web links 2) Converted Kirk's IPP mapping (MS Word) to PDF, and fixed filenames. 3) Renamed 'psi.doc/pdf' to 'psi-model-view.doc/pdf' (for clarity). 4) Renamed 'psi.mdl' to 'psi-model.mdl' (Rational Rose model of PSI). Here's a directory listing of the current PSI docs at: ftp://ftp.pwg.org/pub/pwg/ps/ ftp> ls -ltr 200 PORT command successful. 150 Opening ASCII mode data connection for file list. -rw-r--r-- 1 pwg staff 52 Feb 12 15:34 Print Services Directory. txt -rw-r--r-- 1 pwg staff 15017 Feb 27 12:35 PSI-Charter-02.pdf -rw-r--r-- 1 pwg staff 66472 Mar 1 18:26 psi-requirements06.pdf -rw-r--r-- 1 pwg staff 452608 Mar 4 13:13 psi-spec22.doc -rw-r--r-- 1 pwg staff 105205 Mar 4 17:39 psi-spec22.pdf -rw-r--r-- 1 pwg staff 83876 Mar 5 18:30 psi_intro.pdf -rw-r--r-- 1 pwg staff 449536 Mar 13 20:38 psi-spec23.doc -rw-r--r-- 1 pwg staff 4979 Apr 15 11:05 attributes.xsd -rw-r--r-- 1 pwg staff 79360 Apr 15 11:06 psi-ipp-mapping.doc -rw-r--r-- 1 pwg staff 46080 Apr 15 11:06 psi-model-view.doc -rw-r--r-- 1 pwg staff 50176 Apr 15 11:06 psi1.doc -rw-r--r-- 1 pwg staff 412399 Apr 15 11:07 psi-model.mdl -rw-r--r-- 1 pwg staff 142986 Apr 15 11:07 psi-model-view.pdf -rw-r--r-- 1 pwg staff 156414 Apr 15 11:07 psi-requirements07.pdf -rw-r--r-- 1 pwg staff 410112 Apr 15 11:08 psi-spec25.doc -rw-r--r-- 1 pwg staff 193686 Apr 15 11:08 psi-spec25.pdf -rw-r--r-- 1 pwg staff 20621 Apr 15 12:52 psi-ipp-mapping.pdf And below is Alan Berkema's note from last Friday (12 April). Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, April 12, 2002 12:00 PM To: 'Don Levinstone'; 'Ira McDonald'; 'Jerry Thrasher'; 'Kirk Ocke'; 'Peter Mierau'; 'Peter Zehler'; 'Lee Farrell'; 'Paul@intermate-us.com' Subject: FW: PSI docs Importance: High This doesn't seem to be getting out. Here it is just in case. Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, April 12, 2002 8:52 AM To: 'Harry Lewis' Cc: 'Don Wright' Subject: FW: PSI reqs Importance: High Harry, We sent this stuff out a few days ago. Course it is to big for the reflector. Gail does not seem to be around. Can you put it on the ps web site. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Thursday, April 11, 2002 2:33 PM To: 'Gail Songer' Subject: PSI reqs Gail, Can you post these docs and send a note to the reflector. Thanks, see ya in Boston From imcdonald at sharplabs.com Wed Apr 17 15:27:46 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> FW: New I-D for Internationalized Resource Identifiers Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19DF@mailsrvnt02.enet.sharplabs.com> Hi, FYI - latest version of IRIs (fully internationalized UTF-8 based URIs). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Martin Duerst [mailto:duerst@w3.org] Sent: Wednesday, April 17, 2002 2:41 AM To: www-international@w3.org Subject: New I-D for Internationalized Resource Identifiers Dear Web Internationalizers, I have just submitted draft-w3c-i18n-iri-00.txt to the Internet Drafts editor. This draft replaces draft-masinter-url-i18n-08.txt. It should be published in a few hours/days. In the mean time it is available at http://www.w3.org/International/2002/draft-w3c-i18n-iri-00.txt. Based on discussions at the W3C Technical Plenary in February, and in particular on input from Larry Masinter, we have made some changes in the responsibilities for the Internationalized Resource Identifiers (IRI) draft, as follows: - The W3C I18N WG is taking on responsibility for carefully reviewing the current draft and bringing it to maturity for submission to the IESG. - Larry is glad to step down as a co-editor, and Michel Suignard has volunteered to become a new co-editor. Many thanks to Larry for his work as co-author of many earlier versions of this document. This has resulted in the name change. The document will still be handled as an individual submission from the point of view of the IETF. We hope to take this document to IETF/W3C Last Call in May, after some more work. Please review draft-w3c-i18n-iri-00.txt and send comments to w3c-i18n-comments@w3.org (publicly archived at http://lists.w3.org/Archives/Public/www-i18n-comments/). Regards, Martin. From alan_berkema at hp.com Fri Apr 19 12:45:53 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: teleconference 4/23 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD030@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 29? (In Barcelona) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Will work on an agenda: See webex info below ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 21690293 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Fri Apr 19 16:24:56 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: requirements ver 0.071 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD035@xrose03.rose.hp.com> Only editorial changes. Don if you do not get this twice can you inform Graydon that I sent it at ~1:25 PST Thanks, Alan From KOcke at crt.xerox.com Mon Apr 22 10:08:44 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: teleconference 4/23 8:00:am Pacific Message-ID: As many of you may have noticed I did not make the Boston meeting. My sincere apologies. I was unfortunately not able to make the four hour drive from on Tuesday due to illness. "See" you at the teleconference. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, April 19, 2002 12:46 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: teleconference 4/23 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 23 (USA) No Call April 29? (In Barcelona) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Will work on an agenda: See webex info below ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 21690293 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Apr 23 16:54:52 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: teleconference 4/30 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD057@xrose03.rose.hp.com> -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, April 19, 2002 9:46 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: teleconference 4/23 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Dave Hall will lead and set the agenda. He will also send out webex info. At the 4/23 meeting we spent the entire session reviewing Kirks IPP to PSI mapping document. The next revision will reflect the changes. Will also modify the PSI spec to add some of the attributes of IPP. Actions from F2F: Define Off-Ramp Identifier Schema - Dave & Kirk Add Document Reference as discussed to next rev of spec. - Dave Send out class attribute structure - Peter Send out Status schema - Peter Define Job Attributes for Get Jobs - Peter Look at UPDF for Extended Attribute Definition - all Actions from call - IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave From alan_berkema at hp.com Thu Apr 25 18:10:43 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: New docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD075@xrose03.rose.hp.com> Hey All, I just posted psi042204.pdf and psi-spec26.pdf to the PS ftp site. Thanks, Alan From don at lexmark.com Fri Apr 26 10:30:06 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: New docs Message-ID: <200204261431.KAA02197@interlock2.lexmark.com> All: So that the Web Site points to the latest versions without requiring changes to the site for each new version, I have changed the names of Alan's files as follows: psi042204.pdf ---> psi-model-view.pdf psi-spec26.pdf ---> psi-spec-latest.pdf In order to have an archive of these files as we move forward, we should always upload the files with the version number or date included in the file name and then upload the same files with the generic name. Happy hunting!! ********************************************** Don Wright don@lexmark.com Member, IEEE SA Standards Board Member, IEEE-ISTO Board of Directors f.wright@ieee.org / f.wright@computer.org Director, Alliances & Standards Lexmark International 740 New Circle Rd Lexington, Ky 40550 859-825-4808 (phone) 603-963-8352 (fax) ********************************************** "BERKEMA,ALAN C (HP-Roseville,ex1)" on 04/25/2002 06:10:43 PM To: "'a PSI pwg.org'" cc: (bcc: Don Wright/Lex/Lexmark) Subject: PS> [PSI]: New docs Hey All, I just posted psi042204.pdf and psi-spec26.pdf to the PS ftp site. Thanks, Alan From dhall at hp.com Tue Apr 30 10:56:40 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> FW: Meeting Invitation from David Hall Message-ID: <77261E830267D411BD4D00902740AC2507F2A2E8@xvan01.vcd.hp.com> Subject: Meeting Invitation from David Hall David Hall, David Hall has invited you to join a meeting on the Web, using WebEx. ------------------------- TO JOIN THE MEETING ------------------------- On 4/30/2002, at 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time), click this URL: https://hp.webex.com/webex/e.php?AT=JE&EventID=74715997&UUID=4434397 The password is: mypsi ------------------------- 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. To set up now, go to: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: psi Date: 4/30/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 28519863 Meeting Password: mypsi Teleconference: None Agenda: Host: David Hall 1(360)212x4228 mailto:dhall@hp.com http://www.webex.com We've got to start meeting like this(TM) From imcdonald at sharplabs.com Tue Apr 30 14:04:20 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> FW: Registration of new charsets: UTF-32, UTF-32BE, UTF-32LE Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19EF@mailsrvnt02.enet.sharplabs.com> Hi folks, Below are the registrations for the three labels for UTF-32 (UCS-4 restricted to the 'UTF-16 accessible' first million codepoints). Cheers, - Ira McDonald High North Inc -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Friday, April 12, 2002 11:54 AM To: Martin Duerst; Mark Davis Cc: Harald Tveit Alvestrand; ietf-charsets@iana.org Subject: RE: Registration of new charsets: UTF-32, UTF-32BE, UTF-32LE Martin and Mark, Big apologies for the delay. The following have been added to the Character Sets registry: Name: UTF-32 [Davis] MIBenum: 1017 Source: Alias: None Name: UTF-32BE [Davis] MIBenum: 1018 Source: Alias: None Name: UTF-32LE [Davis] MIBenum: 1019 Source: Alias: None Please see: Please let me know if anything appears incorrectly or if you have any questions. Thank you, Michelle S. Cotton IANA Administrator From imcdonald at sharplabs.com Tue Apr 30 14:06:38 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> FW: New IANA 'character-sets' directory Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19F0@mailsrvnt02.enet.sharplabs.com> Hi folks, New home for the IANA Charsets Registry. Tom Hastings - please note for upcoming IPP documents References sections edits. Cheers, - Ira McDonald High North Inc -----Original Message----- From: IANA [mailto:iana@iana.org] Sent: Thursday, April 18, 2002 1:47 PM To: Martin Duerst; Harald Tveit Alvestrand Cc: ietf-charsets@iana.org Subject: RE: Fixing redirects for 'character-sets' directory Martin and Harald, I have made some changes to the Character Set information that is linked from the IANA page at http://www.iana.org/numbers.htm. These changes include the following: I have added: This now replaces the isi.edu page. At: I have updated the registrations that include pointers to registration templates to now point to www.iana.org Please let me know if you see anything that appears incorrect. Michelle IANA From Lee.Farrell at cda.canon.com Wed May 1 22:47:00 2002 From: Lee.Farrell at cda.canon.com (Farrell, Lee) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI Meeting Notes -- Apr '02 Message-ID: <> =========================== Lee Farrell Canon Development Americas 110 Innovation Drive Irvine, CA 92612 (949) 856-7163 - voice (949) 856-7510 - fax lee.farrell@cda.canon.com =========================== -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI Meeting Notes 020416.pdf Type: application/octet-stream Size: 20065 bytes Desc: PSI Meeting Notes 020416.pdf Url : http://www.pwg.org/archives/ps/attachments/20020501/bfa36e82/PSIMeetingNotes020416-0001.obj From imcdonald at sharplabs.com Mon May 6 17:25:53 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> I-D Guidelines for XML in IETF Protocols Message-ID: <116DB56CD7DED511BC7800508B2CA5370A19FB@mailsrvnt02.enet.sharplabs.com> Hi folks, RECOMMENDED reading For anyone interested in XML-based protocols - Bob Herriot, Dave Hall, Kirk Ocke, and other PWG editors. In the IETF repository 'ftp://ftp.ietf.org/internet-drafts/' see: "Guidelines for the Use of XML within IETF Protocols", by Scott Hollenbeck (VeriSign), Marshall Rose (Dover Beach), Larry Masinter (Adobe). (29 April 2002) As noted below, this document is intended to become an IETF BCP (Best Current Practice) RFC. Cheers, - Ira McDonald High North Inc ---------------------------------------- Abstract The Extensible Markup Language (XML) is a framework for structuring data. While it evolved from SGML -- a markup language primarily focused on structuring documents -- XML has evolved to be a widely- used mechanism for representing structured data. There are a wide variety of Internet protocols being developed; many have need for a representation for structured data relevant to their application. There has been much interest in the use of XML as a representation method. This document describes basic XML concepts, analyzes various alternatives in the use of XML, and provides guidelines for the use of XML within IETF standards-track protocols. Intended Publication Status It is the goal of the authors that this draft (when completed and then approved by the IESG) be published as a Best Current Practice (BCP). Conventions Used In This Document This document recommends, as policy, what specifications for Internet protocols -- and, in particular, IETF standards track protocol documents -- should include as normative language within them. The capitalized keywords "SHOULD", "MUST", "REQUIRED", etc. are used in the sense of how they would be used within other documents with the meanings as specified in RFC 2119 [1]. ---------------------------------------- Table of Contents 1. Introduction and Overview . . . . . . . . . . . . . . . . . 4 1.1 Intended Audience . . . . . . . . . . . . . . . . . . . . . 4 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 XML Evolution . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 XML Users, Support Groups, and Additional Information . . . 5 2. XML Selection Considerations . . . . . . . . . . . . . . . . 6 3. XML Alternatives . . . . . . . . . . . . . . . . . . . . . . 8 4. XML Use Considerations and Recommendations . . . . . . . . . 10 4.1 XML Declarations . . . . . . . . . . . . . . . . . . . . . . 10 4.2 XML Processing Instructions . . . . . . . . . . . . . . . . 10 4.3 Well-Formedness . . . . . . . . . . . . . . . . . . . . . . 11 4.4 Validity and Extensibility . . . . . . . . . . . . . . . . . 11 4.5 Namespaces . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.5.1 Namespaces and Attributes . . . . . . . . . . . . . . . . . 13 4.6 Element and Attribute Design Considerations . . . . . . . . 13 4.7 Binary Data . . . . . . . . . . . . . . . . . . . . . . . . 15 4.8 Incremental Processing . . . . . . . . . . . . . . . . . . . 15 5. Internationalization Considerations . . . . . . . . . . . . 16 5.1 Character Sets and Encodings: UTF-8 and UTF-16 . . . . . . . 16 5.2 Language Declaration . . . . . . . . . . . . . . . . . . . . 16 5.3 Other Considerations . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 Normative References . . . . . . . . . . . . . . . . . . . . 21 Informative References . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 24 A. Appendix A: Change History . . . . . . . . . . . . . . . . . 26 Full Copyright Statement . . . . . . . . . . . . . . . . . . 28 From dhall at hp.com Mon May 6 18:28:56 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> No PSI meeting tomorrow Message-ID: <77261E830267D411BD4D00902740AC2507F2A3C6@xvan01.vcd.hp.com> I haven't had any time to update docs, and Alan won't be available.. See you next week! David Hall HP From alan_berkema at hp.com Fri May 10 16:00:48 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:13 2009 Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD08A@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From PZehler at crt.xerox.com Mon May 13 12:26:36 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: All, Attached is a class hierarchy for operational attributes. I have shown them in a PWG semantic model specific way. I used CreateJob for InvokeJob, AddDocument for AddContent Post and Reference. I used the GetJobs, GetJobAttributes and GetPrinterAttributes for all the status and attribute calls in PSI. It does demonstrate that classes are dderive form a base clas and are specialized for job creation, content addition, queries and query lists (i.e. list of jobs/documents). I only have the IPP specific ways of identifying a target. I assume that when PSI defines the offramp identifier it will be another choice in the "Target" complex type. I will send the XML schema under separate cover. Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, May 10, 2002 4:01 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: OperationalAttributes.pdf Type: application/octet-stream Size: 130729 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020513/6b04fa11/OperationalAttributes-0001.obj From PZehler at crt.xerox.com Mon May 13 12:29:24 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: All, The XML Schema demonstrating operational attributes. Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, May 10, 2002 4:01 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: teleconference 5/14 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: PsiOperational.xsd Type: application/octet-stream Size: 6538 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020513/55b81342/PsiOperational-0001.obj From alan_berkema at hp.com Tue May 14 11:01:29 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> RE: [PSI]: teleconference 5/14 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD091@xrose03.rose.hp.com> Meeting Number: 21248466 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, May 10, 2002 1:01 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: teleconference 5/14 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday April 30 (USA) Through June (USA) Time: 8 AM (US PST) 404 774-4112 (T774-4112) ID: 55605 Also, see webex info below. Agenda: 1) Review actions 2) TBD Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22694237 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue May 14 14:50:05 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/14, next 5/21 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD099@xrose03.rose.hp.com> *Note new phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 21 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Tom Hastings 05/21/02 Agenda 1) review updated doc with first pass at including attributes expected 5/16 PM. 05/14/02 Agenda: 1) Review Peter's attribute document. Minutes: Spent the entire meeting talking about what should be a method parameter vs. an attribute. Great discussion on how to partition things for interoperability. One extreme is that we just have a goForIt method with all the operation details in XML another is that all operation choices are parameters. I think we achieved consensus to minimize parameters, keeping those that optimize PSI and keep the majority in XML for interoperable extensibility. Dave & Kirk & Alan will take a first pass at merging Peter's doc into the PSI spec. Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Wed May 15 18:36:41 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: New docs 05/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD09F@xrose03.rose.hp.com> All, Updated web site as follows: added both sets of these files: psi051502.pdf ---> psi-model-view.pdf psi-spec27.pdf ---> psi-spec-latest.pdf As well as: attributes051502.xsd reference051502.xsd targetdevice051502.xsd Thanks, Alan From alan_berkema at hp.com Thu May 16 18:36:27 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: More New docs 05/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD0B1@xrose03.rose.hp.com> Ftp'd another one from Kirk offramp051402.xsd Alan ---- -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Wednesday, May 15, 2002 3:37 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: New docs 05/15/02 All, Updated web site as follows: added both sets of these files: psi051502.pdf ---> psi-model-view.pdf psi-spec27.pdf ---> psi-spec-latest.pdf As well as: attributes051502.xsd reference051502.xsd targetdevice051502.xsd Thanks, Alan From alan_berkema at hp.com Tue May 21 16:32:29 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD0C8@xrose03.rose.hp.com> *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 28 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Don Wright Bob Taylor Don Levinstone Lee Farrell Ira McDonald 05/28/02 Agenda 1) review template attributes 2) review Target Device Identifier and Reference schema 3) Review actions 05/21/02 Agenda: 1) Review Latest Selected Logical View Report (psi051505). Minutes: 1) Reviewed how Peter's IPP attributes document relates to PSI. Most map to attributes, however, last document takes the place of invoke complete as a Boolean parameter. Attributes schemas: Job Attributes - Apply to the entire Job and all the documents Document Attributes - Overall general characteristics of a document Template Attribute - Name is a left over from IPP. We think processing attributes might be a better name. These a things like number of copies, N-up etc. Requested Attributes - inherit from Job & Template attributes Exception Attributes - List of attributes and values that the device does not support. 2) Dave did a quick review of the latest PSI spec (psi_spec051502). Group agreed to and accept changes/revisions from previous reviews. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From PZehler at crt.xerox.com Thu May 23 08:47:24 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:14 2009 Subject: PS> PWG Semantic Model Message-ID: All, The Print semantics that we defined in IPP are being used throughout the industry. The print system may be less functional (e.g. UPnP) or much more complex (e.g. JDF DigitalPrinting). The important point is that whenever possible the semantics are being reused. The reuse is a great benefit to Printer manufacturers. It simplifies the logic necessary to incorporate our devices into these various network environments. It speeds the definition of printing protocols/systems since the semantics of common features need not be reargued. One of the barriers to the use of the PWG print model is its tight association with IPP. In the definition of IPP we clearly separated the model from the protocol. RFC2911 covers the base semantics. We also have extensions to the model defined in some Internet Drafts and IEEE-ISTO PWG standards. I believe we should split the IPP semantic model from the IPP protocol. Using the "PWG Semantic Model" in discussions around industry wide agreed upon print semantics avoids the "IPP baggage". I believe the separation will foster reuse in various network printing environments and standards. The separation will not affect compatibility with IPP. To begin the conversation I though we might start with the definition of a "PrintJob Ticket". The existing semantics has the Job Template Attributes that cover most of a PrintJob Ticket. These cover the semantics of the production instructions. There are some additional descriptive and control attributes that are required. Examples include "jobName", "jobRequestingUserName" and "attributeFidelity". These attributes are normally held in an operation's Operational Attributes. Often there is a direct mapping to a Job's Description Attribute as with "jobName". There are cases where the mapping is simple between the Operational Attribute and the Description Attribute as with "JobRequestingUserName" mapping to "JobOriginatingUserName". We even have cases where there is no mapping such as with "attributeFidelity". We have already agreed on the semantics. We need to work out what a freestanding PrintJob Ticket will look like for the PWG. I have uploaded an XML schema definition for RFC2911. The schema includes some types (e.g. rangeOfInteger), a Job and the elements that compose a Job, namely Job Description and Job Template elements. Included is a sample PrintJob Ticket based on the Job Template. I thought a conversation around a Print Job and a PrintJob Ticket would be appropriate. Some rules I used in the schema mapping: 1) Data types are simplified where ever possible. ( "nameWithLanguage" becomes "string" with a length restriction) 2) For attributes (and operations) the '-' character is dropped and the following character is capitalized. ("job-name" becomes "jobName") 3) Attribute value strings remain the same. ("job-state-reasons"='job-printing' becomes "jobStateReasons"='job-printing') 4) Any attribute with the string "ipp" has the "ipp" string removed. ("ipp-attribute-fidelity" becomes "attributeFidelity") 5) All IPP attributes are represented as XML elements. 6) All attribute groups are represented as an ordered set of elements (i.e. sequence) 7) All enums are represented as strings using the string associated with the integer value. ("job-state"='3' becomes "jobState"="pending") 8) All type 1 enumes are represented as a "string" type with an enumerations restriction. (i.e. can not be extended) 9) All type 2 and 3 are represented as a "string". The standardized values are captured as appinfo annotations. (i.e. allows vendor and site extensions) 10) Multivalue attributes are represented as a single instance of an element that contains a sequence of elements (see "finishings" in sample PrintJobTicket or JobTemplate schema) 11) shema allows addition of new elements via "xsd:any" and places no restriction on namespace of addition. Some PWG specific types: "ftp://pwg.org/pub/pwg/Semantic_model/typesPWG.xsd" The Job: "ftp://pwg.org/pub/pwg/Semantic_model/Job.xsd" The Job Description attributes(i.e. XML elements) for the Job: "ftp://pwg.org/pub/pwg/Semantic_model/JobDescription.xsd" The Job Template attributes(i.e. XML elements) for the Job: "ftp://pwg.org/pub/pwg/Semantic_model/JobDescription.xsd" A Sample Print Job Ticket based on Job Template attributes: "ftp://pwg.org/pub/pwg/Semantic_model/PrintJobTicket.xml" I also have a 21 page PWG Semantic Model Overview document that I will send out tomorrow. This version is limited to RFC2911. It is a very concise semantic guide for those of us who are not IPP experts. It describes the model, objects, attributes and actions as briefly as possible. It contains references to RFC2911 sections for those who want the bloody details. Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 Though the printer is part of the schema I thought we would start with the Job and "PrintJobTicket" discussion. I have uploaded a version of a Printer Schema. I also have done some work modeling the operations and their associated messages. They are not ready to be shared yet. The Printer: "ftp://pwg.org/pub/pwg/Semantic_model/Printer.xsd" The Printer Description attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterDescription.xsd" The Printer's Job Template attributes are represented in the schema as the combination of PrinterDefaults, PrinterSupported and PrinterReady: The PrinterDefaults attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterDefaults.xsd" The PrinterSupported attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterSupported.xsd" The PrinterReady attributes(i.e. XML elements) for the Printer: "ftp://pwg.org/pub/pwg/Semantic_model/PrinterReady.xsd" From KOcke at crt.xerox.com Tue May 28 08:13:01 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific Message-ID: All, I will not be able to make today's teleconference; I have another commitment. So, we can either delay the reference and offramp schema discussion, or you can begin to tear them apart and forward me the results; I'm fine with either approach. Sorry for the late notice about not being able to attend. Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Tuesday, May 21, 2002 4:32 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 28 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Don Wright Bob Taylor Don Levinstone Lee Farrell Ira McDonald 05/28/02 Agenda 1) review template attributes 2) review Target Device Identifier and Reference schema 3) Review actions 05/21/02 Agenda: 1) Review Latest Selected Logical View Report (psi051505). Minutes: 1) Reviewed how Peter's IPP attributes document relates to PSI. Most map to attributes, however, last document takes the place of invoke complete as a Boolean parameter. Attributes schemas: Job Attributes - Apply to the entire Job and all the documents Document Attributes - Overall general characteristics of a document Template Attribute - Name is a left over from IPP. We think processing attributes might be a better name. These a things like number of copies, N-up etc. Requested Attributes - inherit from Job & Template attributes Exception Attributes - List of attributes and values that the device does not support. 2) Dave did a quick review of the latest PSI spec (psi_spec051502). Group agreed to and accept changes/revisions from previous reviews. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue May 28 12:16:00 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A17@mailsrvnt02.enet.sharplabs.com> Hi folks, Sorry - I also had to miss this morning's telecon. Will there be a telecon next Tuesday (5 June)? Cheers, - Ira McDonald -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, May 28, 2002 8:13 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific All, I will not be able to make today's teleconference; I have another commitment. So, we can either delay the reference and offramp schema discussion, or you can begin to tear them apart and forward me the results; I'm fine with either approach. Sorry for the late notice about not being able to attend. Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Tuesday, May 21, 2002 4:32 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/21, next 5/28 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday May 28 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Kirk Ocke Peter Zehler Don Wright Bob Taylor Don Levinstone Lee Farrell Ira McDonald 05/28/02 Agenda 1) review template attributes 2) review Target Device Identifier and Reference schema 3) Review actions 05/21/02 Agenda: 1) Review Latest Selected Logical View Report (psi051505). Minutes: 1) Reviewed how Peter's IPP attributes document relates to PSI. Most map to attributes, however, last document takes the place of invoke complete as a Boolean parameter. Attributes schemas: Job Attributes - Apply to the entire Job and all the documents Document Attributes - Overall general characteristics of a document Template Attribute - Name is a left over from IPP. We think processing attributes might be a better name. These a things like number of copies, N-up etc. Requested Attributes - inherit from Job & Template attributes Exception Attributes - List of attributes and values that the device does not support. 2) Dave did a quick review of the latest PSI spec (psi_spec051502). Group agreed to and accept changes/revisions from previous reviews. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk 2) Add Document Reference as discussed to next rev of spec. - Dave 3) Send out class attribute structure - Peter Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From PZehler at crt.xerox.com Wed May 29 16:03:43 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:14 2009 Subject: PS> PWG Semantic Model Overview Message-ID: All, As promised here is a pointer to an initial version of a PWG Semantic Model Overview document. This version is limited to RFC2911. It is a very concise semantic guide for those of us who are not IPP experts. It describes the model, objects, attributes and actions as briefly as possible. It contains references to RFC2911 sections for those who want the bloody details. The pdf version of the PWG Semantic Model Overview document can be found at: "ftp://pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-Overview.pdf" Please use this version for any comments since it has line numbers. An MS Word version of the document is available in the same directory with a similar file name (.doc instead of .pdf). Comments welcomed, Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 From alan_berkema at hp.com Thu May 30 17:24:18 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD0FB@xrose03.rose.hp.com> *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Sat Jun 1 18:42:39 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> RFC 3282 - Content Language Header Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A19@mailsrvnt02.enet.sharplabs.com> Hi folks, For HTTP and other protocols, here's the Content-Language header definition. Available at: ftp://ftp.isi.edu/in-notes/rfc3282.txt Cheers, - Ira McDonald High North Inc --------------------------------------------------------- [from RFC 3282] Abstract This document defines a "Content-language:" header, for use in cases where one desires to indicate the language of something that has RFC 822-like headers, like MIME body parts or Web documents, and an "Accept-Language:" header for use in cases where one wishes to indicate one's preferences with regard to language. From imcdonald at sharplabs.com Sun Jun 2 12:38:41 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> UDDI LDAP Schema I-D v0.1 (31 May 2002) Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A1A@mailsrvnt02.enet.sharplabs.com> Hi folks, A set of attributes and classes (see excerpts below) for UDDI (Universal Description, Discovery, and Integration) business and service objects stored in LDAP directories. Worth reading. ftp://ftp.ietf.org/internet-drafts/draft-bergeson-uddi-ldap-schema-01.txt Cheers, - Ira McDonald High North Inc ---------------------------- [excerpts] 5. Attribute Type Definitions The following attribute types are defined in this document: uddiBusinessKey uddiAuthorizedName uddiOperator uddiName uddiDescription uddiDiscoveryURLs uddiUseType uddiPersonName uddiPhone uddiEMail uddiSortCode uddiTModelKey uddiAddressLine uddiIdentifierBag uddiCategoryBag uddiKeyedReference uddiServiceKey uddiBindingKey uddiAccessPoint uddiHostingRedirector uddiInstanceDescription uddiInstanceParms uddiOverviewDescription uddiOverviewURL uddiFromKey uddiToKey uddiUUID uddiIsHidden 6. Object Class Definitions The following object classes are defined in this document: uddiBusinessEntity uddiContact uddiAddress uddiBusinessService uddiBindingTemplate uddiTModelInstanceInfo uddiTModel uddiPublisherAssertion From KOcke at crt.xerox.com Tue Jun 4 09:47:21 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: offramp.xsd Type: application/octet-stream Size: 4760 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020604/14b8df3d/offramp-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 3325 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020604/14b8df3d/reference-0001.obj From KOcke at crt.xerox.com Tue Jun 4 12:27:14 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 2982 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020604/ab3cd1c5/reference-0001.obj From imcdonald at sharplabs.com Wed Jun 5 13:43:25 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A1D@mailsrvnt02.enet.sharplabs.com> Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From KOcke at crt.xerox.com Thu Jun 6 08:58:10 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: Ira, good comments. The "type" attribute was related to the document format, not the FTP transfer mode, and it was removed since "document-format" is specified elsewhere. However, you make a good point, namely, that if the client knows that the transfer mode should be text or binary it would be useful to specify it. So, I propose adding a "type" attribute to the "ftp" element with those semantics (will not include directory lookup since that is not applicable). I'm not sure that the IANA Charset is needed. I think simply allowing a client to specify text/binary is sufficient. Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From KOcke at crt.xerox.com Thu Jun 6 10:31:20 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> Updated offramp and reference schemas Message-ID: All, here are the latest updates. The changes include Ira's recent feedback (see below), addition of some annotations, changing all references to ipAddress to host and changing ipAddressType to hostType. Questions: the pathType has an attribute that specifies the OS. Is there a well defined (preferably IANA) list of OS's or file systems that would be appropriate here? Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 -------------- next part -------------- A non-text attachment was scrubbed... Name: offramp.xsd Type: application/octet-stream Size: 4757 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020606/53009ddd/offramp-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 3972 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020606/53009ddd/reference-0001.obj From imcdonald at sharplabs.com Thu Jun 6 13:32:56 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A23@mailsrvnt02.enet.sharplabs.com> Hi Kirk, OK - the IANA charset (on reflection) is conveyed in the 'charset' parameter of the MIME media type specified in the 'document-format' attribute (and defaults if omitted to implementation defined charset guessing - which is not very good). What if PSI tightened up and said the 'charset' parameter SHOULD be specified (whenever known by the invoking client)? Cheers, - Ira McDonald High North Inc -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, June 06, 2002 8:58 AM To: 'McDonald, Ira'; Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Ira, good comments. The "type" attribute was related to the document format, not the FTP transfer mode, and it was removed since "document-format" is specified elsewhere. However, you make a good point, namely, that if the client knows that the transfer mode should be text or binary it would be useful to specify it. So, I propose adding a "type" attribute to the "ftp" element with those semantics (will not include directory lookup since that is not applicable). I'm not sure that the IANA Charset is needed. I think simply allowing a client to specify text/binary is sufficient. Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Thu Jun 6 13:46:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> Updated offramp and reference schemas [OS names] Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A24@mailsrvnt02.enet.sharplabs.com> Hi Kirk, Yes, there's an IANA registry of operating system names. It is now referenced in the IPP Driver Install spec: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipp-install-04.txt The IPP Driver Install spec defines a composite Printer attribute named "client-print-support-files-supported", which in turn defines the 'field': "os-type" One or more REQUIRED comma-separated LOWER-CASE 'keyword' strings identifying the operating system types supported by this set of Client Print Support Files. Valid values are the operating system names defined in the IANA document [os-names] and the special keyword value: 'unknown'. Although the IANA registry requires that the names be all upper-case, the values MUST be all lower case in this field (plus hyphen-minus (-), period (.), and slash (/)). Examples: 'linux', 'linux-2.2', 'os/2', 'sun-os-4.0', 'unix', 'unix-bsd', 'win32', 'windows-95', 'windows-98', 'windows-ce', 'windows-nt', 'windows-nt-4', 'windows-nt-5', 'unknown'. Here's a note from IANA on this topic: The Operating System Names registry has moved to the following: http://www.iana.org/assignments/operating-system-names For all registries, please see the following: http://www.iana.org/numbers.htm Cheers, - Ira McDonald High North Inc -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Thursday, June 06, 2002 10:31 AM To: 'a PSI pwg.org' Subject: PS> Updated offramp and reference schemas All, here are the latest updates. The changes include Ira's recent feedback (see below), addition of some annotations, changing all references to ipAddress to host and changing ipAddressType to hostType. Questions: the pathType has an attribute that specifies the OS. Is there a well defined (preferably IANA) list of OS's or file systems that would be appropriate here? Kirk -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, June 05, 2002 1:43 PM To: 'Ocke, Kirk J'; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Hi Kirk, You removed 'type' from 'ftp'? Standard FTP URLs have defined a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to distinguish a directory lookup from ascii or binary file transfer. Don't we need the IANA charset (if known) and the text/binary mode for transfer of FTP resources in PSI (note that depending on filename extensions in the FTP resource is unreliable for determinate selection of text/binary mode). Cheers, - Ira ---------------------------------- [excerpt from RFC 1738, pages 7 to 8] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: //...//;type= Where through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The part ";type=" may be omitted. The and parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 12:27 PM To: Ocke, Kirk J; 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Here is the updated reference.xsd with the following changes. 1) ipAddressType Changed to hostType, 2) type attribute removed, 3) removed referenceRunList, 4) Did not change ip_addr attribute since the ipAddressType defines an element, 5) did not add annotations refereing to BT BP Profile. -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Tuesday, June 04, 2002 9:47 AM To: 'a PSI pwg.org' Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific Updated reference.xsd and offramp.xsd Kirk -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, May 30, 2002 5:24 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific *NOTE NEW phone number and webex number* PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 4 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below Attendees: Alan Berkema Gail Songer Dave Hall Jerry Thasher Harry Lewis Ted Tronson Peter Mierau Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions 05/28/02 Agenda: 1) Review PWG attribute schemas. Minutes: 1) Peter walked us through the XML schema for IPP attributes. Need to figure out exactly how these fit into the PSI spec. 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Fri Jun 7 12:13:16 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: Updated docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD128@xrose03.rose.hp.com> psi060602.pdf == psi-model-view.pdf psi-spec28.pdf == psi-spec-latest.pdf reference060502.xsd offramp060502.xsd cheers, Alan From alan_berkema at hp.com Fri Jun 7 13:30:22 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: next 6/11 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD12C@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 11 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 06/11/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Fri Jun 7 17:17:28 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 6/4/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD131@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler *Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell *Don Wright *Kirk Ocke * = attendance 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions Minutes: 1) Review Reference Schema Spent the entire time working on this schema. Kirk updated the previous version to include all of the Bluetooth attribute except for new_sheet and billing_code since these are covered in other attributes. on[status_code] was also not included since there is no way to specify on* in a schema. Would need to list all onxxx codes individually and this did not seem worthwhile, we can add more if we need them. Some discussion on why we are specifying attributes vs. just saying URL is all you need, add if you need attributes, URLs already allow for syntax to include anything that is needed. Overall the group decided to keep this more explicit reference schema since it provides guidelines for what is actually intended. Also since a URL is allowed it does not preclude the other method. Kirk has updated the schema based on this discussion. Question on the time, does it include the Time Zone? I think that for time to be useful we should mandate a time zone. Thanks, Alan 05/21/02 Actions: 1) Dave to send Alan latest versions of psi_spec and psi to post. Status: Done. 2) Peter to post and announce template attributes to new PWG location Status: Done 3) Kirk to send Alan or post latest Target Device & Reference schema Status: Done Actions from F2F: 1) Define Off-Ramp Identifier Schema - Dave & Kirk Status: Needs Review 2) Add Document Reference as discussed to next rev of spec. - Dave Status: Kirk working on this, needs review. 3) Send out class attribute structure - Peter Status: Done. 4) Send out Status schema - Peter 5) Define Job Attributes for Get Jobs - Peter Status: Done 6) Look at UPDF for Extended Attribute Definition - all Actions from call - 7) IPP returns status from it's operations. How does PSI WSDL status happen from exceptions thrown via SOAP when done with Java or C etc? May need an explicit status return value - Dave From alan_berkema at hp.com Mon Jun 10 17:44:00 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]:Time Zone next 6/11 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD13B@xrose03.rose.hp.com> From: http://www.w3.org/TR/xmlschema-2/#dateTime dateTime3.2.7 dateTime dt_dateTime[Definition:] dateTime represents a specific instant of time. The ?value space? of dateTime is the space of Combinations of date and time of day values as defined in ? 5.4 of [ISO 8601] . dateTime_lexical_repr3.2.7.1 Lexical representation A single lexical representation, which is a subset of the lexical representations allowed by [ISO 8601] , is allowed for dateTime. This lexical representation is the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e the format ss.ss... with any number of digits after the decimal point is supported. The fractional seconds part is optional; other parts of the lexical form are not optional. To accommodate year values greater than 9999 additional digits can be added to the left of this representation. Leading zeros are required if the year value would otherwise have fewer than four digits; otherwise they are forbidden. The year 0000 is prohibited. The CCYY field must have at least four digits, the MM, DD, SS, hh, mm and ss fields exactly two digits each (not counting fractional seconds); leading zeroes must be used if the field would otherwise have too few digits. This representation may be immediately followed by a "Z" to indicate Coordinated Universal Time (UTC) or, to indicate the time zone, i.e. the difference between the local time and Coordinated Universal Time, immediately followed by a sign, + or -, followed by the difference from UTC represented as hh:mm (note: the minutes part is required). See ISO 8601 Date and Time Formats (?D) for details about legal values in the various fields. If the time zone is included, both hours and minutes must be present. For example, to indicate 1:20 pm on May the 31st, 1999 for Eastern Standard Time which is 5 hours behind Coordinated Universal Time (UTC), one would write: 1999-05-31T13:20:00-05:00. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Friday, June 07, 2002 10:30 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]: next 6/11 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 11 (USA) Through June USA) Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 06/11/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Jun 11 13:06:19 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> IPP Event Notification Subscription and Delivery documents Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A2F@mailsrvnt02.enet.sharplabs.com> Hi folks, Per our brief topic of printer/job event notifications during today's PSI Telecon, below are references for the related IPP documents: Cheers, - Ira McDonald High North Inc --------------------------------------------------------------------------- [list of IPP Printer and Job events] printer-state-changed printer-restarted printer-shutdown printer-stopped printer-config-changed printer-media-changed printer-finishings-changed printer-queue-order-changed job-state-changed job-created job-completed job-stopped job-config-changed job-progress [page level events] --------------------------------------------------------------------------- "Internet Printing Protocol (IPP): IPP Event Notifications and Subscriptions", J. Martin, T. Hastings, R. Herriot, S. Isaacson, R deBry, R. Bergman, Michael Shepherd, 11/28/2001, [defines the IPP Subscription object and the Subscription Attributes group for IPP "job creation" operations] "Internet Printing Protocol (IPP): Job Progress Attributes", T. Hastings, R Bergman, R. Bergman, 07/23/2001, [defines the page-level job events, which should only be delivered via a low-latency protocol] "Internet Printing Protocol (IPP): The 'mailto:' Delivery Method for Event Notifications", T. Hastings, R. Herriot, Carl-Uno Manros, Henrik Holst, 07/23/2001, [defines new Subscription attributes for email and the packaging of IPP email event notifications - in plaintext with optional additional MIME body parts] "Internet Printing Protocol (IPP):The 'indp' Delivery Method for Event Notifications and Protocol/1.0", T. Hastings, Hugo Parra, 07/23/2001, [defines a low-latency event delivery method using 'reverse HTTP' (client acts as mini-HTTP-server and receives incoming connections from Printer or Event Notification Server for delivery of events.] All of the above are available from the IETF server in the directory ftp://ftp.ietf.org/internet-drafts/ and the PWG Server in the directory ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ ONLY on the PWG server, also see 'ippget' (strangely, only this _one_ IPP I-D was just deleted from the I-D directory last week, although it is currently under IESG consideration): "Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications", R. Herriot, T. Hastings, C. Kugler, 11/19/2001, [defines an in-band event delivery method, where client either polls Printer when directed (with server next-poll hints) OR (optional) uses "long" operations with multiple HTTP Responses (for a server to client stream of events)] --------------------------------------------------------------------------- [excerpt from the IPP Notifications spec table of contents] 5 Subscription Object.............................................16 5.1 Rules for Support of Subscription Template Attributes.........17 5.2 Rules for Processing Subscription Template Attributes.........18 5.3 Subscription Template Attributes..............................22 5.3.1 notify-recipient-uri (uri) OR notify-pull-method (type2 keyword)...............................................25 5.3.1.1 notify-recipient-uri (uri)................................25 5.3.1.2 notify-pull-method (type2 keyword)........................25 5.3.2 notify-events (1setOf type2 keyword)........................26 5.3.2.1 Standard Values for Subscribed Events.....................26 5.3.2.1.1 No Events...............................................27 5.3.2.1.2 Subscribed Printer Events...............................27 5.3.2.1.3 Subscribed Job Events...................................29 5.3.2.2 Rules for Matching of Subscribed Events...................30 5.3.2.2.1 Rules for Matching of Printer Events....................30 5.3.2.2.2 Rules for Matching of Job Events........................31 5.3.2.2.3 Special Cases for Matching Rules........................31 5.3.3 notify-attributes (1setOf type2 keyword)....................32 5.3.4 notify-user-data (octetString(63))..........................34 5.3.5 notify-charset (charset)....................................34 5.3.6 notify-natural-language (naturalLanguage)...................35 5.3.7 notify-lease-duration (integer(0:67108863)).................35 5.3.8 notify-time-interval (integer(0:MAX)).......................36 5.4 Subscription Description Attributes...........................38 5.4.1 notify-subscription-id (integer (1:MAX))...................38 5.4.2 notify-sequence-number (integer (0:MAX))....................39 5.4.3 notify-lease-expiration-time (integer(0:MAX))...............39 5.4.4 notify-printer-up-time (integer(1:MAX)).....................40 5.4.5 notify-printer-uri (uri)....................................41 5.4.6 notify-job-id (integer(1:MAX))..............................41 5.4.7 notify-subscriber-user-name (name(MAX)).....................42 6 Printer Description Attributes Related to Notification..........42 6.1 printer-state-change-time (integer(1:MAX))....................43 6.2 printer-state-change-date-time (dateTime).....................43 7 New Values for Existing Printer Description Attributes..........43 7.1 operations-supported (1setOf type2 enum)......................43 8 Attributes Only in Event Notifications..........................44 8.1 notify-subscribed-event (type2 keyword).......................44 8.2 notify-text (text(MAX)).......................................45 9 Event Notification Content......................................45 9.1 Content of Machine Consumable Event Notifications.............48 9.1.1 Event Notification Content Common to All Events.............48 9.1.2 Additional Event Notification Content for Job Events........50 9.1.3 Additional Event Notification Content for Printer Events....51 9.2 Content of Human Consumable Event Notification................51 9.2.1 Event Notification Content Common to All Events.............52 9.2.2 Additional Event Notification Content for Job Events........54 9.2.3 Additional Event Notification Content for Printer Events....55 From alan_berkema at hp.com Tue Jun 11 15:49:49 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: next 6/18 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD142@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 18 (USA) No Call June 25 (F2F June 26) Through June USA) No Call July 2 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 06/18/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Jun 11 16:49:32 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 6/11/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD144@xrose03.rose.hp.com> Apologies for missing Ira last week. PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson *Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone *Lee Farrell Don Wright *Kirk Ocke *Ira Mcdonald * = attendance 06/04/02 Agenda 1) review Target Device Identifier and Reference schema 2) Spec updates with attributes? 3) Review actions Minutes: 1) Review Reference Schema passwd and User could apply to any of the "choice" elements Kirk will think about elevating these to be reference attributes instead of at the child element level. Ira mentioned the need for a security "certificate" attribute. Time attribute - discussion started around time zone and lead to -> should this actually be a duration time instead. Actual time should be handeled at higher application layers. Could even be detrimental at the reference layer if devices are out of sync. Talked about adding additional elements for e-mail Kirk to investigate IMAP RFC 2192, SMTP RFC 2368 and POP3 RFC 2384 2) Review psi specs. Decided to adopt the new methods: InvokeJobWithContentByReference InvokeJobWithContentByValue Except that we decided to remove the last_document paramater. This discussion raised the topic of event notification. Will PSI address this? Needs further investigation. IPP is strugelling with too many optional notfication methods need to scale this down if it will be used with PSI. Subscription for events can occuur at the: o Printer Level o Job level o Job page level, this (if included) should not use high latency methods. Also need to consider existing industry methods such as JMS 0) Job Control Interface starting to stabilize Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security Finish all that and PSI is done :) New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thouts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave Thanks, Alan From imcdonald at sharplabs.com Wed Jun 12 14:48:27 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> Thoughts on Discovery for PSI Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A34@mailsrvnt02.enet.sharplabs.com> Hi folks, It seems to me that PSI usage scenarios that require discovery (essentially all of them) separate into two broad classes, just like discovery for IPP: 1) Discovery of available 'public' print services (for example, while staying in a hotel) - public registries of services like UDDI (the future practice, not the current state of deployment) would work well here - but UDDI doesn't give any help solving the 'locality of reference' problem (that is, you don't want to find a 'public' print service in Timbuktoo - you want one _very_ close to your roaming handheld geographically) - SLPv2 (RFC 2608) with Gateway Directory Agents (an extension currently under development at Columbia University) would also work (if widely deployed in the future) 2) Discovery of available 'private' print services (within a single administrative domain - for example, an enterprise LAN) - SLPv2 (RFC 2608) would work well (using the existing 'printer' SLP schema) - LDAPv3 would work well (using the existing 'printer' LDAP schema, which is technically aligned with the SLP 'printer' schema) - DNS SRV (service) records would also work well (but they burden the enterprise DNS and administrators much more than SLPv2 does) - dozens of proprietary discovery services, like Microsoft SSDP, would also probably work (but they're usually impossible to successfully deploy across a heterogenous enterprise LAN). For those interested learning more about remote discovery via SLPv2 see: ftp://ftp.ietf.org/internet-drafts/draft-zhao-slp-remote-da-discovery-03.txt (26 March 2002) Cheers, - Ira McDonald High North Inc From harryl at us.ibm.com Fri Jun 14 16:05:03 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:14 2009 Subject: PS> Alternative JDF derived Job Ticket Message-ID: Peter recently posted a PWG Job Ticket proposal derived from IPP attributes. While I wholeheartedly support establishing and leveraging the PWG Semantic Model (and deriving it largely from IPP)... I want to bring to the attention of PWG members that there is already a robust XML Job Ticket defined by the CIP4 JDF working group. http://www.cip4.org/ JDF has it's roots in Graphic Arts and Workflow and , in it's full definition, the JDF JT is not as simple as what Peter is proposing. The JDF JT incorporates aspects of the Adobe Portable Job Ticket Format and addresses things like order of operations, has longevity and facilitates job tracking and accounting. Nonetheless, the JDF Job Ticket can be reduced and simplified. Because the JDF job ticket is already gaining acceptance in some industry segments and overlaps with our goals to a degree, I suggest we consider either basing our Job Ticket definition on JDF (see link to simple example, below) or, at least, assure a simple mechanical XSLT mapping between the two. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020614/5334d6e1/attachment-0001.html From alan_berkema at hp.com Fri Jun 14 17:31:22 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> Another view of the PWG semantic model Message-ID: <499DC368E25AD411B3F100902740AD650E6AD156@xrose03.rose.hp.com> Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From imcdonald at sharplabs.com Sun Jun 16 16:43:32 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> [PDF version] Another view of the PWG semantic model Message-ID: <116DB56CD7DED511BC7800508B2CA5370A1A39@mailsrvnt02.enet.sharplabs.com> Hi folks, I distilled this MS Word file (see below) and converted it to PDF and stored it in the same directory at: ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.pdf (I just tested the above link, to make sure it works correctly) Comments on Alan's alternative proposal will probably be easier to correlate it they reference the line-numbered PDF version above. Cheers, - Ira McDonald High North Inc -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From pmierau at adobe.com Mon Jun 17 12:37:58 2002 From: pmierau at adobe.com (Peter Mierau) Date: Wed May 6 14:02:14 2009 Subject: PS> Alternative JDF derived Job Ticket In-Reply-To: Message-ID: <4.3.2.7.2.20020617093432.01d14a50@mailsj.corp.adobe.com> Harry, I agree with you that JDF job tickets can be quite suitable for enterprise printing such as PSI. And if there happen to be any deficiencies, a "psi" namespace could be used to add functionality to it. I'm sure the CIP4 would also entertain changing the JDF spec to better suit the PSI needs, too. Like you mentioned, though, the JDF spec is quite large and can be daunting to absorb, even though we'd only be interested in a fraction of it for enterprise printing. At 02:05 PM 6/14/2002 -0600, Harry Lewis wrote: >Peter recently posted a PWG Job Ticket proposal derived from IPP >attributes. While I wholeheartedly support establishing and leveraging the >PWG Semantic Model (and deriving it largely from IPP)... I want to bring >to the attention of PWG members that there is already a robust XML Job >Ticket defined by the CIP4 JDF working group. >http://www.cip4.org/ > >JDF has it's roots in Graphic Arts and Workflow and , in it's full >definition, the JDF JT is not as simple as what Peter is proposing. The >JDF JT incorporates aspects of the Adobe Portable Job Ticket Format and >addresses things like order of operations, has longevity and facilitates >job tracking and accounting. Nonetheless, the JDF Job Ticket can be >reduced and simplified. > >Because the JDF job ticket is already gaining acceptance in some industry >segments and overlaps with our goals to a degree, I suggest we consider >either basing our Job Ticket definition on JDF (see link to simple >example, below) or, at least, assure a simple mechanical XSLT mapping >between the two. > >ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml >---------------------------------------------- >Harry Lewis >IBM Printing Systems >---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020617/1f613167/attachment-0001.html From PZehler at crt.xerox.com Mon Jun 17 14:29:01 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:14 2009 Subject: PS> PWG semantic model document version for PWG meeting Message-ID: All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" MS Word version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc" Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From alan_berkema at hp.com Tue Jun 18 18:08:57 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> RE: [PSI]: minutes 6/11/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD167@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema Gail Songer *Dave Hall *Jerry Thasher Harry Lewis Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone *Lee Farrell *Don Wright *Kirk Ocke *Ira Mcdonald * = attendance 06/18/02 Agenda 1) Review Target Device Identifier and Reference schema 2) Review PWG Semantic model with consideration for PSI Minutes: 1) Review Target Device Identifier and Reference schema Postponed to F2F 2) Review PWG Semantic model with consideration for PSI Spent most of the meeting talking about the PWG Semantic model using rev 06-020617. Started with Figure 5. Is this just an example of how Attributes could be used or is this the actual model? PSI is very close to this except that PSI has separated out Job and Content Objects. Talked about 3 levels of the Semantic Model 1) Base Attribute Definitions 2) Structure Definitions 3) Base Operational Model For PSI JobAttributes, ContentAttributes, RenderingAttributes, FinishingAttributes and ImpositionAttributes are all Base Level Attribute groupings. The Base Attributes are defined within each of these. Job and Processing are structures which import the Base Level Attribute groupings. General discussion on grouping indicated a desire for the appropriate level of granularity. One extreme would be no grouping at all, just attribute defs like words in a dictionary, while this has some value since we would all have the same definitions, it does not move the model forward for interoperability and reuse. It looses the semantic meaning. Another extreme is to group them all together. This would be too much for some applications and might still not be enough for others. Need a compromise that could allow profiles to structure the Base level groupings in a way that suits the application. Also decided that Fidelity should be part of Job as well as Content. See ya next week, Alan ---- 0) Job Control Interface starting to stabilize Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security Finish all that and PSI is done :) New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thouts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave Thanks, Alan From alan_berkema at hp.com Thu Jun 20 15:46:04 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> PSI Minutes from -- Apr '02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD171@xrose03.rose.hp.com> Lee sent this a while back while I was in Barcelona, just remembered to pass them along. Will also post. Thanks Lee! Will need a volunteer for next week. Alan -----Original Message----- From: Farrell, Lee [mailto:Lee.Farrell@cda.canon.com] Sent: Wednesday, May 01, 2002 7:47 PM To: PSI (E-mail) Subject: PS> PSI Meeting Notes -- Apr '02 <> =========================== Lee Farrell Canon Development Americas 110 Innovation Drive Irvine, CA 92612 (949) 856-7163 - voice (949) 856-7510 - fax lee.farrell@cda.canon.com =========================== -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI Meeting Notes 020416.pdf Type: application/octet-stream Size: 20065 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020620/5cc01cf3/PSIMeetingNotes020416-0001.obj From hastings at cp10.es.xerox.com Thu Jun 20 19:37:02 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:14 2009 Subject: PS> Comments on the PWG Semantic Model document version 0.06, dated J une 17, 2002 Message-ID: <918C79AB552BD211A2BD00805F15CE8506DF43A4@x-crt-es-ms1.cp10.es.xerox.com> Here are my comments on the document. Unfortunately, I won't be able to be at either the PSI or the PWG meeting to discuss. Have a good meeting. 1. The WG should consider whether the 10-page summary of the attributes in section 2.3 (pages 14 through 23) should be moved back to the appendix where the summary of the actions is. Then section 2 will be reduced from 18 pages to 9 pages (pages 6-14) on the Data Class attributes. The figures in section 2 give the names of the attributes and how they are grouped which gives the reader a good overview of the attribute and object part of the model. With such a move, section 3 Actions and 4 status codes combined will be roughly the same size at 6 pages (pages 24-29) as section 2 (9 pages). This was Melinda Grant's suggestion which was put into version 0.2, 5/23/02. 2. The use of the term "Content" instead of "Document" in attribute and object names seems a step backwards and will lead to confusion with the existing standards that have already incorporated IPP semantics into them, such as IPP, UPnPv1, Bluetooth, and the OMG Print Facility, and the implementations of these standards. Also ISO DPA used the term Document. The PWG will look silly progressing a Semantic Model that covers a lot of existing and future practice, if we change the commonly used terminology. If the reason for the change is to allow other types of electronic representation to be submitted in a print job, such as fonts, forms, logos, etc., we can add a "DocumentType" attribute which indicates the type as: 'printable', 'font', 'form', 'logo', etc. This is what ISO DPA did. 3. Page 9, section 2.2, Page 12, section 2.2.2 Figure 8, and page 15, section 2.3.2 Job Attribute: The Job attributes that a client supplies the values for should not be grouped with the Job attributes that the Printer alone sets. The latter could be called Job Description attributes, as in IPP and the former called just Job Attributes. More comments later. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, June 17, 2002 11:29 To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; ps@pwg.org; pwg@pwg.org Subject: PS> PWG semantic model document version for PWG meeting All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" MS Word version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc" Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From KOcke at crt.xerox.com Fri Jun 21 10:12:51 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> NEW reference.xsd and targetDevice.xsd Message-ID: Alan, et. al., here are the promised updated to the schemas. I have not put detailed annotations into the schemas yet, but the new elements have names that are taken directly from the standards they refer to (e.g., uid element in imap element in reference.xsd taken directly from uid definition in IMAP RFC). I'll add annotations post the face to face meeting. Kirk From KOcke at crt.xerox.com Fri Jun 21 10:28:45 2002 From: KOcke at crt.xerox.com (Ocke, Kirk J) Date: Wed May 6 14:02:14 2009 Subject: PS> NEW reference.xsd and targetDevice.xsd Message-ID: With attachments this time ;-) -----Original Message----- From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com] Sent: Friday, June 21, 2002 10:13 AM To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'a PSI pwg.org' Subject: PS> NEW reference.xsd and targetDevice.xsd Alan, et. al., here are the promised updated to the schemas. I have not put detailed annotations into the schemas yet, but the new elements have names that are taken directly from the standards they refer to (e.g., uid element in imap element in reference.xsd taken directly from uid definition in IMAP RFC). I'll add annotations post the face to face meeting. Kirk -------------- next part -------------- A non-text attachment was scrubbed... Name: targetDevice.xsd Type: application/octet-stream Size: 6165 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020621/cea6a91f/targetDevice-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: reference.xsd Type: application/octet-stream Size: 6598 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020621/cea6a91f/reference-0001.obj From alan_berkema at hp.com Fri Jun 21 17:21:15 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> PSI Agenda 6/26/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD179@xrose03.rose.hp.com> All: Here is a proposed agenda for the PSI F2F on Wednesday I. Introductions II. Review and Approve minutes from April (ftp://ftp.pwg.org/pub/pwg/ps/PSIMeetingNotes020416.pdf) III. Review Agenda III. Review Action Items IV. New PSI Overview Diagram (slide and in rev29 spec.) V. Review PSI Selected Logical View (ftp://ftp.pwg.org/pub/pwg/ps/psi062102.pdf) VI. Review PSI Spec (ftp://ftp.pwg.org/pub/pwg/ps/psi-spec29.pdf) VII. Review reference schema (ftp://ftp.pwg.org/pub/pwg/ps/reference062102.xsd) VIII. Review targetDevice schema (ftp://ftp.pwg.org/pub/pwg/ps/targetDevice062102.xsd) IX. Discuss Attributes X. Discuss New Work Items X1. Plan Forward & teleconference schedule with respect to Holidays & Vacations (Thanks for the format Don :) Alan From hastings at cp10.es.xerox.com Tue Jun 25 11:45:47 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:14 2009 Subject: PS> Rest of my comments on the Message-ID: <918C79AB552BD211A2BD00805F15CE8506DF444D@x-crt-es-ms1.cp10.es.xerox.com> Here are the rest of my comments on the PWG Semantic Model in version 0.06, dated June 17, 2002, "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" 2. (continued) Here are some more arguments in support of using the term "Document", instead of "Content": In the late 1960, there was a fad in system design to invent entirely new terms so that no one could possibly be mis-led into thinking that a term carried along some assumptions from some other usage. However, the result was that no one really understood anyone else, since learning an entirely new vocabulary was much too hard. Bernie Galler from the University of Michigan wrote a letter to the Communications of the ACM, strongly urging system designers to abandon this fad of inventing new terms. Instead, he said use the terms that have a common understanding. Put an adjective in front if you really want to distinguish your term from the common usage. Live with the term including the adjective for a while and see if you still really need the adjective. If you don't, drop the adjective. Either way, be sure to put the term into a terminology section and describe the specifics of the use of the term in your specification. So if the reason for changing the word from "Document" (which all print standards have used) to "Content" is to avoid some kind of unwarranted assumptions or confusions about "Document", just define what is meant by "Document" in the PWG Semantic Model. A Document can be any electronic form of representation that is represented by a MIME Media type, including a text document, an XML representation, an image, etc. If you want to distinguish between the electronic form that is submitted in a print job from the hardcopy form that the Printer produces, you could add adjectives in front of Document. For example, Input Document and Output Document, respectively, as has been done for the Document and Page Overrides specification for IPP. [Comments 1, initial 2, and 3 are below in the earlier email message.] 4. Page 5, section 1, Model Overview, the third sentence, says: "The PWG model describes the device as a Printer object." We also need to clarify, as in RFC 2911, that the communication can be between a desktop and a spooler, a desktop and a printing device, or between a spooler and a printing device. One fix would be to replace the third sentence with something like: The PWG Model represents the entity that accepts print requests as a Printer object. The Printer object can represent a printing device, a spooler, or both. Such a spooler may control one or more devices and spools jobs before forwarding them to one of the printing device. 5. Page 5, bottom of the page. Add the terms "Printer", "Client", "Document" to the list of terms. I suggest capitalizing the first letter when the special term is intended. 6. Page 8, section 2.1.3 "Job Processing" Printer Attributes: I agree that the term "Job Processing" attributes is probably a better term than the IPP Semantic Model "Job Template" attributes term, so this is an OK terminology change (but needs to be added to the IPP mapping appendix). 7. Page 8, Table 1, JobPriority, the "xxxSupported syntax: Change "Integer (MAX value)" to "Integer (number of priority levels)". 8. Page 14, Table 2, Sides: Delete the two last values: 'two-sided-long-edge' [duplicate] and 'tumble' [not defined]. 9. Page 15, Table 2, Media: The reference should be to [RFC2911] "media" appendix, not pwg5101.1. The example should be something like: 'na-letter-white that is defined in RFC 2911. The next two attributes (MediaSize and MediaType) correctly refer to pwg5101.1. 10. Page 25-26, section 3.2.1 PrintJob and PrintUri, could be eliminated and then add a note that some protocols may combine CreateJob and SendDocument into a single operation, called PrintJob and combine CreateJob and SendUri into a single operation, called PrintUri. This will reduce the number of actions in the document (while still covering both IPP and PSI which do have the combined action). 11. Page 31, Appendix - IPP Mapping Change the title of this appendix, so that it is just specifying more detail for the actions as part of the Model. This appendix could eliminate 7.2.1 PrintJob and 7.2.2 PrintUri. Move the details of 7.2.1 PrintJob into 7.2.3 CreateJob. 12. Add a separate (much shorter) appendix that indicates the IPP Mapping to the Model. Either in this Appendix also indicate the PSI Mapping to the PWG Model, or in a separate Appendix. The advantage of having in the same appendix, is that it will be easier to compare the IPP Semantic Model and the PSI semantics. For example, a single table might contain three columns: PWG Model, IPP Semantics, and PSI Semantics. Tom -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Thursday, June 20, 2002 16:37 To: Zehler, Peter; 'BERKEMA,ALAN C (HP-Roseville,ex1)' Cc: ps@pwg.org; pwg@pwg.org Subject: PWG> Comments on the PWG Semantic Model document version 0.06, dated J une 17, 2002 Here are my comments on the document. Unfortunately, I won't be able to be at either the PSI or the PWG meeting to discuss. Have a good meeting. 1. The WG should consider whether the 10-page summary of the attributes in section 2.3 (pages 14 through 23) should be moved back to the appendix where the summary of the actions is. Then section 2 will be reduced from 18 pages to 9 pages (pages 6-14) on the Data Class attributes. The figures in section 2 give the names of the attributes and how they are grouped which gives the reader a good overview of the attribute and object part of the model. With such a move, section 3 Actions and 4 status codes combined will be roughly the same size at 6 pages (pages 24-29) as section 2 (9 pages). This was Melinda Grant's suggestion which was put into version 0.2, 5/23/02. 2. The use of the term "Content" instead of "Document" in attribute and object names seems a step backwards and will lead to confusion with the existing standards that have already incorporated IPP semantics into them, such as IPP, UPnPv1, Bluetooth, and the OMG Print Facility, and the implementations of these standards. Also ISO DPA used the term Document. The PWG will look silly progressing a Semantic Model that covers a lot of existing and future practice, if we change the commonly used terminology. If the reason for the change is to allow other types of electronic representation to be submitted in a print job, such as fonts, forms, logos, etc., we can add a "DocumentType" attribute which indicates the type as: 'printable', 'font', 'form', 'logo', etc. This is what ISO DPA did. 3. Page 9, section 2.2, Page 12, section 2.2.2 Figure 8, and page 15, section 2.3.2 Job Attribute: The Job attributes that a client supplies the values for should not be grouped with the Job attributes that the Printer alone sets. The latter could be called Job Description attributes, as in IPP and the former called just Job Attributes. More comments later. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, June 17, 2002 11:29 To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; ps@pwg.org; pwg@pwg.org Subject: PS> PWG semantic model document version for PWG meeting All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf" MS Word version is available at "ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc" Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan From hastings at cp10.es.xerox.com Tue Jun 25 11:45:44 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:14 2009 Subject: PS> RE: PWG> Agenda for Thursday Plenary - Portland [there's a later PWG Semantic Model] Message-ID: <918C79AB552BD211A2BD00805F15CE8506DF444C@x-crt-es-ms1.cp10.es.xerox.com> Harry, Peter posted a later PWG Semantic Model on 6/17, building on Alan Berkima's version (which built on Peter's previous version). So the agenda should show: ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc (Peter made a typo in the file name: "Mode" instead of "Model", but that is how it is stored.) Thanks, Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Monday, June 17, 2002 11:29 To: 'BERKEMA,ALAN C (HP-Roseville,ex1)'; ps@pwg.org; pwg@pwg.org Subject: PS> PWG semantic model document version for PWG meeting All, I have uploaded the version of the PWG Semantic Model document to be used at the PWG meeting next week. I have taken Allen's version and put back the semantics for Actions but limited it to a high level description. Detailed discussion of parameters remain in a section dedicated to an IPP mapping of the print semantics. I have also done some other minor edits. We will use the PDF version, which has line numbers, in our conversations. The PDF version is available at ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf MS Word version is available at ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, June 14, 2002 5:31 PM To: ps@pwg.org; pwg@pwg.org Subject: PS> Another view of the PWG semantic model Here is another cut at the PWG Semantic Model ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.doc It started with Peter's and attempts to provides a more generic model with the IPP specifics in the Appendix. It also groups the collections of attributes differently. regards, Alan * -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Friday, June 21, 2002 15:26 To: pwg@pwg.org Subject: PWG> Agenda for Thursday Plenary - Portland MORNING 1. Standard Plenary reports 1.1 IPP Update - Harry Lewis 1.2 Printer MIB Update - Harry Lewis 1.3 XHTML-Print Status - Don Wright 1.4 PSI Status - Alan Berkema 1.5 UPDF Status - Norbert Schade 1.6 IPP-FAX Status - Gail Songer 1.7 Misc and Related - As needed 2. Linux and Free Software Group Update 2.1 CUPS, PAPI ftp://ftp.pwg.org/pub/pwg/Related/Linux/papi.pdf 2.1.1 IPP Job Ticket and Capabilities Object Extension ftp://ftp.pwg.org/pub/pwg/ipp/new_JTCO/JTCO_RoughDraft.pdf 2.2 Job Ticket API ftp://ftp.pwg.org/pub/pwg/Related/FSGOpen/ 2.2.1 PWG Job Ticket ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrintJobTicket.xml 2.2.2 JDF Job Ticket ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml 2.2.3 Job Ticket Type supported attribute 3. PWG Semantic Model (Overview and Charter) 3.1 Role Of PWG 3.2 Other groups, other models 3.3 Role of Job Ticket, Capabilities Object ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-Charter-Proposal .pdf ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-Overview.pdf AFTERNOON 4. Adobe Presentation 4.1 TIFF-FX vs. PDF as a common PDL 4.2 Applicability to IETF IFAX, IPP-FAX, other 4.3 Licensing 5. PWG Semantic Model (Review) ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model1161402.pdf 5.1 Correlation 5.1.1 IPP, IPP-FAX, UPDF, PSI, XHTML-Print ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020625/83b68ded/attachment-0001.html From imcdonald at sharplabs.com Tue Jul 2 13:43:42 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> RFC 3288 - SOAP over BEEP (Proposed Standard) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CCE9@mailsrvnt02.enet.sharplabs.com> Hi folks, This RFC was written by W3C folks to specify a (simple, but complete) mapping of W3C Simple Object Access Protocol (SOAP) over the recent IETF Blocks Extensible Exchange Protocol (BEEP), RFC 3080 (March 2001). Note that SOAP over BEEP would be dramatically faster than SOAP over HTTP/1.1, due to BEEPs efficient channel management (versus HTTP). Worth looking at. Cheers, - Ira McDonald High North Inc From alan_berkema at hp.com Mon Jul 8 09:45:19 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> NO PSI Call 7/9/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD181@xrose03.rose.hp.com> Dave and I are both out. regards, Alan From norbertschade at attbi.com Mon Jul 8 10:32:20 2002 From: norbertschade at attbi.com (Norbert Schade) Date: Wed May 6 14:02:14 2009 Subject: PS> Semantic model: media handling Message-ID: <001a01c2268c$4544aa00$a8948018@ne1.client2.attbi.com> I have problems to follow two different ways to specify media handling and UPDF would have problems to support that. I'm fine with the specification of single media attributes like size, type, etc. I agree that there should exist a media instance a level higher, which is a media element with a number of media attributes. The number of attributes can vary. In one sample it may be just size and type, in another it may be something like the IPP media collection. My point is that the attributes a media is described by may vary. There should not be a predefined media collection in a common Semantic Model representing one implementation. Feel free to check the composite feature definition we have in UPDF. Open the UPDF.xsd schema to do this and follow the path down to PrintCapabilities.Features. The current sample description xml of an imaginary LJ9000 has a 'Media' composite feature. We can compose any number of features to a new feature, be it Media, Quality or anything else. This is a very flexible structure and is expected to be used frequently. We got very positive feedback once we finished it last year. We'd appreciate if the Semantic Model does something down that path. Otherwise the spec is ambiguous. Another statement: We've seen the current schema of the Semantic Model. We know there are a number of ways to write schemas. The UPDF group made the experience that working with attributes instead of assigning text to elements directly has advantages. Validation is easier and we can define constraints (these are really constraints and not dependencies) for attributes. You may think that over. Regards Norbert Schade 69 Prescott Drive North Chelmsford, MA 01863 978-251-1017 norbertschade@attbi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020708/ea976b89/attachment-0001.html From alan_berkema at hp.com Sun Jul 14 11:43:40 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: next 7/23 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD184@xrose03.rose.hp.com> PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 23 (USA) No Call July 16 Through August 6 No Call July 2 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/23/02 Agenda TBD ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From hastings at cp10.es.xerox.com Mon Jul 15 19:12:38 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: next 7/23 8:00:am Pacific Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F90806F914@x-crt-es-ms1.cp10.es.xerox.com> Alan, Is there a call August 6 or not? Thanks, Tom -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Sunday, July 14, 2002 08:44 To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> [PSI]: next 7/23 8:00:am Pacific PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday June 23 (USA) No Call July 16 Through August 6 No Call July 2 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/23/02 Agenda TBD ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Meeting Date: 4/2/2002 Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 22027801 Meeting Password: mypsi Host: Alan Berkema 1(916)7855605 From robert_b_taylor at hp.com Tue Jul 16 23:13:37 2002 From: robert_b_taylor at hp.com (TAYLOR,BOB (HP-Vancouver,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> Semantic model: media handling Message-ID: <6D805D4C4567D411AF32009027B683510B40FFA6@xvan02.vcd.hp.com> Hi Norbert, all, One of the things we (HP) have been suggesting for the semantic model is the separation of the raw "attribute/element" definitions from the structures/model that pull them together for a particular use. As you not, UPDF has done this structuring in a different way than IPP - which is also somewhat different than UPnP & PSI, etc. I'm not sure we want to try codify any one structure as part of the core semantic model - these will tend to vary by market segment and domain, and I'm not sure we can do this one-size-fits-all. What we would like to see, though, is common definition of the core "attributes/elements" - this seems much more reusable across models & domains. It does make sense, though, to publish some of the "common models" as at least examples of structural models - IPP, UPDF, etc. are likely candidates for this. This exposes some of useful constructs (such as the composite feature you describe below) for reuse. thanks, bt --------------------------------------------------- Bob Taylor Senior Architect IPG Strategic Technology Development Hewlett-Packard Co. mailto:robertt@vcd.hp.com phone: 360.212.2625/T212.2625 fax: 208.730-5111 --------------------------------------------------- -----Original Message----- From: Norbert Schade [mailto:norbertschade@attbi.com] Sent: Monday, July 08, 2002 7:32 AM To: Print Services group Cc: UPD group Subject: PS> Semantic model: media handling I have problems to follow two different ways to specify media handling and UPDF would have problems to support that. I'm fine with the specification of single media attributes like size, type, etc. I agree that there should exist a media instance a level higher, which is a media element with a number of media attributes. The number of attributes can vary. In one sample it may be just size and type, in another it may be something like the IPP media collection. My point is that the attributes a media is described by may vary. There should not be a predefined media collection in a common Semantic Model representing one implementation. Feel free to check the composite feature definition we have in UPDF. Open the UPDF.xsd schema to do this and follow the path down to PrintCapabilities.Features. The current sample description xml of an imaginary LJ9000 has a 'Media' composite feature. We can compose any number of features to a new feature, be it Media, Quality or anything else. This is a very flexible structure and is expected to be used frequently. We got very positive feedback once we finished it last year. We'd appreciate if the Semantic Model does something down that path. Otherwise the spec is ambiguous. Another statement: We've seen the current schema of the Semantic Model. We know there are a number of ways to write schemas. The UPDF group made the experience that working with attributes instead of assigning text to elements directly has advantages. Validation is easier and we can define constraints (these are really constraints and not dependencies) for attributes. You may think that over. Regards Norbert Schade 69 Prescott Drive North Chelmsford, MA 01863 978-251-1017 norbertschade@attbi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020716/0568c4ca/attachment-0001.html From harryl at us.ibm.com Wed Jul 17 11:34:40 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:14 2009 Subject: PS> Semantic model: media handling Message-ID: I like Bob's analysis. I think the Semantic Model will be most useful taking this approach. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "TAYLOR,BOB (HP-Vancouver,ex1)" Sent by: owner-ps@pwg.org 07/16/2002 09:13 PM To: Norbert Schade , Print Services group cc: UPD group Subject: RE: PS> Semantic model: media handling Hi Norbert, all, One of the things we (HP) have been suggesting for the semantic model is the separation of the raw "attribute/element" definitions from the structures/model that pull them together for a particular use. As you not, UPDF has done this structuring in a different way than IPP - which is also somewhat different than UPnP & PSI, etc. I'm not sure we want to try codify any one structure as part of the core semantic model - these will tend to vary by market segment and domain, and I'm not sure we can do this one-size-fits-all. What we would like to see, though, is common definition of the core "attributes/elements" - this seems much more reusable across models & domains. It does make sense, though, to publish some of the "common models" as at least examples of structural models - IPP, UPDF, etc. are likely candidates for this. This exposes some of useful constructs (such as the composite feature you describe below) for reuse. thanks, bt --------------------------------------------------- Bob Taylor Senior Architect IPG Strategic Technology Development Hewlett-Packard Co. mailto:robertt@vcd.hp.com phone: 360.212.2625/T212.2625 fax: 208.730-5111 --------------------------------------------------- -----Original Message----- From: Norbert Schade [mailto:norbertschade@attbi.com] Sent: Monday, July 08, 2002 7:32 AM To: Print Services group Cc: UPD group Subject: PS> Semantic model: media handling I have problems to follow two different ways to specify media handling and UPDF would have problems to support that. I'm fine with the specification of single media attributes like size, type, etc. I agree that there should exist a media instance a level higher, which is a media element with a number of media attributes. The number of attributes can vary. In one sample it may be just size and type, in another it may be something like the IPP media collection. My point is that the attributes a media is described by may vary. There should not be a predefined media collection in a common Semantic Model representing one implementation. Feel free to check the composite feature definition we have in UPDF. Open the UPDF.xsd schema to do this and follow the path down to PrintCapabilities.Features. The current sample description xml of an imaginary LJ9000 has a 'Media' composite feature. We can compose any number of features to a new feature, be it Media, Quality or anything else. This is a very flexible structure and is expected to be used frequently. We got very positive feedback once we finished it last year. We'd appreciate if the Semantic Model does something down that path. Otherwise the spec is ambiguous. Another statement: We've seen the current schema of the Semantic Model. We know there are a number of ways to write schemas. The UPDF group made the experience that working with attributes instead of assigning text to elements directly has advantages. Validation is easier and we can define constraints (these are really constraints and not dependencies) for attributes. You may think that over. Regards Norbert Schade 69 Prescott Drive North Chelmsford, MA 01863 978-251-1017 norbertschade@attbi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020717/1623e816/attachment-0001.html From alan_berkema at hp.com Mon Jul 22 12:36:42 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: NEW WEBEX Info & Docs - next 7/23 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD188@xrose03.rose.hp.com> New WEBEX meeting number and passwd below. Also new docs posted psi071802.pdf == psi-model-view.pdf psi-spec30.pdf == psi-spec-latest.pdf psi071802.mdl PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday July 23 (USA) No Call July 16 Through August 6 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/23/02 Agenda 1) Review psi-spec30.pdf ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 28877789 Meeting Password: newpsi Host: Alan Berkema 1(916)7855605 From alan_berkema at hp.com Tue Jul 23 12:41:56 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: next 7/30 8:00:am Pacific Message-ID: <499DC368E25AD411B3F100902740AD650E6AD18F@xrose03.rose.hp.com> * Webex and phone number same as last week. * PSI Meeting schedule Teleconference details 2002: Date: Tuesdays Tuesday July 30 (USA) No Call July 16 Through August 6 Time: 8 AM (US PST) 650-690-9360 ID: 55605 (T348-9360) See webex info below 07/30/02 Agenda 1) Review psi-spec31.pdf and continue discussions from 7/23 ----------- 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 Tuesdays use: http://hp.webex.com Then click join unlisted meeting. Use the info below: ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 28877789 Meeting Password: newpsi Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Tue Jul 23 18:58:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:14 2009 Subject: PS> Basic notification events and included attributes Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD07@mailsrvnt02.enet.sharplabs.com> Hi folks, Tuesday (23 July 2002) Per my action item from today's PSI Telecon, here's some information on the basic event notification model from IPP. For more info please see: ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-not-spec-09.txt Cheers, - Ira McDonald High North Inc ---------------------------------------- Printer Event Conformance printer-state-changed REQUIRED printer-restarted OPTIONAL printer-shutdown OPTIONAL printer-stopped REQUIRED printer-config-changed OPTIONAL printer-media-changed OPTIONAL printer-finishings-changed OPTIONAL printer-order-queue-changed OPTIONAL ---------------------------------------- Job Event Conformance job-state-changed REQUIRED job-created REQUIRED job-completed REQUIRED job-stopped OPTIONAL job-config-changed OPTIONAL job-progress OPTIONAL ---------------------------------------- Table 5 - Attributes in Event Notification Content Source Value Sends Source Object notify-subscription-id (integer(1:MAX)) MUST Subscription notify-printer-uri (uri) MUST Subscription notify-subscribed-event (type2 keyword) MUST Event Notification printer-up-time (integer(MIN:MAX)) MUST Printer printer-current-time (dateTime) * MUST Printer notify-sequence-number (integer (0:MAX)) SHOULD Subscription notify-charset (charset) SHOULD Subscription notify-natural-language (naturalLanguage) SHOULD Subscription notify-user-data (octetString(63)) ** SHOULD Subscription notify-text (text) SHOULD Event Notification attributes from the "notify-attributes" MAY Printer attribute *** attributes from the "notify-attributes" MAY Job attribute *** attributes from the "notify-attributes" MAY Subscription attribute *** *A Printer MUST send this value only if and only if it supports the Printer's "printer-current-time" attribute. ** If the Subscription Object does not contain a "notify-user-data" attribute and the Delivery Method Document REQUIRES the Printer to send the "notify-user-data" source value in the Event Notification, the Printer MUST send an octet-string of length 0. *** The last three rows represent additional attributes that a client MAY request via the "notify-attributes" attribute. A Printer MAY support the "notify-attributes" attribute. The Delivery Method MUST say that the Printer MUST, SHOULD, MAY, MUST NOT, SHOULD NOT, or NEED NOT support the "notify-attributes" attribute and specific values of this attribute. The Delivery Method MAY say that support for the "notify-attributes" is conditioned on support of the attribute by the Printer or it MAY say that Printer MUST support the "notify- attributes" attribute if the Printer supports the Delivery Method. ---------------------------------------- Table 6 - Additional Event Notification Content for Job Events Source Value Sends Source Object job-id (integer(1:MAX)) MUST Job job-state (type1 enum) MUST Job job-state-reasons (1setOf type2 keyword) MUST Job job-impressions-completed (integer(0:MAX)) * MUST Job * The Printer MUST send the "job-impressions-completed" attribute in an Event Notification only for the combinations of Events and Subscribed Events shown in Table 7. ---------------------------------------- Table 7 - Combinations of Events and Subscribed Events for "job-impressions-completed" Job Event Subscribed Job Event 'job-progress' 'job-progress' 'job-completed' 'job-completed' 'job-completed' 'job-state-changed' ---------------------------------------- Table 8 - Additional Event Notification Content for Printer Events Source Value Sends Source Object printer-state (type1 enum) MUST Printer printer-state-reasons (1setOf type2 keyword) MUST Printer printer-is-accepting-jobs (boolean) MUST Printer ---------------------------------------- From alan_berkema at hp.com Thu Jul 25 13:12:20 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:14 2009 Subject: PS> [PSI]: minutes 7/23/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1A0@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright *Kirk Ocke *Ira Mcdonald *Amir Shahindoust * = attendance 07/23/02 Agenda 1) Review psi-spec30.pdf Minutes: 1) Review psi-spec30.pdf Ira asked about minutes from the Portland F2F. Unfortunately we do not have a secratary yet and while Jim Sommer volunteered he was only able to attend half of the meeting. He did give his notes for the first half. I while try to provide an overview of the meeting, however, most of the real details of the discussion were captured in psi-spec30.pdf. We still need a secratary for Santa Fe! Started out with a review of psi-spec30.pdf, focusing on unfinished work from the F2F. Since we are aligning with the PWG semantic model Pete said that he would have a new rev of the document and new schemas for us to review in Santa Fe. Next we looked at GetServiceAttributes and exactly what this should return? This folded into GetSelfDescribingServiceAttributes which we decided was better named GetServiceAttributeMetaData. Discussion on whether the return should be an instance document or a schema and do we need both methods? Can we align the two so we do have two different methods with different levels of return values. Decieded that if we return a Schema we can have only one method and for PSI 1.0 it would return a Schema with base level attributes. The Schema could be extended with Meta Data (self decribing type of features) in the future (beyond PSI 1.0). What is UPDFs role in this? How will UPDF harmonize with the semantic model? Talked about the PSI dependency on the semantic model vs. the PSI schedule. Decided that the amount of work involved with the semantic model and it's similar schedule will not add an unreasonable risk to PSI. Determined that formal notification/eventing methods will not be included in the PSI 1.0 spec. Could be considered in a following revision. Security came up again. The goal of PSI is to facilitate existing security methods by including credentials needed by existing methods in appropriate PSI schemas. We do need to consider privilege roles: o End User o Operator o Administrator For example we would not want to allow End Users to cancel other users jobs. When we reviewed the Target Interface we observed that PostStatus, PostJobStatus, PostDocumentStatus are really a lot like a Notifications. We could call these simple notifications and include a Boolean in CreateJob that indicates whether or not the notifications were desired. Formal Notifications, that we decided were post PSI 1.0, would include Notification subscriptions and Cancel subscription methods that add complexity. However if we model our post status as simple notifications then they would naturally fit with the Formal notifications in the future. Simple notifications would only be associated with the life of a CreateJob . Ira took an action to provide information about what IPP uses for notification payload, things like JobState, JobStateReasons and various counters. Simple notifications will limit the payload values. Alan ---- 0) Job Control Interface starting to stabilize Work Remaining Overview: 1) Finalize reference and Target Device Schemas 2) Attributes: PSI has Job, Document, and Processing (template) Need to help with and leverage the PWG semantic model attributes 3) Discovery, PS and the target Devices a PS knows about? 4) Revisit Target Device Interface 5) Status code, hoping that this will also be part of the PWG semantic model for leverage 6) Event Notification 7) Security Finish all that and PSI is done :) New 6/11/02 Actions: 1) Referenc schema work user name, passwd, certifiacte and e-mail elements. Owner: Kirk: 2) Investigate original thougts on time attribute with Bluetooth folks Owner: Alan 3) Examine Use Models for Job Control interface implemenation owner: Dave Thanks, Alan From alan_berkema at hp.com Fri Jul 26 18:53:47 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> June Meeting Minutes Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1AB@xrose03.rose.hp.com> The unapproved minutes from the June Meeting are attached and now available at: ftp://ftp.pwg.org/ps/MinutesJune2602.pdf Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: MinutesJune2602.pdf Type: application/octet-stream Size: 59535 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020726/0dc1d1fb/MinutesJune2602-0001.obj From alan_berkema at hp.com Tue Jul 30 12:17:29 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: minutes 7/30/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1C1@xrose03.rose.hp.com> Please see attached -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI minutes 73002.pdf Type: application/octet-stream Size: 39708 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020730/1e549b0c/PSIminutes73002-0001.obj From alan_berkema at hp.com Wed Jul 31 17:11:04 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: next call 08/06/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1D4@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday August 6 (USA) Through August 6 (USA) (No Call August 13) New Number after this Time: 8 AM (US PST) Number: 650-690-9360(T348-9360) ID: 55605 Agenda: 1) Review work in progress 2) Review new Schemas (Kirk?) WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 8/6/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From imcdonald at sharplabs.com Tue Aug 6 15:35:21 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> SMB Reference Info - SMB URL I-D Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD30@mailsrvnt02.enet.sharplabs.com> Hi folks, Per today's PSI telecon question (from Kirk Ocke) about the content of an SMB reference, see "SMB Filesharing URL Scheme": ftp://ftp.ietf.org/internet-drafts/draft-crhertel-smb-url-03.txt Abstract The Server Message Block (SMB) protocol is one of the most widely used network filesystem protocols in existence. This document describes a format for an SMB Uniform Resource Locator. The SMB URL can be used to indicate SMB workgroups, servers, shares, files, inter-process communications pipes, print queues, and devices; the objects in the SMB network filesystem space. This is an excellent spec, with good references. That said, the complexities of an SMB reference (and how to resolve one for NetBIOS names to and from DNS names and IP addresses) are sufficient that I propose we (PSI) punt and just use URL forms for SMB references. Cheers, - Ira McDonald High North Inc ------------------------------------------------------------------- [some excerpts] Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. URL Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1 NBT Transport. . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1.1 nbt_name . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.2 ntdomain . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.3 nbt_context. . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Relative SMB URLs. . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Fragments. . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.4. Use of the 'port' Field. . . . . . . . . . . . . . . . . . . . 7 3. Relationship Between the URL and the UNC Formats. . . . . . . . . . 7 4. Authentication and Security Considerations. . . . . . . . . . . . . 7 5. SMB URL Semantics . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Character Encoding Issues . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 9. Author's Address. . . . . . . . . . . . . . . . . . . . . . . . . .10 Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 1. Introduction The Server Message Block protocol (SMB) was created in the 1980's by Dr. Barry Feigenbaum at IBM Corporation. It was later extended by IBM, 3Com, Intel, and Microsoft. SMB is now also known by the name CIFS, which stands for Common Internet FileSystem. SMB was originally carried via a proprietary network transport, the interface to which was called NetBIOS (Network Basic Input Output System). Two Internet RFCs ([RFC1001], [RFC1002]) were published which describe a mechanism for implementing the NetBIOS API on top of TCP and UDP. Those RFCs are now known collectively as Internet Standard #19 (STD 19), and the protocol they describe is known as NBT (for NetBIOS over TCP). SMB is intended to be transport independent. In addition to transport via NBT, SMB may be carried directly on TCP/IP without the intervening NetBIOS emulation layer. Several attempts have been made to document and even standardize the SMB protocol ([XOPENSMB], [ONET], [SNIACIFS]), yet the further development of SMB remains under the control of Microsoft. Despite its proprietary nature, the workings of SMB are sufficiently well known that SMB filesharing has been successfully implemented by several third-party commercial vendors, and in Open Source. SMB server and client software is available for a wide variety of operating system platforms. The very large number of systems which support this form of filesharing make an SMB URL scheme both practical and desirable. 1.1. Purpose This document does not attempt to describe the implementation of the SMB protocol itself. The goal is to present the syntax of the SMB URL, and explain how it maps to the features of SMB. 2. URL Definition An SMB URL may begin with one of two protocol prefixes: "smb" or "cifs". Both are considered to be equivalent. The following grammar defines the syntax of the SMB URL. It is based upon the grammar given in Appendix A of [RFC2396], as amended by [RFC2732]. Refer to those RFCs for any token definitions missing from the grammar below. smb_URL = ( SMB_absURL | SMB_relURL ) [ "#" fragment ] smb_absURL = scheme "://" [ smb_net_path ] [ "?" [ nbt_context ] ] smb_relURL = abs_path | rel_path scheme = "smb" | "cifs" smb_net_path = smb_server [ abs_path ] smb_server = [ smb_userinfo "@" ] smb_srv_name [ ":" port ] smb_srv_name = nbt_name | host nbt_name = netbiosname [ "." scope_id ] netbiosname = 1*( netbiosnamec ) *( netbiosnamec | "*" ) netbiosnamec = ( alphanum | escaped | ":" | "=" | "+" | "$" | "," | "-" | "_" | "!" | "~" | "'" | "(" | ")" ) scope_id = domainlabel *( "." domainlabel ) smb_userinfo = [ ntdomain ";" ] username [ ":" password ] ntdomain = *( unreserved | escaped | "&" | "=" | "+" | "$" | "," ) username = *( unreserved | escaped | "&" | "=" | "+" | "$" | "," ) password = *( unreserved | escaped | "&" | "=" | "+" | "$" | "," ) nbt_context = nbt_param *(";" nbt_param ) nbt_param = ( ( "NBNS=" | "WINS=" ) host ) | ( "CALLED=" netbiosname ) | ( "CALLING=" netbiosname ) | ( ( "WORKGROUP=" | "NTDOMAIN=" ) nbt_name ) From imcdonald at sharplabs.com Tue Aug 6 15:52:05 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: IPP (Job/Doc) Object Attributes work-in-progress Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD32@mailsrvnt02.enet.sharplabs.com> Hi folks, Per Alan's question about progress on the PWG Semantic Model at today's PSI Telecon: Tom Hastings (Xerox) has added a real Document object to the IPP Model (for addition to the PWG Semantic Model by Pete Zehler) - see the URL below for the PDF version. Tom and Pete and I spent quite a while on the phone over this the last two weeks, so it's a pretty good effort (we hope). Cheers, - Ira McDonald, High North Inc -----Original Message----- From: McDonald, Ira Sent: Sunday, August 04, 2002 2:30 PM To: 'Hastings, Tom N'; printing-spool@freestandards.org; printing-cap@freestandards.org; 'ipp@pwg.org' Cc: Zehler, Peter; McDonald, Ira Subject: RE: RESEND: PAPI Chapter 9 ISSUE: Reference to a document which lists all attributes Hi folks, I posted Tom's Acrobat (PDF) file to the requested URL: ftp://ftp.pwg.org/pub/pwg/fsg/spool/IPP-Object-Attributes.pdf After six tries, I still can't FTP transfer the (large) MS Word source file to the PWG server without the PWG server dropping the connection before it completes. No matter - the PDF file should be used for comments anyway. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Saturday, August 03, 2002 8:33 PM To: printing-spool@freestandards.org; printing-cap@freestandards.org Cc: Zehler, Peter; McDonald, Ira at Sharp Subject: RESEND: PAPI Chapter 9 ISSUE: Reference to a document which lists all attributes I misspelled the spool and cap DLs. Sorry for the resend. Tom -----Original Message----- From: Hastings, Tom N Sent: Saturday, August 03, 2002 16:53 To: 'spool@freestandards.org' Cc: printing-jobticket@freestandards.org; 'cap@freestandards.org'; 'ipp@pwg.org'; Zehler, Peter Subject: PAPI Chapter 9 ISSUE: Reference to a document which lists all attributes Alan, Chapter 9 of the FSG Print API (PAPI) spec, version V0.4 (ftp://ftp.pwg.org/pub/pwg/fsg/spool/papi_v0.4.pdf) has the following: Chapter 9. Attributes * ISSUE: Waiting for reference to single document from Tom H. I assume that this PAPI reference should be to a short document that lists all attributes and points to the specifications where they are described in detail, right? ISSUE: We need to discuss whether this short document should be to the PWG Semantic Model or to a more IPP specific document which contains references to all of the IPP attributes with the same IPP spellings and attribute syntaxes. I'm also copying this mail note to the FSG jobticket mailing list, since the job ticket API should provide mappings to the appropriate Job and Document attributes in the attached document. I'm also copying this mail note to the FSG cap (capabilities) mailing list, since the Capabilities API should provide mappings to the appropriate Printer attributes in the attached document. To see a draft of the PWG Semantic Model see: See ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.pdf ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Mode-06-020617.doc or later If the short document that the PAPI reference in Chapter 9 should be more IPP-specific, I've attached such a document. It only lists IPP WG approved IPP attributes, plus a few additions for a Document object proposal being worked on as part of the PWG Semantic Model and as an extension to IPP. The Document object proposal mostly re-uses job level attributes at the document level. Peter Zehler is incorporating all these attributes into the PWG Semantic Model and schema. Please send any comments to the mailing list. I'm in the process of registering with IANA those attributes in this document that have been published in RFCs. Unfortunately, I was unable to down load this file to the PWG FTP server: ftp://ftp.pwg.org/pub/pwg/fsg/spool/IPP-Object-Attributes.pdf ftp://ftp.pwg.org/pub/pwg/fsg/spool/IPP-Object-Attributes.doc so I've attached them as a single .zip file. I hope that it makes it through the freestandards mail system, since there is some limits to the size of attachments. Could somebody down load them to the above URLs this week? I'm leaving on vacation tomorrow (Sunday) and will return Thursday, August 15. Peter, If you want them in the PWG Semantic_model directory, please down load them there too. Thanks, Tom From alan_berkema at hp.com Sat Aug 10 10:26:00 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]:NEW Number next call 08/20/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD1FE@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday August 20 (USA) (No Call August 28) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) F2F Prep 2) TBD WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 8/20/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From imcdonald at sharplabs.com Wed Aug 14 13:00:00 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: [Srvloc-discuss] Zeroconf and SLP BoF at Linux-Kongress [5 Se pt 2002] Message-ID: <116DB56CD7DED511BC7800508B2CA53735CD3F@mailsrvnt02.enet.sharplabs.com> Hi folks, FYI - a BoF on Zeroconf and SLP at Linux-Kongress 2002 in Cologne (Koln) Germany on Thursday (5 September 2002). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Brad Hards [mailto:bhards@bigpond.net.au] Sent: Tuesday, August 13, 2002 7:04 PM To: openslp-devel@lists.sourceforge.net; zeroconf@merit.edu; srvloc-discuss@lists.sourceforge.net Cc: Erik Guttman Subject: [Srvloc-discuss] [OT] zeroconf and SLP BoF at Linux-Kongress -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have arranged a BoF session for Linux-Kongress 2002 on automatic networking technology implementation. A full description of what is planned is on line at http://www.linux-kongress.org/2002/bofs/index.html#zeroconf The BoF will be held Thursday 5-September-2002, in Cologne (Koln), Germany. The BoF will officially start at 1430, and run until 1600 (local time). However I will try to be at the room from about 1400 to welcome people and have informal discussions. We may have to vacate the room after (depends on other BoFs that are still to be scheduled) and find a pub or coffee house if it runs a bit long. Erik Guttman and I (well, mostly Erik, I guess) will be moderating it. I already have some expressions of interest from CUPS developers who will be at the conference, but if anyone else with an interest in this area can make, it'd be great to see you there. Full conference details are on their web-site (see above). I strongly encourage you to register (even if only for the day), although it is not absolutely mandatory if you only want to attend the BoF. If you don't register, you can't go to the official talks and wont get any coffee in the breaks etc. and no printed proceedings. You can attend the exhibition though. Sorry if this is too off-topic, but a get-together for a few hours can often overcome weeks of emails, so this might be a good chance to progress things. Brad - -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9WZBUW6pHgIdAuOMRAmypAJ9iamNZoKOr/SVrKTTD6YDnodh7PwCgrBcc RZ1Yo1s+UCIImE6YHJkE/fM= =Fa+r -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Srvloc-discuss mailing list Srvloc-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/srvloc-discuss From alan_berkema at hp.com Mon Aug 19 21:37:30 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: [PSI]:NEW Docs NEW Number next call 08/20/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD206@xrose03.rose.hp.com> Hey all (especially Ira), I put a new psi-spec32.doc == psi-spec-latest.pdf on the web site. OK if you just want to follow along with webex. Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Saturday, August 10, 2002 7:26 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: [PSI]:NEW Number next call 08/20/02 Teleconference details: Date: Tuesdays, Next: Tuesday August 20 (USA) (No Call August 28) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) F2F Prep 2) TBD WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 8/20/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Tue Aug 20 18:33:56 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: next call 09/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD219@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: (No Call September 3, day after holiday after F2F) Tuesday Septemebr 10 (USA) (No Call Septemebr 24?) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) Continue F2F Topics and actions 2) TBD WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 9/10/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Thu Aug 22 14:01:30 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD22D@xrose03.rose.hp.com> Hey all, I posted pdf files with line numbers to psi-spec & the selected logical view on the ps page. Alan From alan_berkema at hp.com Thu Aug 22 16:37:59 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: [PSI]: F2F Agenda 8/28/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD233@xrose03.rose.hp.com> All: Here is a proposed agenda for the PSI F2F on Wednesday I. Introductions II. Review and Approve minutes from June (ftp://ftp.pwg.org/pub/pwg/ps/MinutesJune2602.pdf) III. Review Agenda IV. Review Action Items V. Topics from Phone Conferences Print Service Interface name change to something like QueryInterfaceEndpoints. This is the interface in the spec. not renaming the spec. itself. Discuss Discovery Strategy Notification Name Change Seperate Credential Schema? VI. Review Attribute Structure Object Schemas (ftp://ftp.pwg.org/pub/pwg/ps/Job.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/JobAttibutes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Document.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/DocumentAttributes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Processing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Finishing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Rendering.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Imposition.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/typesPWG.xsd) VII. Review reference schema (ftp://ftp.pwg.org/pub/pwg/ps/reference080502.xsd) VIII. Review targetDevice schema (ftp://ftp.pwg.org/pub/pwg/ps/targetDevice080502.xsd) IX. Review PSI Spec & Selected Logical View (ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf) (ftp://ftp.pwg.org/pub/pwg/ps/psi-model-view.pdf) X. Plan Forward & teleconference schedule with respect to Holidays & Vacations Alan From hastings at cp10.es.xerox.com Thu Aug 22 16:52:17 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:15 2009 Subject: PS> First Draft IPP Document Object spec down-loaded Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F9080702FC@x-crt-es-ms1.cp10.es.xerox.com> Peter Zehler posted the next draft (0.07) of the PWG Semantic Model on August 16 at: ftp://ftp.pwg.org/pub/pwg/Semantic_model/PWG-Semantic-Model-07-020816.pdf The PWG Semantic Model document is intended to be short and to refer to other documents for the details (mostly IPP documents). The PWG Semantic Model is also intended to be used by other groups that are developing print semantics in order to make any API, protocol, and job ticket semantics as similar as possible, such as those being developed by other PWG sub-groups and other groups, such as the sub-groups in the Free Standards Group OpenPrinting WG. The PWG Semantic Model adds a new Document object to the model. It re-uses most of the existing Job attributes for the Document object. However, the detailed specification for the Document object, operations, attributes, and values is needed for the Semantic Model to reference. This mail note announces a first draft of such a 36-page document. Its available at: ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/document-object-v094.pdf 200Kb ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/document-object-v094.doc 1000Kb ftp://ftp.pwg.org/pub/pwg/ipp/new_DOC/document-object-v094.zip 140Kb - just the .doc The .doc file is 1Mbyte, probably because of the two Visio state diagrams, or maybe the tables. This IPP Document Object specification is intended to give a common semantic model for the Document object for use by IPP (ipp@pwg.org), the PWG Semantic Model (sm@pwg.org), the PWG Print Services Interface (PSI) (ps@pwg.org), and the Free Software Group (FSG) PAPI (printing-spool@freestandards.org) and Job Ticket APIs (printing-jobticket@freestandards.org). For more info on the 3 PWG sub-groups, visit http://www.pwg.org For more info on the 2 FSG sub-groups, visit http://www.freestandards.org/openprinting The PWG is meeting next week in Santa Fe: Monday Aug 26: Internet FAX Tuesday Aug 27: PWG Plenary/XHTML-print Wednesday, Aug 28: Print Services Interface (PSI) (Thursday UPnP). There are 9 issues (included below) in the document that would be good to handle at some point in the agenda. And any other issues raised by reading the spec would be good too. Since there are 5 groups working on this (see To list), I suggest that any comments be sent to all lists as a reply all. Here is the Abstract: This document is an IPP extension proposal to extend the IPP/PWG semantics to include a Document object. The Job object is said to contain one or more Document objects which are passive objects operated on by the Job. The Document object is created by the existing Send-Document and Send-URI operations. However, a client can supply additional Document Template attributes with each document and new Document Description attributes are defined. Also there are seven new operations defined for Documents once they have been created. The purpose for specifying the Document object, is so that we can have a common specification for use in IPP, the PWG Semantic Model, the PWG PSI project, and the Free Standards Group Job Ticket API which all have a Document object. Here are the 9 issues: ISSUE 01: Should we publish this document as an IETF standards track document or as an IEEE-ISTO standard? If the former, since the IETF IPP WG is in the process of being closed down when all the current specifications are published, Peter and Tom will propose the specification as individual authors standards track contribution (after PWG review). If the latter, it will be published as one more IEEE-ISTO standard in the 5100.n series. --------------------------- According to [coll], the "document-overrides" (collection) attribute MAY be supplied by the client in a Send-Document or Send-URI request as an Operation attribute to apply document overrides to this and/or subsequent documents in the job. See the "document-overrides" Job Template attribute in Table 3 for the listing of the member attributes. However, with the introduction of the Document object, the "document-overrides" (collection) attribute SHOULD NOT be used (either as a Job Template attribute or an Operation attribute). Instead, the client simply supplies the Document Template attributes (see Table 3) for each Document Creation request (in a new Document Template attribute group) without needing a collection. ISSUE 02: What do we want to do with the "document-overrides" collection attributes when supporting the Document object, which is no longer needed as either a Job Template, Document Template, or operation attribute in Job and Document Creation requests? --------------------------- Similarly, according to [coll], the "page-overrides" (collection) attribute MAY be supplied by the client in a Send-Document or Send-URI request as an Operation attribute to apply page overrides to this and/or subsequent documents in the job. See the "page-overrides" Job Template attribute in Table 3 for the listing of the member attributes. However, with the introduction of the Document object, the "page-overrides" (collection) attribute SHOULD be more simply supplied as one of the Document Template attributes for this document only. ISSUE 03: What do we want to do with the "page-overrides" collection attributes when supporting the Document object, which is still needed as a Job Template and Document Template attribute for overriding attributes in specified page ranges, but is not needed as an operation attribute on Document Creation requests? --------------------------- ISSUE 04: Is the following query behavior for Job and Document objects OK? Job Template and Document Template attributes are OPTIONAL for a Printer to support and for a client to supply in a Job Creation or Document Creation request or a Document Overrides or Page Overrides. If a Printer supports a Job Template or Document Template attribute, then it MUST copy the supplied attribute to the Job or Document object, respectively so that a client MAY query the attributes in subsequent Get-Job-Attributes/Get-Jobs and Get-Document-Attributes/Get-Documents operations, respectively. The effect of Job Template Attributes supplied in Job Creation requests are inherited by the Document objects, unless the Document Creation operation supplies the attribute with a different value. However, the Printer MUST NOT propagate Job Template attributes supplied in Job Creation operations to the Document object. Similarly, the Printer MUST NOT promote Document Template attributes up to the Job object when no corresponding Job Template attribute was supplied in the Job Creation operation. Thus the Printer returns in queries only Job Template and Document Template attributes that were actually supplied by a client. --------------------------- [job-] indicates an attribute that shouldn't have had a "job-" prefix in its name in [RFC2911], so that the same attribute could also apply to the Document object as a Document Description attribute. Note: For the PWG Semantic Model, the "job-" prefix is proposed to be dropped. ISSUE 05: Should we sort the attributes ignoring the [job-]? Current the "job-" is used in the sort for attributes. ISSUE 06: How will we register these attributes with IANA, since they will be registered for IPP use, with the "job-" prefix. Do we add the ones without "job-" as aliases to the IANA registry as is done for charset registrations? --------------------------- [job-] indicates a state reason keyword value that shouldn't have had a "job-" prefix in its name in [RFC2911], so that the same value could also apply at the Document level as a "document-state-reasons" attribute value. Note: For the PWG Semantic Model, the "job-" prefix will be dropped. For purposes of sorting in Table 6, the "[job-]" prefix is ignored, since the PWG Semantic Model name is proposed without the prefix. ISSUE 07: Should we sort the attributes values including the [job-]? Currently the "job-" is ignored in the sort for attribute values. ISSUE 08: How will we register these attribute values with IANA, since they will be registered for IPP use, with the "job-" prefix. Do we add the ones without "job-" as aliases to the IANA registry as is done for charset registrations? --------------------------- TBD - one to list the Document Template keyword attribute names supported. ISSUE 09: What other Printer Description attributes are needed, if any? Send comments to the mailing lists. Thanks, Tom From PZehler at crt.xerox.com Fri Aug 23 10:09:49 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: [PSI]: F2F Agenda 8/28/02 Message-ID: All, I would like to modify the proposed agenda for the upcoming PSI face to face. Based on input from our last meeting and the mailing list I have updated the schemas referenced in section VI. There is now a "master list" of all the semantic elements(and types) defined by the PWG Semantic model (See i). These semantic elements and groups are referenced from the other files. There is a single file that defines the grouping of processing attributes into the 4 groups finishing, rendering, imposition and job-level (See ii). The document, job and printer are described in the remaining files. VI. Review Attribute Structure Object Schemas i. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PwgAttr.xsd ii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/ProcessingAttributes.xsd iii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Document.xsd iv. ftp://ftp.pwg.org/pub/pwg/Semantic_model/DocumentAttributes.xsd v. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Job.xsd vi. ftp://ftp.pwg.org/pub/pwg/Semantic_model/JobAttributes.xsd vii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Printer.xsd viii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrinterAttributes.xsd Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (716) 265-8755 FAX: (716) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, August 22, 2002 4:38 PM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: PS> RE: [PSI]: F2F Agenda 8/28/02 All: Here is a proposed agenda for the PSI F2F on Wednesday I. Introductions II. Review and Approve minutes from June (ftp://ftp.pwg.org/pub/pwg/ps/MinutesJune2602.pdf) III. Review Agenda IV. Review Action Items V. Topics from Phone Conferences Print Service Interface name change to something like QueryInterfaceEndpoints. This is the interface in the spec. not renaming the spec. itself. Discuss Discovery Strategy Notification Name Change Seperate Credential Schema? VI. Review Attribute Structure Object Schemas (ftp://ftp.pwg.org/pub/pwg/ps/Job.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/JobAttibutes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Document.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/DocumentAttributes.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Processing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Finishing.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Rendering.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/Imposition.xsd) (ftp://ftp.pwg.org/pub/pwg/ps/typesPWG.xsd) VII. Review reference schema (ftp://ftp.pwg.org/pub/pwg/ps/reference080502.xsd) VIII. Review targetDevice schema (ftp://ftp.pwg.org/pub/pwg/ps/targetDevice080502.xsd) IX. Review PSI Spec & Selected Logical View (ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf) (ftp://ftp.pwg.org/pub/pwg/ps/psi-model-view.pdf) X. Plan Forward & teleconference schedule with respect to Holidays & Vacations Alan From hastings at cp10.es.xerox.com Mon Aug 26 20:50:28 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:15 2009 Subject: PS> Terminology comment: "Job Attributes" and "Document Attributes" Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F9080703C1@x-crt-es-ms1.cp10.es.xerox.com> Peter, I don't have any problem with the PWG Semantic Model improving on the terminology from IPP, such as the term "Processing Attributes" instead of "Job Template Attributes". I also think that the Processing Attributes are a combination of the IPP Job Template attributes and the Job Creation operation attributes, and the concept of operation attributes has disappeared, right? However, where the IPP terminology is OK, I suggest we stick with it. For example, the term "Job Attributes" (section 2.2.1, Figure 5 and Section 4.2 Table 4) is equivalent to the IPP Job Description Attributes. I suggest that we stick with the term "Job Description Attributes" in the PWG Semantic Model, i.e., attributes that the Printer produces the values for. Another reason is that the term Job Attributes should mean all of the attributes of the Job object, not a subset. The Processing Attributes are really Job Attributes too, since the client supplies them, but the Printer copies them to the Job object. So I suggest that a Job object contains Job Attributes which consist of Processing Attributes supplied by the client and Job Description attribute supplied by the Printer. Same for the term "Document Attributes" (section 2.3.1, Figure 7, section 4.3, Table 5). The term should be "Document Description Attributes". So a Document object contains Document Attributes which consist of Processing Attributes supplied by the client and Document Description attribute supplied by the Printer. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Saturday, August 24, 2002 18:05 To: 'sm@pwg.org' Subject: SM> Semantic documernts All, Sorry if this as a repeat for you. I apparently was not subscribed to the sm mailing list for some unknown reason. Therefore I have missed any traffic. In preparation for the meeting in Santa Fe a new version of the Semantic Model document was posted on the PWG site. The URL is " ". We will use this document with line numbers as the basis for our conversation at the PWG meeting. I have updated the XML schema files based on input and the new semantic document. There is now a "master list" of all the semantic elements(and types) defined by the PWG Semantic model (See i). These semantic elements and groups are referenced from the other files. There is a single file that defines the grouping of processing attributes into the 4 groups finishing, rendering, imposition and job-level (See ii). The document, job and printer are described in the remaining files. VI. Review Attribute Structure Object Schemas i. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PwgAttr.xsd ii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/ProcessingAttributes.xsd iii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Document.xsd iv. ftp://ftp.pwg.org/pub/pwg/Semantic_model/DocumentAttributes.xsd v. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Job.xsd vi. ftp://ftp.pwg.org/pub/pwg/Semantic_model/JobAttributes.xsd vii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Printer.xsd viii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrinterAttributes.xsd Pete From hastings at cp10.es.xerox.com Tue Aug 27 17:03:47 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New docs [watch out: web page != ftp directory] Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F908070423@x-crt-es-ms1.cp10.es.xerox.com> Alan, The psi-spec32.doc file that you posted as ftp://ftp.pwg.org/pub/pwg/ps/psi-spec32.doc on August 19, has Revision number 0.32 and a date in the document of August 19. However, the .PDF versions that you posted as ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf on August 22, has a Revision number of 0.30 and a date in the document of July 18 and doesn't have line numbers. Also the Model View file that you posted on August 22 as ftp://ftp.pwg.org/pub/pwg/ps/psi-model-view.pdf on August 22, has an internal generated date of April 22, 2002. However, if you go to the web page, you do get the intended .pdf file with a version of 0.32 that agree with the .doc. Is there anyway to keep the ftp available files synchronized with the web page available files? What about all of the schema xsd files that appear both on the web page and the FTP directory with a date of August 22? Are they the same files? Thanks, Tom -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Thursday, August 22, 2002 11:02 To: 'a PSI pwg.org'; BERKEMA,ALAN C (HP-Roseville,ex1) Subject: PS> [PSI]: New docs Hey all, I posted pdf files with line numbers to psi-spec & the selected logical view on the ps page. Alan From hastings at cp10.es.xerox.com Tue Aug 27 17:11:13 2002 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:02:15 2009 Subject: PS> Terminology comment: "Job Attributes" and "Document Attri butes" Message-ID: <0CCC9D5E696C4E4DBFC2EBCEA6A3F908070424@x-crt-es-ms1.cp10.es.xerox.com> PSI WG, I should have said that this comment on terminology was for both the PWG Semantic Model and the PSI Specification, since terms in question are nicely aligned between PSI Spec and the PWG Semantic Model. Tom -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Monday, August 26, 2002 17:50 To: 'sm@pwg.org' Cc: ps@pwg.org Subject: PS> Terminology comment: "Job Attributes" and "Document Attributes" Peter, I don't have any problem with the PWG Semantic Model improving on the terminology from IPP, such as the term "Processing Attributes" instead of "Job Template Attributes". I also think that the Processing Attributes are a combination of the IPP Job Template attributes and the Job Creation operation attributes, and the concept of operation attributes has disappeared, right? However, where the IPP terminology is OK, I suggest we stick with it. For example, the term "Job Attributes" (section 2.2.1, Figure 5 and Section 4.2 Table 4) is equivalent to the IPP Job Description Attributes. I suggest that we stick with the term "Job Description Attributes" in the PWG Semantic Model, i.e., attributes that the Printer produces the values for. Another reason is that the term Job Attributes should mean all of the attributes of the Job object, not a subset. The Processing Attributes are really Job Attributes too, since the client supplies them, but the Printer copies them to the Job object. So I suggest that a Job object contains Job Attributes which consist of Processing Attributes supplied by the client and Job Description attribute supplied by the Printer. Same for the term "Document Attributes" (section 2.3.1, Figure 7, section 4.3, Table 5). The term should be "Document Description Attributes". So a Document object contains Document Attributes which consist of Processing Attributes supplied by the client and Document Description attribute supplied by the Printer. Tom -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Saturday, August 24, 2002 18:05 To: 'sm@pwg.org' Subject: SM> Semantic documernts All, Sorry if this as a repeat for you. I apparently was not subscribed to the sm mailing list for some unknown reason. Therefore I have missed any traffic. In preparation for the meeting in Santa Fe a new version of the Semantic Model document was posted on the PWG site. The URL is " ". We will use this document with line numbers as the basis for our conversation at the PWG meeting. I have updated the XML schema files based on input and the new semantic document. There is now a "master list" of all the semantic elements(and types) defined by the PWG Semantic model (See i). These semantic elements and groups are referenced from the other files. There is a single file that defines the grouping of processing attributes into the 4 groups finishing, rendering, imposition and job-level (See ii). The document, job and printer are described in the remaining files. VI. Review Attribute Structure Object Schemas i. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PwgAttr.xsd ii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/ProcessingAttributes.xsd iii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Document.xsd iv. ftp://ftp.pwg.org/pub/pwg/Semantic_model/DocumentAttributes.xsd v. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Job.xsd vi. ftp://ftp.pwg.org/pub/pwg/Semantic_model/JobAttributes.xsd vii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/Printer.xsd viii. ftp://ftp.pwg.org/pub/pwg/Semantic_model/PrinterAttributes.xsd Pete From alan_berkema at hp.com Wed Sep 4 19:17:41 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: Proposed mins 8/28/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD263@xrose03.rose.hp.com> please see attached will also post later comments/corrections welcome Thanks, Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: PSI minutes 82802.pdf Type: application/octet-stream Size: 79281 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20020904/9ae1dd9e/PSIminutes82802-0001.obj From alan_berkema at hp.com Thu Sep 5 12:51:58 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New Docs from 08/28/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD269@xrose03.rose.hp.com> With modifications from F2F psi-spec33.doc = psi-spec-latest.pdf psi082802.doc = psi-model-view.pdf psi082802.mdl = no link yet Thanks, Alan From alan_berkema at hp.com Tue Sep 10 13:14:58 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: next call 09/17/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD29F@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday Septemebr 17 (USA) (No Call Septemebr 24???) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) Continue TargetDeviceSupport Interface & Basic Notification Discussion 2) PWG Sematic Model Attribute Alignment WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 9/17/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Thu Sep 12 17:24:26 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: minutes 9/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD2C0@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema Gail Songer *Dave Hall Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke Ira Mcdonald Amir Shahindoust * = attendance 09/10/02 Agenda 1) Review the PSI schedule 2) Review the targetDeviceSupport interface Minutes: Thinly attended, however it was still a very productive meeting. 1) Review the PSI schedule See schedule attached. By the end of September we will attempt to get the spec to rev 0.9. This will include the spec. and the logical view in a single document. We need to resolve all the outsatnding issues or jetison the feature to Post 1.0. It will also add the WSDL/SOAP for the methods. I realize this is aggresive, however, we definately won't make it if don't try for it. When we post .9 we have a few phone conferences to continue to work on it. On October 22 we will post the revisions as a .93 spec, two week before the Novemebr F2F. .93 is the candidate .95 spec. We will review this and changes will become the .94 spec. Apx. two weeks after this I will call for a vote to promote this to 0.95. The philosophy behind setting an aggressive schedule in the charter was to enable a base level of PSI functionality to test it and attempt to foster early market adoption, rather than work on a spec for multiple years that covers everything. 2) Review the targetDeviceSupport interface associateTargetDevice(), does this belong in 1.0? Ira commented that this isn't specified well enough and "a mircle needs to happen" for this to work. Take a look and we will revisit at the next call. The postStatus methods were changed to sendServiceNotifications sendJobNotifications sendDocumentNotifications sendServiceNotifications includes jobState, jobStateReasons and an eventID. These are all simple noticiations that do not involve subscriptions. The above conclusion was reached via an involved discussion about notifications in general, subscriptions, and why are we doing notifications at all and why are we doing them in the targetDeviceSupport interface? Conclusion is that the targetDeviceSupport interface is primarlly used when the targetDevice is behind a firewall and the PS cannot do a getJobAttributes. We need a boolean that tells the targetDevice if the PS wants notifications or not. We previously thought that this would go in the createJob, however since the notifications are only used with the tagetDeviceSupport interface we deiced to put the boolean in the getNextJob. Is it also in getNextDcoument? forgot where we landed. Discussion about getKnowTargetDevices, does this belong in the targetDeviceSupport? I think we decided to move this to jobControl? that is all, Alan From alan_berkema at hp.com Fri Sep 13 16:16:53 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: [PSI]: Updated minutes 9/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD2D0@xrose03.rose.hp.com> I forgot to include Ira as an attendee. Alan ---- PSI Working Group: *Alan Berkema Gail Songer *Dave Hall Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 09/10/02 Agenda 1) Review the PSI schedule 2) Review the targetDeviceSupport interface Minutes: Thinly attended, however it was still a very productive meeting. 1) Review the PSI schedule See schedule attached. By the end of September we will attempt to get the spec to rev 0.9. This will include the spec. and the logical view in a single document. We need to resolve all the outsatnding issues or jetison the feature to Post 1.0. It will also add the WSDL/SOAP for the methods. I realize this is aggresive, however, we definately won't make it if don't try for it. When we post .9 we have a few phone conferences to continue to work on it. On October 22 we will post the revisions as a .93 spec, two week before the Novemebr F2F. .93 is the candidate .95 spec. We will review this and changes will become the .94 spec. Apx. two weeks after this I will call for a vote to promote this to 0.95. The philosophy behind setting an aggressive schedule in the charter was to enable a base level of PSI functionality to test it and attempt to foster early market adoption, rather than work on a spec for multiple years that covers everything. 2) Review the targetDeviceSupport interface associateTargetDevice(), does this belong in 1.0? Ira commented that this isn't specified well enough and "a mircle needs to happen" for this to work. Take a look and we will revisit at the next call. The postStatus methods were changed to sendServiceNotifications sendJobNotifications sendDocumentNotifications sendServiceNotifications includes jobState, jobStateReasons and an eventID. These are all simple noticiations that do not involve subscriptions. The above conclusion was reached via an involved discussion about notifications in general, subscriptions, and why are we doing notifications at all and why are we doing them in the targetDeviceSupport interface? Conclusion is that the targetDeviceSupport interface is primarlly used when the targetDevice is behind a firewall and the PS cannot do a getJobAttributes. We need a boolean that tells the targetDevice if the PS wants notifications or not. We previously thought that this would go in the createJob, however since the notifications are only used with the tagetDeviceSupport interface we deiced to put the boolean in the getNextJob. Is it also in getNextDcoument? forgot where we landed. Discussion about getKnowTargetDevices, does this belong in the targetDeviceSupport? I think we decided to move this to jobControl? that is all, Alan From imcdonald at sharplabs.com Thu Sep 19 09:57:41 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: IPP> FW: Errata in RFC 2911: "Internet Printing Protocol/1.1: Model an d Semantics" Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDA7@mailsrvnt02.enet.sharplabs.com> Hi folks, Please note the following minor errata to IPP/1.1 (RFC 2911). Cheers, - Ira McDonald High North Inc -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Wednesday, September 18, 2002 3:12 PM To: ipp@pwg.org Subject: IPP> FW: Errata in RFC 2911: "Internet Printing Protocol/1.1: Model an d Semantics" This very minor RFC 2911 Errata has been posted finally. To see any RFC Errata, go to: http://www.rfc-editor.org/rfcsearch.html Then bug on the RFC Errata box. They are sorted in reverse order by RFC number. If you've looked before, make sure you tell your Browser to refresh or you won't find the latest Errata. Tom -----Original Message----- From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: Wednesday, September 18, 2002 10:13 To: rfc-editor@rfc-editor.org; hastings@cp10.es.xerox.com Cc: hastings@cp10.es.xerox.com; carl@manros.com Subject: Re: FW: IPP> Errata in RFC 2911: "Internet Printing Protocol/1.1: Mod el and Semantics" Tom, We apologize for the delay. We have updated our errata page to refelct the errors indicated below. Thank you. RFC Editor > From: "Hastings, Tom N" > To: rfc-editor@rfc-editor.org > Cc: "Hastings, Tom" , "Manros, Carl-Uno" > Subject: FW: IPP> Errata in RFC 2911: "Internet Printing Protocol/1.1: Mod el and Semantics" > Date: Tue, 3 Sep 2002 13:32:16 -0700 > MIME-Version: 1.0 > > I submitted this Errata in July. It hasn't been posted yet. Is there > anything more that I have to do? Does it have to be approved by anyone, > such as our AD? > > Its not critical, though a recent I-D that is going through last call is > assuming that the errata is true and accepted, so it would be good to post > the errata. > > Thanks, > Tom > > -----Original Message----- > From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] > Sent: Wednesday, July 17, 2002 17:52 > To: rfc-editor@rfc-editor.org > Cc: ipp@pwg.org > Subject: IPP> Errata in RFC 2911: "Internet Printing Protocol/1.1: Model > and Se mantics" > > > This note points out two errata in RFC 2911 regarding the ranges of status > codes. > > Section 13, which is "APPENDIX B: Status Codes and Suggested Status Code > Messages" has: > > "redirection" - 0x0200 to 0x02FF > > which should be: > > "redirection" - 0x0300 to 0x03FF > > and has: > > The top half (128 values) of each range (0x0n40 to 0x0nFF, for n = 0 > to 5) is reserved for vendor use within each status code class. > > which should be: > > The top half (128 values) of each range (0x0n80 to 0x0nFF, for n = 0 > to 5) is reserved for vendor use within each status code class. > > Thank you, > > Tom Hastings > IPP WG Editor From harryl at us.ibm.com Thu Sep 19 12:21:32 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:15 2009 Subject: PS> Throwing exceptions Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/e5d349de/attachment-0001.html From dhall at hp.com Thu Sep 19 12:33:01 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: Throwing exceptions Message-ID: <77261E830267D411BD4D00902740AC250B5970F7@xvan01.vcd.hp.com> We are rapidly approaching a working PSI prototype that will be able to "throw exceptions" from the method calls. They are known as "soap faults"... Our current methods don't "throw exceptions" in the XML string parameters that are returned, it was an unfortunate naming of the return paramater - "ExceptionAttributes" that is now named "UnsupportedAttributes". Returning "UnsupportedAttributes" does not mean that an error has occured, rather that some requested attributes are not supported by the service. We will be throwing "faults" from the soap calls... Hopefully this is clearer now.. :) Dave -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, September 19, 2002 9:22 AM To: HALL,DAVID (HP-Vancouver,ex1) Cc: ps@pwg.org; alan_berkema@hp.com Subject: Throwing exceptions How to throw an exception form a SOAP method. I see this in the spec as a question ... "DHall - define exactly how to throw an exception from a SOAP method" section 5.3.1. Our current definition packages exceptions as a multi XML string parm set in the return. Is this our conscious resolution to PSI exceptions? Have we considered throwing exceptions, independently, across the web services interface? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/9c062e0f/attachment-0001.html From harryl at us.ibm.com Thu Sep 19 16:47:37 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: Throwing exceptions Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/3c600b89/attachment-0001.html From dhall at hp.com Thu Sep 19 17:12:37 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: Throwing exceptions Message-ID: <77261E830267D411BD4D00902740AC250B597110@xvan01.vcd.hp.com> Hey Harry... I believe that the polling scenario is indeed the correct model. For this particular method, we may not have it exactly right. We could overload the JobID == 0 to mean that no job is available, but that doesn't quite feel right. Throwing an exception in this case is really our way of informing the client (targetdevice) that no job is available for it yet. Dave Pseudo code: Boolean bJobAvailable = false; String JobID = ""; while (!bJobAvailable) { try { JobID = PrintService.TargetDeviceSupportInterface.GetNextJob("myTargetDeviceIdentifi er"); bJobAvailable = true; } catch (Exception e) { if (e == InvalidTargetDeviceIdentifier) { exit(InvalidTargetDeviceIdentifier); } elseif (e == TargetDeviceNotSupported) { exit(TargetDeviceNotSupported); } elseif (e == NoJobAvaliable) { // OK, keep polling } } } // Now we have a JobID, continue processing... -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, September 19, 2002 1:48 PM To: HALL,DAVID (HP-Vancouver,ex1) Cc: BERKEMA,ALAN C (HP-Roseville,ex1); HALL,DAVID (HP-Vancouver,ex1); ps@pwg.org Subject: RE: Throwing exceptions OK, thanks for that clarification. Related question... In the TargetDeviceSupportInterface the operation GetNextJob "throws and exception" if no job is available for the target device. I assume, then, this is a SOAP "fault"? If so, is this really what we want? The design is polling from target device to print service. In this case won't "no job available" be the more likely case? Or, are we suggesting (via the scenarios) that the target device isn't expected to poll unless having been asked to out of band by a client (implying there SHOULD be a job present... thus the "fault")? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- "HALL,DAVID (HP-Vancouver,ex1)" 09/19/2002 10:33 AM To: Harry Lewis/Boulder/IBM@IBMUS, "HALL,DAVID (HP-Vancouver,ex1)" cc: ps@pwg.org, "BERKEMA,ALAN C (HP-Roseville,ex1)" Subject: RE: Throwing exceptions We are rapidly approaching a working PSI prototype that will be able to "throw exceptions" from the method calls. They are known as "soap faults"... Our current methods don't "throw exceptions" in the XML string parameters that are returned, it was an unfortunate naming of the return paramater - "ExceptionAttributes" that is now named "UnsupportedAttributes". Returning "UnsupportedAttributes" does not mean that an error has occured, rather that some requested attributes are not supported by the service. We will be throwing "faults" from the soap calls... Hopefully this is clearer now.. :) Dave -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, September 19, 2002 9:22 AM To: HALL,DAVID (HP-Vancouver,ex1) Cc: ps@pwg.org; alan_berkema@hp.com Subject: Throwing exceptions How to throw an exception form a SOAP method. I see this in the spec as a question ... "DHall - define exactly how to throw an exception from a SOAP method" section 5.3.1. Our current definition packages exceptions as a multi XML string parm set in the return. Is this our conscious resolution to PSI exceptions? Have we considered throwing exceptions, independently, across the web services interface? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20020919/ecbc911d/attachment-0001.html From alan_berkema at hp.com Fri Sep 20 14:13:22 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New Docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD306@xrose03.rose.hp.com> psi-spec35.doc = psi-spec-latest.pdf psi091902.doc = psi-model-view.pdf psi091902.mdl = no link yet Thanks, Alan From imcdonald at sharplabs.com Mon Sep 23 11:21:07 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: Unicode text editor mined 2000 release 4 Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDB1@mailsrvnt02.enet.sharplabs.com> Hi folks, FYI - a native Unicode text editor for all UNIX/DOS/Windows platforms. Cheers, - Ira McDonald High North Inc -----Original Message----- From: thomas@towo.net [mailto:thomas@towo.net] Sent: Sunday, September 22, 2002 7:13 PM To: linux-utf8@nl.linux.org; Subject: Unicode text editor mined 2000 release 4 ANNOUNCEMENT mined 2000 release 4 An editor that is small and easy to use but yet full of capabilities. Runs in plain text mode terminals. Supports Unicode. Provides mouse control and menus. Runs on Unix and DOS/Windows platforms. Short description Good interactive features * an intuitive user interface * command control and pull-down menus available * control and function key or mouse control Many useful text editing features * extensive Unicode support, including double-width and combining characters * many text editing capabilities, e.g. paragraph wrapping, smart quotes, multi-line support in search and replacement patterns * program editing features, HTML support and syntax highlighting, identifier search * systematic text and file handling safety, avoiding loss of data "Small-footprint" operation and portability * plain text mode (terminal) operation * instant start-up * cross-platform operation (Unix, DOS/Windows) More information (with screenshots and change log) and download are available from the mined web page at http://towo.net/mined/ ---------------------------------------------------------------------------- - Thomas Wolff mined@towo.net -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/ From dhall at hp.com Tue Sep 24 09:57:24 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> PSI Meeting Info for 9-24 Message-ID: <77261E830267D411BD4D00902740AC250B597175@xvan01.vcd.hp.com> Hi All... Sorry for the late meeting notice info... Dave Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 ------------------------- MEETING SUMMARY ------------------------- Name: PSI Date: 9/24/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 22021870 Meeting Password: newpsi From PZehler at crt.xerox.com Tue Sep 24 13:08:37 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:15 2009 Subject: PS> Server side Stub generation Message-ID: Dave, I think it was you that asked about tools that support the generation of server-side skeletons as well as client-side stubs from a WSDL file. I know that Microsoft .NET, Sun ONE, SYSINET WASP and Ximian SOUP support it. And I believe OpenSource FSU GSOAP also does. Pete 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 From imcdonald at sharplabs.com Tue Sep 24 15:34:44 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> Valid XML - ISO DSDL and RELAX NG Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDB5@mailsrvnt02.enet.sharplabs.com> Hi folks, Per my action item from today's PSI telecon, some info on RELAX NG, which is the OASIS developed successor to RELAX and is soon to be published part 2 of ISO 19757. For more info on RELAX NG see the OASIS site at: http://www.oasis-open.org/committees/relax-ng/ For more info on RELAX NG tools go to: http://www.oasis-open.org/committees/relax-ng/#tools I just stored several files on the PWG FTP server: ftp://ftp.pwg.org/pub/pwg/ps/dsdl/iso-cd-19757-0-DSDL-Overview.pdf - ISO/IEC CD 19757-0 Document Description and Processing Languages - Document Schema Definition Language (DSDL) - Part 0 - Overview - CD = Committee Draft (i.e., working document) ftp://ftp.pwg.org/pub/pwg/ps/dsdl/iso-dis-19757-2-RELAX-NG.pdf - ISO/IEC DIS 19757-2 Document Description and Processing Languages - Document Schema Definition Language (DSDL) - Part 2 - Grammar-Based Validation - RELAX NG - DIS = Draft International Standard (now in balloting) ftp://ftp.pwg.org/pub/pwg/ps/dsdl/xmloperator-2.0-supports-RELAX-NG.txt - text of a mail note from the RELAX-NG mailing list this morning Cheers, - Ira McDonald High North Inc From alan_berkema at hp.com Fri Sep 27 11:36:02 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New docs Message-ID: <499DC368E25AD411B3F100902740AD650E6AD31C@xrose03.rose.hp.com> psi-spec37.doc = psi-spec-latest.pdf psi092602.doc = psi-model-view.pdf reference.xsd targetDevice.xsd interfaceIdentifer.xsd Thanks, Alan From alan_berkema at hp.com Mon Sep 30 12:05:48 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: next call 10/01/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD320@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday October 1 (USA) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) Continue TargetDeviceSupport Interface & Basic Notification Discussion 2) PWG Sematic Model Attribute Alignment WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 10/1/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan_berkema at hp.com Mon Sep 30 13:41:43 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: WSDL on the web Message-ID: <499DC368E25AD411B3F100902740AD650E6AD326@xrose03.rose.hp.com> Hi all, Checkout the PSI WSDL files: ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.TargetDeviceSupportInterface.w sdl AND ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.TargetDeviceSupportInterface.w sdl Thanks Dave, Alan From Lee.Farrell at cda.canon.com Mon Sep 30 14:32:31 2002 From: Lee.Farrell at cda.canon.com (Farrell, Lee) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: WSDL on the web Message-ID: Uhh... is there any comment/explanation/comparison about the difference(s) of these two sets of files that anyone would care to offer? At the very least, why two? -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, September 30, 2002 10:42 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: WSDL on the web Hi all, Checkout the PSI WSDL files: ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.ServiceCapabilitiesInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.TargetDeviceSupportInterface.wsdl AND ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.ServiceCapabilitiesInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.TargetDeviceSupportInterface.wsdl Thanks Dave, Alan From dhall at hp.com Mon Sep 30 15:35:22 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: WSDL on the web Message-ID: <77261E830267D411BD4D00902740AC250B59721F@xvan01.vcd.hp.com> Lee.. Nope, not yet - the main difference is that one was generated by the Axis toolkit, the other by the Wasp toolkit. We are leaning towards the Axis version, as it appears to be simplier, and the Wasp toolkit generates some dependencies on Wasp supporting libraries / types. We are in the middle of generating server and client code from the WSDL, and this will probably give us a definitive answer as to which we go with. Also, the WSDL may require a bit of hand tweaking, but I hope not.. Dave -----Original Message----- From: Farrell, Lee [mailto:Lee.Farrell@cda.canon.com] Sent: Monday, September 30, 2002 11:33 AM To: ps@pwg.org Cc: alan_berkema@hp.com Subject: RE: PS> [PSI]: WSDL on the web Uhh... is there any comment/explanation/comparison about the difference(s) of these two sets of files that anyone would care to offer? At the very least, why two? -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Monday, September 30, 2002 10:42 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: WSDL on the web Hi all, Checkout the PSI WSDL files: ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/axis/org.pwg.psi.TargetDeviceSupportInterface.w sdl AND ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.JobControlInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.QueryEndPointsInterface.wsdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.ServiceCapabilitiesInterface.w sdl ftp://ftp.pwg.org/pub/pwg/ps/wasp/org.pwg.psi.TargetDeviceSupportInterface.w sdl Thanks Dave, Alan From alan_berkema at hp.com Tue Oct 1 16:27:07 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New docs & Java code Message-ID: <499DC368E25AD411B3F100902740AD650E6AD32D@xrose03.rose.hp.com> psi-spec90.doc = psi-spec-latest.pdf - latest clean version psi-spec38.doc = psi-spec38.pdf - Changes from the past on java89/org.pwg.psi.zip - java code version of the methods Thanks, Alan From imcdonald at sharplabs.com Wed Oct 2 13:51:02 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: New docs Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDBE@mailsrvnt02.enet.sharplabs.com> Hi Alan, Something's not quite right. See the excerpt from an FTP listing of the PSI directory below. Cheers, - Ira McDonald High North Inc -------------------------- -rw-r--r-- 1 ftp ftp 344763 Oct 1 16:19 psi-spec38.pdf -rw-r--r-- 1 ftp ftp 328520 Oct 1 16:20 psi-spec-latest.pdf -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com] Sent: Friday, September 27, 2002 11:36 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: New docs psi-spec37.doc = psi-spec-latest.pdf psi092602.doc = psi-model-view.pdf reference.xsd targetDevice.xsd interfaceIdentifer.xsd Thanks, Alan From alan_berkema at hp.com Mon Oct 7 11:50:49 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: next call 10/08/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD348@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday October 8 (USA) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) GetServiceAttributes 2) PSI Attribute Mandatory Optional? WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 10/1/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From harryl at us.ibm.com Tue Oct 8 02:01:56 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:15 2009 Subject: PS> Question about DocumentTypeSupportQuery Message-ID: In the ServiceCapabilities interface, the DocumentTypeSupportQuery has two parameters documentType:String targetDeviceIdentifier:String The targetDeviceIdentifier may be null or empty if the client only wishes to test whether the print service supports a particular documentType. What exactly does this mean? (What is the utility?) I'm thinking that a print service will support conversions "from and to" and it may be meaningless to ask the print service if it supports one side of the transform. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021008/cee1a897/attachment-0001.html From harryl at us.ibm.com Tue Oct 8 02:02:04 2002 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:02:15 2009 Subject: PS> Redundant operations in JobControl vs. TargetDeviceSupport interfaces? Message-ID: I had a task to write up a new use case and flow diagram. I got hung up as you can see below and need some explanation about the two ways for a client to associate a target device with a job and specify the document type transform. 1. Job is submitted to a printer via IPP or some other ?legacy? protocol a. Job is in some document format the printer does not support natively b. Printer will behave as both client and target device to engage print (transform) service. c. Printer does not want to poll to know when the print service has completed the transform and is ready to deliver the job 2. Using the TargetDeviceSupported Interface on the print service, Printer registers with print service as Target Device a. targetDeviceSupportInterface i. registerTargetDevice ii. deliveryMethod ? ?push? 3. Using the JobControl Interface on the print service, Printer (acting as client) defines targetDevice, specifies ?deliver? and requests a data type to translate to (of course the Printer will request the correct document format for itself? the whole point of this exercise). a. jobControlInterface i. createJob 1. targetDeviceIdentifier 2. deliverToTargetDevice = true 3. requestedTargetDeviceDataType OK HERE?S (ONE PLACE) WHERE I?M LOST 4. Using the targetDeviceSupportedInterface on the print service, Printer COULD associate the target device with the UID acquired during createJob (right?) and also request the target device data type a. targetDeviceSupportInterface i. associateTargetDevice 1. jobURI 2. userID 3. targetDeviceIdentifier 4. requestedTargetDeviceDataType What am I missing? Why do I feel like (3) and (4) are mostly redundant? Is one supposed to represent a longer term relationship between client and print service while the other should be thought of more as a ?per job? specification? ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021008/181d58c0/attachment-0001.html From alan_berkema at hp.com Tue Oct 8 12:57:34 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: next call 10/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD34E@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday October 15 (USA) Time: 8 AM (US PST) Number: 404-348-2002(T348-2002) ID: 55605 Agenda: 1) To Do & Action Progress 2) Get Service Capabilities 3) Mandatory Optional Attributes WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 10/1/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From imcdonald at sharplabs.com Wed Oct 9 13:21:26 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: W3C WG on Internationalization of Web Services Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDE7@mailsrvnt02.enet.sharplabs.com> Hi, Note the following (and see complete text of note below): - The Web Services (WS) Task Force is investigating the needs and problems in the area of internationalization of Web Services, in particular the dependency of Web Services on language, culture, region, and locale-related contexts. The chair of the Web Services Task Force is Addison Phillips, webMethods. See http://www.w3.org/International/ws for how you can participate. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Martin Duerst [mailto:duerst@w3.org] Sent: Thursday, October 03, 2002 9:21 AM To: www-international@w3.org Subject: Call for participation: I18N Activity WG Task Forces Dear Internationalizers, As announced at the International Unicode Conference in San Jose the W3C Internationalization Activity has recently been restructured, and the Internationalization Working Group (WG) and Interest Group (IG) have been re-chartered. We are sure that this will provide you with increased possibilities to contribute to Web Internationalization in the widest sense, and are looking forward to your participation. More information can be found at http://www.w3.org/International/about and in the WG charter http://www.w3.org/2002/05/i18n-recharter/WG-charter. The Working Group now consists of three Task Forces (see below) - The Core Task Force is continuing previous work: completing the Character Model for the World Wide Web and the Internationalized Resource Identifiers (IRIs) specifications, and continuing reviewing specifications produced by other W3C Working Groups. The chair of the WG and the Core Task Force is Misha Wolf, Reuters. See http://www.w3.org/International/core for how you can participate. - The Web Services (WS) Task Force is investigating the needs and problems in the area of internationalization of Web Services, in particular the dependency of Web Services on language, culture, region, and locale-related contexts. The chair of the Web Services Task Force is Addison Phillips, webMethods. See http://www.w3.org/International/ws for how you can participate. - The GEO (Guidelines, Education & Outreach) Task Force is helping to get the internationalization aspects of W3C technology better understood and more widely and consistently used. The chair of the GEO Task Force is Richard Ishida, W3C. See http://www.w3.org/International/geo/howto-join-geo for how you can participate. This list will be used for general public discussion on Web Internationalization, but with increased technical focus. Regards, Martin. #-#-# Martin J. Du"rst, I18N Activity Lead, World Wide Web Consortium #-#-# mailto:duerst@w3.org http://www.w3.org/People/D%C3%BCrst From alan_berkema at hp.com Wed Oct 9 18:49:48 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> RE: [PSI]: minutes 10/08/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD36D@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald *Amir Shahindoust * = attendance 10/08/02 Agenda 1) Review Harry's e-mail questions 2) Review the use of port 3700 3) Review ToDo list 4) Call for action Minutes: As a prelude Ira suggested that we move PSI defined schemas into a seperate directory. Dave mentioned that the spec already calls for them to be ps/0.95 so we will put them there. Action: Move them Owner: Alan Status: Open 1) Review Harry's e-mail questions The first question revolves around the use of DocumentTypeSupportQuery and what it means if the TargetDeviceidentifier is NULL and is this useful? After much good discussion we decided that we can really do this same thing with GetServiceAttributes as long as we explicitly provide an example of how to do it. So DocumentTypeSupportQuery will be removed from the spec. Action: Write up some examples for GetServiceAttributes Owner: Dave Status: Open Harry's other question was around his new use case, which we agreed was illustrated as Use model 5 in the requirements doc. The question was about RegisterTargetDevice vs. AssociateTargetDevice. These are not intended to used together and enable the different use models we have. Action: Write up a an Applicability statement for AssociateTargetDevice useful in firewall scenario etc. and is redundant otherwise. Owner: Dave Status: Open As we looked at use model % in the requirements doc, we noticed that numbering on the arrows were off. Action: Fix Numbers and post Owner: Alan Status: Open 2) Review the use of port 3700 PSI has proposed asking IAN for a static port assignment we are calling port 3700 (IANA will probably dictate what actually get). We debated this vs. just using a dynamic port. Ira had some valid reasons for a static port in data aggregation scenarios with routers and gateways. Decided that a static port will be used for QueryInterafceEndpoints. Other discovery protocols will be used to get the hostname and could return a dynamic port. If a port is provide further queries will use that dynamic port. Otherwise the static port will be used. Doesn't this still open us up to the problems with dynamic ports? Action: Provide a brief write that explains why dynamic ports have issues. Also could get a brief write up on why overloading port 80 is not a good idea. Owner: Ira Status: Open 3) Review ToDo list Dave walked us through the ToDo list see spec 0.90 an the seem to be under control. 4) Call for action We are currently at rev 0.90 and it's time to do your homework and to take a close look at the spec. Harry set a good example with his e-mail questions. We will post intervening revs and a 0.94 candidate 2 weeks before the F2F. Fixes from the F2F will be incorporate into the 0.95 candidate. Action: Review the spec. Owner: All Status: Open Thanks, Alan From PZehler at crt.xerox.com Thu Oct 10 06:51:22 2002 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:15 2009 Subject: PS> Java Print Service APIs Message-ID: All, Has any consideration been given to existing Java print APIs (based on IPP) and their relationship to PSI? http://java.about.com/gi/dynamic/offsite.htm?site=http://java.sun.com/j2se/1 .4/docs/guide/jps/index.html Pete 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021010/af39467f/attachment-0001.html From imcdonald at sharplabs.com Fri Oct 11 14:09:18 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> PWG Parameters for MIME types ("document-format" values) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDEA@mailsrvnt02.enet.sharplabs.com> Hi folks, Friday (11 October 2002) Per my action item from Tuesday's PSI Telecon: Below are four proposed PWG standard optional parameters for MIME types, all extracted directly from the attributes (so-called SNMP 'objects') defined in the InterpreterTable of the Printer MIB (see comments below). Any of these PWG parameters MAY be appended (unordered) to any MIME type value of the IPP/PWG SM "document-format" attribute, for example: application/vnd.hp-pcl;pwg-pdl-resolution="400,400,dpi" These PWG parameters are specified in Augmented Backus-Naur Form (ABNF, RFC 2234). Every element used in one of these PWG parameter ABNF productions is defined in an excerpt from ABNF (RFC 2234), MIME Part One (RFC 2045), or Internet Message Format (RFC 2822) at the end of this note. According to RFC 2045: (1) Parameters MUST be ignored when unrecognized; (2) Parameters MUST be ignored when comparing values of MIME types; (3) MIME type names MUST be treated as case-insensitive; (4) MIME parameter names MUST be treated as case-insensitive; (5) MIME parameter values MUST be treated as case-sensitive. Each parameter name begins with a "pwg-" (namespace) prefix, to ensure that it is safely ignored by existing MIME-enabled software and systems. ; prtInterpreterLangLevel OCTET STRING ; - not supported in IPP/PWG SM pdl-level = "pwg-pdl-level" ; PDL language level "=" quoted-string ; e.g., "5e" for HP PCL ; or "2" for Adobe PostScript ; prtInterpreterLangVersion OCTET STRING ; - not supported in IPP/PWG SM pdl-version = "pwg-pdl-version" ; PDL version or date code "=" quoted-string ; e.g., "4027" for PostScript ; prtInterpreterDescription PrtLocalizedDescriptionStringTC ; - not supported in IPP/PWG SM pdl-desc = "pwg-pdl-desc" ; PDL description "=" quoted-string ; e.g., "Adobe PostScript..." ; prtInterpreterFeedAddressability Integer32, ; prtInterpreterXFeedAddressability Integer32, ; - see "printer-resolution" in IPP/PWG SM pdl-res = "pwg-pdl-resolution" ; PDL resolution "=" quoted-string ; cross-feed "," feed "," units ; cross-feed = 1*DIGIT ; feed = 1*DIGIT ; units = "dpi" / "dpcm" ; dots/inch or dots/centimeter ; e.g., "300,600,dpi" means ; 300 cross-feed X 600 feed DPI The following Interpreter attributes from the Printer MIB are omitted (for the reasons noted below): ; prtInterpreterLangFamily PrtInterpreterLangFamilyTC, ; - see "document-format" in IPP/PWG SM ; prtInterpreterVersion OCTET STRING, ; - redundant with prtInterpreterLangVersion ; prtInterpreterDefaultOrientation PrtPrintOrientationTC, ; - see "orientation-requested-default" in IPP/PWG SM ; prtInterpreterDefaultCharSetIn IANACharset, ; - see "charset-configured" in IPP/PWG SM ; prtInterpreterDefaultCharSetOut IANACharset, ; - not supported in IPP/PWG SM - only useful for softcopy output ; prtInterpreterTwoWay PrtInterpreterTwoWayTC ; - not supported in IPP/PWG SM - bidirectional print channel Cheers, - Ira McDonald, co-editor of Printer MIB v2 High North Inc ------------------------------------------------------------------------ [from "MIME Part Two: Media Types", RFC 2046] > Parameters are modifiers of the media subtype, and as such do not > fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their > defining media type or subtype or they may be optional. MIME > implementations must also ignore any parameters whose names they do > not recognize. ------------------------------------------------------------------------ [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] DIGIT = %x30-39 DQUOTE = %x22 ------------------------------------------------------------------------ [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] parameter = attribute "=" value attribute = token ; Matching of attributes ; is ALWAYS case-insensitive. value = token / quoted-string token = 1* tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values ------------------------------------------------------------------------ [from "Internet Message Format", RFC 2822] quoted-string = [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS] A quoted-string is treated as a unit. That is, quoted-string is identical to atom, semantically. Since a quoted-string is allowed to contain FWS, folding is permitted. Also note that since quoted-pair is allowed in a quoted-string, the quote and backslash characters may appear in a quoted-string so long as they appear as a quoted-pair. Semantically, neither the optional CFWS outside of the quote characters nor the quote characters themselves are part of the quoted-string; the quoted-string is what is contained between the two quote characters. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS/CFWS that appears within the quoted-string are semantically "invisible" and therefore not part of the quoted-string either. <...> CFWS = *([FWS] comment) (([FWS] comment) / FWS) FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space obs-FWS ctext = NO-WS-CTL / ; Non white space controls %d33-39 / ; The rest of the US-ASCII %d42-91 / ; characters not including "(", %d93-126 ; ")", or "\" ccontent = ctext / quoted-pair / comment comment = "(" *([FWS] ccontent) [FWS] ")" Throughout this standard, where FWS (the folding white space token) appears, it indicates a place where header folding, as discussed in section 2.2.3, may take place. Wherever header folding appears in a message (that is, a header field body containing a CRLF followed by any WSP), header unfolding (removal of the CRLF) is performed before any further lexical analysis is performed on that header field according to this standard. That is to say, any CRLF that appears in FWS is semantically "invisible." A comment is normally used in a structured field body to provide some human readable informational text. Since a comment is allowed to contain FWS, folding is permitted within the comment. Also note that since quoted-pair is allowed in a comment, the parentheses and backslash characters may appear in a comment so long as they appear as a quoted-pair. Semantically, the enclosing parentheses are not part of the comment; the comment is what is contained between the two parentheses. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS that appears within the comment are semantically "invisible" and therefore not part of the comment either. Runs of FWS, comment or CFWS that occur between lexical tokens in a structured field header are semantically interpreted as a single space character. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Fri Oct 11 14:26:04 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> Port for PSI - Static vs Dynamic issues Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDEB@mailsrvnt02.enet.sharplabs.com> Hi, Per my action item from Tuesday's PSI Telecon: PSI interfaces SHOULD have a static port (IANA-registered by vendor 'PWG') that is always the PSI listen port. PSI interfaces SHOULD NOT use dynamic ports (even by protocol agreement during PSI WSDL sessions), because: 1) Firewalls and NAT (Network Address Translator) systems assume that all protocols allowed to pass (traverse the domain boundary) use static IANA-registered ports (permission rules are normally based on a specific application protocol over a specific numbered port). Firewalls/NATs often implement ALGs (Application Layer Gateways) that enforce fine-grained permission rules. But the premise is always that the protocol on a given port is INVARIANT, and is determined by the port number (FTP proxies are fundamentally dangerous, for this reason). Dynamic ports completely defeat ALGs and firewall permissions (thus destroying the 'security perimeter' of the firewall). (There are a series of horrible exceptions in ALGs around HTTP port 80, due to other 'hidden' application protocols - PSI should not go there...) 2) Boundary routers (between enterprise and public networks) and core routers (within the Internet backbone) manage quality of service and packet delivery by 'aggregating' destinations (host/port pairs) for routing decisions. Dynamic ports completely defeat traffic 'aggregation' (because the router has no way to know that the alternate port traffic is associated with the original static port traffic). Routers also block all ports that are not specifically authorized to cross a domain boundary (in one direction or the other - not necessarily both) in their permission rules. Dynamic ports simply won't work in the general case. Hope this helps. Cheers, - Ira McDonald High North Inc From alan_berkema at hp.com Tue Oct 15 18:00:12 2002 From: alan_berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: minutes 10/15/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD38C@xrose03.rose.hp.com> Lots of new actions folks, scan for your name! PSI Working Group: *Alan Berkema *Gail Songer *Dave Hall *Jerry Thasher *Harry Lewis *Ted Tronson *Peter Mierau Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 10/15/02 Agenda 1) To Do & Action Progress 2) Get Service Capabilities 3) Mandatory Optional Attributes 10/15/02 Minutes: See updated status and new discussion in line. 1) To Do & Action Progress Walked through the previous actions and covered the second agenda item as one of the actions. > 10/08/02 Minutes: > As a prelude Ira suggested that we move PSI defined schemas > into a seperate > directory. Dave mentioned that the spec already calls for > them to be ps/0.95 > so we will put them there. > > Action: Move them > Owner: Alan Status: Done > > 1) Review Harry's e-mail questions > The first question revolves around the use of DocumentTypeSupportQuery > and what it means if the TargetDeviceidentifier is NULL and > is this useful? > After much good discussion we decided that we can really do > this same thing > with > GetServiceAttributes as long as we explicitly provide an > example of how to > do it. > So DocumentTypeSupportQuery will be removed from the spec. > > Action: Write up some examples for GetServiceAttributes > Owner: Dave Status: Started Dave reviewed the examples he started with. GetServiceAttributes passes in requestedAttributes which is an XML instance document using that conforms to pwgAttr.xsd. snippet: 4 If an empty element is used, the response is all of the values that a service or the targetDevice supports. In the case of copies the response might be 1 throught 99. In the case of duplex, if this is a boolean ine the pwgAttr schema it might be True or False etc. If an element has a value than the printer or service indicates whether or not it can accomodate the specific value. What actually gets returned here? How about 4 - Means yes, and or Means No? More details on the examples revelaed in next rev. of the spec. In GetServiceAttributes is the targetDeviceIdentfier mandatory? Yes, though what if the Service knows about mant targets? Could someone respond with the discussion on why the answer is still Yes. I recall bits of the discussion though my note taking while hold the phone up to my ear was lacking. Next we looked for exactly what the "type" of element DocumentFormat is? Need to ask at SM meeting. Action: Discuss Document Format at SM meeting 10/17/02 Owner: Ira, Peter Z., Dave (I may not make this meeting) Status: Open Action: Write up some examples for a document type support query Owner: Dave Status: Open Action: Discuss Non ambiguous element names at SM meeting 10/17/02 Owner: Ira, Peter Z., Dave (I may not make this meeting) Status: Open Action: Have something to share on alternatives to returning a Schema in GetServiceAttributes by the next call. Owner: Bob Status: Open Action: Add an additional parameter for natural language & char set Owner: Dave Status: Open > > Harry's other question was around his new use case, which we agreed > was illustrated as Use model 5 in the requirements doc. The > question was > about > RegisterTargetDevice vs. AssociateTargetDevice. These are not > intended to > used > together and enable the different use models we have. > > Action: Write up a an Applicability statement for > AssociateTargetDevice > useful in firewall scenario etc. and is redundant otherwise. > Owner: Dave > Status: Open > > As we looked at use model 5 in the requirements doc, we noticed that > numbering on the > arrows were off. > > Action: Fix Numbers and post > Owner: Alan > Status: Open Action: Include trace diagram for use model 5 in the requirements doc Owner: Dave Status: Done, the example uses PSI in a dynamic nature Action: Include trace diagram for use model 5 in the requirements doc that shows pre configuration Owner: Dave Status: Open Discussion on how JobID works in above use model. Did we get an action out of this? Spec need some discussion on the way this should be handled? Action: Ask IANA for PSI port number Owner: Harry Status: Done, expect one in 30 days, likely not 3700 This is about as far as we got touched on the next one, though may want to discuss some more. Likely that we will not allow dynamic ports at any time. > > 2) Review the use of port 3700 > PSI has proposed asking IAN for a static port assignment we > are calling port > 3700 (IANA will probably dictate what actually get). > We debated this vs. just using a dynamic port. Ira had some > valid reasons > for > a static port in data aggregation scenarios with routers and gateways. > Decided that a static port will be used for QueryInterafceEndpoints. > Other discovery protocols will be used to get the hostname > and could return > a dynamic port. If a port is provide further queries will use > that dynamic > port. > Otherwise the static port will be used. > Doesn't this still open us up to the problems with dynamic ports? > > Action: Provide a brief write that explains why dynamic ports > have issues. > Also could get a brief write up on why overloading port 80 is > not a good > idea. > Owner: Ira > Status: Open > > 3) Review ToDo list > Dave walked us through the ToDo list see spec 0.90 an the > seem to be under control. > > 4) Call for action > We are currently at rev 0.90 and it's time to do your homework and to > take a close look at the spec. Harry set a good example with > his e-mail > questions. We will post intervening revs and a 0.94 candidate > 2 weeks before the F2F. Fixes from the F2F will be > incorporate into the > 0.95 candidate. > > Action: Review the spec. > Owner: All > Status: Open > > Thanks, > Alan From imcdonald at sharplabs.com Tue Oct 15 18:43:06 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: LISA Forum Europe - November 4-7, 2002 in Heidelberg, German y Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDF7@mailsrvnt02.enet.sharplabs.com> Hi, FYI - a good conference on localization coming up 4-7 November. Cheers, - Ira McDonald High North Inc -----Original Message----- From: Michael Anobile [mailto:lisa@lisa.org] Sent: Tuesday, October 15, 2002 2:55 PM To: imcdonald@sharplabs.com Subject: LISA Forum Europe - November 4-7, 2002 in Heidelberg, Germany * Agenda Update * THE LISA FORUM EUROPE Multilingual Content Authoring, Web-Services, Workflow and your Company's ROI 4-7 November 2002 * Heidelberg, Germany REGISTER http://www.lisa.org/events/2002europe/registration.html AGENDA http://www.lisa.org/events/2002europe/agenda.html PARTICIPANTS http://www.lisa.org/events/2002europe/participants_list.html WORKSHOPS http://www.lisa.org/events/2002europe/workshops/ ------------------------------------------------------------------------ LISA's 44th international conference and exhibition focuses on the optimization of technologies and standards in global web services. Through workshops, discussion groups, case studies and panels, you will learn from clients and end-users how standards in technology and business are providing unprecedented ROI and strategic advantage in today's increasingly competitive global marketplace. The program will feature: * Localizing Europe's air travel industry - An Amadeus Corporation Case Study * The business case for enterprise terminology - A Cisco Systems ROI presentation * Improving the ROI of the Authoring Environment and CMS - A Philip Morris Case Study * Clients and Developers measure customer satisfaction and MT's ROI * The Scope, Challenges and Oulook of Today's Translation Industry * OSCAR Survey Results: Analyzing content authoring and content localization * Standards in the GILT industry - what's working, what isn't, and why? * Special sessions: SME Profiles - Terminology - XML and Localization * LISA WORKSHOPS - Managing Localization Projects - Reducing Localization Costs with XML-based Technology - Evaluating Website Globalization Systems - L10n & I18n Testing - Internationalization: Preparing Software and Web Sites for Translation -- Workgroup leaders, speakers and invited guests include -- Acrolinx * Amadeus * Belga News Agency * Cisco Systems * Corporate Language Services * Comprendium Technologies * The Economist * Euro RSCG Wnek Gosper * GlobalSight * Herald Tribune International * Hewlett-Packard * i18N Inc * IAI Saarbrucken * IBM * Interverbum * IP Options * Isogen International * JD Edwards * LionBridge * Logitech * Logos Group * OASIS * Philip Morris International * RWS Group * SAP * SDL International * Software AG * STAR Group * Trados * USAF Research Lab * Venturi Partners * Wall Street Journal * Welocalize * WH&P * Xplanation * AUTOMATED WORKFLOW TOOLS AND LOCALIZATION SERVICES EXHIBITION The industry's leading technology developers for automated language processing systems, web-services, internationalization, translation and localization suppliers will demonstrate their products and services. LISA Forum Exhibitors SDL * Star Group * Trados * GlobalSight * ISOGEN * Xplanation * Comprendium * Telelingua * PASS Engineering * Connect Global Solutions * Translate.IT LISA Forum Europe Hosts and Member Sponsors SAP AG * WH&P - Wegwitz, Hoser & Partners * IBM * Hewlett Packard * SMP Marketing SarL * with the collaboration of * OASIS * Logos SpA * Donau University ================================================ - Notices - ================================================ LISA is the premier organization providing the mechanisms, services and networking for professionals interested in sharing information on the development of globalization and localization processes, tools, web services and international business models. Formed in 1990, today LISA members comprise 210 companies employing over 400,000 people in 65 countries. * We apologize if you received duplicates of this announcement. * If you would like to UNSUBSCRIBE please go to http://www.lisa.org/interact/announce.html ======================================================================== From imcdonald at sharplabs.com Mon Oct 21 16:21:05 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> FW: [Comments on PSI Requirements Spec] Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE02@mailsrvnt02.enet.sharplabs.com> Hi, I got these as personal mail from Anubhav Saxena. Forwarded for the experts to respond to... Cheers, - Ira McDonald High North Inc PS - Anubhav - To post to the list, send mail to 'ps@pwg.org'. -----Original Message----- From: Anubhav Saxena [mailto:anubhav.saxena@wipro.com] Sent: Monday, October 21, 2002 8:11 AM To: McDonald Ira Subject: RE: PS> FW: LISA Forum Europe - November 4-7, 2002 in Heidelberg, Germany Hi, I am Anubhav from Wipro, India. I am interested in your specification of PSI and I am subscribed to the mailing list as well. I am sorry if I am not supposed to post in message on PSI to you this way, however I assure you that once I know the protocol, I will stick to it. Following is my comment on the Requirement Specs of PSI. After reading the speicification document I see a note on page 17. This is actually an issue "How does the mobile device know that it can use Model 3 instead of needing use model 2". I see the following options: a) Model 2 is one, wherein the mobile device is 1. more capable than in model 3 (hence is probably costlier) b) Model 2 is one, wherein the print service is 1. capable of handling lesser channels of simultaneous communications than in model 3 2. for some reason not able to talk to printer Hence i feel that a mobile will need to take a decision to go in for 2/3 based on 1. Existing protocol support on the mobile itself 2. May be depending of the level of support provided by the print services 3. Current load on the mobile/print service However I am not sure about other issues that may be underlying this. Best Regards, Anubhav. -------------- next part -------------- **************************Disclaimer************************************************** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. **************************************************************************************** From dhall at hp.com Mon Oct 21 18:46:14 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> WEBEX info for 10/22 - #22188390 newpsi Message-ID: <77261E830267D411BD4D00902740AC250DB4BB14@xvan01.vcd.hp.com> Hey All.. Here is the WEBEX info for tomorrows meeting.. Dave ------------------------- 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: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Date: 10/22/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 22188390 Meeting Password: newpsi Teleconference: None. Agenda: Host: David Hall 1(360)212x4228 mailto:dhall@hp.com http://www.webex.com We've got to start meeting like this(TM) From dhall at hp.com Tue Oct 22 11:00:32 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> WEBEX info for 10/22 - #22188390 newpsi 404-348-2002 #556 05 Message-ID: <77261E830267D411BD4D00902740AC250DB4BB26@xvan01.vcd.hp.com> -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Monday, October 21, 2002 3:46 PM To: 'ps@pwg.org' Subject: PS> WEBEX info for 10/22 - #22188390 newpsi Hey All.. Here is the WEBEX info for tomorrows meeting.. Dave ------------------------- 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: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Date: 10/22/2002 Time: 8:00AM, (GMT -07:00) Pacific Time, USA & Canada (DayLight Time) Meeting Number: 22188390 Meeting Password: newpsi Teleconference: None. Agenda: Host: David Hall 1(360)212x4228 mailto:dhall@hp.com http://www.webex.com We've got to start meeting like this(TM) From dhall at hp.com Tue Oct 22 13:55:45 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> PSI WSDL Interface Specification - To strongly type or not? Message-ID: <77261E830267D411BD4D00902740AC250DB4BB2B@xvan01.vcd.hp.com> Hey All... We currently have our parameters in PSI defined mostly as Strings, (jobProcessingAttributes for example), and are relying on the PWG SM schemas to provide the strong typing for the structure that the string contains.. One option is to strongly type the parameters as a complex type rather than a string... I hate to open up this can of worms, but... So far, I've heard of 3 different approaches for this... I've tried to summarize the advantages / disadvantages for each of the approaches. Please add your thoughts to the discussion.. Dave Strongly Typed WSDL Parameters Discussion One of the discussions that has been going on is around our WSDL definition of the PSI interfaces. There are three possibilities that have presented themselves: 1) The parameters (for example, jobProcessingAttributes) should be encoded as a string defined by a schema. Extensions are added within the XML document... 2) The parameters should be encoded as a strongly typed complex type, extensions are added as new, vendor defined elements. 3) The parameters should be encoded as a strongly typed complex type, where the last parameter is a string[] of structures. There are a number of advantages and dis-advantages to each which I have tried to capture here: 1) String parameters defined by schema: This is the current model for the PSI interface specification.. Advantages: * Easily (understandably) extensible at the element level by the application. * Clients can code up only the elements that they wish to deal with. * Allows name-space extensions to the interfaces through the QueryEndPoints mechanism. (ie, give me the JobControlInterface that understands the pwg common semantic model, and give me the JobControlInterface that understands the Digital Imaging semantic model.) * Interoperability between toolkits. The simple types are readily encoded / decoded by the toolkits. * A 1.0 server (think existing printer that talks 1.0 psi) would be able to interpret a 2.0 clients request. (Assuming the method signatures didn't change - it would simply ignore the elements it did not understand.) * A 2.0 server (Think new print service) could interpret a 1.0 client request (Assuming no new mandatory elements were added...) * A reference to the schema that defines the parameters can simply be made in the interface documentation. Disadvantages: * We need to hand generate the serializers / deserializers * Interoperability between devices is not enforced by a strongly typed interface. 2) Complex type parameters Advantages: * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. * Aligns with UPnP direction Disadvantages: * How to deal with the #any extensions in the toolkits? (Thought is that you inherit from the toolkit generated serializer, and add extensibility yourself) * Toolkit incompatibilities (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server, the burden would be on the client to also be able to talk the 1.0 interface specification. 3) Complex type parameters with string[] of structures element at the end Advantages: * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. Disadvantages: * Toolkit incompatibilities - structures within structures have been problematic in the past. (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server (assuming new elements are added to the base definition), the burden would be on the client to also be able to talk the 1.0 interface specification. From dhall at hp.com Tue Oct 22 14:05:26 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> PSI WSDL Interface Specification - To strongly type or no t? Message-ID: <77261E830267D411BD4D00902740AC250DB4BB2C@xvan01.vcd.hp.com> Ouch, we lost our formatting.. Here is an easier to read version: Hey All... We currently have our parameters in PSI defined mostly as Strings, (jobProcessingAttributes for example), and are relying on the PWG SM schemas to provide the strong typing for the structure that the string contains.. One option is to strongly type the parameters as a complex type rather than a string... I hate to open up this can of worms, but... So far, I've heard of 3 different approaches for this... I've tried to summarize the advantages / disadvantages for each of the approaches. Please add your thoughts to the discussion.. Dave Strongly Typed WSDL Parameters Discussion: One of the discussions that has been going on is around our WSDL definition of the PSI interfaces. There are three possibilities that have presented themselves: 1) The parameters (for example, jobProcessingAttributes) should be encoded as a string defined by a schema. Extensions are added within the XML document... 2) The parameters should be encoded as a strongly typed complex type, extensions are added as new, vendor defined elements. 3) The parameters should be encoded as a strongly typed complex type, where the last parameter is a string[] of structures. There are a number of advantages and dis-advantages to each which I have tried to capture here: 1) String parameters defined by schema: This is the current model for the PSI interface specification.. Advantages: ---------------------- * Easily (understandably) extensible at the element level by the application. * Clients can code up only the elements that they wish to deal with. * Allows name-space extensions to the interfaces through the QueryEndPoints mechanism. (ie, give me the JobControlInterface that understands the pwg common semantic model, and give me the JobControlInterface that understands the Digital Imaging semantic model.) * Interoperability between toolkits. The simple types are readily encoded / decoded by the toolkits. * A 1.0 server (think existing printer that talks 1.0 psi) would be able to interpret a 2.0 clients request. (Assuming the method signatures didn't change - it would simply ignore the elements it did not understand.) * A 2.0 server (Think new print service) could interpret a 1.0 client request (Assuming no new mandatory elements were added...) * A reference to the schema that defines the parameters can simply be made in the interface documentation. Disadvantages: ---------------------- * We need to hand generate the serializers / deserializers * Interoperability between devices is not enforced by a strongly typed interface. 2) Complex type parameters Advantages: ---------------------- * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. * Aligns with UPnP direction Disadvantages: ---------------------- * How to deal with the #any extensions in the toolkits? (Thought is that you inherit from the toolkit generated serializer, and add extensibility yourself) * Toolkit incompatibilities (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server, the burden would be on the client to also be able to talk the 1.0 interface specification. 3) Complex type parameters with string[] of structures element at the end Advantages: ---------------------- * Serializers and de-serializers generated by toolkits automatically. * Interoperability between devices is more enforced by the strongly typed interface. Disadvantages: ---------------------- * Toolkit incompatibilities - structures within structures have been problematic in the past. (Thought to be somewhat mitigated at this point.) * A 2.0 client would not be able to talk to a 1.0 server (assuming new elements are added to the base definition), the burden would be on the client to also be able to talk the 1.0 interface specification. From imcdonald at sharplabs.com Wed Oct 23 19:10:37 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> Revised PWG std MIME parameters ABNF (23 Oct 2002) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE09@mailsrvnt02.enet.sharplabs.com> Hi folks, Wednesday (23 October 2002) [Per my action item from the PWG PSI Telecon on 8 October 2002)] After talking with Tom Hastings about CIP4 JDF needs, some revised ABNF for IEEE/ISTO "IPP: PWG Standard MIME Parameters for Document Formats". All but one of these parameters were derived from the InterpreterTable defined in Printer MIB [RFC 1759]. Problem Statement: Registered MIME types (for example, used as values of the 'document-format' Job attribute in IPP/1.1 [RFC 2910, RFC 2911]) are imprecise. PWG PSI, CIP4 JDF, FSG PAPI, and FSG Job Ticket working groups have all identified a requirement for document format metadata. Rejected Solution: A data structure with the required metadata - works well within a given interface - but incompatible with 'cut-and-paste'. Proposed Solution: PWG standard optional MIME parameters - may be appended to _any_ registered MIME type to add the required metadata - compatible with 'cut-and-paste' across all applications (because the parameters are actually _part of_ the same MIME type "word" in the source text). Tom Hastings and I plan to write IEEE/ISTO 5100.10 "IPP: PWG Standard MIME Parameters for Document Formats". Watch for an announcement. Cheers, - Ira McDonald, co-editor of Printer MIB v2 High North Inc ------------------------------------------------------------------------ [PWG Standard MIME Parameters] In the printer industry, a document format MIME type is one of: (a) PDL - page description language (e.g., HTML or Adobe PostScript) (b) JCL - job control language (e.g., HP PJL) (c) JDL - job definition language (e.g., CIP4 JDF) (d) text - plaintext, richtext, HTML, SGML, XML, etc. Any PWG standard MIME parameter MAY be appended (unordered) to any document format, for example: application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (HP PCL 400x400 dpi) These PWG parameters are specified in Augmented Backus-Naur Form (ABNF, RFC 2234). Every element used in one of these PWG parameter ABNF productions is defined in an excerpt from ABNF (RFC 2234), MIME Part One (RFC 2045), or Internet Message Format (RFC 2822) at the end of this note. Each parameter name begins with a "pwg-" (namespace) prefix, to ensure that it is safely ignored by existing MIME-enabled software and systems. According to RFC 2045: (1) Parameters MUST be ignored when unrecognized; (2) Parameters MUST be ignored when comparing values of MIME types; (3) MIME type names MUST be treated as case-insensitive; (4) MIME parameter names MUST be treated as case-insensitive; (5) MIME parameter values MUST be treated as case-sensitive. document-format = type "/" subtype *[parameter] *[pwg-parameter] ; MIME type (plus optional parameters) pwg-parameter = ";" pl-level / pl-build / pl- prof / pl-desc / pl-res ; PWG standard parameter with a 'quoted-string' value Desc: Document format See: Section 5.1 in MIME Part One [RFC 2045] for ABNF definition of 'type', 'subtype', and 'parameter' See: Section 4.1.9 in IPP/1.1 Model and Semantics [RFC 2911] for definition of 'mimeMediaType' syntax pl-level = "pwg-lang-level" "=" quoted-string Desc: Language level (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterLangLevel' Examples: application/postscript;pwg-lang-level="2" (Adobe PostScript Level 2) application/vnd.hp-pcl;pwg-lang-level="5e" (HP PCL 5e) application/vnd.cip4-jdf+xml;pwg-lang-level="1.1" (CIP4 JDF 1.1) pl-prof = "pwg-lang-profile" "=" quoted-string Desc: Language profile (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' Examples: application/pdf;pwg-lang-profile="ISO-15930-3" (PDF-X3:2002) pl-build = "pwg-lang-build" "=" quoted-string Desc: This implementation's build ID (i.e., date code or version). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterLangVersion' Examples: application/vnd.hp-pcl;pwg-lang-build="20021025" (HP PCL) application/postscript;pwg-lang-build="AP4027.45..3" (Adobe PS) pdl-lang-res = "pwg-lang-resolution" "=" res-value res-value = DQUOTE res-xfeed "," res-feed "," res-units DQUOTE ; quoted string res-xfeed = 1*DIGIT ; cross-feed direction resolution res-feed = 1*DIGIT ; feed direction resolution res-units = "dpi" / "dpcm" ; resolution units of dots/inch or dots/centimeter Desc: Language resolution, expressed as "xfeed,feed,units". Human-readable information, suitable for client UI and debug. Also suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 4.2.12 in IPP/1.1 Model and Semantics [RFC 2911] for definition of 'printer-resolution' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterXFeedAddressability' and 'prtInterpreterFeedAddressability' See: Section 14 'The Marker Group' in Printer MIB [RFC 1759] for definition of 'prtMarkerAddressabilityUnit' Examples: application/postscript;pwg-lang-res="300,600,dpi" (300x600 dpi) application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (400x400 dpi) pl-desc = "pwg-lang-desc" "=" quoted-string Desc: Language description. Human-readable information, suitable for client UI and debug. Not suitable for use by automata. Note: This parameter should be _last_, since embedded whitespace may terminate 'cut-and-paste'. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterDescription' Examples: application/postscript;pwg-lang-desc="Adobe PostScript Level 2" application/vnd.hp-pcl;pwg-lang-desc="HP PCL Level 5e - 25 Oct 2002" The following Interpreter attributes from the Printer MIB are omitted (for the reasons noted below): 'prtInterpreterLangFamily' - language family (i.e., simple MIME type) - see 'document-format' in IPP/1.1 Model [RFC 2911] 'prtInterpreterVersion' - more free-form interpreter language version info - redundant with 'prtInterpreterLangVersion' in Printer MIB 'prtInterpreterDefaultOrientation' - default orientation (portrait or landscape) - see "orientation-requested-default" in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetIn' - default input charset (to avoid charset 'guessing') - see 'charset-configured' in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetOut' - default output charset, - only useful for softcopy output (i.e., 'print-to-file') - not supported in IPP/1.1 Model [RFC 2911] 'prtInterpreterTwoWay' - indicates support for bidirectional print channel - not supported in IPP/1.1 Model [RFC 2911] ------------------------------------------------------------------------ [from "MIME Part Two: Media Types", RFC 2046] > Parameters are modifiers of the media subtype, and as such do not > fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their > defining media type or subtype or they may be optional. MIME > implementations must also ignore any parameters whose names they do > not recognize. ------------------------------------------------------------------------ [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] DIGIT = %x30-39 DQUOTE = %x22 ------------------------------------------------------------------------ [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] parameter = attribute "=" value attribute = token ; Matching of attributes ; is ALWAYS case-insensitive. value = token / quoted-string token = 1* tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values ------------------------------------------------------------------------ [from "Internet Message Format", RFC 2822] quoted-string = [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS] A quoted-string is treated as a unit. That is, quoted-string is identical to atom, semantically. Since a quoted-string is allowed to contain FWS, folding is permitted. Also note that since quoted-pair is allowed in a quoted-string, the quote and backslash characters may appear in a quoted-string so long as they appear as a quoted-pair. Semantically, neither the optional CFWS outside of the quote characters nor the quote characters themselves are part of the quoted-string; the quoted-string is what is contained between the two quote characters. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS/CFWS that appears within the quoted-string are semantically "invisible" and therefore not part of the quoted-string either. <...> CFWS = *([FWS] comment) (([FWS] comment) / FWS) FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space obs-FWS ctext = NO-WS-CTL / ; Non white space controls %d33-39 / ; The rest of the US-ASCII %d42-91 / ; characters not including "(", %d93-126 ; ")", or "\" ccontent = ctext / quoted-pair / comment comment = "(" *([FWS] ccontent) [FWS] ")" Throughout this standard, where FWS (the folding white space token) appears, it indicates a place where header folding, as discussed in section 2.2.3, may take place. Wherever header folding appears in a message (that is, a header field body containing a CRLF followed by any WSP), header unfolding (removal of the CRLF) is performed before any further lexical analysis is performed on that header field according to this standard. That is to say, any CRLF that appears in FWS is semantically "invisible." A comment is normally used in a structured field body to provide some human readable informational text. Since a comment is allowed to contain FWS, folding is permitted within the comment. Also note that since quoted-pair is allowed in a comment, the parentheses and backslash characters may appear in a comment so long as they appear as a quoted-pair. Semantically, the enclosing parentheses are not part of the comment; the comment is what is contained between the two parentheses. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS that appears within the comment are semantically "invisible" and therefore not part of the comment either. Runs of FWS, comment or CFWS that occur between lexical tokens in a structured field header are semantically interpreted as a single space character. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Fri Oct 25 21:29:27 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE11@mailsrvnt02.enet.sharplabs.com> Hi folks, Friday (25 October 2002) [Per my action item from the PWG PSI Telecon on 8 October 2002)] Further revised ABNF for three PWG parameters for MIME document formats. Two of these parameters (pwg-lang-level and pwg-lang-desc) were derived from the InterpreterTable defined in Printer MIB [RFC 1759]. The other parameter (pwg-lang-profile) was suggested by Tom Hastings. Problem Statement: Registered MIME types (for example, used as values of the 'document-format' Job attribute in IPP/1.1 [RFC 2910, RFC 2911]) are imprecise. PWG PSI, CIP4 JDF, FSG PAPI, and FSG Job Ticket working groups have all identified a requirement for document format metadata. Rejected Solution: A data structure with the required metadata - works well within a given interface - but incompatible with 'cut-and-paste'. Proposed Solution: PWG standard optional MIME parameters - may be appended to _any_ registered MIME type to add the required metadata - compatible with 'cut-and-paste' across all applications (because the parameters are actually _part of_ the same MIME type "word" in the source text). Tom Hastings and I plan to write a proposal for "IPP: PWG Standard MIME Parameters for Document Formats". Watch for an announcement. Cheers, - Ira McDonald, co-editor of Printer MIB v2 High North Inc ------------------------------------------------------------------------ [PWG Standard MIME Parameters] In the printer industry, a document format MIME type is one of: (a) PDL - page description language (e.g., HTML or Adobe PostScript) (b) JCL - job control language (e.g., HP PJL) (c) JDL - job definition language (e.g., CIP4 JDF) (d) text - plaintext, richtext, HTML, SGML, XML, etc. Any PWG standard MIME parameter MAY be appended (unordered) to any document format, for example: application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (HP PCL 400x400 dpi) These PWG parameters are specified in Augmented Backus-Naur Form (ABNF, RFC 2234). Every element used in one of these PWG parameter ABNF productions is defined in an excerpt from ABNF (RFC 2234), MIME Part One (RFC 2045), or Internet Message Format (RFC 2822) at the end of this note. Each parameter name begins with a "pwg-" (namespace) prefix, to ensure that it is safely ignored by existing MIME-enabled software and systems. According to RFC 2045: (1) Parameters MUST be ignored when unrecognized; (2) Parameters MUST be ignored when comparing values of MIME types; (3) MIME type names MUST be treated as case-insensitive; (4) MIME parameter names MUST be treated as case-insensitive; (5) MIME parameter values MUST be treated as case-sensitive. document-format = type "/" subtype *[parameter] *[pwg-parameter] ; MIME type (plus optional parameters) pwg-parameter = ";" pl-level / pl-build / pl- prof / pl-desc / pl-res ; PWG standard parameter with a 'quoted-string' value Desc: Document format See: Section 5.1 in MIME Part One [RFC 2045] for ABNF definition of 'type', 'subtype', and 'parameter' See: Section 4.1.9 in IPP/1.1 Model and Semantics [RFC 2911] for definition of 'mimeMediaType' syntax pl-level = "pwg-lang-level" "=" quoted-string Desc: Language level and/or version (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterLangLevel' Examples: application/postscript;pwg-lang-level="2" (Adobe PostScript Level 2) application/vnd.hp-pcl;pwg-lang-level="5e" (HP PCL 5e) application/vnd.cip4-jdf+xml;pwg-lang-level="1.1" (CIP4 JDF 1.1) pl-prof = "pwg-lang-profile" "=" quoted-string Desc: Language profile or subset (not applicable for 'text/plain'). Human-readable information, suitable for client UI and debug. Not suitable for use by automata. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' Examples: application/pdf;pwg-lang-profile="PDF-X3" (ISO-15930-3:2002) pl-desc = "pwg-lang-desc" "=" quoted-string Desc: Language description. Human-readable information, suitable for client UI and debug. Not suitable for use by automata. Note: This parameter should be _last_, since embedded whitespace may terminate 'cut-and-paste'. See: Section 3.2.5 of Internet Message Formats [RFC 2822] for ABNF definition of 'quoted-string' See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] for definition of 'prtInterpreterDescription' Examples: application/postscript;pwg-lang-desc="Adobe PostScript Level 2" application/vnd.hp-pcl;pwg-lang-desc="HP PCL Level 5e - 25 Oct 2002" The following Interpreter attributes from the Printer MIB are omitted (for the reasons noted below): 'prtInterpreterLangFamily' - language family (i.e., simple MIME type) - see 'document-format' in IPP/1.1 Model [RFC 2911] 'prtInterpreterLangVersion' - language version - ambiguous in actual usage with 'prtInterpreterLangLevel' 'prtInterpreterVersion' - interpreter implementation build version info - not applicable for MIME types 'prtInterpreterDefaultOrientation' - default orientation (portrait or landscape) - see "orientation-requested-default" in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetIn' - default input charset (to avoid charset 'guessing') - see 'charset-configured' in IPP/1.1 Model [RFC 2911] 'prtInterpreterDefaultCharSetOut' - default output charset, - only useful for softcopy output (i.e., 'print-to-file') - not supported in IPP/1.1 Model [RFC 2911] 'prtInterpreterTwoWay' - indicates support for bidirectional print channel - not supported in IPP/1.1 Model [RFC 2911] ------------------------------------------------------------------------ [from "MIME Part Two: Media Types", RFC 2046] > Parameters are modifiers of the media subtype, and as such do not > fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their > defining media type or subtype or they may be optional. MIME > implementations must also ignore any parameters whose names they do > not recognize. ------------------------------------------------------------------------ [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] DIGIT = %x30-39 DQUOTE = %x22 ------------------------------------------------------------------------ [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] parameter = attribute "=" value attribute = token ; Matching of attributes ; is ALWAYS case-insensitive. value = token / quoted-string token = 1* tspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values ------------------------------------------------------------------------ [from "Internet Message Format", RFC 2822] quoted-string = [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS] A quoted-string is treated as a unit. That is, quoted-string is identical to atom, semantically. Since a quoted-string is allowed to contain FWS, folding is permitted. Also note that since quoted-pair is allowed in a quoted-string, the quote and backslash characters may appear in a quoted-string so long as they appear as a quoted-pair. Semantically, neither the optional CFWS outside of the quote characters nor the quote characters themselves are part of the quoted-string; the quoted-string is what is contained between the two quote characters. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS/CFWS that appears within the quoted-string are semantically "invisible" and therefore not part of the quoted-string either. <...> CFWS = *([FWS] comment) (([FWS] comment) / FWS) FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space obs-FWS ctext = NO-WS-CTL / ; Non white space controls %d33-39 / ; The rest of the US-ASCII %d42-91 / ; characters not including "(", %d93-126 ; ")", or "\" ccontent = ctext / quoted-pair / comment comment = "(" *([FWS] ccontent) [FWS] ")" Throughout this standard, where FWS (the folding white space token) appears, it indicates a place where header folding, as discussed in section 2.2.3, may take place. Wherever header folding appears in a message (that is, a header field body containing a CRLF followed by any WSP), header unfolding (removal of the CRLF) is performed before any further lexical analysis is performed on that header field according to this standard. That is to say, any CRLF that appears in FWS is semantically "invisible." A comment is normally used in a structured field body to provide some human readable informational text. Since a comment is allowed to contain FWS, folding is permitted within the comment. Also note that since quoted-pair is allowed in a comment, the parentheses and backslash characters may appear in a comment so long as they appear as a quoted-pair. Semantically, the enclosing parentheses are not part of the comment; the comment is what is contained between the two parentheses. As stated earlier, the "\" in any quoted-pair and the CRLF in any FWS that appears within the comment are semantically "invisible" and therefore not part of the comment either. Runs of FWS, comment or CFWS that occur between lexical tokens in a structured field header are semantically interpreted as a single space character. ------------------------------------------------------------------------ From alan.berkema at hp.com Wed Oct 30 21:11:14 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: Docs for F2F Message-ID: <499DC368E25AD411B3F100902740AD650E6AD3F3@xrose03.rose.hp.com> Hi all, I have been having ftp problems, looks like it is on our end. Firewall? Anyway, the docs I tried to post last Thursday are finally out there, thanks to Harry. psi-spec92.doc == psi-spec92.pdf == psi-spec-latest.pdf Also, have a look at ps/samplecode/92 F2F agenda will be out tomorrow. Thanks, Alan From dhall at hp.com Thu Oct 31 02:03:32 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: Docs for F2F Message-ID: <77261E830267D411BD4D00902740AC250DB4BC66@xvan01.vcd.hp.com> The latest sample code can be found at: ftp://ftp.pwg.org/pub/pwg/ps/samplecode/Code92b/psi.zip Also, we've updated the ps home page: http://www.pwg.org/ps/index.html If anyone has additional suggestions for links / documents we need to publish, let us know.. Dave and Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Wednesday, October 30, 2002 6:11 PM To: 'a PSI pwg.org' Subject: PS> [PSI]: Docs for F2F Hi all, I have been having ftp problems, looks like it is on our end. Firewall? Anyway, the docs I tried to post last Thursday are finally out there, thanks to Harry. psi-spec92.doc == psi-spec92.pdf == psi-spec-latest.pdf Also, have a look at ps/samplecode/92 F2F agenda will be out tomorrow. Thanks, Alan From alan.berkema at hp.com Thu Oct 31 17:42:11 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: F2F Agenda Message-ID: <499DC368E25AD411B3F100902740AD650E6AD3FD@xrose03.rose.hp.com> Hi All, Please have a look at the attached agenda proposal. Any input? Thanks, Alan <> -------------- next part -------------- A non-text attachment was scrubbed... Name: agenda_110602.pdf Type: application/octet-stream Size: 116029 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021031/50b2857e/agenda_110602-0001.obj From alan.berkema at hp.com Thu Oct 31 19:01:59 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:15 2009 Subject: PS> [PSI]: Slides from 10/29 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD400@xrose03.rose.hp.com> Hey All, An enhanced version of the slides I showed at the last telecon are available on the web site under: QueryInterfaceEndPoints Examples later, Alan From imcdonald at sharplabs.com Fri Nov 1 13:48:04 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:15 2009 Subject: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE18@mailsrvnt02.enet.sharplabs.com> Hi Bob, Apologies for my slow reply. I was off the map travelling most of this week. My comments are inline below in your note. Cheers, - Ira McDonald High North Inc -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) [mailto:bobt@hp.com] Sent: Monday, October 28, 2002 7:58 PM To: 'McDonald, Ira'; 'ps@pwg.org'; 'hastings@cp10.es.xerox.com' Cc: SIMPSON,SHELL (HP-Boise,ex1) Subject: RE: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Hi Ira, Tom, all, Some comments/questions: - We understand the rational for the "cut and paste" vs. "structure" objectives, but should PSI have a structure for this? As we'll mention in a bit, there is probably more information we need to capture here, and continual extension of the MIME string doesn't seem to scale well/reliably with too many parameters. For reference (I think we've already shared this), attached is a simple xsd we're using for this. Agreed - the continual extension of the MIME type string does _not_ work very well. - The proposal explicitly states in several places "Human-readable information, suitable for client UI and debug. Not suitable for use by automata". Given that we do need to use content type information for automata, is it assumed that something else (e.g., a "structure" definition) must be defined as well? The proposal _notes_ the current definition of the proposed information in Printer MIB v1 (RFC 1759, March 1995) as "human-readable". But PSI shouldn't solve this problem without a clear IPP binding of whatever the "solution" is. (I can now almost hear myself suggesting an IPP binding based on "document-format-col (1setOf collection)" - yuck! - an awful solution for IPP). A good long-term solution for IPP would be to use the proposed generic Resource object and (just as we've proposed for "media" as a _much_ better solution than the "media-col" attributes) define a Document Format type of Resource. - To be deterministic about what the format actually is (or what formats are supported by a service), we think there are a few additional things necessary: language -- Human language for which the data format is defined. Some word processing applications defined different data formats for different locales--even though the version for the data format remained the same (e.g. early versions of MS Word). Here, we should use IETF RFC 3066 conformant "language-tags". platform -- Operating system for which the data format is defined. Some applications (e.g. MS Word) defined different data formats for different operating systems (e.g. Windows and the Mac) even though the version for the data format remained the same. Here, we're in serious trouble. The (now languishing) IPP device driver installation spec needed a better list of operating systems than the current IANA registry, but creation of such a registry by the PWG is unacceptable to most people. model -- Target device for which the data was created. PDLs (such as Postscript or PCL) can include printer model specific information. (Each printer model has its own specific language specification.) Can you suggest a deterministic, portable way to enumerate printer models that interoperates across software and hardware vendors? Again, a PWG registry is an unacceptable (and unworkable) solution, I believe. container -- Describes embedded content types, such as those embedded within a ZIP file. In the XML domain (not the MIME multipart domain), the best way to describe embedded content types that I know of is the "Manifest" that's an optional part of an XML Digital Signature (RFC 3275, March 2002). Again, needs major work for some kind of IPP binding. - I noticed that pdl-lang-res is missing from the revised proposal. We actually think this is the right answer (i.e., it does not belong here), but wanted to make sure this was intentional and not accidental. Tom Hastings convinced me to remove pwg-lang-res (resolution), because it "opened the barn door to inappropriate parameters". I will note that my own experience at Xerox and Sharp has been that client apps folks do read the Interpreter Table in the Printer MIB to determine the MAXIMUM resolution supported by a given PDL interpreter. No point in sending images at higher resolution, for example. thanks, bt --------------------------------------------------- Bob Taylor Senior Architect IPG Strategic Technology Development Hewlett-Packard Co. mailto:robertt@vcd.hp.com phone: 360.212.2625/T212.2625 fax: 208.730-5111 --------------------------------------------------- > -----Original Message----- > From: McDonald, Ira [mailto:imcdonald@sharplabs.com] > Sent: Friday, October 25, 2002 6:29 PM > To: McDonald, Ira; 'ps@pwg.org'; 'hastings@cp10.es.xerox.com' > Subject: PS> Further Revised PWG std MIME parameters ABNF (25 > Oct 2002) > > > Hi folks, Friday (25 > October 2002) > > [Per my action item from the PWG PSI Telecon on 8 October 2002)] > > Further revised ABNF for three PWG parameters for MIME > document formats. > > Two of these parameters (pwg-lang-level and pwg-lang-desc) > were derived > from the InterpreterTable defined in Printer MIB [RFC 1759]. > The other > parameter (pwg-lang-profile) was suggested by Tom Hastings. > > > Problem Statement: Registered MIME types (for example, used as values > of the 'document-format' Job attribute in IPP/1.1 [RFC 2910, > RFC 2911]) > are imprecise. PWG PSI, CIP4 JDF, FSG PAPI, and FSG Job > Ticket working > groups have all identified a requirement for document format metadata. > > > Rejected Solution: A data structure with the required > metadata - works > well within a given interface - but incompatible with 'cut-and-paste'. > > > Proposed Solution: PWG standard optional MIME parameters - may be > appended to _any_ registered MIME type to add the required metadata - > compatible with 'cut-and-paste' across all applications (because the > parameters are actually _part of_ the same MIME type "word" in the > source text). > > > Tom Hastings and I plan to write a proposal for "IPP: PWG > Standard MIME > Parameters for Document Formats". Watch for an announcement. > > Cheers, > - Ira McDonald, co-editor of Printer MIB v2 > High North Inc > > -------------------------------------------------------------- > ---------- > [PWG Standard MIME Parameters] > > > In the printer industry, a document format MIME type is one of: > > (a) PDL - page description language (e.g., HTML or Adobe PostScript) > (b) JCL - job control language (e.g., HP PJL) > (c) JDL - job definition language (e.g., CIP4 JDF) > (d) text - plaintext, richtext, HTML, SGML, XML, etc. > > Any PWG standard MIME parameter MAY be appended (unordered) to any > document format, for example: > > application/vnd.hp-pcl;pwg-lang-res="400,400,dpi" (HP PCL > 400x400 dpi) > > These PWG parameters are specified in Augmented Backus-Naur > Form (ABNF, > RFC 2234). Every element used in one of these PWG parameter ABNF > productions is defined in an excerpt from ABNF (RFC 2234), > MIME Part One > (RFC 2045), or Internet Message Format (RFC 2822) at the end of this > note. > > Each parameter name begins with a "pwg-" (namespace) prefix, to ensure > that it is safely ignored by existing MIME-enabled software > and systems. > > According to RFC 2045: > > (1) Parameters MUST be ignored when unrecognized; > (2) Parameters MUST be ignored when comparing values of MIME types; > (3) MIME type names MUST be treated as case-insensitive; > (4) MIME parameter names MUST be treated as case-insensitive; > (5) MIME parameter values MUST be treated as case-sensitive. > > > > > > document-format = type "/" subtype *[parameter] *[pwg-parameter] > ; MIME type (plus optional parameters) > > pwg-parameter = ";" pl-level / pl-build / pl- prof / > pl-desc / pl-res > ; PWG standard parameter with a 'quoted-string' value > > Desc: Document format > > See: Section 5.1 in MIME Part One [RFC 2045] > for ABNF definition of 'type', 'subtype', and 'parameter' > See: Section 4.1.9 in IPP/1.1 Model and Semantics [RFC 2911] > for definition of 'mimeMediaType' syntax > > > > > > pl-level = "pwg-lang-level" "=" quoted-string > > Desc: Language level and/or version (not applicable for > 'text/plain'). > Human-readable information, suitable for client UI and debug. > Not suitable for use by automata. > > See: Section 3.2.5 of Internet Message Formats [RFC 2822] > for ABNF definition of 'quoted-string' > See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] > for definition of 'prtInterpreterLangLevel' > > Examples: > > application/postscript;pwg-lang-level="2" (Adobe PostScript Level 2) > > application/vnd.hp-pcl;pwg-lang-level="5e" (HP PCL 5e) > > application/vnd.cip4-jdf+xml;pwg-lang-level="1.1" (CIP4 JDF 1.1) > > > > > > pl-prof = "pwg-lang-profile" "=" quoted-string > > Desc: Language profile or subset (not applicable for 'text/plain'). > Human-readable information, suitable for client UI and debug. > Not suitable for use by automata. > > See: Section 3.2.5 of Internet Message Formats [RFC 2822] > for ABNF definition of 'quoted-string' > > Examples: > > application/pdf;pwg-lang-profile="PDF-X3" (ISO-15930-3:2002) > > > > > pl-desc = "pwg-lang-desc" "=" quoted-string > > Desc: Language description. > Human-readable information, suitable for client UI and debug. > Not suitable for use by automata. > > Note: This parameter should be _last_, since embedded whitespace may > terminate 'cut-and-paste'. > > See: Section 3.2.5 of Internet Message Formats [RFC 2822] > for ABNF definition of 'quoted-string' > See: Section 19 'The Interpreter Group' in Printer MIB [RFC 1759] > for definition of 'prtInterpreterDescription' > > Examples: > > application/postscript;pwg-lang-desc="Adobe PostScript Level 2" > > application/vnd.hp-pcl;pwg-lang-desc="HP PCL Level 5e - 25 Oct 2002" > > > > > The following Interpreter attributes from the Printer MIB are omitted > (for the reasons noted below): > > 'prtInterpreterLangFamily' > - language family (i.e., simple MIME type) > - see 'document-format' in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterLangVersion' > - language version > - ambiguous in actual usage with 'prtInterpreterLangLevel' > > 'prtInterpreterVersion' > - interpreter implementation build version info > - not applicable for MIME types > > 'prtInterpreterDefaultOrientation' > - default orientation (portrait or landscape) > - see "orientation-requested-default" in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterDefaultCharSetIn' > - default input charset (to avoid charset 'guessing') > - see 'charset-configured' in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterDefaultCharSetOut' > - default output charset, > - only useful for softcopy output (i.e., 'print-to-file') > - not supported in IPP/1.1 Model [RFC 2911] > > 'prtInterpreterTwoWay' > - indicates support for bidirectional print channel > - not supported in IPP/1.1 Model [RFC 2911] > > > -------------------------------------------------------------- > ---------- > [from "MIME Part Two: Media Types", RFC 2046] > > > Parameters are modifiers of the media subtype, and as such do not > > fundamentally affect the nature of the content. The set of > meaningful parameters depends on the media type and subtype. Most > parameters are associated with a single specific subtype. > However, a > given top-level media type may define parameters which are > applicable > to any subtype of that type. Parameters may be required by their > > defining media type or subtype or they may be optional. MIME > > implementations must also ignore any parameters whose names they do > > not recognize. > > > -------------------------------------------------------------- > ---------- > [from "Augmented BNF for Syntax Specifications (ANBF)", RFC 2234] > > DIGIT = %x30-39 > > DQUOTE = %x22 > > > -------------------------------------------------------------- > ---------- > [from "MIME Part One: Format of Internet Message Bodies", RFC 2045] > > parameter = attribute "=" value > > attribute = token > ; Matching of attributes > ; is ALWAYS case-insensitive. > > value = token / quoted-string > > token = 1* or tspecials> > > tspecials = "(" / ")" / "<" / ">" / "@" / > "," / ";" / ":" / "\" / <"> > "/" / "[" / "]" / "?" / "=" > ; Must be in quoted-string, > ; to use within parameter values > > > -------------------------------------------------------------- > ---------- > [from "Internet Message Format", RFC 2822] > > quoted-string = [CFWS] > DQUOTE *([FWS] qcontent) [FWS] DQUOTE > [CFWS] > > A quoted-string is treated as a unit. That is, quoted-string is > identical to atom, semantically. Since a quoted-string is > allowed to > contain FWS, folding is permitted. Also note that since > quoted-pair > is allowed in a quoted-string, the quote and backslash > characters may > appear in a quoted-string so long as they appear as a quoted-pair. > > Semantically, neither the optional CFWS outside of the quote > characters nor the quote characters themselves are part of the > quoted-string; the quoted-string is what is contained > between the two > quote characters. As stated earlier, the "\" in any > quoted-pair and > the CRLF in any FWS/CFWS that appears within the quoted-string are > semantically "invisible" and therefore not part of the > quoted-string > either. > > <...> > > CFWS = *([FWS] comment) (([FWS] comment) / FWS) > > FWS = ([*WSP CRLF] 1*WSP) / ; Folding white space > obs-FWS > > ctext = NO-WS-CTL / ; Non white space controls > > %d33-39 / ; The rest of the US-ASCII > %d42-91 / ; characters not > including "(", > %d93-126 ; ")", or "\" > > ccontent = ctext / quoted-pair / comment > > comment = "(" *([FWS] ccontent) [FWS] ")" > > Throughout this standard, where FWS (the folding white space token) > appears, it indicates a place where header folding, as discussed in > section 2.2.3, may take place. Wherever header folding > appears in a > message (that is, a header field body containing a CRLF followed by > any WSP), header unfolding (removal of the CRLF) is > performed before > any further lexical analysis is performed on that header field > according to this standard. That is to say, any CRLF that > appears in > FWS is semantically "invisible." > > A comment is normally used in a structured field body to > provide some > human readable informational text. Since a comment is allowed to > contain FWS, folding is permitted within the comment. > Also note that > since quoted-pair is allowed in a comment, the parentheses and > backslash characters may appear in a comment so long as they appear > as a quoted-pair. Semantically, the enclosing parentheses are not > part of the comment; the comment is what is contained > between the two > parentheses. As stated earlier, the "\" in any quoted-pair and the > CRLF in any FWS that appears within the comment are semantically > "invisible" and therefore not part of the comment either. > > Runs of FWS, comment or CFWS that occur between lexical tokens in a > structured field header are semantically interpreted as a single > space character. > > -------------------------------------------------------------- > ---------- > From imcdonald at sharplabs.com Mon Nov 4 13:58:35 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE1D@mailsrvnt02.enet.sharplabs.com> Hi Bob, See some replies inline below. Thanks very much for thinking hard about these issues. High level comment - I'm ready to throw in the towel and declare that for machine-readable and machine-actionable needs the addition of parameters to MIME types is a non-solution. So I think we're back to a structure/object for PSI, SM, IPP, etc. Cheers, - Ira McDonald High North Inc -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) [mailto:bobt@hp.com] Sent: Monday, November 04, 2002 1:19 AM To: McDonald, Ira; 'ps@pwg.org'; 'hastings@cp10.es.xerox.com' Cc: SIMPSON,SHELL (HP-Boise,ex1) Subject: RE: PS> Further Revised PWG std MIME parameters ABNF (25 Oct 2002 ) Hi Ira, See a couple of specific comments below - with large chunks trimmed since I agreed and wanted to make it more readable. bt > -----Original Message----- > From: McDonald, Ira [mailto:imcdonald@sharplabs.com] > > - The proposal explicitly states in several places "Human-readable > information, > suitable for client UI and debug. Not suitable for use by automata". > Given > that we do need to use content type information for automata, is it > assumed > that something else (e.g., a "structure" definition) must > be defined as > well? > > > The proposal _notes_ the current definition of the proposed > information > in Printer MIB v1 (RFC 1759, March 1995) as "human-readable". > > But PSI shouldn't solve this problem without a clear IPP binding of > whatever the "solution" is. > > (I can now almost hear myself suggesting an IPP binding based on > "document-format-col (1setOf collection)" - yuck! - an awful > solution for IPP). > > A good long-term solution for IPP would be to use the > proposed generic > Resource object and (just as we've proposed for "media" as a _much_ > better solution than the "media-col" attributes) define a > Document Format > type of Resource. > Agreed - but our (HP) interest is primarily in PSI & SM, where we can use the structural flexibility of XML. I don't have a problem with defining an IPP structure for this, but we need to define something quickly for PSI and SM, so I'd advocate maybe doing these first on this one. I agree that we need some solution very quickly for PSI and SMI. But I started on this problem because it was identified for FSG PAPI and FSG Job Ticket (both of which HP is certainly interested in, too). I'm OK with pursuing an XML structure solution for PSI and SM first. But I'd like to aggressively work on how to pass this in either IPP Printer object attributes or IPP (new Resource) object attributes, so that Free Software Group Open Printing isn't at a disadvantage. > > model -- Target device for which the data was created. > PDLs (such as > Postscript or PCL) can include printer model specific > information. > (Each > printer model has its own specific language specification.) > > > Can you suggest a deterministic, portable way to enumerate > printer models > that interoperates across software and hardware vendors? Again, a PWG > registry is an unacceptable (and unworkable) solution, I believe. > Could we just spec that standard IEEE1284 DeviceIDs be used? I believe these are already deterministic, and also can declare "compatible" models to provide hints on what other models may understand a datastream. Yes, IEEE1284 DeviceID is probably a good solution for device model. And it's a stable registry that we (PWG) don't have to maintain. From imcdonald at sharplabs.com Mon Nov 4 14:03:40 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> FW: DHCP Option for SNMP Notifications Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE1E@mailsrvnt02.enet.sharplabs.com> Hi folks, Mark Bakke (Cisco) has been doing some good work to define a new DHCP boot option that tells a device where to send SNMP traps (i.e., addresses of SNMP Notification Receivers, network management stations). Definitely applicable for printer devices. Cheers, - Ira McDonald High North Inc PS - Mark Bakke co-wrote the SLP MIB with me last year. -----Original Message----- From: Mark Bakke [mailto:mbakke@cisco.com] Sent: Monday, November 04, 2002 10:17 AM To: dhcwg@ietf.org; snmpv3@lists.tislabs.com; mibs@ops.ietf.org Subject: DHCP Option for SNMP Notifications Hi- I've submitted a new DHCP Option for SNMP Notifications draft, after attempting to incorporate the feedback I received on the first one. Until it pops out of the I-D queue, it's available at: ftp://ftpeng.cisco.com/mbakke/ips/dhcp/draft-bakke-dhc-snmp-trap-01.txt Thanks to everyone who contributed and helped me get the SNMP security stuff figured out. I just realized that I forgot to update some of the acknowledgements; Randy Presuhn and David Perkins also helped with this. I also need to spend more time on the references; I realized that these sections are still not up-to-date. Comments? Thanks, -- Mark A. Bakke Cisco Systems mbakke@cisco.com 763.398.1054 From imcdonald at sharplabs.com Wed Nov 6 17:57:57 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> RE: Line length of ornamented MIME type names Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE22@mailsrvnt02.enet.sharplabs.com> Hi Harry, As of my note yesterday to Bob Taylor (HP), I've _abandoned_ my idea for the PWG standard MIME parameters. A few Printer MIB-derived text parameters are feasible (although line length may well become a problem in some cut-and-paste interfaces). But _none_ of the interoperable machine-readable parameters that HP and others have asked for are practical. I believe we should leave unchanged the simple (unornamented) MIME types currently deployed in IPP/1.x implementations. For the PWG SM and PWG PSI interfaces, we should define an XML structured element (such as the suggested "document-type") with as many new details as we need. For the IPP binding, we need to figure out the best solution. I vastly prefer an IPP Resource-based solution, but we _could_ kludge these in with something like "document-type-col" (a collection). Adding a new ordered IPP Printer attribute that is directly parallel to the "document-format-supported" is possible, but a TERRIBLE idea. Cheers, - Ira McDonald High North Inc PS - I copied PSI and IPP lists on this reply to make sure others see my answer to your question promptly. -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Wednesday, November 06, 2002 12:37 PM To: imcdonald@sharplabs.com Subject: In the MIME type definitions standard where you are embellishing... for better description of document types... is there any thought given to resulting length and how this works (or not) with various protocols (ex. SNMP, SMTP, etc.). Question came up at f2f today. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- From alan.berkema at hp.com Thu Nov 7 18:21:21 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: Call for Intellectual Property Message-ID: <499DC368E25AD411B3F100902740AD65149EF264@xrose03.rose.hp.com> > This is a call for Patents that are relevant to the IEEE ISTO PWG PSI > specification. > I'm not sure if the ISTO has their own procedures. To me it would seem > safe to use > the policy and procedures of the IEEE since the ISTO is an affiliate. > The IEEE call, is for essential Patents, though, it may not always be > clear what is > essential. > > If you believe you have IP in the PSI space you are encouraged to file an > LOA, > see below. > > If you know of a company that has IP in this space, that does participate > in the > working group, please let me know and I will send them the appropriate > letter asking > them to file an LOA. > > Also, if there is a more appropriate procedure, please let me know. > > Thanks, > Alan > > -------------------------------------------------------------------------- > --------------------------------------- > From: don@lexmark.com > Sent: Tuesday, December 18, 2001 5:46 AM > To: stds-msc@majordomo.ieee.org > Subject: PatCom Guide and LoA Form - now available > > Attached is a note with the latest information about Patents and the IEEE. > Working group chairs should read, understand and apply the PatCom Guide. > > ********************************************** > * Don Wright don@lexmark.com * > * * > * Chair, IEEE MSC * > * Member, IEEE SA Board of Governors * > * Member, IEEE-ISTO Board of Directors * > * * > * Director, Alliances & Standards * > * Lexmark International * > * 740 New Circle Rd * > * Lexington, Ky 40550 * > * 859-825-4808 (phone) 603-963-8352 (fax) * > ********************************************** > > ---------------------- Forwarded by Don Wright/Lex/Lexmark on 12/18/2001 > 08:44 > AM --------------------------- > > d.ringle%ieee.org@interlock.lexmark.com on 12/17/2001 02:38:49 PM > > To: std-liaison-reps@ieee.org > cc: (bcc: Don Wright/Lex/Lexmark) > Subject: PatCom Guide and LoA Form - now available > > All, > > There are some new Patent Committee documents available for your use. > > 1. Patent Letter of Assurance (LoA) Form > > This form can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link on the right-hand side for Entire Package > (http://standards.ieee.org/board/pat/july_2001.zip). In the package, > there > is an LoA form. > > This LoA form is the preferred format for letters of assurance. All > responses received on the Form can be easily reviewed (and accepted) by > PatCom. As of 1 January 2002, it is required that this be the only form > sent to potential patent holders when seeking a letter of assurance. > > {If the patent holder does not complete the form and, instead, sends in a > free-form letter, PatCom will take appropriate actions.} > > 2. PatCom Guide - "Understanding Patent Issues During IEEE Standards > Development" > > This guide can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link for 'Understanding Patent Issues During IEEE Standards > Development' (http://standards.ieee.org/board/pat/guide.html). > > > If you have any questions, let me know. > > Regards, > ************************************************************************** > ******** > > > David L. Ringle > PatCom Administrator > IEEE Standards Activities Dept. > > 445 Hoes Lane PH: +1 732 562 3806 > PO Box 1331 FX: +1 732 562 > 1571 > Piscataway, NJ 08855-1331 d.ringle@ieee.org > ************************************************************************** > ******** From alan.berkema at hp.com Tue Nov 12 12:08:28 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> RE: No meeting? Message-ID: <499DC368E25AD411B3F100902740AD650E6AD422@xrose03.rose.hp.com> Sorry all, I snoozed, took Monday off and got out of sync. Think we are OK since we just got back from the F2F and need some time to re-group anyway. We'll do it next week, I'll send out the meeting info later. Alan -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, November 12, 2002 8:13 AM To: 'Harry Lewis'; alan_berkema@hp.com; HALL,DAVID (HP-Vancouver,ex1) Subject: RE: No meeting? Not that I can tell! I haven't heard from Alan.. D -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Tuesday, November 12, 2002 8:05 AM To: alan_berkema@hp.com; dhall@hp.com Subject: No meeting? I wasn't able to get the webx or phone nums that I have for the call to work this morning. I'm guessing it's too soon after the f2f and we decided not to have a call. Looking forward to updated docs. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20021112/20a10e73/attachment-0001.html From dhall at hp.com Tue Nov 12 12:33:01 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> New specification document available Message-ID: <77261E830267D411BD4D00902740AC250DB4BEE5@xvan01.vcd.hp.com> psi-spec93b.doc = psi-spec-latest.pdf - latest clean version Thanks, Alan and Dave From alan.berkema at hp.com Thu Nov 14 11:32:53 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 11/19/02 - New Number Message-ID: <499DC368E25AD411B3F100902740AD650E6AD444@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday November 19 (USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Look at the WSDL with the strong typing mechanism discussed at the F2F 2) Discovery - What do we need to enable each protocol Assign action owners WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 11/19/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Thu Nov 14 16:31:59 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> Updated Number [PSI]: next call 11/19/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD455@xrose03.rose.hp.com> The tool missed my first date: Here is the number for the 19th 650-690-9362(T348-9362) ID 55605 -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, November 14, 2002 8:33 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: next call 11/19/02 - New Number Teleconference details: Date: Tuesdays, Next: Tuesday November 19 (USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Look at the WSDL with the strong typing mechanism discussed at the F2F 2) Discovery - What do we need to enable each protocol Assign action owners WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 11/19/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Mon Nov 18 19:13:17 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: F2F Minutes 11/06/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD47B@xrose03.rose.hp.com> proposed minutes attached, Thanks to Jerry for capturing the meeting, Alan <> -------------- next part -------------- A non-text attachment was scrubbed... Name: psi_minutes_110602.pdf Type: application/octet-stream Size: 96747 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021118/dc396379/psi_minutes_110602-0001.obj From alan.berkema at hp.com Wed Nov 20 10:19:23 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 12/03/02 - NO Call 11/26 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD489@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday November 19 (USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Look at the WSDL with the strong typing mechanism discussed at the F2F 2) Discovery - What do we need to enable each protocol Assign action owners WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Scheduled Time: 11/19/2002 at 8:00AM (GMT -07:00) Pacific Time, USA & Canada (DayLight Time). Meeting Number: 28877789 Password: newpsi From dhall at hp.com Wed Nov 27 09:35:00 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> Updated Documents Message-ID: <77261E830267D411BD4D00902740AC250DB4C051@xvan01.vcd.hp.com> Hey All! We've updated the specification document to 94a: ftp://ftp.pwg.org/pub/pwg/ps/psi-spec94a.doc This version of the document has made a stab at getting the mandatory / optional definitions into each of the methods comments section. For the AddDocumentByReference, this was modified to return an array of DocumentURI's, as a reference can refer to potentially more than one document. (For example, an email reference...) Also, we have successfully updated the sample code to utilize the strongly typed interfaces, and have made some soap calls with the new interfaces as well! The latest code can is linked from the web page. We have a couple of road blocks to overcome however - the current version of the Axis toolkit has problems with the following constructs within the semantic model: 1) Union - the way we are utilizing union to merge KWV and a pattern cause Axis to generate no code for the element. 2) NMTOKEN for enumerations. Axis also doesn't appear to support this. To address these two problems for the current sample code, I've taken a snapshot of the PWG semantic model schemas, removed the Union declarations (by simply defining the types directly as KWV), and changed the NMTOKEN enumerations to string enumerations. I don't believe that we should change NMTOKEN's to string in the semantic model schemas, rather we should add support for NMTOKEN enumerations into the Axis toolkit. However, the union of KWV and string extension definition has me a bit concerned that this is probably way beyond current toolkits capabilities. Mainly because this would require that in the entity objects that the toolkits generate, they would need to perform some sort of type checking when a client tried to set the member variables to see if any restrictions were violated. Perhaps we could do the following: Declare the elements that need to either be a keyword or a string extension to have two sub elements - one defined by the KWV, and the other being a string... Any thoughts / suggestions? Have a great Thanksgiving! Dave Hall HP From imcdonald at sharplabs.com Fri Nov 29 15:09:16 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> SLP/LDAP for PSI Discovery - details and examples Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE2C@mailsrvnt02.enet.sharplabs.com> Hi folks, Friday (29 November 2002) Per my action item at last week's PSI Telecon (19 November 2002), below are some examples and details for PSI discovery via SLPv2 (RFC 2608) and LDAPv3 (RFC 2251). Note that the definition of standard PSI URL scheme names (see below) will allow the use of SLPv2 and LDAPv3 for PSI discovery without ANY additions to the existing standard printer schemas. Cheers, - Ira McDonald, co-editor of SLPv2 and LDAPv3 Printer Schemas High North Inc imcdonald@sharplabs.com ------------------------------------------------------------------------ PSI URL Schemes --------------- Since PSI Print Services and PSI Target Devices MUST use the (future) IANA-registered PSI port and MUST NOT use "http:" port 80 for their WSDL/SOAP interface, it follows that we need to define standard URL scheme names for them. URL scheme registration in the IETF tree (without embedded hyphen '-') is EXTREMELY slow (currently several YEARS before acceptance and RFC publication). Therefore, I suggest we do NOT register the following two PSI URL scheme names, but instead use an unregistered alternative tree (with a "pwg-" prefix). Conformant to "Registration Procedures for URL Scheme Names" (RFC 2717): pwg-psips: - PSI Print Service pwg-psitd: - PSI Target Device PSI URLs should be converted to underlying HTTP URLs by substitution of the "http:" scheme name and insertion of the PSI standard port. Printer Schema Locations ------------------------ The IANA-registered SLPv2 Printer Template v2.0 is in the directory: ftp://ftp.iana.org/assignments/svrloc-templates/ in the file: printer.2.0.en (8 March 2000) The current draft of LDAPv3 Printer Schema v1.0 is in the directory: ftp://ftp.ietf.org/internet-drafts/ in the file: draft-fleming-ldap-printer-schema-02.txt (30 June 2002) Note: The content and OIDs of the standard LDAPv3 Printer Schema v1.0 have been stable for three years. IBM and other vendors have been shipping implementations for over two years. Although not yet published as an RFC, the LDAPv3 Printer Schema v1.0 is entirely safe to deploy (the OIDs are assigned in the IBM namespace, NOT in the IETF namespace). If the LDAPv3 Printer Schema v1.0 continues to be delayed by the IETF, we plan to adopt and publish it as an IEEE/ISTO PWG standard in early calendar 2003. SLPv2 Discovery --------------- For PSI discovery, we can use the IANA-registered standard SLPv2 Printer Template v2.0 (without ANY extensions), by specifying SLPv2 service URLs of the form: service:printer:pwg-psips://hostport[abs_path] service:printer:pwg-psitd://hostport[abs_path] hostport = host [ ":" port ] host = IPv6reference / IPv4address / hostname port = *DIGIT abs_path = "/" path_segments SLPv2 Service Request --------------------- To locate available PSI Print Service(s), a PSI Client, acting in the role of an SLPv2 User Agent (UA), should use an SLPv2 Service Request (see section 8.1 of SLPv2, RFC 2608) of the form: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Service Location header (function = SrvRqst = 1) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of predicate string | Service Request \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | length of string | String \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The should be "service:printer:pwg-psips", to locate available PSI Print Service providers. Note that the final ":" MUST NOT be included in the . The (without explicit configuration) should be "DEFAULT" (the standard SLPv2 scope). Note that SLPv2 scope names are always case-sensitive, so "DEFAULT" must be in uppercase. The (not needed) MAY specify any LDAPv3 search filter (see "The String Representation of LDAP Search Filters", RFC 2254). To find a PSI Print Service provider that has SLPv2 registered with a different base URL (for example a "service:printer:ipp" URL), use a that specifies a substring search for "pwg-psips" in the "printer-xri-supported" attribute. For example an LDAPv3 filter of: "printer-xri-supported=*pwg-psips*" SLPv2 Service Reply ------------------- When operating in a zero config environment (without infrastructure), an available PSI Print Service(s), acting in the role of an SLPv2 Service Agent (UA), will DIRECTLY reply to the PSI Client. When operating in a managed environment (with infrastructure), an SLPv2 Directory Agent (DA) will reply to the PSI Client (on behalf of the registered appropriate SLPv2 SAs). The presence of the network infrastructure is completely transparent to the PSI Client - SLPv2 discovery uses identical SLPv2 requests and responses in either case. The SLPv2 Service Reply will be of the form: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Service Location header (function = SrvRply = 2) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Error Code | URL Entry count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Each returned PSI Print Service URL MUST specify either an IPv4/IPv6 address (directly usable) or a hostname (which must be resolved by DNS or mDNS lookup). SLPv2 DA Discovery ------------------ The DHCP option (decimal) 78 may be used, to find an SLPv2 Directory Agent (DA), per "DHCP Options for Service Location Protocol" (RFC 2610). LDAPv3 Discovery ---------------- For PSI discovery, we can use the standard LDAPv3 Printer Schema v1.0 (without ANY extensions), by searching for the LDAPv3 object class "printerService" (a base class) or "printerServiceAuxClass" (may be attached, for example, to a DMTF CIM printer object class - same content as "printerService") to find printer URLs (values of the "printer-uri" attribute) of the form: pwg-psips://hostport[abs_path] pwg-psitd://hostport[abs_path] Also, an LDAPv3 search filter may be used (as with SLPv2) to find the substring "pwg-psips" or "pwg-psitd" in the "printer-xri-supported" attribute. LDAPv3 DSA Discovery -------------------- The DHCP option (decimal) 95 may be used, to find an LDAPv3 Directory Service Agent (DSA). See the definition in the directory: ftp://ftp.iana.org/assignments/bootp-dhcp-extensions/ DNS Server Discovery -------------------- The DHCP option (decimal) 6 may be used to find a DNS server address. See "DHCP Options and BOOTP Vendor Extensions" (RFC 2132). The DHCP option (decimal) 117 may also be used to find a DNS server. See "The Name Service Search Option for DHCP" (RFC 2937). From imcdonald at sharplabs.com Fri Nov 29 16:05:11 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> [PDF posted] Updated Documents Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE2E@mailsrvnt02.enet.sharplabs.com> Hi Dave, I distilled the MS Word source and just posted: ftp://ftp.pwg.org/pub/pwg/ps/psi-spec94a.pdf and (for the Web page link) ftp://ftp.pwg.org/pub/pwg/ps/psi-spec-latest.pdf Cheers, - Ira McDonald High North Inc -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Wednesday, November 27, 2002 8:35 AM To: 'ps@pwg.org' Subject: PS> Updated Documents Hey All! We've updated the specification document to 94a: ftp://ftp.pwg.org/pub/pwg/ps/psi-spec94a.doc This version of the document has made a stab at getting the mandatory / optional definitions into each of the methods comments section. For the AddDocumentByReference, this was modified to return an array of DocumentURI's, as a reference can refer to potentially more than one document. (For example, an email reference...) Also, we have successfully updated the sample code to utilize the strongly typed interfaces, and have made some soap calls with the new interfaces as well! The latest code can is linked from the web page. We have a couple of road blocks to overcome however - the current version of the Axis toolkit has problems with the following constructs within the semantic model: 1) Union - the way we are utilizing union to merge KWV and a pattern cause Axis to generate no code for the element. 2) NMTOKEN for enumerations. Axis also doesn't appear to support this. To address these two problems for the current sample code, I've taken a snapshot of the PWG semantic model schemas, removed the Union declarations (by simply defining the types directly as KWV), and changed the NMTOKEN enumerations to string enumerations. I don't believe that we should change NMTOKEN's to string in the semantic model schemas, rather we should add support for NMTOKEN enumerations into the Axis toolkit. However, the union of KWV and string extension definition has me a bit concerned that this is probably way beyond current toolkits capabilities. Mainly because this would require that in the entity objects that the toolkits generate, they would need to perform some sort of type checking when a client tried to set the member variables to see if any restrictions were violated. Perhaps we could do the following: Declare the elements that need to either be a keyword or a string extension to have two sub elements - one defined by the KWV, and the other being a string... Any thoughts / suggestions? Have a great Thanksgiving! Dave Hall HP From imcdonald at sharplabs.com Tue Dec 3 15:39:23 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> Multiple filenames per Job/Document Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE39@mailsrvnt02.enet.sharplabs.com> Hi folks, Tuesday (3 December 2002) At today's PSI Telecon, we proposed that both simple Jobs (in the Free Software Group's PAPI/1.0) and Documents (in future PWG Semantic Model and FSG Job Ticket API/2.0) should support an attribute that's a list of filenames that "comprise the _single_ document (when concatenated), for purposes of page exceptions". Note that PAPI says the printer should do page breaks and separator sheets between the files. That's not faithful to the model we agreed upon in FSG Job Ticket API telecons: the running input text is simply contatenated and subsequently repaginated in the output document format (input filenames could have MS Word, PostScript, PDF, etc. extensions). FSG PAPI reference implementation is CUPS over IPP/1.1 with extensions. This semantic ambiguity should be resolved or the CUPS implementation of the (future) IPP Job creation operation attribute "file-names" may become broken. Pete and Tom: In FSG PAPI v0.9, this attribute is called "file_names", which would become "file-names" for Job/Doc in IPP/1.x and "jobFileNames" and "documentFileNames" in PWG Semantic Model, right? Or just always (on Job or Document object) "document-file-names" in PWG SM and IPP? Note that "document-file-names" is then orthogonal to the single-valued "document-format" (because given document formats are _implied_ by the filename extensions by universal convention). Opinions? Cheers, - Ira McDonald High North Inc ------------------------------------------------------------------------ ftp://ftp.pwg.org/pub/pwg/fsg/spool/papi-v0.9.pdf (18 November 2002) [Extracted from section 7.2 "papiJobSubmitByReference" of PAPI/0.9, the description of the input operation parameter "file_names"] file_names NULL terminated list of pointers to names of files to print. If more than one file is specified, the files will be treated by the print system as separate "documents" for things like page breaks and separator sheets, but they will be scheduled and printed together as one job and the specified attributes will apply to all the files. These file names may contain absolute path names, relative path names or URIs ([RFC1738], [RFC2396]). The implementation SHOULD NOT copy the referenced data unless (or until) it is no longer feasible to maintain the reference. Feasibility limitations may arise out of security issues, namespace issues, and/or protocol or printer limitations. Implementations MUST support the absolute path, relative path, and "file:" URI scheme. Use of other URI schemes could result in a PAPI_URI_SCHEME error, depending on the implementation. The semantics explained in the preceding paragraphs allows for flexibility in the PAPI implementation. For example: (1) PAPI on top of a local service to maintain the reference for the life of the job, if the local service supports it. (2) PAPI on top of IPP to send a reference when the server can access the referenced data and copy it when it is not accessible to the server. (3) PAPI on top of network printing protocols that don't support references to copy the data on the way out to the remote server. From imcdonald at sharplabs.com Wed Dec 4 15:27:23 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> RE: URI GUID example Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE3E@mailsrvnt02.enet.sharplabs.com> Hi Dave, Take a look at "A UUID URN Namespace": ftp://ftp.ietf.org/internet-drafts/draft-mealling-uuid-urn-00.txt (Note that this registration comes from the ISO JTC1 folks, this is solid). Numerous examples, and implementation details. Cheers, - Ira McDonald High North Inc ------------------------------------------------------------------ [exerpts from "A UUID URN Namespace" draft] Abstract This specification defines a Uniform Resource Name namespace for UUIDs ( (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and if generated according to the one of the mechanisms in this document, is either guaranteed to be different from all other UUIDs/GUIDs generated until 3400 A.D. or extremely likely to be different (depending on the mechanism chosen). UUIDs were originally used in the Network Computing System (NCS) [1] and later in the Open Software Foundation's (OSF) Distributed Computing Environment [2]. This specification is derived from the latter specification with the kind permission of the OSF. The original version of this document was written by Paul Leach and Rich Salz but was unpublished for several years. This is an updated version incorporated as part of the URN registration document. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Namespace Registration Template . . . . . . . . . . . . . . 4 4. Specification . . . . . . . . . . . . . . . . . . . . . . . 7 4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1.1 Variant . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1.2 UUID Layout . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1.3 Version . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.4 Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.5 Clock sequence . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.6 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.7 Nil UUID . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2 Algorithms for creating a time-based UUID . . . . . . . . . 12 4.2.1 Basic algorithm . . . . . . . . . . . . . . . . . . . . . . 12 4.2.2 Reading stable storage . . . . . . . . . . . . . . . . . . . 13 4.2.3 System clock resolution . . . . . . . . . . . . . . . . . . 13 4.2.4 Writing stable storage . . . . . . . . . . . . . . . . . . . 14 4.2.5 Sharing state across processes . . . . . . . . . . . . . . . 14 4.2.6 UUID Generation details . . . . . . . . . . . . . . . . . . 14 4.3 Algorithm for creating a name-based UUID . . . . . . . . . . 15 5. Algorithms for creating a UUID from truly random or pseudo-random numbers . . . . . . . . . . . . . . . . . . . 16 6. Byte order of UUIDs . . . . . . . . . . . . . . . . . . . . 17 7. Node IDs when no IEEE 802 network card is available . . . . 17 8. Obtaining IEEE 802 addresses . . . . . . . . . . . . . . . . 19 9. Community Considerations . . . . . . . . . . . . . . . . . . 19 10. Security Considerations . . . . . . . . . . . . . . . . . . 20 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 Normative References . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21 A. Appendix A - UUID Sample Implementation . . . . . . . . . . 21 B. Appendix B - Sample output of utest . . . . . . . . . . . . 33 C. Appendix C - Some name space IDs . . . . . . . . . . . . . . 33 Full Copyright Statement . . . . . . . . . . . . . . . . . . 35 -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Wednesday, December 04, 2002 10:47 AM To: 'McDonald, Ira' Subject: URI GUID example Hey Ira... We're moving forward with the sample implementation, and are having a hard time figuring out what a String representation of a GUID would be... Do you have a link to, or can you make some examples? Would it look like this:? GUID://myserver.mydomain/{12321-23123-231adfe-321f} Thanks! Dave From alan.berkema at hp.com Thu Dec 5 12:21:49 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 12/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4CB@xrose03.rose.hp.com> Teleconference details: Date: Tuesdays, Next: Tuesday December 10 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From dhall at hp.com Tue Dec 10 10:55:21 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 12/10/02 Message-ID: <77261E830267D411BD4D00902740AC250DB4C155@xvan01.vcd.hp.com> Morning Alan - The meeting number / password is complaining on WebEx this morning... Dave -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, December 05, 2002 9:22 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: next call 12/10/02 Teleconference details: Date: Tuesdays, Next: Tuesday December 10 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From dhall at hp.com Tue Dec 10 11:10:09 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 12/10/02 Message-ID: <77261E830267D411BD4D00902740AC250DB4C156@xvan01.vcd.hp.com> New meeting ID & password 21410551, newpsi2 -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, December 10, 2002 7:55 AM To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org' Subject: RE: PS> [PSI]: next call 12/10/02 Morning Alan - The meeting number / password is complaining on WebEx this morning... Dave -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, December 05, 2002 9:22 AM To: 'a PSI pwg.org' Subject: PS> [PSI]: next call 12/10/02 Teleconference details: Date: Tuesdays, Next: Tuesday December 10 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From dhall at hp.com Tue Dec 10 12:08:51 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> 12/10 Minutes Message-ID: <77261E830267D411BD4D00902740AC250DB4C157@xvan01.vcd.hp.com> PSI Meeting Minutes 1) WSDL with strong typing - Discussed element defined by union - Unioned restrictions should have the same type to make sense for the base element. PSI is OK with the existing semantic model definitions - with the exception of DocumentFormatWKV - since this needs to be a string, other restriction needs to be a string, not NMTOKEN. 2) Discovery update - Ira discussed Mobile Addhock Network - issues a Service Request rather than a Route Request. SLP service types. Nokia is developing the specification. ietf home page www.ietf.org - working groups mana... This would be deployed in smaller ad-hock networks in accesspoints, etc.. Could this be deployed in an enterprise? A big enterprise would run into problems... Mane give a route as well as a URL.. - Last week, discussed the possibility of having a PrintService published during DHCP configuration. 3) Review 0.94a Mandatory/Optional - QueryEndPointsInterface - Client - Mandatory unless administratively pre-configured - QueryInterfaceEndPoint & QueryInterfaceWSDL - Client One is mandatory unless administratively pre-configured - QueryInterfaceWSDL - this method returns a URL that refers to the WSDL that defines what the service ACTUALLY supports, not simply the standard PWG definition. - For example, target devices could return a URL to the WSDL that is hosted by the manufacturer, and not on the printer, or to the WSDL that is configured by the administrator. - ServiceCapabilitiesInterface - GetTargetDeviceElements - Discussion around making a TargetDevice validate the targetDeviceIdentifier, and throw an exception (New exception - InvalidTargetDeviceIdentifier) if not correct. - TargetDeviceIdentifier - Client to TargetDevice - Mandatory - requestedElements - If NULL, returns all elements supported - JobControlInterface Client - Conditionally mandatory - If you want to create a job, must use the interface. CreateJob Method TargetDeviceIdentifier - same as above deliverToTargetDevice - Client to TargetDevice - Mandatory, must be TRUE requestedTargetDeviceDataType - Client to TargetDevice - optional. If provided, validated Pick up on AddDocumentByReference next time. From dhall at hp.com Tue Dec 10 12:39:24 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <77261E830267D411BD4D00902740AC250DB4C159@xvan01.vcd.hp.com> During today's meeting, we discussed the QueryInterfacWSDL method, and came up with the following statement: - For example, target devices could return a URL to the WSDL that is hosted by the manufacturer, and not on the printer, or to the WSDL that is configured by the administrator. I don't think that this will actually work however. The WSDL typically has a service binding within it, and this couldn't be returned generically - The whole point of calling this method was to figure out what URL path to bind to for the interface you are requesting. We could change the meaning of the method to be "retrieve a WSDL that describes the interface" - but the client MUST use QueryInterfaceEndPoint to get the end point to bind to... Thoughts? Dave From dhall at hp.com Tue Dec 10 12:55:12 2002 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <77261E830267D411BD4D00902740AC250DB4C15A@xvan01.vcd.hp.com> That could work - We could even combine the two methods - QueryInterfaceEndPoint and QueryInterfaceWSDL, into a single method QueryInterfaceDefinition - it would return two URL's - One to the EndPoint, the second to the WSDL.. The client must bind to the EndPoint provided, regardless of what the WSDL states. D -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) Sent: Tuesday, December 10, 2002 9:53 AM To: HALL,DAVID (HP-Vancouver,ex1); 'ps@pwg.org' Subject: RE: PS> QueryInterfaceWSDL discussion Yep - I think we forgot the "two halves" of WSDL. Could we modify QueryInterfaceWSDL to pass back both the URL the the WSDL AND the endpoint that the target device binds to that WSDL? bt > -----Original Message----- > From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] > Sent: Tuesday, December 10, 2002 9:39 AM > To: 'ps@pwg.org' > Subject: PS> QueryInterfaceWSDL discussion > > > During today's meeting, we discussed the QueryInterfacWSDL > method, and came > up with the following statement: > > - For example, target devices could return a > URL to the WSDL > that is hosted by the manufacturer, and not on the printer, > or to the WSDL > that is configured by the administrator. > > I don't think that this will actually work however. The WSDL > typically has > a service binding within it, and this couldn't be returned > generically - The > whole point of calling this method was to figure out what URL > path to bind > to for the interface you are requesting. > > > > binding="intf:org.pwg.psi.JobControlInterfaceSoapBinding"> > location="http://127.0.0.1/org.pwg.psi.JobControlInterface"/> > > > > We could change the meaning of the method to be "retrieve a WSDL that > describes the interface" - but the client MUST use > QueryInterfaceEndPoint to > get the end point to bind to... > > Thoughts? > > Dave > From imcdonald at sharplabs.com Tue Dec 10 12:56:28 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE4B@mailsrvnt02.enet.sharplabs.com> Hi David, You said it at the end below: 1) QueryInterfaceWSDL returns "a WSDL that describes the interface" (and NOT a specific WSDL endpoint identifier) 2) QueryInterfaceEndPoint - Client MUST use this to discover the actual WSDL endpoint OK? Cheers, - Ira McDonald High North Inc -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, December 10, 2002 11:39 AM To: 'ps@pwg.org' Subject: PS> QueryInterfaceWSDL discussion During today's meeting, we discussed the QueryInterfacWSDL method, and came up with the following statement: - For example, target devices could return a URL to the WSDL that is hosted by the manufacturer, and not on the printer, or to the WSDL that is configured by the administrator. I don't think that this will actually work however. The WSDL typically has a service binding within it, and this couldn't be returned generically - The whole point of calling this method was to figure out what URL path to bind to for the interface you are requesting. We could change the meaning of the method to be "retrieve a WSDL that describes the interface" - but the client MUST use QueryInterfaceEndPoint to get the end point to bind to... Thoughts? Dave From imcdonald at sharplabs.com Tue Dec 10 12:58:12 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> QueryInterfaceWSDL discussion Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE4C@mailsrvnt02.enet.sharplabs.com> Hi, Good simplification - I agree. Cheers, - Ira McDonald High North Inc -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, December 10, 2002 11:55 AM To: TAYLOR,BOB (HP-Vancouver,ex1); 'ps@pwg.org' Subject: RE: PS> QueryInterfaceWSDL discussion That could work - We could even combine the two methods - QueryInterfaceEndPoint and QueryInterfaceWSDL, into a single method QueryInterfaceDefinition - it would return two URL's - One to the EndPoint, the second to the WSDL.. The client must bind to the EndPoint provided, regardless of what the WSDL states. D -----Original Message----- From: TAYLOR,BOB (HP-Vancouver,ex1) Sent: Tuesday, December 10, 2002 9:53 AM To: HALL,DAVID (HP-Vancouver,ex1); 'ps@pwg.org' Subject: RE: PS> QueryInterfaceWSDL discussion Yep - I think we forgot the "two halves" of WSDL. Could we modify QueryInterfaceWSDL to pass back both the URL the the WSDL AND the endpoint that the target device binds to that WSDL? bt > -----Original Message----- > From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] > Sent: Tuesday, December 10, 2002 9:39 AM > To: 'ps@pwg.org' > Subject: PS> QueryInterfaceWSDL discussion > > > During today's meeting, we discussed the QueryInterfacWSDL > method, and came > up with the following statement: > > - For example, target devices could return a > URL to the WSDL > that is hosted by the manufacturer, and not on the printer, > or to the WSDL > that is configured by the administrator. > > I don't think that this will actually work however. The WSDL > typically has > a service binding within it, and this couldn't be returned > generically - The > whole point of calling this method was to figure out what URL > path to bind > to for the interface you are requesting. > > > > binding="intf:org.pwg.psi.JobControlInterfaceSoapBinding"> > location="http://127.0.0.1/org.pwg.psi.JobControlInterface"/> > > > > We could change the meaning of the method to be "retrieve a WSDL that > describes the interface" - but the client MUST use > QueryInterfaceEndPoint to > get the end point to bind to... > > Thoughts? > > Dave > From alan.berkema at hp.com Sun Dec 15 12:04:41 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: FW: PS> [PSI]: next call 12/10/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4E1@xrose03.rose.hp.com> Hey all, Sorry I missed the last call I got caught up in the BlueTooth unplug fest and developers conference and forgot what day it was. Hope you had the call anyway. Alan ---- Teleconference details: NEXT: Tuesday December 17 (USA) NO CALL: - Tuesday December 24 (USA) NO CALL: - Tuesday December 31 (USA) NEXT: Tuesday January 7 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: TBD? 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Sun Dec 15 12:12:50 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 12/17/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4E3@xrose03.rose.hp.com> Fixed date in subject. -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Sunday, December 15, 2002 9:05 AM To: 'a PSI pwg.org' Subject: FW: PS> [PSI]: next call 12/10/02 Hey all, Sorry I missed the last call I got caught up in the BlueTooth unplug fest and developers conference and forgot what day it was. Hope you had the call anyway. Alan ---- Teleconference details: NEXT: Tuesday December 17 (USA) NO CALL: - Tuesday December 24 (USA) NO CALL: - Tuesday December 31 (USA) NEXT: Tuesday January 7 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: TBD? 1) WSDL with strong typing - update 2) Discovery - update 3) Review 0.94a Mandatory/Optional WebEx info: 1. If this is your first time joining a WebEx meeting, at least 15 minutes before the scheduled time, go to http://hp.webex.com/ and then click on New User to enable your system for web-based meetings. 2. To join the meeting, click this link at the scheduled time. http://hp.webex.com/webex/ 3. Meeting Summary Meeting Name: PSI Meeting Number: 28877789 Password: newpsi From alan.berkema at hp.com Sun Dec 15 12:50:24 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: minutes 12/03/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4E4@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema Gail Songer *Dave Hall *Jerry Thasher Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 12/02/02 Agenda 1) Call for IP New Form attached 2) Discovery per Ira's action results 3) Strong Typed WSDL and tool kits with SM Schemas 4) Spec rev 0.94a mandatory/optional 12/02/02 Minutes: Action: Provide actuall examples of SSDP discovery Owner: Alan Status: Open Action: Provide actuall examples of mDNS-SD discovery Owner: Dave Status: Open Action: Register for mDNS-SD discovery, can we use the same names as SLPv2? Owner: Ira Status: Open Action: Register pwg- as an alternate SLPv2 tree root. Owner: Harry Status: Open Ira walked us through his SLPv2 and LDAPv3 examples. SLPv2 discovery requests are sent to an IANA registered multicast address using UDP/IP. Talked about allowing predicate to filter for PSI while sending discovery request to service:Printer Decided it would be better to always use service:Printer:pwg-psixx since this will make the SLPv2 Reply clear as to exactly what the discovered URL should be. Dave mentioned that DHCP would be a nice way to discovery the Print Service at the same time as other DHCP discovered values. Make this a consideration for future action since it will likely take some time. LDAPv3 may be a two step process? Action: Determine if we can get request attributes directly Owner: Ira Status: Open From alan.berkema at hp.com Tue Dec 17 10:48:53 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: PWG Form Call for Intellectual Property Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4F7@xrose03.rose.hp.com> Attached is the PWG version of the IEEE form. I think the other docs and procedures the PatCom uses still apply. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, November 07, 2002 3:21 PM To: a PSI pwg.org Subject: PS> [PSI]: Call for Intellectual Property > This is a call for Patents that are relevant to the IEEE ISTO PWG PSI > specification. > I'm not sure if the ISTO has their own procedures. To me it would seem > safe to use > the policy and procedures of the IEEE since the ISTO is an affiliate. > The IEEE call, is for essential Patents, though, it may not always be > clear what is > essential. > > If you believe you have IP in the PSI space you are encouraged to file an > LOA, > see below. > > If you know of a company that has IP in this space, that does participate > in the > working group, please let me know and I will send them the appropriate > letter asking > them to file an LOA. > > Also, if there is a more appropriate procedure, please let me know. > > Thanks, > Alan > > -------------------------------------------------------------------------- > --------------------------------------- > From: don@lexmark.com > Sent: Tuesday, December 18, 2001 5:46 AM > To: stds-msc@majordomo.ieee.org > Subject: PatCom Guide and LoA Form - now available > > Attached is a note with the latest information about Patents and the IEEE. > Working group chairs should read, understand and apply the PatCom Guide. > > ********************************************** > * Don Wright don@lexmark.com * > * * > * Chair, IEEE MSC * > * Member, IEEE SA Board of Governors * > * Member, IEEE-ISTO Board of Directors * > * * > * Director, Alliances & Standards * > * Lexmark International * > * 740 New Circle Rd * > * Lexington, Ky 40550 * > * 859-825-4808 (phone) 603-963-8352 (fax) * > ********************************************** > > ---------------------- Forwarded by Don Wright/Lex/Lexmark on 12/18/2001 > 08:44 > AM --------------------------- > > d.ringle%ieee.org@interlock.lexmark.com on 12/17/2001 02:38:49 PM > > To: std-liaison-reps@ieee.org > cc: (bcc: Don Wright/Lex/Lexmark) > Subject: PatCom Guide and LoA Form - now available > > All, > > There are some new Patent Committee documents available for your use. > > 1. Patent Letter of Assurance (LoA) Form > > This form can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link on the right-hand side for Entire Package > (http://standards.ieee.org/board/pat/july_2001.zip). In the package, > there > is an LoA form. > > This LoA form is the preferred format for letters of assurance. All > responses received on the Form can be easily reviewed (and accepted) by > PatCom. As of 1 January 2002, it is required that this be the only form > sent to potential patent holders when seeking a letter of assurance. > > {If the patent holder does not complete the form and, instead, sends in a > free-form letter, PatCom will take appropriate actions.} > > 2. PatCom Guide - "Understanding Patent Issues During IEEE Standards > Development" > > This guide can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link for 'Understanding Patent Issues During IEEE Standards > Development' (http://standards.ieee.org/board/pat/guide.html). > > > If you have any questions, let me know. > > Regards, > ************************************************************************** > ******** > > > David L. Ringle > PatCom Administrator > IEEE Standards Activities Dept. > > 445 Hoes Lane PH: +1 732 562 3806 > PO Box 1331 FX: +1 732 562 > 1571 > Piscataway, NJ 08855-1331 d.ringle@ieee.org > ************************************************************************** > ******** -------------- next part -------------- A non-text attachment was scrubbed... Name: pwg-loa.doc Type: application/msword Size: 28672 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021217/f5c03dc0/pwg-loa-0001.doc From alan.berkema at hp.com Tue Dec 17 10:57:40 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: New webex Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4F9@xrose03.rose.hp.com> > Meeting number 23402009 > passwd newpsi > > http://hp.webex.com > > From don at lexmark.com Tue Dec 17 11:01:22 2002 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: PWG Form Call for Intellectual Property Message-ID: Just to be sure everyone is aware, the completed form should be sent to: Secretariat, Printer Working Group c/o IEEE-ISTO 445 Hoes Lane Piscataway, NJ 08855 USA FAX (+651-318-7292) with a copy to Alan. ********************************************** Don Wright don@lexmark.com Member, IEEE SA Standards Board PatCom Chair, SCC Liaison Member, IEEE-ISTO Board of Directors f.wright@ieee.org / f.wright@computer.org Director, Alliances & Standards Lexmark International 740 New Circle Rd Lexington, Ky 40550 859-825-4808 (phone) 603-963-8352 (fax) ********************************************** "BERKEMA,ALAN C (HP-Roseville,ex1)" @pwg.org on 12/17/2002 10:48:53 AM Sent by: owner-ps@pwg.org To: "a PSI pwg.org" cc: Subject: PS> [PSI]: PWG Form Call for Intellectual Property Attached is the PWG version of the IEEE form. I think the other docs and procedures the PatCom uses still apply. Thanks, Alan -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, November 07, 2002 3:21 PM To: a PSI pwg.org Subject: PS> [PSI]: Call for Intellectual Property > This is a call for Patents that are relevant to the IEEE ISTO PWG PSI > specification. > I'm not sure if the ISTO has their own procedures. To me it would seem > safe to use > the policy and procedures of the IEEE since the ISTO is an affiliate. > The IEEE call, is for essential Patents, though, it may not always be > clear what is > essential. > > If you believe you have IP in the PSI space you are encouraged to file an > LOA, > see below. > > If you know of a company that has IP in this space, that does participate > in the > working group, please let me know and I will send them the appropriate > letter asking > them to file an LOA. > > Also, if there is a more appropriate procedure, please let me know. > > Thanks, > Alan > > -------------------------------------------------------------------------- > --------------------------------------- > From: don@lexmark.com > Sent: Tuesday, December 18, 2001 5:46 AM > To: stds-msc@majordomo.ieee.org > Subject: PatCom Guide and LoA Form - now available > > Attached is a note with the latest information about Patents and the IEEE. > Working group chairs should read, understand and apply the PatCom Guide. > > ********************************************** > * Don Wright don@lexmark.com * > * * > * Chair, IEEE MSC * > * Member, IEEE SA Board of Governors * > * Member, IEEE-ISTO Board of Directors * > * * > * Director, Alliances & Standards * > * Lexmark International * > * 740 New Circle Rd * > * Lexington, Ky 40550 * > * 859-825-4808 (phone) 603-963-8352 (fax) * > ********************************************** > > ---------------------- Forwarded by Don Wright/Lex/Lexmark on 12/18/2001 > 08:44 > AM --------------------------- > > d.ringle%ieee.org@interlock.lexmark.com on 12/17/2001 02:38:49 PM > > To: std-liaison-reps@ieee.org > cc: (bcc: Don Wright/Lex/Lexmark) > Subject: PatCom Guide and LoA Form - now available > > All, > > There are some new Patent Committee documents available for your use. > > 1. Patent Letter of Assurance (LoA) Form > > This form can be found at http://standards.ieee.org/board/pat/index.html. > Click on the link on the right-hand side for Entire Package > (http://standards.ieee.org/board/pat/july_2001.zip). In the package, > there > is an LoA form. > > This LoA form is the preferred format for letters of assurance. All > responses received on the Form can be easily reviewed (and accepted) by > PatCom. As of 1 January 2002, it is required that this be the only form > sent to potential patent holders when seeking a letter of assurance. > > {If the patent holder does not complete the form and, instead, sends in a > free-form letter, PatCom will take appropriate actions.} > > 2. PatCom Guide - "Understanding Patent Issues During IEEE Standards > Development" > > This guide can be found at http://standards.ieee.org/board/pat/index.html . > Click on the link for 'Understanding Patent Issues During IEEE Standards > Development' (http://standards.ieee.org/board/pat/guide.html). > > > If you have any questions, let me know. > > Regards, > ************************************************************************** > ******** > > > David L. Ringle > PatCom Administrator > IEEE Standards Activities Dept. > > 445 Hoes Lane PH: +1 732 562 3806 > PO Box 1331 FX: +1 732 562 > 1571 > Piscataway, NJ 08855-1331 d.ringle@ieee.org > ************************************************************************** > ******** (See attached file: pwg-loa.doc) -------------- next part -------------- A non-text attachment was scrubbed... Name: pwg-loa.doc Type: application/msword Size: 28672 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021217/3bfeef48/pwg-loa-0001.doc From alan.berkema at hp.com Wed Dec 18 11:59:15 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: next call 01/07/03 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD50B@xrose03.rose.hp.com> Teleconference details: NEXT: Tuesday January 7 2003 (USA) NO CALL: - Tuesday December 24 (USA) NO CALL: - Tuesday December 31 (USA) NEXT: Tuesday January 14 2003 USA) Time: 8 AM (US PST) Number: 404-774-4112(T774-4112) ID: 55605 Agenda: 1) Discovery - Finalize: SLPv2 and LDAPv3 examples for spec, SSDP examples for spec. 2) Look at mDNS-SD examples 3) Spec review topics WebEx info: ------------------------- 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: https://hp.webex.com/join/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting Number: 21643883 Meeting Password: newpsi Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Wed Dec 18 18:13:45 2002 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:16 2009 Subject: PS> [PSI]: minutes 12/17/02 Message-ID: <499DC368E25AD411B3F100902740AD650E6AD513@xrose03.rose.hp.com> PSI Working Group: *Alan Berkema *Dave Hall Gail Songer *Jerry Thasher *Harry Lewis *Ted Tronson Peter Mierau *Peter Zehler Paul Tykodi *Bob Taylor Don Levinstone Lee Farrell Don Wright Kirk Ocke *Ira Mcdonald Amir Shahindoust * = attendance 12/17/02 Agenda 1) New LOA for Call for IP sent to reflector 2) SSDP Example walk through 3) QueryInterface discussion 4) Few spec changes 5) Spec rev 0.94a mandatory/optional - left off at addDocumentByReference 12/17/02 Minutes: 0) Rev 0.94x (candidate for 0.95) will be delivered on the morning of January 13 2003. This gives us a week to review before the start of the week of PWG F2F meetings. Planning page turner review at PSI F2F January 24 2003. 1) Done. 2) Walked through SSDP example attached. We talked ourselves into the need for a psi:rootdevice, I believe for some type of compatibility. A day later I am have trouble seeing why this makes sense. Still seems like things would work fine with out it? Can anyone describe the reasons for why we added it? 3) I think we adopted the following: QueryInterfaceEndPoint and QueryInterfaceWSDL, into a single method QueryInterfaceDefinition - it would return two URL's - One to the EndPoint, the second to the WSDL.. The client must bind to the EndPoint provided, regardless of what the WSDL states. 4) Will come out as part of the next rev. 5) Did not get this far. -------------- next part -------------- A non-text attachment was scrubbed... Name: psi SSDP.pdf Type: application/octet-stream Size: 91873 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20021218/c73e46a8/psiSSDP-0001.obj From imcdonald at sharplabs.com Thu Dec 19 14:34:51 2002 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:16 2009 Subject: PS> RFC 3391 - The MIME Application/Vnd.pwg-multiplexed Content-Type Message-ID: <116DB56CD7DED511BC7800508B2CA53735CE5C@mailsrvnt02.enet.sharplabs.com> Hi folks, Finally, Bob Herriot's work has been published. Relevant to XHTML-Print, PWG PSIv1, FSG PAPIv1, UPnPv2, and others. Please note the "IESG Note" at the beginning (see below). Cheers, - Ira McDonald High North Inc ----------------------------------------------------------------------- IESG Note The IESG believes use of this media type is only appropriate in situations where the producer is fully aware of the capabilities and limitations of the consumer. In particular, this mechanism is very dependent on the producer knowing when the consumer will need a particular component of a multipart object. But consumers potentially work in many different ways and different consumers may need different things at different times. This mechanism provides no means for a producer to determine the needs of a particular consumer and how they are to be accommodated. Alternative mechanisms, such as a protocol based on BEEP which is capable of bidirectional communication between the producer and consumer, should be considered when the capabilities of the consumer are not known by the producer. Abstract The Application/Vnd.pwg-multiplexed content-type, like the Multipart/Related content-type, provides a mechanism for representing objects that consist of multiple components. An Application/Vnd.pwg-multiplexed entity contains a sequence of chunks. Each chunk contains a MIME message or a part of a MIME message. Each MIME message represents a component of the compound object, just as a body part of a Multipart/Related entity represents a component. With a Multipart/Related entity, a body part and its reference in some other body part may be separated by many octets. With an Application/Vnd.pwg-multiplexed entity, a message and its reference in some other message can be made quite close by chunking the message containing the reference. For example, if a long message contains references to images and the producer does not know of the need for each image until it generates the reference, then Application/Vnd.pwg-multiplexed allows the consumer to process the reference to the image and the image before it consumes the entire long message. This ability is important in printing and scanning applications. This document defines the Application/Vnd.pwg- multiplexed content-type. It also provides examples of its use.