4.12 Name: Covered by FRSAD model Language of name 5.2 Name: is F12 Nomen P1i identifies appellation of E1 CRM Entity 5.4.1 Earlier/Later Connect two F52 Name name Use Activities by P120 relationship 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 E1 CRM Entity P38i is 4 name thema of F35 Nomen Use relationships Statement R37 states as nomen F12 Nomen 5.4.3 Expanded name E1 CRM Entity P38i is relationship thema of F35 Nomen Use (Acronym / Statement R37 states as initials / nomen F12 Nomen abbreviations 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 use F13 Identifier, but model Controlled Access Point 4.13 Identifier: Type F13 Identifier P2 has We include types of CAPs in the of an identifier Type E55 Type sense of structural differentiation of the Identifier composition which may come with different Entity types they are designed for 5.2 Identifier: is F13 Identifier P1i assigned to identifies E1 CRM Entity 3.4 Controlled F50 Controlled Access Access Point Point 4.14 CAP: Status of covered by FRSAD and is controlled described in the scope notes of access point F34 KOS and R34 has validity period (is validity period of) 4.14 CAP: F50 Controlled Access Designated Point R37i is stated as usage of nomen in F35 Nomen Use controlled Statement P2 has type access point E55 Type 4.14 CAP: F50 Controlled Access Point R37i is stated as access point nomen in F35 Nomen Use Statement P2 has type
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 use F13 Identifier, but model Controlled Access Point 4.13 Identifier: Type of an identifier F13 Identifier P2 has Type E55 Type We include types of CAPs in the sense of structural differentiation of the Identifier composition which may come with different Entity types they are designed for 5.2 Identifier: is assigned to F13 Identifier P1i identifies E1 CRM Entity 3.4 Controlled Access Point F50 Controlled Access Point 4.14 CAP: Status of controlled access point covered by FRSAD and is described in the scope notes of F34 KOS and R34 has validity period (is validity period of) 4.14 CAP: Designated usage of controlled access point F50 Controlled Access Point R37i is stated as nomen in F35 Nomen Use Statement P2 has type E55 Type 4.14 CAP: access point F50 Controlled Access Point R37i is stated as nomen in F35 Nomen Use Statement P2 has type
FRBRoo_V2.1_2015February.docx