- From: Wood, John \(HP Labs\) <johnw@hp.com>
- Date: Mon, 27 Nov 2006 14:07:22 -0000
- To: <connolly@w3.org>, <www-archive@w3.org>
Hi there,
Apologies if you are not the person to mention this to.
I just spotted a discrepancy in the FTP URI defintion on the addressing
page on the W3C website.
Background: In the FTP URI, you can include a statement at the end of
the URI of the form ";type=<typecode>" to indicate what transfer more to
use (e.g. ascii or "image" [binary]).
On the W3C website [1] it states that the type should take the form:
;type = <type-code>
...
The type code is in the format defined in RFC959...
In RFC959 [2], the <type-code> is defined as:
<type-code> ::= A [<sp> <form-code>]
| E [<sp> <form-code>]
| I
| L <sp> <byte-size>
Note these are all capital letters (A, E, I, L) so, for example to
indicate using the "image" mode you would put:
;type=I
However, in RFC1738[3], it states
...<typecode> is one of the characters "a", "i", or "d"...
Here they are indicated as lower case.
So anyway, there is a discrepancy here. Obviously I guess the simple
answer is to go with RFC1738 as it is more recent.
Just wondered if you had any input on this?
Regards,
John Wood
[1] http://www.w3.org/Addressing/URL/4_1_FTP.html
[2] http://www.w3.org/Protocols/rfc959/5_Declarative.html#z9
[3] http://www.faqs.org/rfcs/rfc1738.html
Received on Tuesday, 28 November 2006 07:23:30 UTC