> > Besides, most applications looking for "en-US" should look for
> "en" if it
> > can't find American English, then look for "en-*", then
> "i-default", then
> > something with no language, then either assume nothing is available or
> > prompt the user with which languages it can provide information in (the
> > latter would depend strongly on the purpose of the application). Basic
> > send-strict receive-liberal surely?
> Excuse me...DC is not just an English dialects and spelling fun club.
> You may infer xml:lang="en-US" ===> xml:lang="en"
> No such rule is true for xml:lang="de"
I disagree. Indeed my concern is to enable such rules to work for "de" and
for other languages that aren't English.
If an application was looking for *de* literals and failed to find them,
failed to find de-1901, de-1996, de-AT, de-CH, de-DE, de-AT-1901,
de-AT-1996, de-CH-1901, de-CH-1996, de-DE-1901, de-DE-1996 or any other
German literal (or i-default if i-default was considered acceptable by the
application), and then failed to find any other acceptable language (say for
a user who understood both German and French) then
<dc:date>2003-03-18</dc:date> could be used by that application but <dc:date
xml:lang="en-US">2003-03-18</dc:date> could not since it is foreign (unless
the specific application had knowledge that language wasn't relevant on such