Meeting minutes
review pr 281 - drop uri templates
<Vlad> see w3c/
Switched from uri templates to binary format (using opcodes like CFF). Overall simplifies things for implementations. Implementation is done on client and encoder and can confirm it resulted in significant simplications (particularily on the client side).
Will update the github issue to say that implementation is done and what the experience was.
Issue to be updated: w3c/
Client side implementation: googlefonts/
Server side implementation: w3c/
review changes to privacy guidance, PR 282
<Vlad> see w3c/
Garret: updated the privacy section to better expand on how the IFT encoding affects privacy. The most important addition is the mention that use of IFT fonts places some amount of trust in them (no matter how well encoded they are). Recommended privacy sensitive use cases to self host to keep information from transferring out of the site/app.
Lastly, added concrete guidance on how to assess the privacy of a particular encoding by looking at group size, including recommending minimum group sizes based on prior research.
Skef: still need to address the issue of dynamic patches. Is there an issue open for that?
Garret: not yet, let's start one.
Garret: I'll get an issue filed
<ChrisL> w3c/
review editorial changes made by Chris issue 283
Skef and Garret both reviewed and looks good.
RESOLUTION: publish a new working draft.
Chris will work on making that happen.
<ChrisL> Here is the wide review issue
<ChrisL> w3c/
RESOLUTION: request a transition to CR after the working draft is published.
Discussion on what implementations are availabile and/or in progress. So far the fontations IFT client and the w3c/ift-encoder. No one is aware of other implementations at this time.
Chris: any conformance tests updates?
Garret: nothing is done yet, the old patch subset work is no longer applicable.
Tentative next meeting is three weeks from now (July 29th)