- From: Richard Ishida <ishida@w3.org>
- Date: Wed, 27 Aug 2014 18:37:47 +0100
- To: "Phillips, Addison" <addison@lab126.com>, Larry Masinter <masinter@adobe.com>
- CC: "www-international@w3.org" <www-international@w3.org>
Larry, Anne, all, The spec has not yet been changed, but the wording proposal previously suggested by Anne was that shown below, ie.: "Historically encodings and their specifications (if any) were kept track of by the IANA Character Sets registry. For the purposes of specifications using this specification, that registry is obsolete. " In various discussions with others, the word 'obsolete' still caused difficulties, so I discussed alternatives with Addison and a number of people. After several iterations, we proposed the following text to Anne for the third paragraph in the Preface at http://www.w3.org/TR/2014/WD-encoding-20140603/#preface: "User agents actually use a subset of the IANA Character Sets registry in a particular way. This specification documents this to establish interoperability on the Open Web Platform. Specifications and applications using this specification must restrict themselves to the encodings as documented in this specification." Anne was not comfortable with that, but did think that an alternative suggested by Addison could work. That would be to replace the third paragraph with: "Historically encodings and their specifications (if any) were kept track of by the IANA Character Sets registry. For the purposes of specifications using this specification, that registry no longer relevant." The i18n WG felt that this last attempt was workable. Please let us know asap whether we can settle on this wording and move on. Thanks, RI On 09/08/2014 17:35, Phillips, Addison wrote: > Hello Larry, > > In the reply below, it seems that I erred in which text recommendation > we wanted to make. The correct recommended text is: > > -- > > "For the purposes of specifications using this specification, that > > registry is obsolete." > > -- > > This text has the advantage of not trying to define what the Web is nor > impose artificial boundaries on where the Encoding specification should > be used while simultaneously avoiding saying anything about the status > of the IANA Charset registry (which all agree is beyond the remit of > Encoding as a specification). > > I regret the error. Please let us know if this text satisfies your comment. > > Addison (for I18N) >
Received on Wednesday, 27 August 2014 17:38:19 UTC