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

XML Core WG Status and Open Actions as of 2012 March 12

From: Paul Grosso <paul@paulgrosso.name>
Date: Mon, 12 Mar 2012 09:29:23 -0500
Message-ID: <4F5E0843.4070308@paulgrosso.name>
To: core <public-xml-core-wg@w3.org>

The XML Core WG telcons are every other week.

Our next telcon will be 2012 March 21.


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

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.

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


issues with the Polyglot draft:  BOM
------------------------------------
Henry sent email with various potential issues at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Nov/0037

We discussed the point about the spec recommending [P1] the use of
the UTF-8 BOM.

[P1] http://dev.w3.org/html5/html-xhtml-author-guide/#character-encoding

Henry thinks we converged on this in email on Wednesday 11 January:
See
http://lists.w3.org/Archives/Public/public-xml-core-wg/2012Jan/0007

ACTION: Henry to file an issue against Polyglot about the BOM.


issues with the Polyglot draft:  xml:space and xml:base
-------------------------------------------------------
See the minutes at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2012Jan/0016
for the discussion.

ACTION: Henry to draft an issue regarding xml:space and xml:base in
the Polyglot draft for WG review.


XInclude 1.1
------------
On 2012 February 14, we published
XInclude 1.1 Requirement and Use Cases
http://www.w3.org/TR/xinclude-11-requirements/
summarizing the requirements and use cases for possible
enhancements to XInclude addressing the issues:

* @xpointer when parse="text"
* copying attributes from the xinclude element to the root
  included element

Before producing an XInclude 1.1, we will need an amended
charter as indicated by Ian at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Dec/0014

We will wait to see what if any feedback we get from the
published requirements and use cases and then, if we want
to go ahead with an XInclude 1.1, we should look into amending
our charter.

Norm has posted something to the DocBook TC:
http://lists.oasis-open.org/archives/docbook/201202/msg00001.html
and at
http://lists.oasis-open.org/archives/docbook/201202/msg00002.html
was a follow up posting that (I believe) requested that we also
augment XInclude to allow for including the *contents* of all
the elements addressed by the xpointer attribute, but not the
elements themselves.

ACTION to Norm:  Continue to publicize the XInclude 1.1
Requirement and Use Cases WG Note to potentially interested
parties and see if you can drum up any feedback.
Received on Monday, 12 March 2012 14:29:53 UTC

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