W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > October 2004

Agenda for XML Core WG telcon of 2004 October 27

From: Paul Grosso <pgrosso@arbortext.com>
Date: Mon, 25 Oct 2004 10:06:58 -0400
Message-ID: <F13E1BF26B19BA40AF3C0DE7D4DA0C030114112B@ati-mail01.arbortext.local>
To: <public-xml-core-wg@w3.org>

We have an XML Core WG phone call scheduled for Wednesday, 
Ocotber 27, from
          08:00-09:00 Pacific time aka
          11:00-12:00 Eastern time aka
          15:00-16: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 occurs 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.

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:

The meeting will be held in the Hyatt Harborside, Boston:

3. Problem with xml:space in the Schema document for the XML namespace

Masayasu Ishikawa <mimasa@w3.org> sent us email on this at:

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:


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
This is in countdown until this week's telcon; check the
language and rationale at:

PE 134 Non-ascii chars in XML/text declaration
The xml-editor list received a comment at
which is presumably asking the same question asked earlier at
and which the commenter claims we never answered satisfactorily.
I see at
JohnC suggested:

  8) NEL issue can be bypassed by using different transcoding
http://lists.w3.org/Archives/Public/xml-editor/2003OctDec/0048.html .

  Recommendation:  Reject.  Special code pages for XML are undesirable, 
  and older mainframe tools can't cope with them anyway.

This is in countdown until next week.  Read the proposed resolution at

PE132 Validity of default attribute values (again)
The PE document suggests this might just be a problem with the test

5. Namespaces in XML.

  ACTION to Richard:  Produce a draft for NS1.0 2nd Ed.

6. Xinclude PR was published Sept 30 at:
   and announced to the AC at

   Please be sure your AC reps vote on it by October 29!!!!!!!!

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 20 though dated Nov 2) is at
READ IT and be prepared to approve for LC publication at
this week's telcon.

We will shoot for Nov 2 for the pubdate, Oct 28-29 for the 
pub request, 2004 Dec 13 end of LC period.

The (public) xml:id issues is at:
[Not up to date as of the writing of this agenda, but
all issues are closed.]

8.  XML Profile.  The TAG (via Norm) asks about progress on this:

We last talked about this at the March 2004 f2f.

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.

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

[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/0019
[8] http://www.w3.org/XML/xml-V10-3e-errata
[9] http://www.w3.org/XML/xml-V11-1e-errata
Received on Monday, 25 October 2004 14:07:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:33 UTC