14:02:16 RRSAgent has joined #exi 14:02:16 logging to http://www.w3.org/2016/03/29-exi-irc 14:02:18 RRSAgent, make logs public 14:02:18 Zakim has joined #exi 14:02:20 Zakim, this will be EXIWG 14:02:20 ok, trackbot 14:02:21 Meeting: Efficient XML Interchange Working Group Teleconference 14:02:21 Date: 29 March 2016 14:02:26 scribe: TK 14:02:32 scribeNick: taki 14:03:21 dape has joined #exi 14:14:24 TOPIC: W3C TPAC 2016 14:14:40 scribe: dape 14:14:44 scribeNick: DP 14:14:55 scribeNick: dape 14:15:02 scribe: DP 14:15:11 TK: 14:16:02 TK: At most 2 people on the side. Don and Javier showed interest joining remotely 14:16:36 ... sometimes very productive to meet even with few people 14:17:20 ... one option Carine mentioned is: 1st submit form to meet and later re-consider 14:18:32 brutzman has joined #exi 14:18:39 DP: if we do not conflict with WoT meetings I expect also some Siemens people have interest 14:20:23 DB: will try to attend by phone 14:21:56 ... w.r.t. interest of joining WoT group.. I wonder about the possible relations 14:22:59 We are getting a lot of good work done at a steady pace, even with a small number of people now. 14:23:15 First law of engineering: "if it isn't broken, don't fix it." 14:23:40 DP: No decision yet.. not even formally discussed 14:23:43 we can also have a 1day meeting 14:23:49 Nevertheless we might report back to WoT group once or twice a month, or perhaps have some other informal regular interaction. 14:24:03 That would likely benefit both groups over the long term. 14:24:04 or a breakout session if there are in the agenda 14:24:39 TK: this discussion should be raised before TPAC 14:24:45 s/relations/relationships that might occur./ 14:25:15 ... could talk about this in Montreal F2F 14:25:34 If someone in EXI can go to WoT TPAC meeting, we might offer a report. 14:26:58 DP: Taki and I are attending the WoT F2F 14:27:40 Dave Raggett and LIam Quinn both are likely to give us good advice in these matters. 14:27:55 DB: Dave has definitely a good advice... also w.r.t. AMP 14:28:24 Our primary goal should likely be to keep making progress, and also to continue outreach so that others might engage and participate. 14:29:02 s/1day/1 day/ 14:29:04 TK: Can we indicate that we meet at TPAC also indicating avoid conflict with WoT? 14:30:13 DP: I think it makes sense... we don't get an answer about joining WoT the next days 14:31:25 DB: time till 15th of April to decide 14:31:53 Just to be clear about overall strategy - I was not urging that we "join" the WoT group, rather would think that simply commencing a regular dialog would be helpful. Attending another working-group's meeting is always informative. 14:32:02 ... otherwise we can also organize break-out sessions on Wednesday 14:32:59 DP: having a break-out session on Wednesday makes sense either way to me 14:33:13 last year's breakout sessions program: https://www.w3.org/wiki/TPAC/2015/SessionIdeas 14:33:47 also CGs are invited to have 2-hrs meetings this year 14:35:13 TK: will answer the questionnaire before next telecon 14:36:30 TK: Note: April 12th there will be no EXI telecon.. (due to WoT F2F) 14:37:19 TOPIC: EXI for CSS 14:37:47 DP: published first tests on github, https://github.com/EXIficient/exificient-for-css 14:38:11 .. also added some test fiels 14:38:32 s/fiels/files 14:39:36 .. think we should experiment with more test files and add the missing part 14:41:06 ... i think having a solution for CSS, JSON and HTML5 makes sense to show during a break-out session at TPAC 14:42:35 TK: plan to experiment 14:44:05 DP: some missing parts like @media 14:45:03 .. feel free to send me some test files.. 14:45:14 CB: might be able to share some... 14:46:04 DB: is there a CSS test-suite? 14:46:53 Found it: Cascading Style Sheets Official W3C Test Suites https://www.w3.org/Style/CSS/Test/Overview.en.html 14:47:05 DP/DB: test files are more unit test files... not really realistic 14:47:27 s/DB:/CB: 14:48:25 Unit tests are good for compatibility coverage. It is also possible to aggregate stylesheets into something larger using the @import directive. 14:50:07 TOPIC: Extended String 14:50:18 Interesting link on the CSS Test Suites page: Test the Web Forward, W3C's one stop shop for Open Web Platform testing. http://testthewebforward.org 14:51:35 TK: In your last email about annotation you say "grouping".. not sure what you mean 14:54:19 DP: given that an annotation is linked to a type I wondered whether it makes sense to pre-populete the table for a given type 14:54:36 TK: instead of one global tables many tables? 14:54:42 DP: Correct 14:57:09 DP: also maybe we want to have the annotation more general w.r.t to other types.. not only enumerations 14:57:37 TK: agree. Enumerations usually don't need pre-populated values 14:58:47 DP: need to agree on syntax 14:59:41 .. or put the enumeration syntax in xsd:annotation element 15:00:22 TK: thing in xsd:annotation get not parsed by Xerces 15:00:25 DP: correct 15:03:10 TK: Partitioning by type is a possibility 15:03:34 DP: yes, but I am personally not convinced yet 15:03:57 TK: We could also consider one global table and may smaller tables 15:04:12 s/may/many 15:05:30 TK: let's continue discussion in emails 15:07:31 DP: plan to run some tests with the extended string across TTFMS test suite 15:09:32 TK: Do not expect any benefit without shared strings 15:10:04 DP: It depends... for example RDF testfiles have lots of URIs and splitting those uris in smaller parts helps a lot to reduce the size 15:12:33 TOPIC: Canonical EXI 15:13:25 TK: Daniel proposed to change the order of AT production selection 15:13:36 ... new order makes more sense 15:14:03 .. also for OpenEXI 15:14:11 DP: same for EXIficient 15:14:38 TK: one other thing is terminology .. d) and e) are AT(*) 15:15:18 ... in EXI spec we don't qualify [schema-typed value] 15:15:51 .... c) and d) need to be updated with removing [schema-typed value] 15:17:20 DP: Was also wondering whether we should flip b) with c).. 15:18:27 TK: a) and b) next to each other makes more sense... would keep the "new" list as it is 15:18:55 DP: will update the spec... 15:19:15 ... think we are complete. I do not have any open point anymore. 15:19:40 TK: currently last call 15:19:57 .. consider moving it to CR 15:21:05 CB: last call and CR are the same now 15:21:27 TK: moving to CR is also easier? 15:21:41 CB: re-publishing CR is easier 15:22:42 TK: after the change we should have a final review before moving to CR 15:23:17 DP: How is the timing for interop tests? 15:23:22 CB: it is CR 15:24:00 ... moving out of CR requires interoperability 15:32:32 rrsagent, create minutes 15:32:32 I have made the request to generate http://www.w3.org/2016/03/29-exi-minutes.html taki 16:10:46 Zakim has left #exi