5.3.1.3 Thema: E55 Type P2i is type Instance of E1 CRM Entity relationship 5.3.1.4 Thema: This is a statement about the Polyhierarchical cardinality of the relationships relationship enumerated in section 5.3 of FRSAD, rather than a distinct relationship in its own right 5.3.1.5 Thema: Other hierarchical relationship 5.3.2 Thema: Any other No model necessary “related Associative relationship. to” relationships 3.5 Nomen F12 Nomen 4.2.1 Nomen: Type F12 Nomen P2 has of nomen type E55 Type 4.2.2 Nomen: F35 Nomen Use FRSAD:Scheme = KOS, FRAD Scheme Statement R35 is E32 Authority “authority file” ⁬⊃ specified by F34 Document. KOS The scheme in which the nomen is established, including value encoding schemes (subject heading lists, thesauri, classification systems, name authority lists, etc.) and syntax encoding schemes (standards for encoding dates, etc.). 4.2.3 Nomen: Warning! F35 Nomen Use Reference Only if Statement R32 is source of Nomen is warranted by F52 nomen uniquely Name Use Activity defined by one symbolic form 4.2.4 Nomen: F12 Nomen. P2 has Representation type E55 Type 4.2.5 Nomen: F35 Nomen Use Language Statement (instantiated as E33 Linguistic Object) R54 has nomen language E56 Language 4.2.6 Nomen: Script The script F12 Nomen P2 has type in the type E55 Type sense of ISO15924 4.2.7 Nomen: Script F35 Nomen Use conversion Statement R36 uses script conversion F36 Script Conversion
5.3.1.3 Thema: Instance relationship E55 Type P2i is type of E1 CRM Entity 5.3.1.4 Thema: Polyhierarchical relationship This is a statement about the cardinality of the relationships enumerated in section 5.3 of FRSAD, rather than a distinct relationship in its own right 5.3.1.5 Thema: Other hierarchical relationship 5.3.2 Thema: Associative relationships Any other “related to” relationship. No model necessary 3.5 Nomen F12 Nomen 4.2.1 Nomen: Type of nomen F12 Nomen P2 has type E55 Type 4.2.2 Nomen: Scheme F35 Nomen Use Statement R35 is specified by F34 KOS FRSAD:Scheme = KOS, FRAD “authority file” ⁬⊃ E32 Authority Document. The scheme in which the nomen is established, including value encoding schemes (subject heading lists, thesauri, classification systems, name authority lists, etc.) and syntax encoding schemes (standards for encoding dates, etc.). 4.2.3 Nomen: Reference source of nomen Warning! Only if Nomen is uniquely defined by one symbolic form F35 Nomen Use Statement R32 is warranted by F52 Name Use Activity 4.2.4 Nomen: Representation F12 Nomen. P2 has type E55 Type 4.2.5 Nomen: Language F35 Nomen Use Statement (instantiated as E33 Linguistic Object) R54 has nomen language E56 Language 4.2.6 Nomen: Script The script type in the sense of ISO15924 F12 Nomen P2 has type E55 Type 4.2.7 Nomen: Script conversion F35 Nomen Use Statement R36 uses script conversion F36 Script Conversion
FRBRoo_V2.4.docx