- From: François Yergeau <francois@yergeau.com>
- Date: Thu, 23 Mar 2006 10:25:39 -0800
- To: public-xml-core-wg@w3.org
This made me take a new look at the XML namespace document, located at http://www.w3.org/XML/1998/namespace. It turns out to need a little brushing up: -------------------- Section "Namespace policy" This should be "Namespace *change* policy", as this is what it specifies (correctly as per the draft finding: "Specifications ... SHOULD explicitly state their policy with respect to changes in the names..."). -------------------- Section "Related Resources" Herein this sentence: "The value of the xml:lang attribute must be as specified by RFC 1766 or its successors, or be empty." RFC 1766 has been obsoleted a long time ago, and the XML spec has pointed to RFC 3066 since (I think) 2nd edition. RFC 3066 has now been obsoleted, but unfortunately its successor does not yet have an RFC number and we can't practically point to it at this time. The best option is probably to point to IETF PCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt, which currently returns RFC 3066 but will return RFC3066bis as soon as publihsed. -------------------- Section "Language Codes for use in xml:lang" I don't quite understand why we try to partially (and wrongly, since RFC3066bis) describe language tags here, instead of relying on the authoritative reference. Furthermore, some of the info is stale, notably the IANA registry. The new RFC3066bis registry is now online and contains all the required alpha-2 and alpha-3 language subtags as well as the alpha-2 country subtags. I would propose to remove that entire section and simply add a reference to the registry (http://www.iana.org/assignments/language-subtag-registry) to the BCP 47 entry in Related Resources. -------------------- -- François Grosso, Paul a écrit : > FYI. > > -----Original Message----- > From: chairs-request@w3.org [mailto:chairs-request@w3.org] On Behalf Of > Susan Lesch > Sent: Wednesday, 2006 March 22 22:37 > To: Steve Bratt > Cc: timbl@w3.org; Norman Walsh; Dan Connolly; chairs@w3.org; W3C Comm > Team > Subject: Transition request: First Public Working Draft for "The > Disposition of Names in an XML Namespace" > > The TAG requests First Public Working Draft maturity level for "The > Disposition of Names in an XML Namespace." > > Current draft: > http://www.w3.org/2001/tag/2006/02/namespaceState/TR/2006/WD-namespaceSt > ate-20060223/ > Proposed shortname: http://www.w3.org/TR/namespaceState/ > Estimated publication date: 28 March > > The TAG resolved to request publication of this document during its > regularly > scheduled teleconference on 14 February [1]. (TimBL was in attendance.) > > [1] http://www.w3.org/2001/tag/2006/02/14-tagmem-minutes#item03 > > Proposed Abstract > > A finding of the W3C Technical Architecture Group (TAG), this > document addresses the question of whether or not adding new names > to a (published) namespace is a sound practice. > > Proposed Status of This Document > > This section describes the status of this document at the time of > its publication. Other documents may supersede this document. A > list of current W3C publications and the latest revision of this > technical report can be found in the W3C technical reports index > at http://www.w3.org/TR/. > > This is a First Public Working Draft of produced by the W3C > Technical Architecture Group (TAG). This document is a TAG finding > that addresses TAG issue nameSpaceState-48. The TAG approved this > finding at its 3 January 2006 teleconference. Additional TAG > findings, both approved and in draft state, may also be available. > > Please send comments on this finding to the publicly archived TAG > mailing list www-tag@w3.org (archive). > > Publication as a Working Draft does not imply endorsement by the > W3C Membership. This is a draft document and may be updated, > replaced or obsoleted by other documents at any time. It is > inappropriate to cite this document as other than work in > progress. > > This document was produced under the 5 February 2004 W3C Patent > Policy. The group has not determined whether this document should > become a W3C Recommendation. W3C maintains a public list of any > patent disclosures made in connection with the deliverables of the > group; that page also includes instructions for disclosing a patent. > An individual who has actual knowledge of a patent which the > individual believes contains Essential Claim(s) must disclose the > information in accordance with section 6 of the W3C Patent Policy. > > >
Received on Thursday, 23 March 2006 18:25:58 UTC