From 9d460dd1fc47001c60aaddbf54c054a96ce340f3 Mon Sep 17 00:00:00 2001 From: Larry Golding Date: Thu, 14 Feb 2019 15:46:59 -0800 Subject: [PATCH] #179: Don't replace conversion.tool with conversion.driver MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit conversion.tool is the conversion scenario analog of run.tool. Both the direct production and the conversion scenarios are accomplished by a tool that consists of a driver, and possibly a set of auxiliary files including plugins and configuration files. In the conversion scenario, configuration files are more likely than plugins, but that’s neither here nor there. --- Documents/Schema changes between SARIF v1 and v2.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/Documents/Schema changes between SARIF v1 and v2.md b/Documents/Schema changes between SARIF v1 and v2.md index 0189e9bc..d779a1bc 100644 --- a/Documents/Schema changes between SARIF v1 and v2.md +++ b/Documents/Schema changes between SARIF v1 and v2.md @@ -1266,10 +1266,6 @@ _and_ [Issue #311](https://github.com/oasis-tcs/sarif-spec/issues/311): "Provide - Add a property `notificationIndex` of type `integer`, `default: -1`. optional. - Add a property `notificationExtensionIndex` of type `integer`, `default: -1`. optional. - In the `conversion` object: - - - Rename the `tool` property to `driver`, and change its type from `tool` to `toolComponent`. - - [Issue #312](https://github.com/oasis-tcs/sarif-spec/issues/312): "Consider adding 'updated' baselineState" In the `result` object: