-
Notifications
You must be signed in to change notification settings - Fork 9
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
STIX Patterning language needs intra-list matching capability #66
Comments
This is definitely something that we need to fix, as users are encountering this issue. Here's the draft text we've proposed: "The literal 's' indicates that, when evaluating two or more AND'd Comparison Expressions that contain a list-based object path, that the Boolean expression MUST evaluate to true if there is an s that allows the AND'd Comparison Expressions to be true, otherwise false" |
I'm okay with this change, even though it does make code to evaluate patterns more complex (despite the relatively minor change to the grammar). I don't think this should be considered a "bug" that needs to be "fixed", though. It's additional functionality, and was a known limitation at the time the current list-item-matching construct was added. |
I think this was something we overlooked when adding the existing list-item-matching construct. So maybe not quite a bug, but it's something that should have been in there ;) |
@samcornwell points out this related CAR proposal |
We could possibly solve the multi vars by restricting it to parenthesized expressions: Sam brought up the case of wanting to do an or for one part of it, such as: This may be valid per the existing text, as ([s] = 'a' or [s] = 'b') is a comparison expression, and so therefor should work. |
We talked about this 2019-06-05 and Jason says this is super important and that he will propose some text in the document. |
No description provided.
The text was updated successfully, but these errors were encountered: