Minutes for XML Core WG telcon of 2016 March 30

Attendees
---------
Norm
Paul
Jirka

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

Regrets
-------
Liam
David, proxy to the chair
Mohamed, proxy to the chair

Absent organizations
--------------------
University of Edinburgh
NACS (with regrets, proxy to the chair)
Innovimax (with regrets, proxy to the chair)
W3C (with regrets)

Our next telcon is scheduled for April 13.



> 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. (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
> http://www.w3.org/TR/2015/CR-xinclude-11-20150630/
> 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:
> http://www.xmlmind.com/xmleditor/changes.html#v6.2.0

Jirka will plan to run the XML Mind XML Editor through the new test suite.


> 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 has made a first pass at updating the test suite; see
> https://lists.w3.org/Archives/Public/public-xml-core-wg/2016Mar/0004
>
> ACTION to Norm:  Update the implementation report and test suite.

Norm has made updates to the test suite and will run them
through his implementation.


>
> ---
>
> 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
> https://lists.w3.org/Archives/Public/public-xml-core-wg/2016Feb/0003
>
> 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.

Norm expects to have an updated spec in two weeks.


>
>
> paul
>
> [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/2016Feb/0005
>
>
>