Re: Agenda for XML Core WG telcon of 2015 March 4

I must also give regrets.  My room reservation was overridden.

Loren

Sent from my iPad

> On Mar 2, 2015, at 3:07 PM, David Ezell <David_E3@VERIFONE.com> wrote:
> 
> Folks:
> I must give regrets, since the Web Payments IG (I’m chairing) decided to use 11:30 Wednesday as its conference time.  This may change.  For now, regrets, and proxy to the chair.
>  
> Best regards,
> David
>  
> From: Paul Grosso [mailto:paul@paulgrosso.name] 
> Sent: Monday, March 02, 2015 11:03 AM
> To: core
> Subject: Agenda for XML Core WG telcon of 2015 March 4
>  
> We have an XML Core WG phone call scheduled for Wednesday, 
> March 4, from 
>          08:30-09:00 Pacific time aka 
>          11:30-12:00 Eastern time aka 
>          16:30-17: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 Potential Errata
> --------------------
> Comment that “or by the Byte Order Mark” is lacking in section 4.3.3:
> http://lists.w3.org/Archives/Public/xml-editor/2013OctDec/0002
> 
> Comment that an entity cannot “begin” with a BOM as suggested in section 4.3.3:
> http://lists.w3.org/Archives/Public/xml-editor/2013OctDec/0003
> 
> ACTION to John and Henry:  Review and comment on the above two comments
> on the discussion of BOMs in section 4.3.3 of the XML spec.
> 
> ----
> 
> Comment about documents with an "empty DTD":
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Jan/thread#msg8
> and
> http://lists.w3.org/Archives/Public/xml-editor/2014JanMar/
> 
> Henry suggests we could probably make the XML spec clearer here;
> see also his comments at
> http://lists.w3.org/Archives/Public/xml-editor/2014JanMar/0004
> 
> Paul sent the WG response at
> http://lists.w3.org/Archives/Public/xml-editor/2014JanMar/0005
> and there was more back from the commentor at
> http://lists.w3.org/Archives/Public/xml-editor/2014JanMar/
> 
> Henry referenced Paul's email at
> http://lists.w3.org/Archives/Public/xml-editor/2014JanMar/0010
> especially Paul's suggestion in point 4, though Henry wasn't
> sure he agreed with the suggestion.
> 
> ACTION to Henry:  Post some suggestion(s) to the list about
> how to address: Comment about documents with an "empty DTD".
> 
> ----
> 
> Question about normalization checking in XML 1.1
> ------------------------------------------------
> John Cowan forwarded an email for us to consider at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Dec/0026
> which I've also forwarded to the xml-editor list at
> http://lists.w3.org/Archives/Public/xml-editor/2014OctDec/0000
> for official/archive purposes.
> 
> Paul wrote some comments in email at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Dec/0028
> 
> Henry checked with Richard who agrees it's a bug, though how
> to fix it isn't obvious.  Probably the only candidates for not
> being normalized are (internal and external) doctypes per email at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2015Jan/0004
> 
> ----
> 
> Potential Erratum to Namespaces
> -------------------------------
> CMSMcQ raised a potential erratum against Namespaces at
> http://lists.w3.org/Archives/Public/xml-names-editor/2014Sep/0000
> with WG discussion started at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Sep/0019
> 
> He says that our latest wording in the definition of 'namespace name'
> (section 2.1) appears to say that an element with no namespace binding
> in scope is in no namespace as opposed to saying its namespace is
> unknown (thereby leaving the possibility that its namespace
> information may be determined by some other methods).
> 
> Norm, Paul, and Henry posted some thoughts on this, and none
> of us feel that the current wording is necessarily bad enough
> to be worth any change.  In particular, Norm doesn't agree with
> what Michael thinks should be the case.  Henry points out that
> HTML5 does "make use of" defining namespaces without the
> namespace spec mechanism.
> 
> Henry had some more (private) exchanges with Michael, and
> Henry will summarize the discussion for the WG.
> 
> ACTION to Henry:  Summarize and provide current status of
> the discussion of this namespace potential erratum.
> 
> ----
> 
> Eric van der Vlist (via Norm) asks what the post-XInclude infoset 
> is for this element:
> 
>   <xi:include xmlns:my="MYNAMESPACE"
>               href="mydoc.xml" fragid="element(foo)"
>               my:root="true"/>
> 
> when mydoc.xml is:
> 
> <doc xmlns:my="YOURNAMESPACE">
>   <my:note xml:id="foo">
>     <my:x/>
>   </my:note>
> </doc>
> 
> We decided that this isn't an infoset problem, it's just a
> serialization issue.  Paul wrote a draft response at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2015Feb/0013
> 
> ACTION to Norm, Henry (and others):  Read and comment on
> Paul's suggested response to Eric, especially on the question
> of whether we should add anything to the latest XInclude 1.1 draft.
> 
> 
> 3. Submitting XML Schema 1.1 to ISO
> 
> See also
> https://www.w3.org/XML/Group/Core#xml-schema
> 
> We have decided we will first publish XML Schema 1.1 2E (with
> approved errata).  After that, we would send XML Schema 1.1 2E
> (only) to ISO.
> 
> Loren has offered to do the editorial duties, and David
> talked to CMSMCQ about getting some more help in the details.
> 
> It looks like there are 3 bugs for Structures, none for Datatypes,
> but after checking with Michael, he found
> https://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.errata-2012.html
> which shows 8 errata items whereas bugzilla shows only 3.
> 
> We discussed
> https://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.errata-2012.html
> 
> Henry figures we can just publish this document.
> 
> Loren believes the latest document includes everything,
> so the next step is to push it through the tool chain.
> 
> We will need a diff (or list of changes).
> Loren says the diff is already available.
> 
> We needed to consider whether any of the changes are normative
> and/or require a change to the test suite.  After some discussion,
> we decided we should just create a PER.
> 
> ACTION to Loren:  Create the PER, i.e., XML Schema 1.1 Second Edition,
> and post (e.g., at http://www.w3.org/XML/Group/2014/12/xschema11.html)
> for the WG to review (talk to Paul if you need help so posting).
> 
> 
> 4.  XML Test Suite. 
> 
> See also http://www.w3.org/XML/Group/Core#xml-test-suite 
> 
> 
> 5.  LEIRIs--see http://www.w3.org/XML/Group/Core#leiri 
> 
> We have planned to issue the following spec editions referencing 
> LEIRIs (and any outstanding errata): 
> 
> * XML 1.0 6th Edition (John to be editor) 
> * XML 1.1 3rd Edition (John to be editor) 
> * XInclude 3rd Edition (Paul to be editor) 
> 
> but all this is on hold awaiting resolution of IRIbis. 
> 
> 
> 6.  XInclude 1.1--see http://www.w3.org/XML/Group/Core#xinclude 
> 
> On 2012 February 14, we published 
> XInclude 1.1 Requirement and Use Cases 
> http://www.w3.org/TR/xinclude-11-requirements/ 
> 
> On 9 October 2012, we published our FPWD of XInclude 1.1 at
> http://www.w3.org/XML/2012/10/WD-xinclude-11-20121009/
> 
> On 15 January 2013, we published our (first) Last Call of
> XInclude 1.1 at
> http://www.w3.org/TR/2013/WD-xinclude-11-20130115/
> and Paul sent the transition announcement at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2013Jan/0012
> (also cc-ing the chairs mailing list).
> 
> On 2013 October 8, we published the XInclude 1.1 CR at
> http://www.w3.org/TR/2013/CR-xinclude-11-20131008/
>  
> Norm reports that Michael Kay's code just accesses Xerces code, 
> so Norm might have to work with Xerces. 
>  
> DV reports that he is busy and so cannot commit to a deadline
> for adding XInclude 1.1 support to libxml.
>  
> ACTION to Norm:  Continue to work toward getting XInclude 1.1
> implementations and document them in our implementation report.
>  
> Note also the desire for another test case for the XInclude test suite per
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Apr/0000
> Norm may see if he knows anyone still working on Xerces.
>  
> Norm is planning to write a SAX filter to implement XInclude 1.1.
> He believes this will lead to a way for using XInclude 1.1 with
> Saxon's XSLT processor and most any other Java based tool.
>  
> Jirka has implemented a subset of an XInclude processor
> in XSLT; it deals mainly with the new copy-attributes feature.
>  
> We have published (another) Last Call 2014 December 16 at
> http://www.w3.org/TR/2014/WD-xinclude-11-20141216/
>  
> The Last Call period ended January 17.  There were no comments.
>  
> Paul drafted a Transition Request (including SOTD wording) at
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2015Feb/0010
> Liam said Paul should send it to Ralph and PLH (not Philipp Hoschka).
> Liam said we might not need a telcon.
>  
> ACTION to Norm:  Create the pub-ready CR taking into account the
> wording/URLs in Paul's draft Transition Request (but make the
> proposed pubdate [and corresponding URLs] some reasonable future
> date).
> 
> 7. MicroXML
> 
> MicroXML is not in our new charter, but we can discuss it.
> We will leave this as an ongoing item in our standing agenda.
> 
> 
> 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/2014Nov/0027
> 
> 
> 
> 
> This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.