OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sarif message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: Issue #362: We need "request" and "response" objects after all


I am also confused by the following:

 

âOtherwise (that is, if thisObject is not an element of theRun.requests, and theRun.requests does contain a cached object for thisObject), then index SHALL be present, and its value SHALL be the array index within theRun.requests of the cached object.â

 

I am confused about what is the difference between thisObject being an element of theRun.requests and theRun.requests containing a cached object for thisObject. Same question applies to other similar sections.

 

k

 

From: Larry Golding (Myriad Consulting Inc) [mailto:v-lgold@microsoft.com]
Sent: Thursday, April 11, 2019 9:28 AM
To: Yekaterina O'Neil <katrina@microfocus.com>; OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Cc: Michael Fanning <Michael.Fanning@microsoft.com>; Harleen Kaur Kohli <harleen.kohli@microsoft.com>
Subject: RE: Issue #362: We need "request" and "response" objects after all

 

Web analyzers keep insisting on using our format 😊

 

From: Yekaterina O'Neil <katrina@microfocus.com>
Sent: Thursday, April 11, 2019 9:15 AM
To: Larry Golding (Myriad Consulting Inc) <v-lgold@microsoft.com>; OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Cc: Michael Fanning <Michael.Fanning@microsoft.com>; Harleen Kaur Kohli <harleen.kohli@microsoft.com>
Subject: RE: Issue #362: We need "request" and "response" objects after all

 

I still feel like request/response information is outside of the scope of SARIF, but I guess if there is a pressing needâ

k

 

From: sarif@lists.oasis-open.org [mailto:sarif@lists.oasis-open.org] On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Tuesday, April 09, 2019 6:15 PM
To: Larry Golding (Myriad Consulting Inc) <v-lgold@microsoft.com>; OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Cc: Michael Fanning <Michael.Fanning@microsoft.com>; Harleen Kaur Kohli <harleen.kohli@microsoft.com>
Subject: [sarif] RE: Issue #362: We need "request" and "response" objects after all
Importance: High

 

I made these changes, produced a change draft,

 

https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-362-request-response.docx

 

merged it into the provisional draft,

 

https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ProvisionalDrafts/sarif-v2.0-csd02-provisional.docx

 

and closed the issue.

 

Please let us know ASAP if you have any questions or concerns with this issue. This is a substantive addition to the format, although as I said below, it is non-breaking, uses design patterns weâve used before, and addresses a pressing need.

 

We came very close to meeting our goal of having all changes merged one week before TC #35. Of the three remaining issues that involve any writing (#266, #323, and #358), two of them are quite small, and one of them (#266) Iâm inclined to dispense with entirely. I expect to finish #323 and #358 tomorrow.

 

Thanks,

Larry

 

 

From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Tuesday, April 9, 2019 2:15 PM
To: OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Cc: Michael Fanning <Michael.Fanning@microsoft.com>; Harleen Kaur Kohli <harleen.kohli@microsoft.com>
Subject: [sarif] Issue #362: We need "request" and "response" objects after all
Importance: High

 

While writing a converter for a web analysis tool, it became clear to me that using threadFlow.immutableState to hold web request headers was not sufficient to meet the needs of these tools. So I filed Issue #362, âDefined request and response objects.â

 

The issue explains the rationale in more detail, and presents a proposal. The proposal is non-breaking. It recapitulates the pattern weâve used previously for logical locations and addresses: using cached objects to reduce repetition of request and response objects, and making requests and responses externalizable to reduce file size.

 

I am going to produce a change draft and optimistically merge it into the provisional draft. I donât actually think this is a controversial proposal; I just wish I had understood earlier how important it was.

 

My original goal was to have everything merged by end of day Tuesday (today) to give everybody a full week to review the final version. At this point I will miss that goal, but only by about half a day. Despite the seeming size of this change, itâs quite similar to text Iâve written many times before, so I expect to be done no later than noon tomorrow. Iâll let you know as soon as the draft is available.

 

Thanks,

Larry

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]