Open BartvanBekkum opened 5 years ago
@BartvanBekkum , please, is there a SEMPER GitHub or similar collaborative tool to which we can subscribe, contribute and get feed-back from?
Thanks!
According to Merriam-Webster dictionary:
So, I see mandatee as a synonym of representative if the legal right is the existence of a mandate. If the legal right is other than a mandate, then the representative cannot be called "mandatee".
Conclusion: A mandatee is always a representative, but a representative might not be a mandatee
I can think of several types of representatives according to how the representation is granted, and only some of them are related to mandates:
1 & 2 can be named as "mandates" because the authorization is given to the representative by the represented one at some point of time and to a certain extent. However some of these mandates are composed by structure data and others are not (notarial deeds are documents written in plain text without a given structure).
4 are proven by the existence of the agreement and the registration of a professional (the representative here) in the corresponding association.
3 are proven by the regulation that states such rigths and the corresponding register.
This contribution is really very interesting. I think it is related to something that we're right now modelling and that we refer to as the "PowerSource" (source of the power). We are proposing to have a new class nameto use it with a twofold objective: (1) to link the power of a mandator that is a mandatee (delegation) to the mandate where it was originally empowered, and (2) to indicate whether the power comes directly from an existing legislation.
If the class PowerSource carried a sourceType code then we could cover also the other options you indicate in your points 3 and 4. Points 1 and 2 would already be covered by our latest proposal.
Allow us to finish implementing the change today in the Conceptual Data Model and we'll post it tomorrow morning.