RE: #387: anyOf externalPropertyFileReference location or guid is requir

Indeed it should 😊 Fixed in the upcoming âaddressâ draft.

It makes me really happy and confident to see this close attention to detail.

Larry

From: Yekaterina O'Neil <katrina@microfocus.com>
Sent: Monday, April 29, 2019 9:47 AM
To: Larry Golding (Myriad Consulting Inc) <v-lgold@microsoft.com>; OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Subject: RE: #387: anyOf externalPropertyFileReference location or guid is required

Should it be â(possibly located inline; see Â3.13.5).â ?

From: sarif@lists.oasis-open.org [mailto:sarif@lists.oasis-open.org] On Behalf Of Larry Golding (Myriad Consulting Inc)
Sent: Thursday, April 25, 2019 4:16 PM
To: OASIS SARIF TC Discussion List <sarif@lists.oasis-open.org>
Subject: [sarif] #387: anyOf externalPropertyFileReference location or guid is required
Importance: High

Caution: This email originated from outside the organization. Do not click links or open attachments unless you have verified this email is legitimate.

I created and merged a change draft for Issue #387, âanyOf externalPropertyFileReference location or guid is requiredâ:

https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-387-anyOf-guid-location.docx

This was simply a bug of omission. You have to have on or the other of these properties or you canât find the externalized properties.

Please take a look. The entire change is pasted below.

Next is Issue #397: âAdd more address kindsâ

Thanks,

Larry

3.16.2 Constraints [on the externalPropertyFileReference object]

At least one of the location property (Â3.16.3) or the guid property (Â3.16.4) SHALL be present. If both are present, they SHALL identify the same set of externalized properties (possible located inline; see Â3.13.5).

NOTE: This constraint ensures that it is possible to locate the externalized properties.

sarif message