XML Core WG Status and Open Actions as of 2011 September 26

The XML Core WG telcons are every other week.

Our next telcon will be 2011 October 5.


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

TPAC week
---------
TPAC will be 31 October through 4 November 2011 in Santa Clara
California.  We are planning to have a f2f during this week:
http://www.w3.org/2011/11/TPAC/ - Meeting Overview page.

Registration is now open:
http://www.w3.org/2002/09/wbs/35125/TPAC2011/
The XML Core WG is meeting Thursday of the TPAC week.  We will NOT
meet on Friday.

Discounted hotel rates end 10 October, registration closes 14 October.

Likely attendance:

Probably will:  Paul, Norm, Henry, Liam
Maybe:  Mohamed
Most likely won't:  John, Daniel, Jirka, Glenn


xml-stylesheet and HTML5
------------------------
Henry started a thread at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Jul/0008

In the HTML5 spec, when dealing with the XML prolog, there is
nothing about processing instructions, so it isn't clear that
browsers would pick up the xml-stylesheet PI.

John Cowan said there was another part of the spec that applies
to that process, but Henry hasn't yet followed up on that.

ACTION to Henry:  Research to ensure that the xml-stylesheet PI
is appropriately referenced from HTML5 and/or 3023bis (the XML
media type definition).

Note that 3023bis could say that browsers should reference
Assoc SS and process the SSPI when processing an XML resource.


Extending XInclude
------------------
Norm sent email on behalf of DocBook at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Jul/0013
asking whether we want to consider extending Xinclude.

The key issue is that xincluding content can often cause
duplicate ids, and the question is whether we can define
some kind of fix up.

See http://docbook.org/docs/transclusion-requirements/#uc-5
for a use case.

See http://www.docbook.org/docs/transclusion/#d6e180 for
some DocBook proposals for id fixup.

A processor might be able to find ids and/or idrefs if xml:id
is used and/or there is a DTD/schema available, and even if 
that is the case, fixup would only work within the included
module, but is that partial case worth augmenting XInclude.

Liam suggests the only real solution is to do a transformation,
so he doesn't feel there is an XInclude solution.

Norm concluded it was not feasible to implement Jirka's proposals 
using xproc alone.

ACTION to Norm:  Try to implement Jirka's proposals using XSLT+XProc.


XML Signature comments
----------------------
Paul's latest response to the comment resolution is at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Sep/0013


XPointer and XPointer Registry
------------------------------
Norm asks whether http://www.w3.org/TR/xptr-framework/
should be updated to point to the XPointer Registry explicitly.


LEIRIs and new editions
-----------------------
We continue to wait to see what might happen with IRIbis.


XML 1.0 6th Edition and XML 1.1 3rd 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.


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.

Norm sent email at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Sep/0011
saying that the existence of RFC 5147 makes the constraint that
@xpointer
must not be present when parse="text" inappropriate.  He suggests we
remove that constraint.

He also suggests that someone should register a text() XPointer scheme 
that implements RFC 5147.

Received on Monday, 26 September 2011 14:25:45 UTC