sarif — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
#361: Unconstrained, multiformat state objects
Michael requested a change to the definition of “state” objects (such as threadFlow.initialState and
edgeTraversalLocation.finalState ):
Remove the restriction that the property names and values conform to the “_expression_” syntax of a programming language. State items are not necessarily expressions. Consider the examples in the spec where the state includes Web request headers, so the state properties might include, for example, "accept-language": "en-US" .
Allow property values to include formatting information. This means changing the property values from string to multiformatMessageString objects.
I made these changes, produced a change draft,
https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ChangeDrafts/Accepted/sarif-v2.0-issue-361-multiformat-state-values.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.
Thanks,
Larry
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]