XML Core WG Status and Open Actions as of 2011 November 21

The XML Core WG telcons are every other week.

Our next telcon will be November 30.

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

xml-stylesheet and HTML5
------------------------
Henry and Paul met with Anne van Kesteren at the f2f.

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 some more work to do for Hickson.

ACTION to Henry:  Do some more fiddling with reporting the issue.

HT: I have an *xhtml* doc with an xml-stylesheet PI with type=text/xsl.
Does the HTML5 specs cover this case? 

ACTION to Henry: Consider asking the above question of the HTML5 WG
after doing some research to determine what does currently happen.

HT: Section 5.5.3 doesn't appear to distinguish between xhtml and 
non-xhtml xml documents.  The spec does not make it obvious what 
should happen for non-xhtml xml documents.

ACTION to Henry:  Think about the above statement and determine
if we need to file a bug report or ask a question about it.


Extending XInclude
------------------
Henry, Paul, Liam, Murray discussed this at the f2f (see minutes).

Those present generally liked the idea of extending xinclude to copy
attributes on the xinclude element down to the root included element,
but we didn't agree on details.

Some issues include:

1.  exactly what attributes to copy?  Henry and Liam preferred to 
copy un-prefixed attributes (except those in the xinclude spec) too.

Norm worries what this would mean if we add another attribute
in the XInclude spec?

Henry wants to be able to have unprefixed attributes copied
onto the root included element.

Henry: we could add a new "copy me without prefix" namespace 
to xinclude.

Norm doesn't need that, but could live with it.

2.  what to do about attribute conflict (error or one or the other
wins).

3.  whether we should "log" additions (e.g., via an attribute that 
says what attributes were added).

At first, we didn't think this was much of a concern, but then we
realized perhaps it was something worth considering.

4.  whether we should have some way for targets to say whether they
can be xincluded and/or, when included, have attributes added.

We had a discussion about xinclude being like img/@src rather than
a/@href in that xincluding things is basically "stealing" them.

Yes, it's worth thinking about this a bit, but it seems like
this issue exists already elsewhere, and it may not make sense
to worry about this in XInclude.

We aren't quite ready to start drafting Xinclude 1.1,
but discussion will continue.

Liam tells us that it's okay to work on requirements for an
XInclude 1.1, but before publishing a FPWD, we'll need a charter
revision.  He doesn't anticipate any problems, provided there's 
a realistic schedule for getting to Rec.


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.


XInclude @xpointer when parse="text"
------------------------------------

Henry, Paul, Liam, Murray discussed this at the f2f (see minutes).

Previous email discussion at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Oct/thread.ht
ml#msg46

We seem to have three choices:

1.  allow use of the @xpointer attribute when parse=text
2.  add a new "@textptr" attribute to use when parse=text
3.  add a new "@fragid" attribute to use in all cases and possibly
    deprecate the @xpointer attribute

The assembled group was generally positive about working on a solution
of some sort.  It felt like the "right" solution if we could time-travel
backwards would be #3, the easiest spec change was to #2, though some 
of us felt that #1 was the best choice at the present.

Paul restarted the email discussion at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Nov/thread.ht
ml#msg12

Received on Monday, 21 November 2011 16:30:55 UTC