W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > March 2016

Agenda for XML Core WG telcon of 2016 March 30

From: Paul Grosso <paul@paulgrosso.name>
Date: Tue, 29 Mar 2016 09:36:55 -0500
To: core <public-xml-core-wg@w3.org>
Message-ID: <56FA9307.2070300@paulgrosso.name>
We have an XML Core WG phone call scheduled for Wednesday,
March 30, 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

We are now using Webex for our conferences. See

You can join by phone by dialing +1-617-324-0000 directly and
using an access code of 643 434 633#.

You can also use the Webex client (and have it call you)
by pointing your browser at

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.

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. (None.)

3. XInclude 1.1--see http://www.w3.org/XML/Group/Core#xinclude

On 2015 June 30, we published our second XInclude 1.1 CR at

Norm has an implementation in XML Calabash.
He has also implemented XInclude 1.1 in MarkLogic.

Jirka reports that there is another XInclude 1.1 implementation
in XML Mind XML Editor.  See:

Note also the desire for another test case for the XInclude test suite per

Norm has made a first pass at updating the test suite; see

ACTION to Norm:  Update the implementation report and test suite.


Henry pointed out that Section 4.4 references RFC 3023
which has been superseded by RFC 7303.  The 7303 rules
for determining encoding of XML documents are slightly
different from the 3023 ones.

Henry reviewed the consequences to the spec of changing
3023 to 7303 and sent email with suggested rewording at

ACTION to Norm:  Net editorial tweaking, make this wording
change to the latest XInclude 1.1 draft.  Also, replace
the reference to 3023 with one to 7303.


Paul raised the question of whether the spec requires
the support for RFC 5147. It isn't mentioned under
Application Conformance, but the description of fragid,
it says "for text processing, [the fragid value] is
interpreted as a [IETF RFC 5147] fragment identifier"
and it doesn't discuss what to do if an implementation
doesn't support that.

Norm suggests that we can't force implementations to
support it and that we should clarify the spec to say
that lack of support for fragid when parse=text
should be a recoverable error.

Henry and Paul agree with that suggestion.

ACTION to Norm:  Update the spec to clarify that lack
of support for fragid when parse=text should be a
recoverable error.


[1] http://www.w3.org/XML/Group/Core
[2] http://www.w3.org/XML/Group/Core#tasks
[3] https://lists.w3.org/Archives/Public/public-xml-core-wg/2016Jan/0010
Received on Tuesday, 29 March 2016 14:42:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:40:54 UTC