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

XML Core WG Status and Open Actions as of 2014 June 30

From: Paul Grosso <paul@paulgrosso.name>
Date: Mon, 30 Jun 2014 11:32:02 -0500
Message-ID: <53B19102.1070002@paulgrosso.name>
To: core <public-xml-core-wg@w3.org>

The XML Core WG telcons are scheduled for every other week.

Our next telcon is scheduled for July 9
(for which Henry gives regrets).

If there has been no email indication of any progress--or
any other email request to have the telcon--by 9:00 Boston
time on Monday July 7, I will send out a status report
instead of a telcon agenda, and the telcon for July 9
will be cancelled.

Status and open actions

XML Potential Errata
Comment that "or by the Byte Order Mark" is lacking in section 4.3.3:

Comment that an entity cannot "begin" with a BOM as suggested in section 

ACTION to John and Henry: Review and comment on the above two comments
on the discussion of BOMs in section 4.3.3 of the XML spec.


Comment about documents with an "empty DTD":

Henry suggests we could probably make the XML spec clearer here;
see also his comments at

Paul sent the WG response at
and there was more back from the commentor at

ACTION to Henry: Read the post-February 6 email at
and let us know what you think we should do.

Submitting XML Schema 1.1 to ISO
See also

We have decided we will first publish XML Schema 1.1 2E (with
approved errata). After that, we would send XML Schema 1.1 2E
(only) to ISO.

Loren has offered to do the editorial duties, and David
talked to CMSMCQ about getting some more help in the details.

ACTION to Loren and David: Produce a publication-ready version
of XML Schema 1.1 2E incorporating the approved errata.

It looks like there are 3 bugs for Structures, none for Datatypes,
but after checking with Michael, he found
which shows 8 errata items whereas bugzilla shows only 3.

We discussed

Henry figures we can just publish this document.

Loren believes the latest document includes everything,
so the next step is to push it through the tool chain,
but that make take help from Henry or Michael. Loren
will try to contact Michael again.

We will need a diff (or list of changes) and a test suite.
Loren says the diff is already available.

We need to see if any of the changes are normative.
It appears that none of the changes require a chance
in the test suite.

ACTION to Loren:  Check if any changes are normative and/or
would require a change to the test suite.

XML Media types (3023bis)
There is now a February 23 draft at
with a diff at
and a DoC at http://www.w3.org/XML/2012/10/3023bis/07-comments.html
...and finally a March 2 draft at
(I could find no DoC or non-auto diff).

[Henry, the first sentence of the last paragraph of section 2.2
includes the phrase "are given names in in [UNICODE]"--note
the extra "in".]

Paul has sent another WG email of support at

Henry reports that the IESG has tentatively approved the spec.
There we many comments made, though none requiring substantive
changes. Henry is creating the final draft of the final version.

And Wendy Seltzer has acknowledged that the W3C is now the official
change controller for all the XML related media type registrations.

Henry reports that we are in the real end game.
Review is over, and it is in the RFC editor queue.
We will get an RFC number soon-ish.

But later Henry says that xml-mediatypes RFC is stalled waiting
for HTTPbis.

XInclude 1.1
On 2012 February 14, we published
XInclude 1.1 Requirement and Use Cases

On 9 October 2012, we published our FPWD of XInclude 1.1 at

On 15 January 2013, we published our (first) Last Call of
XInclude 1.1 at
and Paul sent the transition announcement at
(also cc-ing the chairs mailing list).

On 2013 October 8, we published the XInclude 1.1 CR at

Norm reports that Michael Kay's code just accesses Xerces code,
so Norm might have to work with Xerces.

DV reports that he is busy and so cannot commit to a deadline
for adding XInclude 1.1 support to libxml.

ACTION to Norm:  Continue to work toward getting XInclude 1.1
implementations and document them in our implementation report.

Note also the desire for another test case for the XInclude test suite per

Norm may see if he knows anyone still working on Xerces.

Norm is planning to write a SAX filter to implement XInclude 1.1.
He believes this will lead to a way for using XInclude 1.1 with
Saxon's XSLT processor and most any other Java based tool.
Received on Monday, 30 June 2014 16:32:54 UTC

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