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

Minutes for XML Core WG telcon of 2012 February 8

From: Paul Grosso <paul@paulgrosso.name>
Date: Wed, 08 Feb 2012 15:02:43 -0600
Message-ID: <4F32E2F3.4090506@paulgrosso.name>
To: public-xml-core-wg@w3.org
Attendees
---------
Paul
Henry
John

[3 organizations (5 with proxies) present out of 9]

Regrets
-------
Daniel, proxy to the chair
Mohamed, proxy to the chair
Norm
Liam
Jirka


Absent organizations
--------------------
IBM
Innovimax (with regrets, proxy to the chair)
Marklogics (with regrets)
W3C (with regrets)
Daniel Veillard (with regrets, proxy to the chair)
Jirka Kosek (with regrets)

Our next telcon is February 22.


> 1. Accepting the minutes from the last telcon [3] and
> the current task status [2] (have any questions, comments,
> or corrections ready by the beginning of the call).
>

Accepted.

>
> 2. Miscellaneous administrivia and document reviews.
>
> xml-stylesheet and HTML5
> ------------------------
> Henry 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.
>
> ACTION to Henry: File a bug against the HTML5 spec saying that it should
> support styling XML with CSS.

ACTION to Henry continued.

>
> The CSS2 spec says something about styling XML with CSS.
> Henry also notes http://www.w3.org/Style/styling-XML.en.html.
>
> Henry's tests are at
> http://www.w3.org/XML/2011/11/ssTests/
> You need to look at the README and README2 files there.
>
>
> issues with the Polyglot draft
> ------------------------------
> Henry sent email with various potential issues at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Nov/0037
>
> Polyglot draft: BOM
> -------------------
> 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/index.html
>
> Henry: I think we should file an issue against Polyglot about the BOM.
>
> ACTION: Henry to file an issue against Polyglot about the BOM.

ACTION to Henry continued.

>
> 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.

ACTION to Henry continued.

>
>
> 3. XML 1.0--see http://www.w3.org/XML/Group/Core#xml-errata
>
> We are creating an XML 1.0 6th Edition and XML 1.1 3rd (or
> perhaps 6th) 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.
>
>
> 4. XML Test Suite.
>
> See also http://www.w3.org/XML/Group/Core#xml-test-suite
>
> ACTION to Henry: Construct a test case for the XML test suite issues
> raised by Frans Englich:
> http://lists.w3.org/Archives/Public/public-xml-testsuite/2007Mar/
>
> 5. Namespaces in XML 1.0/1.1--see
> http://www.w3.org/XML/Group/Core#ns1.0
> and http://www.w3.org/XML/Group/Core#ns1.1.
>
>
> 6. LEIRIs--see http://www.w3.org/XML/Group/Core#leiri
>
> We had planned to issue the following spec editions referencing LEIRIs:
>
> * XML 1.0 6th Edition
> * XML 1.1 3rd Edition
> * XInclude 3rd Edition
>
> We continue to wait to see what might happen with IRIbis.
>
>
> 7. xml:id--see http://www.w3.org/XML/Group/Core#xml-id
>
>
> 8. XML Base 2nd Ed--see http://www.w3.org/XML/Group/Core#xml-base
>
>
> 9. XLink 1.1--see http://www.w3.org/XML/Group/Core#xlink1.1
>
>
> 10. XInclude 3rd Ed--see http://www.w3.org/XML/Group/Core#xinclude
>
> We are creating an 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"
> ------------------------------------
> Previous email discussion at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Oct/thread.html#msg46
>
> and
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2011Nov/thread.html#msg12
>
>
> 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
>
> We are leaning toward choice #2 which Norm will include in the
> XInclude 1.1 requirements document and initial draft.
>
>
> Extending XInclude
> ------------------
> We've discussed extending xinclude to copy attributes on the xinclude
> element down to the root included element.
>
> 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.
>
>
> XInclude 1.1
> ------------
> This would address the two issues discussed above:
> * @xpointer when parse="text"
> * copying attributes from the xinclude element to the root
> included element
>
> If we want to produce 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
> but we can discuss requirements now.
>
> Norm drafted an initial XInclude 1.1 requirements document at
> http://www.w3.org/XML/2012/01/xinclude-11-requirements/
>
> We plan to clean up this draft a bit and publish it
> as a WG Note.

The WG had CONSENSUS to publish
http://www.w3.org/XML/2012/01/xinclude-11-requirements/
as a WG Note.

ACTION to Paul, Norm:  Add references to:
http://www.ietf.org/rfc/rfc5147.txt
and one or both of
http://docbook.org/docs/transclusion-requirements/
http://docbook.org/docs/transclusion/
and complete the SOTD and publish as a WG Note.

>
> 11. Associating Stylesheets.
>
> See also http://www.w3.org/XML/Group/Core#assoc-ss
>
> AssocSS 2nd Ed is now a Recommendation at
> http://www.w3.org/TR/2010/REC-xml-stylesheet-20101028/
>
>
> 12. xml-model
>
> See also http://www.w3.org/XML/Group/Core#assoc-schemas
>
> The Second Edition has been published as a WG Note at
> http://www.w3.org/TR/2011/NOTE-xml-model-20110811/
>
>
> paul
>
> [1] http://www.w3.org/XML/Group/Core
> [2] http://www.w3.org/XML/Group/Core#tasks
> [3] http://lists.w3.org/Archives/Public/public-xml-core-wg/2012Jan/0016
>
Received on Wednesday, 8 February 2012 21:03:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 February 2012 21:03:23 GMT