[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sarif] Updated Schedule
I see. And do they have to have used the very final version? Cuz they didn't. That was months ago.
-----Original Message-----
From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of David Keaton
Sent: Monday, July 15, 2019 2:08 PM
To: sarif@lists.oasis-open.org
Subject: Re: [sarif] Updated Schedule
Larry,
Outside SoUs are welcome. They must be submitted to sarif-comment@list.oasis-open.org.
David
On 7/15/19 2:05 PM, Larry Golding (Myriad Consulting Inc) wrote:
> That's a great point. Do the SOU's have to come from TC members? Maybe SATE can give us one.
>
> -----Original Message-----
> From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On
> Behalf Of David Keaton
> Sent: Monday, July 15, 2019 2:03 PM
> To: sarif@lists.oasis-open.org
> Subject: Re: [sarif] Updated Schedule
>
> Larry,
>
> Well, that's debatable. They didn't really use the resulting log file; they only submitted it to SATE. It would be easier to make the case that Microsoft and SATE conform, though I see what you're saying.
>
> It isn't a big deal. We only need three Statements of Use, and we know of at least two organizations so far that will submit them so far.
>
> In the end, the TC will need to vote on whether each Statement of Use is sufficient. It would be best to get as many SoUs as we can where the answer is clear cut.
>
> David
>
> On 7/15/19 1:51 PM, Larry Golding (Myriad Consulting Inc) wrote:
>> But they still _used_ the resulting log file, so that counts as a use of the "log file" conformance clause, right?
>>
>> -----Original Message-----
>> From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On
>> Behalf Of Yekaterina O'Neil
>> Sent: Monday, July 15, 2019 1:50 PM
>> To: David Keaton <dmk@dmk.com>; sarif@lists.oasis-open.org
>> Subject: RE: [sarif] Updated Schedule
>>
>> Got it, thank you :)
>> k
>>
>> -----Original Message-----
>> From: sarif@lists.oasis-open.org [mailto:sarif@lists.oasis-open.org]
>> On Behalf Of David Keaton
>> Sent: Monday, July 15, 2019 1:49 PM
>> To: sarif@lists.oasis-open.org
>> Subject: Re: [sarif] Updated Schedule
>>
>> Oh, then Microsoft conforms. :-)
>>
>> You would only submit a Statement of Use if your own software conforms to one or more of the conformance clauses.
>>
>> David
>>
>> On 7/15/19 1:47 PM, Yekaterina O'Neil wrote:
>>> We use Microsoft converter though
>>> k
>>>
>>> -----Original Message-----
>>> From: sarif@lists.oasis-open.org [mailto:sarif@lists.oasis-open.org]
>>> On Behalf Of David Keaton
>>> Sent: Monday, July 15, 2019 1:45 PM
>>> To: sarif@lists.oasis-open.org
>>> Subject: Re: [sarif] Updated Schedule
>>>
>>> Katrina,
>>>
>>> Yes, if you produce conforming SARIF files, that means that you at least conform to the SARIF log file and SARIF producer conformance clauses.
>>>
>>> David
>>>
>>> On 7/15/19 1:36 PM, Yekaterina O'Neil wrote:
>>>> David,
>>>>
>>>> Is submission of results in SARIF format to SATE treated as a use?
>>>> k
>>>>
>>>> -----Original Message-----
>>>> From: sarif@lists.oasis-open.org
>>>> [mailto:sarif@lists.oasis-open.org]
>>>> On Behalf Of David Keaton
>>>> Sent: Monday, July 15, 2019 12:50 PM
>>>> To: sarif@lists.oasis-open.org
>>>> Subject: Re: [sarif] Updated Schedule
>>>>
>>>> Katrina,
>>>>
>>>> Sorry, I just realized that I didn't answer your second question.
>>>>
>>>> The Statements of Use are only for organizations that currently use the standard. We need to have three of those total. An organization that does not yet use the standard will not submit a Statement of Use.
>>>>
>>>> David
>>>>
>>>> On 7/15/19 12:48 PM, David Keaton wrote:
>>>>> Katrina,
>>>>>
>>>>>  Only three Statements of Use are needed. One of them
>>>>> has to be from an OASIS organizational member. Microsoft will
>>>>> submit one, and they are an organizational member, so we are covered there.
>>>>>
>>>>> ÂÂÂÂ The Statements of Use will be available for inspection
>>>>> by the TC, so I can share the attached as an example. It turns
>>>>> out that we will need to reference the Committee Specification
>>>>> instead of the CSD, but Jim did a great job putting everything that is required into it.
>>>>>
>>>>> ÂÂÂÂ For complete detail on what needs to be in a Statement
>>>>> of Use, the following definition explains it well.
>>>>>
>>>>> https://ww
>>>>> w.oasis-open.org%2Fpolicies-guidelines%2Foasis-defined-terms-2&
>>>>> ;
>>>>> d
>>>>> ata=02%7C01%7Cv-lgold%40microsoft.com%7C96cf6e2f66a74aad90e308d709
>>>>> 6
>>>>> 6
>>>>> 2d85%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369882067591323
>>>>> 6
>>>>> 5
>>>>> &sdata=DOTAa%2Bw1eUlwDcPVs2uCImQjDsNfx1tdXLuDWOVMvmI%3D&re
>>>>> s
>>>>> e
>>>>> rved=0
>>>>> 0
>>>>> 1
>>>>> 8-05-22#dStatementUse
>>>>>
>>>>>
>>>>> ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ David
>>>>>
>>>>> On 7/15/19 11:29 AM, Yekaterina O'Neil wrote:
>>>>>> Thank you, David!
>>>>>>
>>>>>> I do have a couple of questions about statement of use (I might
>>>>>> have missed earlier discussions of these):
>>>>>>
>>>>>> ÂÂÂÂ- does everyone on the TC need to submit statement of use?
>>>>>> ÂÂÂÂ- what happens if we don't currently use the standard,
>>>>>> but are planning in the future?
>>>>>> ÂÂÂÂ- what is the format of the document? Is there a template?
>>>>>>
>>>>>> Thank you!
>>>>>> k
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: sarif@lists.oasis-open.org
>>>>>> [mailto:sarif@lists.oasis-open.org]
>>>>>> On Behalf Of David Keaton
>>>>>> Sent: Sunday, July 14, 2019 7:36 PM
>>>>>> To: sarif@lists.oasis-open.org
>>>>>> Subject: [sarif] Updated Schedule
>>>>>>
>>>>>> ÂÂÂÂÂÂ At last week's meeting, I took an action item to
>>>>>> update the dates in our delivery schedule. I have posted the
>>>>>> following document, which contains the original explanations of
>>>>>> each stage with an updated schedule at the end.
>>>>>>
>>>>>> https://w
>>>>>> ww.oasis-open.org%2Fcommittees%2Fdocument.php%3Fdocument_id%3D656
>>>>>> 2
>>>>>> &
>>>>>> amp;data=02%7C01%7Cv-lgold%40microsoft.com%7C96cf6e2f66a74aad90e3
>>>>>> 0
>>>>>> 8
>>>>>> d709662d85%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636988206
>>>>>> 7
>>>>>> 5
>>>>>> 9132365&sdata=T4buVZlcBFU5Hd4QTUNg%2B5zoDa%2F8tgp3RGE5MtRHJL4
>>>>>> %
>>>>>> 3
>>>>>> D&reserved=0
>>>>>> 2
>>>>>> &
>>>>>> wg_abbrev=sarif
>>>>>>
>>>>>>
>>>>>>  That document is very general. Below I list the more
>>>>>> specific events and dates I used to determine the updated schedule.
>>>>>> The actual actions might happen a little sooner or a little later
>>>>>> than my assumed schedule, depending on how things go.
>>>>>>
>>>>>> ÂÂÂÂÂÂ Please note that it is a good idea to start preparing
>>>>>> the Statements of Use now. You can update them with the proper
>>>>>> document reference and dates when the Special Majority Vote for
>>>>>> Committee Specification closes.
>>>>>>
>>>>>> ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ David
>>>>>>
>>>>>> ---
>>>>>>
>>>>>> Committee Specification Special Majority Vote
>>>>>> ÂÂÂÂ2019-07-26 ~ 2019-08-02
>>>>>>
>>>>>> Statements of Use:Â Get ready now, submit when SMV closes
>>>>>> ÂÂÂÂ2019-08-09
>>>>>>
>>>>>> Ballot to request Candidate OASIS Standard SMV
>>>>>> ÂÂÂÂ2019-08-09 ~ 2019-08-16
>>>>>>
>>>>>> Candidate OASIS Standard SMV
>>>>>> ÂÂÂÂ2019-08-30 ~ 2019-09-06
>>>>>>
>>>>>> Candidate OASIS Standard 60-day public review
>>>>>> ÂÂÂÂ2019-09-06 ~ 2019-11-05
>>>>>>
>>>>>> Ballot to approve non-material changes due to review comments and
>>>>>> request SMV to proceed with Call for Consent
>>>>>> ÂÂÂÂ2019-11-12 ~ 2019-11-19
>>>>>>
>>>>>> SMV to begin Call for Consent for OASIS Standard
>>>>>> ÂÂÂÂ2019-11-20 ~ 2019-11-27
>>>>>>
>>>>>> Call for Consent for OASIS Standard
>>>>>> ÂÂÂÂ2019-12-02 ~ 2019-12-16
>>>>>>
>>>>>> OASIS Standard
>>>>>> ÂÂÂÂ2019-12-16
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> -
>>>>>> - 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&data=02%7C01%7Cv-lgold%40microsoft.com%7Cb9e4010a6ac14c01d62008d709687b63%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636988216661846918&sdata=bcOldxhGo14fOmQEocANeua8gRR0ZtSH1hI1zFfHYe0%3D&reserved=0.
>>>>>> p
>>>>>> h
>>>>>> p
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - 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://ww
>>>>> w.oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.
>>>>> p
>>>>> &data=02%7C01%7Cv-lgold%40microsoft.com%7C96cf6e2f66a74aad90e3
>>>>> 0
>>>>> 8
>>>>> d709662d85%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369882067
>>>>> 5
>>>>> 9
>>>>> 132365&sdata=VcJ7D0ObqkxxCDXAD6Ll0kZoXh%2Bwagn7y8KFj4UX4cY%3D&
>>>>> a
>>>>> m
>>>>> p;reserved=0
>>>>> h
>>>>> p
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - 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://www
>>>> .oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.p
>>>> h
>>>> &
>>>> amp;data=02%7C01%7Cv-lgold%40microsoft.com%7C96cf6e2f66a74aad90e308
>>>> d
>>>> 7
>>>> 09662d85%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369882067591
>>>> 3
>>>> 2
>>>> 365&sdata=pvKIH4FDknU6dJNECg3JXOfuxFBVUwQ%2FcJ2H8wBOCnI%3D&
>>>> r
>>>> e
>>>> served=0
>>>> p
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - 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://www.
>>> oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.php
>>> &
>>> a
>>> mp;data=02%7C01%7Cv-lgold%40microsoft.com%7C96cf6e2f66a74aad90e308d7
>>> 0
>>> 9
>>> 662d85%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369882067591323
>>> 6
>>> 5
>>> &sdata=XRK4OKyVXc%2BbN6z7%2BXIKTYtKO%2BG1cnEnAoT76MQYexs%3D&
>>> r
>>> e
>>> served=0
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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://www.
>> oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.php&
>> a
>> mp;data=02%7C01%7Cv-lgold%40microsoft.com%7C9200e5759cbf4749bf7c08d70
>> 9
>> 67e3e9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63698821411823988
>> 3
>> &sdata=ogeWORbyUplnmz3edFcZmBqgm7ioRWcOP2ncHruQNF4%3D&reserve
>> d
>> =0
>>
>
>
> ---------------------------------------------------------------------
> 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&a
> mp;data=02%7C01%7Cv-lgold%40microsoft.com%7Cb9e4010a6ac14c01d62008d709
> 687b63%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636988216661846918
> &sdata=PfN5KFb8Oq5gCw213%2FNAkjLCV8jRRYsQ0NL3r5ahC24%3D&reserv
> ed=0
>
---------------------------------------------------------------------
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&data=02%7C01%7Cv-lgold%40microsoft.com%7Cb9e4010a6ac14c01d62008d709687b63%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636988216661846918&sdata=PfN5KFb8Oq5gCw213%2FNAkjLCV8jRRYsQ0NL3r5ahC24%3D&reserved=0
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]