Subject: RE: [sarif] Change draft for #159 (Id property renames) and #166 (engineering system conformance profile)
I botched both the title and the link for the change draft. Here it is:
I forgot the usual formula: “I will move its adoption at TC #17 on May 16th”.
I pushed a change draft for these two issues:
The change draft is here:
In a previous email, I explained the rationale for adding the “engineering system” performance profile. The rationale for the property name changes is in Issue #159, but I reproduce it here for your convenience:
… [W]e now understand the distinction between globally unique "instance identifiers" (like the identifier that uniquely identifies the reporting of a result in a specific run) and "logical identifiers" (like the identifier that tells you that this is the x86 variant of the nightly security tools run). We want to define the "instance identifiers" as GUIDs, we want to define the logical identifiers as "hierarchical strings", and we want the property names to make that distinction explicit to the reader of the log file. ...