<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 5, 2017, at 11:52 PM, Andrew James Weaver <<a href="mailto:weevz@uw.edu" class="">weevz@uw.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello all!<div class="">(cc-ing the flac-dev list)<br class=""><div class=""><br class=""></div><div class="">I would like to give an update as to the recent CELLAR work on the FLAC specification.</div><div class=""><br class=""></div><div class="">• Work has been done to make internal and external links more accurate and reliable.</div><div class="">• 'Rice Coding' has been clarified as 'Exponential Golomb Coding.'</div><div class="">• Clarifications have been made for binary representation.</div><div class="">• Typos and other small changes have been fixed for clarity.</div><div class=""><br class=""></div><div class="">Lastly, a version 00 release has been made (available at <a href="https://github.com/privatezero/flac_markdown/releases" class="">https://github.com/privatezero/flac_markdown/releases</a>) and the draft document has been uploaded to the IETF datatracker (<a href="https://datatracker.ietf.org/doc/draft-xiph-cellar-flac/" class="">https://datatracker.ietf.org/doc/draft-xiph-cellar-flac/</a>)</div><div class=""><br class=""></div><div class="">All the best!</div><div class="">Andrew Weaver</div></div></div></div></blockquote></div><br class=""><div class="">From a review of the markdown and the rendered RFC, I’d like to consider renaming many of the components of FLAC from the ALL_CAPS_WITH_UNDERSCORE_STYLE to `Title Case Names in BackTicks` (which is similar to how local components have been named and referenced in the FFV1 and Matroska documents). Thus “METADATA_BLOCK_HEADER” would be `Metadata Block Header` and expressed with that same case and quoting at each reference. I also suggest that the metadata block types such as “METADATA_BLOCK_STREAMINFO” and “METADATA_BLOCK_APPLICATION” simply be renamed as `Streaminfo Block` and `Application Block` and that each of those components be defined as being a `Metadata Block`.</div><div class=""><br class=""></div><div class="">I may send a pull request for this soon but wanted to ask around in case there’s some reason for or advantage of the ALL_CAPS_WITH_UNDERSCORE_STYLE that I’m missing.</div><div class=""><br class=""></div><div class="">Best Regards,</div><div class="">Dave Rice</div></div><div class=""><br class=""></div></body></html>