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

XML Core WG Status and Open Actions as of 2012 September 10

From: Paul Grosso <paul@paulgrosso.name>
Date: Mon, 10 Sep 2012 08:56:23 -0500
Message-ID: <504DF187.1010303@paulgrosso.name>
To: core <public-xml-core-wg@w3.org>

The XML Core WG telcons are every other week.

Our next telcon will be September 19.  Norm sends regrets.


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

Charter renewal, need to rejoin
-------------------------------
The new XML Core WG charter has been approved:
https://lists.w3.org/Archives/Member/w3c-ac-members/2012JulSep/0033

The call for participation has gone out and all WG members must
have their AC rep rejoin the WG per
https://lists.w3.org/Archives/Member/w3c-ac-members/2012JulSep/0034

The following membership issues appear (to me, I could be wrong)
outstanding:

1.  IBM has not yet rejoined.
2.  Innovimax has rejoined but not nominated anyone.
3.  MarkLogic has rejoined but not nominated anyone.
4.  Red Hat has rejoined but not nominated anyone.


When I go to the page that is supposed to be the XML Core data base at
https://www.w3.org/2000/09/dbwg/details?group=18796
there are clearly a lot of people who are not really members, so
ones appearance on this page proves nothing.

ACTIONs to Liam:  (1) Clear out all the entries from
https://www.w3.org/2000/09/dbwg/details?group=18796
except the nine of us listed at
https://www.w3.org/XML/Group/Core#membership.
(2) Let us know which of the nine organizations still
need to rejoin the working group.  (3) Let us know which
of the nine organization still need to nominate a person.


Error Recovery Note
-------------------
Liam raised an issue about a note about error recovery at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2012Sep/0002

Neither Paul nor Norm thought creating such a note was
going to be particularly useful, and Paul wondered why
the XML Core WG should write a note about something that
is not XML, but we decided we would pick this up when
Liam and others can be on the call.


Fall TPAC
---------
There will be a TPAC meeting in Lyon, France in October/November:
http://www.w3.org/2012/10/TPAC/Overview.html

We have signed up to have a WG f2f there.

Likely to attend:  Norm, Liam, Henry, Jirka, Mohamed
Not likely to attend:  Glenn, Paul, John, Daniel


xml-stylesheet and HTML5
------------------------
Hnery took an action to file a bug about xml-stylesheet
handling.  Done:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14689

Henry has done a lot more testing and filing of results to date.
Henry's tests are at
http://www.w3.org/XML/2011/11/ssTests/
You need to look at the README and README2 files there.

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

Henry has filed bugs against the HTML5 spec saying that
it should support styling XML with CSS.  Currently, there are:

[Bug 17976] New: xml-stylesheet with type=text/xsl needs to be handled 
explicitly
and
[Bug 14689] xml-stylesheet with type=text/xsl needs to be handled explicitly

A lot of bugzilla email has been exchanged on this issue.
It looks like we have agreement to address it, but only
in HTML.next.


XInclude 1.1
------------
On 2012 February 14, we published
XInclude 1.1 Requirement and Use Cases
http://www.w3.org/TR/xinclude-11-requirements/

Norm created a first draft XInclude 1.1 which is at
http://www.w3.org/XML/2012/08/xinclude-11/diff.html

Paul, Norm, Jirka, and John have reviewed and have no
comments (other than the items listed "TO DO").

ACTION to Henry, Glenn, Daniel, Mohamed, Liam: Review
and comment on the XInclude 1.1 draft.

Paul thinks we should publish an FPWD for XInclude 1.1
by mid-October so that it will have been out before TPAC.
That gives us Sept 19 and Oct 3 telcons, and it would be
best to be able to approve the FPWD for publication on
our Oct 3 telcon so that I can request publication around
October 9.

Note that the XInclude errata at
http://www.w3.org/XML/2006/11/xinclude-errata/
lists one simple erratum that we will want to incorporate
into XInclude 1.1.

ACTION to Norm:  Add some examples, change "resource error"
to "recoverable error", implement the above mentioned
erratum, and make a general sanity check pass on the
XInclude 1.1 draft.

ACTION to Paul:  Propose SOTD wording for a FPWD.
Received on Monday, 10 September 2012 13:57:07 UTC

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