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.,
<xsd:schema targetNamespace="http://www.pwg.org/schemas/sm/1.0/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.pwg.org/schemas/sm/1.0/">
(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
This archive was generated by hypermail 2b29 : Mon Jul 12 2004 - 01:18:41 EDT