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

Agenda for XML Core WG telcon of 2006 January 25

From: Grosso, Paul <pgrosso@ptc.com>
Date: Mon, 23 Jan 2006 11:37:19 -0500
Message-ID: <CF83BAA719FD2C439D25CBB1C9D1D30202177CBB@HQ-MAIL4.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>

We have an XML Core WG phone call scheduled for Wednesday, 
January 25, 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.


Norm can only be on a short time at the beginning of the
call, so please dial in promptly so that we can get XLink 1.1
approved to go to CR.


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 and document reviews.

We are planning a f2f at the Technical Plenary 27 Feb-3 March 2006
in Cannes, France.  The XML Core WG is currently scheduled to
meet Thursday and Friday, March 2-3 of that week.

TP2006 registration is open until 17 February 2006:
The TP Week overview page is at

Expected:  Paul, Norm, Daniel, Richard, Philippe

2b.  IRI wording in xml:base et al.

Chris Lilley asks about xml:base and IRI:

Norm thinks we should change the bib ref from 2986
to 3986.  Section 3.1 should say any xml:base should
first have spaces escaped to %20 and then have the
IRI changed to a URI per 3987.

We should have uniform language for XLink 1.1, XLink 1.0,
xml:base, xinclude, XML 1.0, and XML 1.1 (as errata for 
all but XLink 1.1).

There is some question as to whether we should bother to 
make an erratum for XLink 1.0, but we did not resolve this.

We basically want to put the text that is in XLink 1.1 into
the other specs.

We talked about pulling the necessary wording into a normative
appendix in XML 1.0 3rd Ed and XML 1.1 (as errata in both cases).
Then we could reference that appendix in xml:base, XInclude, etc.

We also said we could just make it section 4.2.3.  As long as it
is referenceable by other specs.

Francois sent updated suggestions at
(ignore the "System identifiers (and other XML strings..." 
sentence at the beginning.)

This will go into XLink 1.1 as a separate section.  
Then we can do it as an erratum for XML 1.0 and 1.1.
Then we would produce XML 1.0 4th Ed and 1.1 2nd Ed.
XInclude and xml:base (and probably NS 1.1) we do 
errata pointing them to the new editions of XML or 
if we're in a bigger hurry, errata quoting the whole 
text.  (We don't want to point the lower specs to XLink.)  

ACTION to Richard:  Look at this wrt putting into NS 1.1.

We do have a suggestion from Murata-san at
that we process such an erratum against NS 1.0.

We're not sure what we think about this yet.

3.  XLink update.

The LC WD of XLink 1.1 has been published:

We have comments at
and a DoC at

Paul sent a draft CR request at

Thread 19--Schema issues 
Comments on the schema for xlink.

ACTION to Henry [due Jan 25]:  Think about and reply to this one.

We have taken care of all other issues, and we expect to 
vote to take XLink 1.1 to CR during this week's telcon.

Norm has sent out the latest CR-ready draft at

ACTION to Henry:  Try to schedule an LC-to-CR transition
call for Jan 27th (or 26th).  Norm prefers Friday afternoon
due to his travel schedule.

We hope we'll be able to run CR from Feb 1 to Mar 1 so
that it will end just as we're meeting at the Tech Plen.

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

ACTION to Francois:  Update the PE document including
issues raised on public-xml-testsuite@w3.org.

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.

ACTION to Henry [due Jan 31]:  Review the MAYs again and 
create a marked up version with changes.

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

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

We note that the IRI spec is now finished-RFC 3987-so 
we have to issue an erratum for NS 1.1 for this.  We
discussed some details of this under the XLink discussion:
Briefly, 3987 does have some wording (the "MAY" paragraph) 
about what used to be called unwise characters.  For the 
NS 1.1 erratum, the MAY paragraph doesn't apply since 
namespace names cannot have the unwise characters.  (The 
MAY paragraph will be needed for XML 1.* system identifiers.)

ACTION to Richard:  Process an erratum to NS 1.1 to
refer to RFC 3987: http://www.ietf.org/rfc/rfc3987.txt

There is a namespace PE:

Richard's suggested resolutions are at

CONSENSUS with Richard's suggested resolutions.

These would be errata to both NS 1.0 and 1.1.

ACTION to Richard:  Update the NS PE doc and Errata documents.

6. Xinclude Rec was published 2004 December 30 at:

Our XInclude potential errata document is at:

Daniel has updated the Errata document at

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

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

9.  C14N is listed in our charter:

 Canonical XML version 1.1

 The work on xml:id uncovered some inconsistencies
 in Canonical XML version 1.0 (see xml:id CR,
 Appendix C, "Impacts on Other Standards"). The
 Working Group will produce a new version of
 Canonical XML to address those inconsistencies,
 as well as others that might be discovered at a
 later stage.

We have CONSENSUS that we have been chartered to do a 1.1
and that we should not try to do this as an erratum.

We are not sure how best to do this as a 1.1.  We should try
to elaborate the possible ways of handling this and ask the
C14N community how best to go about this.  For example, if
we create a new namespace for C14N 1.1, what do we say the 
old namespace means?  We'd like to avoid the flak we are
getting for XML 1.1.

We should probably use the existing mailing list
w3c-ietf-xmldsig@w3.org to gather opinions.

Glenn posted an email to w3c-ietf-xmldsig@w3.org explaining
we are doing a 1.1 and asking for how we can minimize disruption:

Glenn summarized that discussion at:

The email includes a discussion on whether an erratum to C14N 1.0
or a C14N 1.1 would be less disruptive.  There was no consensus
among the discussants of this thread.

The XML Core WG has consensus to stick with a C14N 1.1 as chartered.

Henry points out we could produce a 1.1 and use the old identifier.
But Norm doesn't think we can do that.

We seem to be ready to produce a first WD of C14N 1.1.

ACTION to Glenn:  Produce an actual first editor's draft of C14N 1.1.

10.  Henry added a "forking QNames" item:

We had some discussion last week.

Norm argues that we should object to the use of the
QName syntax for things that aren't QNames.  He also
objects to the invention of a new mechanism for declaring
things that look like namespaces when they aren't really.

Norm is still trying to understand whether there is an
issue yet, and he needs to wait until they publish a
document to be sure.

ACTION to Norm:  Raise this concern at the TAG level
at the appropriate time.

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

[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/2006Jan/0015
[8] http://www.w3.org/XML/xml-V10-3e-errata
[9] http://www.w3.org/XML/xml-V11-1e-errata
Received on Monday, 23 January 2006 16:37:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:40:30 UTC