|
|
In an application we're working on, we're finding the
PartyRelationship model not quite describing our data
accurately. As it is the partyIdTo|roleTypeIdTo /
partyIdFrom|roleTypeIdFrom only really allows for a
"monogomous" relationship and very limiting and
repetitive to describe the different roles that
someone acts in for the same relationship.
We were thinking this is solved by following the
pattern used by most of the other entityRole
implementations. ie
<entity entity-name="Relationship">
...
</entity>
<entity entity-name="RelationshipRole">
..
</entity>
Any feedback?
|
Locked
