Re: SVG12: RFC 3066 reference

* Chris Lilley wrote:
>AP> According to LTRU correspondents in recent days, the solution is to
>AP> cite RFC 3066's (or its successor's) official IETF status, which is
>AP> as BCP 47. BCP 47 will always be the most current version of
>AP> language tags, no matter what the RFC number assigned. Thus a better
>AP> reference might be "IETF BCP 47, currently represented by RFC 3066".
>
>Excellent suggestion, the specification has been amended to say [BCP47]
>instead of [RFC3066] and the references section has the wording you
>suggest.

Thanks.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

Received on Thursday, 29 December 2005 10:50:42 UTC