XML Core WG Status and Open Actions as of 2006 October 2

The XML Core WG telcons are every other week.

We do not meet October 4th.  

Our next telcon will be October 11th.

Status and open actions
=======================

C14N
----
Glenn produced a new editor's draft of C14N 1.1 in response
to Konrad's suggestions at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Aug/0046

This latest draft is at
http://www.w3.org/XML/Group/2006/09/WD-xml-c14n11-20060928.html

ACTION to Konrad and others:
Please review and send comments to the WG mailing list.

Jose reminded anyone who wishes to see the C14N discussion
to subscribe to www-xml-canonicalization-comments@w3.org .

XML Base
--------
Richard is working on a new draft currently at
http://www.w3.org/XML/Group/2006/09/xmlbase-2e/

ACTION to Richard:  Make a suggestion for replacement of 
section 5.1 for next week.

Regarding XSLT 2.0 and IRI's, Norm answered that the current 
Saxon behavior is a bug. At the August f2f, the WGs agreed
that unescaped characters would be returned.

Henry pointed out Richard could use the XLink test tool at
http://www.w3.org/XML/2006/03/xlink11-tests
to do some of his XML Base testing.

XLink
-----
The XLink CR was published at
http://www.w3.org/TR/2006/CR-xlink11-20060328/ 

Paul wrote a draft PR request at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Jul/0001

ACTION to Norm:  Create an XLink DoC.

ACTION to Norm:  Post to the WG mailing list something to
show that any valid XLink 1.1 document can be programmatically 
converted into an equivalent XLink 1.0 document.

ACTION to Norm:  Provide a few more tests for the test suite.

The old version XLink in section 5.5, we talk about values
of href attributes.  In the new version, we talk about IRIs 
and XML Resource Identifiers and other ways of encoding.  So 
it's unclear now what to do about spaces in href attributes.  
Norm thinks instead of spaces, we should now say non-URI
characters. 

ACTION to Norm:  Make a suggestion how best to fix this.

Also, nowhere do we say that conversion from an XML Resource
Identifier to an IRI must occur as late as possible.
Suggested new wording:

 If required, the IRI reference resulting from converting
 an XML Resource Identifier can be converted to a
 URI reference by following the prescriptions of
 Section 3.1 of [RFC 3987].

 The conversion from an XML Resource Identifiers to an
 IRI must be performed only when absolutely necessary and
 as late as possible in a processing chain.  In particular,
 neither the process of converting a relative XML Resource
 Identifier to an absolute one nor the process of passing
 an XML Resource Identifier to a process or software component
 responsible for dereferencing it should trigger escaping.

ACTION to Norm:  Implement the new wording in XLink 1.1.

XML 1.0/1.1
-----------
Henry has made the "edited in place" changes to the
HTML and XML of the non-review copy.

ACTION to Henry:  Correct the review versions.

Richard notes that there were some comments sent to the
xml-editor list:
http://lists.w3.org/Archives/Public/xml-editor/2006JulSep/0004
http://lists.w3.org/Archives/Public/xml-editor/2006JulSep/0005

ACTION to Francois: Add the above two issues to the PE document.

Namespaces 1.0/1.1
------------------
ACTION to Richard:  Record Anne's issue/proposed resolution
in the Namespace PE document.

XInclude
--------
ACTION to Henry:  Oversee the publication of the XInclude PER
(expected to be published on 2006 October 3).

RFC 3023 et al.
---------------
Months ago, we had said:

Chris and Henry also are backing "xpointer scheme" down 
from "registered" to "pending" in the registry.

I note at http://www.w3.org/2005/04/xpointer-schemes/
that xpointer is still listed as "Status: Registered".

ACTION to Henry:  Correct the listing for "xpointer scheme" 
from "registered" to "pending" in the registry.

Received on Monday, 2 October 2006 15:20:05 UTC