(Ditching the design of adding explicit properties for capabilities and requirements)
it may be more elegant to derive capabilities and requirements from relationships.
Option-1: This may be done by mining the relation types. e.g. x->has -> y, denotes most probably a capability. x -> needs -> y, denotes most probably a requirement.
Other options are TBD.
The persistent storage of such derivations/inferences may be done using properties to relationships.
NOTE- such inferred caps and reqs may need to be human reviewed, but that's a different story :)
(Ditching the design of adding explicit properties for capabilities and requirements) it may be more elegant to derive capabilities and requirements from relationships. Option-1: This may be done by mining the relation types. e.g. x->has -> y, denotes most probably a capability. x -> needs -> y, denotes most probably a requirement. Other options are TBD. The persistent storage of such derivations/inferences may be done using properties to relationships.
NOTE- such inferred caps and reqs may need to be human reviewed, but that's a different story :)