Hi, Larry,
I am not sure resurrecting run.startTimeUtc makes sense, please see my most recent reply.
I led us to this situation because I forgot that we removed this property. All things considered, introducing it again seems like it brings more complexity without much incremental value.
Michael
From: <>
On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Sunday, December 9, 2018 1:56 PM
To: OASIS SARIF TC Discussion List <>
Subject: [sarif] Change draft for #287: default for lastDetectionTimeUtc
I pushed a change draft for
Issue #287: “Define default for resultProvenance.lastDetectionTimeUtc”.
Documents/ChangeDrafts/Active/sarif-v2.0-issue-287-lastDetectionTimeUtc-default.docx
In the issue’s discussion thread, Michael and I decided that it made sense to bring back the property
run.startTimeUtc. Please read the thread to see how that idea is related to this issue. So we’ve restored that property, and for symmetry, also restored
run.endTimeUtc.
We’ll move its adoption at TC #29 on Wednesday December 12th.
Thanks,
Larry
