Traversing access descriptions

[Yucukof]

Hi panellists,

On the occasion of my M.Sc. thesis, I am working on a prototype for your proposal (which I hope to share with you soon).

Doing so, I am trying to traverse the access needs graph dynamically to generate the request UI for a given application.

In the picture below, the entry point is the Application entity in green.

ℹ️ all predicates come from the specification available here

As you can see, there are two nodes which cannot be reached using the available predicates.

• AccessNeedGroupDescription
• AccessNeedDescription

In order to get, say, the English description of an access need, I have no choice but to know where they are, read them in bulk then filter down to what I needed.

💡 To simplify navigation, I would suggest using the following predicates.

→This makes a much nicer directed tree easier to traverse, from my point of view.

What do you think?