Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue template to follow every time
Example using this template to propose type indexing in BIDS-prov
Type-indexing on agents/activities/entities in BIDS-prov
Problem Statement
When defining new graphs in BIDS-prov we have no way to know the type of an object in advance.
If we want to find all entities in a given graph, we must iterate over the entire graph.
In addition, this layout currently makes reading of the graph harder, and spotting errors becomes tedious
Rationale
We propose to use a feature called type indexing, for all our graphs
This will allow to group nodes by type, and maybe to create a hierarchy in the future, accessing the most basic types at first and then descending in the graph for more specific types (eg. Agent vs Software Agent)
Minimal examples
Before
After
Checklist