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 at sharplabs.com
-----Original Message-----
From: Masanori ITOH [mailto:ito at src.ricoh.co.jp]
Sent: Thursday, July 15, 2004 3:03 AM
To: McDonald, Ira
Cc: 'ps at 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 at 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., <xsd:complexType name="JobEvents">) 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.
------------------------------------------------------------------------