Document: draft-shafranovich-mime-csv-03.txt
Review: Joel M. Halpern
Date: 25 mars 2005 

This document is nearly ready for publication as an Informational RFC.
There is one small apparent BNF bug, one question, and one clarificaiton.

The BNF for 'escaped" does not list COMMA in the characters that can
be included in the double-quoted string.  The early text (and common
sense) indicates that comma needs to be able to appear there.  (Note
also that the CRLF in the list of permitted characters is redundant
given that CR and LF already appear.  Just change that to COMMA.)

I am not clear as to whether an Informational document can be used to
create an IETF tree MIME type.  RFC 2048 says "RFC publication" which
this clearly is.  It also says "requires standards-track processing"
which this clearly is not.

Also, if the option of a header line is going to be described, then
the text ought to indicate that recognition or expectation of such a
header line is an application specific or local matter not covered by
the format definition.  (There is no way for a computer to tell
looking at CSV content according to these rules whether the first line
is header or content.)