Re: Agenda for XML Core WG telcon of 2006 December 20

/ "Grosso, Paul" <pgrosso@ptc.com> was heard to say:
| The QA working group asked Ian Hickson of the Web Application 
| Formats WG to request that the XML Core working group review 
| the XBL2 specification that is currently in Last Call:
[...]
| ACTION to Norm:  Review this WD.

Alas, I have not had a chance to do this yet. It's still on my "todo"
list.

| Issue on attribute canonicalization raised by Norm at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Oct/0020
| and by Eric Prud'hommeaux at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Oct/0019
|
| We figure if this is RDF's way to quote attributes, 
| it's fine with us, as it's RDF-specific.
|
| ACTION to Norm:  Reply to Eric with this and see if we've
| misunderstood something.

Eric and I chatted about this on IRC, but I haven't yet completed this
action.

| 5.  XLink update.
|
| 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
|
| Norm posted a DoC at
| http://www.w3.org/XML/Group/2006/10/xlink11-doc.html
|
| ACTION to Norm:  Update the DoC to remove the two non-XLink comments.

Done.

| ACTION to Norm:  Follow up in email on:
| XLink conformance criteria question, Boris Zbarsky 

Sigh. I swear I did this but there's no record in the archives. :-(

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

Drat. :-(

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

Did we have specific tests in mind?

| 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.  Compare
| http://www.w3.org/TR/xlink11/#link-semantics and the
| wording above it in section 5.4.1 at
| http://www.w3.org/TR/xlink11/#xml-resource-identifier
|
| Norm thinks instead of spaces, we should now say non-URI
| characters. 
|
| ACTION to Norm:  Make a suggestion how best to fix this.

I think we should delete the sentence at the end of the second
paragraph in 5.5 that begins "Spaces in these..."

We don't say (and never did AFAICT) that these attributes are XML
Resource Identifiers, we say they must be IRI. So unescaped spaces
aren't allowed.

If we want to say that they can be XML Resource Identifiers, then
I think we should change the sentence that begins "Spaces in these..."
so that it reads:

"The values of these attributes must be treated as XML Resource
Identifiers and converted to IRIs by the procedure described in 5.4.1
XML Resource Identifiers."

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

Done. See

   http://www.w3.org/XML/Group/2004/xmlcore/xlink11/

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.