RE: Change draft for #248: Associate file location with repo

[Michael Fanning <Michael.Fanning@microsoft.com>]

I am concerned at the difficult in understanding this proposal. I also am wondering whether we have clearly identified the goals of this design.

 

Hereâs the scenario that originally drove this request

 

1. I have a SARIF log file and would like to recreate the enlistment locally in order to get source files that match the analysis
2. I see an originalUriBase that points to the non-deterministic root of the enlistment
3. Iâd like to find the version control details for this root and to sync to it locally.

 

Michael

From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Sunday, December 9, 2018 5:04 PM
To: Larry Golding (Myriad Consulting Inc) <v-lgold@microsoft.com>; OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Subject: [sarif] RE: Change draft for #248: Associate file location with repo

 

That probably read snarkier than I intended 😊 Jimâs description is accurate and much more compact than it would have been if heâd expressed it without the symbols. Itâs just that readers of the spec will need some help to understand it.

 

From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Sunday, December 9, 2018 5:01 PM
To: OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Subject: [sarif] Change draft for #248: Associate file location with repo

 

I pushed a change draft for Issue #248: âVersion control details not strongly associated with resultsâ:

 

Documents/ChangeDrafts/Active/sarif-v2.0-issue-248-versionControlProvenance-file-mapping.docx

 

We will move its adoption at TC 29 on Wednesday December 12^th.

 

We had previously proposed a design for this, but Jim objected and proposed what, after a careful reading, I think is a better one. The new change draft follows Jimâs design.

 

Jim, academic that he is 😊, expressed his mapping algorithm rather abstractly. Fortunately, I was also an academic in a former life, so I interspersed some comments into Jimâs description of his design, and extensively annotated his example in the text of the change draft. Please follow the example closely to make sure you know what Jim is proposing.

 

Thanks,

Larry