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

XML Core WG Status and Open Actions as of 2012 November 19

From: Paul Grosso <paul@paulgrosso.name>
Date: Mon, 19 Nov 2012 08:58:11 -0600
Message-ID: <50AA4903.3020404@paulgrosso.name>
To: core <public-xml-core-wg@w3.org>

The XML Core WG telcons are every other week.

Our next telcon will be November 28.

Status and open actions

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

[Bug 17976] New: xml-stylesheet with type=text/xsl needs to be handled 
[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.

This was discussed at the TPAC f2f.  The conclusion was
for Norm to pass on to the HTML5 WG suggested text for a
non-normative note to be included in the HTML5 1.0 spec
which he did:

ACTION to Norm:  Check with Robin that some words will be going
into the V1 spec.

This is the W3C Community Group work on a subset of XML. See

Henry says that if they do decide to standardize it, we
should do it.  We do own that name.

John says the group is finished with its document, so it is
ready for us to consider what we will do with it.

We could publish it as a WG Note at any time.  If the document
is to become a Rec, that would have to go into our next charter
which is due this coming January.  If anything about MicroXML
is to go into our charter, we would want to review the wording
first, and Henry wants to be sure we are allowed, but not required
by the charter, to do anything with MicroXML.

Names that begin [Xx][Mm][Ll]
This was discussed at the TPAC f2f.

Norm: proposed erratum

   s/in this or future versions of this specification/
    /in this or future specifications from the XML Core WG or its successors/

Henry: I'm perfectly happy to entertain a motion to remove this from
this specification and retain the "xml:" prefix only for elements and
attributes and "xml-" only for PI targets.

Norm: I'd prefer to make explicit that you *can* write names that
begin "xml", but doing so exposes you to being walked on in the
future. So don't do that.

Jirka: I can go either way, it's always been a restriction, users
should know better, but there are lots of documents that use it,
so we should adapt to common practice.

ACTION to Norm:  Draft an erratum to "reserve" xml-* for PI targets
and delete the restriction that we lay claim to other names that
start with "xml".

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

This was discussed at the TPAC f2f and there was agreement
on how to use MIME content types for the value of the parse

ACTION: Norm to revise the XInclude 1.1 draft to use media types
for the parse attribute.
Received on Monday, 19 November 2012 14:58:44 UTC

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