W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > September 2005

Agenda for XML Core WG telcon of 2005 Sept 28

From: Grosso, Paul <pgrosso@ptc.com>
Date: Mon, 26 Sep 2005 14:20:37 -0400
Message-ID: <CF83BAA719FD2C439D25CBB1C9D1D302DB8FBA@HQ-MAIL4.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>

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

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 and Henry give regrets for Sept 28.

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.

Impending Last Call revisions for XSLT/XQuery/XPath documents

Richard checked the data model document and has the 
following issues:


I'm still a little unclear about the relationship between XSL/Query
datatypes and schema datatypes.  The resolution says that "All
primitive atomic types, such as xs:integer and xs:string, have
xdt:anyAtomicType as their base type." which is not true in XML Schema.


They're adding a note to the XPath backwards compatibility appendix
(appendix to what?) noting the incompatibility when there is a DTD,
but this still seems like a big change: for example, identity
transformations will now strip element-content whitespace.  And I
still don't see why they are not describing it in terms of [element
content whitespace].

ACTION to Richard:  Accept the others, but question
there two in the bugzilla data base.

JohnC looked at the wording about XML 1.1 in the 
language documents (xpath, xquery):

XQuery, XPath, and Data Model all use the same idea: an implementation
can use XML 1.0 rules or XML 1.1 rules for whitespace and names.
XQuery explicitly says that 1.1 implementations may wish to provide a
1.0 mode;  I'd like to see this strengthened to SHOULD, to agree with
the XML 1.1 Recommendation.

The Functions and Operators draft refers to XML 1.1 support as a
but the datatypes are imported from XML Schema part 2, which does not
deal with XML 1.1 names or strings.

ACTION to John:  Add your two comments ASAP into bugzilla:

3.  XLink update.

The LC WD of XLink 1.1 has been published:

We have comments at

ACTION to Norm:  Reply as feasible and bring issues worth
discussing to the WG via email.

XLink 1.1: XML Base confusion

XML Base references RFC 2396 and XLink references RFC 3987
(the IRI one) which references RFC 3986 (2396-bis) for
absolutization and such, but nothing has changed between
2396 and 3986 wrt absolutization.  So we don't see the problem.

ACTION to Norm:  Take this back to the commentor.

XLink 1.1: Error handling

We say what the conformance criteria are but not what
to do when an error is encountered.  For example, what
should we do if someone specifies an invalid value for
one of the xlink:* attributes.

Francois points out that this hasn't changed since XLink 1.0.

ACTION to Norm:  Craft some words along the lines of error
handling being implementation dependent.

XLink 1.1: XLink 1.1 in XML 1.1

Norm suggests we just say that XLink works for both XML 1.0
and XML 1.1, and the names should just match the version
being used.

XLink 1.1: Integration with CSS

How does XLink interact with CSS's :link selector?

Francois suggests that we add a note that says "languages
such as CSS should see XLink links as links."

ACTION to Norm:  Respond to the commenter and to the CSS WG.

ACTIONs to Norm continued--expected due date October 12th.

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.

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

6. Xinclude Rec was published 2004 December 30 at:

Our XInclude potential errata document is at:

We need to turn the PE document into an errata document.

ACTION to DV:  Produce a draft Errata document, using
http://www.w3.org/2004/12/xinclude-errata as a starting 

Elliotte's results are not
included in our Implementation Report at
as he reports in

ACTION to Richard:  Run ERH's tests through the other
implementations and add the results to the XInclude IR.

ERH's tests are in the CVS repository for the test suite.

ACTION to Daniel:  Run ERH's tests through libxml and
provide Richard with a report.

Richard will ask ERH for his results if he can't find them.

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 should start drafting a V1.1.

We need to change the URI to identify the c14n scheme,
we need to fix the bit about inheritance of xml:*
attributes.  That should be it.

Do we say that xml:lang and xml:space get inherited
and the rest don't, or do we say that C14N should
not fool with xml:* attributes at all?

Glenn might be willing to be the editor for C14N V1.1.

ACTION to Glenn:  Look for the source and start on a

[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/2005Sep/0029
[8] http://www.w3.org/XML/xml-V10-3e-errata
[9] http://www.w3.org/XML/xml-V11-1e-errata
Received on Monday, 26 September 2005 18:18:35 UTC

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