- From: Paul Grosso <paul@paulgrosso.name>
- Date: Mon, 21 Oct 2013 11:03:22 -0500
- To: core <public-xml-core-wg@w3.org>
- Message-ID: <5265504A.1060901@paulgrosso.name>
The XML Core WG telcons are every other week. Our next telcon is October 30. John is at risk. **** NOTE: On October 30, we will be in the period where the UK and Europe as ended daylight time but North America is still observing daylight time. Given that our telcon time is based on local time in Boston, callers in the UK and Europe will need to call in one hour EARLIER on Oct 30. Status and open actions ======================= Submitting XML Schema 1.1 to ISO -------------------------------- Liam raised the question of whether the W3C should submit XML Schema 1.1 as an ISO standard; some discussion ensued: http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Oct/thread#msg28 On the call, most of us were luke warm at best, but we need to hear from David to see how enthusiastic he is about pushing this through and doing the editorial work. Loren offered to do some editorial work. ACTION to David: Express your opinion of making XML Schema 1.1 and ISO standard including your willingness to direct the effort. XML Media types (3023bis) ------------------------- The latest (diff marked) draft (now October 16 dated 2013 ) is at http://www.w3.org/XML/2012/10/3023bis/draft-ietf-appsawg-xml-mediatypes-03_diff.html Comments and resolutions at http://www.w3.org/XML/2012/10/3023bis/02-comments.html Please note in particular that a significant addition has been made to section 3.6 [1], to address the fact that the XML spec. itself defers to this spec. to define the precedence of charset parameter [in the http header], BOM and XML encoding declaration [both in the document]. The key new paragraph reads: All processors SHOULD treat a BOM (Section 4) as authoritative if it is present in an XML MIME entity. In the absence of a BOM (Section 4), all processors SHOULD treat the charset parameter as authoritative. Section 4.3.3 of the [XML] specification does _not_ make it an error for the charset parameter and the XML encoding declaration to be inconsistent. ACTION to John: Review the latest 3023-bis draft. ACTION to Henry: Implement all Paul's and John's editorial comments made earlier at http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Sep/0010 and http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Sep/0019 XInclude 1.1 ------------ On 2012 February 14, we published XInclude 1.1 Requirement and Use Cases http://www.w3.org/TR/xinclude-11-requirements/ On 9 October 2012, we published our FPWD of XInclude 1.1 at http://www.w3.org/XML/2012/10/WD-xinclude-11-20121009/ On 15 January 2013, we published our (first) Last Call of XInclude 1.1 at http://www.w3.org/TR/2013/WD-xinclude-11-20130115/ and Paul sent the transition announcement at http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Jan/0012 (also cc-ing the chairs mailing list). On 2013 October 8, we published the XInclude 1.1 CR at http://www.w3.org/TR/2013/CR-xinclude-11-20131008/ ACTION to Norm: Talk to Michael Kay and DV about implementing XInclude 1.1.
Received on Monday, 21 October 2013 16:03:51 UTC