RE: [sarif] Statements of Use

["Larry Golding (Myriad Consulting Inc)" <v-lgold@microsoft.com>]

Now that's very interesting. The Conformance Clauses are very coarse-grained:

5	Conformance						168
5.1	Conformance targets					168
5.2	Conformance Clause 1: SARIF log file			168
5.3	Conformance Clause 2: SARIF producer			168
5.4	Conformance Clause 3: Direct producer			168
5.5	Conformance Clause 4: Deterministic producer		169
5.6	Conformance Clause 5: Converter			169
5.7	Conformance Clause 6: SARIF post-processor		169
5.8	Conformance Clause 7: SARIF consumer			169
5.9	Conformance Clause 8: Viewer				169
5.10	Conformance Clause 9: Result management system	169
5.11	Conformance Clause 10: Engineering system		169

... so you just have to say "I implemented a SARIF producer" (5.3) and it was a "direct producer" (5.4) and it was "deterministic" (5.5) and it produced "log files" (5.2). At least three companies have done that.

That's the good news. More good news: MS has implemented a SARIF-based "result management system" (5.9) and "engineering system" (5.10), with converters (5.6), post-processors (5.7) and viewers (5.9).

The bad news: Who aside from MS has done those other things? Do we need three users of _every conformance clause_?

Larry

-----Original Message-----
From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of David Keaton
Sent: Wednesday, April 3, 2019 11:21 AM
To: sarif@lists.oasis-open.org
Subject: [sarif] Statements of Use

      Here is the information I promised during the meeting.

      The Statements of Use are for a couple of stages farther along in the process than we are now:

1.  We are about to approve a Committee Specification Draft and start a public comment period on it.

2.  After the public comment period concludes, if we make no substantive changes, we can approve the draft as a Committee Specification.

3.  The next step is to submit that Committee Specification as a Candidate OASIS Standard.  To do so, we will need three Statements of Use, which must be for the Committee Specification being considered for Candidate OASIS Standard.  It takes a careful reading, but the following text does indicate that the Statements of Use must reference "the Committee Specification" being promoted.

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.oasis-open.org%2Fpolicies-guidelines%2Ftc-process-2017-05-26%23OSsubmission&amp;data=02%7C01%7Cv-lgold%40microsoft.com%7C17241965726d4d9b1a4d08d6b861244c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636899124760597736&amp;sdata=83jaM0tPY6UPmiyXKi8ssiv6mRFZtV24ixVMLEBb%2B0U%3D&amp;reserved=0

3a.  The Statements of Use must indicate whether all of the current Committee Specification is in use, or parts of it.  If only parts, the specific conformance clauses being used must be indicated.

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.oasis-open.org%2Fpolicies-guidelines%2Foasis-defined-terms-2018-05-22%23dStatementUse&amp;data=02%7C01%7Cv-lgold%40microsoft.com%7C17241965726d4d9b1a4d08d6b861244c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636899124760597736&amp;sdata=iYML0%2Bv55KWqSKA9s5CUrt3cLGskWxhDTJdGUbR8OGY%3D&amp;reserved=0

      However, note that someone who conforms to a previous CSD could rightfully claim that they conform to the current Committee Specification for those conformance clauses that have not changed since the earlier CSD.

      The Statements of Use may be from members or nonmembers, but at least one must be from an OASIS Organizational member.

					David

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.php&amp;data=02%7C01%7Cv-lgold%40microsoft.com%7C17241965726d4d9b1a4d08d6b861244c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636899124760597736&amp;sdata=IxmB8rECHdsoLGCm4v%2Bdhc4d7PU1Sta7y2KXdSjvkZo%3D&amp;reserved=0