RE: Agenda for XML Core WG telcon of 2014 September 17

Folks:
I have to miss tomorrow, too.  However, Loren and I did meet shortly after our last meeting, and we made progress on our action.

As it turns out (thanks to Loren) I was wrong about worrying about Bugzilla.  The actual errata are in the following document, graciously provided by MSM:
https://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.errata-2012.html


I don’t believe there are errata for datatypes.

It would be good for Core to review this document.  I believe that there are normative changes, but I don’t think they’re >breaking< changes.

Also, the following document has Bugzilla views of issues discussed but not closed:
http://www.w3.org/XML/XMLSchema/v1.1/1e/errata.html#Errata1


For now, I think Loren and I agree that XML Core should consider including the items already integrated in the first document above for the purposes of 2e.

Best regards,
David

From: Loren Cahlander [mailto:loren.cahlander@gmail.com]
Sent: Tuesday, September 16, 2014 2:39 PM
To: Paul Grosso
Cc: core
Subject: Re: Agenda for XML Core WG telcon of 2014 September 17

I need to send my regrets for tomorrow.

I will have my review of the xsd errata completed by Friday.

My proxy to the chair.

Loren

Sent from my iPad

On Sep 15, 2014, at 10:18 AM, Paul Grosso <paul@paulgrosso.name<mailto:paul@paulgrosso.name>> wrote:
We have an XML Core WG phone call scheduled for Wednesday,
September 17, 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<http://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/


ACTION to Henry: Read the post-February 6 email at
http://lists.w3.org/Archives/Public/xml-editor/2014JanMar/

and let us know what you think we should do.


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,
but that make take help from Henry or Michael.  Loren
will try to contact Michael again.

We will need a diff (or list of changes) and a test suite.
Loren says the diff is already available.

We need to see if any of the changes are normative.
It appears that none of the changes require a chance
in the test suite.

ACTION to Loren and David:  Check if any changes are normative
and/or would require a change to the test suite (and that aren't
already supported by implementations).

ACTION to Loren:  Check that he can run the build.


3.  XML Test Suite.

See also http://www.w3.org/XML/Group/Core#xml-test-suite



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


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



Norm raised an issue about xml:base at

http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Sep/0004


wherein he concluded:



 We could say that xml:base and xml:lang aren't

 copied because there are separate controls for them.



 Another option is to say that if xml:base is copied,

 the absolute base URI is used as the attribute's value.
There was some follow up discussion on the list.


6. 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/2014Jun/0006<http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Mar/0006>







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