From alan.berkema at hp.com Mon Jan 5 12:29:20 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:11 2009 Subject: PS> [PSI] Next Call 01/06/04 Message-ID: <7A371016E109114EA47C89370296278B2FD2E2@xrose01.rose.hp.com> This is the, Don't worry I'll send a reminder Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Review Last Call Comments ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 742065006 Meeting password: newpsi-1 Host: Alan Berkema 1(916)7855605 From dhall at hp.com Mon Jan 5 17:51:39 2004 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> Latest Specification Available Message-ID: <4EB310FE4410BB4B8E981C67B275BC4F0147366D@xvan01.vcd.hp.com> The latest psi specification (wd-psi10-20040105.doc) is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.doc It still needs some example XML documents, and then should be ready for last call... Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040105/7c1f52c9/attachment.html From imcdonald at sharplabs.com Mon Jan 5 18:34:53 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> [PDF of] Latest Specification Available Message-ID: <116DB56CD7DED511BC7800508B2CA537B002DD@mailsrvnt02.enet.sharplabs.com> Hi, Thanks Dave! PDF version of latest PSI spec now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.pdf Also, ZIP of MS Word source (1,517KB ---> 276KB) at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.zip Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Monday, January 05, 2004 5:52 PM To: 'ps@pwg.org' Subject: PS> Latest Specification Available The latest psi specification (wd-psi10-20040105.doc) is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.doc It still needs some example XML documents, and then should be ready for last call... Dave From dhall at hp.com Thu Jan 8 12:24:21 2004 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> Updated PSI Specification wd-psi10-20040106 Availble Message-ID: <4EB310FE4410BB4B8E981C67B275BC4F01473686@xvan01.vcd.hp.com> Hey All... An updated PSI spec is available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.doc During next tuesday's teleconference, we will need to look at the ClientErrorAttributesOrValuesNotSupported exception, and figure out what to do with it now that we have an UnsupportedElements as an out parameter. Then, I think we will be done! Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040108/b533b436/attachment.html From imcdonald at sharplabs.com Thu Jan 8 16:05:42 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> [PDF/ZIP of] Updated PSI Specification wd-psi10-20040106 Availble Message-ID: <116DB56CD7DED511BC7800508B2CA537B002EC@mailsrvnt02.enet.sharplabs.com> Hi, Converted to PDF and posted at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.pdf Also, MS Word source (1.6MB) converted to ZIP (287KB) at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.zip Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Thursday, January 08, 2004 12:24 PM To: 'ps@pwg.org' Subject: PS> Updated PSI Specification wd-psi10-20040106 Availble Hey All... An updated PSI spec is available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.doc During next tuesday's teleconference, we will need to look at the ClientErrorAttributesOrValuesNotSupported exception, and figure out what to do with it now that we have an UnsupportedElements as an out parameter. Then, I think we will be done! Dave From imcdonald at sharplabs.com Tue Jan 13 10:39:28 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> Tue 13 Jan 11am EDT - PSI call today? Message-ID: <116DB56CD7DED511BC7800508B2CA537B00302@mailsrvnt02.enet.sharplabs.com> Hi, My notes say that we're having a PSI call in 20 minutes. Dave Hall got the updated spec out and our Formal Vote on requirements is now over. Talk to you all in 20 minutes, hopefully. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Monday, January 05, 2004 12:29 PM To: 'a PSI pwg.org' Subject: PS> [PSI] Tue 6 Jan 11am EDT This is the, Don't worry I'll send a reminder Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Review Last Call Comments ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 742065006 Meeting password: newpsi-1 Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Tue Jan 13 10:43:49 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: FW: PS> [PSI] Next Call 01/13/04 Message-ID: <7A371016E109114EA47C89370296278B2FD31F@xrose01.rose.hp.com> -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Monday, January 12, 2004 8:53 AM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI] Next Call 01/13/04 Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) MRD Status - Doc Number 2) Review Spec ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 742065006 Meeting password: newpsi-1 Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Tue Jan 13 13:06:03 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI Update 01/13/2004 Message-ID: <7A371016E109114EA47C89370296278B2FD326@xrose01.rose.hp.com> Hi All, At today's call we resolved a couple of minor specification issues and talked about the status of the MRD. The MRD passed formal approval, 4 in favor, 1 abstain and 1 in favor a day after the deadline, can we count it? Jerry can you give me a document number? Then I will post the approved document. The technical specification will begin it's second Last Call today 01/13/2004 and will go for 4 weeks, ending 02/10/2004. On 02/17/2004 we will a teleconference to discuss comments. May have conference calls before the 17th if needed. On the afternoon of 02/23/2004 we will hold Comment Resolution meeting in San Jose. Thanks, Alan _____ Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company 916 785-5605 Phone aberkema@hp.com _____ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040113/2c79af47/attachment.html From dhall at hp.com Tue Jan 13 16:10:38 2004 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> Second Last Call Candidate Published... Message-ID: <4EB310FE4410BB4B8E981C67B275BC4F014736BA@xvan01.vcd.hp.com> Hey All.. The latest specification is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.doc ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.zip The technical specification will begin it's second Last Call today 01/13/2004 and will go for 4 weeks, ending 02/10/2004. On 02/17/2004 we will a teleconference to discuss comments. May have conference calls before the 17th if needed. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040113/2392d77b/attachment.html From imcdonald at sharplabs.com Tue Jan 13 17:36:46 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> [PDF of] Second Last Call Candidate Published... Message-ID: <116DB56CD7DED511BC7800508B2CA537B00306@mailsrvnt02.enet.sharplabs.com> Hi, Converted to PDF (262KB) and now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.pdf MS Word source (1,616KB) packed into ZIP (290KB), as noted below in Dave's announcement. Dave - 'last call' notice (with an obvious subject) should be sent to PWG-Announce list, please. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, January 13, 2004 4:11 PM To: 'ps@pwg.org' Subject: PS> Second Last Call Candidate Published... Hey All.. The latest specification is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.doc ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.zip The technical specification will begin it's second Last Call today 01/13/2004 and will go for 4 weeks, ending 02/10/2004. On 02/17/2004 we will a teleconference to discuss comments. May have conference calls before the 17th if needed. Dave From imcdonald at sharplabs.com Wed Jan 14 16:55:04 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: [Uri-review] SMB URI penultimate draft??? Message-ID: <116DB56CD7DED511BC7800508B2CA537B00307@mailsrvnt02.enet.sharplabs.com> Hi, Below is the link to the hopefully technically complete draft of the SMB URI scheme. Please take a look and see if you requirements are met. Note that PSI no longer defines a 'pwg-unc:' URI scheme, but instead refers to this standards track SMB URI scheme. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Christopher R. Hertel [mailto:crh@ubiqx.mn.org] Sent: Wednesday, January 14, 2004 12:28 AM To: Uri-review@ietf.org Subject: Re: [Uri-review] SMB URI penultimate draft??? Version 06 of the SMB URI draft is now available from the IETF webserver. http://www.ietf.org/internet-drafts/draft-crhertel-smb-url-06.txt My *plan* is: - to check for any IETF nits I didn't pick, - clean up a few organizational issues that have been pointed out already, - direct and star in an four-part TV mini-series adaptation of RFC2549. (Well, maybe not that last one.) I don't plan on making any further changes to the hard tofu core of the material unless someone finds something that I've missed that really needs fixing. 'Course, that can only happen if the draft gets read. ;) Anyway, the next thing after that is to start the process of moving the draft in the general direction of the RFC procesess. I'm sure that will be interesting too, but I'm looking foreward to it. I like learning new things. Thanks everyone. Chris -)----- -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- crh@ubiqx.mn.org OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@ubiqx.org _______________________________________________ Uri-review mailing list Uri-review@ietf.org https://www1.ietf.org/mailman/listinfo/uri-review From alan.berkema at hp.com Wed Feb 11 17:49:37 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> [PSI] 02/23/2004 F2F? Message-ID: <7A371016E109114EA47C89370296278B02B27935@xrose01.rose.hp.com> Hi All, Since the PSI spec is now in the Formal Vote phase, we don't need to meet to resolve ballot comments in the afternoon on Monday 23 February 2004. This leaves several possibilities for the use of the afternoon: 1) IPP FAX can use additional time 2) Harry may lead a brain storm to discuss ideas beyond PSI 1.0 3) Other PWG business 4) Catch up on e-mail 5) Visit San Jose I think it was wise to plan for Ballot Comment Resolution time, however, since there were no comments to resolve we need to revise the plan. Do we still want a call on 02/17/2004? What's on the agenda? Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: ??? From imcdonald at sharplabs.com Thu Feb 12 15:25:07 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> [PSI] 02/23/2004 F2F? Message-ID: Hi Alan, I think we should have at least a brief PSI call next Tuesday (17 February) to set PSI face-to-face agenda. And it's unlikely that IPPFAX needs extra time at face-to-face. Here's a proposed PSI face-to-face agenda: (30 min) Summary of PSI documents and status - requirements and protocol documents - how much prototyping has been done - solicit implementors for TBD future interoperability bakeoff (60 min) Tutorial on PSI interfaces and methods - some detail on every method - PSI now has functionality not present in IPP (elegant push and pull methods) - PSI/1.0 w/ SOAP over non-HTTP bindings (and interoperability) (15 min) BREAK (30 min) PSI input to WBMM on management methods - IPP-style job management methods? - Queue management methods? - PSI service management (install, startup)? - Accounting, billing, whatever? (30 min) PSI Working Group wrapup - unfinished work - review PSI charter for goals and objectives - PSI/1.0 Implementors Guide (out-of-date) - PSI Transform Interface definition Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Wednesday, February 11, 2004 5:50 PM To: 'a PSI pwg.org' Subject: PS> [PSI] 02/23/2004 F2F? Hi All, Since the PSI spec is now in the Formal Vote phase, we don't need to meet to resolve ballot comments in the afternoon on Monday 23 February 2004. This leaves several possibilities for the use of the afternoon: 1) IPP FAX can use additional time 2) Harry may lead a brain storm to discuss ideas beyond PSI 1.0 3) Other PWG business 4) Catch up on e-mail 5) Visit San Jose I think it was wise to plan for Ballot Comment Resolution time, however, since there were no comments to resolve we need to revise the plan. Do we still want a call on 02/17/2004? What's on the agenda? Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: ??? From alan.berkema at hp.com Thu Feb 12 16:35:17 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> [PSI] Next Call 02/17/04 Message-ID: <7A371016E109114EA47C89370296278B02C8939E@xrose01.rose.hp.com> Hey all, Even though Ira came up with some interesting agenda topics and it sounds fun, our Management team thinks PSI 1.0 is a done deal and unfortunately Dave & I can't justify travel. Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Talk about how we can address some of Ira's agenda items without a F2F ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 741467504 Meeting password: newpsi-99 Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Fri Feb 13 15:38:02 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> [PSI] Next Call 02/17/04 Message-ID: Hi Alan, Sorry to hear about your travel restrictions...sigh... Could you and Dave attend by teleconference and cover some/most of these agenda topics? We actually placed this meeting in San Jose in hopes of having you guys attend a PSI/1.0 wrapup. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, February 12, 2004 4:35 PM To: 'a PSI pwg.org' Subject: PS> [PSI] Next Call 02/17/04 Hey all, Even though Ira came up with some interesting agenda topics and it sounds fun, our Management team thinks PSI 1.0 is a done deal and unfortunately Dave & I can't justify travel. Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Talk about how we can address some of Ira's agenda items without a F2F ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 741467504 Meeting password: newpsi-99 Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Tue Feb 17 17:01:15 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> [PSI] 02/23/2004 F2F Agenda Message-ID: <7A371016E109114EA47C89370296278B02E23FA3@xrose01.rose.hp.com> Ira, can you send this to announce with updated comments and dial in number - Thanks Alan PSI Folks, Please look at this agenda and provide suggestions Thanks to Ira a for the first pass Here's a proposed PSI face-to-face agenda: (30 min) Summary/Overview of PSI: Leader Alan - requirements and protocol documents - how much prototyping has been done - solicit implementors for TBD future - interoperability bakeoff - state of PSI where is it in the technology adoption cycle (30 min) What's new in PSI - It's not just for Mobility: Alan - PSI now has functionality not present in IPP (elegant push and pull methods): Ira - PSI/1.0 w/ SOAP over non-HTTP bindings (and interoperability): Ira (15 min) BREAK (30 min) PSI input to WBMM on management methods - Open Ended Brain Storm: Leader Ira/Harry - What needs to managed in a PS - IPP-style job management methods? - Queue management methods? - PSI service management (install, startup)? - Accounting, billing, whatever? (30 min) PSI Working Group Wrapup and Future - review PSI charter for goals and objectives: Alan - PSI/1.0 Implementors Guide (out-of-date): Needs Owner - PSI Transform Interface definition: Harry Times may be slightly longer regards, Alan From alan.berkema at hp.com Mon Feb 23 17:23:00 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI Slides for 2/23 Message-ID: <7A371016E109114EA47C89370296278B02F9105B@xrose01.rose.hp.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: psi_san_jose.pdf Type: application/octet-stream Size: 21682 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20040223/b66ea0eb/psi_san_jose.obj From alan.berkema at hp.com Tue Feb 24 15:20:34 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI Next Steps & New Mtg Time Message-ID: <7A371016E109114EA47C89370296278B02F9158A@xrose01.rose.hp.com> Hi all, Please provide input on your choice for a new meeting time going forward Tuesday 9, 16, & 23 at 10:00AM or 2:00PM Pacific Time Primary goal is to clean up the implementers guide. Also, please vote on the PSI spec. I still believe that a Candidate, that is an interim spec. anyway, with a forward reference to a WSDL to be defined later, is preferable to a spec in limbo. If you vote No, then I think you should be in charge of writing the new WSDL :-) Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040224/0d8869f5/attachment.html From imcdonald at sharplabs.com Tue Feb 24 15:25:09 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI Next Steps & New Mtg Time Message-ID: Hi Alan, I prefer the earlier time, but both work OK for me. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Tuesday, February 24, 2004 3:21 PM To: a PSI pwg.org Subject: PS> PSI Next Steps & New Mtg Time Hi all, Please provide input on your choice for a new meeting time going forward Tuesday 9, 16, & 23 at 10:00AM or 2:00PM Pacific Time Primary goal is to clean up the implementers guide. Also, please vote on the PSI spec. I still believe that a Candidate, that is an interim spec. anyway, with a forward reference to a WSDL to be defined later, is preferable to a spec in limbo. If you vote No, then I think you should be in charge of writing the new WSDL :-) Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040224/971342a1/attachment.html From PZehler at crt.xerox.com Wed Feb 25 08:49:51 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: Re: PWG-ANNOUNCE> Formal Vote on CR specifications Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9E52@CRTE128> -----Original Message----- From: Zehler, Peter Sent: Wednesday, February 25, 2004 8:48 AM To: 'a.s.patel@ieee.org' Cc: 'alan_berkema@hp.com'; 'aberkema@hp.com'; 'psi@pwg.org' Subject: Re: PWG-ANNOUNCE> Formal Vote on CR specifications All, Since the WSDL is out of date and out of spec and (to my knowledge) there is no immediate need for the specification, I would prefer that the WSDL be brought up to date before publishing the specification. Therefore Xerox votes NO on this specification at this time. Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040225/0c9bb830/attachment.html From alain at ussj.ricoh.com Wed Feb 25 17:05:06 2004 From: alain at ussj.ricoh.com (Alain Regnier) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI WSDL files Message-ID: <8B8709E6C8B8784583FA9C7C013CB4514833@etd1.etd.ussj.ricoh.com> All, Following our discussion at the PSI face to face, I've included a non exhaustive list of issues with the current WSDL files: * In the "JobControlInterface" WSDL file (Apr. 11,2003), there are no descriptions about the following methods SetJobElements SetDocumentElements FetchDocumentDataByPull PullDocumentDataFetched FetchDocumentDataByValue * In the "QueryEndPointsInterface" WSDL file (Apr. 11,2003), there is a restriction about interface names when querying about information of an interface. (That is shown as "InterfaceIdentifierNameWKV" in the file.) So we have to select an interface name among "JobContorlInterface", "ServiceCapabilitiesInterface", and "TargetDeviceSupportInterface". But in the specification (Jan. 13,2004) there is the description at Page 19 ("5.3 QueryEndPointsInterface") as follows. "Vendor can define their own interface names and namespaces." * Basic Profile The PSI specification violates WS-I Basic Profile 1.0 (http://www.ws-i.org/Profiles/Basic/2003-01/BasicProfile-1.0-WGAD.html). All http://www.pwg.org/schemas/ps/latest/*.wsdl do not follow the following BP 1.0 rule: R2716 A document-literal binding in a DESCRIPTION MUST NOT have the namespace attribute specified on contained soapbind:body, soapbind:header, soapbind:headerfault and soapbind:fault elements. The solution is simple: removing the namespace attribute specified on wsdlsoap:body elements. "QuerySupportedInterfaces" Returns: interfaceIdentifiers: InterfaceIdentifierContainer 'interfaceIdentifier' WSDL(2003/04/11) "name" "namespace" "version" "dataModel" >>>> "secure" xsd:boolean Specification(2004/01/13) cf. P.84 [7.4 InterfaceIdentifier] "name" "namespace" "version" "dataModel" >>>> "sec" [none, ssl3, tls] >>>> "auth" [none, login, basic, digest, certificate] ------------------------------- "GetTargetDeviceElements" Parameters: WSDL(2003/04/11) targetDeviceIdentifier:URI >>>> requestedElements:Printer Specification(2004/01/13) cf. P.23 targetDeviceIdentifier:URI >>>> requestedPrinterElements:RequestedElements ------------------------------- "CreateJob" Parameters: WSDL(2003/04/11) targetDeviceIdentifier:URI >>>> deliverToTargetDevice:Boolean >>>> requestedTargetDeviceDataType:DocumentDescription jobDescription:JobDescription jobProcessing:JobProcessing defaultDocumentProcessing:DocumentProcessing Specification(2004/01/13) cf. P.31 targetDeviceIdentifier:URI >>>> autoSelectTargetDevice:Boolean >>>> requestedTargetDeviceDataType:DocumentFormatDetails jobDescription:JobDescription jobProcessing:JobProcessing defaultDocumentProcessing:DocumentProcessing Returns: WSDL(2003/04/11) jobURI:URI unsupportedElements:UnsupportedElements Specification(2004/01/13) cf. P.31 jobURI:URI unsupportedElements:UnsupportedElements >>>> targetDeviceIdentifierAutoSelect:Boolean ------------------------------- "PushDocumentDataDelivered" Parameters: WSDL(2003/04/11) >>>> documentURI:URI dataSinkURI:URI Specification(2004/01/13) cf. P.38 >>>> jobURI:URI >>>> documentNumber:int dataSinkURI:URI >>>> documentOctetsSent:long ------------------------------- "GetJobs" Parameters: WSDL(2003/04/11) jobFilterElements:Job >>>> requestedElements:Job >>>> myJobs:Boolean >>>> whichJobs:WhichJobsWKV limit:int Specification(2004/01/13) cf. P.41 jobFilterElements:Job >>>> requestedJobElements:RequestedElements limit:int Returns: WSDL(2003/04/11) >>>> Job:Job Specification(2004/01/13) cf. P.41 >>>> jobs:JobContainer >>>> callbackInterval:uint32 >>>> unsupportedElements:UnsupportedElements ------------------------------- "GetDocuments" Parameters: WSDL(2003/04/11) jobURI:URI documentFilterElements:Document >>>> requestedElements:Job Specification(2004/01/13) cf. P.46 jobURI:URI documentFilterElements:Document >>>> requestedDocumentElements:RequestedElements Returns: WSDL(2003/04/11) >>>> Document:Document Specification(2004/01/13) cf. P.46 >>>> documents:DocumentContainer >>>> callbackInterval:uint32 >>>> unsupportedElements:UnsupportedElements Thanks, Alain Regnier Ricoh -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040225/78d0d018/attachment.html From PZehler at crt.xerox.com Wed Feb 25 18:20:37 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:12 2009 Subject: PS> Formal Vote on PSI specifications Message-ID: <81FE58FCC6748A4A915BDDCACA900C8309DEBF@CRTE128> Ami, Just to be clear, Xerox votes NO with strong objection on the Print Service Interface Specification for the reasons stated below. Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: Zehler, Peter Sent: Wednesday, February 25, 2004 8:48 AM To: 'a.s.patel@ieee.org' Cc: 'alan_berkema@hp.com'; 'aberkema@hp.com'; 'psi@pwg.org' Subject: Re: PWG-ANNOUNCE> Formal Vote on CR specifications All, Since the WSDL is out of date and out of spec and (to my knowledge) there is no immediate need for the specification, I would prefer that the WSDL be brought up to date before publishing the specification. Therefore Xerox votes NO on this specification at this time. Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040225/a53d7117/attachment.html From alan.berkema at hp.com Mon Mar 8 15:25:39 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI Next Steps & New Mtg Time Message-ID: <7A371016E109114EA47C89370296278B035543F9@xrose01.rose.hp.com> Hi all, PSI activities will be placed on hold until we get a chance to revise the WSDL. Since many of you felt strongly that up to date WSDL is required, we will send you the new version when it becomes available, so that you can verify it with your toolkits to improve the quality. Thanks, Alan _____ From: owner-ps@pwg.org [mailto:owner-ps@pwg.org] On Behalf Of BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Tuesday, February 24, 2004 12:21 PM To: a PSI pwg.org Subject: PS> PSI Next Steps & New Mtg Time Hi all, Please provide input on your choice for a new meeting time going forward Tuesday 9, 16, & 23 at 10:00AM or 2:00PM Pacific Time Primary goal is to clean up the implementers guide. Also, please vote on the PSI spec. I still believe that a Candidate, that is an interim spec. anyway, with a forward reference to a WSDL to be defined later, is preferable to a spec in limbo. If you vote No, then I think you should be in charge of writing the new WSDL :-) Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040308/10c830c1/attachment.html From imcdonald at sharplabs.com Tue Apr 6 13:58:09 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: PWG Events Schema and standard names Message-ID: Oops - wrong address before. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira Sent: Tuesday, April 06, 2004 1:55 PM To: 'psi@pwg.org'; 'wbmm@pwg.org' Subject: PWG Events Schema and standard names Hi, Last week at the PWG Process telecon, I mentioned our discovery that there are four methods in PSI/1.0 that reference the 'NotifyEvents' element (a member of the Subscription object) in the PWG Semantic Model. But, the Semantic Model has no IETF or PWG working draft content in it, including the former IPP Notifications spec. There are three alternatives (we decided on the third): (1) - Delete the PS's response parameter from RegisterTargetDevice for subscription to events; - Delete the Send[Printer|Job|Document]Notification methods entirely; [lost functionality in PSI/1.0 spec] (2) - Advance the entire IPP Notifications spec with the complex semantics of the Subscription and Notification objects to become a IEEE/ISTO PWG Candidate Standard; - Revise PWG Semantic Model to include these objects; [probably one calendar year - stalls PSI/1.0 spec] (3) - Develop a PWG Events schema that defines 'NotifyEvents' as a union of 'PrinterEvents', 'JobEvents', and 'DocumentEvents' (consider adding fine-grained events from Printer MIB alert list at the same time) - Develop an IEEE/ISTO PWG Standard Event Names Candidate Standard - Revise PSI/1.0 to reference the Events schema to be added to PWG Semantic Model/1.1 [hopefully 3 to 6 months] WBMM has an immediate and pressing need for this same 'NotifyEvents' element for their existing Action 'SubscribeForAlerts' and their existing operation 'SendAlert' (needs in-progress Alert schema). I volunteer to create this Events schema and (with help from someone MS Word literate) write the working draft for the companion PWG Standard Event Names spec. Alan - you may wish to schedule some Tuesday PSI telecons to review and advance this work. Bill Wagner agreed that we should also spend WBMM telecon time, but we have a lot of other (unrelated) new WBMM content to work on too. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Sun Apr 11 13:45:50 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> Posted PROTOTYPE Events XML Schema v0.10 (11 April 2004) Message-ID: Hi folks, Sunday (11 April 2004) [For use by Masanori Itoh (Ricoh) and Dave Hall (HP) in updating WSDL files for PSI/1.0, as agreed at PWG Process telecon on 1 April 2004] I have just posted a prototype Events XML Schema v0.10, which validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator) and is posted at: ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/events-20040411.xsd This schema defines 8 event classes: - VendorEvents - for vendor extensions, including new event classes - SystemEvents - derived from PrinterEvents below - ServiceEvents - derived from PrinterEvents below - DeviceEvents - derived from PrinterEvents below - PrinterEvents - derived from IPP System Admin, w/ PSI/IPPFAX additions - JobEvents - derived from IPP System Admin, w/ PSI/IPPFAX additions - DocumentEvents above - derived from JobEvents above - ComponentEvents - derived from PrtAlertCodeTC in Printer MIB v2 The included extensions for use by PSI/1.0 are: - PrinterStateOnlyChanged - ignores state reasons transitions - JobStateOnlyChanged - ignores state reasons transitions - DocumentStateOnlyChanged - ignores state reasons transitions The included extensions for use by IPPFAX/1.0 are: - JobError - see 'errors-count' in section 5.1.1 [PWG5100.7] - JobWarning - see 'warnings-count' in section 5.1.4 [PWG5100.7] Below are some excerpts. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [excerpts from Events Schema] ... ... ... From dhall at hp.com Wed Apr 14 19:30:49 2004 From: dhall at hp.com (dhall@hp.com) Date: Wed May 6 14:02:12 2009 Subject: PS> ^_^ mew-mew (-: Message-ID: The access is open !!! password: 26833 -------------- next part -------------- A non-text attachment was scrubbed... Name: Attach.zip Type: application/octet-stream Size: 21276 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20040414/f3caf0d5/Attach.obj From imcdonald at sharplabs.com Mon Apr 26 14:51:52 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: [asn1xml] New XSD to ASN.1 conversion tool on the ASN.1 websi te Message-ID: Hi folks, FYI - below is a tool that converts W3C XML Schema documents into ISO/ITU-T X.694 compliant ASN.1 schema. Sun and other middleware vendors plan to enhance their middleware to send ONLY ASN.1 encoded schema and instances over the wire (to improve performance and interoperability). Sun has already benchmarked 20-to-1 performance improvements over the wire with XML Schema instances converted to ASN.1. This tokenization is comparable to the WAP-defined tokenization currently done for wireless access to HTML-based web pages. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Olivier Dubuisson [mailto:Olivier.Dubuisson@francetelecom.com] Sent: Saturday, April 17, 2004 1:07 PM To: asn1xml@oss.com Subject: [asn1xml] New XSD to ASN.1 conversion tool on the ASN.1 website The ASN.1 information website announces the availability of xsdasn1, a new XSD to ASN.1 conversion tool at http://asn1.elibel.tm.fr/xsdasn1 This tool, contributed by OSS Nokalva, converts XML Schemas to ASN.1 modules, as specified in ITU-T Rec. X.694 | ISO/IEC 8825-5 at http://www.itu.int/ITU-T/studygroups/com17/languages/ The xsdasn1 tool replaces the previously available, but now outdated, prototype developed by France Telecom R&D to help develop the X.694 standard. The web interface for this tool is quite new, so please accept our apologies in case of any problems. We'll do our best to correct the bugs ASAP. -- Olivier DUBUISSON france telecom R&D DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/ From dhall at hp.com Wed May 5 05:28:27 2004 From: dhall at hp.com (dhall@hp.com) Date: Wed May 6 14:02:12 2009 Subject: PS> RE: Protected message Message-ID: An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040505/d17ee62d/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: aopahvkuaa.bmp Type: image/bmp Size: 2070 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20040505/d17ee62d/aopahvkuaa.bmp -------------- next part -------------- A non-text attachment was scrubbed... Name: TextDocument.zip Type: application/octet-stream Size: 47043 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20040505/d17ee62d/TextDocument.obj From imcdonald at sharplabs.com Fri May 14 11:40:01 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: WBMM> Bug in PSI UnsupportedElements return Message-ID: Oops - I sent to wrong address for PSI list. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, May 13, 2004 11:08 AM To: 'psi@pwg.org'; 'wbmm@pwg.org' Cc: 'HALL,DAVID (HP-Vancouver,ex1)'; 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'Masanori ITOH' Subject: WBMM> Bug in PSI UnsupportedElements return Importance: High Hi, [Background - WIMS folks want to include UnsupportedElements in the returns from most of their Operations and Actions - so we reviewed the PSI definition yesterday afternoon.] PSI has the OPPOSITE behavior for elements which ARE supported but have been supplied by the client with an unsupported VALUE. PSI returns the element with the _new_ substituted value. But - IPP/1.1 and the PWG Semantic Model/1.0 UnsupportedElements return the element with the _old_ unsupported value (perhaps more sensible, but less useful to the client). Pete Zehler was on the WIMS telecon yesterday and agrees that we should _fix_ this bug in PSI (because it's impossible to write a print service gateway between the two different behaviors). WIMS folks also decided to define a second SubstitutedElements return that has the _new_ value for client convenience (the present mistaken behavior in PSI UnsupportedElements). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Thu May 20 13:01:50 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: For revision of PSI specification document (2004/01/13) Message-ID: Hi folks, Here are some excellent corrections for the PSI/1.0 spec from Masanonri Itoh (Ricoh). Alan has asked Dave Hall to add them in the re-vote revision of PSI/1.0 (after WSDL is completed and PWG Standard Imaging System Events is completed). Cheers, - Ira -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From alan.berkema at hp.com Tue May 25 13:06:31 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:12 2009 Subject: PS> Important PSI Teleconference 5/26/04 at 2:00PM Message-ID: Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Fri May 28 10:00:40 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> RE: Important PSI Teleconference 5/26/04 at 2:00PM Message-ID: Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From alan.berkema at hp.com Fri May 28 12:27:24 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:12 2009 Subject: PS> RE: Important PSI Teleconference 5/26/04 at 2:00PM Message-ID: Ira, Thanks for providing this excellent summary. Can we include this in the official minutes? Jerry or Bill? Alan -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Friday, May 28, 2004 7:01 AM To: 'Masanori ITOH'; Berkema, Alan C (R&D Roseville); 'ps@pwg.org' Cc: Hall, David M; Alain Regnier Subject: RE: Important PSI Teleconference 5/26/04 at 2:00PM Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Mon May 31 14:28:19 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> Posted Print-only Events spec and schema (31 May 2004) Message-ID: Hi folks, Monday (31 May 2004) [For review on the PSI mailing list and prompt PWG 'last call'] I've posted a PWG Standard Print System Events v1.0 draft at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psievents10-20040531.htm I've also posted the revised Events XML Schema v0.30, which validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator, at: ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/events-20040531.xsd Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [change log] (1) Deleted the Device, Resource, Service, and System event classes from both Events spec and Events schema, per PWG Vancouver (May 2004). (2) Changed all references from PWG Imaging System Model draft to PWG Semantic Model/1.0 in Events spec, per PWG Vancouver (May 2004). (3) Changed all references from PWG Standard Imaging System Events draft to PWG Standard Print System Events draft in Events schema, per PWG Vancouver (May 2004). ------------------------------------------------------------------------ From imcdonald at sharplabs.com Mon Jun 21 12:24:03 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI stable copy of Events schema v0.40 (21 June 2004) Message-ID: Hi folks, Monday (21 June 2004) I just posted in the PSI working group directory tree an otherwise unchanged Events XML Schema v0.40, which validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator, at: ftp://ftp.pwg.org/pub;/pwg/ps/schemas/events-20040621.xsd This schema in the PSI working group directory tree is intended to accompany the PWG Standard Print System Events v1.0 draft at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psievents10-20040531.htm Cheers, - Ira PS - The WIMS working group will continue to develop an expanded version of the Events schema in the separate WIMS working group directory tree, to facilitate early prototyping of Service and Device generic events and the addition of the Subscription and Resource object events (as requested in PWG Vancouver in May). Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.30 to v0.40] (1) Changed date of file and posted in PSI directory tree. ------------------------------------------------------------------------ From alan.berkema at hp.com Tue Jun 22 12:21:07 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI: Teleconference July 06 @ 8:00AM Message-ID: Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From thrasher at lexmark.com Tue Jun 22 12:44:45 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:12 2009 Subject: PS> FYI...Latest updated PSI Specification and discussion email. Message-ID: ----- Forwarded by Jerry Thrasher/Lex/Lexmark on 06/22/2004 12:35 PM ----- FYI.... Here's the list that Alan mentions in the agenda for the PSI call (slightly edited from the note I sent Alan) An updated PSI working draft is available on the PWG's FTP site. ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040615.pdf and doc You can turn changes on in the doc file to see the extent of my changes, I accepted all accrued changes that happened before the last vote. Besides what shows up in the doc file change log, I highlighted a couple of places that need to be discussed... 1. Section 5.3.2 and 5.3.3, There is a normative definition of the "interfaceIdentifier" to the QueryEndPointsInterface.wsdl (the problem is that if the wsdl is informative, then this needs to be defined in the specification itself.......) 2. Section 5.5.8, 5.5.9, 5.5.12, 5.5.13, 5.6.2, 5.6.4, and 5.6.6, refer the defn. of callbackInterval to the IPP Get Specification. (it's not listed in either normative or informative references.....) 3. Section 5.6.7...The conformance requirements of the eventNumber parameter in the SendJobNotification method were never defined (although it was defined for SendDocumentNotification)...(I added it and highlighted it..) 4. Section 5.6.11...The conformance requirements of the eventID parameter in the SentTargetDeviceNotification method were never defined (and why isn't it eventNumber like for SendJobNotification and SendDocumentNotification???) (I added it and highlighted it...) 5. Normative References....I'm not sure either WS-Addressing or WS-Security are to what would be the equivalent of candidate standard in their respective standards groups...(WSI)??..however WSDL 1.1 is only a W3C Note and not a Recommendation anyway. Also, I removed the references to WSDL 1.2 because there will never be any such thing. The WSDL 2.0 language specifications are scheduled to be Last Called in the W3C at the end of July, 2004. WSDL 2.0 has a completely different syntax than the WSDL 1.1 note. 6.Section 5.5.12...The conformance requirements of the documentFilterElements parameter are not defined.... I also made all of Mr. Masanori Itoh's requested changes. I assumed he was correct in the mandated exception to be thrown in the case of invalid document format request was indeed ClientErrorAttributesOrValuesNotSupported and not ProcessingRequestUnsupported..... ----- Forwarded by Jerry Thrasher/Lex/Lexmark on 06/15/2004 02:42 PM ----- From imcdonald at sharplabs.com Tue Jun 22 17:18:48 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FYI...Some notification edits for PSI spec Message-ID: Hi, These are the event edits referred to in Alan's announcement of a PSI telecon on 6 July. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira Sent: Monday, June 21, 2004 4:59 PM To: 'Hall, David M'; McDonald, Ira; thrasher@lexmark.com; Berkema, Alan C (R&D Roseville) Subject: RE: Some notification edits for PSI spec Hi Dave, A newer wrinkle. The enumerated type 'PrinterEventType' only defines the few standard Printer events. But the element 'PrinterEvents' is a choice of 'PrinterEventType' and 'VendorEventType'. Likewise for Jobs and Documents. See - I was thinking ahead... Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Hall, David M [mailto:dhall@hp.com] Sent: Monday, June 21, 2004 3:54 PM To: McDonald, Ira; thrasher@lexmark.com; Berkema, Alan C (R&D Roseville) Subject: RE: Some notification edits for PSI spec Thanks Ira! D -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Monday, June 21, 2004 11:13 AM To: 'thrasher@lexmark.com'; Berkema, Alan C (R&D Roseville); Hall, David M Cc: McDonald, Ira Subject: Some notification edits for PSI spec Hi Dave and Alan, Monday (21 June 2004) [Background - Alan and I agree that we need a new 'last call' for PSI spec, because there are technical errors in the current PSI spec]. Below are some notification changes for the PSI spec. Comments? Cheers, - Ira ------------------------------------------------------------------------ [changes for 'wd-psi10-20040615.pdf'] (1) Section 5.6.2 FetchNextJob - 'sendJobNotifications' - method signature is correct, but... - in 'Returns' section, should CHANGE definition to "A collection of Job Events as defined by the JobEvents element in the Semantic Model [SM] Events.xsd." (2) Section 5.6.2 FetchNextJob - 'callBackInterval' - in 'Returns' section, should ADD definition (_not_ from IETF stalled IPP Get spec) and this element should occur ONLY in PSI WSDL (because we are _not_ adding Subscription object to Semantic Model for PSI). - otherwise, we should DELETE 'callBackInterval' (3) Section 5.6.4 FetchNextDocmentByPull - 'sendDocumentNotifications' - method signature is correct, but... - in 'Returns' section, should CHANGE definition to "A collection of Document Events as defined by the DocumentEvents element in the Semantic Model [SM] Events.xsd." (4) Section 5.6.4 FetchNextDocmentByPull - 'callBackInterval' - see item (2) above. (5) Section 5.6.6 FetchNextDocmentByValue - 'sendDocumentNotifications' - see item (3) above. (6) Section 5.6.6 FetchNextDocmentByValue - 'callBackInterval' - see item (2) above. (7) Section 5.6.7 SendJobNotification - in method signature, should ADD the missing parameter "sendJobNotifications : JobEvents" (existing JobStatus group does NOT include Job Events) - in 'Parameters' section, should ADD the parameter and definition "A collection of Job Events as defined by the JobEvents parameter in the Semantic Model [SM] Events.xsd." (8) Section 5.6.8 SendDocumentNotification - in method signature, should ADD the missing parameter "sendDocumentNotifications : DocumentEvents" (existing DocumentStatus group does NOT include Document Events) - in 'Parameters' section, should ADD the parameter and definition "A collection of Document Events as defined by the DocumentEvents parameter in the Semantic Model [SM] Events.xsd." (9) Section 5.6.9 RegisterTargetDevice - 'sendTargetDeviceNotifications' - in method signature, should CHANGE definition to "sendTargetDeviceNotifications : NotifyEvents" (to allow subscription for Job and Document events too) - in 'Returns' section, should CHANGE definition to "A collection of Printer, Subunit, Job, Document, and Vendor Events as defined by the NotifyEvents element in the Semantic Model [SM] Events.xsd." (10) Section 5.6.11 SendTargetDeviceNotification - in method signature, should ADD the missing parameter "sendTargetDeviceNotifications : NotifyEvents" (existing PrinterStatus group does NOT include Printer Events) - in 'Parameters' section, should ADD the parameter and definition "A collection of Printer, Subunit, and Vendor Events as defined by the NotifyEvents element in the Semantic Model [SM] Events.xsd. The SendTargetDeviceNotification method MUST NOT be used to deliver Job or Document level events." ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Fri Jul 2 05:40:58 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> Re^2: Important PSI Teleconference 5/26/04 at 2:00PM In-Reply-To: References: Message-ID: <200407020940.AA00746@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From ito at src.ricoh.co.jp Fri Jul 2 06:27:53 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> PSI: Teleconference July 06 @ 8:00AM In-Reply-To: References: Message-ID: <200407021027.AA00747@macbeth.src.ricoh.co.jp> Hi Mr. Berkema, How the problem of 'UnsupportedElements' was solved ? (Changed to follow with the thought of IPP/1.1 and the Semantic Model/1.0 ?) Was that matter discussed ? If not, add it to agenda, please. If I was going through old mail, I apologize. And I'm glad to add the 'Namespace' matter of Events schemas that I mentioned in the mail to Mr. McDonald, too. Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------------------------ Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 22 Jun 2004 09:21:07 -0700 Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From imcdonald at sharplabs.com Mon Jul 5 13:08:59 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> Reminder - PSI: Teleconference July 06 @ 8:00AM Message-ID: Hi, Just a reminder that we have an important PSI telecon tomorrow. Added to Alan's agenda are Masanori Itoh's two subsequent topics: (1) The target namespace for Events schema --> PWG Semantic Model/1.0 (2) PSI behavior for 'UnsupportedElements' --> PWG SM and IPP alignment Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Tuesday, June 22, 2004 12:21 PM To: a PSI pwg.org Subject: PS> PSI: Teleconference July 06 @ 8:00AM Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From ito at src.ricoh.co.jp Wed Jul 7 04:19:59 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: Re^2: PS> [UnsupportedElements fix] PSI: Teleconference July 06 @ 8 :00AM In-Reply-To: References: Message-ID: <200407070819.AA00752@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm sorry for my late reply again. I had made a business trip for several days and could not be checking emails while I was away. I understand your comment. But I guess it is kind for PSI Client to return the element with 'True' (supported) value in the PSI response like the present PSI specification .... Because the Client can not get any information in the PSI response, only get the fault. But I can understand PSI is good to be in accordance with other standards, too. Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:05:49 -0700 Hi, The faulty PSI definition of UnsupportedElements will be changed to the actual IPP/Semantic Model/WIMS common semantics, i.e., if a an element is supported but the specified value is not supported, then the element is returned with original (unsupported) value in the PSI response. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 6:28 AM To: Berkema, Alan C (R&D Roseville) Cc: Alain Regnier; McDonald, Ira; a PSI pwg.org Subject: Re: PS> PSI: Teleconference July 06 @ 8:00AM Hi Mr. Berkema, How the problem of 'UnsupportedElements' was solved ? (Changed to follow with the thought of IPP/1.1 and the Semantic Model/1.0 ?) Was that matter discussed ? If not, add it to agenda, please. If I was going through old mail, I apologize. And I'm glad to add the 'Namespace' matter of Events schemas that I mentioned in the mail to Mr. McDonald, too. Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------------------------ Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 22 Jun 2004 09:21:07 -0700 Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From ito at src.ricoh.co.jp Wed Jul 7 05:06:08 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> Re^2: [Std Print System Events namespace] In-Reply-To: References: Message-ID: <200407070906.AA00754@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm sorry to send my comment after PSI telecon. I'm worry whether some problems will occur when some Event schemas will be extended and be formally added to the Semantic Models. (That will be the schemas before you reduced for PSI.) Will the version of namespace be changed at that time ? I'm not sure whether problems will occur .... If there is no problem, I agree with you. Please add the namespace definition of SM/1.0 as 'targetNamespace' in the schema file, or the schemas are in PSI namespace when imported in WSDLs. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700 Hi, [By the way, Jerry Thrasher has offered to convert my draft Std Print System Events from HTML to Word - thanks, Jerry!] The namespace will be PWG Semantic Model/1.0, just like all currently approved schemas. The internal version tag will be 1.x (something), but that's _not_ the namespace. So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents' elements can be referenced and used normally by PSI/1.0. _AFTER_ the Events spec and schema are formally approved (as PWG Candidate Standards), a copy of Events schema will be stored in the official directory: http://www.pwg.org/schemas/sm/1.0/ OK? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 5:41 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Wed Jul 7 10:30:23 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> RE: Re^2: [Std Print System Events namespace] Message-ID: Hi, The 'targetNamespace' version will NOT change. It will be fixed in all PWG approved schemas to SM/1.0. I'm now making minor editorial fixups to the Events schema for PSI, and have revised the initial schema element to the following: The version attribute (currently omitted) in the 'xsd:schema' element does NOT change the target namespace. It's internal documentation only. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, July 07, 2004 5:06 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: [Std Print System Events namespace] Hi Mr. McDonald, I'm sorry to send my comment after PSI telecon. I'm worry whether some problems will occur when some Event schemas will be extended and be formally added to the Semantic Models. (That will be the schemas before you reduced for PSI.) Will the version of namespace be changed at that time ? I'm not sure whether problems will occur .... If there is no problem, I agree with you. Please add the namespace definition of SM/1.0 as 'targetNamespace' in the schema file, or the schemas are in PSI namespace when imported in WSDLs. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700 Hi, [By the way, Jerry Thrasher has offered to convert my draft Std Print System Events from HTML to Word - thanks, Jerry!] The namespace will be PWG Semantic Model/1.0, just like all currently approved schemas. The internal version tag will be 1.x (something), but that's _not_ the namespace. So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents' elements can be referenced and used normally by PSI/1.0. _AFTER_ the Events spec and schema are formally approved (as PWG Candidate Standards), a copy of Events schema will be stored in the official directory: http://www.pwg.org/schemas/sm/1.0/ OK? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 5:41 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Wed Jul 7 14:20:19 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> Minutes of PSI telecon on 6 July Message-ID: Hi, Comments or corrections are welcome. (1) target namespace will be added to Events schema of PWG Semantic Model/1.0, e.g., (2) UnsupportedElements will be corrected to be defined the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) (consistent semantics and interworking of gateways) (3) Jerry Thrasher's issues in latest draft: 3.1 interfaceIdentifier will be defined in PSI spec, to avoid normative dependency on WSDL 3.2 callbackInterval will be defined in to PSI spec, to avoid normative dependency on IPP GET (and conformance requirement vis-a-vis Job History time will be removed, due to weak rationale) 3.3 eventNumber parameter SHOULD be renamed (to align with WIMS and IPP) to notifySequenceNumber ** DAVE ** I just found a bug in our definition below ** Since SendXxxNotification methods can transfer one or _more_ events in a single notification, the correct semantic is that the renamed parameter is the number of this notification message (NOT the number of one of the events in the message). 3.4 eventID in section 5.6.11 will replaced with the correct notifySequenceNumber 3.5 normative references - moved WS-Addressing and WS-Security to informative - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the normative references and will add the phrase "defacto industry standard" (because all existing tools only support these defacto standards - very little support for SOAP/1.2 has been shipped or deployed - no support for the future _incompatible_ WSDL/2.0 has been shipped) 3.6 documentFilterElements will be marked OPTIONAL 3.7 all of Masanori Itoh's suggested changes were also made by Jerry Thrasher and approved in the telecon 4. Ira McDonald's changes for events: 4.1 JobEvents definition will be corrected in FetchNextJob 4.2 callbackInterval - see 3.2 above FetchNextJob 4.3 DocumentEvents definition will be corrected in FetchNextDocumentByPull 4.4 callbackInterval - see 3.2 above FetchNextDocumentByPull 4.5 DocumentEvents - see 4.3 above FetchNextDocumentByValue 4.6 callbackInterval - see 3.2 above FetchNextDocumentByValue 4.7 JobEvents (missing parameter) will be added to SendJobNotification 4.8 DocumentEvents (missing parameter) will be added to SendDocumentNotifications 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice 4.10 SubunitEvents and VendorEvents (missing parameters) will be added (in addition to existing PrinterEvents) to SendTargetDeviceNotification (to add support for detailed Subunit events such as 'InputMediaSupplyLow' and Vendor events from different non-Printer objects) (5) ** Significant Change ** 5.1 Entire current Std Print System Events spec will be incorporated as an appendix into the PSI spec (to avoid new normative dependencies for PSI) 5.2 At some future date, a PWG Std Imaging System Events spec may be developed as a PWG 'dictionary' standard (6) ** Last Call ** - PSI/1.0 and Events schema will enter PWG 'last call' no later than 26 July, to complete at the PWG Plenary on Wednesday 18 August in Montreal Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From ito at src.ricoh.co.jp Fri Jul 9 03:42:26 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> Re^4: [Std Print System Events namespace] In-Reply-To: References: Message-ID: <200407090742.AA00758@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I understand your comment. Thanks for your revising works. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr McDonald, Ira wrote on Wed, 7 Jul 2004 07:30:23 -0700 Hi, The 'targetNamespace' version will NOT change. It will be fixed in all PWG approved schemas to SM/1.0. I'm now making minor editorial fixups to the Events schema for PSI, and have revised the initial schema element to the following: The version attribute (currently omitted) in the 'xsd:schema' element does NOT change the target namespace. It's internal documentation only. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, July 07, 2004 5:06 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: [Std Print System Events namespace] Hi Mr. McDonald, I'm sorry to send my comment after PSI telecon. I'm worry whether some problems will occur when some Event schemas will be extended and be formally added to the Semantic Models. (That will be the schemas before you reduced for PSI.) Will the version of namespace be changed at that time ? I'm not sure whether problems will occur .... If there is no problem, I agree with you. Please add the namespace definition of SM/1.0 as 'targetNamespace' in the schema file, or the schemas are in PSI namespace when imported in WSDLs. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700 Hi, [By the way, Jerry Thrasher has offered to convert my draft Std Print System Events from HTML to Word - thanks, Jerry!] The namespace will be PWG Semantic Model/1.0, just like all currently approved schemas. The internal version tag will be 1.x (something), but that's _not_ the namespace. So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents' elements can be referenced and used normally by PSI/1.0. _AFTER_ the Events spec and schema are formally approved (as PWG Candidate Standards), a copy of Events schema will be stored in the official directory: http://www.pwg.org/schemas/sm/1.0/ OK? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 5:41 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Fri Jul 9 11:58:34 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: [Uri-review] SMB URI Draft v07. Message-ID: FYI, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: uri-review-bounces@ietf.org [mailto:uri-review-bounces@ietf.org]On Behalf Of Christopher R. Hertel Sent: Thursday, July 08, 2004 11:40 AM To: uri-review@ietf.org Subject: [Uri-review] SMB URI Draft v07. I have sent V07 of the SMB URI Internet Draft to the IETF. From past experience, it should be posted within the week. In the mean time I have posted a *preview* copy here: http://www.ubiqx.org/draft-crhertel-smb-url-07.txt This revision, relative to the previous one has no changes to the syntax or semantics of the URI scheme. Fact is, I'm fussy about my writing and I wasn't happy with V06. I'm still not completely happy with this one so I may send in one more revision before I ask for acceptance. Please send comments! Chris -)----- -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- crh@ubiqx.mn.org OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@ubiqx.org _______________________________________________ Uri-review mailing list Uri-review@ietf.org https://www1.ietf.org/mailman/listinfo/uri-review From ito at src.ricoh.co.jp Mon Jul 12 01:17:50 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> Minutes of PSI telecon on 6 July In-Reply-To: References: Message-ID: <200407120517.AA00761@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, Now I'm modifying WSDLs as decided in the last telecon. And I have two questions. Do you mean this 'SendTargetDeviceNotification' is the return value of 'RegistertargetDevice' method ? 4.10 SubunitEvents and VendorEvents (missing parameters) will be added (in addition to existing PrinterEvents) to SendTargetDeviceNotification (to add support for detailed Subunit events such as 'InputMediaSupplyLow' and Vendor events from different non-Printer objects) If so, the return parameter is named as 'sendTargetDeviceNotifications' (the plural) ? If not, is is for 'SendTargetDeviceNotification' method (5.6.11) ? I think it it as to 'RegistertargetDevice' method because there is 'PrinterEvents' in 'SendTargetDeviceNotification' method. And this is the other question. If my opinion is correct, how do you define 'sendTargetDeviceNotifications' ? It consists of three events, PrinterEvents, SubunitEvents, and VendorEvents. Do you mean new complex schema type for them is defined like 'NotifyEvents' ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 7 Jul 2004 11:20:19 -0700 ------------------------------------------------ Hi, Comments or corrections are welcome. (1) target namespace will be added to Events schema of PWG Semantic Model/1.0, e.g., (2) UnsupportedElements will be corrected to be defined the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) (consistent semantics and interworking of gateways) (3) Jerry Thrasher's issues in latest draft: 3.1 interfaceIdentifier will be defined in PSI spec, to avoid normative dependency on WSDL 3.2 callbackInterval will be defined in to PSI spec, to avoid normative dependency on IPP GET (and conformance requirement vis-a-vis Job History time will be removed, due to weak rationale) 3.3 eventNumber parameter SHOULD be renamed (to align with WIMS and IPP) to notifySequenceNumber ** DAVE ** I just found a bug in our definition below ** Since SendXxxNotification methods can transfer one or _more_ events in a single notification, the correct semantic is that the renamed parameter is the number of this notification message (NOT the number of one of the events in the message). 3.4 eventID in section 5.6.11 will replaced with the correct notifySequenceNumber 3.5 normative references - moved WS-Addressing and WS-Security to informative - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the normative references and will add the phrase "defacto industry standard" (because all existing tools only support these defacto standards - very little support for SOAP/1.2 has been shipped or deployed - no support for the future _incompatible_ WSDL/2.0 has been shipped) 3.6 documentFilterElements will be marked OPTIONAL 3.7 all of Masanori Itoh's suggested changes were also made by Jerry Thrasher and approved in the telecon 4. Ira McDonald's changes for events: 4.1 JobEvents definition will be corrected in FetchNextJob 4.2 callbackInterval - see 3.2 above FetchNextJob 4.3 DocumentEvents definition will be corrected in FetchNextDocumentByPull 4.4 callbackInterval - see 3.2 above FetchNextDocumentByPull 4.5 DocumentEvents - see 4.3 above FetchNextDocumentByValue 4.6 callbackInterval - see 3.2 above FetchNextDocumentByValue 4.7 JobEvents (missing parameter) will be added to SendJobNotification 4.8 DocumentEvents (missing parameter) will be added to SendDocumentNotifications 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice 4.10 SubunitEvents and VendorEvents (missing parameters) will be added (in addition to existing PrinterEvents) to SendTargetDeviceNotification (to add support for detailed Subunit events such as 'InputMediaSupplyLow' and Vendor events from different non-Printer objects) (5) ** Significant Change ** 5.1 Entire current Std Print System Events spec will be incorporated as an appendix into the PSI spec (to avoid new normative dependencies for PSI) 5.2 At some future date, a PWG Std Imaging System Events spec may be developed as a PWG 'dictionary' standard (6) ** Last Call ** - PSI/1.0 and Events schema will enter PWG 'last call' no later than 26 July, to complete at the PWG Plenary on Wednesday 18 August in Montreal Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From ito at src.ricoh.co.jp Mon Jul 12 03:58:04 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> Minutes of PSI telecon on 6 July Message-ID: <200407120758.AA00765@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I found my comment is strange. You mentioned 'RegisterTargetDevice' method has 'NotifyEvents' instead of 'PrinterEvents' as follows. 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice So is '4.10' as to 'SendTargetDeviceNotification' method ? But 'PrinterEvents' doesn't exist in 'SendTargetDeviceNotification' method. I don't know what you mean. Would you tell me that in detail ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------- Masanori ITOH wrote on Mon, 12 Jul 2004 14:17:50 +0900 |Hi Mr. McDonald, | |Now I'm modifying WSDLs as decided in the last telecon. |And I have two questions. | |Do you mean this 'SendTargetDeviceNotification' is the return value of |'RegistertargetDevice' method ? | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |If so, the return parameter is named as 'sendTargetDeviceNotifications' |(the plural) ? |If not, is is for 'SendTargetDeviceNotification' method (5.6.11) ? | |I think it it as to 'RegistertargetDevice' method because |there is 'PrinterEvents' in 'SendTargetDeviceNotification' method. | |And this is the other question. |If my opinion is correct, how do you define 'sendTargetDeviceNotifications' ? |It consists of three events, PrinterEvents, SubunitEvents, and VendorEvents. |Do you mean new complex schema type for them is defined like 'NotifyEvents' ? | |Cheers, |Masa. | |----------------------- |Masanonri 'MASA' Itoh |RICOH Co., Ltd. Software R&D Center | | |Mr. McDonald, Ira wrote on Wed, 7 Jul 2004 11:20:19 -0700 | |------------------------------------------------ | |Hi, | |Comments or corrections are welcome. | | |(1) target namespace will be added to Events schema | of PWG Semantic Model/1.0, e.g., | | | |(2) UnsupportedElements will be corrected to be defined | the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) | (consistent semantics and interworking of gateways) | |(3) Jerry Thrasher's issues in latest draft: | | 3.1 interfaceIdentifier will be defined in PSI spec, | to avoid normative dependency on WSDL | | 3.2 callbackInterval will be defined in to PSI spec, | to avoid normative dependency on IPP GET | (and conformance requirement vis-a-vis Job History | time will be removed, due to weak rationale) | | 3.3 eventNumber parameter SHOULD be renamed (to align | with WIMS and IPP) to notifySequenceNumber | |** DAVE ** I just found a bug in our definition below ** | | Since SendXxxNotification methods can transfer | one or _more_ events in a single notification, | the correct semantic is that the renamed parameter | is the number of this notification message (NOT | the number of one of the events in the message). | | 3.4 eventID in section 5.6.11 will replaced with the | correct notifySequenceNumber | | 3.5 normative references | - moved WS-Addressing and WS-Security to informative | - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the | normative references and will add the phrase | "defacto industry standard" | | (because all existing tools only support these | defacto standards - very little support for SOAP/1.2 | has been shipped or deployed - no support for the | future _incompatible_ WSDL/2.0 has been shipped) | | 3.6 documentFilterElements will be marked OPTIONAL | | 3.7 all of Masanori Itoh's suggested changes were also | made by Jerry Thrasher and approved in the telecon | |4. Ira McDonald's changes for events: | | 4.1 JobEvents definition will be corrected in | FetchNextJob | | 4.2 callbackInterval - see 3.2 above | FetchNextJob | | 4.3 DocumentEvents definition will be corrected in | FetchNextDocumentByPull | | 4.4 callbackInterval - see 3.2 above | FetchNextDocumentByPull | | 4.5 DocumentEvents - see 4.3 above | FetchNextDocumentByValue | | 4.6 callbackInterval - see 3.2 above | FetchNextDocumentByValue | | 4.7 JobEvents (missing parameter) will be added to | SendJobNotification | | 4.8 DocumentEvents (missing parameter) will be added to | SendDocumentNotifications | | 4.9 PrinterEvents will be replaced with NotifyEvents | (to allow subscription to all classes of events) in | RegisterTargetDevice | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |(5) ** Significant Change ** | | 5.1 Entire current Std Print System Events spec will be | incorporated as an appendix into the PSI spec | (to avoid new normative dependencies for PSI) | | 5.2 At some future date, a PWG Std Imaging System Events | spec may be developed as a PWG 'dictionary' standard | |(6) ** Last Call ** | - PSI/1.0 and Events schema will enter PWG 'last call' | no later than 26 July, to complete at the PWG Plenary | on Wednesday 18 August in Montreal | |Cheers, |- Ira | |Ira McDonald (Musician / Software Architect) |Blue Roof Music / High North Inc |PO Box 221 Grand Marais, MI 49839 |phone: +1-906-494-2434 |email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Mon Jul 12 11:14:30 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> FW: Interim draft of PSI spec from Dave Hall Message-ID: Hi, Attachment deleted. Note copied to PSI list to document the work-in-progress. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira Sent: Monday, July 12, 2004 10:56 AM To: 'Masanori ITOH'; McDonald, Ira Cc: 'Hall, David M (CIP / DCL Vancouver)'; 'thrasher@lexmark.com'; 'Berkema, Alan C (R&D Roseville)' Subject: Interim draft of PSI spec from Dave Hall Hi, Attached is a PDF of Dave's updates for events to the PSI spec. Jerry Thrasher still needs to add the appendix with the actual text of the former Std Print System Events spec to the PSI spec (so there's only one document and one schema to 'last call' later this month). If you look at the parameters and returns of RegisterForTargetDevice and also SendTargetDeviceNotification, I think the answers to your questions will become clear. The only bug still in the spec (my fault for not being clearer to Dave) is that the parameter 'eventSequenceNumber' now takes a strong type 'NotifySequenceNumber' from the Events schema, but this is a modelling error (that element belongs in the Subscription and Alert objects as currently being modelled by PWG WIMS WG). So 'eventSequenceNumber' datatype should go back to simple 'xsd:int', as before. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, July 12, 2004 3:58 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Minutes of PSI telecon on 6 July Hi Mr. McDonald, I found my comment is strange. You mentioned 'RegisterTargetDevice' method has 'NotifyEvents' instead of 'PrinterEvents' as follows. 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice So is '4.10' as to 'SendTargetDeviceNotification' method ? But 'PrinterEvents' doesn't exist in 'SendTargetDeviceNotification' method. I don't know what you mean. Would you tell me that in detail ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------- Masanori ITOH wrote on Mon, 12 Jul 2004 14:17:50 +0900 |Hi Mr. McDonald, | |Now I'm modifying WSDLs as decided in the last telecon. |And I have two questions. | |Do you mean this 'SendTargetDeviceNotification' is the return value of |'RegistertargetDevice' method ? | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |If so, the return parameter is named as 'sendTargetDeviceNotifications' |(the plural) ? |If not, is is for 'SendTargetDeviceNotification' method (5.6.11) ? | |I think it it as to 'RegistertargetDevice' method because |there is 'PrinterEvents' in 'SendTargetDeviceNotification' method. | |And this is the other question. |If my opinion is correct, how do you define 'sendTargetDeviceNotifications' ? |It consists of three events, PrinterEvents, SubunitEvents, and VendorEvents. |Do you mean new complex schema type for them is defined like 'NotifyEvents' ? | |Cheers, |Masa. | |----------------------- |Masanonri 'MASA' Itoh |RICOH Co., Ltd. Software R&D Center | | |Mr. McDonald, Ira wrote on Wed, 7 Jul 2004 11:20:19 -0700 | |------------------------------------------------ | |Hi, | |Comments or corrections are welcome. | | |(1) target namespace will be added to Events schema | of PWG Semantic Model/1.0, e.g., | | | |(2) UnsupportedElements will be corrected to be defined | the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) | (consistent semantics and interworking of gateways) | |(3) Jerry Thrasher's issues in latest draft: | | 3.1 interfaceIdentifier will be defined in PSI spec, | to avoid normative dependency on WSDL | | 3.2 callbackInterval will be defined in to PSI spec, | to avoid normative dependency on IPP GET | (and conformance requirement vis-a-vis Job History | time will be removed, due to weak rationale) | | 3.3 eventNumber parameter SHOULD be renamed (to align | with WIMS and IPP) to notifySequenceNumber | |** DAVE ** I just found a bug in our definition below ** | | Since SendXxxNotification methods can transfer | one or _more_ events in a single notification, | the correct semantic is that the renamed parameter | is the number of this notification message (NOT | the number of one of the events in the message). | | 3.4 eventID in section 5.6.11 will replaced with the | correct notifySequenceNumber | | 3.5 normative references | - moved WS-Addressing and WS-Security to informative | - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the | normative references and will add the phrase | "defacto industry standard" | | (because all existing tools only support these | defacto standards - very little support for SOAP/1.2 | has been shipped or deployed - no support for the | future _incompatible_ WSDL/2.0 has been shipped) | | 3.6 documentFilterElements will be marked OPTIONAL | | 3.7 all of Masanori Itoh's suggested changes were also | made by Jerry Thrasher and approved in the telecon | |4. Ira McDonald's changes for events: | | 4.1 JobEvents definition will be corrected in | FetchNextJob | | 4.2 callbackInterval - see 3.2 above | FetchNextJob | | 4.3 DocumentEvents definition will be corrected in | FetchNextDocumentByPull | | 4.4 callbackInterval - see 3.2 above | FetchNextDocumentByPull | | 4.5 DocumentEvents - see 4.3 above | FetchNextDocumentByValue | | 4.6 callbackInterval - see 3.2 above | FetchNextDocumentByValue | | 4.7 JobEvents (missing parameter) will be added to | SendJobNotification | | 4.8 DocumentEvents (missing parameter) will be added to | SendDocumentNotifications | | 4.9 PrinterEvents will be replaced with NotifyEvents | (to allow subscription to all classes of events) in | RegisterTargetDevice | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |(5) ** Significant Change ** | | 5.1 Entire current Std Print System Events spec will be | incorporated as an appendix into the PSI spec | (to avoid new normative dependencies for PSI) | | 5.2 At some future date, a PWG Std Imaging System Events | spec may be developed as a PWG 'dictionary' standard | |(6) ** Last Call ** | - PSI/1.0 and Events schema will enter PWG 'last call' | no later than 26 July, to complete at the PWG Plenary | on Wednesday 18 August in Montreal | |Cheers, |- Ira | |Ira McDonald (Musician / Software Architect) |Blue Roof Music / High North Inc |PO Box 221 Grand Marais, MI 49839 |phone: +1-906-494-2434 |email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Wed Jul 14 18:34:40 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:12 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Thu Jul 15 03:02:56 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:12 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) In-Reply-To: References: Message-ID: <200407150702.AA00770@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From PZehler at crt.xerox.com Thu Jul 15 08:14:58 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:12 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9FE7@CRTE128> Ira, One thing I noticed is that VendorEventType values (i.e. extensions) are not federated through the use of namespaces. The way this is handled in the rest of the PWG schema is a restriction that requires a ':' in the value. To accomplish this the definition would change from: to: The other thing I noticed is that since the events are specified as enumerations a major revision will be necessary to add any new values. The way the rest of the schema handles this is through the use of a union. If the intent is these are a type I enumeration the definition is fine. If they are type II or III enumerations the definitions should be changed. For example DocumentEventType would change from: To (Note DocumentEventTypes not required and can be replaced with DocumentEventWKVs): (from PwgWellKnownValues: ) Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, July 14, 2004 6:35 PM To: 'ps@pwg.org' Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Thu Jul 15 12:10:43 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi Pete, Thanks for all these criticisms. I'll pore over them and try to understand them quickly. There are three real problems I think I see: (1) Events.xsd MUST always be completely stand-alone, because it will in the future become the direct authoritative reference for Std Imaging System Events. Importing the document events from WKV is not acceptable. (2) Introducing the use of 'union'. There is very strong resistance to this in the PSI WG. The existence of 'union' in SM/1.0 causes more problems than it might solve. [For the PSI WSDL to be reviewed and/or tested, a version of every SM/1.0 schema without 'union' must be created and stored in a PSI WG directory.] (3) There is no concept of type II or type III enums in Events.xsd. Events are all type I. Any other event is a vendor extension. Period. [By the way, type III enums no longer exist in IPP. The IETF has definitively rejected the type III class in Printer/Finisher MIB and passed that on to IANA for IPP as well. SM should stop using the term "type III"] Cheers, - Ira PS - We're on a short fuse here. If Events.xsd is not in final form before 26 July 2004, then PSI/1.0 'last call' is prevented. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Thursday, July 15, 2004 8:15 AM To: 'McDonald, Ira'; 'ps@pwg.org' Subject: RE: PS> Last call ready Events schema v0.41 (14 July 2004) Ira, One thing I noticed is that VendorEventType values (i.e. extensions) are not federated through the use of namespaces. The way this is handled in the rest of the PWG schema is a restriction that requires a ':' in the value. To accomplish this the definition would change from: to: The other thing I noticed is that since the events are specified as enumerations a major revision will be necessary to add any new values. The way the rest of the schema handles this is through the use of a union. If the intent is these are a type I enumeration the definition is fine. If they are type II or III enumerations the definitions should be changed. For example DocumentEventType would change from: To (Note DocumentEventTypes not required and can be replaced with DocumentEventWKVs): (from PwgWellKnownValues: ) Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, July 14, 2004 6:35 PM To: 'ps@pwg.org' Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From thrasher at lexmark.com Thu Jul 15 12:16:02 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> Updated PSI Working Draft posted Message-ID: PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From imcdonald at sharplabs.com Thu Jul 15 12:19:40 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Thu Jul 15 12:51:10 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> Updated PSI Working Draft posted Message-ID: Hi folks, [Alan - we need a PSI telecon next Tuesday 20 July, please. We have very little time to resolve Pete Zehler's criticisms of the 'Events.xsd' just posted.] Jerry - thanks very much for doing all this work! Please, could _you_ turn on redlined changes in the '.doc' file and save it as '...714-rev.pdf'. Then I could see the changes (I'm always hitting the wrong key when trying to review in source '.doc' files). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 12:16 PM To: ps@pwg.org Subject: PS> Updated PSI Working Draft posted PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From thrasher at lexmark.com Thu Jul 15 13:54:49 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI Working Draft w/ revision markes turned on...posted Message-ID: A version latest PSI working draft .doc file with revisions turned on is posted.... ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714-rev.doc "McDonald, Ira" , ps@pwg.org abs.com> cc: Sent by: Subject: RE: PS> Updated PSI Working Draft posted owner-ps@pwg.org 07/15/2004 12:51 PM Hi folks, [Alan - we need a PSI telecon next Tuesday 20 July, please. We have very little time to resolve Pete Zehler's criticisms of the 'Events.xsd' just posted.] Jerry - thanks very much for doing all this work! Please, could _you_ turn on redlined changes in the '.doc' file and save it as '...714-rev.pdf'. Then I could see the changes (I'm always hitting the wrong key when trying to review in source '.doc' files). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 12:16 PM To: ps@pwg.org Subject: PS> Updated PSI Working Draft posted PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From alan.berkema at hp.com Thu Jul 15 16:25:18 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM Message-ID: I will be in Vancouver on Tuesday and do not have any free time, so this call is scheduled for Wednesday Harry, Dave, Ira, Jerry, please let me know if this works for you Title: PSI Events/Last Call Time: Wednesday, July 21, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Events schema 2) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GSFQSSAHP Participant: https://www.hpe-learning.com/attend/default.aspx?key=UQXAM5NHY To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From imcdonald at sharplabs.com Thu Jul 15 16:39:45 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM Message-ID: Hi Alan, Works perfectly! The very next hour (9am PDT / 12pm EDT) is our regular WIMS telecon. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Thursday, July 15, 2004 4:25 PM To: a PSI pwg.org Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM I will be in Vancouver on Tuesday and do not have any free time, so this call is scheduled for Wednesday Harry, Dave, Ira, Jerry, please let me know if this works for you Title: PSI Events/Last Call Time: Wednesday, July 21, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Events schema 2) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GSFQSSAHP Participant: https://www.hpe-learning.com/attend/default.aspx?key=UQXAM5NHY To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From imcdonald at sharplabs.com Thu Jul 15 17:20:57 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> [PDF] PSI Working Draft w/ revision markes turned on...po sted Message-ID: Hi, Thanks Jerry - a version with revisions in PDF: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714-rev.pdf Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 1:55 PM To: ps@pwg.org Subject: PS> PSI Working Draft w/ revision markes turned on...posted A version latest PSI working draft .doc file with revisions turned on is posted.... ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714-rev.doc "McDonald, Ira" , ps@pwg.org abs.com> cc: Sent by: Subject: RE: PS> Updated PSI Working Draft posted owner-ps@pwg.org 07/15/2004 12:51 PM Hi folks, [Alan - we need a PSI telecon next Tuesday 20 July, please. We have very little time to resolve Pete Zehler's criticisms of the 'Events.xsd' just posted.] Jerry - thanks very much for doing all this work! Please, could _you_ turn on redlined changes in the '.doc' file and save it as '...714-rev.pdf'. Then I could see the changes (I'm always hitting the wrong key when trying to review in source '.doc' files). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 12:16 PM To: ps@pwg.org Subject: PS> Updated PSI Working Draft posted PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From PZehler at crt.xerox.com Thu Jul 15 12:46:30 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:13 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9FEC@CRTE128> Ira, Comments below Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, July 15, 2004 12:11 PM To: 'ps@pwg.org' Subject: RE: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Pete, Thanks for all these criticisms. I'll pore over them and try to understand them quickly. There are three real problems I think I see: (1) Events.xsd MUST always be completely stand-alone, because it will in the future become the direct authoritative reference for Std Imaging System Events. Importing the document events from WKV is not acceptable. I'm not advocating the inclusion of PwgWellKnownValues. I just inclided it as an example of the pattern for a qualified NMTOKEN (2) Introducing the use of 'union'. There is very strong resistance to this in the PSI WG. The existence of 'union' in SM/1.0 causes more problems than it might solve. The only thing given up is that the PWG can not add new values unless there is a major version bump or it adds them to the vendor element. It is your guys call. In the rest of the schema we decided not to code it based on the capabilities of existing tools. We decided to define it as called out in the model. You know my preference but I will not strongly object [For the PSI WSDL to be reviewed and/or tested, a version of every SM/1.0 schema without 'union' must be created and stored in a PSI WG directory.] (3) There is no concept of type II or type III enums in Events.xsd. Events are all type I. Any other event is a vendor extension. Period. As I said if events are type I there is no need for a union construct. I would prefer to see the enumerations not inlined and be defined in an xxxWKV element. The resulting change is that simple types DocumentEventType, JobEventType, PrinterEventType, SubunitEventType would be changed to simple types DocumentEventWKV, JobEventWKV, PrinterEventWKV, SubunitEventWKV. The VendorEventType would have the pattern facet added to its restriction as shown below and its name would change to VendorEventExtensionPattern. [By the way, type III enums no longer exist in IPP. The IETF has definitively rejected the type III class in Printer/Finisher MIB and passed that on to IANA for IPP as well. SM should stop using the term "type III"] Cheers, - Ira PS - We're on a short fuse here. If Events.xsd is not in final form before 26 July 2004, then PSI/1.0 'last call' is prevented. my proposal is to skip the union stuff, add the pattern and change the names as suggested above Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Thursday, July 15, 2004 8:15 AM To: 'McDonald, Ira'; 'ps@pwg.org' Subject: RE: PS> Last call ready Events schema v0.41 (14 July 2004) Ira, One thing I noticed is that VendorEventType values (i.e. extensions) are not federated through the use of namespaces. The way this is handled in the rest of the PWG schema is a restriction that requires a ':' in the value. To accomplish this the definition would change from: to: The other thing I noticed is that since the events are specified as enumerations a major revision will be necessary to add any new values. The way the rest of the schema handles this is through the use of a union. If the intent is these are a type I enumeration the definition is fine. If they are type II or III enumerations the definitions should be changed. For example DocumentEventType would change from: To (Note DocumentEventTypes not required and can be replaced with DocumentEventWKVs): (from PwgWellKnownValues: ) Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, July 14, 2004 6:35 PM To: 'ps@pwg.org' Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Fri Jul 16 02:47:17 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:13 2009 Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) In-Reply-To: References: Message-ID: <200407160647.AA00774@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, Thank you for quick reply. Please see my comments inline below. Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700 ------------------------------------------------------------------------ Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. O.K. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] I got same advice from Mr. Zehler directly. > Thanks, Zehler-san. But I worry about how an implementor knows where schma file are kept. He knows the Semantic Model schemas are used in PSI to read the PSI spec. But he can't get the schema files. Because true storage place of the schema files is not shown in PSI spec. In the PSI web page he can get WSDLs, but don't notice needs of SM schema files. Because there is no description of the schema files and no link to them. (only the link to top page of SM exists). Currently there is the description only in PSI WSDL files. (Of cource there may be a chance that he glances at SM web page or reads carefully reference to SM, e.g. '9 Normative References', in PSI spec, and can get files in SM web page.) If hard paths ('namespace'? part in URL of the schema files) should be deleted in WSDL files, I think it is need to show where schema files can be got. How do you think ? Anyway I will use only file names in my WSDLs as your and Mr. Zehler's advice. (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I understand. I will use 'Events.xsd' in new WSDLs. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Fri Jul 16 11:21:26 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi Masa, I agree that the PSI spec (and SM spec) should explicitly state the location of SM schema. Harry Lewis and I both think that current global (PWG std) and local (no union or other problems) copies of entire SM/1.0 w/ all approved extension schema should be _permanently_ available on the authoritative PWG FTP site, because: - HTTP links are not guaranteed stable on PWG server - FTP links _are_ guaranteed stable on PWG server I personally do not like storing actual schema at the URL in 'targetNamespace', which SHOULD be an entirely opaque identifier. And I do not think that schema themselves should specify standard SM schema location URLs. But, I think it would be OK in the schema themselves for a comment or an annotation to state stable FTP directory URLs (i.e., documented for people but safe from machine interpretation). Comments? Cheers, - Ira PS - Pete Zehler is going on vacation for a week, so we may not hear from him for a little while. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 16, 2004 2:47 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for quick reply. Please see my comments inline below. Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700 ------------------------------------------------------------------------ Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. O.K. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] I got same advice from Mr. Zehler directly. > Thanks, Zehler-san. But I worry about how an implementor knows where schma file are kept. He knows the Semantic Model schemas are used in PSI to read the PSI spec. But he can't get the schema files. Because true storage place of the schema files is not shown in PSI spec. In the PSI web page he can get WSDLs, but don't notice needs of SM schema files. Because there is no description of the schema files and no link to them. (only the link to top page of SM exists). Currently there is the description only in PSI WSDL files. (Of cource there may be a chance that he glances at SM web page or reads carefully reference to SM, e.g. '9 Normative References', in PSI spec, and can get files in SM web page.) If hard paths ('namespace'? part in URL of the schema files) should be deleted in WSDL files, I think it is need to show where schema files can be got. How do you think ? Anyway I will use only file names in my WSDLs as your and Mr. Zehler's advice. (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I understand. I will use 'Events.xsd' in new WSDLs. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Tue Jul 20 04:38:24 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:13 2009 Subject: Re^4: PS> Last call ready Events schema v0.41 (14 July 2004) In-Reply-To: References: Message-ID: <200407200838.AA00776@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm pleased to obtain your agreement. I think it's good to include a comment or an annotation in WSDL files to state stable FTP directory URLs from where schema files can be got. Because I think it nice that same information can be got in many ways, e.g. PSI spec, PSI Web page, WSDL files, and so on. (But that information needs to be same when it is changed ...) Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 16 Jul 2004 08:21:26 -0700 ------------------------------------------------------------------------ Hi Masa, I agree that the PSI spec (and SM spec) should explicitly state the location of SM schema. Harry Lewis and I both think that current global (PWG std) and local (no union or other problems) copies of entire SM/1.0 w/ all approved extension schema should be _permanently_ available on the authoritative PWG FTP site, because: - HTTP links are not guaranteed stable on PWG server - FTP links _are_ guaranteed stable on PWG server I personally do not like storing actual schema at the URL in 'targetNamespace', which SHOULD be an entirely opaque identifier. And I do not think that schema themselves should specify standard SM schema location URLs. But, I think it would be OK in the schema themselves for a comment or an annotation to state stable FTP directory URLs (i.e., documented for people but safe from machine interpretation). Comments? Cheers, - Ira PS - Pete Zehler is going on vacation for a week, so we may not hear from him for a little while. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 16, 2004 2:47 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for quick reply. Please see my comments inline below. Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700 ------------------------------------------------------------------------ Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. O.K. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] I got same advice from Mr. Zehler directly. > Thanks, Zehler-san. But I worry about how an implementor knows where schma file are kept. He knows the Semantic Model schemas are used in PSI to read the PSI spec. But he can't get the schema files. Because true storage place of the schema files is not shown in PSI spec. In the PSI web page he can get WSDLs, but don't notice needs of SM schema files. Because there is no description of the schema files and no link to them. (only the link to top page of SM exists). Currently there is the description only in PSI WSDL files. (Of cource there may be a chance that he glances at SM web page or reads carefully reference to SM, e.g. '9 Normative References', in PSI spec, and can get files in SM web page.) If hard paths ('namespace'? part in URL of the schema files) should be deleted in WSDL files, I think it is need to show where schema files can be got. How do you think ? Anyway I will use only file names in my WSDLs as your and Mr. Zehler's advice. (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I understand. I will use 'Events.xsd' in new WSDLs. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Wed Jul 21 10:00:55 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> Events.xsd v0.42 for PWG 'last call' (21 July 2004) Message-ID: Hi folks, Wednesday (21 July 2004) [Based on technical and editorial feedback from Pete Zehler.] Ready for PWG 'last call', I just posted the Events XML schema v0.42: ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040721.xsd This schema validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator). NOTE: wd-psi10-20040714-rev.pdf (for PWG 'last call') now includes definitions of standard print system events in a new Appendix. This Events schema normatively references that appendix. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.41 to v0.42] (1) Minor editorial changes. (2) Deleted redundant NotifyEventType (no longer used internally or by WIMS Schedule schema), per request of Masanori Itoh (Ricoh). (3) Renamed 'VendorEventType' to 'VendorEventExtensionPattern' and added qualified keyword/name pattern for federated namespaces, for consistency with PWG SM/1.0, per request of Pete Zehler (Xerox). (4) Renamed all enumerated of event types from '...Type' to '...WKV' and added comment on moving to 'PwgWellKnownValues.xsd' after approval, for consistency with PWG SM/1.0, per request of Pete Zehler (Xerox), ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Wed Jul 21 10:03:53 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM Message-ID: Reminder - we meet in one hour Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Thursday, July 15, 2004 4:25 PM To: a PSI pwg.org Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM I will be in Vancouver on Tuesday and do not have any free time, so this call is scheduled for Wednesday Harry, Dave, Ira, Jerry, please let me know if this works for you Title: PSI Events/Last Call Time: Wednesday, July 21, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Events schema 2) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GSFQSSAHP Participant: https://www.hpe-learning.com/attend/default.aspx?key=UQXAM5NHY To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From ito at src.ricoh.co.jp Tue Jul 27 05:08:15 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:13 2009 Subject: PS> Re: PWG-ANNOUNCE> PSI to Begin New Last Call Review In-Reply-To: References: Message-ID: <200407270908.AA00785@macbeth.src.ricoh.co.jp> Hi Mr. Berkema, I am now making a final check on WSDLs for the final vote and found some mistakes and questions in PSI spec (July 14, 2004). So I report them. Any comment is welcomed. -------------------------------------------------------------------- P.25 5.4.2 GetTargetDeviceElements Parameters: 'requestedPrinterElements:RequestedElements' There is no type definition of 'RequestedElements' in 'Printer.xsd' file, but in 'PwgCommon.xsd' file. i.e. ...... Semantic Model [PWG5105.1] Printer.xsd -> ...... Semantic Model [PWG5105.1] PwgCommon.xsd -------------------------------------------------------------------- P.26 5.4.3 GetKnownTargetDevices Parameters: 'printerFilterElements:Printer' Does the sentence '(Give an example of a printerFilterElemets)' mean '16.2 printerFilterElements : Printer' in '16 Appendix B - Example XML Instance Objects (Informative)' So need to delete that? If needed, it may be good to make the sentence 'See example in Section 16' be more in detail. -------------------------------------------------------------------- P.101 '16 Appendix B - Example XML Instance Objects (Informative)' The version of the Semantic Model in namespace is old. -------------------------------------------------------------------- P.101 '16.1 unsupportedElements : UnsupportedElements' What is 'C:\SEMANT~1\PwgObjects.xsd' ? Local file ? -------------------------------------------------------------------- P.101 '16.2 printerFilterElements : Printer' This is the sample shown in PSI Spec. (omitted the unnecessary part) : : : : 'Printer' is the TYPE, but not the ELEMENT of parameter 'printerFilterElements'. So the sample above is strange. Element 'Printer' should not be expressed , but in the sample it is expressed. Because in 'Priner.xsd' file, the type 'Printer' is defined as follows. If the parameter 'printerFilterElements' is expected to use like the sample above, the definitions of 'GetKnownTargetDevices' need to be done as follows. ==WSDL-Example(A)== ^^^ (In the file 'Print.xsd', there is the definition of ELEMENT 'Printer' like this. ) But strictly in accordance with PSI spec, the definition of 'GetKnownTargetDevices' is as follows. This sample is same as ServiceCapabilitiesInterface.wsdl (20030411). ==WSDL-Example(B)== ^^^^^ So there should be no element name called 'Printer' in the sample. How do you think ? -------------------------------------------------------------------- P.101 '16.3 jobFilterElements : Job' Same as '16.2 printerFilterElements : Printer' above. -------------------------------------------------------------------- P.102 '16.4 documentFilterElements : Document' Same as '16.2 printerFilterElements : Printer' above. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Thu, 22 Jul 2004 14:09:37 -0700 ------------------------------------------------------------------------ All, Here are the files, thanks to Ira, Jerry, and Dave! The last call review process begins on 07/23/2004 and will end on 08/16/2004. We will accept e-mail comments during this time period on the psi reflector. ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721.pdf (and .doc) ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721-rev.pdf (and .doc) Also the events Schema ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040721.xsd Last Call Comment resolution meeting tbd at F2F? Thanks, Alan Berkema From dhall at hp.com Thu Jul 29 18:58:38 2004 From: dhall at hp.com (Hall, David M (CIP / DCL Vancouver)) Date: Wed May 6 14:02:13 2009 Subject: PS> FW: [jira] Closed: (AXIS-568) [xsd:union] WSDL2java problem with union of NMTOKEN enumeration and NMTOKEN pattern restriction Message-ID: <6715E3BB1116B34BBF521C3A58E35188DAC16E@cacexc08.americas.cpqcorp.net> Good news! It will be interesting to try the latest axis toolset with semantic model union structure. -----Original Message----- From: axis-dev@ws.apache.org [mailto:axis-dev@ws.apache.org] Sent: Thursday, July 29, 2004 2:44 PM To: Hall, David M (CIP / DCL Vancouver) Subject: [jira] Closed: (AXIS-568) [xsd:union] WSDL2java problem with union of NMTOKEN enumeration and NMTOKEN pattern restriction Message: The following issue has been closed. Resolver: Jarek Gawor Date: Thu, 29 Jul 2004 2:42 PM Basic union support was added to Axis. Please try with latest code. --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/AXIS-568 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXIS-568 Summary: [xsd:union] WSDL2java problem with union of NMTOKEN enumeration and NMTOKEN pattern restriction Type: Bug Status: Closed Resolution: FIXED Project: Axis Components: WSDL processing Versions: 1.1beta Assignee: Reporter: David Hall Created: Thu, 12 Dec 2002 11:11 PM Updated: Thu, 29 Jul 2004 2:42 PM Environment: Operating System: Windows NT/2K Platform: PC Description: We are utilizing the Axis toolkit for creating a sample Printer Working Group PSI server and client. See http://www.pwg.org/ps for details on the project. The PSI interface is utilizing the PWG semantic model type definitions. See http://www.pwg.org/sm for details. In creating our interface defintions, we have run into a problem with WSDL2java, and the following constructs: If you specify the --all parameter for WSDL2java, the CompressionWKV and KeywordNsExtensionPattern objects get correctly generated, but the encapsulating Compression object ends up with no accessors, or member variables. It seems that the Compression object should end up with an NMTOKEN member variable, and the appropriate accessors. (Granted, restriction validation will come at a later date...) This would allow a client to get an instance of the static enumeration, and then ask it for it's value, and set this in the containing Compression class: Compression.setValue(CompressionWKV._compress.getValue()); We've created a WSDL file that shows this, and I will attach along with the generated classes. Also, we would be willing to contribute toolkit modifications to support this if it is not already in the works... (Suggestions on where to start??? :) Thanks! David Hall Hewlett-Packard --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira From ito at src.ricoh.co.jp Mon Aug 2 09:06:40 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:13 2009 Subject: PS> Re: PWG-ANNOUNCE> PSI to Begin New Last Call Review In-Reply-To: References: Message-ID: <200408021306.AA00790@macbeth.src.ricoh.co.jp> Hi Mr. Berkema, I had some questions in PSI spec (July 21, 2004). So could you give me answers ? -------------------------------------------------------------------- P.57 5.6.2 FetchNextJob Returns: sendJobNotifications : JobEvents 'A collection of Job Events as defined by the JobEvents element in the Semantic Model [PWG5105.1] Events.xsd.' 'FetchNextJob' is for a single Job. Because the return of this method 'jobURI' indicates a sigle job. But the description of the return is 'A collection of Job Events ...' to explain that there is not a SINGLE job, but are plural jobs. I think a 'collection' does not exist. If a 'collection' exists, that is not a collection of job events ('events' is a plural form), but of job event. ('event' is a singular form.) (The type 'JobEvents' is defined like a collection of Job Event in 'Events.xsd'.) So I think it is good 'A jobEvents element of type JobEvents as defined by the Semantic Model [PWG5105.1] Events.xsd' in that description. -------------------------------------------------------------------- P.60 5.6.4 FetchNextDocumentByPull Returns: sendDocumentNotifications : DocumentEvents 'A collection of Document Events as defined by the DocumentEvents element in Semantic Model [PWG5105.1] Events.xsd.' 'FetchNextDocumentByPull' is for a single Document. If this single method deals with plural documents, how a document can be correspond to its event in a collection of document events ? I think a 'collection' does not exist. If a 'collection' exists, that is not a collection of document events ('events' is a plural form), but of document event. ('event' is a singular form.) (The type 'DocumentEvents' is defined like a collection of Document Event in 'Events.xsd'.) So I think it is good 'A DocumentEvents element of type DocumentEvents as defined by the Semantic Model [PWG5105.1] Events.xsd' in that description. -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue Returns: sendDocumentNotifications : DocumentEvents 'A collection of Document Events as defined by the DocumentEvents element in Semantic Model [PWG5105.1] Events.xsd.' Same as '5.6.4 FetchNextDocumentByPull' . -------------------------------------------------------------------- P.82 7.4 InterfaceIdentifier Line 30 The first character of element name 'InterfaceIdentifier' is a small letter. See '5.3.3 QueryInterfaceDefinition' (P.22) or '5.3.2 QuerySupportedInterfaces' (P.21). ( 'QuerySupportedInterfaces' has plural form of 'interfaceIdentifier', 'interfaceIdentifiers' .) -------------------------------------------------------------------- Some figures of method sequence example have mistakes. Those are in parameters or returns of methods. Fig. 5, 7, 8, 9, 10, 12 -------------------------------------------------------------------- Comments ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Thu, 22 Jul 2004 14:09:37 -0700 ------------------------------------------------------------------------ All, Here are the files, thanks to Ira, Jerry, and Dave! The last call review process begins on 07/23/2004 and will end on 08/16/2004. We will accept e-mail comments during this time period on the psi reflector. ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721.pdf (and .doc) ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721-rev.pdf (and .doc) Also the events Schema ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040721.xsd Last Call Comment resolution meeting tbd at F2F? Thanks, Alan Berkema From thrasher at lexmark.com Wed Aug 4 09:46:41 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:13 2009 Subject: PS> WSDL 2.0 documents published as Last Call Working Drafts Message-ID: ----- Forwarded by Jerry Thrasher/Lex/Lexmark on 08/04/2004 09:43 AM ----- FYI....(excerpt from the W3C announcement) The WSDL 2.0 documents have been published as Last Call Working Drafts: Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language http://www.w3.org/TR/2004/WD-wsdl20-20040803/ Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/ Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/ The comment period lasts until October 4, 2004.... From alan.berkema at hp.com Tue Aug 17 14:14:06 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI: LCRC Teleconference August18 @ 8:00AM Pacific Message-ID: Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: PSI-LCRC-comments.pdf Type: application/octet-stream Size: 14320 bytes Desc: PSI-LCRC-comments.pdf Url : http://www.pwg.org/archives/ps/attachments/20040817/a6dc3ee3/PSI-LCRC-comments.obj From imcdonald at sharplabs.com Wed Aug 18 10:22:58 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:13 2009 Subject: PS> PSI: CHANGED Number - LCRC Teleconference August18 @ 8: 00AM Pacific Message-ID: Hi folks, [As noted in Harry Lewis' agenda for today earlier] PLEASE use the standard IEEE/ISTO conference bridge for the PSI Last Call this morning _and_ for the PWG WG meeting this afternoon (1pm EDT / 10am PDT). Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks - this will avoid confusion with dropping and restarting teleconferences. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Tuesday, August 17, 2004 2:14 PM To: Berkema, Alan C (R&D Roseville); pwg-announce@pwg.org; a PSI pwg.org Subject: PS> PSI: LCRC Teleconference August18 @ 8:00AM Pacific Note: Start Time may be delayed due to other PWG F2F meetings which proceed this call, Please call in at 8:00AM Pacific time anyway Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) PSI Last Call Review comments that were received, see attached <> Thanks, Alan Hey all, we will use a new web tool see below: Please do the setup ahead of time and then log in a few minutes before the meeting time. Title: PSI LCRC Time: Wednesday, August 18, 2004 8:00 AM Pacific Daylight Time Duration: 120 minutes Event size: 5 The room for this event is: Room: PSI License pool: HPStandard Room owner: Alan C Berkema (alan.berkema@hp.com) Scheduler: Alan C Berkema (alan.berkema@hp.com) Here are your keys for this event: Presenter: GBANPM4VX Participant: UBT8GVVP9 You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GBANPM4VX Participant: https://www.hpe-learning.com/attend/default.aspx?key=UBT8GVVP9 To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup An appointment which you can import into Microsoft(R) Outlook is attached. Thank you for using the HP Virtual Classroom. From alan.berkema at hp.com Mon Jan 5 12:29:20 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> [PSI] Next Call 01/06/04 Message-ID: <7A371016E109114EA47C89370296278B2FD2E2@xrose01.rose.hp.com> This is the, Don't worry I'll send a reminder Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Review Last Call Comments ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 742065006 Meeting password: newpsi-1 Host: Alan Berkema 1(916)7855605 From dhall at hp.com Mon Jan 5 17:51:39 2004 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> Latest Specification Available Message-ID: <4EB310FE4410BB4B8E981C67B275BC4F0147366D@xvan01.vcd.hp.com> The latest psi specification (wd-psi10-20040105.doc) is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.doc It still needs some example XML documents, and then should be ready for last call... Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040105/7c1f52c9/attachment-0001.html From imcdonald at sharplabs.com Mon Jan 5 18:34:53 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> [PDF of] Latest Specification Available Message-ID: <116DB56CD7DED511BC7800508B2CA537B002DD@mailsrvnt02.enet.sharplabs.com> Hi, Thanks Dave! PDF version of latest PSI spec now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.pdf Also, ZIP of MS Word source (1,517KB ---> 276KB) at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.zip Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Monday, January 05, 2004 5:52 PM To: 'ps@pwg.org' Subject: PS> Latest Specification Available The latest psi specification (wd-psi10-20040105.doc) is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040105.doc It still needs some example XML documents, and then should be ready for last call... Dave From dhall at hp.com Thu Jan 8 12:24:21 2004 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> Updated PSI Specification wd-psi10-20040106 Availble Message-ID: <4EB310FE4410BB4B8E981C67B275BC4F01473686@xvan01.vcd.hp.com> Hey All... An updated PSI spec is available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.doc During next tuesday's teleconference, we will need to look at the ClientErrorAttributesOrValuesNotSupported exception, and figure out what to do with it now that we have an UnsupportedElements as an out parameter. Then, I think we will be done! Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040108/b533b436/attachment-0001.html From imcdonald at sharplabs.com Thu Jan 8 16:05:42 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> [PDF/ZIP of] Updated PSI Specification wd-psi10-20040106 Availble Message-ID: <116DB56CD7DED511BC7800508B2CA537B002EC@mailsrvnt02.enet.sharplabs.com> Hi, Converted to PDF and posted at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.pdf Also, MS Word source (1.6MB) converted to ZIP (287KB) at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.zip Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Thursday, January 08, 2004 12:24 PM To: 'ps@pwg.org' Subject: PS> Updated PSI Specification wd-psi10-20040106 Availble Hey All... An updated PSI spec is available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040106.doc During next tuesday's teleconference, we will need to look at the ClientErrorAttributesOrValuesNotSupported exception, and figure out what to do with it now that we have an UnsupportedElements as an out parameter. Then, I think we will be done! Dave From imcdonald at sharplabs.com Tue Jan 13 10:39:28 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> Tue 13 Jan 11am EDT - PSI call today? Message-ID: <116DB56CD7DED511BC7800508B2CA537B00302@mailsrvnt02.enet.sharplabs.com> Hi, My notes say that we're having a PSI call in 20 minutes. Dave Hall got the updated spec out and our Formal Vote on requirements is now over. Talk to you all in 20 minutes, hopefully. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Monday, January 05, 2004 12:29 PM To: 'a PSI pwg.org' Subject: PS> [PSI] Tue 6 Jan 11am EDT This is the, Don't worry I'll send a reminder Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Review Last Call Comments ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 742065006 Meeting password: newpsi-1 Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Tue Jan 13 10:43:49 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: FW: PS> [PSI] Next Call 01/13/04 Message-ID: <7A371016E109114EA47C89370296278B2FD31F@xrose01.rose.hp.com> -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Monday, January 12, 2004 8:53 AM To: BERKEMA,ALAN C (HP-Roseville,ex1) Subject: RE: PS> [PSI] Next Call 01/13/04 Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) MRD Status - Doc Number 2) Review Spec ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 742065006 Meeting password: newpsi-1 Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Tue Jan 13 13:06:03 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI Update 01/13/2004 Message-ID: <7A371016E109114EA47C89370296278B2FD326@xrose01.rose.hp.com> Hi All, At today's call we resolved a couple of minor specification issues and talked about the status of the MRD. The MRD passed formal approval, 4 in favor, 1 abstain and 1 in favor a day after the deadline, can we count it? Jerry can you give me a document number? Then I will post the approved document. The technical specification will begin it's second Last Call today 01/13/2004 and will go for 4 weeks, ending 02/10/2004. On 02/17/2004 we will a teleconference to discuss comments. May have conference calls before the 17th if needed. On the afternoon of 02/23/2004 we will hold Comment Resolution meeting in San Jose. Thanks, Alan _____ Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company 916 785-5605 Phone aberkema@hp.com _____ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040113/2c79af47/attachment-0001.html From dhall at hp.com Tue Jan 13 16:10:38 2004 From: dhall at hp.com (HALL,DAVID (HP-Vancouver,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> Second Last Call Candidate Published... Message-ID: <4EB310FE4410BB4B8E981C67B275BC4F014736BA@xvan01.vcd.hp.com> Hey All.. The latest specification is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.doc ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.zip The technical specification will begin it's second Last Call today 01/13/2004 and will go for 4 weeks, ending 02/10/2004. On 02/17/2004 we will a teleconference to discuss comments. May have conference calls before the 17th if needed. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040113/2392d77b/attachment-0001.html From imcdonald at sharplabs.com Tue Jan 13 17:36:46 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> [PDF of] Second Last Call Candidate Published... Message-ID: <116DB56CD7DED511BC7800508B2CA537B00306@mailsrvnt02.enet.sharplabs.com> Hi, Converted to PDF (262KB) and now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.pdf MS Word source (1,616KB) packed into ZIP (290KB), as noted below in Dave's announcement. Dave - 'last call' notice (with an obvious subject) should be sent to PWG-Announce list, please. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall@hp.com] Sent: Tuesday, January 13, 2004 4:11 PM To: 'ps@pwg.org' Subject: PS> Second Last Call Candidate Published... Hey All.. The latest specification is now available at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.doc ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040113.zip The technical specification will begin it's second Last Call today 01/13/2004 and will go for 4 weeks, ending 02/10/2004. On 02/17/2004 we will a teleconference to discuss comments. May have conference calls before the 17th if needed. Dave From imcdonald at sharplabs.com Wed Jan 14 16:55:04 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: [Uri-review] SMB URI penultimate draft??? Message-ID: <116DB56CD7DED511BC7800508B2CA537B00307@mailsrvnt02.enet.sharplabs.com> Hi, Below is the link to the hopefully technically complete draft of the SMB URI scheme. Please take a look and see if you requirements are met. Note that PSI no longer defines a 'pwg-unc:' URI scheme, but instead refers to this standards track SMB URI scheme. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Christopher R. Hertel [mailto:crh@ubiqx.mn.org] Sent: Wednesday, January 14, 2004 12:28 AM To: Uri-review@ietf.org Subject: Re: [Uri-review] SMB URI penultimate draft??? Version 06 of the SMB URI draft is now available from the IETF webserver. http://www.ietf.org/internet-drafts/draft-crhertel-smb-url-06.txt My *plan* is: - to check for any IETF nits I didn't pick, - clean up a few organizational issues that have been pointed out already, - direct and star in an four-part TV mini-series adaptation of RFC2549. (Well, maybe not that last one.) I don't plan on making any further changes to the hard tofu core of the material unless someone finds something that I've missed that really needs fixing. 'Course, that can only happen if the draft gets read. ;) Anyway, the next thing after that is to start the process of moving the draft in the general direction of the RFC procesess. I'm sure that will be interesting too, but I'm looking foreward to it. I like learning new things. Thanks everyone. Chris -)----- -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- crh@ubiqx.mn.org OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@ubiqx.org _______________________________________________ Uri-review mailing list Uri-review@ietf.org https://www1.ietf.org/mailman/listinfo/uri-review From alan.berkema at hp.com Wed Feb 11 17:49:37 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> [PSI] 02/23/2004 F2F? Message-ID: <7A371016E109114EA47C89370296278B02B27935@xrose01.rose.hp.com> Hi All, Since the PSI spec is now in the Formal Vote phase, we don't need to meet to resolve ballot comments in the afternoon on Monday 23 February 2004. This leaves several possibilities for the use of the afternoon: 1) IPP FAX can use additional time 2) Harry may lead a brain storm to discuss ideas beyond PSI 1.0 3) Other PWG business 4) Catch up on e-mail 5) Visit San Jose I think it was wise to plan for Ballot Comment Resolution time, however, since there were no comments to resolve we need to revise the plan. Do we still want a call on 02/17/2004? What's on the agenda? Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: ??? From imcdonald at sharplabs.com Thu Feb 12 15:25:07 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> [PSI] 02/23/2004 F2F? Message-ID: Hi Alan, I think we should have at least a brief PSI call next Tuesday (17 February) to set PSI face-to-face agenda. And it's unlikely that IPPFAX needs extra time at face-to-face. Here's a proposed PSI face-to-face agenda: (30 min) Summary of PSI documents and status - requirements and protocol documents - how much prototyping has been done - solicit implementors for TBD future interoperability bakeoff (60 min) Tutorial on PSI interfaces and methods - some detail on every method - PSI now has functionality not present in IPP (elegant push and pull methods) - PSI/1.0 w/ SOAP over non-HTTP bindings (and interoperability) (15 min) BREAK (30 min) PSI input to WBMM on management methods - IPP-style job management methods? - Queue management methods? - PSI service management (install, startup)? - Accounting, billing, whatever? (30 min) PSI Working Group wrapup - unfinished work - review PSI charter for goals and objectives - PSI/1.0 Implementors Guide (out-of-date) - PSI Transform Interface definition Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Wednesday, February 11, 2004 5:50 PM To: 'a PSI pwg.org' Subject: PS> [PSI] 02/23/2004 F2F? Hi All, Since the PSI spec is now in the Formal Vote phase, we don't need to meet to resolve ballot comments in the afternoon on Monday 23 February 2004. This leaves several possibilities for the use of the afternoon: 1) IPP FAX can use additional time 2) Harry may lead a brain storm to discuss ideas beyond PSI 1.0 3) Other PWG business 4) Catch up on e-mail 5) Visit San Jose I think it was wise to plan for Ballot Comment Resolution time, however, since there were no comments to resolve we need to revise the plan. Do we still want a call on 02/17/2004? What's on the agenda? Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: ??? From alan.berkema at hp.com Thu Feb 12 16:35:17 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> [PSI] Next Call 02/17/04 Message-ID: <7A371016E109114EA47C89370296278B02C8939E@xrose01.rose.hp.com> Hey all, Even though Ira came up with some interesting agenda topics and it sounds fun, our Management team thinks PSI 1.0 is a done deal and unfortunately Dave & I can't justify travel. Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Talk about how we can address some of Ira's agenda items without a F2F ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 741467504 Meeting password: newpsi-99 Host: Alan Berkema 1(916)7855605 From imcdonald at sharplabs.com Fri Feb 13 15:38:02 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> [PSI] Next Call 02/17/04 Message-ID: Hi Alan, Sorry to hear about your travel restrictions...sigh... Could you and Dave attend by teleconference and cover some/most of these agenda topics? We actually placed this meeting in San Jose in hopes of having you guys attend a PSI/1.0 wrapup. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Thursday, February 12, 2004 4:35 PM To: 'a PSI pwg.org' Subject: PS> [PSI] Next Call 02/17/04 Hey all, Even though Ira came up with some interesting agenda topics and it sounds fun, our Management team thinks PSI 1.0 is a done deal and unfortunately Dave & I can't justify travel. Teleconference details: NEXT: Tuesday Time: 8:00AM (US PDT) Number: 866-639-4738 Participant PIN: 7855605 If Trouble with Above Try: Toll Access Number: 574-935-6700 Participant PIN: 7855605 Agenda: 1) Talk about how we can address some of Ira's agenda items without a F2F ----------------- 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: http://hp.webex.com/ Then click New User. ------------------------- MEETING SUMMARY ------------------------- Name: PSI Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada Meeting number: 741467504 Meeting password: newpsi-99 Host: Alan Berkema 1(916)7855605 From alan.berkema at hp.com Tue Feb 17 17:01:15 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> [PSI] 02/23/2004 F2F Agenda Message-ID: <7A371016E109114EA47C89370296278B02E23FA3@xrose01.rose.hp.com> Ira, can you send this to announce with updated comments and dial in number - Thanks Alan PSI Folks, Please look at this agenda and provide suggestions Thanks to Ira a for the first pass Here's a proposed PSI face-to-face agenda: (30 min) Summary/Overview of PSI: Leader Alan - requirements and protocol documents - how much prototyping has been done - solicit implementors for TBD future - interoperability bakeoff - state of PSI where is it in the technology adoption cycle (30 min) What's new in PSI - It's not just for Mobility: Alan - PSI now has functionality not present in IPP (elegant push and pull methods): Ira - PSI/1.0 w/ SOAP over non-HTTP bindings (and interoperability): Ira (15 min) BREAK (30 min) PSI input to WBMM on management methods - Open Ended Brain Storm: Leader Ira/Harry - What needs to managed in a PS - IPP-style job management methods? - Queue management methods? - PSI service management (install, startup)? - Accounting, billing, whatever? (30 min) PSI Working Group Wrapup and Future - review PSI charter for goals and objectives: Alan - PSI/1.0 Implementors Guide (out-of-date): Needs Owner - PSI Transform Interface definition: Harry Times may be slightly longer regards, Alan From alan.berkema at hp.com Mon Feb 23 17:23:00 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI Slides for 2/23 Message-ID: <7A371016E109114EA47C89370296278B02F9105B@xrose01.rose.hp.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: psi_san_jose.pdf Type: application/octet-stream Size: 21682 bytes Desc: not available Url : http://www.pwg.org/archives/ps/attachments/20040223/b66ea0eb/psi_san_jose-0001.obj From alan.berkema at hp.com Tue Feb 24 15:20:34 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI Next Steps & New Mtg Time Message-ID: <7A371016E109114EA47C89370296278B02F9158A@xrose01.rose.hp.com> Hi all, Please provide input on your choice for a new meeting time going forward Tuesday 9, 16, & 23 at 10:00AM or 2:00PM Pacific Time Primary goal is to clean up the implementers guide. Also, please vote on the PSI spec. I still believe that a Candidate, that is an interim spec. anyway, with a forward reference to a WSDL to be defined later, is preferable to a spec in limbo. If you vote No, then I think you should be in charge of writing the new WSDL :-) Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040224/0d8869f5/attachment-0001.html From imcdonald at sharplabs.com Tue Feb 24 15:25:09 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI Next Steps & New Mtg Time Message-ID: Hi Alan, I prefer the earlier time, but both work OK for me. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan.berkema@hp.com] Sent: Tuesday, February 24, 2004 3:21 PM To: a PSI pwg.org Subject: PS> PSI Next Steps & New Mtg Time Hi all, Please provide input on your choice for a new meeting time going forward Tuesday 9, 16, & 23 at 10:00AM or 2:00PM Pacific Time Primary goal is to clean up the implementers guide. Also, please vote on the PSI spec. I still believe that a Candidate, that is an interim spec. anyway, with a forward reference to a WSDL to be defined later, is preferable to a spec in limbo. If you vote No, then I think you should be in charge of writing the new WSDL :-) Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040224/971342a1/attachment-0001.html From PZehler at crt.xerox.com Wed Feb 25 08:49:51 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: Re: PWG-ANNOUNCE> Formal Vote on CR specifications Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9E52@CRTE128> -----Original Message----- From: Zehler, Peter Sent: Wednesday, February 25, 2004 8:48 AM To: 'a.s.patel@ieee.org' Cc: 'alan_berkema@hp.com'; 'aberkema@hp.com'; 'psi@pwg.org' Subject: Re: PWG-ANNOUNCE> Formal Vote on CR specifications All, Since the WSDL is out of date and out of spec and (to my knowledge) there is no immediate need for the specification, I would prefer that the WSDL be brought up to date before publishing the specification. Therefore Xerox votes NO on this specification at this time. Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040225/0c9bb830/attachment-0001.html From alain at ussj.ricoh.com Wed Feb 25 17:05:06 2004 From: alain at ussj.ricoh.com (Alain Regnier) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI WSDL files Message-ID: <8B8709E6C8B8784583FA9C7C013CB4514833@etd1.etd.ussj.ricoh.com> All, Following our discussion at the PSI face to face, I've included a non exhaustive list of issues with the current WSDL files: * In the "JobControlInterface" WSDL file (Apr. 11,2003), there are no descriptions about the following methods SetJobElements SetDocumentElements FetchDocumentDataByPull PullDocumentDataFetched FetchDocumentDataByValue * In the "QueryEndPointsInterface" WSDL file (Apr. 11,2003), there is a restriction about interface names when querying about information of an interface. (That is shown as "InterfaceIdentifierNameWKV" in the file.) So we have to select an interface name among "JobContorlInterface", "ServiceCapabilitiesInterface", and "TargetDeviceSupportInterface". But in the specification (Jan. 13,2004) there is the description at Page 19 ("5.3 QueryEndPointsInterface") as follows. "Vendor can define their own interface names and namespaces." * Basic Profile The PSI specification violates WS-I Basic Profile 1.0 (http://www.ws-i.org/Profiles/Basic/2003-01/BasicProfile-1.0-WGAD.html). All http://www.pwg.org/schemas/ps/latest/*.wsdl do not follow the following BP 1.0 rule: R2716 A document-literal binding in a DESCRIPTION MUST NOT have the namespace attribute specified on contained soapbind:body, soapbind:header, soapbind:headerfault and soapbind:fault elements. The solution is simple: removing the namespace attribute specified on wsdlsoap:body elements. "QuerySupportedInterfaces" Returns: interfaceIdentifiers: InterfaceIdentifierContainer 'interfaceIdentifier' WSDL(2003/04/11) "name" "namespace" "version" "dataModel" >>>> "secure" xsd:boolean Specification(2004/01/13) cf. P.84 [7.4 InterfaceIdentifier] "name" "namespace" "version" "dataModel" >>>> "sec" [none, ssl3, tls] >>>> "auth" [none, login, basic, digest, certificate] ------------------------------- "GetTargetDeviceElements" Parameters: WSDL(2003/04/11) targetDeviceIdentifier:URI >>>> requestedElements:Printer Specification(2004/01/13) cf. P.23 targetDeviceIdentifier:URI >>>> requestedPrinterElements:RequestedElements ------------------------------- "CreateJob" Parameters: WSDL(2003/04/11) targetDeviceIdentifier:URI >>>> deliverToTargetDevice:Boolean >>>> requestedTargetDeviceDataType:DocumentDescription jobDescription:JobDescription jobProcessing:JobProcessing defaultDocumentProcessing:DocumentProcessing Specification(2004/01/13) cf. P.31 targetDeviceIdentifier:URI >>>> autoSelectTargetDevice:Boolean >>>> requestedTargetDeviceDataType:DocumentFormatDetails jobDescription:JobDescription jobProcessing:JobProcessing defaultDocumentProcessing:DocumentProcessing Returns: WSDL(2003/04/11) jobURI:URI unsupportedElements:UnsupportedElements Specification(2004/01/13) cf. P.31 jobURI:URI unsupportedElements:UnsupportedElements >>>> targetDeviceIdentifierAutoSelect:Boolean ------------------------------- "PushDocumentDataDelivered" Parameters: WSDL(2003/04/11) >>>> documentURI:URI dataSinkURI:URI Specification(2004/01/13) cf. P.38 >>>> jobURI:URI >>>> documentNumber:int dataSinkURI:URI >>>> documentOctetsSent:long ------------------------------- "GetJobs" Parameters: WSDL(2003/04/11) jobFilterElements:Job >>>> requestedElements:Job >>>> myJobs:Boolean >>>> whichJobs:WhichJobsWKV limit:int Specification(2004/01/13) cf. P.41 jobFilterElements:Job >>>> requestedJobElements:RequestedElements limit:int Returns: WSDL(2003/04/11) >>>> Job:Job Specification(2004/01/13) cf. P.41 >>>> jobs:JobContainer >>>> callbackInterval:uint32 >>>> unsupportedElements:UnsupportedElements ------------------------------- "GetDocuments" Parameters: WSDL(2003/04/11) jobURI:URI documentFilterElements:Document >>>> requestedElements:Job Specification(2004/01/13) cf. P.46 jobURI:URI documentFilterElements:Document >>>> requestedDocumentElements:RequestedElements Returns: WSDL(2003/04/11) >>>> Document:Document Specification(2004/01/13) cf. P.46 >>>> documents:DocumentContainer >>>> callbackInterval:uint32 >>>> unsupportedElements:UnsupportedElements Thanks, Alain Regnier Ricoh -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040225/78d0d018/attachment-0001.html From PZehler at crt.xerox.com Wed Feb 25 18:20:37 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:20 2009 Subject: PS> Formal Vote on PSI specifications Message-ID: <81FE58FCC6748A4A915BDDCACA900C8309DEBF@CRTE128> Ami, Just to be clear, Xerox votes NO with strong objection on the Print Service Interface Specification for the reasons stated below. Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: Zehler, Peter Sent: Wednesday, February 25, 2004 8:48 AM To: 'a.s.patel@ieee.org' Cc: 'alan_berkema@hp.com'; 'aberkema@hp.com'; 'psi@pwg.org' Subject: Re: PWG-ANNOUNCE> Formal Vote on CR specifications All, Since the WSDL is out of date and out of spec and (to my knowledge) there is no immediate need for the specification, I would prefer that the WSDL be brought up to date before publishing the specification. Therefore Xerox votes NO on this specification at this time. Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040225/a53d7117/attachment-0001.html From alan.berkema at hp.com Mon Mar 8 15:25:39 2004 From: alan.berkema at hp.com (BERKEMA,ALAN C (HP-Roseville,ex1)) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI Next Steps & New Mtg Time Message-ID: <7A371016E109114EA47C89370296278B035543F9@xrose01.rose.hp.com> Hi all, PSI activities will be placed on hold until we get a chance to revise the WSDL. Since many of you felt strongly that up to date WSDL is required, we will send you the new version when it becomes available, so that you can verify it with your toolkits to improve the quality. Thanks, Alan _____ From: owner-ps@pwg.org [mailto:owner-ps@pwg.org] On Behalf Of BERKEMA,ALAN C (HP-Roseville,ex1) Sent: Tuesday, February 24, 2004 12:21 PM To: a PSI pwg.org Subject: PS> PSI Next Steps & New Mtg Time Hi all, Please provide input on your choice for a new meeting time going forward Tuesday 9, 16, & 23 at 10:00AM or 2:00PM Pacific Time Primary goal is to clean up the implementers guide. Also, please vote on the PSI spec. I still believe that a Candidate, that is an interim spec. anyway, with a forward reference to a WSDL to be defined later, is preferable to a spec in limbo. If you vote No, then I think you should be in charge of writing the new WSDL :-) Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/ps/attachments/20040308/10c830c1/attachment-0001.html From imcdonald at sharplabs.com Tue Apr 6 13:58:09 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: PWG Events Schema and standard names Message-ID: Oops - wrong address before. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira Sent: Tuesday, April 06, 2004 1:55 PM To: 'psi@pwg.org'; 'wbmm@pwg.org' Subject: PWG Events Schema and standard names Hi, Last week at the PWG Process telecon, I mentioned our discovery that there are four methods in PSI/1.0 that reference the 'NotifyEvents' element (a member of the Subscription object) in the PWG Semantic Model. But, the Semantic Model has no IETF or PWG working draft content in it, including the former IPP Notifications spec. There are three alternatives (we decided on the third): (1) - Delete the PS's response parameter from RegisterTargetDevice for subscription to events; - Delete the Send[Printer|Job|Document]Notification methods entirely; [lost functionality in PSI/1.0 spec] (2) - Advance the entire IPP Notifications spec with the complex semantics of the Subscription and Notification objects to become a IEEE/ISTO PWG Candidate Standard; - Revise PWG Semantic Model to include these objects; [probably one calendar year - stalls PSI/1.0 spec] (3) - Develop a PWG Events schema that defines 'NotifyEvents' as a union of 'PrinterEvents', 'JobEvents', and 'DocumentEvents' (consider adding fine-grained events from Printer MIB alert list at the same time) - Develop an IEEE/ISTO PWG Standard Event Names Candidate Standard - Revise PSI/1.0 to reference the Events schema to be added to PWG Semantic Model/1.1 [hopefully 3 to 6 months] WBMM has an immediate and pressing need for this same 'NotifyEvents' element for their existing Action 'SubscribeForAlerts' and their existing operation 'SendAlert' (needs in-progress Alert schema). I volunteer to create this Events schema and (with help from someone MS Word literate) write the working draft for the companion PWG Standard Event Names spec. Alan - you may wish to schedule some Tuesday PSI telecons to review and advance this work. Bill Wagner agreed that we should also spend WBMM telecon time, but we have a lot of other (unrelated) new WBMM content to work on too. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Sun Apr 11 13:45:50 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> Posted PROTOTYPE Events XML Schema v0.10 (11 April 2004) Message-ID: Hi folks, Sunday (11 April 2004) [For use by Masanori Itoh (Ricoh) and Dave Hall (HP) in updating WSDL files for PSI/1.0, as agreed at PWG Process telecon on 1 April 2004] I have just posted a prototype Events XML Schema v0.10, which validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator) and is posted at: ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/events-20040411.xsd This schema defines 8 event classes: - VendorEvents - for vendor extensions, including new event classes - SystemEvents - derived from PrinterEvents below - ServiceEvents - derived from PrinterEvents below - DeviceEvents - derived from PrinterEvents below - PrinterEvents - derived from IPP System Admin, w/ PSI/IPPFAX additions - JobEvents - derived from IPP System Admin, w/ PSI/IPPFAX additions - DocumentEvents above - derived from JobEvents above - ComponentEvents - derived from PrtAlertCodeTC in Printer MIB v2 The included extensions for use by PSI/1.0 are: - PrinterStateOnlyChanged - ignores state reasons transitions - JobStateOnlyChanged - ignores state reasons transitions - DocumentStateOnlyChanged - ignores state reasons transitions The included extensions for use by IPPFAX/1.0 are: - JobError - see 'errors-count' in section 5.1.1 [PWG5100.7] - JobWarning - see 'warnings-count' in section 5.1.4 [PWG5100.7] Below are some excerpts. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [excerpts from Events Schema] ... ... ... From imcdonald at sharplabs.com Mon Apr 26 14:51:52 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: [asn1xml] New XSD to ASN.1 conversion tool on the ASN.1 websi te Message-ID: Hi folks, FYI - below is a tool that converts W3C XML Schema documents into ISO/ITU-T X.694 compliant ASN.1 schema. Sun and other middleware vendors plan to enhance their middleware to send ONLY ASN.1 encoded schema and instances over the wire (to improve performance and interoperability). Sun has already benchmarked 20-to-1 performance improvements over the wire with XML Schema instances converted to ASN.1. This tokenization is comparable to the WAP-defined tokenization currently done for wireless access to HTML-based web pages. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Olivier Dubuisson [mailto:Olivier.Dubuisson@francetelecom.com] Sent: Saturday, April 17, 2004 1:07 PM To: asn1xml@oss.com Subject: [asn1xml] New XSD to ASN.1 conversion tool on the ASN.1 website The ASN.1 information website announces the availability of xsdasn1, a new XSD to ASN.1 conversion tool at http://asn1.elibel.tm.fr/xsdasn1 This tool, contributed by OSS Nokalva, converts XML Schemas to ASN.1 modules, as specified in ITU-T Rec. X.694 | ISO/IEC 8825-5 at http://www.itu.int/ITU-T/studygroups/com17/languages/ The xsdasn1 tool replaces the previously available, but now outdated, prototype developed by France Telecom R&D to help develop the X.694 standard. The web interface for this tool is quite new, so please accept our apologies in case of any problems. We'll do our best to correct the bugs ASAP. -- Olivier DUBUISSON france telecom R&D DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/ From imcdonald at sharplabs.com Fri May 14 11:40:01 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: WBMM> Bug in PSI UnsupportedElements return Message-ID: Oops - I sent to wrong address for PSI list. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, May 13, 2004 11:08 AM To: 'psi@pwg.org'; 'wbmm@pwg.org' Cc: 'HALL,DAVID (HP-Vancouver,ex1)'; 'BERKEMA,ALAN C (HP-Roseville,ex1)'; 'Masanori ITOH' Subject: WBMM> Bug in PSI UnsupportedElements return Importance: High Hi, [Background - WIMS folks want to include UnsupportedElements in the returns from most of their Operations and Actions - so we reviewed the PSI definition yesterday afternoon.] PSI has the OPPOSITE behavior for elements which ARE supported but have been supplied by the client with an unsupported VALUE. PSI returns the element with the _new_ substituted value. But - IPP/1.1 and the PWG Semantic Model/1.0 UnsupportedElements return the element with the _old_ unsupported value (perhaps more sensible, but less useful to the client). Pete Zehler was on the WIMS telecon yesterday and agrees that we should _fix_ this bug in PSI (because it's impossible to write a print service gateway between the two different behaviors). WIMS folks also decided to define a second SubstitutedElements return that has the _new_ value for client convenience (the present mistaken behavior in PSI UnsupportedElements). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Thu May 20 13:01:50 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: For revision of PSI specification document (2004/01/13) Message-ID: Hi folks, Here are some excellent corrections for the PSI/1.0 spec from Masanonri Itoh (Ricoh). Alan has asked Dave Hall to add them in the re-vote revision of PSI/1.0 (after WSDL is completed and PWG Standard Imaging System Events is completed). Cheers, - Ira -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From alan.berkema at hp.com Tue May 25 13:06:31 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:20 2009 Subject: PS> Important PSI Teleconference 5/26/04 at 2:00PM Message-ID: Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Fri May 28 10:00:40 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> RE: Important PSI Teleconference 5/26/04 at 2:00PM Message-ID: Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From alan.berkema at hp.com Fri May 28 12:27:24 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:20 2009 Subject: PS> RE: Important PSI Teleconference 5/26/04 at 2:00PM Message-ID: Ira, Thanks for providing this excellent summary. Can we include this in the official minutes? Jerry or Bill? Alan -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Friday, May 28, 2004 7:01 AM To: 'Masanori ITOH'; Berkema, Alan C (R&D Roseville); 'ps@pwg.org' Cc: Hall, David M; Alain Regnier Subject: RE: Important PSI Teleconference 5/26/04 at 2:00PM Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Mon May 31 14:28:19 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> Posted Print-only Events spec and schema (31 May 2004) Message-ID: Hi folks, Monday (31 May 2004) [For review on the PSI mailing list and prompt PWG 'last call'] I've posted a PWG Standard Print System Events v1.0 draft at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psievents10-20040531.htm I've also posted the revised Events XML Schema v0.30, which validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator, at: ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/events-20040531.xsd Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [change log] (1) Deleted the Device, Resource, Service, and System event classes from both Events spec and Events schema, per PWG Vancouver (May 2004). (2) Changed all references from PWG Imaging System Model draft to PWG Semantic Model/1.0 in Events spec, per PWG Vancouver (May 2004). (3) Changed all references from PWG Standard Imaging System Events draft to PWG Standard Print System Events draft in Events schema, per PWG Vancouver (May 2004). ------------------------------------------------------------------------ From imcdonald at sharplabs.com Mon Jun 21 12:24:03 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI stable copy of Events schema v0.40 (21 June 2004) Message-ID: Hi folks, Monday (21 June 2004) I just posted in the PSI working group directory tree an otherwise unchanged Events XML Schema v0.40, which validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator, at: ftp://ftp.pwg.org/pub;/pwg/ps/schemas/events-20040621.xsd This schema in the PSI working group directory tree is intended to accompany the PWG Standard Print System Events v1.0 draft at: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psievents10-20040531.htm Cheers, - Ira PS - The WIMS working group will continue to develop an expanded version of the Events schema in the separate WIMS working group directory tree, to facilitate early prototyping of Service and Device generic events and the addition of the Subscription and Resource object events (as requested in PWG Vancouver in May). Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.30 to v0.40] (1) Changed date of file and posted in PSI directory tree. ------------------------------------------------------------------------ From alan.berkema at hp.com Tue Jun 22 12:21:07 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI: Teleconference July 06 @ 8:00AM Message-ID: Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From thrasher at lexmark.com Tue Jun 22 12:44:45 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:20 2009 Subject: PS> FYI...Latest updated PSI Specification and discussion email. Message-ID: ----- Forwarded by Jerry Thrasher/Lex/Lexmark on 06/22/2004 12:35 PM ----- FYI.... Here's the list that Alan mentions in the agenda for the PSI call (slightly edited from the note I sent Alan) An updated PSI working draft is available on the PWG's FTP site. ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040615.pdf and doc You can turn changes on in the doc file to see the extent of my changes, I accepted all accrued changes that happened before the last vote. Besides what shows up in the doc file change log, I highlighted a couple of places that need to be discussed... 1. Section 5.3.2 and 5.3.3, There is a normative definition of the "interfaceIdentifier" to the QueryEndPointsInterface.wsdl (the problem is that if the wsdl is informative, then this needs to be defined in the specification itself.......) 2. Section 5.5.8, 5.5.9, 5.5.12, 5.5.13, 5.6.2, 5.6.4, and 5.6.6, refer the defn. of callbackInterval to the IPP Get Specification. (it's not listed in either normative or informative references.....) 3. Section 5.6.7...The conformance requirements of the eventNumber parameter in the SendJobNotification method were never defined (although it was defined for SendDocumentNotification)...(I added it and highlighted it..) 4. Section 5.6.11...The conformance requirements of the eventID parameter in the SentTargetDeviceNotification method were never defined (and why isn't it eventNumber like for SendJobNotification and SendDocumentNotification???) (I added it and highlighted it...) 5. Normative References....I'm not sure either WS-Addressing or WS-Security are to what would be the equivalent of candidate standard in their respective standards groups...(WSI)??..however WSDL 1.1 is only a W3C Note and not a Recommendation anyway. Also, I removed the references to WSDL 1.2 because there will never be any such thing. The WSDL 2.0 language specifications are scheduled to be Last Called in the W3C at the end of July, 2004. WSDL 2.0 has a completely different syntax than the WSDL 1.1 note. 6.Section 5.5.12...The conformance requirements of the documentFilterElements parameter are not defined.... I also made all of Mr. Masanori Itoh's requested changes. I assumed he was correct in the mandated exception to be thrown in the case of invalid document format request was indeed ClientErrorAttributesOrValuesNotSupported and not ProcessingRequestUnsupported..... ----- Forwarded by Jerry Thrasher/Lex/Lexmark on 06/15/2004 02:42 PM ----- From imcdonald at sharplabs.com Tue Jun 22 17:18:48 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FYI...Some notification edits for PSI spec Message-ID: Hi, These are the event edits referred to in Alan's announcement of a PSI telecon on 6 July. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira Sent: Monday, June 21, 2004 4:59 PM To: 'Hall, David M'; McDonald, Ira; thrasher@lexmark.com; Berkema, Alan C (R&D Roseville) Subject: RE: Some notification edits for PSI spec Hi Dave, A newer wrinkle. The enumerated type 'PrinterEventType' only defines the few standard Printer events. But the element 'PrinterEvents' is a choice of 'PrinterEventType' and 'VendorEventType'. Likewise for Jobs and Documents. See - I was thinking ahead... Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Hall, David M [mailto:dhall@hp.com] Sent: Monday, June 21, 2004 3:54 PM To: McDonald, Ira; thrasher@lexmark.com; Berkema, Alan C (R&D Roseville) Subject: RE: Some notification edits for PSI spec Thanks Ira! D -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Monday, June 21, 2004 11:13 AM To: 'thrasher@lexmark.com'; Berkema, Alan C (R&D Roseville); Hall, David M Cc: McDonald, Ira Subject: Some notification edits for PSI spec Hi Dave and Alan, Monday (21 June 2004) [Background - Alan and I agree that we need a new 'last call' for PSI spec, because there are technical errors in the current PSI spec]. Below are some notification changes for the PSI spec. Comments? Cheers, - Ira ------------------------------------------------------------------------ [changes for 'wd-psi10-20040615.pdf'] (1) Section 5.6.2 FetchNextJob - 'sendJobNotifications' - method signature is correct, but... - in 'Returns' section, should CHANGE definition to "A collection of Job Events as defined by the JobEvents element in the Semantic Model [SM] Events.xsd." (2) Section 5.6.2 FetchNextJob - 'callBackInterval' - in 'Returns' section, should ADD definition (_not_ from IETF stalled IPP Get spec) and this element should occur ONLY in PSI WSDL (because we are _not_ adding Subscription object to Semantic Model for PSI). - otherwise, we should DELETE 'callBackInterval' (3) Section 5.6.4 FetchNextDocmentByPull - 'sendDocumentNotifications' - method signature is correct, but... - in 'Returns' section, should CHANGE definition to "A collection of Document Events as defined by the DocumentEvents element in the Semantic Model [SM] Events.xsd." (4) Section 5.6.4 FetchNextDocmentByPull - 'callBackInterval' - see item (2) above. (5) Section 5.6.6 FetchNextDocmentByValue - 'sendDocumentNotifications' - see item (3) above. (6) Section 5.6.6 FetchNextDocmentByValue - 'callBackInterval' - see item (2) above. (7) Section 5.6.7 SendJobNotification - in method signature, should ADD the missing parameter "sendJobNotifications : JobEvents" (existing JobStatus group does NOT include Job Events) - in 'Parameters' section, should ADD the parameter and definition "A collection of Job Events as defined by the JobEvents parameter in the Semantic Model [SM] Events.xsd." (8) Section 5.6.8 SendDocumentNotification - in method signature, should ADD the missing parameter "sendDocumentNotifications : DocumentEvents" (existing DocumentStatus group does NOT include Document Events) - in 'Parameters' section, should ADD the parameter and definition "A collection of Document Events as defined by the DocumentEvents parameter in the Semantic Model [SM] Events.xsd." (9) Section 5.6.9 RegisterTargetDevice - 'sendTargetDeviceNotifications' - in method signature, should CHANGE definition to "sendTargetDeviceNotifications : NotifyEvents" (to allow subscription for Job and Document events too) - in 'Returns' section, should CHANGE definition to "A collection of Printer, Subunit, Job, Document, and Vendor Events as defined by the NotifyEvents element in the Semantic Model [SM] Events.xsd." (10) Section 5.6.11 SendTargetDeviceNotification - in method signature, should ADD the missing parameter "sendTargetDeviceNotifications : NotifyEvents" (existing PrinterStatus group does NOT include Printer Events) - in 'Parameters' section, should ADD the parameter and definition "A collection of Printer, Subunit, and Vendor Events as defined by the NotifyEvents element in the Semantic Model [SM] Events.xsd. The SendTargetDeviceNotification method MUST NOT be used to deliver Job or Document level events." ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Fri Jul 2 05:40:58 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:20 2009 Subject: PS> Re^2: Important PSI Teleconference 5/26/04 at 2:00PM In-Reply-To: References: Message-ID: <200407020940.AA00746@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From ito at src.ricoh.co.jp Fri Jul 2 06:27:53 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:20 2009 Subject: PS> PSI: Teleconference July 06 @ 8:00AM In-Reply-To: References: Message-ID: <200407021027.AA00747@macbeth.src.ricoh.co.jp> Hi Mr. Berkema, How the problem of 'UnsupportedElements' was solved ? (Changed to follow with the thought of IPP/1.1 and the Semantic Model/1.0 ?) Was that matter discussed ? If not, add it to agenda, please. If I was going through old mail, I apologize. And I'm glad to add the 'Namespace' matter of Events schemas that I mentioned in the mail to Mr. McDonald, too. Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------------------------ Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 22 Jun 2004 09:21:07 -0700 Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From imcdonald at sharplabs.com Mon Jul 5 13:08:59 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> Reminder - PSI: Teleconference July 06 @ 8:00AM Message-ID: Hi, Just a reminder that we have an important PSI telecon tomorrow. Added to Alan's agenda are Masanori Itoh's two subsequent topics: (1) The target namespace for Events schema --> PWG Semantic Model/1.0 (2) PSI behavior for 'UnsupportedElements' --> PWG SM and IPP alignment Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Tuesday, June 22, 2004 12:21 PM To: a PSI pwg.org Subject: PS> PSI: Teleconference July 06 @ 8:00AM Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From ito at src.ricoh.co.jp Wed Jul 7 04:19:59 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:20 2009 Subject: Re^2: PS> [UnsupportedElements fix] PSI: Teleconference July 06 @ 8 :00AM In-Reply-To: References: Message-ID: <200407070819.AA00752@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm sorry for my late reply again. I had made a business trip for several days and could not be checking emails while I was away. I understand your comment. But I guess it is kind for PSI Client to return the element with 'True' (supported) value in the PSI response like the present PSI specification .... Because the Client can not get any information in the PSI response, only get the fault. But I can understand PSI is good to be in accordance with other standards, too. Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:05:49 -0700 Hi, The faulty PSI definition of UnsupportedElements will be changed to the actual IPP/Semantic Model/WIMS common semantics, i.e., if a an element is supported but the specified value is not supported, then the element is returned with original (unsupported) value in the PSI response. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 6:28 AM To: Berkema, Alan C (R&D Roseville) Cc: Alain Regnier; McDonald, Ira; a PSI pwg.org Subject: Re: PS> PSI: Teleconference July 06 @ 8:00AM Hi Mr. Berkema, How the problem of 'UnsupportedElements' was solved ? (Changed to follow with the thought of IPP/1.1 and the Semantic Model/1.0 ?) Was that matter discussed ? If not, add it to agenda, please. If I was going through old mail, I apologize. And I'm glad to add the 'Namespace' matter of Events schemas that I mentioned in the mail to Mr. McDonald, too. Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------------------------ Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 22 Jun 2004 09:21:07 -0700 Title: PSI Updates Time: Tuesday, July 06, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Review/resolve defects Jerry identified 2) Add event enhancements Ira identified 3) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=G5TE67YW7 Participant: https://www.hpe-learning.com/attend/default.aspx?key=UUFRRB8LX To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From ito at src.ricoh.co.jp Wed Jul 7 05:06:08 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:20 2009 Subject: PS> Re^2: [Std Print System Events namespace] In-Reply-To: References: Message-ID: <200407070906.AA00754@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm sorry to send my comment after PSI telecon. I'm worry whether some problems will occur when some Event schemas will be extended and be formally added to the Semantic Models. (That will be the schemas before you reduced for PSI.) Will the version of namespace be changed at that time ? I'm not sure whether problems will occur .... If there is no problem, I agree with you. Please add the namespace definition of SM/1.0 as 'targetNamespace' in the schema file, or the schemas are in PSI namespace when imported in WSDLs. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700 Hi, [By the way, Jerry Thrasher has offered to convert my draft Std Print System Events from HTML to Word - thanks, Jerry!] The namespace will be PWG Semantic Model/1.0, just like all currently approved schemas. The internal version tag will be 1.x (something), but that's _not_ the namespace. So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents' elements can be referenced and used normally by PSI/1.0. _AFTER_ the Events spec and schema are formally approved (as PWG Candidate Standards), a copy of Events schema will be stored in the official directory: http://www.pwg.org/schemas/sm/1.0/ OK? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 5:41 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Wed Jul 7 10:30:23 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> RE: Re^2: [Std Print System Events namespace] Message-ID: Hi, The 'targetNamespace' version will NOT change. It will be fixed in all PWG approved schemas to SM/1.0. I'm now making minor editorial fixups to the Events schema for PSI, and have revised the initial schema element to the following: The version attribute (currently omitted) in the 'xsd:schema' element does NOT change the target namespace. It's internal documentation only. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, July 07, 2004 5:06 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: [Std Print System Events namespace] Hi Mr. McDonald, I'm sorry to send my comment after PSI telecon. I'm worry whether some problems will occur when some Event schemas will be extended and be formally added to the Semantic Models. (That will be the schemas before you reduced for PSI.) Will the version of namespace be changed at that time ? I'm not sure whether problems will occur .... If there is no problem, I agree with you. Please add the namespace definition of SM/1.0 as 'targetNamespace' in the schema file, or the schemas are in PSI namespace when imported in WSDLs. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700 Hi, [By the way, Jerry Thrasher has offered to convert my draft Std Print System Events from HTML to Word - thanks, Jerry!] The namespace will be PWG Semantic Model/1.0, just like all currently approved schemas. The internal version tag will be 1.x (something), but that's _not_ the namespace. So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents' elements can be referenced and used normally by PSI/1.0. _AFTER_ the Events spec and schema are formally approved (as PWG Candidate Standards), a copy of Events schema will be stored in the official directory: http://www.pwg.org/schemas/sm/1.0/ OK? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 5:41 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Wed Jul 7 14:20:19 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> Minutes of PSI telecon on 6 July Message-ID: Hi, Comments or corrections are welcome. (1) target namespace will be added to Events schema of PWG Semantic Model/1.0, e.g., (2) UnsupportedElements will be corrected to be defined the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) (consistent semantics and interworking of gateways) (3) Jerry Thrasher's issues in latest draft: 3.1 interfaceIdentifier will be defined in PSI spec, to avoid normative dependency on WSDL 3.2 callbackInterval will be defined in to PSI spec, to avoid normative dependency on IPP GET (and conformance requirement vis-a-vis Job History time will be removed, due to weak rationale) 3.3 eventNumber parameter SHOULD be renamed (to align with WIMS and IPP) to notifySequenceNumber ** DAVE ** I just found a bug in our definition below ** Since SendXxxNotification methods can transfer one or _more_ events in a single notification, the correct semantic is that the renamed parameter is the number of this notification message (NOT the number of one of the events in the message). 3.4 eventID in section 5.6.11 will replaced with the correct notifySequenceNumber 3.5 normative references - moved WS-Addressing and WS-Security to informative - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the normative references and will add the phrase "defacto industry standard" (because all existing tools only support these defacto standards - very little support for SOAP/1.2 has been shipped or deployed - no support for the future _incompatible_ WSDL/2.0 has been shipped) 3.6 documentFilterElements will be marked OPTIONAL 3.7 all of Masanori Itoh's suggested changes were also made by Jerry Thrasher and approved in the telecon 4. Ira McDonald's changes for events: 4.1 JobEvents definition will be corrected in FetchNextJob 4.2 callbackInterval - see 3.2 above FetchNextJob 4.3 DocumentEvents definition will be corrected in FetchNextDocumentByPull 4.4 callbackInterval - see 3.2 above FetchNextDocumentByPull 4.5 DocumentEvents - see 4.3 above FetchNextDocumentByValue 4.6 callbackInterval - see 3.2 above FetchNextDocumentByValue 4.7 JobEvents (missing parameter) will be added to SendJobNotification 4.8 DocumentEvents (missing parameter) will be added to SendDocumentNotifications 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice 4.10 SubunitEvents and VendorEvents (missing parameters) will be added (in addition to existing PrinterEvents) to SendTargetDeviceNotification (to add support for detailed Subunit events such as 'InputMediaSupplyLow' and Vendor events from different non-Printer objects) (5) ** Significant Change ** 5.1 Entire current Std Print System Events spec will be incorporated as an appendix into the PSI spec (to avoid new normative dependencies for PSI) 5.2 At some future date, a PWG Std Imaging System Events spec may be developed as a PWG 'dictionary' standard (6) ** Last Call ** - PSI/1.0 and Events schema will enter PWG 'last call' no later than 26 July, to complete at the PWG Plenary on Wednesday 18 August in Montreal Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From ito at src.ricoh.co.jp Fri Jul 9 03:42:26 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:20 2009 Subject: PS> Re^4: [Std Print System Events namespace] In-Reply-To: References: Message-ID: <200407090742.AA00758@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I understand your comment. Thanks for your revising works. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr McDonald, Ira wrote on Wed, 7 Jul 2004 07:30:23 -0700 Hi, The 'targetNamespace' version will NOT change. It will be fixed in all PWG approved schemas to SM/1.0. I'm now making minor editorial fixups to the Events schema for PSI, and have revised the initial schema element to the following: The version attribute (currently omitted) in the 'xsd:schema' element does NOT change the target namespace. It's internal documentation only. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, July 07, 2004 5:06 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: [Std Print System Events namespace] Hi Mr. McDonald, I'm sorry to send my comment after PSI telecon. I'm worry whether some problems will occur when some Event schemas will be extended and be formally added to the Semantic Models. (That will be the schemas before you reduced for PSI.) Will the version of namespace be changed at that time ? I'm not sure whether problems will occur .... If there is no problem, I agree with you. Please add the namespace definition of SM/1.0 as 'targetNamespace' in the schema file, or the schemas are in PSI namespace when imported in WSDLs. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center ------------------------------------------------ Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700 Hi, [By the way, Jerry Thrasher has offered to convert my draft Std Print System Events from HTML to Word - thanks, Jerry!] The namespace will be PWG Semantic Model/1.0, just like all currently approved schemas. The internal version tag will be 1.x (something), but that's _not_ the namespace. So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents' elements can be referenced and used normally by PSI/1.0. _AFTER_ the Events spec and schema are formally approved (as PWG Candidate Standards), a copy of Events schema will be stored in the official directory: http://www.pwg.org/schemas/sm/1.0/ OK? Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 02, 2004 5:41 AM To: McDonald, Ira Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain Regnier Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. McDonald, I'm so sorry to be late for this reply to you. I've been a 'ROM' beacuse of my many pressing works. Thank you for this excellent summary of agenda. I can understand the content of the meeting very much. And I have a question. When "Standard Print System Events" will be voted as you mentioned as follows, what will be the 'Namespace' of the schema file (now posted in the ftp site as 'events-20040621.xsd') for that working draft ? There is no definition of 'targetNamespace' in the file. Is it same as the one of the Semantic Model or of PSI ? If the schema definition is temporary and for PSI, is it same as the 'Namespace' of PSI ? Or if the schema definition is temporary for next addition to the Semantic Model, is it same as the 'Namesapce' of SM ? If so, I guess some problem will occur when some original Events before removing will be added. How do you think ? Thank you, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700 Hi, At yesterday's meeting, we decided to simplify my recent "Standard Imaging Systems Events" draft and remove _all_ of the multi-function/non-printer events and classes. I will very shortly issue "Standard Print System Events" as a PSI working draft. We will review it on the PSI mailing list (and in PSI telecons, if necessary). PWG people agreed to plan to hold an "Interim Plenary" (by telecon) in July, in order to: (1) Complete adoption of PWG Process 2.0 (2) Complete 'last call' and then start Formal Approval (PWG-wide vote) of "Standard Print System Events". Then PSI/1.0 could be revoted for adoption. So we plan to keep the "SendXxxEvent" methods in PSI/1.0 and the Events schema should be approved for addition to the PWG Semantic Model to support those methods. Cheers, - Ira PS - Separately, WIMS WG has decided _not_ to work on the multi-function imaging system model, but instead to call for a BOF in the August face-to-face on this topic. This might then lead to writing a charter for MFISM working group, development of requirements, and finally return to my recent draft Imaging System Model spec (I hope). Which would delay work on WIMS support for any non-print systems until sometime in calendar 2005, it would appear. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, May 27, 2004 3:44 AM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM Hi Mr. Berkema, Thank you for your notice. But I couldn't attend that meeting becuase I read your E-mail after it. Sorry. (I might not be able to attend because it started early morning in Japan even if I read your E-mail before the meeting.) If there is the minutes, would you send them for me ? Thank you, Masa ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700 -----Original Message----- Dave, Mr. Itoh, Alain, and all, The PWG will discuss eventing and the impact on PSI at 2:00PM PDT on 5/26/04 during the current F2F. This could have a dramatic impact on the PSI schedule. Please call in if you can. Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Wednesday, May 19, 2004 11:07 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: Re^2: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, Thank you for your apology. That's no problem. Never mind, please. I thought I should send this report to Mr. Hall rather than you because he is the editor of PSI-WG. But I decided to send it to you because my some E-mails could not be reached to Mr. Hall when I posted to him and I received the error message automatically sent from HP mail server, that is "Delivery to the following recipients failed. david_hall3@am.exch.hp.com". If that is not appropriate, I have to apologize to you for that. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38 -0700 -----Original Message----- Sorry about the type in Mr. Itoh's name below, accidentally hit the send before reviewing regards, Alan ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Berkema, Alan C (R&D Roseville) Sent: Wednesday, May 19, 2004 9:20 AM To: 'Masanori ITOH' Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: RE: For revision of PSI specification document (2004/01/13) Mr Itch, Thanks for your careful review, Dave can you make these editorial corrections for the next re-vote? Thanks, Alan ---- ----- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13) Hi Mr. Berkema, I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them. If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them. Will you please point out any mistakes to me in this report. Cheers, ----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs' CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue' DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' ) i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface' CHANGING '' (cf. P.84 '7.4 InterfaceIdentifier' ) i.e. -> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType' What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements CHANGING 'JobContainter' (misspelling) i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ... DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?) i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference CHANGING 'see appendix (X)' i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- From imcdonald at sharplabs.com Fri Jul 9 11:58:34 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:20 2009 Subject: PS> FW: [Uri-review] SMB URI Draft v07. Message-ID: FYI, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: uri-review-bounces@ietf.org [mailto:uri-review-bounces@ietf.org]On Behalf Of Christopher R. Hertel Sent: Thursday, July 08, 2004 11:40 AM To: uri-review@ietf.org Subject: [Uri-review] SMB URI Draft v07. I have sent V07 of the SMB URI Internet Draft to the IETF. From past experience, it should be posted within the week. In the mean time I have posted a *preview* copy here: http://www.ubiqx.org/draft-crhertel-smb-url-07.txt This revision, relative to the previous one has no changes to the syntax or semantics of the URI scheme. Fact is, I'm fussy about my writing and I wasn't happy with V06. I'm still not completely happy with this one so I may send in one more revision before I ask for acceptance. Please send comments! Chris -)----- -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- crh@ubiqx.mn.org OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@ubiqx.org _______________________________________________ Uri-review mailing list Uri-review@ietf.org https://www1.ietf.org/mailman/listinfo/uri-review From ito at src.ricoh.co.jp Mon Jul 12 01:17:50 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: PS> Minutes of PSI telecon on 6 July In-Reply-To: References: Message-ID: <200407120517.AA00761@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, Now I'm modifying WSDLs as decided in the last telecon. And I have two questions. Do you mean this 'SendTargetDeviceNotification' is the return value of 'RegistertargetDevice' method ? 4.10 SubunitEvents and VendorEvents (missing parameters) will be added (in addition to existing PrinterEvents) to SendTargetDeviceNotification (to add support for detailed Subunit events such as 'InputMediaSupplyLow' and Vendor events from different non-Printer objects) If so, the return parameter is named as 'sendTargetDeviceNotifications' (the plural) ? If not, is is for 'SendTargetDeviceNotification' method (5.6.11) ? I think it it as to 'RegistertargetDevice' method because there is 'PrinterEvents' in 'SendTargetDeviceNotification' method. And this is the other question. If my opinion is correct, how do you define 'sendTargetDeviceNotifications' ? It consists of three events, PrinterEvents, SubunitEvents, and VendorEvents. Do you mean new complex schema type for them is defined like 'NotifyEvents' ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 7 Jul 2004 11:20:19 -0700 ------------------------------------------------ Hi, Comments or corrections are welcome. (1) target namespace will be added to Events schema of PWG Semantic Model/1.0, e.g., (2) UnsupportedElements will be corrected to be defined the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) (consistent semantics and interworking of gateways) (3) Jerry Thrasher's issues in latest draft: 3.1 interfaceIdentifier will be defined in PSI spec, to avoid normative dependency on WSDL 3.2 callbackInterval will be defined in to PSI spec, to avoid normative dependency on IPP GET (and conformance requirement vis-a-vis Job History time will be removed, due to weak rationale) 3.3 eventNumber parameter SHOULD be renamed (to align with WIMS and IPP) to notifySequenceNumber ** DAVE ** I just found a bug in our definition below ** Since SendXxxNotification methods can transfer one or _more_ events in a single notification, the correct semantic is that the renamed parameter is the number of this notification message (NOT the number of one of the events in the message). 3.4 eventID in section 5.6.11 will replaced with the correct notifySequenceNumber 3.5 normative references - moved WS-Addressing and WS-Security to informative - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the normative references and will add the phrase "defacto industry standard" (because all existing tools only support these defacto standards - very little support for SOAP/1.2 has been shipped or deployed - no support for the future _incompatible_ WSDL/2.0 has been shipped) 3.6 documentFilterElements will be marked OPTIONAL 3.7 all of Masanori Itoh's suggested changes were also made by Jerry Thrasher and approved in the telecon 4. Ira McDonald's changes for events: 4.1 JobEvents definition will be corrected in FetchNextJob 4.2 callbackInterval - see 3.2 above FetchNextJob 4.3 DocumentEvents definition will be corrected in FetchNextDocumentByPull 4.4 callbackInterval - see 3.2 above FetchNextDocumentByPull 4.5 DocumentEvents - see 4.3 above FetchNextDocumentByValue 4.6 callbackInterval - see 3.2 above FetchNextDocumentByValue 4.7 JobEvents (missing parameter) will be added to SendJobNotification 4.8 DocumentEvents (missing parameter) will be added to SendDocumentNotifications 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice 4.10 SubunitEvents and VendorEvents (missing parameters) will be added (in addition to existing PrinterEvents) to SendTargetDeviceNotification (to add support for detailed Subunit events such as 'InputMediaSupplyLow' and Vendor events from different non-Printer objects) (5) ** Significant Change ** 5.1 Entire current Std Print System Events spec will be incorporated as an appendix into the PSI spec (to avoid new normative dependencies for PSI) 5.2 At some future date, a PWG Std Imaging System Events spec may be developed as a PWG 'dictionary' standard (6) ** Last Call ** - PSI/1.0 and Events schema will enter PWG 'last call' no later than 26 July, to complete at the PWG Plenary on Wednesday 18 August in Montreal Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From ito at src.ricoh.co.jp Mon Jul 12 03:58:04 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: PS> Minutes of PSI telecon on 6 July Message-ID: <200407120758.AA00765@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I found my comment is strange. You mentioned 'RegisterTargetDevice' method has 'NotifyEvents' instead of 'PrinterEvents' as follows. 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice So is '4.10' as to 'SendTargetDeviceNotification' method ? But 'PrinterEvents' doesn't exist in 'SendTargetDeviceNotification' method. I don't know what you mean. Would you tell me that in detail ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------- Masanori ITOH wrote on Mon, 12 Jul 2004 14:17:50 +0900 |Hi Mr. McDonald, | |Now I'm modifying WSDLs as decided in the last telecon. |And I have two questions. | |Do you mean this 'SendTargetDeviceNotification' is the return value of |'RegistertargetDevice' method ? | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |If so, the return parameter is named as 'sendTargetDeviceNotifications' |(the plural) ? |If not, is is for 'SendTargetDeviceNotification' method (5.6.11) ? | |I think it it as to 'RegistertargetDevice' method because |there is 'PrinterEvents' in 'SendTargetDeviceNotification' method. | |And this is the other question. |If my opinion is correct, how do you define 'sendTargetDeviceNotifications' ? |It consists of three events, PrinterEvents, SubunitEvents, and VendorEvents. |Do you mean new complex schema type for them is defined like 'NotifyEvents' ? | |Cheers, |Masa. | |----------------------- |Masanonri 'MASA' Itoh |RICOH Co., Ltd. Software R&D Center | | |Mr. McDonald, Ira wrote on Wed, 7 Jul 2004 11:20:19 -0700 | |------------------------------------------------ | |Hi, | |Comments or corrections are welcome. | | |(1) target namespace will be added to Events schema | of PWG Semantic Model/1.0, e.g., | | | |(2) UnsupportedElements will be corrected to be defined | the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) | (consistent semantics and interworking of gateways) | |(3) Jerry Thrasher's issues in latest draft: | | 3.1 interfaceIdentifier will be defined in PSI spec, | to avoid normative dependency on WSDL | | 3.2 callbackInterval will be defined in to PSI spec, | to avoid normative dependency on IPP GET | (and conformance requirement vis-a-vis Job History | time will be removed, due to weak rationale) | | 3.3 eventNumber parameter SHOULD be renamed (to align | with WIMS and IPP) to notifySequenceNumber | |** DAVE ** I just found a bug in our definition below ** | | Since SendXxxNotification methods can transfer | one or _more_ events in a single notification, | the correct semantic is that the renamed parameter | is the number of this notification message (NOT | the number of one of the events in the message). | | 3.4 eventID in section 5.6.11 will replaced with the | correct notifySequenceNumber | | 3.5 normative references | - moved WS-Addressing and WS-Security to informative | - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the | normative references and will add the phrase | "defacto industry standard" | | (because all existing tools only support these | defacto standards - very little support for SOAP/1.2 | has been shipped or deployed - no support for the | future _incompatible_ WSDL/2.0 has been shipped) | | 3.6 documentFilterElements will be marked OPTIONAL | | 3.7 all of Masanori Itoh's suggested changes were also | made by Jerry Thrasher and approved in the telecon | |4. Ira McDonald's changes for events: | | 4.1 JobEvents definition will be corrected in | FetchNextJob | | 4.2 callbackInterval - see 3.2 above | FetchNextJob | | 4.3 DocumentEvents definition will be corrected in | FetchNextDocumentByPull | | 4.4 callbackInterval - see 3.2 above | FetchNextDocumentByPull | | 4.5 DocumentEvents - see 4.3 above | FetchNextDocumentByValue | | 4.6 callbackInterval - see 3.2 above | FetchNextDocumentByValue | | 4.7 JobEvents (missing parameter) will be added to | SendJobNotification | | 4.8 DocumentEvents (missing parameter) will be added to | SendDocumentNotifications | | 4.9 PrinterEvents will be replaced with NotifyEvents | (to allow subscription to all classes of events) in | RegisterTargetDevice | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |(5) ** Significant Change ** | | 5.1 Entire current Std Print System Events spec will be | incorporated as an appendix into the PSI spec | (to avoid new normative dependencies for PSI) | | 5.2 At some future date, a PWG Std Imaging System Events | spec may be developed as a PWG 'dictionary' standard | |(6) ** Last Call ** | - PSI/1.0 and Events schema will enter PWG 'last call' | no later than 26 July, to complete at the PWG Plenary | on Wednesday 18 August in Montreal | |Cheers, |- Ira | |Ira McDonald (Musician / Software Architect) |Blue Roof Music / High North Inc |PO Box 221 Grand Marais, MI 49839 |phone: +1-906-494-2434 |email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Mon Jul 12 11:14:30 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> FW: Interim draft of PSI spec from Dave Hall Message-ID: Hi, Attachment deleted. Note copied to PSI list to document the work-in-progress. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: McDonald, Ira Sent: Monday, July 12, 2004 10:56 AM To: 'Masanori ITOH'; McDonald, Ira Cc: 'Hall, David M (CIP / DCL Vancouver)'; 'thrasher@lexmark.com'; 'Berkema, Alan C (R&D Roseville)' Subject: Interim draft of PSI spec from Dave Hall Hi, Attached is a PDF of Dave's updates for events to the PSI spec. Jerry Thrasher still needs to add the appendix with the actual text of the former Std Print System Events spec to the PSI spec (so there's only one document and one schema to 'last call' later this month). If you look at the parameters and returns of RegisterForTargetDevice and also SendTargetDeviceNotification, I think the answers to your questions will become clear. The only bug still in the spec (my fault for not being clearer to Dave) is that the parameter 'eventSequenceNumber' now takes a strong type 'NotifySequenceNumber' from the Events schema, but this is a modelling error (that element belongs in the Subscription and Alert objects as currently being modelled by PWG WIMS WG). So 'eventSequenceNumber' datatype should go back to simple 'xsd:int', as before. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, July 12, 2004 3:58 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Minutes of PSI telecon on 6 July Hi Mr. McDonald, I found my comment is strange. You mentioned 'RegisterTargetDevice' method has 'NotifyEvents' instead of 'PrinterEvents' as follows. 4.9 PrinterEvents will be replaced with NotifyEvents (to allow subscription to all classes of events) in RegisterTargetDevice So is '4.10' as to 'SendTargetDeviceNotification' method ? But 'PrinterEvents' doesn't exist in 'SendTargetDeviceNotification' method. I don't know what you mean. Would you tell me that in detail ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center -------------------------------------------------------- Masanori ITOH wrote on Mon, 12 Jul 2004 14:17:50 +0900 |Hi Mr. McDonald, | |Now I'm modifying WSDLs as decided in the last telecon. |And I have two questions. | |Do you mean this 'SendTargetDeviceNotification' is the return value of |'RegistertargetDevice' method ? | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |If so, the return parameter is named as 'sendTargetDeviceNotifications' |(the plural) ? |If not, is is for 'SendTargetDeviceNotification' method (5.6.11) ? | |I think it it as to 'RegistertargetDevice' method because |there is 'PrinterEvents' in 'SendTargetDeviceNotification' method. | |And this is the other question. |If my opinion is correct, how do you define 'sendTargetDeviceNotifications' ? |It consists of three events, PrinterEvents, SubunitEvents, and VendorEvents. |Do you mean new complex schema type for them is defined like 'NotifyEvents' ? | |Cheers, |Masa. | |----------------------- |Masanonri 'MASA' Itoh |RICOH Co., Ltd. Software R&D Center | | |Mr. McDonald, Ira wrote on Wed, 7 Jul 2004 11:20:19 -0700 | |------------------------------------------------ | |Hi, | |Comments or corrections are welcome. | | |(1) target namespace will be added to Events schema | of PWG Semantic Model/1.0, e.g., | | | |(2) UnsupportedElements will be corrected to be defined | the same as PWG SM/1.0 schema and IPP/1.1 (RFC 2911) | (consistent semantics and interworking of gateways) | |(3) Jerry Thrasher's issues in latest draft: | | 3.1 interfaceIdentifier will be defined in PSI spec, | to avoid normative dependency on WSDL | | 3.2 callbackInterval will be defined in to PSI spec, | to avoid normative dependency on IPP GET | (and conformance requirement vis-a-vis Job History | time will be removed, due to weak rationale) | | 3.3 eventNumber parameter SHOULD be renamed (to align | with WIMS and IPP) to notifySequenceNumber | |** DAVE ** I just found a bug in our definition below ** | | Since SendXxxNotification methods can transfer | one or _more_ events in a single notification, | the correct semantic is that the renamed parameter | is the number of this notification message (NOT | the number of one of the events in the message). | | 3.4 eventID in section 5.6.11 will replaced with the | correct notifySequenceNumber | | 3.5 normative references | - moved WS-Addressing and WS-Security to informative | - kept W3C Notes on WSDL/1.1 and SOAP/1.1 in the | normative references and will add the phrase | "defacto industry standard" | | (because all existing tools only support these | defacto standards - very little support for SOAP/1.2 | has been shipped or deployed - no support for the | future _incompatible_ WSDL/2.0 has been shipped) | | 3.6 documentFilterElements will be marked OPTIONAL | | 3.7 all of Masanori Itoh's suggested changes were also | made by Jerry Thrasher and approved in the telecon | |4. Ira McDonald's changes for events: | | 4.1 JobEvents definition will be corrected in | FetchNextJob | | 4.2 callbackInterval - see 3.2 above | FetchNextJob | | 4.3 DocumentEvents definition will be corrected in | FetchNextDocumentByPull | | 4.4 callbackInterval - see 3.2 above | FetchNextDocumentByPull | | 4.5 DocumentEvents - see 4.3 above | FetchNextDocumentByValue | | 4.6 callbackInterval - see 3.2 above | FetchNextDocumentByValue | | 4.7 JobEvents (missing parameter) will be added to | SendJobNotification | | 4.8 DocumentEvents (missing parameter) will be added to | SendDocumentNotifications | | 4.9 PrinterEvents will be replaced with NotifyEvents | (to allow subscription to all classes of events) in | RegisterTargetDevice | | 4.10 SubunitEvents and VendorEvents (missing parameters) | will be added (in addition to existing PrinterEvents) to | SendTargetDeviceNotification | (to add support for detailed Subunit events such as | 'InputMediaSupplyLow' and Vendor events from different | non-Printer objects) | |(5) ** Significant Change ** | | 5.1 Entire current Std Print System Events spec will be | incorporated as an appendix into the PSI spec | (to avoid new normative dependencies for PSI) | | 5.2 At some future date, a PWG Std Imaging System Events | spec may be developed as a PWG 'dictionary' standard | |(6) ** Last Call ** | - PSI/1.0 and Events schema will enter PWG 'last call' | no later than 26 July, to complete at the PWG Plenary | on Wednesday 18 August in Montreal | |Cheers, |- Ira | |Ira McDonald (Musician / Software Architect) |Blue Roof Music / High North Inc |PO Box 221 Grand Marais, MI 49839 |phone: +1-906-494-2434 |email: imcdonald@sharplabs.com From imcdonald at sharplabs.com Wed Jul 14 18:34:40 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Thu Jul 15 03:02:56 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) In-Reply-To: References: Message-ID: <200407150702.AA00770@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From PZehler at crt.xerox.com Thu Jul 15 08:14:58 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:21 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9FE7@CRTE128> Ira, One thing I noticed is that VendorEventType values (i.e. extensions) are not federated through the use of namespaces. The way this is handled in the rest of the PWG schema is a restriction that requires a ':' in the value. To accomplish this the definition would change from: to: The other thing I noticed is that since the events are specified as enumerations a major revision will be necessary to add any new values. The way the rest of the schema handles this is through the use of a union. If the intent is these are a type I enumeration the definition is fine. If they are type II or III enumerations the definitions should be changed. For example DocumentEventType would change from: To (Note DocumentEventTypes not required and can be replaced with DocumentEventWKVs): (from PwgWellKnownValues: ) Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, July 14, 2004 6:35 PM To: 'ps@pwg.org' Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Thu Jul 15 12:10:43 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi Pete, Thanks for all these criticisms. I'll pore over them and try to understand them quickly. There are three real problems I think I see: (1) Events.xsd MUST always be completely stand-alone, because it will in the future become the direct authoritative reference for Std Imaging System Events. Importing the document events from WKV is not acceptable. (2) Introducing the use of 'union'. There is very strong resistance to this in the PSI WG. The existence of 'union' in SM/1.0 causes more problems than it might solve. [For the PSI WSDL to be reviewed and/or tested, a version of every SM/1.0 schema without 'union' must be created and stored in a PSI WG directory.] (3) There is no concept of type II or type III enums in Events.xsd. Events are all type I. Any other event is a vendor extension. Period. [By the way, type III enums no longer exist in IPP. The IETF has definitively rejected the type III class in Printer/Finisher MIB and passed that on to IANA for IPP as well. SM should stop using the term "type III"] Cheers, - Ira PS - We're on a short fuse here. If Events.xsd is not in final form before 26 July 2004, then PSI/1.0 'last call' is prevented. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Thursday, July 15, 2004 8:15 AM To: 'McDonald, Ira'; 'ps@pwg.org' Subject: RE: PS> Last call ready Events schema v0.41 (14 July 2004) Ira, One thing I noticed is that VendorEventType values (i.e. extensions) are not federated through the use of namespaces. The way this is handled in the rest of the PWG schema is a restriction that requires a ':' in the value. To accomplish this the definition would change from: to: The other thing I noticed is that since the events are specified as enumerations a major revision will be necessary to add any new values. The way the rest of the schema handles this is through the use of a union. If the intent is these are a type I enumeration the definition is fine. If they are type II or III enumerations the definitions should be changed. For example DocumentEventType would change from: To (Note DocumentEventTypes not required and can be replaced with DocumentEventWKVs): (from PwgWellKnownValues: ) Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, July 14, 2004 6:35 PM To: 'ps@pwg.org' Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From thrasher at lexmark.com Thu Jul 15 12:16:02 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:21 2009 Subject: PS> Updated PSI Working Draft posted Message-ID: PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From imcdonald at sharplabs.com Thu Jul 15 12:19:40 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Thu Jul 15 12:51:10 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> Updated PSI Working Draft posted Message-ID: Hi folks, [Alan - we need a PSI telecon next Tuesday 20 July, please. We have very little time to resolve Pete Zehler's criticisms of the 'Events.xsd' just posted.] Jerry - thanks very much for doing all this work! Please, could _you_ turn on redlined changes in the '.doc' file and save it as '...714-rev.pdf'. Then I could see the changes (I'm always hitting the wrong key when trying to review in source '.doc' files). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 12:16 PM To: ps@pwg.org Subject: PS> Updated PSI Working Draft posted PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From thrasher at lexmark.com Thu Jul 15 13:54:49 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:21 2009 Subject: PS> PSI Working Draft w/ revision markes turned on...posted Message-ID: A version latest PSI working draft .doc file with revisions turned on is posted.... ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714-rev.doc "McDonald, Ira" , ps@pwg.org abs.com> cc: Sent by: Subject: RE: PS> Updated PSI Working Draft posted owner-ps@pwg.org 07/15/2004 12:51 PM Hi folks, [Alan - we need a PSI telecon next Tuesday 20 July, please. We have very little time to resolve Pete Zehler's criticisms of the 'Events.xsd' just posted.] Jerry - thanks very much for doing all this work! Please, could _you_ turn on redlined changes in the '.doc' file and save it as '...714-rev.pdf'. Then I could see the changes (I'm always hitting the wrong key when trying to review in source '.doc' files). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 12:16 PM To: ps@pwg.org Subject: PS> Updated PSI Working Draft posted PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From alan.berkema at hp.com Thu Jul 15 16:25:18 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:21 2009 Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM Message-ID: I will be in Vancouver on Tuesday and do not have any free time, so this call is scheduled for Wednesday Harry, Dave, Ira, Jerry, please let me know if this works for you Title: PSI Events/Last Call Time: Wednesday, July 21, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Events schema 2) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GSFQSSAHP Participant: https://www.hpe-learning.com/attend/default.aspx?key=UQXAM5NHY To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From imcdonald at sharplabs.com Thu Jul 15 16:39:45 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM Message-ID: Hi Alan, Works perfectly! The very next hour (9am PDT / 12pm EDT) is our regular WIMS telecon. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Thursday, July 15, 2004 4:25 PM To: a PSI pwg.org Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM I will be in Vancouver on Tuesday and do not have any free time, so this call is scheduled for Wednesday Harry, Dave, Ira, Jerry, please let me know if this works for you Title: PSI Events/Last Call Time: Wednesday, July 21, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Events schema 2) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GSFQSSAHP Participant: https://www.hpe-learning.com/attend/default.aspx?key=UQXAM5NHY To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From imcdonald at sharplabs.com Thu Jul 15 17:20:57 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> [PDF] PSI Working Draft w/ revision markes turned on...po sted Message-ID: Hi, Thanks Jerry - a version with revisions in PDF: ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714-rev.pdf Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 1:55 PM To: ps@pwg.org Subject: PS> PSI Working Draft w/ revision markes turned on...posted A version latest PSI working draft .doc file with revisions turned on is posted.... ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714-rev.doc "McDonald, Ira" , ps@pwg.org abs.com> cc: Sent by: Subject: RE: PS> Updated PSI Working Draft posted owner-ps@pwg.org 07/15/2004 12:51 PM Hi folks, [Alan - we need a PSI telecon next Tuesday 20 July, please. We have very little time to resolve Pete Zehler's criticisms of the 'Events.xsd' just posted.] Jerry - thanks very much for doing all this work! Please, could _you_ turn on redlined changes in the '.doc' file and save it as '...714-rev.pdf'. Then I could see the changes (I'm always hitting the wrong key when trying to review in source '.doc' files). Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of thrasher@lexmark.com Sent: Thursday, July 15, 2004 12:16 PM To: ps@pwg.org Subject: PS> Updated PSI Working Draft posted PSI folks... An updated PSI working draft is available on the PWG's FTP site. This working draft includes the Appendix that describes the Standard Printing System Events. It does NOT include any changes/corrections that have been mentioned on the list.....from Ira, Mr Itoh, or Pete....I'd expect there will be one more round of edits before the Last Call working draft is ready.......maybe a Conf.Call next week??? ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040714.pdf and doc You can turn changes on in the doc file to see the extent of the accrued changes since the last vote. Jerry From PZehler at crt.xerox.com Thu Jul 15 12:46:30 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:02:21 2009 Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9FEC@CRTE128> Ira, Comments below Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, July 15, 2004 12:11 PM To: 'ps@pwg.org' Subject: RE: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Pete, Thanks for all these criticisms. I'll pore over them and try to understand them quickly. There are three real problems I think I see: (1) Events.xsd MUST always be completely stand-alone, because it will in the future become the direct authoritative reference for Std Imaging System Events. Importing the document events from WKV is not acceptable. I'm not advocating the inclusion of PwgWellKnownValues. I just inclided it as an example of the pattern for a qualified NMTOKEN (2) Introducing the use of 'union'. There is very strong resistance to this in the PSI WG. The existence of 'union' in SM/1.0 causes more problems than it might solve. The only thing given up is that the PWG can not add new values unless there is a major version bump or it adds them to the vendor element. It is your guys call. In the rest of the schema we decided not to code it based on the capabilities of existing tools. We decided to define it as called out in the model. You know my preference but I will not strongly object [For the PSI WSDL to be reviewed and/or tested, a version of every SM/1.0 schema without 'union' must be created and stored in a PSI WG directory.] (3) There is no concept of type II or type III enums in Events.xsd. Events are all type I. Any other event is a vendor extension. Period. As I said if events are type I there is no need for a union construct. I would prefer to see the enumerations not inlined and be defined in an xxxWKV element. The resulting change is that simple types DocumentEventType, JobEventType, PrinterEventType, SubunitEventType would be changed to simple types DocumentEventWKV, JobEventWKV, PrinterEventWKV, SubunitEventWKV. The VendorEventType would have the pattern facet added to its restriction as shown below and its name would change to VendorEventExtensionPattern. [By the way, type III enums no longer exist in IPP. The IETF has definitively rejected the type III class in Printer/Finisher MIB and passed that on to IANA for IPP as well. SM should stop using the term "type III"] Cheers, - Ira PS - We're on a short fuse here. If Events.xsd is not in final form before 26 July 2004, then PSI/1.0 'last call' is prevented. my proposal is to skip the union stuff, add the pattern and change the names as suggested above Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Zehler, Peter [mailto:PZehler@crt.xerox.com] Sent: Thursday, July 15, 2004 8:15 AM To: 'McDonald, Ira'; 'ps@pwg.org' Subject: RE: PS> Last call ready Events schema v0.41 (14 July 2004) Ira, One thing I noticed is that VendorEventType values (i.e. extensions) are not federated through the use of namespaces. The way this is handled in the rest of the PWG schema is a restriction that requires a ':' in the value. To accomplish this the definition would change from: to: The other thing I noticed is that since the events are specified as enumerations a major revision will be necessary to add any new values. The way the rest of the schema handles this is through the use of a union. If the intent is these are a type I enumeration the definition is fine. If they are type II or III enumerations the definitions should be changed. For example DocumentEventType would change from: To (Note DocumentEventTypes not required and can be replaced with DocumentEventWKVs): (from PwgWellKnownValues: ) Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice:??? (585) 265-8755 FAX:????? (585) 422-7961 US Mail: Peter Zehler Xerox Corp. ??????? 800 Phillips Rd. ??????? M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Wednesday, July 14, 2004 6:35 PM To: 'ps@pwg.org' Subject: PS> Last call ready Events schema v0.41 (14 July 2004) Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Fri Jul 16 02:47:17 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) In-Reply-To: References: Message-ID: <200407160647.AA00774@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, Thank you for quick reply. Please see my comments inline below. Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700 ------------------------------------------------------------------------ Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. O.K. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] I got same advice from Mr. Zehler directly. > Thanks, Zehler-san. But I worry about how an implementor knows where schma file are kept. He knows the Semantic Model schemas are used in PSI to read the PSI spec. But he can't get the schema files. Because true storage place of the schema files is not shown in PSI spec. In the PSI web page he can get WSDLs, but don't notice needs of SM schema files. Because there is no description of the schema files and no link to them. (only the link to top page of SM exists). Currently there is the description only in PSI WSDL files. (Of cource there may be a chance that he glances at SM web page or reads carefully reference to SM, e.g. '9 Normative References', in PSI spec, and can get files in SM web page.) If hard paths ('namespace'? part in URL of the schema files) should be deleted in WSDL files, I think it is need to show where schema files can be got. How do you think ? Anyway I will use only file names in my WSDLs as your and Mr. Zehler's advice. (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I understand. I will use 'Events.xsd' in new WSDLs. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Fri Jul 16 11:21:26 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) Message-ID: Hi Masa, I agree that the PSI spec (and SM spec) should explicitly state the location of SM schema. Harry Lewis and I both think that current global (PWG std) and local (no union or other problems) copies of entire SM/1.0 w/ all approved extension schema should be _permanently_ available on the authoritative PWG FTP site, because: - HTTP links are not guaranteed stable on PWG server - FTP links _are_ guaranteed stable on PWG server I personally do not like storing actual schema at the URL in 'targetNamespace', which SHOULD be an entirely opaque identifier. And I do not think that schema themselves should specify standard SM schema location URLs. But, I think it would be OK in the schema themselves for a comment or an annotation to state stable FTP directory URLs (i.e., documented for people but safe from machine interpretation). Comments? Cheers, - Ira PS - Pete Zehler is going on vacation for a week, so we may not hear from him for a little while. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 16, 2004 2:47 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for quick reply. Please see my comments inline below. Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700 ------------------------------------------------------------------------ Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. O.K. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] I got same advice from Mr. Zehler directly. > Thanks, Zehler-san. But I worry about how an implementor knows where schma file are kept. He knows the Semantic Model schemas are used in PSI to read the PSI spec. But he can't get the schema files. Because true storage place of the schema files is not shown in PSI spec. In the PSI web page he can get WSDLs, but don't notice needs of SM schema files. Because there is no description of the schema files and no link to them. (only the link to top page of SM exists). Currently there is the description only in PSI WSDL files. (Of cource there may be a chance that he glances at SM web page or reads carefully reference to SM, e.g. '9 Normative References', in PSI spec, and can get files in SM web page.) If hard paths ('namespace'? part in URL of the schema files) should be deleted in WSDL files, I think it is need to show where schema files can be got. How do you think ? Anyway I will use only file names in my WSDLs as your and Mr. Zehler's advice. (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I understand. I will use 'Events.xsd' in new WSDLs. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From ito at src.ricoh.co.jp Tue Jul 20 04:38:24 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: Re^4: PS> Last call ready Events schema v0.41 (14 July 2004) In-Reply-To: References: Message-ID: <200407200838.AA00776@macbeth.src.ricoh.co.jp> Hi Mr. McDonald, I'm pleased to obtain your agreement. I think it's good to include a comment or an annotation in WSDL files to state stable FTP directory URLs from where schema files can be got. Because I think it nice that same information can be got in many ways, e.g. PSI spec, PSI Web page, WSDL files, and so on. (But that information needs to be same when it is changed ...) Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Fri, 16 Jul 2004 08:21:26 -0700 ------------------------------------------------------------------------ Hi Masa, I agree that the PSI spec (and SM spec) should explicitly state the location of SM schema. Harry Lewis and I both think that current global (PWG std) and local (no union or other problems) copies of entire SM/1.0 w/ all approved extension schema should be _permanently_ available on the authoritative PWG FTP site, because: - HTTP links are not guaranteed stable on PWG server - FTP links _are_ guaranteed stable on PWG server I personally do not like storing actual schema at the URL in 'targetNamespace', which SHOULD be an entirely opaque identifier. And I do not think that schema themselves should specify standard SM schema location URLs. But, I think it would be OK in the schema themselves for a comment or an annotation to state stable FTP directory URLs (i.e., documented for people but safe from machine interpretation). Comments? Cheers, - Ira PS - Pete Zehler is going on vacation for a week, so we may not hear from him for a little while. Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Friday, July 16, 2004 2:47 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for quick reply. Please see my comments inline below. Thanks, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700 ------------------------------------------------------------------------ Hi, (1) 'NotifyEventType' is no longer needed. It was being used in WIMS 'Schedule.xsd', but 'NotifyEvents' (as a type or an element) can be used instead. O.K. (2) In your WSDL, imports should be local/simple filenames (same directory as WSDL). [Pete Zehler just removed the use of hard paths for imports in all of the SM/1.0 schema, because they cause some tools to directly access the PWG site, which MUST NOT happen in released products. Also, those hard paths require hand-editing to create a local version of SM/1.0 schema.] I got same advice from Mr. Zehler directly. > Thanks, Zehler-san. But I worry about how an implementor knows where schma file are kept. He knows the Semantic Model schemas are used in PSI to read the PSI spec. But he can't get the schema files. Because true storage place of the schema files is not shown in PSI spec. In the PSI web page he can get WSDLs, but don't notice needs of SM schema files. Because there is no description of the schema files and no link to them. (only the link to top page of SM exists). Currently there is the description only in PSI WSDL files. (Of cource there may be a chance that he glances at SM web page or reads carefully reference to SM, e.g. '9 Normative References', in PSI spec, and can get files in SM web page.) If hard paths ('namespace'? part in URL of the schema files) should be deleted in WSDL files, I think it is need to show where schema files can be got. How do you think ? Anyway I will use only file names in my WSDLs as your and Mr. Zehler's advice. (3) 'Events.xsd' is the intended name. It may be extended (but only with _new_ events or more probably event classes). But those 'official' extensions will be sometime in 2005, at the earliest. I understand. I will use 'Events.xsd' in new WSDLs. I hope these answers help. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Thursday, July 15, 2004 3:03 AM To: McDonald, Ira Cc: 'ps@pwg.org' Subject: Re: PS> Last call ready Events schema v0.41 (14 July 2004) Hi Mr. McDonald, Thank you for uploading. I have two questions. Type difinition named 'NotifyEventType' is not used. i.e. It is not refered from every element difinition. Is is OK ? (I feel a little strage for it. This difinition is for a CHOICE from all five events. I guess it can be covered with each individual event difinition. I wonder how this type difinition is used. If 'xsd:all' or 'xsd:sequence' is used and plural events can be treated in other elements (e.g. in a Vendor's event), I guess this type difinition is worthy. But if it were so, this type has same meaning as the type difinition 'NotifyEvents'. This difinition has worth only as the definite TYPE definition because there are characters 'Type' in its name. Um.... ) The other question is the official name (URI) of this schema file. I need this information to add 'import' definition of this file in new PSI WSDLs. Will this file be officially named as 'http://www.pwg.org/schemas/sm/1.0/Events.xsd' ? If the file name 'Events.xsd' needs to be reserved for the future extension of Events, will be other name adopted, e.g. 'StandardPrintSystemEvents.xsd' ? A little verbose. Um... Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. McDonald, Ira wrote on Wed, 14 Jul 2004 15:34:40 -0700 ------------------------------------------------------------------------ Hi folks, Wednesday (14 July 2004) Ready for PWG 'last call', I just posted the Events XML schema v0.41 in the PSI working group directory tree. It validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator): ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040714.xsd NOTE: The _next_ version of PSI/1.0 (for PWG 'last call') will include definitions of standard print system events in a new Appendix. This Events schema references that (to be published) version of PSI/1.0. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Wed Jul 21 10:00:55 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> Events.xsd v0.42 for PWG 'last call' (21 July 2004) Message-ID: Hi folks, Wednesday (21 July 2004) [Based on technical and editorial feedback from Pete Zehler.] Ready for PWG 'last call', I just posted the Events XML schema v0.42: ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040721.xsd This schema validates without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator). NOTE: wd-psi10-20040714-rev.pdf (for PWG 'last call') now includes definitions of standard print system events in a new Appendix. This Events schema normatively references that appendix. **** We intend to submit PSI/1.0 and this companion Events schema for PWG 'last call' no later than 26 July 2004, for conclusion at the Plenary on Wednesday 18 August 2004 at the PWG face-to-face in Montreal. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [changes from Events v0.41 to v0.42] (1) Minor editorial changes. (2) Deleted redundant NotifyEventType (no longer used internally or by WIMS Schedule schema), per request of Masanori Itoh (Ricoh). (3) Renamed 'VendorEventType' to 'VendorEventExtensionPattern' and added qualified keyword/name pattern for federated namespaces, for consistency with PWG SM/1.0, per request of Pete Zehler (Xerox). (4) Renamed all enumerated of event types from '...Type' to '...WKV' and added comment on moving to 'PwgWellKnownValues.xsd' after approval, for consistency with PWG SM/1.0, per request of Pete Zehler (Xerox), ------------------------------------------------------------------------ [changes from Events v0.40 to v0.41] (1) Minor editorial changes. (2) Added standard PWG SM/1.0 target namespace to schema declaration, per request of Masonori Itoh (Ricoh). (3) Added type names (e.g., ) to all event groups (e.g., JobEvents), for support of PSI parameters, per PSI WG telecon 6 July 2004. (4) Added normative reference to PSI/1.0 spec for event definitions (new appendix to be added w/ Std Print System Events spec content), per PSI WG telecon 6 July 2004. (5) Added detailed informative references to IPP/1.1 (RFC 2911), IPP Document Object (PWG 5100.5), Printer MIB v2 (RFC 3805), and IPP Event Notifications and Subscriptions (IESG-approved), for implementor convenience. ------------------------------------------------------------------------ From imcdonald at sharplabs.com Wed Jul 21 10:03:53 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM Message-ID: Reminder - we meet in one hour Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Thursday, July 15, 2004 4:25 PM To: a PSI pwg.org Subject: PS> PSI: *Wednesday* Teleconference July 21 @ 8:00AM I will be in Vancouver on Tuesday and do not have any free time, so this call is scheduled for Wednesday Harry, Dave, Ira, Jerry, please let me know if this works for you Title: PSI Events/Last Call Time: Wednesday, July 21, 2004 8:00 AM Pacific Daylight Time Duration: 60 minutes Hey all, we will use a new web tool see below: Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) Events schema 2) Determine new last call plans Thanks, Alan ---- HPVC web tool: You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GSFQSSAHP Participant: https://www.hpe-learning.com/attend/default.aspx?key=UQXAM5NHY To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup Thank you for using the HP Virtual Classroom. From ito at src.ricoh.co.jp Tue Jul 27 05:08:15 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: PS> Re: PWG-ANNOUNCE> PSI to Begin New Last Call Review In-Reply-To: References: Message-ID: <200407270908.AA00785@macbeth.src.ricoh.co.jp> Hi Mr. Berkema, I am now making a final check on WSDLs for the final vote and found some mistakes and questions in PSI spec (July 14, 2004). So I report them. Any comment is welcomed. -------------------------------------------------------------------- P.25 5.4.2 GetTargetDeviceElements Parameters: 'requestedPrinterElements:RequestedElements' There is no type definition of 'RequestedElements' in 'Printer.xsd' file, but in 'PwgCommon.xsd' file. i.e. ...... Semantic Model [PWG5105.1] Printer.xsd -> ...... Semantic Model [PWG5105.1] PwgCommon.xsd -------------------------------------------------------------------- P.26 5.4.3 GetKnownTargetDevices Parameters: 'printerFilterElements:Printer' Does the sentence '(Give an example of a printerFilterElemets)' mean '16.2 printerFilterElements : Printer' in '16 Appendix B - Example XML Instance Objects (Informative)' So need to delete that? If needed, it may be good to make the sentence 'See example in Section 16' be more in detail. -------------------------------------------------------------------- P.101 '16 Appendix B - Example XML Instance Objects (Informative)' The version of the Semantic Model in namespace is old. -------------------------------------------------------------------- P.101 '16.1 unsupportedElements : UnsupportedElements' What is 'C:\SEMANT~1\PwgObjects.xsd' ? Local file ? -------------------------------------------------------------------- P.101 '16.2 printerFilterElements : Printer' This is the sample shown in PSI Spec. (omitted the unnecessary part) : : : : 'Printer' is the TYPE, but not the ELEMENT of parameter 'printerFilterElements'. So the sample above is strange. Element 'Printer' should not be expressed , but in the sample it is expressed. Because in 'Priner.xsd' file, the type 'Printer' is defined as follows. If the parameter 'printerFilterElements' is expected to use like the sample above, the definitions of 'GetKnownTargetDevices' need to be done as follows. ==WSDL-Example(A)== ^^^ (In the file 'Print.xsd', there is the definition of ELEMENT 'Printer' like this. ) But strictly in accordance with PSI spec, the definition of 'GetKnownTargetDevices' is as follows. This sample is same as ServiceCapabilitiesInterface.wsdl (20030411). ==WSDL-Example(B)== ^^^^^ So there should be no element name called 'Printer' in the sample. How do you think ? -------------------------------------------------------------------- P.101 '16.3 jobFilterElements : Job' Same as '16.2 printerFilterElements : Printer' above. -------------------------------------------------------------------- P.102 '16.4 documentFilterElements : Document' Same as '16.2 printerFilterElements : Printer' above. Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Thu, 22 Jul 2004 14:09:37 -0700 ------------------------------------------------------------------------ All, Here are the files, thanks to Ira, Jerry, and Dave! The last call review process begins on 07/23/2004 and will end on 08/16/2004. We will accept e-mail comments during this time period on the psi reflector. ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721.pdf (and .doc) ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721-rev.pdf (and .doc) Also the events Schema ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040721.xsd Last Call Comment resolution meeting tbd at F2F? Thanks, Alan Berkema From dhall at hp.com Thu Jul 29 18:58:38 2004 From: dhall at hp.com (Hall, David M (CIP / DCL Vancouver)) Date: Wed May 6 14:02:21 2009 Subject: PS> FW: [jira] Closed: (AXIS-568) [xsd:union] WSDL2java problem with union of NMTOKEN enumeration and NMTOKEN pattern restriction Message-ID: <6715E3BB1116B34BBF521C3A58E35188DAC16E@cacexc08.americas.cpqcorp.net> Good news! It will be interesting to try the latest axis toolset with semantic model union structure. -----Original Message----- From: axis-dev@ws.apache.org [mailto:axis-dev@ws.apache.org] Sent: Thursday, July 29, 2004 2:44 PM To: Hall, David M (CIP / DCL Vancouver) Subject: [jira] Closed: (AXIS-568) [xsd:union] WSDL2java problem with union of NMTOKEN enumeration and NMTOKEN pattern restriction Message: The following issue has been closed. Resolver: Jarek Gawor Date: Thu, 29 Jul 2004 2:42 PM Basic union support was added to Axis. Please try with latest code. --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/AXIS-568 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXIS-568 Summary: [xsd:union] WSDL2java problem with union of NMTOKEN enumeration and NMTOKEN pattern restriction Type: Bug Status: Closed Resolution: FIXED Project: Axis Components: WSDL processing Versions: 1.1beta Assignee: Reporter: David Hall Created: Thu, 12 Dec 2002 11:11 PM Updated: Thu, 29 Jul 2004 2:42 PM Environment: Operating System: Windows NT/2K Platform: PC Description: We are utilizing the Axis toolkit for creating a sample Printer Working Group PSI server and client. See http://www.pwg.org/ps for details on the project. The PSI interface is utilizing the PWG semantic model type definitions. See http://www.pwg.org/sm for details. In creating our interface defintions, we have run into a problem with WSDL2java, and the following constructs: If you specify the --all parameter for WSDL2java, the CompressionWKV and KeywordNsExtensionPattern objects get correctly generated, but the encapsulating Compression object ends up with no accessors, or member variables. It seems that the Compression object should end up with an NMTOKEN member variable, and the appropriate accessors. (Granted, restriction validation will come at a later date...) This would allow a client to get an instance of the static enumeration, and then ask it for it's value, and set this in the containing Compression class: Compression.setValue(CompressionWKV._compress.getValue()); We've created a WSDL file that shows this, and I will attach along with the generated classes. Also, we would be willing to contribute toolkit modifications to support this if it is not already in the works... (Suggestions on where to start??? :) Thanks! David Hall Hewlett-Packard --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira From ito at src.ricoh.co.jp Mon Aug 2 09:06:40 2004 From: ito at src.ricoh.co.jp (Masanori ITOH) Date: Wed May 6 14:02:21 2009 Subject: PS> Re: PWG-ANNOUNCE> PSI to Begin New Last Call Review In-Reply-To: References: Message-ID: <200408021306.AA00790@macbeth.src.ricoh.co.jp> Hi Mr. Berkema, I had some questions in PSI spec (July 21, 2004). So could you give me answers ? -------------------------------------------------------------------- P.57 5.6.2 FetchNextJob Returns: sendJobNotifications : JobEvents 'A collection of Job Events as defined by the JobEvents element in the Semantic Model [PWG5105.1] Events.xsd.' 'FetchNextJob' is for a single Job. Because the return of this method 'jobURI' indicates a sigle job. But the description of the return is 'A collection of Job Events ...' to explain that there is not a SINGLE job, but are plural jobs. I think a 'collection' does not exist. If a 'collection' exists, that is not a collection of job events ('events' is a plural form), but of job event. ('event' is a singular form.) (The type 'JobEvents' is defined like a collection of Job Event in 'Events.xsd'.) So I think it is good 'A jobEvents element of type JobEvents as defined by the Semantic Model [PWG5105.1] Events.xsd' in that description. -------------------------------------------------------------------- P.60 5.6.4 FetchNextDocumentByPull Returns: sendDocumentNotifications : DocumentEvents 'A collection of Document Events as defined by the DocumentEvents element in Semantic Model [PWG5105.1] Events.xsd.' 'FetchNextDocumentByPull' is for a single Document. If this single method deals with plural documents, how a document can be correspond to its event in a collection of document events ? I think a 'collection' does not exist. If a 'collection' exists, that is not a collection of document events ('events' is a plural form), but of document event. ('event' is a singular form.) (The type 'DocumentEvents' is defined like a collection of Document Event in 'Events.xsd'.) So I think it is good 'A DocumentEvents element of type DocumentEvents as defined by the Semantic Model [PWG5105.1] Events.xsd' in that description. -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue Returns: sendDocumentNotifications : DocumentEvents 'A collection of Document Events as defined by the DocumentEvents element in Semantic Model [PWG5105.1] Events.xsd.' Same as '5.6.4 FetchNextDocumentByPull' . -------------------------------------------------------------------- P.82 7.4 InterfaceIdentifier Line 30 The first character of element name 'InterfaceIdentifier' is a small letter. See '5.3.3 QueryInterfaceDefinition' (P.22) or '5.3.2 QuerySupportedInterfaces' (P.21). ( 'QuerySupportedInterfaces' has plural form of 'interfaceIdentifier', 'interfaceIdentifiers' .) -------------------------------------------------------------------- Some figures of method sequence example have mistakes. Those are in parameters or returns of methods. Fig. 5, 7, 8, 9, 10, 12 -------------------------------------------------------------------- Comments ? Cheers, Masa. ----------------------- Masanonri 'MASA' Itoh RICOH Co., Ltd. Software R&D Center Mr. Berkema, Alan C (R&D Roseville) wrote on Thu, 22 Jul 2004 14:09:37 -0700 ------------------------------------------------------------------------ All, Here are the files, thanks to Ira, Jerry, and Dave! The last call review process begins on 07/23/2004 and will end on 08/16/2004. We will accept e-mail comments during this time period on the psi reflector. ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721.pdf (and .doc) ftp://ftp.pwg.org/pub/pwg/ps/wd/wd-psi10-20040721-rev.pdf (and .doc) Also the events Schema ftp://ftp.pwg.org/pub/pwg/ps/schemas/events-20040721.xsd Last Call Comment resolution meeting tbd at F2F? Thanks, Alan Berkema From thrasher at lexmark.com Wed Aug 4 09:46:41 2004 From: thrasher at lexmark.com (thrasher@lexmark.com) Date: Wed May 6 14:02:21 2009 Subject: PS> WSDL 2.0 documents published as Last Call Working Drafts Message-ID: ----- Forwarded by Jerry Thrasher/Lex/Lexmark on 08/04/2004 09:43 AM ----- FYI....(excerpt from the W3C announcement) The WSDL 2.0 documents have been published as Last Call Working Drafts: Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language http://www.w3.org/TR/2004/WD-wsdl20-20040803/ Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/ Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/ The comment period lasts until October 4, 2004.... From alan.berkema at hp.com Tue Aug 17 14:14:06 2004 From: alan.berkema at hp.com (Berkema, Alan C (R&D Roseville)) Date: Wed May 6 14:02:21 2009 Subject: PS> PSI: LCRC Teleconference August18 @ 8:00AM Pacific Message-ID: Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: PSI-LCRC-comments.pdf Type: application/octet-stream Size: 14320 bytes Desc: PSI-LCRC-comments.pdf Url : http://www.pwg.org/archives/ps/attachments/20040817/a6dc3ee3/PSI-LCRC-comments-0001.obj From imcdonald at sharplabs.com Wed Aug 18 10:22:58 2004 From: imcdonald at sharplabs.com (McDonald, Ira) Date: Wed May 6 14:02:21 2009 Subject: PS> PSI: CHANGED Number - LCRC Teleconference August18 @ 8: 00AM Pacific Message-ID: Hi folks, [As noted in Harry Lewis' agenda for today earlier] PLEASE use the standard IEEE/ISTO conference bridge for the PSI Last Call this morning _and_ for the PWG WG meeting this afternoon (1pm EDT / 10am PDT). Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Thanks - this will avoid confusion with dropping and restarting teleconferences. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ps@pwg.org [mailto:owner-ps@pwg.org]On Behalf Of Berkema, Alan C (R&D Roseville) Sent: Tuesday, August 17, 2004 2:14 PM To: Berkema, Alan C (R&D Roseville); pwg-announce@pwg.org; a PSI pwg.org Subject: PS> PSI: LCRC Teleconference August18 @ 8:00AM Pacific Note: Start Time may be delayed due to other PWG F2F meetings which proceed this call, Please call in at 8:00AM Pacific time anyway Toll Free Phone: 1 866 639-4738 Code: 785-5605 International (or if trouble with above) Phone: 1 574 935-6700 Code 785-5605 Agenda: 1) PSI Last Call Review comments that were received, see attached <> Thanks, Alan Hey all, we will use a new web tool see below: Please do the setup ahead of time and then log in a few minutes before the meeting time. Title: PSI LCRC Time: Wednesday, August 18, 2004 8:00 AM Pacific Daylight Time Duration: 120 minutes Event size: 5 The room for this event is: Room: PSI License pool: HPStandard Room owner: Alan C Berkema (alan.berkema@hp.com) Scheduler: Alan C Berkema (alan.berkema@hp.com) Here are your keys for this event: Presenter: GBANPM4VX Participant: UBT8GVVP9 You can use the following links to enter your event: Presenter: https://www.hpe-learning.com/attend/default.aspx?key=GBANPM4VX Participant: https://www.hpe-learning.com/attend/default.aspx?key=UBT8GVVP9 To test your setup ahead of your event, please use the following link: https://www.hpe-learning.com/testsetup An appointment which you can import into Microsoft(R) Outlook is attached. Thank you for using the HP Virtual Classroom.