- From: Paul Grosso <pgrosso@arbortext.com>
- Date: Mon, 1 Nov 2004 12:01:55 -0500
- To: <public-xml-core-wg@w3.org>
We have an XML Core WG phone call scheduled for Wednesday, November 3, from 08:00-09:00 Pacific time aka 11:00-12:00 Eastern time aka 16:00-17:00 UTC 16:00-17:00 in Ireland and the UK 17:00-18:00 in middle (most of) Europe on the Zakim W3C Bridge, +1 617 761 6200, passcode 9652#. We also use IRC channel #xmlcore on irc.w3.org:6665 . [For those wondering, the switch from daylight savings time to standard time occurred on October 31st for the home locale of everyone on the WG.] See the XML Core group page [1] for pointers to current documents and other information. If you have additions to the agenda, please email them to the WG list before the start of the telcon. Please also review our group page's task list [2] for accuracy and completeness and be prepared to amend if necessary and accept it at the beginning of the call. Agenda ====== 1. Accepting the minutes from the last telcon [3] and the current task status [2] (have any questions, comments, or corrections ready by the beginning of the call). 2. Miscellaneous administrivia. The next W3C Technical Plenary Week will be 28 February 2005 through 4 March 2005: http://www.w3.org/2002/09/TPOverview.html The meeting will be held in the Hyatt Harborside, Boston: http://harborside.hyatt.com/property/index.jhtml Chairs are sending in expectations this week. The XML Activity will be asking that XSL and Query meet Monday, Tuesday of the week and that XML Core and XML Schema will meet Thursday and Friday, with the Plenary on Wednesday. Please try to have some idea (e.g., at the 75% confidence level) as to whether you expect to attend or not by this week's telcon. 3. Problem with xml:space in the Schema document for the XML namespace Masayasu Ishikawa <mimasa@w3.org> sent us email on this at: http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Jul/0019 CONSENSUS to remove the default for xml:space from the schema for the xml namespace. Henry has installed the updated XSD (that also has xml:id) at: http://www.w3.org/2001/xml.xsd http://www.w3.org/2004/10/xml.xsd There are a few more things to do to clean this up; per Henry: http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Oct/0035 http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Oct/0036 ACTION to Henry: Complete clean up of xml namespace documents and reply to Michael cc-ing XML Core. 4. XML errata. The published 1.0 errata document is [8], the published 1.1 errata document is [9], and the NEW PUBLIC Potential Errata (PE) document is [7]. PE 133 CDATA sections, PIs and Comments in Mixed and ANY content models ----------------------------------------------------------------------- CONSENSUS to approve and publish. ACTION to Francois: Update PE and Errata documents for PE 133. PE 134 Non-ascii chars in XML/text declaration ---------------------------------------------- The xml-editor list received a comment at http://lists.w3.org/Archives/Public/xml-editor/2004OctDec/0003 which is presumably asking the same question asked earlier at http://lists.w3.org/Archives/Public/xml-editor/2003OctDec/0048 and which the commenter claims we never answered satisfactorily. We had a proposed resolution at http://www.w3.org/XML/2004/02/proposed-xml10-3e-and-xml11-errata#PE134 but the commentor came back at http://lists.w3.org/Archives/Member/w3c-archive/2004Oct/0131 thereby requiring Francois to update the rationale. ACTION to Francois: Update the rationale and restart the countdown. PE132 Validity of default attribute values (again) -------------------------------------------------- This comes down to the wording in section 3.3.2 where we say "only the syntactic constraints of the type are required here" but then we argued about what "syntactic" means. CONSENSUS: It is a violation of the Attribute Default Legal VC for the default value not to be one of those specified in the enumerated list for enumerated type attributes. ACTION to John: Propose new language for "Validity constraint: Attribute Default Legal" to solve the ambiguity here. 5. Namespaces in XML. ACTION to Richard: Produce a draft for NS1.0 2nd Ed. 6. Xinclude PR was published Sept 30 at: http://www.w3.org/TR/2004/PR-xinclude-20040930/ and announced to the AC at http://lists.w3.org/Archives/Member/w3c-ac-members/2004JulSep/0043 The AC review closed October 29. Henry, let us know if you have any status on the review. Sandra has added ERH's tests to the CVS of the XInclude Test Suite. We will plan to update the tar and zip (and test suite home page) after the PR ends and we are ready to publish the Rec. 7. xml:id. The Last Call ready draft (of Oct 27 though dated Nov 9) is at http://www.w3.org/XML/Group/2004/xmlcore/xmlid/xml-id.html This includes rewrites coming out of last week's telcon and is therefore the version we plan to approve for publication! READ IT before the call and be prepared to vote for publication. We will now shoot for WG approval THIS WEEK, Nov 9th pubdate, Nov 11-12 for the pub request, but still 2004 Dec 13 end of LC period. ACTION to Norm: Update the last para of the Status to indicate that this document is under the newer PP IP policy. The (public) xml:id issues is at: http://www.w3.org/XML/2004/xml-id/wd-status/status-report.html [Not up to date as of the writing of this agenda, but all issues are closed.] ACTION to Norm: Update the xml:id issues document. Norm announced he had a sax filter implementation of xml:id: http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Oct/0042 8. XML Profile. The TAG (via Norm) asks about progress on this: http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0004 We last talked about this at the March 2004 f2f: http://www.w3.org/XML/Group/2004/02/xml-f2f-20040301-minutes#profile Norm continues to recommend that we make a profile that is the same as XML 1.1 except to change the bnf so that you can't have any sort of doctype decl. Norm suggests we generate a WG Note outlining the subset. Glenn asks about how this might affect the idea of a compliant XML processor. Specifically, a processor that only processes this subset is not a compliant XML processor. SOAP also forbids PIs, but we believe they can live with a subset with PIs. ACTION to Norm: Send email summarizing his suggested plan (though the ACTION below to check with the TAG should probably come first). Norm started a TAG discussion at http://lists.w3.org/Archives/Member/tag/2004Oct/0059 but reached no denouement. ACTION to Norm: Check with the TAG that this is something they still want to see worked on. The next step would seem to be to write a summary of the plan and send it out and see if it makes people happy. We should be sure to include at least the TAG, SOAP, the XML CG. [1] http://www.w3.org/XML/Group/Core [2] http://www.w3.org/XML/Group/Core#tasks [3] http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Oct/0038 [7] http://www.w3.org/XML/2004/02/proposed-xml10-3e-and-xml11-errata.html [8] http://www.w3.org/XML/xml-V10-3e-errata [9] http://www.w3.org/XML/xml-V11-1e-errata
Received on Monday, 1 November 2004 17:01:57 UTC