Efficient Extensible Interchange Working Group Teleconference

28 Feb 2017

See also: IRC log




Canonical EXI - 4.3.1 and 4.3.2


DP: I am going to provide a simple example. Strict mode and schema requires a string.
... I will propose the change.

Canonical EXI section 4.2.2


DP: I should change "MUST NOT" to "should not".

Canonical EXI section 4.2


DP: I will provide links to sub-sections.

Efficient XML Interchange - Wikipedia

DB: We should do an update.
... If we agree on changes, I can apply them.
... Update the name.

DP: You can have same page with an alias.
... We can create the same content, and use it from two URL.

DB: We want to change top-level URL.

DP: Transportation redirects you to Transport.

DB: Top-level is Efficient XML Interchange.

DP: I would not remove old one.
... I would keep "Efficient XML Interchange".

DB: We should make "Efficient Extensible Interchange" the primary name.

DP: It makes sense.

DB: In history, we can add renaming.

<brutzman> most recent press release: https://www.w3.org/2011/03/exi-pr.html.en W3C Extends Reach of XML to New Devices, Applications March 2011

<brutzman> In November 2016, the working group was renamed to "Efficient Extensible Interchange (EXI)" from "Efficient XML Interchange (EXI)" to reflect the broader scope of EXI applicability.

<brutzman> ... that was a draft sentence to add to Wikipedia EXI page, History section

<brutzman> entered that change to wikipedia: https://en.wikipedia.org/wiki/Efficient_XML_Interchange

<dape> Wikipedia redirect, see https://en.wikipedia.org/wiki/Wikipedia:Redirect

<brutzman> We probably want a similar sesntence about renaming near the top of the EXI Working Group page https://www.w3.org/XML/Group/EXI/

<brutzman> redirect is now in place, thanks Daniel: https://en.wikipedia.org/wiki/Efficient_Extensible_Interchange

<brutzman> we should also change the name of the working group at the top of the page...

<brutzman> discussion about renaming top-level page, difference between EXI recommendation and EXI working group, user expectations, redirects, etc.

<brutzman> perhaps we should make "EXI" the top-level link since it applies equally to EXI Rec, working group, EXI4JSON etc.

<brutzman> Suggestion: we just fix wording on current page and defer any reshuffling of priority page, it will be good to think about it further.

<brutzman> ... so only recommended modification is second sentence "It was developed by the W3C's Efficient XML Interchange Working Group" to "

<brutzman> ... to "It was developed by the W3C's Efficient Extensible Interchange Working Group"

<brutzman> (discussed) OK change made and will appear at https://en.wikipedia.org/wiki/Efficient_XML_Interchange

<brutzman> Doing just a little bit on wikipedia page is likely a good idea for each meeting.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/02/28 19:58:23 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/#status//

WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: taki
Inferring Scribes: taki

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 28 Feb 2017
Guessing minutes URL: http://www.w3.org/2017/02/28-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]