The CRM currently describes family relations by Birth events and assumed fatherhood. This is a maximal elementary analysis for genetically determined family relations except for loan-mothers and cloning. There are problems in describing family relations where the genetic intermediates (common ancestors) are not known. There are also legal and social relations that have a status of family relations to be described.
Some of these issues are : (1) E67 Birth has properties for the Mother (P96), the assumed father (P97) and the child (P98). This is has some problems with it. For example, it doesn't allow for adoption. (2) similar to the Acquisition event is required to deal with the legal aspects of adoption:
- A legal relationship is established by an activity.
- A genetic relationship is established by birth (except for loan-mothers)
- A social relationship is established by bringing up someone.
Martin Doerr suggested creating an adoption event presented in the following figure. He warned against modeling events for which we have no evidence in databases.
The importance of parenthood as a legal construct was discussed. Different cultures approach this issue differently. It is expressed the importance of the Adoption event in establishing the relationship. This is different to characterizing a longer-lasting social activity that establishes a de-facto bond.
There was a question of how the de-assignment of an adoption should be modeled (in order to preserve the symmetry of the model). A comment was that adoption should be modeled in the same way as Transfer of Custody/Acquisition.
There was a consideration about other relationships with open numbers of intermediates e.g. uncles, aunts, cousins etc.
Proposal: There should be a CRM extension dealing with family relationships. It is suggested that this should be done by someone with ethnological knowledge to ensure that we do not impose a Western construct to family relationships.
10th CIDOC CRM SIG Meeting, Nuremberg, 9-10th December 2004
How to model authority documents (FRAD case) which include family relations, like adoption, or being member of a family or stopping being member of a family type group. Marriage can be regarded as a family type group.
9th FRBR/CRM Harmonization meeting March 14th, 2007, Paris
There should be a CRM extension about being a member and ceasing to be a member of a group.
E85 Joining - IsA E7 Activity
E85. P143 joined (was joined by) E39 Actor
E85. P144 joined with (gained member by) E74 Group
E86 Leaving IsA E7 Activity
E86. P145 separated (left by) E39 Actor
E86. P146 separated from (lost member by) E74 Group
Scope notes,
And change scope note for Group:
Refer to families, and holder of a title/post/office
The additions follow:
E85 Joining | |
Subclass of: | E7 Activity |
Scope note: |
This class comprises the activities that result in an instance of E49 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. |
Examples: |
|
Properties: |
P143 joined (was joined by): E39 Actor |
E80 Leaving | |
Subclass of: | E7 Activity |
Scope note: |
This class comprises the activities that result in an instance of E49 Actor to be separated from an instance of E74 Group. This class does not imply initiative by either party. |
Examples: |
|
Properties: |
P145 separated (left by) E39 Actor |
P143 joined (was joined by) | |
Domain: | E85 Joining |
Range: | E39 Actor |
Subproperty of: | E5 Event: P11 had participant (participated in): E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: |
This property identifies the instance of E39 Actor that becomes member of a E74 Group in an E85 Joining. |
Examples: |
|
P144 joined with (gained member by) | |
Domain: | E85 Joining |
Range: |
E74 Group |
Subproperty of: | E5 Event: P11 had participant (participated in): E39 Actor |
Quantification: |
many to many, necessary (1,n:0,n) |
Scope note: |
This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining. |
Examples: |
|
P145 separated (left by) | |
Domain: | E86 Leaving |
Range: | E39 Actor |
Subproperty of: | E5 Event: P11 had participant (participated in): E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: | This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving. |
Examples: |
|
P146 separated from (lost member by) | |
Domain: | E86 Leaving |
Range: | E74 Group |
Subproperty of: | E5 Event: P11 had participant (participated in): E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: |
This property identifies the instance of E74 Group that an instance of E39 Actor leaves through an instance of E86 Leaving. |
Examples: |
|
Edinburgh 10/7/2007
The proposed classes and properties have been accepted while the examples need more elaboration. CEO will help
Nuremberg 4-7 December 2007
E85 Joining
Subclass of: | E7 Activity |
Scope note: |
This class comprises the activities that result in an instance of E49 Actor becoming a member of an instance of E74 Group. This class does not imply initiative by either party. Typical scenarios include becoming a member of a social organisation, becoming employee of a company, marriage, the adoption of a child by a family and the inauguration of somebody into an official position. |
Examples: |
|
Properties: | P143 joined (was joined by): E39 Actor P144 joined with (gained member by) E74 Group |
E86 Leaving
Subclass of: | E7 Activity |
Scope note: | This class comprises the activities that result in an instance of E39 Actor to be disassociated from an instance of E74 Group. This class does not imply initiative by either party. Typical scenarios include the termination of membership in a social organisation, ending the employment at a company, divorce, and the end of tenure of somebody in an official position. |
Examples: |
|
Properties: | P145 separated (left by) E39 Actor P146 separated from (lost member by) E74 Group |
P143 joined (was joined by)
Domain: | E85 Joining |
Range: | E39 Actor |
Subproperty of: | E5 Event. P11 had participant (participated in): E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: | This property identifies the instance of E39 Actor that becomes member of a E74 Group in an E85 Joining. |
Examples: |
|
P144 joined with (gained member by)
Domain: | E85 Joining |
Range: | E74 Group |
Subproperty of: | E5 Event. P11 had participant (participated in): E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: | This property identifies the instance of E74 Group of which an instance of E39 Actor becomes a member through an instance of E85 Joining. Although a Joining activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which becoming member of one Group implies becoming member of another Group as well. |
Examples: |
|
P145 separated (left by)
Domain: | E86 Leaving |
Range: | E39 Actor |
Subproperty of: | E5 Event. P11 had participant (participated in):E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: | This property identifies the instance of E39 Actor that leaves an instance of E74 Group through an instance of E86 Leaving. |
Examples: |
|
P146 separated from (lost member by)
Domain: | E86 Leaving |
Range: | E74 Group |
Subproperty of: | E5 Event. P11 had participant (participated in): E39 Actor |
Quantification: | many to many, necessary (1,n:0,n) |
Scope note: |
This property identifies the instance of E74 Group an instance of E39 Actor leaves through an instance of E86 Leaving. Although a Leaving activity normally concerns only one instance of E74 Group, it is possible to imagine circumstances under which leaving one E74 Group implies leaving another E74 Group as well. |
Examples: |
|
Crete 12-15 May 2008
Proposal accepted