[3.2]
|
Work
|
|
F1 Work
|
|
5.1
|
Work: has subject
|
|
F1 Work P129 is about E1 CRM Entity
|
|
|
|
|
|
|
3.4
|
Thema
|
|
E1 CRM Entity
|
Appears as the reference to any entity without specifying a specific way in which the entity appears in the work. MD: relational expression to anything => class = E1
|
4.1.1
|
Thema: Type of thema
|
|
E1 CRM Entity. P2 has type E55 Type
|
|
4.1.2
|
Thema: Scope note
|
|
E1 CRM Entity. P3 has note E62 String
|
|
5.1
|
Thema: is subject of
|
|
E1 CRM Entity P1029i is subject of F1 Work
|
|
5.2
|
Thema: has appellation
|
|
E1 CRM Entity P1 is identified by F12 Nomen
|
|
5.3.1.1
|
Thema: Generic relationship
|
|
IsA
OR
E55 Type P127 has broader term (has narrower term) E55 Type
|
|
5.3.1.2
|
Thema: Whole-part relationship
|
|
a) for E55 Type:
SKOS broader partitive
b) a series of CRM properties relating to inclusion to be listed
|
|
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
|
|
4.2.8
|
Nomen: Form
|
|
F35 Nomen Use Statement R55 has nomen form E55 Type
|
|
4.2.9
|
Nomen: Time of validity of nomen
|
|
F35 Nomen Use Statement R35 is specified by F34 KOS R34 has validity period E52 Time-Span
|
Only validity status of participation in KOS release
|
4.2.10
|
Nomen: Audience
|
|
F35 Nomen Use Statement R39 is intended for E74 Group
|
Audience is not usage status
|
4.2.11
|
Nomen: Status
|
|
F35 Nomen Use Statement R35 is specified by {R35.1 has status E55 Type} F34 KOS
|
|
5.2
|
Nomen: is appellation of
|
|
F12 Nomen P1i identifies E1 CRM Entity
|
|
5.4.1
|
Nomen: Equivalence relationship
|
|
F35 Nomen Use Statement R56 has related use {R56.1 has type E55 Type = “equivalence”} F35 Nomen Use Statement
|
|
5.4.2
|
Nomen: Whole-part relationship
|
|
F35 Nomen Use Statement P106 is composed of E90 Symbolic Object
|
|
