W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > June 2007

Minutes for XML Core WG telcon of 2007 June 6

From: Norman Walsh <ndw@nwalsh.com>
Date: Wed, 06 Jun 2007 11:30:04 -0400
To: public-xml-core-wg@w3.org
Message-ID: <871wgp6qyr.fsf@nwalsh.com>
/ "Grosso, Paul" <pgrosso@ptc.com> was heard to say:
| Minutes
| =======

Present: Norm, Daniel, Glenn [until xx:20], Konrad, Richard, Henry
Regrets: Paul
Chair: Norm
Scribe: Norm

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

Accept minutes of 23 May 2007[3]?


| 2. Miscellaneous administrivia and document reviews.
| XML clarification
| -----------------
| Norm sent email about < in attribute values at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007Apr/0006
| Glenn's proposed wording is at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007May/0024
| and slightly modified by
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007May/0030
| ACTION to Francois:  Add this to the PE document for countdown.


| 3.  C14N 
| The C14N 1.1 Last Call working draft is published at
| http://www.w3.org/TR/2006/WD-xml-c14n11-20061220
| Known Issues with Canonical XML 1.0 (C14N/1.0) WG Note 
| has been published at
| http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220/
| Using XML Digital Signatures in the 2006 XML Environment 
| WG Note has been published at
| http://www.w3.org/TR/2006/NOTE-DSig-usage-20061220/
| The CR-ready C14N 1.1 draft is at
| http://www.w3.org/XML/Group/2007/05/CR-xml-c14n11-20070509 
| Paul sent out a draft CR request at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007May/0040
| We had WG consensus to go to CR.
| ACTION to Henry:  Organize a CR telcon for the 11th or 12th
| with a target pubdate of June 14.
| ACTION to Paul:  Send in CR request.

Henry continues to work on getting the CR telcon organized. Planned
publication date will have to slip.

| 4.  xml:base, [baseURI], and IRIs -> HRRIs
| The (Second Edition) PER has been published at
| http://www.w3.org/TR/2006/PER-xmlbase-20061220/ 
| It's now waiting for us to say what should happen next--whether 
| we want a Director's call now or not.
| We need to remember to correct the IP part of the Status section per
| http://lists.w3.org/Archives/Public/www-xml-linking-comments/2007JanMar/
| 0000
| Mike Kay thinks the defn of XML Resource Identifier is too vague. 
| We decided to write an RFC to define XML Resource Identifier.
| The plan is to get this to an RFC and then reference it from
| XML Base (which we can then take to REC) and others. 
| 4.5.  HRRI RFC
| The latest HRRI draft was published as an ID on May 14 at
| http://www.ietf.org/internet-drafts/draft-walsh-tobin-hrri-01.txt
| Martin Duerst raise security issues with the HRRI draft.  
| ACTION to Norm:  Get Martin to send his comments to an accessible 
| list (or get his permission to forward them to such).


| ACTION to Norm:  Copy/reference/incorporate the security 
| text from the IRI RFC and add text mentioning the security risk
| inherent in allowing the use of control characters in HRRIs.


| ACTION to Norm:  Get Martin's acceptance of our changes.

Martin's mail:


Richard notes that we could go back to converting them to URIs.

But we are referring to things in the IRI spec.

Norm: So if we just added the private use area to our list, then that
would cover it, yes?

Richard: Yes, I think so.

Norm: I'll add

  * characters in the Unicode private use area, except where they appear
    in the query part.

and see if that addresses Martin's concern. 

| ACTION to Norm:  Publish another ID once we have
| agreement from Martin on the security wording.

Continued. I'll also try to get Martin to provide a more exhaustive

| 5.  XLink update.
| The XLink CR was published at
| http://www.w3.org/TR/2006/CR-xlink11-20060328/ 
| The latest almost PR-ready XLink draft is at
| http://www.w3.org/XML/Group/2004/xmlcore/xlink11/
| Norm posted a DoC at
| http://www.w3.org/XML/Group/2006/10/xlink11-doc.html
| Paul wrote a SECOND draft PR request at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Dec/0059
| ACTION to Norm:  Complete resolution of DoC.
| ACTION to WG (need volunteer):  Update the Implementation Report.
| ACTION to Norm:  Produce PR-ready draft.
| ACTION to Norm:  Produce diff/review version.
| HOWEVER, the actions here are pending until we get the HRRI
| RFC since we plan to reference it from XLink.

Suspended until HRRI resolved.

| 6. XML 1.0/1.1 4th/2nd Editions published 2006 August 16:
|  Extensible Markup Language (XML) 1.0 (Fourth Edition)
|  http://www.w3.org/TR/2006/REC-xml-20060816
|  Extensible Markup Language (XML) 1.1 (Second Edition)
|  http://www.w3.org/TR/2006/REC-xml11-20060816
| ACTION to Francois:  Update the PE document per previous 
| telcons' decisions.


| On PE 157, John sent email at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Oct/0036
| with his suggested response and a question for the WG:
|> Should we add specific references to UTF-16BE, UTF-16LE, CESU-8,
|> etc. etc. to 4.3.3?  If so, we might as well remove "We consider the
|> first case first" from Appendix F; it's more than obvious.
| We agreed that, according to the spec, such a character is not a BOM.
| We have decided that John's email should be sent to the commentor
| as a response (done, see [11]), and that the only change resulting from 
| this PE are some editorial changes as outlined in John's email at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Dec/0056
| ACTION to Francois:  Update the PE document with John's editorial
| changes as the proposed resolution to PE 157.


Henry/Richard discussed the test suite issues raised by Frans Englich:


These need to be resolved.

Richard reports that the 2005 issue has been resolved in the latest

The one from 2006, character references with numbers with dozens of
digits, may not be.

ACTION: Richard to construct a test case for these issues.

| [11] http://lists.w3.org/Archives/Public/xml-editor/2006OctDec/0010
| ----
| John sent email about a new PE related to UTF-8 BOM at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2006Dec/0067
| proposing the following language as a new paragraph in 4.3.3
| for both XML 1.0 and XML 1.1:
| 	If the replacement text of an external entity is to
| 	begin with the character U+FEFF, and no text declaration
| 	is present, then a Byte Order Mark MUST be present,
| 	whether the entity is encoded in UTF-8 or UTF-16.
| ACTION to Francois:  Add a new PE per John's comments above
| and make some suggested resolution wording.


| 7. Namespaces in XML 1.0/1.1 2nd Editions published 2006 August 16:
|  Namespaces in XML 1.0 (Second Edition)
|  http://www.w3.org/TR/2006/REC-xml-names-20060816
|  Namespaces in XML 1.1 (Second Edition)
|  http://www.w3.org/TR/2006/REC-xml-names11-20060816
| Richard has recorded Anne's issue/proposed resolution at
| http://www.w3.org/XML/Group/2001/05/proposed-xml-names-errata.html#NPE27

No discussion today.

| 8.  XInclude 1.0 Second Edition has been published:
|     http://www.w3.org/TR/2006/REC-xinclude-20061115/
| We got a comment about the XInclude spec at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007Jan/0013
| Paul suggested some specific wording to clarify the xi:fallback at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007Jan/0023
| Henry suggested wording to clarify xml:lang fixup at
| http://lists.w3.org/Archives/Public/public-xml-core-wg/2007Jan/0022
| ACTION to Daniel:  Process these as (editorial) errata to the
| latest XInclude spec.

Continued. DV is working on it.

| [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/2007May/0045.html

Any other business?



                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/            | possible, but no simpler.

Received on Wednesday, 6 June 2007 15:30:23 UTC

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