18:36:34 RRSAgent has joined #exi 18:36:34 logging to http://www.w3.org/2017/02/28-exi-irc 18:36:36 RRSAgent, make logs public 18:36:36 Zakim has joined #exi 18:36:38 Zakim, this will be EXIWG 18:36:38 ok, trackbot 18:36:39 Meeting: Efficient Extensible Interchange Working Group Teleconference 18:36:39 Date: 28 February 2017 18:36:50 zakim, this is exi 18:36:50 got it, taki 18:43:43 TOPIC: Canonical EXI - 4.3.1 and 4.3.2 18:43:50 https://lists.w3.org/Archives/Public/public-exi-comments/2017Jan/0000.html 18:44:25 DP: I am going to provide a simple example. Strict mode and schema requires a string. 18:44:54 DP: I will propose the change. 18:49:08 TOPIC: Canonical EXI section 4.2.2 18:49:11 https://lists.w3.org/Archives/Public/public-exi-comments/2017Feb/0000.html 18:52:09 DP: I should change "MUST NOT" to "should not". 18:52:18 TOPIC: Canonical EXI section 4.2 18:52:30 https://lists.w3.org/Archives/Public/public-exi-comments/2017Feb/0001.html 18:53:06 DP: I will provide links to sub-sections. 18:55:43 TOPIC: Efficient XML Interchange - Wikipedia 18:57:35 DB: We should do an update. 18:57:49 DB: If we agree on changes, I can apply them. 18:57:58 DB: Update the name. 18:58:54 DP: You can have same page with an alias. 18:59:27 DP: We can create the same content, and use it from two URL. 19:03:34 DB: We want to change top-level URL. 19:04:26 DP: Transportation redirects you to Transport. 19:04:53 DB: Top-level is Efficient XML Interchange. 19:05:23 DP: I would not remove old one. 19:05:38 DP: I would keep "Efficient XML Interchange". 19:06:51 DB: We should make "Efficient Extensible Interchange" the primary name. 19:07:00 DP: It makes sense. 19:07:50 DB: In history, we can add renaming. 19:15:22 brutzman has joined #exi 19:16:53 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 19:19:04 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. 19:19:28 ... that was a draft sentence to add to Wikipedia EXI page, History section 19:25:59 dape has joined #exi 19:27:23 entered that change to wikipedia: https://en.wikipedia.org/wiki/Efficient_XML_Interchange 19:28:59 Wikipedia redirect, see https://en.wikipedia.org/wiki/Wikipedia:Redirect 19:31:57 We probably want a similar sesntence about renaming near the top of the EXI Working Group page https://www.w3.org/XML/Group/EXI/#status 19:32:41 s/#status// 19:42:36 redirect is now in place, thanks Daniel: https://en.wikipedia.org/wiki/Efficient_Extensible_Interchange 19:43:46 we should also change the name of the working group at the top of the page... 19:49:49 discussion about renaming top-level page, difference between EXI recommendation and EXI working group, user expectations, redirects, etc. 19:50:49 perhaps we should make "EXI" the top-level link since it applies equally to EXI Rec, working group, EXI4JSON etc. 19:51:35 Suggestion: we just fix wording on current page and defer any reshuffling of priority page, it will be good to think about it further. 19:52:33 ... so only recommended modification is second sentence "It was developed by the W3C's Efficient XML Interchange Working Group" to " 19:52:54 ... to "It was developed by the W3C's Efficient Extensible Interchange Working Group" 19:55:09 (discussed) OK change made and will appear at https://en.wikipedia.org/wiki/Efficient_XML_Interchange 19:55:23 rrsagent, create minutes 19:55:23 I have made the request to generate http://www.w3.org/2017/02/28-exi-minutes.html taki 19:55:45 Doing just a little bit on wikipedia page is likely a good idea for each meeting. 19:58:18 rrsagent, create minutes 19:58:18 I have made the request to generate http://www.w3.org/2017/02/28-exi-minutes.html taki 20:42:42 Zakim has left #exi