----- 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 -----
This archive was generated by hypermail 2b29 : Tue Jun 22 2004 - 12:45:59 EDT