The summary for the SG16 meeting held August 21st, 2019 is now
available. For those that attended, please review and suggest corrections:
- https://github.com/sg16-unicode/sg16-meetings#august-21st-2019

The next meeting is scheduled for Wednesday, September 4th, from
3:30-5:00pm EDT. An invitation (from invite_at_[hidden]
<mailto:invite_at_[hidden]>) has been sent to the mailing list and
prior attendees. The draft agenda is:
- Discuss Corentin's draft D1854R0 - Conversion to execution encoding
should not lead to loss of meaning
   - https://cor3ntin.github.io/posts/encoding/D1854.pdf
- Discuss a few follow up items from P1689, "Format for describing
dependencies of source files", following discussion in SG15.
   - Bikeshed "data". What do we call the code unit equivalent in path
names?
   - Are we ok stating that JSON readers/writers are not allowed to
apply Unicode normalization?
   - Are we ok with allowing a BOM (JSON doesn't permit one)?
- Is "execution character set" the right term for the run-time locale
dependent encoding used by the character classification and conversion
functions?

For any new attendees: The meetings are video conferences conducted via
BlueJeans. If you are planning to attend, please test your system by
visiting https://bluejeans.com/111 before the scheduled meeting time.

Tom.