Hi Harry,
Inline below.
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: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Monday, August 02, 2004 3:20 PM
To: tfm at pwg.org
Cc: imcdonald at sharplabs.com
Subject: Transform Interface Strawman
Ira, as we had discussed, I think the strawman is powerful in that it limits
the number of interfaces, operations and options.
<ira>
Not in the slides yet is that every operation is REQUIRED
for both Clients and Transformers to support, and every
_parameter_ is also REQUIRED for Clients to supply
</ira>
When you say the TFM interface has "discovery" are you referring to
GetTransformerElements? You are not talking about discovery (existence) of
the transform service, itself... correct?
<ira>
Oops - yes, I meant _service_capabilities_ discovery via
GetTransformerElements.
Actual network device discovery is not solved/solvable
in any application protocol. LDAP, DNS-SD, SLP, etc, are
still needed.
</ira>
How does the client learn the URI to fetch results from? Is this part of
GetJobElements or is it a return on CreateJob?
<ira> If you look at the parameters and _returns_ of
FetchDocumentDataByPull on page 9 of the slides, you'll
see the return 'dataSourceURIs : DataSourceURIs' which
is a list of one or more URIs for the Client to fetch
from (out-of-band). In PSI/1.0 we made it mandatory
that at least one of these URIs was 'http:' or 'ftp:',
to guarantee interoperability.
</ira>
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------