OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Official ISO 639 changes

[ Lists Home | Date Index | Thread Index ]
  • From: John Cowan <cowan@locke.ccil.org>
  • To: elharo@metalab.unc.edu (Elliotte Rusty Harold)
  • Date: Tue, 25 Apr 100 18:47:34 -0400 (EDT)

Elliotte Rusty Harold scripsit:

> Whether it's important or not, all XML 1.0 conforming parsers today 
> do check xml:lang values, at least to the extent of making sure 
> they're two letters and not three. Failing to do so is a 
> well-formedness error because of Production 35.

Oddly enough, this is not true.  Production 35 is not reachable from any
other production, and there is no "must" language in clause 2.12
(except "must be declared in valid documents", which is not relevant).
A document meets the technical definition of well-formedness in 
clause 2.1 even if its xml:lang attribute values are crud.

One view is that conforming to production 35 (or, equivalently, to the
rules in RFC 1766) should be made a validity (not well-formedness)
constraint.  The other view is that productions 35-38 never were
normative and should be disposed of in favor of motherhood language,
something like "xml:lang attribute values should conform to RFC 1766
or its successor."

No decision has been reached.


-- 
John Cowan                                   cowan@ccil.org
       I am a member of a civilization. --David Brin

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS