E55 Type} E62 String characters or symbols that represents the name of an entity. Decision: We regard that any instance/subclass of Nomen should foresee a content string that completely represents the identity of a Nomen instance regardless of the semantics of the structural components it is built from. A nomen identity may not extend to the interpretation of equivalence of structural components. Occurrences of structural tags in the nomen string are regarded as part of the content symbols. 4.12 Name: Scope of F52 Name Use Activity R61 usage occurred in kind of context E55 Type 4.12 Name: Dates of F52 Name Use Activity P4 usage had time-span E52 4.12 Name: Language of Covered by FRSAD model name 5.2 Name: is F12 Nomen P1i identifies E1 appellation of CRM Entity 5.4.1 Earlier/Later name Connect two F52 Name Use relationship Activities by P120 occurs after 5.4.1, 2, Alternative E1 CRM Entity P38i is 3, 4 linguistic form thema of F35 Nomen Use relationship Statement (R37 states as nomen F12 Nomen, P14 carried out by E39 Actor), 5.4.1, 3, Other variant name E1 CRM Entity P38i is 4 relationships thema of F35 Nomen Use Statement R37 states as nomen F12 Nomen 5.4.3 Expanded name E1 CRM Entity P38i is relationship thema of F35 Nomen Use (Acronym / initials / Statement R37 states as abbreviations nomen F12 Nomen relationship) 3.4 Identifier E42 Identifier = F13 FRAD Identifier FRAD ∩ Identifier = (FRAD Controlled Access Point = Identifier FRAD Controlled Access Point). If no attribute specific to FRAD Identifier only can be found, no reason to model disjointness, and
E55 Type} E62 String characters or symbols that represents the name of an entity. Decision: We regard that any instance/subclass of Nomen should foresee a content string that completely represents the identity of a Nomen instance regardless of the semantics of the structural components it is built from. A nomen identity may not extend to the interpretation of equivalence of structural components. Occurrences of structural tags in the nomen string are regarded as part of the content symbols. 4.12 Name: Scope of usage F52 Name Use Activity R61 occurred in kind of context E55 Type 4.12 Name: Dates of usage F52 Name Use Activity P4 had time-span E52 4.12 Name: Language of name Covered by FRSAD model 5.2 Name: is appellation of F12 Nomen P1i identifies E1 CRM Entity 5.4.1 Earlier/Later name relationship Connect two F52 Name Use Activities by P120 occurs after 5.4.1, 2, 3, 4 Alternative linguistic form relationship E1 CRM Entity P38i is thema of F35 Nomen Use Statement (R37 states as nomen F12 Nomen, P14 carried out by E39 Actor), 5.4.1, 3, 4 Other variant name relationships E1 CRM Entity P38i is thema of F35 Nomen Use Statement R37 states as nomen F12 Nomen 5.4.3 Expanded name relationship (Acronym / initials / abbreviations relationship) E1 CRM Entity P38i is thema of F35 Nomen Use Statement R37 states as nomen F12 Nomen 3.4 Identifier E42 Identifier = F13 Identifier = (FRAD Identifier FRAD Controlled Access Point). FRAD Identifier ∩ FRAD Controlled Access Point = If no attribute specific to FRAD Identifier only can be found, no reason to model disjointness, and