Remove details /= Void invariant from PARTY

Description

Rong Chen @ acode.se:
There is no reason why PARTY should have the invariant details /= Void, since it
already has a number of hard-modelled attributes, which in many cases will carry
all the necessary data.

To be more precise...
The PARTY class has the following attributes (some by inheritance):

from Class LOCATABLE:
archetype_details: ARCHETYPED
archetype_node_id: STRING
feeder_audit: FEEDER_AUDIT
links: SET [LINK]
name: DV_TEXT
from Class PARTY:
contacts: SET [CONTACT]
details: ITEM_STRUCTURE *******
identities: SET [PARTY_IDENTITY]
relationships: LINKED_SET [PARTY_RELATIONSHIP]
reverse_relationships: SET [OBJECT_REF]
uid: OBJECT_ID

THe starred one is the one we are talking about. In PARTY, there is an invariant
which says that
details /= Void
meaning that there must be details. But as you can see, there are already structured
attributes for name, identities, contacts, and relationships, so it is quite
possible to create PARTY instances which make sense but have no further details
to record.

Assignee

JeffJ

Reporter

Rong Chen

Raised By

None

Priority

Minor
Configure