Hi Masa,
I agree that the PSI spec (and SM spec) should
explicitly state the location of SM schema.
Harry Lewis and I both think that current global
(PWG std) and local (no union or other problems)
copies of entire SM/1.0 w/ all approved extension
schema should be _permanently_ available on the
authoritative PWG FTP site, because:
- HTTP links are not guaranteed stable on PWG server
- FTP links _are_ guaranteed stable on PWG server
I personally do not like storing actual schema at
the URL in 'targetNamespace', which SHOULD be an
entirely opaque identifier.
And I do not think that schema themselves should
specify standard SM schema location URLs. But,
I think it would be OK in the schema themselves
for a comment or an annotation to state stable
FTP directory URLs (i.e., documented for people
but safe from machine interpretation).
Comments?
Cheers,
- Ira
PS - Pete Zehler is going on vacation for a week,
so we may not hear from him for a little while.
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
-----Original Message-----
From: Masanori ITOH [mailto:ito@src.ricoh.co.jp]
Sent: Friday, July 16, 2004 2:47 AM
To: McDonald, Ira
Cc: 'ps@pwg.org'
Subject: Re^2: PS> Last call ready Events schema v0.41 (14 July 2004)
Hi Mr. McDonald,
Thank you for quick reply.
Please see my comments inline below.
Thanks,
Masa.
-----------------------
Masanonri 'MASA' Itoh
RICOH Co., Ltd. Software R&D Center
Mr. McDonald, Ira wrote on Thu, 15 Jul 2004 09:19:40 -0700
------------------------------------------------------------------------
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.
<Masa> O.K.
(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.]
<Masa> I got same advice from Mr. Zehler directly. > Thanks, Zehler-san.
But I worry about how an implementor knows where schma
file are kept.
He knows the Semantic Model schemas are used in PSI to
read the PSI spec. But he can't get the schema files.
Because true storage place of the schema files is not
shown in PSI spec. In the PSI web page he can get WSDLs,
but don't notice needs of SM schema files. Because there
is no description of the schema files and no link to them.
(only the link to top page of SM exists).
Currently there is the description only in PSI WSDL files.
(Of cource there may be a chance that he glances at SM web
page or reads carefully reference to SM, e.g. '9 Normative
References', in PSI spec, and can get files in SM web page.)
If hard paths ('namespace'? part in URL of the schema files)
should be deleted in WSDL files, I think it is need to show
where schema files can be got.
How do you think ?
Anyway I will use only file names in my WSDLs as your and
Mr. Zehler's advice.
(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.
<Masa> I understand. I will use 'Events.xsd' in new WSDLs.
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@sharplabs.com
-----Original Message-----
From: Masanori ITOH [mailto:ito@src.ricoh.co.jp]
Sent: Thursday, July 15, 2004 3:03 AM
To: McDonald, Ira
Cc: 'ps@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@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.
------------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Fri Jul 16 2004 - 11:21:40 EDT