W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2001

RE: Content-Type / charset in RFC2518, deltaV and ACL specs

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 3 Oct 2001 15:30:07 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103F8AC35@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
Following my standard process, after last call, only unanimously
supported changes are made, so Jim's objection to this change will
keep the draft in its last call state, i.e. explicit charset and
encoding values in the examples.

Cheers,
Geoff

-----Original Message-----
From: Jim Whitehead [mailto:ejw@cse.ucsc.edu]
Sent: Wednesday, October 03, 2001 3:13 PM
To: Webdav WG; ietf-dav-versioning@w3.org
Subject: RE: Content-Type / charset in RFC2518, deltaV and ACL specs



> I think there are good arguments on either side, but I personally
> believe that the risk of someone blindly copying the example and
> leaving out a needed charset parameter or an encoding attribute are
> higher than the risk of someone using a non-UTF-8 encoding, but leaving
> in the UTF-8 charset parameter and encoding attributes from the example.

Before we placed the charset parameter in *every* example of the
specification, I found that implementations were not including the charset
parameter at all. Since this would make it very difficult to correctly
implement i18n features later, I added the charset parameter to all
examples.  I still don't think that all implementations use the charset
parameter, or use it correctly, but I do believe it helped.

One thing I learned from the DAV specification was the large normative
effect the examples have.  Developers sometimes code to the examples, not
the specification.

> But I don't feel strongly about this, so if there is working
> group consensus
> that these charset/encoding info should be stripped from the examples
> (or have their values be replaced by "xxxx"), I'm happy to make
> that change
> to the DeltaV spec (assuming that consensus is reached before the
> author 48 hour period has expired :-).

I feel very strongly that the charset values should be left in the DeltaV
specification, with their current values. This is the form the specification
was approved as, and the form in which it passed last call. I would have
raised an issue during last call if these values were not in the
specification.

Furthermore, RFC 3023 ("XML Media Types") states that use of the charset
parameter is STRONGLY RECOMMENDED, and so if we do not use the charset
parameter, the burden of explanation clearly rests on showing why it is
better to omit it, than to include it.

- Jim
Received on Wednesday, 3 October 2001 15:30:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT