<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>The summary for the SG16 meeting held August 21st, 2019 is now
available. For those that attended, please review and suggest
corrections:<br>
- <a moz-do-not-send="true"
href="https://github.com/sg16-unicode/sg16-meetings#august-21st-2019">https://github.com/sg16-unicode/sg16-meetings#august-21st-2019</a></p>
<p> The next meeting is scheduled for Wednesday, September 4th, from
3:30-5:00pm EDT. An invitation (from <a
href="mailto:invite@bluejeans.com">invite@bluejeans.com</a>) has
been sent to the mailing list and prior attendees. The draft
agenda is:<br>
- Discuss Corentin's draft D1854R0 - Conversion to execution
encoding should not lead to loss of meaning<br>
- <a moz-do-not-send="true"
href="https://cor3ntin.github.io/posts/encoding/D1854.pdf">https://cor3ntin.github.io/posts/encoding/D1854.pdf</a><br>
- Discuss a few follow up items from P1689, "Format for describing
dependencies of source files", following discussion in SG15.<br>
- Bikeshed "data". What do we call the code unit equivalent in
path names?<br>
- Are we ok stating that JSON readers/writers are not allowed to
apply Unicode normalization?<br>
- Are we ok with allowing a BOM (JSON doesn't permit one)?<br>
- Is "execution character set" the right term for the run-time
locale dependent encoding used by the character classification and
conversion functions?</p>
<p>For any new attendees: The meetings are video conferences
conducted via BlueJeans. If you are planning to attend, please
test your system by visiting <a href="https://bluejeans.com/111">https://bluejeans.com/111</a>
before the scheduled meeting time.<br>
<br>
Tom. </p>
</body>
</html>