Establishing relation-based needs for nodes

[i-interprete-on-the-fly]

Currently it is possible to define requirements as well as arbitrary node types and relations between those. Each of those node types may need several other elements, for example I could want to have a requirement having a relation to a software unit, an architecture element or a test case specification. For this scenario it would be useful to be able to specify a set of relations that a specific node has to have established and be able to view missing relations for the node. Depending on the current view there could be different ways of implementing a missing link indication.

What do you think about that?

[stanislaw]

I am missing enough free time cycles to consider this properly, given other higher-priority tasks. Are you using StrictDoc actively enough to come up with a proposal here?

Some quick thoughts:

• I could think of setting up a nodes relation at the document level (a dedicated grammar field) or node-level (a dedicated node field).
• I could think of telling a node that it has to have a specific relation. More than that, has this relation be to a given document identified by document UID/MID or to a node of a given type?