Properties

Domain Property Range Namespace Last updated
Digital Machine Event – D7 was ongoing at – L61 Time Primitive – E61 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digitization Process – D2 documents – L60 CRM Entity – E1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Man-Made Object – E22 has serial number – L59 String – E62 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Data Object – D9 has pixel height – L57 Number – E60 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Data Object – D9 has pixel width – L56 Number – E60 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
CRM Entity – E1 is not uniquely identified by – L53 String – E62 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
CRM Entity – E1 has preferred label – L4 String – E62 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Person Name – D21 has last name – L52 String – E62 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Person Name – D21 has first name – L51 String – E62 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Area – D35 is propagated area of – L50 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Area – D35 is primary area of – L49 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Annotation Event – D30 created annotation – L48 Annotation Object – D29 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
CRM Entity – E1 has comment – L47 String – E62 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Annotation Object – D29 annotates – L43 CRM Entity – E1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-31
Activity – E7 has commissioner – L35 Legal Body – E40 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Activity – E7 has contractor – L34 Legal Body – E40 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Physical Man-Made Thing – E24 has maker – L33 Actor – E39 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 has ending date-time – L32 Time Primitive – E61 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 has starting date-time – L31 Time Primitive – E61 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Activity – E7 has operator – L30 Person – E21 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Activity – E7 has responsible organization – L29 Legal Body – E40 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Software Execution – D10 created logfile – L24 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 used software or firmware – L23 Software – D14 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Formal Derivation – D3 created derivative – L22 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Formal Derivation – D3 used as derivation source – L21 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Measurement Event – D11 has created – L20 Data Object – D9 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Information Carrier – D13 stores – L19 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 has modified – L18 Digital Information Carrier – D13 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Measurement Event – D11 measured thing of type – L17 Type – E55 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Data Transfer Event – D12 has receiver – L16 Digital Device – D8 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-03-26
Data Transfer Event – D12 has sender – L15 Digital Device – D8 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Data Transfer Event – D12 transferred – L14 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Software Execution – D10 used parameters – L13 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 happened on device – L12 Digital Device – D8 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 had output – L11 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digital Machine Event – D7 had input – L10 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Software Execution – D10 used as source – L2 Digital Object – D1 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Digitization Process – D2 digitized – L1 Physical Thing – E18 CRMdig: An Extension of CIDOC CRM to support provenance metadata 2019-01-25
Belief – I2 holds to be – J5 Belief Value – I6 CRMinf: An Extension of CIDOC-CRM to support argumentation 2019-01-23
Belief – I2 that – J4 Proposition Set – I4 CRMinf: An Extension of CIDOC-CRM to support argumentation 2019-01-23
Inference Making – I5 applies – J3 Inference Logic – I3 CRMinf: An Extension of CIDOC-CRM to support argumentation 2019-01-23
Argumentation – I1 conclued that – J2 Belief – I2 CRMinf: An Extension of CIDOC-CRM to support argumentation 2019-01-23
Inference Making – I5 used as premise – J1 Belief – I2 CRMinf: An Extension of CIDOC-CRM to support argumentation 2019-01-23
Embedding – A7 is embedding at – AP20 Place – E53 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Embedding – A7 is embedding in – AP19 Stratigraphic Volume Unit – A2 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Embedding – A7 is embedding of – AP18 Physical Thing – E18 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Embedding – A7 is found by – AP17 Encounter Event – S19 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Group Declaration Event – A6 assigned attribute to – AP16 Stratigraphic Unit – A8 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Unit – A8 is or contains remains of – AP15 Physical Thing – E18 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Unit – A8 has stratigraphic relation – AP13 Stratigraphic Unit – A8 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Interface – A3 confines – AP12 Stratigraphic Volume Unit – A2 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Unit – A8 has physical relation – AP11 Stratigraphic Unit – A8 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Excavation Process Unit – A1 destroyed – AP10 Segment of Matter – S22 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Genesis – A4 took matter from – AP9 Material Substantial – S10 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Genesis – A4 disturbed – AP8 Stratigraphic Interface – A3 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Stratigraphic Genesis – A4 produced – AP7 Stratigraphic Interface – A3 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Excavation Process Unit – A1 intended to approximate – AP6 Stratigraphic Interface – A3 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Excavation Process Unit – A1 removed part or all of – AP5 Stratigraphic Unit – A8 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Excavation Process Unit – A1 produced surface – AP4 Physical Feature – S20 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Excavation Process Unit – A1 excavated – AP3 Place – E53 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2019-01-23
Excavation Process Unit – A1 discarded into – AP2 Amount of Matter – S11 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2018-11-29
Excavation Process Unit – A1 produced – AP1 Amount of Matter – S11 CRMarchaeo: An Extension of CIDOC CRM to support the archaeological excavation process 2018-11-29
Measurement – S21 measured (was measured by) – O24 Observable Entity – S15 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Segment of Matter – S22 is defined by (defines) – O23 Spacetime Volume – E92 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Segment of Matter – S22 partly or completely contains (is part of) – O22 Physical Feature – S20 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Encounter Event – S19 has found at (witnessed) – O21 Place – E53 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Sample Taking – S2 sampled from type of part (type of part was sampled by) – O20 Type – E55 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Encounter Event – S19 has found object (was object found by) – O19 Physical Thing – E18 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Alteration – S18 altered (was altered by) – O18 Physical Thing – E18 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Physical Genesis – S17 generated (was generated by) – O17 Physical Thing – E18 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Observation – S4 observed value (value was observed by) – O16 CRM Entity – E1 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Material Substantial – S10 occupied (was occupied by) – O15 Place – E53 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Event – E5 initializes (is initialized by) – O14 State – S16 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Event – E5 triggers (is triggered by) – O13 Event – E5 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Observable Entity – S15 has dimension (is dimension of) – O12 Dimension – E54 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Data Evaluation – S6 described (was described by) – O11 Observable Entity – S15 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Data Evaluation – S6 assigned dimension (dimension was assigned by) – O10 Dimension – E54 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Observation – S4 observed property type (property type was observed by) – O9 Property Type – S9 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Observation – S4 observed (was observed by) – O8 Observable Entity – S15 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Place – E53 contains or confines (is contained or confined) – O7 Place – E53 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Amount of Fluid – S12 forms former or current part of (has former or current part) – O6 Fluid Body – S14 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Sample Taking – S2 removed (was removed by) – O5 Sample – S13 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Sample Taking – S2 sampled at ((was sampling location of) – O4 Place – E53 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Sample Taking – S2 sampled from (was sample by) – O3 Material Substantial – S10 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Matter Removal – S1 removed (was removed by) – O2 Amount of Matter – S11 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Matter Removal – S1 diminished (was diminished by) – O1 Material Substantial – S10 CRMsci: An Extension of CIDOC CRM to support scientific observation 2019-12-06
Temporal Reference System – SP11 has reference event – Q19 Event – E5 CRMgeo: a Spatiotemporal Model 2019-01-23
Spacetime Volume Expression – SP12 is expressed in terms of – Q18 Spatial Coordinate Reference System – SP4 CRMgeo: a Spatiotemporal Model 2019-01-23
Spacetime Volume Expression – SP12 is expressed in terms of – Q17 Temporal Reference System – SP11 CRMgeo: a Spatiotemporal Model 2019-01-23
Spacetime Volume Expression – SP12 defines spacetime volume – Q16 Declarative Spacetime Volume – SP7 CRMgeo: a Spatiotemporal Model 2019-01-23
Time Expression – SP14 is expressed in terms of – Q15 Temporal Reference System – SP11 CRMgeo: a Spatiotemporal Model 2019-01-23
Time Expression – SP14 defines time – Q14 Declarative Time-Span – SP10 CRMgeo: a Spatiotemporal Model 2019-01-23
Declarative Time-Span – SP10 approximates – Q13 Time-Span – E52 CRMgeo: a Spatiotemporal Model 2019-01-23
Declarative Spacetime Volume – SP7 approximates – Q12 Spacetime Volume – E92 CRMgeo: a Spatiotemporal Model 2019-01-23
Declarative Place – SP6 approximates – Q11 Place – E53 CRMgeo: a Spatiotemporal Model 2019-01-23
Geometric Place Expression – SP5 defines place – Q10 Declarative Place – SP6 CRMgeo: a Spatiotemporal Model 2019-01-23
Geometric Place Expression – SP5 is expressed in terms of – Q9 Spatial Coordinate Reference System – SP4 CRMgeo: a Spatiotemporal Model 2019-01-23
Spatial Coordinate Reference System – SP4 is fixed on – Q8 Physical Feature – E26 CRMgeo: a Spatiotemporal Model 2019-01-23
Spatial Coordinate Reference System – SP4 describes – Q7 Reference Space – SP3 CRMgeo: a Spatiotemporal Model 2019-01-23
Reference Space – SP3 is at rest in relation to – Q6 Physical Thing – E18 CRMgeo: a Spatiotemporal Model 2019-01-23
Place – E53 defined in – Q5 Reference Space – SP3 CRMgeo: a Spatiotemporal Model 2019-01-23
Phenomenal Spacetime Volume – SP1 has spatial projection – Q4 Phenomenal Place – SP2 CRMgeo: a Spatiotemporal Model 2019-01-23
Phenomenal Spacetime Volume – SP1 has temporal projection – Q3 Phenomenal Time-Span – SP13 CRMgeo: a Spatiotemporal Model 2019-01-23
Physical Thing – E18 occupied – Q2 Phenomenal Spacetime Volume – SP1 CRMgeo: a Spatiotemporal Model 2019-01-23
Period – E4 occupied – Q1 Phenomenal Spacetime Volume – SP1 CRMgeo: a Spatiotemporal Model 2019-01-23
Performance – F31 included performed version of – R66 Propositional Object – E89 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Recording Event – F29 recorded aspects of – R65 Physical Thing – E18 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Name Use Activity – F52 used name – R64 Appellation – E41 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Name Use Activity – F52 named – R63 CRM Entity – E1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Name Use Activity – F52 was used for membership in – R62 Group – E74 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Name Use Activity – F52 occured in kind of context – R61 Type – E55 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Pursuit – F51 used to use language – R60 Language – E56 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Pursuit – F51 had typical subject – R59 CRM Entity – E1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Character – F38 has fictional member – R58 Character – F38 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Character – F38 is based on – R57 Actor – E39 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 has related use – R56 Nomen Use Statement – F35 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 has nomen form – R55 Type – E55 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 has nomen language – R54 Language – E56 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Manifestation Assignment – F41 assigned – R53 Manifestation Singleton – F4 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Identifier Assignment – F40 used rule – R52 Identifier Rule – F43 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Expression Assignment – F42 assigned – R51 Expression – F2 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Expression Assignment – F42 assigned to – R50 Complex Work – F15 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Manifestation Assignment – F41 assigned – R49 Manifestation Product Type – F3 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Manifestation Assignment – F41 assigned to – R48 Expression – F2 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Identifier Assignment – F40 assigned to – R46 Identifier – F13 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Identifier Assignment – F40 assigned to – R45 CRM Entity – E1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Expression Assignment – F42 carried out by – R44 Bibliographic Agency – F44 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Representative Manifestation Assignment – F41 carried out by – R43 Bibliographic Agency – F44 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Manifestation Singleton – F4 is representative manifestation singleton for – R42 Expression – F2 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression – F2 has rep manifestation product type – R41 Manifestation Product Type – F3 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Work – F1 has representative expression – R40 Self-Contained Expression – F22 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 is intended for – R39 Group – E74 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 refers to thema – R38 CRM Entity – E1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 states as nomen – R37 Nomen – F12 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 uses script conversion – R36 Script Conversion – F36 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 specified by – R35 KOS – F34 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
KOS – F34 has validity period – R34 Time-Span – E52 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen – F12 has content – R33 String – E62 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Nomen Use Statement – F35 is warranted by – R32 Name Use Activity – F52 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Information Carrier – E84 is reproduction of – R31 Information Carrier – E84 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Reproduction Event – F33 produced – R30 Information Carrier – E84 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Reproduction Event – F33 reproduced – R29 Information Carrier – E84 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Carrier Production Event – F32 produced – R28 Utilized Information Carrier – F54 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Carrier Production Event – F32 used as source material – R27 Publication Expression – F24 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Carrier Production Event – F32 produced things of type – R26 Manifestation Product Type – F3 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Performance – F31 performed – R25 Performance Plan – F25 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Publication Event – F30 created – R24 Publication Expression – F24 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Publication Event – F30 created a realization of – R23 Publication Work – F19 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Recording Event – F29 created a realization of – R22 Recording Work – F21 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Recording Event – F29 created – R21 Recording – F26 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Recording Event – F29 recorded – R20 Temporal Entity – E2 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression Creation – F28 created a realization of – R19 Work – F1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression Creation – F28 created – R18 Manifestation Singleton – F4 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression Creation – F28 created – R17 Expression – F2 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Work Conception – F27 initiated – R16 Work – F1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression – F2 has fragment – R15 Expression Fragment – F23 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Recording Work – F21 is realised in – R13 Recording – F26 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Performance Work – F20 is realised in – R12 Performance Plan – F25 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Serial Work – F18 has issuing rule – R11 Design or Procedure – E29 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Complex Work – F15 has member – R10 Work – F1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Individual Work – F14 is realised in – R9 Self-Contained Expression – F22 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Identifier – F13 consists of – R8 Symbolic Object – E90 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Item – F5 (0,n) is example of – R7 (1,1) Manifestation Product Type – F3 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Utilized Information Carrier – F54 carries – R6 Publication Expression – F24 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression – F2 has component – R5 Self-Contained Expression – F22 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Expression – F2 carriers provided by – R4 Manifestation Product Type – F3 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Work – F1 is realised in – R3 Self-Contained Expression – F22 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Work – F1 is derivative of – R2 Work – F1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Work – F1 is logical successor of – R1 Work – F1 FRBRoo: Functional Requirements for Bibliographic Records 2020-03-31
Manifestation Product Type – F3 should carry – CLR6 Publication Expression – F24 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 right held by – CLP105 Actor – E39 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 subject to – CLP104 Right – E30 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 should have number of parts – CLP57 Number – E60 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 should be composed of – CLP46 Manifestation Product Type – F3 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 should consist of – CLP45 Material – E57 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 should have dimension – CLP43 Dimension – E54 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Manifestation Product Type – F3 should have type – CLP2 Type – E55 FRBRoo: Functional Requirements for Bibliographic Records 2019-01-24
Time-Span – E52 end of the end – P82b Time Primitive – E61 CIDOC CRM 2018-11-16
Time-Span – E52 begin of the begin – P82a Time Primitive – E61 CIDOC CRM 2018-11-16
Time-Span – E52 begin of the end – P81b Time Primitive – E61 CIDOC CRM 2018-11-16
Time-Span – E52 end of the begin – P81a Time Primitive – E61 CIDOC CRM 2018-11-16
Place – E53 place is defined by – P168 Space Primitive – E94 CIDOC CRM 2018-11-16
Presence – E93 (1,1) was at – P167 (1,1) Place – E53 CIDOC CRM 2018-11-16
Presence – E93 (0,n) was a presence of – P166 (1,1) Spacetime Volume – E92 CIDOC CRM 2020-01-03
Information Object – E73 incorporates – P165 Symbolic Object – E90 CIDOC CRM 2018-11-16
Presence – E93 during – P164 Time-Span – E52 CIDOC CRM 2018-11-16
Spacetime Volume – E92 has spatial projection – P161 Place – E53 CIDOC CRM 2018-11-16
Spacetime Volume – E92 has temporal projection – P160 Time-Span – E52 CIDOC CRM 2018-11-16
Place – E53 is at rest relative to – P157 Physical Thing – E18 CIDOC CRM 2018-11-16
Physical Thing – E18 occupies – P156 Place – E53 CIDOC CRM 2018-11-16
Person – E21 has parent – P152 Person – E21 CIDOC CRM 2018-11-16
Formation – E66 (0,n) was formed from – P151 (1,n) Group – E74 CIDOC CRM 2018-11-16
Type – E55 defines typical parts of – P150 Type – E55 CIDOC CRM 2018-11-16
Conceptual Object – E28 is identified by – P149 Conceptual Object Appellation – E75 CIDOC CRM 2018-11-16
Propositional Object – E89 has component – P148 Propositional Object – E89 CIDOC CRM 2018-11-16
Curation Activity – E87 curated – P147 Collection – E78 CIDOC CRM 2018-11-16
Leaving – E86 (0,n) separated from – P146 (1,1) Group – E74 CIDOC CRM 2018-11-16
Leaving – E86 (0,n) separated – P145 (1,1) Actor – E39 CIDOC CRM 2018-11-16
Joining – E85 (0,n) joined with – P144 (1,1) Group – E74 CIDOC CRM 2018-11-16
Joining – E85 (0,n) joined – P143 (1,1) Actor – E39 CIDOC CRM 2018-11-16
Identifier Assignment – E15 used constituent – P142 Symbolic Object – E90 CIDOC CRM 2018-11-16
Attribute Assignment – E13 assigned – P141 CRM Entity – E1 CIDOC CRM 2018-11-16
Attribute Assignment – E13 assigned attribute to – P140 CRM Entity – E1 CIDOC CRM 2018-11-16
Appellation – E41 has alternative form – P139 Appellation – E41 CIDOC CRM 2018-11-16
Visual Item – E36 represents – P138 CRM Entity – E1 CIDOC CRM 2018-11-16
CRM Entity – E1 exemplifies – P137 Type – E55 CIDOC CRM 2018-11-16
Type Creation – E83 was based on – P136 CRM Entity – E1 CIDOC CRM 2018-11-16
Type Creation – E83 created type – P135 Type – E55 CIDOC CRM 2018-11-16
Activity – E7 continued – P134 Activity – E7 CIDOC CRM 2018-11-16
Spacetime Volume – E92 is separated from – P133 Spacetime Volume – E92 CIDOC CRM 2018-11-16
Spacetime Volume – E92 overlaps with – P132 Spacetime Volume – E92 CIDOC CRM 2018-11-16
Actor – E39 is identified by – P131 Actor Appellation – E82 CIDOC CRM 2018-11-16
Thing – E70 shows features of – P130 Thing – E70 CIDOC CRM 2018-11-16
Propositional Object – E89 is about – P129 CRM Entity – E1 CIDOC CRM 2018-11-16
Physical Thing – E18 carries – P128 Symbolic Object – E90 CIDOC CRM 2018-11-16
Type – E55 (0,n) has broader term – P127 (0,n) Type – E55 CIDOC CRM 2020-01-04
Modification – E11 employed – P126 Material – E57 CIDOC CRM 2018-11-16
Activity – E7 used object of type – P125 Type – E55 CIDOC CRM 2018-11-16
Transformation – E81 transformed – P124 Persistent Item – E77 CIDOC CRM 2018-11-16
Transformation – E81 resulted in – P123 Persistent Item – E77 CIDOC CRM 2018-11-16
Place – E53 borders with – P122 Place – E53 CIDOC CRM 2018-11-16
Place – E53 overlaps with – P121 Place – E53 CIDOC CRM 2018-11-16
Temporal Entity – E2 occurs before – P120 Temporal Entity – E2 CIDOC CRM 2018-11-16
Temporal Entity – E2 meets in time with – P119 Temporal Entity – E2 CIDOC CRM 2018-11-16
Temporal Entity – E2 overlaps in time with – P118 Temporal Entity – E2 CIDOC CRM 2018-11-16
Temporal Entity – E2 occurs during – P117 Temporal Entity – E2 CIDOC CRM 2018-11-16
Temporal Entity – E2 starts – P116 Temporal Entity – E2 CIDOC CRM 2018-11-16
Temporal Entity – E2 finishes – P115 Temporal Entity – E2 CIDOC CRM 2018-11-16
Temporal Entity – E2 is equal in time to – P114 Temporal Entity – E2 CIDOC CRM 2018-11-16
Part Removal – E80 removed – P113 Physical Thing – E18 CIDOC CRM 2018-11-16
Part Removal – E80 diminished – P112 Physical Man-Made Thing – E24 CIDOC CRM 2018-11-16
Part Addition – E79 added – P111 Physical Thing – E18 CIDOC CRM 2018-11-16
Part Addition – E79 augmented – P110 Physical Man-Made Thing – E24 CIDOC CRM 2018-11-16
Collection – E78 has current or former curator – P109 Actor – E39 CIDOC CRM 2018-11-16
Production – E12 has produced – P108 Physical Man-Made Thing – E24 CIDOC CRM 2018-11-16
Group – E74 has current or former member – P107 Actor – E39 CIDOC CRM 2018-11-16
Symbolic Object – E90 is composed of – P106 Symbolic Object – E90 CIDOC CRM 2018-11-16
Legal Object – E72 right held by – P105 Actor – E39 CIDOC CRM 2018-11-16
Legal Object – E72 is subject to – P104 Right – E30 CIDOC CRM 2018-11-16
Man-Made Thing – E71 was intended for – P103 Type – E55 CIDOC CRM 2018-11-16
Man-Made Thing – E71 has title – P102 Title – E35 CIDOC CRM 2018-11-16
Thing – E70 had as general use – P101 Type – E55 CIDOC CRM 2018-11-16
Death – E69 (0,n) was death of – P100 (0,1) Person – E21 CIDOC CRM 2019-12-27
Dissolution – E68 (1,n) dissolved – P99 (0,1) Group – E74 CIDOC CRM 2018-11-16
Birth – E67 (1,1) brought into life – P98 (1,1) Person – E21 CIDOC CRM 2019-12-27
Birth – E67 (0,n) from father – P97 (1,n) Person – E21 CIDOC CRM 2019-10-15
Birth – E67 (0,n) by mother – P96 (1,1) Person – E21 CIDOC CRM 2018-11-16
Formation – E66 (1,1) has formed – P95 (1,n) Group – E74 CIDOC CRM 2020-01-31
Creation – E65 has created – P94 Conceptual Object – E28 CIDOC CRM 2018-11-16
End of Existence – E64 took out of existence – P93 Persistent Item – E77 CIDOC CRM 2018-11-16
Beginning of Existence – E63 brought into existence – P92 Persistent Item – E77 CIDOC CRM 2018-11-16
Dimension – E54 has unit – P91 Measurement Unit – E58 CIDOC CRM 2018-11-16
Dimension – E54 has value – P90 Number – E60 CIDOC CRM 2018-11-16
Place – E53 falls within – P89 Place – E53 CIDOC CRM 2018-11-16
Place – E53 is identified by – P87 Place Appellation – E44 CIDOC CRM 2018-11-16
Time-Span – E52 falls within – P86 Time-Span – E52 CIDOC CRM 2018-11-16
Time-Span – E52 had at most duration – P84 Dimension – E54 CIDOC CRM 2018-11-16
Time-Span – E52 had at least duration – P83 Dimension – E54 CIDOC CRM 2018-11-16
Time-Span – E52 at some time within – P82 Time Primitive – E61 CIDOC CRM 2018-11-16
Time-Span – E52 ongoing throughout – P81 Time Primitive – E61 CIDOC CRM 2018-11-16
Time-Span – E52 end is qualified by – P80 String – E62 CIDOC CRM 2018-11-16
Time-Span – E52 beginning is qualified by – P79 String – E62 CIDOC CRM 2018-11-16
Time-Span – E52 is identified by – P78 Time Appellation – E49 CIDOC CRM 2018-11-16
Actor – E39 has contact point – P76 Contact Point – E51 CIDOC CRM 2018-11-16
Actor – E39 possesses – P75 Right – E30 CIDOC CRM 2018-11-16
Actor – E39 has current or former residence – P74 Place – E53 CIDOC CRM 2018-11-16
Linguistic Object – E33 has translation – P73 Linguistic Object – E33 CIDOC CRM 2018-11-16
Linguistic Object – E33 has language – P72 Language – E56 CIDOC CRM 2018-11-16
Authority Document – E32 lists – P71 CRM Entity – E1 CIDOC CRM 2018-11-16
Document – E31 documents – P70 CRM Entity – E1 CIDOC CRM 2018-11-16
Design or Procedure – E29 is associated with – P69 Design or Procedure – E29 CIDOC CRM 2018-11-16
Design or Procedure – E29 foresees use of – P68 Material – E57 CIDOC CRM 2018-11-16
Propositional Object – E89 refers to – P67 CRM Entity – E1 CIDOC CRM 2018-11-16
Physical Man-Made Thing – E24 shows visual item – P65 Visual Item – E36 CIDOC CRM 2018-11-16
Physical Man-Made Thing – E24 depicts – P62 CRM Entity – E1 CIDOC CRM 2018-11-16
Physical Thing – E18 has section – P59 Place – E53 CIDOC CRM 2018-11-16
Physical Thing – E18 has section definition – P58 Section Definition – E46 CIDOC CRM 2018-11-16
Physical Object – E19 has number of parts – P57 Number – E60 CIDOC CRM 2018-11-16
Physical Object – E19 bears feature – P56 Physical Feature – E26 CIDOC CRM 2018-11-16
Physical Object – E19 has current location – P55 Place – E53 CIDOC CRM 2018-11-16
Physical Object – E19 has current permanent location – P54 Place – E53 CIDOC CRM 2018-11-16
Physical Thing – E18 has former or current location – P53 Place – E53 CIDOC CRM 2018-11-16
Physical Thing – E18 has current owner – P52 Actor – E39 CIDOC CRM 2018-11-16
Physical Thing – E18 has former or current owner – P51 Actor – E39 CIDOC CRM 2018-11-16
Physical Thing – E18 has current keeper – P50 Actor – E39 CIDOC CRM 2018-11-16
Physical Thing – E18 has former or current keeper – P49 Actor – E39 CIDOC CRM 2018-11-16
CRM Entity – E1 has preferred identifier – P48 Identifier – E42 CIDOC CRM 2018-11-16
Physical Thing – E18 is composed of – P46 Physical Thing – E18 CIDOC CRM 2018-11-16
Physical Thing – E18 consists of – P45 Material – E57 CIDOC CRM 2018-11-16
Physical Thing – E18 has condition – P44 Condition State – E3 CIDOC CRM 2018-11-16
Thing – E70 has dimension – P43 Dimension – E54 CIDOC CRM 2018-11-16
Type Assignment – E17 assigned – P42 Type – E55 CIDOC CRM 2018-11-16
Type Assignment – E17 classified – P41 CRM Entity – E1 CIDOC CRM 2018-11-16
Measurement – E16 observed dimension – P40 Dimension – E54 CIDOC CRM 2018-11-16
Measurement – E16 measured – P39 CRM Entity – E1 CIDOC CRM 2018-11-16
Identifier Assignment – E15 deassigned – P38 Identifier – E42 CIDOC CRM 2018-11-16
Identifier Assignment – E15 assigned – P37 Identifier – E42 CIDOC CRM 2018-11-16
Condition Assessment – E14 has identified – P35 Condition State – E3 CIDOC CRM 2018-11-16
Condition Assessment – E14 concerned – P34 Physical Thing – E18 CIDOC CRM 2018-11-16
Activity – E7 used specific technique – P33 Design or Procedure – E29 CIDOC CRM 2018-11-16
Activity – E7 used general technique – P32 Type – E55 CIDOC CRM 2018-11-16
Modification – E11 has modified – P31 Physical Man-Made Thing – E24 CIDOC CRM 2018-11-16
Transfer of Custody – E10 transferred custody of – P30 Physical Thing – E18 CIDOC CRM 2018-11-16
Transfer of Custody – E10 custody received by – P29 Actor – E39 CIDOC CRM 2018-11-16
Transfer of Custody – E10 custody surrendered by – P28 Actor – E39 CIDOC CRM 2018-11-16
Move – E9 moved from – P27 Place – E53 CIDOC CRM 2018-11-16
Move – E9 moved to – P26 Place – E53 CIDOC CRM 2018-11-16
Move – E9 moved – P25 Physical Object – E19 CIDOC CRM 2018-11-16
Acquisition – E8 transferred title of – P24 Physical Thing – E18 CIDOC CRM 2018-11-16
Acquisition – E8 transferred title from – P23 Actor – E39 CIDOC CRM 2018-11-16
Acquisition – E8 transferred title to – P22 Actor – E39 CIDOC CRM 2018-11-16
Activity – E7 had general purpose – P21 Type – E55 CIDOC CRM 2018-11-16
Activity – E7 had specific purpose – P20 Event – E5 CIDOC CRM 2018-11-16
Activity – E7 was intended use of – P19 Man-Made Thing – E71 CIDOC CRM 2018-11-16
Activity – E7 was motivated by – P17 CRM Entity – E1 CIDOC CRM 2018-11-16
Activity – E7 used specific object – P16 Thing – E70 CIDOC CRM 2018-11-16
Activity – E7 was influenced by – P15 CRM Entity – E1 CIDOC CRM 2018-11-16
Activity – E7 carried out by – P14 Actor – E39 CIDOC CRM 2018-11-16
Destruction – E6 destroyed – P13 Physical Thing – E18 CIDOC CRM 2018-11-16
Event – E5 occurred in the presence of – P12 Persistent Item – E77 CIDOC CRM 2018-11-16
Event – E5 had participant – P11 Actor – E39 CIDOC CRM 2018-11-16
Spacetime Volume – E92 falls within – P10 Spacetime Volume – E92 CIDOC CRM 2018-11-16
Period – E4 consists of – P9 Period – E4 CIDOC CRM 2018-11-16
Period – E4 (0,n) took place on or within – P8 (0,n) Physical Thing – E18 CIDOC CRM 2019-12-10
Period – E4 took place at – P7 Place – E53 CIDOC CRM 2018-11-16
Condition State – E3 (0,n) consists of – P5 (0,1) Condition State – E3 CIDOC CRM 2018-11-16
Temporal Entity – E2 (1,n) has time-span – P4 (1,1) Time-Span – E52 CIDOC CRM 2019-03-25
CRM Entity – E1 (0,n) has note – P3 (0,1) String – E62 CIDOC CRM 2018-11-16
CRM Entity – E1 (0,n) has type – P2 (0,n) Type – E55 CIDOC CRM 2018-11-16
CRM Entity – E1 (0,n) is identified by – P1 (0,n) Appellation – E41 CIDOC CRM 2018-11-16