- From: Chris Lilley <chris@w3.org>
- Date: Thu, 24 Sep 2009 20:21:21 +0200
- To: "Grosso, Paul" <pgrosso@ptc.com>
- CC: public-xml-core-wg@w3.org
On Thursday, September 24, 2009, 6:58:46 PM, Paul wrote: GP> Glad to see some progress on 3023-bis. GP> The reference to XML Base should reflect the January 2009 2nd Edition GP> (in terms of authors and date--the undated link itself is fine). Thanks for catching that, Paul. GP> Likewise, the reference to XML 1.1 should reflect the August 2006 GP> 2nd Edition. Will fix also. Hopefully that won't be a -04 internet draft, but it will go in the resulting RFC. GP> I don't know why XPointerXmlns is in the normative references. GP> The only reference is from appendix B (which is not normative) GP> wherein it says: GP> XPointer ([XPointerFramework] and [XPointerElement] and [XPointerXmlns]) GP> has been added as fragment identifier syntax ... GP> but in fact [XPointerXmlns] has not been added (and I don't think GP> it should be). So I think you should delete the mention of GP> [XPointerXmlns] from that note in appendix B and delete it from GP> the list of normative references. Again, thanks for catching that. Will fix for the next revision. GP> paul >> -----Original Message----- >> From: public-xml-core-wg-request@w3.org [mailto:public-xml-core-wg- >> request@w3.org] On Behalf Of Chris Lilley >> Sent: Thursday, 2009 September 24 11:29 >> To: public-xml-core-wg@w3.org >> Subject: Re: Fwd: New Version Notification for draft-murata-kohn- >> lilley-xml-03 >> Hello public-xml-core-wg, >> An HTML version of the draft may be seen at >> http://www.w3.org/2006/02/son-of-3023/draft-murata-kohn-lilley-xml- >> 03.html >> This draft incorporates the TAG finding >> Bray, T., Ed., “Internet Media Type registration, consistency of use,” >> April 2004. >> which also brings advice on the use of the charset parameter into line >> with current practice. In brief, the charset parameter should only be >> added if it agrees with the xml encoding declaration. In the absence of >> an explicit charset parameter, the encoding specified by the xml >> encoding declaration is used. (This is a change from RFC 3023, which >> required enforcing us-ascii in that case). >> The only difference between todays draft-03 and the draft-02 of 31 July >> this year is that draft-03 clarifies that the specification applies to >> all editions of XML 1.0 (first to fifth edition) and XML 1.1. The >> syntax of the xml encoding declaration is the same (bar minor >> clarifications) in all editions. Thanks to Henry Thompson for help with >> that. >> Once promoted to an RFC, this specification will obsolete RFC 3023. >> -- >> Chris Lilley mailto:chris@w3.org >> Technical Director, Interaction Domain >> W3C Graphics Activity Lead >> Co-Chair, W3C Hypertext CG -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Thursday, 24 September 2009 18:21:35 UTC