PS> [PSI]: next call 03/18/03 mins 3/11

PS> [PSI]: next call 03/18/03 mins 3/11

BERKEMA,ALAN C (HP-Roseville,ex1) alan.berkema at hp.com
Thu Mar 13 18:03:43 EST 2003


Teleconference details:

NEXT: Tuesday March 18 2003 (USA)

Time: 8 AM (US PST)

Number: 866-639-4738
Participant PIN: 7855605

If Trouble with Above Try:
Toll Access Number: 574-935-6700
Participant PIN: 7855605

Agenda: 
1) closeDocument
2) The Mandatory vs. Supported language action (see 1.1 below)
3) FetchJobs filter example note (see 1.3 below)
4) Other Spec. Changes Review
5) Ready for Last Call


Meeting 03/04/03

  PSI Working Group:
  *Alan Berkema		*Dave Hall        *Gail Songer
  *Jerry Thasher		 Harry Lewis	*Ted Tronson
   Peter Mierau		 Peter Zehler	 Paul Tykodi
  *Bob Taylor	 	 Don Levinstone	 Lee Farrell
   Don Wright	 	 Kirk Ocke		*Ira Mcdonald
   Amir Shahindoust	 Alain Regnier	 Mike Haller
  *Darrell Hopp
  * = attendance
 
Minutes: 
Agenda: 
1) Alain's e-mail Questions
2) addDocumnetByPush review
3) Ready for Last Call
4) ?

2) Once addDocumnetByPush is submitted no more addDoc operations 
permitted until data has completed. Other methods such as cancel or 
status are OK. closeDocument indicates that the data transfer has 
completed. Still some discussion pending on this method.

1) Alain's questions

  1.1) What is meant exactly by Method Support in the specification?
  Do we talk about the "implementation" or the "utilization" of an
  interface or a method?
 
  If we talk about the implementation, I don't really see why "CreateJob"
  and "CloseJob" are mandatory for Clients. (Why should Clients implement
  these methods?)

Method support means the method shall be implemented. Dave will fix the
specfifcation
to state the intent more clearly in terms of shall be implemented and client
is
required to call etc.

  1.2) 5.5.6 Regarding the filtering criteria of GetJobs, I'm not sure why
we have to
  support element by element filtering. Isn't "group of elements"
  filtering enough?
  Do we really need such a granularity?
  It makes implementation more complex, and I'm not sure the gain in term
  of bandwidth, or XML processing is that good. (and you have to process
  the XML document anyway)

Believe that the level of filtering is appropriate. The complexity is in
the Sevice and having less granularity may actually make it more complex
for the Client.  

  1.3) 5.12 for FetchJobs, what else than JobURI, JobAccountingUserID and
  JobPassword might be needed in the jobFilter?
  Do we expect the Print Service to do any kind of filtering on other
  elements?

These are not the only possibilities. The example should note that these
values
are the only possibilities.
 
3) Determine if the spec is ready to begin a 4 week last call cycle
F2F April 4 2003 
  Line by line editorial review
  Last Call Straw Vote - need concrete comments to vote against
  Interop Proto testing plans and schedule
  
3/24 is the last date to post slides other presentations for F2F

Action: Prepare PSI presentation for FSG F2F
Owner: Dave & Alan
Status:

4) Get Jobs - improved language
Only the jobs that the user is authorized to view shall be returned.



More information about the Ps mailing list