Here are the raw notes from todays call.
I'll clean it up some for the F2F.
See ya on Tuesday
Alan
PSI Meeting schedule
Teleconference details 2002:
Date: Tuesdays
Tuesday April 23 (USA)
No Call April 16 (F2F meeting)
Through April 23 USA)
Time: 8 AM (US PST)
404 774-4112 (T774-4112)
ID: 55605
See webex info below
Attendees:
Alan Berkema Paul Tukodi Dave Hall
Jerry Thasher Harry Lewis Ira Mcdonald
Kirk Ocke Peter Zehler
Agenda:
1) Off-Ramp Identifier
2) PSI IPP mapping
3) F2F Agenda Topic
3.1) Off-RampIdentfier-
SOAP endpoint preferred. PORT 9100 & UNC legacy.
Add an SNMP endpoint.
Responsibility of the PS to contact the Off-Ramp and get its
device attributes. Method varies based on Off-RampIdentfier.
3.2) Document reference -
Add in BPP reference attributes. OBEX has doc type in header in the
mime type field. Need to add this to document reference.
3.3) IPP to PSI mapping. Purpose:
A) Insure that we have not missed anything
B) Semantic Alignment
C) Leverage back.
This section of the spec is like a work sheet to help us work
through details of PSI. It may remain as an Appendix.
3.4) RUI or not?
3.5) Get JOBs per user or all jobs operation. Functionality &
methods
3.6) Persistence policy. PS needs to know when the job is actually
printed. Keep job record for history. Job itself should hang around
for some default time 30 secs/60 seconds. Use Job MIB example.
3.7) Really web based job control. Extensible attributes, via
browser.
3.8) Programmatic method for extended attributes. How does client
know if the Off-Ramp supports these extended attributes? And then know if
some attributes are or are not supported. Meta data -Name, syntax, legal
values, text description of what the legal values do. Make it the
standard way for all attributes as well as extended attributes. Name
required rest optional.
3.9 Mechanism for mapping between PS, Off-Ramp & Client. Knowing
what PS the client should talk to. PS to printer mappings.
3.10) Attributes move from object to XML. Combine Base and extended.
Name space for base, use different name space for vendor specific.
Allows for greater flexibility and works with current tool kits.
Also works better with concepts introduced in 3.8.
Caveat is that it places the burden of validation on the receiving
device. Group felt this was a reasonable trade off, the receiving device
needs to be aware that a sending device could send bad attributes (or
values).
List of known work items:
1) Query Interface for extensibility needs work.
2) Off-Ramp Identifier needs to be defined
3) Security Model needs work
4) Job Status & Content Status needs to be defined.
5) Need to rev RequiremntsRequirements doc.
6) PSI overview section needs to be filled out
-----------
webex info
We will also use an on line tool called webex,
if you have not used this before, setup up by
following the First Time Users instructions.
Do this in advance of the meeting.
-------------------------
FIRST TIME USERS
-------------------------
For fully interactive meetings, including the ability
to present your documents and applications, a one-time
setup takes less than 10 minutes. Click this URL to set up now:
Then click New User.
-------------------------
On Tuesdays use:
http://hp.webex.com
Then click join unlisted meeting.
Use the info below:
-------------------------
MEETING SUMMARY
-------------------------
Name: PSI Meeting
Date: 4/2/2002
Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada
Meeting Number: 22694237
Meeting Password: mypsi
Host:
Alan Berkema
1(916)7855605
This archive was generated by hypermail 2b29 : Tue Apr 09 2002 - 12:36:45 EDT