adr for conceptual view

[JimFuller-RedHat]

going to need help fleshing out the rest api ...

[chirino]

I like it. We should consider if there are better terms to use than ancestor and descendant as these could get associated with the AncestorOf relationship. Maybe:

• relationship - reverse-relationship
• forward - reverse
• normal and inverse

If the ancestor and descendant fields found in the response are optional then the same return type can be used for all these API endpoints. If that's the case then I think we could consolidate to a single api/v2/analysis/relationships endpoint if it accepts arg filters like:

• ancestors bool
• descendants bool
• depth: int
• realtionshipType: string

[JimFuller-RedHat]

I like it. We should consider if there are better terms to use than ancestor and descendant as these could get associated with the AncestorOf relationship. Maybe:

* `relationship` - `reverse-relationship`

* `forward` - `reverse`

* `normal` and `inverse`

In the graph world this conversation comes up regularly ... I always settle on anc/desc as most people agree what it means.

If the ancestor and descendant fields found in the response are optional then the same return type can be used for all these API endpoints. If that's the case then I think we could consolidate to a single api/v2/analysis/relationships endpoint if it accepts arg filters like:

* ancestors bool

* descendants bool

* depth: int

* realtionshipType: string

I am all for simplifying and/or having less 'moving parts' ... even better when parameterised ... in this case I suggested separation because it was easier to puzzle out ... lets discuss this in meeting.