Hi Joe,
You reference RFC 3066 (January 2001) for natural language tag
values.
But it was obsoleted by RFC 4646 (September 2006) and in turn
obsoleted by RFC 5646 (September 2009).
RFC 3066 used ISO language codes directly. But RFC 5646 uses
the IANA Registry of Language Subtags (filled from 5 ISO registries)
to *construct* natural language tags.
In your next version, there should be an up-to-date, formal, normative
reference (missing in this version).
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
winter:
579 Park Place Saline, MI 48176
734-944-0094
summer:
PO Box 221 Grand Marais, MI 49839
906-494-2434
On Mon, Jun 7, 2010 at 8:46 AM, Murdock, Joe <jmurdock at sharplabs.com> wrote:
> I've posted a new versionm of the NAP binding specificaton:
>>ftp://ftp.pwg.org/pub/pwg/ids/wd/wd-ids-napsoh10-20100607.doc>ftp://ftp.pwg.org/pub/pwg/ids/wd/wd-ids-napsoh10-20100607.pdf>> This version adds a HCD_Natural_Language attribute for localization. This
> change completes action item #38
>> Joe
>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> _______________________________________________
> ids mailing list
>ids at pwg.org>https://www.pwg.org/mailman/listinfo/ids>>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.