Ira,
good comments. The "type" attribute was related to the document format,
not the FTP transfer mode, and it was removed since "document-format" is
specified elsewhere. However, you make a good point, namely, that if the
client knows that the transfer mode should be text or binary it would be
useful to specify it. So, I propose adding a "type" attribute to the "ftp"
element with those semantics (will not include directory lookup since that
is not applicable).
I'm not sure that the IANA Charset is needed. I think simply allowing a
client to specify text/binary is sufficient.
Kirk
-----Original Message-----
From: McDonald, Ira [mailto:imcdonald@sharplabs.com]
Sent: Wednesday, June 05, 2002 1:43 PM
To: 'Ocke, Kirk J'; 'a PSI pwg.org'
Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific
Hi Kirk,
You removed 'type' from 'ftp'? Standard FTP URLs have defined
a 'type' parameter (see RFC 1738, pages 7 to 8), which is used to
distinguish a directory lookup from ascii or binary file transfer.
Don't we need the IANA charset (if known) and the text/binary mode
for transfer of FTP resources in PSI (note that depending on filename
extensions in the FTP resource is unreliable for determinate selection
of text/binary mode).
Cheers,
- Ira
----------------------------------
[excerpt from RFC 1738, pages 7 to 8]
3.2.2. FTP url-path
The url-path of a FTP URL has the following syntax:
<cwd1>/<cwd2>/.../<cwdN>/<name>;type=<typecode>
Where <cwd1> through <cwdN> and <name> are (possibly encoded) strings
and <typecode> is one of the characters "a", "i", or "d". The part
";type=<typecode>" may be omitted. The <cwdx> and <name> parts may be
empty. The whole url-path may be omitted, including the "/"
delimiting it from the prefix containing user, password, host, and
port.
The url-path is interpreted as a series of FTP commands as follows:
Each of the <cwd> elements is to be supplied, sequentially, as the
argument to a CWD (change working directory) command.
If the typecode is "d", perform a NLST (name list) command with
<name> as the argument, and interpret the results as a file
directory listing.
Otherwise, perform a TYPE command with <typecode> as the argument,
and then access the file whose name is <name> (for example, using
the RETR command.)
Within a name or CWD component, the characters "/" and ";" are
reserved and must be encoded. The components are decoded prior to
their use in the FTP protocol. In particular, if the appropriate FTP
sequence to access a particular file requires supplying a string
containing a "/" as an argument to a CWD or RETR command, it is
necessary to encode each "/".
-----Original Message-----
From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com]
Sent: Tuesday, June 04, 2002 12:27 PM
To: Ocke, Kirk J; 'a PSI pwg.org'
Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific
Here is the updated reference.xsd with the following changes. 1)
ipAddressType Changed to hostType, 2) type attribute removed, 3) removed
referenceRunList, 4) Did not change ip_addr attribute since the
ipAddressType defines an element, 5) did not add annotations refereing to BT
BP Profile.
-----Original Message-----
From: Ocke, Kirk J [mailto:KOcke@crt.xerox.com]
Sent: Tuesday, June 04, 2002 9:47 AM
To: 'a PSI pwg.org'
Subject: RE: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific
Updated reference.xsd and offramp.xsd
Kirk
-----Original Message-----
From: BERKEMA,ALAN C (HP-Roseville,ex1) [mailto:alan_berkema@hp.com]
Sent: Thursday, May 30, 2002 5:24 PM
To: BERKEMA,ALAN C (HP-Roseville,ex1); 'a PSI pwg.org'
Subject: PS> [PSI]: minutes 5/28, next 6/4 8:00:am Pacific
*NOTE NEW phone number and webex number*
PSI Meeting schedule
Teleconference details 2002:
Date: Tuesdays
Tuesday June 4 (USA)
Through June USA)
Time: 8 AM (US PST)
650-690-9360 ID: 55605 (T348-9360)
See webex info below
Attendees:
Alan Berkema Gail Songer Dave Hall
Jerry Thasher Harry Lewis Ted Tronson
Peter Mierau Peter Zehler Paul Tykodi
Bob Taylor Don Levinstone Lee Farrell
06/04/02 Agenda
1) review Target Device Identifier and Reference schema
2) Spec updates with attributes?
3) Review actions
05/28/02
Agenda:
1) Review PWG attribute schemas.
Minutes:
1) Peter walked us through the XML schema for IPP attributes.
Need to figure out exactly how these fit into the PSI spec.
05/21/02 Actions:
1) Dave to send Alan latest versions of psi_spec and psi to post.
2) Peter to post and announce template attributes to new PWG location
Status: Done
3) Kirk to send Alan or post latest Target Device & Reference schema
Actions from F2F:
1) Define Off-Ramp Identifier Schema - Dave & Kirk
Status: Needs Review
2) Add Document Reference as discussed to next rev of spec. - Dave
Status: Kirk working on this, needs review.
3) Send out class attribute structure - Peter
Status: Done.
4) Send out Status schema - Peter
5) Define Job Attributes for Get Jobs - Peter
Status: Done
6) Look at UPDF for Extended Attribute Definition - all
Actions from call -
7) IPP returns status from it's operations.
How does PSI WSDL status happen from exceptions thrown via
SOAP when done with Java or C etc? May need an explicit status
return value - Dave
-----------
webex info
We will also use an on line tool called webex,
if you have not used this before, setup up by
following the First Time Users instructions.
Do this in advance of the meeting.
-------------------------
FIRST TIME USERS
-------------------------
For fully interactive meetings, including the ability
to present your documents and applications, a one-time
setup takes less than 10 minutes. Click this URL to set up now:
Then click New User.
-------------------------
On Tuesdays use:
http://hp.webex.com
Then click join unlisted meeting.
Use the info below:
-------------------------
MEETING SUMMARY
-------------------------
Name: PSI Meeting
Date: 4/2/2002
Time: 8:00AM, (GMT -08:00) Pacific Time, USA & Canada
Meeting Number: 22027801
Meeting Password: mypsi
Host:
Alan Berkema
1(916)7855605
This archive was generated by hypermail 2b29 : Thu Jun 06 2002 - 08:58:18 EDT