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

Re: Agenda for XML Core WG telcon of 2012 February 8

From: Innovimax W3C <innovimax+w3c@gmail.com>
Date: Wed, 8 Feb 2012 11:56:31 +0100
Message-ID: <CAAK2GfGo1R9z6QAThn4Qq0m8WUyeC5XX37Zx-rPGym555EmW+g@mail.gmail.com>
To: Paul Grosso <paul@paulgrosso.name>
Cc: core <public-xml-core-wg@w3.org>
Dear all,

Please accept my regrets for today telcon

My proxy to the chair

Best regards,

Mohamed

On Mon, Feb 6, 2012 at 5:10 PM, Paul Grosso <paul@paulgrosso.name> wrote:
> We have an XML Core WG phone call scheduled for Wednesday,
> February 8, from
>     08:30-09:00 Pacific time aka
>     11:30-12:00 Eastern time aka
>     15:30-16:00 UTC
>     16:30-17:00 in Ireland and the UK
>     17:30-18:00 in middle (most of) Europe
> on the Zakim W3C Bridge, +1 617 761 6200, passcode 9652#.
> We also use IRC channel #xmlcore on irc.w3.org:6665 .
>
> See the XML Core group page [1] for pointers to current documents
> and other information. If you have additions to the agenda, please
> email them to the WG list before the start of the telcon.
>
> Please also review our group page's task list [2] for accuracy and
> completeness and be prepared to amend if necessary and accept it
> at the beginning of the call.
>
>
> Agenda
> ======
> 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).
>
>
> 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.
>
> 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.
>
> 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.
>
>
> 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.
>
>
> 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
>
>
>
>
>
>
>



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Wednesday, 8 February 2012 10:59:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 February 2012 10:59:30 GMT