W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > March 2006

Agenda for XML Core WG telcon of 2006 March 8

From: Grosso, Paul <pgrosso@ptc.com>
Date: Tue, 7 Mar 2006 16:44:15 -0500
Message-ID: <CF83BAA719FD2C439D25CBB1C9D1D3020295820A@HQ-MAIL4.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>

We have an XML Core WG phone call scheduled for Wednesday, 
March 8, 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
          21:30-22:30 in most of India
on the Zakim W3C Bridge, +1 617 761 6200, passcode 9652#.
We also use IRC channel #xmlcore on irc.w3.org:6665 .

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).

We also need to accept the minutes for the f2f which are at

2. Miscellaneous administrivia and document reviews.

We discussed the future of the XML Core WG at our f2f at
but we should discuss this as a group on the telcon.

3.  C14N 

Glenn created an editor's draft of C14N 1.1 which is up at

We had some discussion at the f2f--see
The discussion continues in email.

Note that John Boyer, Thomas Roessler, Jose Kahan, and
Konrad Lanz to the XML Core WG mailing list and are 
expected to dial in for these discussions.  We will
take this topic near the beginning of the telcon to
allow them to drop off as we get to other topics.

ACTION to John Boyer (and others): Send comments on the 
the latest C14N 1.1 editor's draft to the XML Core WG list.

At the f2f, we decided to produce a W3C WG Note documenting 
the current situation and issues and problems.

ACTION to Thomas and John: Generate a draft of the Note.

4.  xml:base, [baseURI], and IRIs.

At the f2f, we had CONSENSUS to change the 
xml:base spec to make it clear we allow IRIs as the 
value of xml:base. We also want to allow IRIs in the 
infoset [baseURI] information item.

However, we are still discussing this in email.

5.  XLink update.

We DECIDED at the f2f to take XLink to CR.

We still need to put exit criteria into the Status 
of the document.

ACTION to Norm: Add exit criteria to the draft.

At the f2f, we also decided we should augment the wording 
that François suggested (and that we are putting into all 
the specs including XLink) to describe the resolution 
algorithm for relative XML Resource Identifiers. It should 
parallel section 6.5 of section RFC 3987.

ACTION to Norm:  Modify the XLink draft accordingly.

Paul had sent a draft CR request at
but he needs to update it.

ACTION to Paul: Send in the (updated) CR request.

6. 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]. 

JohnC did a scan for MUST/SHOULD and reported at
John thought most of the mays were not official mays.

This is now PE 148.

Henry produce a version at

Norm looked at it and approved it.

Paul reviewed it:
and closed the loop at

ACTION to Henry:  Make any final changes needed and repost.

We resolved some other PE at the f2f.

We decided to resolve PE140 by saying that we have 
fiddled this wording enough and we aren't going to 
fiddle it any more for fear of making it worse.

We decided to resolve PE142 by saying that we have 
fiddled this wording enough and we aren't going to 
fiddle it any more for fear of making it worse.

ACTION to François: Update the PE document accordingly
for PE 140 and 142.

We note that the resolution to PE141 has already made 
what we believe is an appropriate wording change in this area.

ACTION to Richard: Respond to the commentor about PE140/142 
including that there is nothing to prevent something from 
being both a WFC and a VC.

With respect to PE143, after production [60], we should 
add a reference to the "No External Entity References" WFC.

ACTION to François: Update the Errata and PE document 
accordingly for PE143.

7. Namespaces in XML.

Richard suggested we take NS 1.1 and revert the two 
substantive changes (IRI and undeclared namespaces) 
to create NS 1.0 2nd Ed. The WG has consensus to do 
that, and we got approval from the team to do so.

ACTION to Richard: Draft the 2nd edition of NS 1.0 
per the above plan (perhaps by creating a single XML 
source document for 1.0 and 1.1 using some conditionals).

ACTION to Richard: Draft a NS 1.1 2nd Edition including 
this IRI work and the outstanding NS 1.1 errata which, to 
date, includes only the issue about preventing abuses of xmlns.

8. Xinclude Rec was published 2004 December 30 at:

Our XInclude potential errata document is at:

Daniel has updated the Errata document at

ACTION to Daniel: Update the PE about IRIs for XInclude.

ACTION to Daniel: Draft XInclude 2nd Edition with all 
the errata (including the IRI one) applied.

9.  Associating stylesheets--awaiting TAG action.

Henry reports that the HTML CG has been discussing this
for a while.  They are developing a draft statement of
the issue, and Chris Lilley will raise this at the XML CG.

Chris started the discussion on the XML CG list--see
The XML CG will continue to discuss it for a while.

10.  Henry raises that RFC 3023 is out of date and the draft
replacement has expired.  Henry says there is a new draft
expected soon (Murata-san will send something to Chris to
publish soon).  

Chris is still hoping that he and Murata will be able
to publish a new ID for 3023bis soon.

11. xml:id is a Recommendation, published 2005 Sept 9:

Robin Berjon asked a question about transition
strategies that we discussed at the f2f--see

12.  Henry added a "forking QNames" item:

We discussed this at the f2f:
and we DECIDED that this usage looked unwise and potentially 
confusing to us, but we will leave it for the TAG.

[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/2006Feb/0035
[8] http://www.w3.org/XML/xml-V10-3e-errata
[9] http://www.w3.org/XML/xml-V11-1e-errata
Received on Wednesday, 8 March 2006 00:23:05 UTC

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