Issue 222: P37, P38, P48 identifiers
Posted by vladimir.alexiev on 21/11/2012
P37, P38, P48 apply to Identifier but I think they should be moved upwards to apply to Appellation. Consequently, two renamings will be needed: E15_Appellation_Assignment, P48_has_preferred_appellation
Reasons:
- P48: see email "Preferred Identifier vs Appellation vs Image"
- P37, P38:
people, groups, places, works of art and conceptual objects are known by different names in different times.
Tracking the temporal validity of identifiers may be important, but it seems to me doing it for these other entities may be more important yet. The BM at least is tracking the temporal validity of person names.
I'll describe a complementary or alternative solution re P37, P38 in further email "ADDITION: property "active in period"
Posted by vladimir.alexiev on 21/11/2012
I propose to add a new property "active in period" with range E4 Period.
The domain should include E39 Actor and E41 Appellation, so I think should be E77 Persistent Item.
If it's judged that such property cannot be defined meaningfully for E77, then could be split to two proeperties for E39 and E41.
Reasons:
1. E39 Actor: BM has a field "period of activity of the actor".
We currently model this as "was present at" a "fake" Event, but P12 doesn't quite say what we need:
2. E41 Appellation: BM tracks temporal validity of person names.
- One solution is described in email "ISSUE: P37, P38, P48 should be moved up to Appellation":
P37i_was_assigned_by
P38i_was_deassigned_by
P4_has_time-span
P82_at_some_time_within "1600".
P4_has_time-span
P82_at_some_time_within "1850".
- But "active in period" would be a much better solution, since it also allows you to specify the cultural period through which the name was used:
P200_active_in_period
P3_has_note "Medieval France";
P7_took_place_at
P4_has_time-span
P82a_begin_of_the_begin "1100";
P82b_end_of_the_end "1650".
The issue is not accepted since P48 implies a default context, which cannot be assumed for appellations in general.
FRBRoo completely covers the issue.
CRM-SIG, Stockholm 7/6/2013