Hi,
Regarding <http://tools.ietf.org/html/draft-shafranovich-mime-sql-03>,
I think the document should be more clear that there are many variants
of the SQL format and the media type is intended as "umbrella type" for
them all, for instance, the Abstract should refer to, say, "variants of
the Structured Query Language" and not "the Structured Query Language".
The "Published specification" field in the registration template should
also note that there exist individual specifications for individual de-
rived formats (like "SQL As Understood By SQLite").
The proposed type has an optional 'charset' parameter. As I understand
it, SQL formats typically indicate character encoding, if at all, in
proprietary ways inline in SQL resources, or entirely out of band, and
for exchange, everybody seems to be settling on UTF-* encodings, so the
parameter is unlikely to serve a useful purpose, but does create some
problems, like how implementations should handle HTTP responses where
the HTTP header says `Content-Type: application/sql;charset=iso-8859-1`
while UTF-8 is specified inline. I think the type would do better with-
out this parameter.
Whether it is kept or not, the media type registration should not de-
fine a default. If the character encoding is not explicitly specified,
then it is unknown, and it should be up to individual applications and
their conventions for their SQL variants how to handle that case.
regards,
--
Björn Höhrmann · mailto:bjoern(_at_)hoehrmann(_dot_)de ·
http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/