15:59:00 RRSAgent has joined #webfonts 15:59:00 logging to https://www.w3.org/2021/08/31-webfonts-irc 15:59:16 Zakim has joined #webfonts 15:59:33 chris has joined #webfonts 15:59:37 zakim, this is webfonts wg meeting 15:59:37 got it, Vlad 15:59:40 rrsagent, here 15:59:40 See https://www.w3.org/2021/08/31-webfonts-irc#T15-59-40 15:59:45 present+ 15:59:52 present+ 16:00:09 sergeym has joined #webfonts 16:01:43 I raised 5 issues. 3 should be addressed before publication. I have simple PR for all of them. The other two are just so i don't forget 16:01:44 https://github.com/w3c/IFT/issues 16:03:15 jpamental has joined #webfonts 16:04:12 present+ Venkat 16:04:17 present+ myles 16:04:18 present+ 16:04:23 Garret has joined #webfonts 16:04:29 present+ 16:04:51 rrsagent, make logs public 16:05:21 present+ 16:05:27 scribenick: jpamental 16:05:28 scribenick jpamental 16:05:38 chair: vlad 16:05:48 zakim, list attendees 16:05:48 As of this point the attendees have been chris, Vlad, Venkat, myles, jpamental, Garret, sergeym 16:07:03 Garret: presenting the spec, found here https://w3c.github.io/IFT/Overview.html (covers patch-subset, range request is coming) 16:07:27 It also covers the protocol negotiation 16:07:42 Garret: Myles will be contributing range request 16:08:26 Garret: pointing out we're using CBOR for encoding 16:09:01 Garret: pointing out SparseBitSet section along with IntegerList data structures 16:09:56 Garret: showing specs for subsetting variable axes 16:11:04 Garret: Sections on Client and Server to describe desired behaviors on both parts, but intentionally broad, without getting overly specific on implementation 16:12:15 Garret: server responds to request from client by sending more than the bare minimum of the client request, but implementor can decide on how much more in order to be more efficient with subsequent requests 16:12:45 q+ 16:13:37 Garret: Showing miscellaneous sections at the end covering computing Checksums, Codepoint reordering, and patch formats 16:14:05 Garret: Mentioning how to implement in HTML/CSS to let the author suggest how the transfer should work in the font-face declaration 16:14:10 q? 16:14:42 https://github.com/w3c/IFT/issues 16:15:08 Chris: mentioned that he had raised 5 issues on the spec, at least 3 of which should be resolved before publication 16:15:19 Myles: I also have some questions 16:16:19 Chris: Proposing some language changes under Privacy and Security considerations 16:16:31 Garret: These look good, I will review the PR 16:17:01 Chris: link cleanup, adding the w3c ID 16:17:07 Garret: I will review that PR 16:17:56 Chris: The section titled 'In HTML', but it's not accurate. Split into 2 sections 'One in CSS', another about protocol negotiation 16:18:05 Garret: agreed, will review the PR 16:18:50 Myles: You mentioned 2 different hash algorithms. what are they? 16:19:01 Garret: These are just checks to make sure things are working correctly 16:19:08 Myles: what happens if they don't match? 16:19:45 Garret: The client is supposed to re-request from scratch if things don't match up. Expected that this will be rare, but better than allowing errors to accumulate 16:19:46 Ok so they re-request to get a known good font, seems correct to me 16:21:16 q+ The hashes are on the font right, not the server software 16:21:19 Myles: I'm worried about multiple back-end servers handling subsequent requests (like at Google Fonts). Maybe there should be a way to ensure one server (with the same software and files) get fulfilled with same versions, etc 16:21:43 Garret: We have a 'sort of similar' idea in Google Fonts, but not quite. I'll think about that 16:22:56 Garret: I'm not certain this will be an issue, but will look into it further 16:23:40 Myles: If the second server has different versions of software it might not be able to produce a new patch correctly 16:23:43 we should raise this one as an issue 16:24:06 Garret: You may be right, I'll follow up and detail a new issue on GitHub 16:24:37 Myles: This doesn't need to stop us from publishing now, but we just have to follow up 16:24:55 Vlad: are there any objections to publishing this as the first working draft? 16:25:42 Vlad: Don't forget that this triggers the first step in patent review 16:26:28 Also if there are no patent concerns, there is nothing that needs to be done 16:26:54 Vlad: I hear no objections 16:26:54 resolved: Publish FPWD of Incremental Font Transfer 16:27:03 rrsagent, here 16:27:03 See https://www.w3.org/2021/08/31-webfonts-irc#T16-27-03 16:27:17 rrsagent, draft minutes 16:27:17 I have made the request to generate https://www.w3.org/2021/08/31-webfonts-minutes.html chris 16:27:51 rrsagent, make logs public 16:28:00 rrsagent, draft minutes 16:28:00 I have made the request to generate https://www.w3.org/2021/08/31-webfonts-minutes.html chris 16:28:29 Meeting: Fonts WG 16:28:32 rrsagent, draft minutes 16:28:32 I have made the request to generate https://www.w3.org/2021/08/31-webfonts-minutes.html chris 16:32:32 rrsagent, make minutes 16:32:32 I have made the request to generate https://www.w3.org/2021/08/31-webfonts-minutes.html chris 16:33:10 so actually, https://github.com/w3c/transitions/issues/374 16:34:24 (we explain W3C Patent policy) 16:38:11 (we explain W3C Wide Review) 16:38:21 (we explain test driven development) 16:39:59 Vlad: TPAC happening 16:40:00 https://www.w3.org/2021/10/TPAC/Overview.html 16:40:35 vlad: opportunity for demos. Can we do one? 16:41:22 Garret: we could do an in-browser demo to gain awareness 16:41:58 ... deck used at ATypI technical talks 16:43:53 (adjourned for realz) 16:44:00 rrsagent, make minutes 16:44:00 I have made the request to generate https://www.w3.org/2021/08/31-webfonts-minutes.html chris 18:41:10 Zakim has left #webfonts