I pushed a revised change draft for Issue #98 , “Add encoding property to file object”: Documents/ChangeDrafts/Active/sarif-v2.0-issue-98-file.encoding-property.docx The only difference from the previous version is what we discussed at the last TC meeting: there is no default value for run.defaultFileEncoding . If a file object’s encoding property is missing, and run.defaultFileEncoding is also missing, then the file’s encoding is taken to be unknown. I will move to adopt this change at tomorrow’s TC meeting. Thanks, Larry