-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Associate descriptor metadata with thread flow locations #381
Labels
2.1.0-CSD.1
Will be fixed in SARIF v2.1.0 CSD.1.
design-approved
The TC approved the design and I can write the change draft
enhancement
impact-non-breaking-change
merged
Changes merged into provisional draft.
resolved-fixed
Comments
@lgolding to author example using MicroFocus inputs. Follow up with Chris Meyer and Scott Louvau to get substantive examples. From Larry: I got the sample from Yekaterina. Our design will work. I'll author the example as I write the spec text. |
ghost
pushed a commit
that referenced
this issue
Apr 25, 2019
For completeness, here's the sample:
|
In the example above and in the draft for 381, should the taxa id value in the threadFlow be "HD0001" not "TD0001"? |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2.1.0-CSD.1
Will be fixed in SARIF v2.1.0 CSD.1.
design-approved
The TC approved the design and I can write the change draft
enhancement
impact-non-breaking-change
merged
Changes merged into provisional draft.
resolved-fixed
TC approves:
Add
threadFlowLocation.taxa
, an array ofreportingDescriptorReference
s, the default location of which (in case where only the RDR index is provided) is the relevant tool component rules data.The text was updated successfully, but these errors were encountered: