You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
referenced_by vs references (e.g., graph directionality)
The text was updated successfully, but these errors were encountered:
MarkDavidson
changed the title
As a User, I want to travers the STIX graph in an efficient manner, so I don't waste resources
As a User, I want to traverse the STIX graph in an efficient manner, so I don't waste resources
Oct 18, 2017
MarkDavidson
changed the title
As a User, I want to traverse the STIX graph in an efficient manner, so I don't waste resources
As a User, I want to traverse the STIX graph over TAXII in an efficient manner, so I don't waste resources
Oct 18, 2017
So, I looked at implementing this in our database abstraction layer. The issue I ran into for directed paths is combining connectivity with Collection read permissions
It's possible that a connected STIX Object may be in another Collection where the client does not have read permissions. So, walking digraph paths becomes a non-trivial operation. It becomes more complicated with can_read which determines if the client can read the collection, meaning that can_read can vary per client for a given Collection. So, if I start walking the objects, I have to determine if connected objects:
are in the the collection the client requested
are in another collection where the client has read access
It got a little weird. This could just be our implementation issue.
Key components:
The text was updated successfully, but these errors were encountered: