is not in scope of FRAD, not even in the context of describing publishers. Fictitious places are treated as concepts (Themas etc). 3.4 Name F12 Nomen E41 Appellation FRSAD:Nomen = F12 Nomen FRBR Name FRAD: Name E41 may include names in the sense of linguistics with a history of evolution. Attribute FRBR Name restricted to characters, FRSAD adds signs. FRAD name excludes constructed identifiers 4.12 Name: Type of F52 Name Use Activity R63 Actually the type of the name named E1 CRM Entity P2 thema has type E55 Type 4.12 Name: Name string F12 Nomen R33 has A sequence of numeric content{R33.1has encoding and/or alphabetic 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
is not in scope of FRAD, not even in the context of describing publishers. Fictitious places are treated as concepts (Themas etc). 3.4 Name F12 Nomen E41 Appellation FRSAD:Nomen = F12 Nomen FRBR Name FRAD: Name E41 may include names in the sense of linguistics with a history of evolution. Attribute FRBR Name restricted to characters, FRSAD adds signs. FRAD name excludes constructed identifiers 4.12 Name: Type of name F52 Name Use Activity R63 named E1 CRM Entity P2 has type E55 Type Actually the type of the thema 4.12 Name: Name string F12 Nomen R33 has content{R33.1has encoding E55 Type} E62 String A sequence of numeric and/or alphabetic 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
FRBRoo_V2.4.docx