Best approach for Identity/Contact Dbus Interface

[bublath]

I'm struggling with the best approach to create a new Dbus Properties Interface for Contacts/Indentities with the target to enable validating trust via Dbus.
The hierarchy between Contact, Indentity, Profile, Recipient (and many others inbetween) is a little confusing to me.

Originally I only wanted to implement one Interface that combines Contacts and Identities, so you have everything that originates from the phone number in one place.
I started filling the interface from m.getIdentities() using getLegacyIdentifier / getIdentifier
However that only gives me a recipientAddresss, while I would need one "level up" to Recipient to then again access the fields on Contact and Profile.
@AsamK any hint how I could achieve this?
While I know that Contacts and Identities is not exactly the same, I thought it would make sense to combine them here. Or would I really need a seprerate Contact Property?

Probably I would then stick to just to the Identity for now, as this is sufficient for set trust. The user would use the number (legacyIdentifier) which should work in the relevant cases.