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

Agenda for XML Core WG telcon of 2012 January 11

From: Grosso, Paul <pgrosso@ptc.com>
Date: Mon, 9 Jan 2012 17:32:44 -0500
Message-ID: <9B2DE9094C827E44988F5ADAA6A2C5DA0467D7E1@HQ-MAIL9.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>

We have an XML Core WG phone call scheduled for Wednesday, 
January 11, from
          08:30-09:00 Pacific time aka
          11:30-12:00 Eastern time aka
          15:30-16:00 UTC 
          16:30-17:00 in Ireland and the UK 
          17:30-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.

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.

xml-stylesheet and HTML5
Henry took an action to file a bug about xml-stylesheet
handling.  Done:

Henry has done a lot more testing and filing of results to date.

ACTION to Henry: File a bug against the HTML5 spec saying that it 
should support styling XML with CSS.

The CSS2 spec says something about styling XML with CSS.
Henry also notes http://www.w3.org/Style/styling-XML.en.html.

Henry's tests are at
You need to look at the README and README2 files there.

issues with the Polyglot draft
Henry sent email with various potential issues at

We should discuss each point and decide what we think.

3.  XML 1.0--see http://www.w3.org/XML/Group/Core#xml-errata

We are creating an XML 1.0 6th Edition and XML 1.1 3rd (or
perhaps 6th) Edition.

ACTION to John:  Update the XML sources for XML 1.0 and 1.1
to reflect any errata and the LEIRI reference.

On hold awaiting resolution of IRIbis.

4.  XML Test Suite.

See also http://www.w3.org/XML/Group/Core#xml-test-suite

ACTION to Henry:  Construct a test case for the XML test suite 
issues raised by Frans Englich:

5.  Namespaces in XML 1.0/1.1--see
   and http://www.w3.org/XML/Group/Core#ns1.1.

6.  LEIRIs--see http://www.w3.org/XML/Group/Core#leiri

We had planned to issue the following spec editions referencing LEIRIs:

* XML 1.0 6th Edition
* XML 1.1 3rd Edition
* XInclude 3rd Edition

We continue to wait to see what might happen with IRIbis.

7.  xml:id--see http://www.w3.org/XML/Group/Core#xml-id

8.  XML Base 2nd Ed--see http://www.w3.org/XML/Group/Core#xml-base

9.  XLink 1.1--see http://www.w3.org/XML/Group/Core#xlink1.1

10.  XInclude 3rd Ed--see http://www.w3.org/XML/Group/Core#xinclude

We are creating an XInclude 3rd Edition.

ACTION to Paul:  Update the XML sources for Xinclude to reflect 
any errata and the LEIRI reference.

On hold awaiting resolution of IRIbis.

XInclude @xpointer when parse="text"
Previous email discussion at

We seem to have three choices:

1.  allow use of the @xpointer attribute when parse=text
2.  add a new "@textptr" attribute to use when parse=text
3.  add a new "@fragid" attribute to use in all cases and possibly
    deprecate the @xpointer attribute

We are leaning toward choice #2 which Norm will include in the
XInclude 1.1 requirements document and initial draft.

Extending XInclude
We've discussed extending xinclude to copy attributes on the 
xinclude element down to the root included element.

Some issues include:

1.  exactly what attributes to copy?  Henry and Liam preferred to 
copy un-prefixed attributes (except those in the xinclude spec) too.

Norm worries what this would mean if we add another attribute
in the XInclude spec?

Henry wants to be able to have unprefixed attributes copied
onto the root included element.

Henry: we could add a new "copy me without prefix" namespace 
to xinclude.

Norm doesn't need that, but could live with it.

2.  what to do about attribute conflict (error or one or the other

3.  whether we should "log" additions (e.g., via an attribute that 
says what attributes were added).

At first, we didn't think this was much of a concern, but then we
realized perhaps it was something worth considering.

4.  whether we should have some way for targets to say whether they
can be xincluded and/or, when included, have attributes added.

XInclude 1.1
This would address the two issues discussed above:
* @xpointer when parse="text"
* copying attributes from the xinclude element to the root
  included element

If we want to produce an XInclude 1.1, we will need an amended 
charter as indicated by Ian at
but we can discuss requirements now.

Norm drafted an initial XInclude 1.1 requirements document at

(Eventual) ACTION to Norm:  Produce the initial XInclude 1.1 
editor's draft.

11.  Associating Stylesheets.

See also http://www.w3.org/XML/Group/Core#assoc-ss

AssocSS 2nd Ed is now a Recommendation at

12.  xml-model

See also http://www.w3.org/XML/Group/Core#assoc-schemas

The Second Edition has been published as a WG Note at


[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/2011Dec/0012
Received on Monday, 9 January 2012 22:33:22 UTC

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