Hi Mr. McDonald,
I'm sorry to send my comment after PSI telecon.
I'm worry whether some problems will occur when some Event
schemas will be extended and be formally added to the Semantic
Models. (That will be the schemas before you reduced for PSI.)
Will the version of namespace be changed at that time ?
I'm not sure whether problems will occur ....
If there is no problem, I agree with you.
Please add the namespace definition of SM/1.0 as 'targetNamespace'
in the schema file, or the schemas are in PSI namespace when
imported in WSDLs.
Cheers,
Masa.
-----------------------
Masanonri 'MASA' Itoh
RICOH Co., Ltd. Software R&D Center
------------------------------------------------
Mr. McDonald, Ira wrote on Fri, 2 Jul 2004 10:02:40 -0700
Hi,
[By the way, Jerry Thrasher has offered to convert my draft
Std Print System Events from HTML to Word - thanks, Jerry!]
The namespace will be PWG Semantic Model/1.0, just like all
currently approved schemas. The internal version tag will be
1.x (something), but that's _not_ the namespace.
So, the 'PrinterEvents', 'JobEvents', and 'DocumentEvents'
elements can be referenced and used normally by PSI/1.0.
_AFTER_ the Events spec and schema are formally approved
(as PWG Candidate Standards), a copy of Events schema
will be stored in the official directory:
http://www.pwg.org/schemas/sm/1.0/
OK?
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: Friday, July 02, 2004 5:41 AM
To: McDonald, Ira
Cc: Berkema, Alan C (R&D Roseville); 'ps@pwg.org'; Hall, David M; Alain
Regnier
Subject: Re^2: Important PSI Teleconference 5/26/04 at 2:00PM
Hi Mr. McDonald,
I'm so sorry to be late for this reply to you.
I've been a 'ROM' beacuse of my many pressing works.
Thank you for this excellent summary of agenda.
I can understand the content of the meeting very much.
And I have a question.
When "Standard Print System Events" will be voted
as you mentioned as follows, what will be the 'Namespace'
of the schema file (now posted in the ftp site as
'events-20040621.xsd') for that working draft ?
There is no definition of 'targetNamespace' in the file.
Is it same as the one of the Semantic Model or of PSI ?
If the schema definition is temporary and for PSI,
is it same as the 'Namespace' of PSI ?
Or if the schema definition is temporary for next addition
to the Semantic Model, is it same as the 'Namesapce' of SM ?
If so, I guess some problem will occur when some original
Events before removing will be added.
How do you think ?
Thank you,
Masa.
-----------------------
Masanonri 'MASA' Itoh
RICOH Co., Ltd. Software R&D Center
Mr. McDonald, Ira wrote on Fri, 28 May 2004 07:00:40 -0700
Hi,
At yesterday's meeting, we decided to simplify my recent
"Standard Imaging Systems Events" draft and remove _all_
of the multi-function/non-printer events and classes.
I will very shortly issue "Standard Print System Events"
as a PSI working draft. We will review it on the PSI
mailing list (and in PSI telecons, if necessary).
PWG people agreed to plan to hold an "Interim Plenary"
(by telecon) in July, in order to:
(1) Complete adoption of PWG Process 2.0
(2) Complete 'last call' and then start Formal Approval
(PWG-wide vote) of "Standard Print System Events".
Then PSI/1.0 could be revoted for adoption.
So we plan to keep the "SendXxxEvent" methods in PSI/1.0
and the Events schema should be approved for addition
to the PWG Semantic Model to support those methods.
Cheers,
- Ira
PS - Separately, WIMS WG has decided _not_ to work on the
multi-function imaging system model, but instead to call
for a BOF in the August face-to-face on this topic. This
might then lead to writing a charter for MFISM working
group, development of requirements, and finally return to
my recent draft Imaging System Model spec (I hope). Which
would delay work on WIMS support for any non-print systems
until sometime in calendar 2005, it would appear.
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, May 27, 2004 3:44 AM
To: Berkema, Alan C (R&D Roseville)
Cc: Hall, David M; McDonald, Ira; Alain Regnier
Subject: Re: Important PSI Teleconference 5/26/04 at 2:00PM
Hi Mr. Berkema,
Thank you for your notice.
But I couldn't attend that meeting becuase I read your E-mail
after it. Sorry.
(I might not be able to attend because it started early morning
in Japan even if I read your E-mail before the meeting.)
If there is the minutes, would you send them for me ?
Thank you,
Masa
-----------------------
Masanonri Itoh
RICOH Co., Ltd. Software R&D Center
Mr. Berkema, Alan C (R&D Roseville) wrote on Tue, 25 May 2004 10:06:31 -0700
-----Original Message-----
Dave, Mr. Itoh, Alain, and all,
The PWG will discuss eventing and the impact on PSI at
2:00PM PDT on 5/26/04 during the current F2F. This could
have a dramatic impact on the PSI schedule.
Please call in if you can.
Dial In: 1-866-365-4406
Toll #: 1-303-248-9655
Passcode: 2635888#
Thanks,
Alan
-----
Alan Berkema
Senior Engineer Scientist
Connectivity Roseville, CA
Hewlett-Packard Company
Tel: 916 785-5605
e-mail: aberkema@hp.com
-----Original Message-----
From: Masanori ITOH [mailto:ito@src.ricoh.co.jp]
Sent: Wednesday, May 19, 2004 11:07 PM
To: Berkema, Alan C (R&D Roseville)
Cc: Hall, David M; McDonald, Ira; Alain Regnier
Subject: Re^2: For revision of PSI specification document (2004/01/13)
Hi Mr. Berkema,
Thank you for your apology.
That's no problem. Never mind, please.
I thought I should send this report to Mr. Hall rather than you because
he is the editor of PSI-WG.
But I decided to send it to you because my some E-mails could not be
reached to Mr. Hall when I posted to him and I received the error
message automatically sent from HP mail server, that is "Delivery to the
following
recipients failed. david_hall3@am.exch.hp.com".
If that is not appropriate, I have to apologize to you for that.
Cheers,
-----------------------
Masanonri Itoh
RICOH Co., Ltd. Software R&D Center
Mr. Berkema, Alan C (R&D Roseville) wrote on Wed, 19 May 2004 10:06:38
-0700
-----Original Message-----
Sorry about the type in Mr. Itoh's name below, accidentally hit the send
before reviewing regards, Alan
-----
Alan Berkema
Senior Engineer Scientist
Connectivity Roseville, CA
Hewlett-Packard Company
Tel: 916 785-5605
e-mail: aberkema@hp.com
-----Original Message-----
From: Berkema, Alan C (R&D Roseville)
Sent: Wednesday, May 19, 2004 9:20 AM
To: 'Masanori ITOH'
Cc: Hall, David M; McDonald, Ira; Alain Regnier
Subject: RE: For revision of PSI specification document (2004/01/13)
Mr Itch,
Thanks for your careful review,
Dave can you make these editorial corrections for the next re-vote?
Thanks,
Alan
--------- Alan Berkema Senior Engineer Scientist Connectivity Roseville, CA Hewlett-Packard Company Tel: 916 785-5605 e-mail: aberkema@hp.com
-----Original Message----- From: Masanori ITOH [mailto:ito@src.ricoh.co.jp] Sent: Monday, May 17, 2004 7:59 PM To: Berkema, Alan C (R&D Roseville) Cc: Hall, David M; McDonald, Ira; Alain Regnier Subject: For revision of PSI specification document (2004/01/13)
Hi Mr. Berkema,
I found some mistakes in the document of PSI specification (2004/01/13). So I inform you, chairperson of PSI-WG about them.
If PSI-WG will have chance of revision (e.g. when specification of 'UnsupportedElements' may be changed or new different return name from 'UnsupportedElements' may be defined ), please refer to them.
Will you please point out any mistakes to me in this report.
Cheers,
----------------------- Masanonri Itoh RICOH Co., Ltd. Software R&D Center
-------------------------------------------------------------------- P.9 JobControlInterface 'GetJobs'
CHANGING 'JobContainter' (misspelling)
i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.10 TargetDeviceSupportInterface 'FetchNextDocumentByValue'
DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?)
i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.20 5.3.2 QuerySupportedInterfaces Returns: interfaceIdentifier:InterfaceIdentifierContainer
MAKING the PLURAL FORM 'interfaceIdentifier' (cf. P.25 'targetDeviceIdentifiers:TargetDeviceIdentifierContainer' of '5.4.3 GetKnownTargetDevices' )
i.e. interfaceIdentifier : InterfaceIdentifierContainer -> interfaceIdentifiers : InterfaceIdentifierContainer ^ -------------------------------------------------------------------- P.21 5.3.3 QueryInterfaceDefinition Exceptions: 'Description' of 'ClientErrorUnsupportedInterface'
CHANGING '<secure>' (cf. P.84 '7.4 InterfaceIdentifier' )
i.e. <secure> -> <sec> -------------------------------------------------------------------- P.32 5.5.2 CreateJob Parameters: description of 'requestedTargetDeviceDataType'
What is 'a ProcessingRequestUnsupported exception' ? Is it the older version of 'ClientErrorAttributesOrValuesNotSupported' exception ? -------------------------------------------------------------------- P.41 5.5.8 GetJobs GetJobs(jobFilterElements:Job, ... , unsupportedElements : UnsupportedElements
CHANGING 'JobContainter' (misspelling)
i.e. ...... jobs:JobContainter, ...... -> jobs:JobContainer ^^^^^^^^^ -------------------------------------------------------------------- P.62 5.6.6 FetchNextDocumentByValue FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...
DELETING 'Boolen' (Duplicate type definition of 'documentNumber' ?)
i.e. FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, Boolean ...... -> FetchNextDocumentByValue(jobURI:URI) : documentNumber:int, ...... -------------------------------------------------------------------- P.77 7.2 Target Device Identifier
CHANGING 'see appendix (X)'
i.e. see appendix (X) -> see appendix A -------------------------------------------------------------------- P.79 7.3 Reference
CHANGING 'see appendix (X)'
i.e. see appendix (X) -> see appendix A --------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Wed Jul 07 2004 - 05:06:51 EDT