[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Change draft for #306: directoryLocation
I pushed a change draft for
Issue #306: "originalUriBaseId object's values are directory locations not file locations" Documents/ChangeDrafts/Active/sarif-v2.0-issue-306-directory-locations.docx We do not plan to move its adoption at TC #30, since you have not had time to review it. We will present this in more detail at the F2F, but feel free to ask questions in email before then. The issue is that the “fileLocation” objects that appear in
run.originalUriBaseIds actually specify the locations of directories, not files. No other “file locations” in SARIF have that characteristic. Michael and I examined various design options, including simply redefining
“file” in the spec to encompass any URI-addressable resource, but we decided that the cleanest option was to define a new object type “directoryLocation” containing
uri and
uriBaseId properties, and to state the
run.originalUriBaseIds contains directoryLocations, not
fileLocations. Thanks, Larry |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]