RE: [stdsreg] Metadata Specification v2.9 - Language

[Makx Dekkers <mail@makxdekkers.com>]

Good point. We had the same comment in the ballot of Dublin Core
as Z39.50 in NISO. The text under the Language element now reads:

Comment: Recommended best practice is to use RFC 3066 [RFC3066],
         which, in conjunction with ISO 639 [ISO639], defines
         two- and three-letter primary language tags with
         optional subtags.  Examples include "en" or "eng" for
         English, "akk" for Akkadian, and "en-GB" for English
         used in the United Kingdom.

This also acknowledges the fact that RFC1766 has been obsoleted
by RFC3066 (see http://www.ietf.org/rfc/rfc3066.txt). Note that
the country code should be uppercase, so it is en-GB, not en-gb.

Makx.

> -----Original Message-----
> From: Ray Gates (home) [mailto:gatesray@rogers.com]
> Sent: Wednesday, 21 August 2002 02:40
> To: Stdsreg
> Subject: [stdsreg] Metadata Specification v2.9 - Language
> 
> 
> 
> In looking at the recently posted specification, I notice an 
> error in the Comment on Language.
> 
> The Comment states:
> "For example, "en" for English, "fr" French or "en-uk" for 
> English used in the United Kingdom."
> 
> In fact, if you check the reference given for country codes, you 
> will see that the code for the United Kingdom is "gb".
> 
> [I assume they don't expect to be united indefinitely, and will 
> eventually revert to Great Britain ;)]
> 
> Perhaps it would be safer to choose "au" or "us".
> 
> Regards,
> Ray Gates
> Editor,  ISO/IEC 11179-3
>