- Not an open issue. The edge defines a source and target, so directionality is represented. For bidirectional links, you need to define two edges.
- Labels describe the elements of a fully formed graph, the nodes and its edges. In a graph traversal, we provider user-facing messages that, reviewed in sequence, take a user through
a specific problem.
- Why have we named state ‘finalState’ in the traversal? Is that what we landed on for other constructs as well?
- A node should have a nestedGraphId or subGraphId. This points to another graph the collected nodes of which comprise the current node.
- We can’t currently allow a graphTraversal to step into a subgraph if it cares to, because we don’t provide a graphId on the edgeTraversal class. We could provide an optional subgraphId
property on an edgeTraversal to support this case (if absent, the graph id would be assumed to be the one defined at the graphTraversal level.
From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org>
On Behalf Of Larry Golding (Comcast)
Sent: Friday, March 30, 2018 11:18 AM
To: sarif@lists.oasis-open.org
Subject: RE: [sarif] Graphs design changes
Another open issue is:
- Do we represent the directionality of an edge?
I pushed a changed to
Documents/ChangeDrafts/Active/graphs.txt that incorporates the changes we discussed at the TC meeting. I understand there’s still some discussion, for example:
- Is there a distinction between a “label” and a “user facing message” on nodes and edges?
- Exactly how do we incorporate sub-graphs?
- Do we want to define additional properties on edgeTraversal?
But I’m going to start writing with what we have.
The easiest way to see the changes I just incorporated is to look at the
commit.
Thanks,
Larry
|