I pushed a change draft for Issue #240 , “Consider removing type inconsistency with message property in exception object” Documents/ChangeDrafts/Active/sarif-v2.0-issue-240-exception-message.docx We will move its adoption at TC #24 on Wednesday 9/26. This was the only message property in the spec that was defined as a string rather than a message object. There was (what seemed to be) a perfectly good reason for this, but both Paul and Michael tripped over this in the course of a week, so obviously this choice violated the “principal of least surprise”. Thanks, Larry