Modeling sequence of given names, e.g. “Johan Ludvig”

[yoge1]

Should a sequence of given names, e.g. “Johan Ludvig” be modelled with several forenames (components of the Linguistic Appellation), and if so, how do we indicate the order of names, only by the indices in url (..name/[123]/…)?

[yoge1]

Both. "Johan Ludvig" as a forename component which has two forename components: "Johan" and "Ludvig".

[sennierer]

currently we have 3 different ways of modelling the names:

• in APIS we use E21_person -> crm:P1_is_identified_by -> crm:E33_E41_Linguistic_Appellation -> crm:P148_has_component -> crm:E33_E41_Linguistic_Appellation and we use it for two components only (one for surname, one for first_name
• in BSampo we also use E21_person -> crm:P1_is_identified_by -> crm:E33_E41_Linguistic_Appellation -> crm:P148_has_component -> crm:E33_E41_Linguistic_Appellation but all the labels are split on whitespace an that means that we have several first_name appellations and surname appellations
• in BNet we use E21_person -> crm:P1_is_identified_by -> crm:E89_Propositional_Object. However, I dont know how the labels are split.
• SBI uses a modelling similar to APIS
  @biktorrr is there any specific reason you are using E89 rather than the Linguistic_Appellation?
  @ptleskin and @yoge1 would it be ok to stick to one first_name Appellation only?

[biktorrr]

I think in BNet we do use linguistic appellation (with an rdfs label ) and additionally E89 propositional object if that is available. So for bgn:PersonDes-8545844_02<http://130.37.53.36:6789/browse/list_resource?r=http%3A//data.biographynet.nl/rdf/PersonDes-8545844_02> : bgn:PersonDes-8545844_02 crm:P1_is_identified_by bgn:PersonDes-8545844_02-7731944-name . bgn:PersonDes-8545844_02-7731944-name a crm:E33_E41_Linguistic_Appellation ;      rdfs:label " A. Hansen RA " crm:P148_has_component bgn:RA , bgn:A , bgn:Hansen . bgn:RA a crm:E89_Propositional_Object ;      rdfs:label "RA" . to be honest, I am not sure why I use E89 for the components. But if we agree that these should be Ling. appellations, I can update that. best Victor

…

________________________________ From: Matthias Schlögl ***@***.***> Sent: Tuesday, October 11, 2022 17:29 To: InTaVia/idm-rdf ***@***.***> Cc: Boer, V. de (Victor) ***@***.***>; Mention ***@***.***> Subject: Re: [InTaVia/idm-rdf] Modeling sequence of given names, e.g. “Johan Ludvig” (Issue #17) currently we have 3 different ways of modelling the names: * in APIS we use E21_person -> crm:P1_is_identified_by -> crm:E33_E41_Linguistic_Appellation -> crm:P148_has_component -> crm:E33_E41_Linguistic_Appellation and we use it for two components only (one for surname, one for first_name * in BSampo we also use E21_person -> crm:P1_is_identified_by -> crm:E33_E41_Linguistic_Appellation -> crm:P148_has_component -> crm:E33_E41_Linguistic_Appellation but all the labels are split on whitespace an that means that we have several first_name appellations and surname appellations * in BNet we use E21_person -> crm:P1_is_identified_by -> crm:E89_Propositional_Object. However, I dont know how the labels are split. * SBI uses a modelling similar to APIS @biktorrr<https://github.com/biktorrr> is there any specific reason you are using E89 rather than the Linguistic_Appellation? @ptleskin<https://github.com/ptleskin> and @yoge1<https://github.com/yoge1> would it be ok to stick to one first_name Appellation only? — Reply to this email directly, view it on GitHub<#17 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALS74IX5AQIE27C6VT5ZHLWCWBXHANCNFSM5TKXNV7A>. You are receiving this because you were mentioned.Message ID: ***@***.***>