A payer always has a first and a last name among other attributes.
Is this true?
For example: If you sell something via Amazon, then Amazon collects the “Payment”
from the “Buyer”, deducts a percentage and then pays the rest to you.
In this scenario, the “Buyer” plays
the role of “Payer” because the Buyer pays money to Amazon. Then Amazon becomes
a Payer” when the Amazon company pays you your money from the sale.
But Amazon does not have a “First Name” nor does it have a “Last Name”.
(This is why I introduced the
concept of “Legal Person” in my earlier model)
Norma supports a data type of "Other: Object ID," which I
think would be equivalent to allowing me to refer to a set of entities in my
model that correspond to a custom (user-defined) data type that I defined.
In Norma, the data type for an “ObjectID”
is “bigint” so this points to an OID such as GUID. As I understand it, an OID
may point to a node in a hierarchy and that node may have Properties.
And - I just had a quick chat with Matt about your requirements.
He is a lot busy right now but this is what he said:
“I have posted before on ORM Foundation about how to hijack a data type. I
think I did something like put an obviously out of range precision on a double
then tweak the DIL datatype generator.”
I had a quick search of the Forum but I could not find Matt’s post. Maybe you
can find it?
Anyway, the implication is that it is possible to do what you want by writing
code in NORMA.
Are you interested in doing that?