Concept Search
Showing 2710 results:
P69 has association with
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
This property is transitive.
This property is transitive.
Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55)
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type ‘has part’ (E55). Preparation of parchment (E29) has association with stretching of skin (E29) has type ‘has part’ (E55). Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type ‘follows’ (E55).
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type 'follows' (E55)'.
Type: Property
Belongs to version: Version 6.2.2
P69 has association with
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55)
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type ‘has part’ (E55). Preparation of parchment (E29) has association with stretching of skin (E29) has type ‘has part’ (E55). Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type ‘follows’ (E55).
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type 'follows' (E55)'.
Type: Property
Belongs to version: Version 6.2
P69 has association with
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55)
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type ‘has part’ (E55). Preparation of parchment (E29) has association with stretching of skin (E29) has type ‘has part’ (E55). Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type ‘follows’ (E55).
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type 'follows' (E55)'.
Type: Property
Belongs to version: Version 6.0
P69 has association with
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
This property is transitive.
This property is transitive.
Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55)
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type ‘has part’ (E55). Preparation of parchment (E29) has association with stretching of skin (E29) has type ‘has part’ (E55). Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type ‘follows’ (E55).
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type 'follows' (E55)'.
Type: Property
Belongs to version: Version 6.2.1
P69 has association with
Quantification: many to many (0,n,0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type. The property is not transitive
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
Examples:
- The procedure for glass blowing (E29) has association with the procedure for glass heating (E29). (Brooks, 1973)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55).
- The preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type has part (E55).
- Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type follows (E55). (Poole and Reed, 1962)
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type follows (E55). (Loubiere, 1995)
Type: Property
Belongs to version: version 7.1.1
P69 has association with
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55)
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type ‘has part’ (E55). Preparation of parchment (E29) has association with stretching of skin (E29) has type ‘has part’ (E55). Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type ‘follows’ (E55).
Type: Property
Belongs to version: Version 5.1.2
P69 has association with
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property generalises relationships like whole-part, sequence, prerequisite or inspired by between instances of E29 Design or Procedure. Any instance of E29 Design or Procedure may be associated with other designs or procedures. The property is considered to be symmetrical unless otherwise indicated by P69.1 has type.
The P69.1 has type property of P69 has association with allows the nature of the association to be specified reading from domain to range; examples of types of association between instances of E29 Design or Procedure include: has part, follows, requires, etc.
The property can typically be used to model the decomposition of the description of a complete workflow into a series of separate procedures.
Examples:
- Procedure for glass blowing (E29) has association with procedure for glass heating (E29)
- The set of instructions for performing Macbeth in Max Reinhardt's production in 1916 in Berlin at Deutsches Theater (E29) has association with the scene design drawing by Ernst Stern reproduced at http://www.glopad.org/pi/fr/record/digdoc/1003814 (E29) has type has part (E55)
- Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type ‘has part’ (E55). Preparation of parchment (E29) has association with stretching of skin (E29) has type ‘has part’ (E55). Stretching of skin (E29) has association with soaking and unhairing of skin (E29) has type ‘follows’ (E55).
- The plan for reassembling the temples at Abu Simbel (E29) has association with the plan for storing and transporting the blocks (E29) has type 'follows' (E55)'.
Type: Property
Belongs to version: Version 6.1
P69 is associated with
Quantification: many to many (0,n,0,n)
Scope note:
This symmetric property describes the association of an E29 Design or Procedure with other Designs or Procedures.
Any instance of E29 Design or Procedure may be associated with other designs or procedures. The nature of the association may be whole-part, sequence, prerequisite etc. The property is assumed to be entirely reciprocal.
Examples:
- procedure for glass blowing (E29) is associated with procedure for glass heating (E29)
Type: Property
Belongs to version: Version 5.0.2
P69 is associated with
Quantification: many to many (0,n,0,n)
Scope note:
This symmetric property describes the association of an E29 Design or Procedure with other Designs or Procedures.
Any instance of E29 Design or Procedure may be associated with other designs or procedures. The nature of the association may be whole-part, sequence, prerequisite etc. The property is assumed to be entirely reciprocal.
Examples:
- procedure for glass blowing (E29) is associated with procedure for glass heating (E29)
Type: Property
Belongs to version: Version 4.1
P69 is associated with
Quantification: many to many (0,n,0,n)
Scope note:
This symmetric property describes the association of an E29 Design or Procedure with other Designs or Procedures.
Any instance of E29 Design or Procedure may be associated with other designs or procedures. The nature of the association may be whole-part, sequence, prerequisite etc. The property is assumed to be entirely reciprocal.
Examples:
- procedure for glass blowing (E29) is associated with procedure for glass heating (E29)
Type: Property
Belongs to version: Version 5.0.1
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations.
It is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place. E4 Period is a subclass of E92 Spacetime Volume. By the definition of P161 has spatial projection an instance of E4 Period takes place on all its spatial projections, that is, instances of E53 Place. Something happening at a given place can also be considered to happen at a larger place containing the first. For example, the assault on the Bastille July 14th 1789 took place in the area covered by Paris in 1789 but also in the area covered by France in 1789.
Examples:
- the period “Révolution française” (E4) took place at the area covered by France in 1789 (E53)
Type: Property
Belongs to version: Version 6.2.2
P7 took place at
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France”, the “Victorian” period, may be said to have taken place in “Britain” and its colonies, as well as other parts of Europe and north America.
A period can take place at multiple locations.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 5.0.2
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France”, the “Victorian” period, may be said to have taken place in “Britain” and its colonies, as well as other parts of Europe and north America.
A period can take place at multiple locations.
It is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. Describe in words.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 6.2
P7 took place at
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France”, the “Victorian” period, may be said to have taken place in “Britain” and its colonies, as well as other parts of Europe and north America.
A period can take place at multiple locations.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 4.1
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example the period “Révolution française” can be said to have taken place in “France” the “Victorian” period may be said to have taken place in “Britain” and its colonies as well as other parts of Europe and north America. A period can take place at multiple locations.
It is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within (contains) to E53 Place. Describe in words.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 6.2.1
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example the period “R?volution fran?aise” can be said to have taken place in “France” the “Victorian” period may be said to have taken place in “Britain” and its colonies as well as other parts of Europe and north America. A period can take place at multiple locations.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 6.0
P7 took place at
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related instance of E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations.
This property is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place. E4 Period is a subclass of E92 Spacetime Volume. By the definition of P161 has spatial projection an instance of E4 Period takes place on all its spatial projections, that is, instances of E53 Place. Something happening at a given place can also be considered to happen at a larger place containing the first. For example, the assault on the Bastille July 14th 1789 took place in the area covered by Paris in 1789 but also in the area covered by France in 1789.
Examples:
- The period “Révolution française” (E4) took place at the area covered by France in 1789 (E53). (Bertaud, 2004)
Type: Property
Belongs to version: version 7.1.1
P7 took place at
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France”, the “Victorian” period, may be said to have taken place in “Britain” and its colonies, as well as other parts of Europe and north America.
A period can take place at multiple locations.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 5.0.1
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period. The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7 took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example the period “Révolution française” can be said to have taken place in “France” the “Victorian” period may be said to have taken place in “Britain” and its colonies as well as other parts of Europe and north America. A period can take place at multiple locations.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 6.1
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related instance of E53 Place should be seen as a wider approximation of the geometric area within which the phenomena that characterise the period in question occurred, see below. P7took place at (witnessed) does not convey any meaning other than spatial positioning (frequently on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France in 1789”; the “Victorian” period may be said to have taken place in “Britain from 1837-1901” and its colonies, as well as other parts of Europe and North America. An instance of E4 Period can take place at multiple non-contiguous, non-overlapping locations.
This property is a shortcut of the more fully developed path from E4 Period through P161 has spatial projection, E53 Place, P89 falls within to E53 Place. E4 Period is a subclass of E92 Spacetime Volume. By the definition of P161 has spatial projection an instance of E4 Period takes place on all its spatial projections, that is, instances of E53 Place. Something happening at a given place can also be considered to happen at a larger place containing the first. For example, the assault on the Bastille July 14th 1789 took place in the area covered by Paris in 1789 but also in the area covered by France in 1789.
Examples:
- the period “Révolution française” (E4) took place at the area covered by France in 1789 (E53) (Bertaud, 2004)
Type: Property
Belongs to version: version 7.1
P7 took place at
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the spatial location of an instance of E4 Period.
The related E53 Place should be seen as an approximation of the geographical area within which the phenomena that characterise the period in question occurred. P7took place at (witnessed) does not convey any meaning other than spatial positioning (generally on the surface of the earth). For example, the period “Révolution française” can be said to have taken place in “France”, the “Victorian” period, may be said to have taken place in “Britain” and its colonies, as well as other parts of Europe and north America.
A period can take place at multiple locations.
Examples:
- the period “Révolution française” (E4) took place at France (E53)
Type: Property
Belongs to version: Version 5.1.2
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the CRM Entities documented as instances of E31 Document.
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement.
Examples:
- the British Museum catalogue (E31) documentsthe British Museum’s Collection (E78) (Franks, 1872) , (British Museum, 1922) (fictitious)
Type: Property
Belongs to version: version 7.1
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.2.2
P70 documents
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the CRM Entities documented by instances of E31 Document.
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense.
Examples:
- the British Museum catalogue (E31) documents the British Museum’s Collection (E78)
Type: Property
Belongs to version: Version 5.0.2
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.2
P70 documents
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the CRM Entities documented by instances of E31 Document.
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense.
Examples:
- the British Museum catalogue (E31) documents the British Museum’s Collection (E78)
Type: Property
Belongs to version: Version 4.1
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.0
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.2.1
P70 documents
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the CRM Entities documented as instances of E31 Document.
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CIDOC CRM class hierarchy. This property is intended for cases where a reference is regarded as making a proposition about reality. This may be of a documentary character, in the scholarly or scientific sense, or a more general statement.
Examples:
- The ‘Catalogue of the Greek coins of Arabia, Mesopotamia and Persia’ (E31) documents parts of the British Museum’s Collection (E78). (British Museum & Hill, 1922)
Type: Property
Belongs to version: version 7.1.1
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 5.1.2
P70 documents
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property describes the CRM Entities documented by instances of E31 Document.
Documents may describe any conceivable entity, hence the link to the highest-level entity in the CRM hierarchy. This property is intended for cases where a reference is regarded as being of a documentary character, in the scholarly or scientific sense.
Examples:
- the British Museum catalogue (E31) documents the British Museum’s Collection (E78)
Type: Property
Belongs to version: Version 5.0.1
P70 documents
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.1
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.1
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property associates an instance of E32 Authority Document, with an instance of E1 CRM Entity which it lists for reference purposes.
Examples:
- the Art & Architecture Thesaurus (E32) listsalcazars (E55) (http://vocab.getty.edu/page/aat/300006897)
Type: Property
Belongs to version: version 7.1
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.2.2
P71 lists
Quantification: many to many (0,n,0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E55 Type.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 5.0.2
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.2
P71 lists
Quantification: many to many (0,n,0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E55 Type.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 4.1
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.0
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 6.2.1
P71 lists
Quantification: many to many (0,n,0,n)
Scope note:
This property associates an instance of E32 Authority Document, with an instance of E1 CRM Entity which it lists for reference purposes.
Examples:
- The Art & Architecture Thesaurus (E32) lists alcazars (E55). (http://vocab.getty.edu/page/aat/300006897)
Type: Property
Belongs to version: version 7.1.1
P71 lists
Quantification: many to many (0,n:0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E1 CRM Entity.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 5.1.2
P71 lists
Quantification: many to many (0,n,0,n)
Scope note:
This property documents a source E32 Authority Document for an instance of an E55 Type.
Examples:
- the Art & Architecture Thesaurus (E32) lists alcazars (E55)
Type: Property
Belongs to version: Version 5.0.1
P72 has language
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 6.1
P72 has language
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56) (Perley, 2017)
Type: Property
Belongs to version: version 7.1
P72 has language
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 6.2.2
P72 has language
Quantification: many to many,necessary (0,n,0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 5.0.2
P72 has language
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 6.2
P72 has language
Quantification: many to many,necessary (0,n,0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 4.1
P72 has language
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 6.0
P72 has language
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 6.2.1
P72 has language
Quantification: many to many,necessary (1,n,0,n)
Scope note:
This property associates an instance(s) of E33 Linguistic Object with an instance of E56 Language in which it is, at least partially, expressed.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- The American Declaration of Independence (E33) has language 18th Century English (E56). (Perley, 2017)
Type: Property
Belongs to version: version 7.1.1
P72 has language
Quantification: many to many, necessary (1,n:0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 5.1.2
P72 has language
Quantification: many to many,necessary (0,n,0,n)
Scope note:
This property describes the E56 Language of an E33 Linguistic Object.
Linguistic Objects are composed in one or more human Languages. This property allows these languages to be documented.
Examples:
- the American Declaration of Independence (E33) has language 18th Century English (E56)
Type: Property
Belongs to version: Version 5.0.1
P73 has translation
Quantification: one to many (0,n:0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Subproperty of: E70 Thing. P130i features are also found on: E70 Thing
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 6.1
P73 has translation
Quantification: many to many (0,n:0,n)
Scope note:
This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A.
When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source.
This property is non-symmetric.
Subproperty of: E70 Thing. P130i features are also found on: E70 Thing
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33) (Surenne, 1840)
Type: Property
Belongs to version: version 7.1
P73 has translation
Quantification: one to many (0,n:0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
This property is transitive.
This property is transitive.
Subproperty of: E70 Thing. P130i features are also found on: E70 Thing
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 6.2.2
P73 has translation
Quantification: one to many (0,n,0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 5.0.2
P73 has translation
Quantification: one to many (0,n:0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Subproperty of: E70 Thing. P130i features are also found on: E70 Thing
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 6.2
P73 has translation
Quantification: one to many (0,n,0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 4.1
P73 has translation
Quantification: one to many (0,n:0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Subproperty of: E70 Thing. P130i features are also found on: E70 Thing
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 6.0
P73 has translation
Quantification: one to many (0,n:0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
This property is transitive.
This property is transitive.
Subproperty of: E70 Thing. P130i features are also found on: E70 Thing
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 6.2.1
P73 has translation
Quantification: many to many (0,n,0,n)
Scope note:
This property links an instance of E33 Linguistic Object (A), to another instance of E33 Linguistic Object (B) which is the translation of A.
When an instance of E33 Linguistic Object is translated into a new language a new instance of E33 Linguistic Object is created, despite the translation being conceptually similar to the source.
This property is non-symmetric.
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33). (Spiers & Surenne, 1854)
Type: Property
Belongs to version: version 7.1.1
P73 has translation
Quantification: one to many (0,n:0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 5.1.2
P73 has translation
Quantification: one to many (0,n,0,1)
Scope note:
This property describes the source and target of instances of E33Linguistic Object involved in a translation.
When a Linguistic Object is translated into a new language it becomes a new Linguistic Object, despite being conceptually similar to the source object.
Examples:
- “Les Baigneurs” (E33) has translation “The Bathers” (E33)
Type: Property
Belongs to version: Version 5.0.1
P74 has current or former residence
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 5.0.1
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 6.1
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: version 7.1
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 6.2.2
P74 has current or former residence
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 5.0.2
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 6.2
P74 has current or former residence
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 4.1
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 6.0
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 6.2.1
P74 has current or former residence
Quantification: many to many (0,n,0,n)
Scope note:
This property describes the current or former place of residence (an instance of E53 Place) of an instance of E39 Actor.
The residence may be either the place where the actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53). (Robinson, 2000)
Type: Property
Belongs to version: version 7.1.1
P74 has current or former residence
Quantification: many to many (0,n:0,n)
Scope note:
This property describes the current or former E53 Place of residence of an E39 Actor.
The residence may be either the Place where the Actor resides, or a legally registered address of any kind.
Examples:
- Queen Elizabeth II (E39) has current or former residence Buckingham Palace (E53)
Type: Property
Belongs to version: Version 5.1.2
P75 possesses
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 5.0.1
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 6.1
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30) (Raga, 2016)
Type: Property
Belongs to version: version 7.1
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 6.2.2
P75 possesses
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 5.0.2
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 6.2
P75 possesses
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 4.1
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 6.0
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 6.2.1
P75 possesses
Quantification: many to many (0,n,0,n)
Scope note:
This property associates an instance of E39 Actor to an instance of E30 Right over which the actor holds or has held a legal claim.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30). (Raga, 2016)
Type: Property
Belongs to version: version 7.1.1
P75 possesses
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies former or current instances of E30 Rights held by an E39 Actor.
Examples:
- Michael Jackson (E21) possesses Intellectual property rights on the Beatles’ back catalogue (E30)
Type: Property
Belongs to version: Version 5.1.2
P76 has contact point
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point bl.ric@rlg.org (E51)
Type: Property
Belongs to version: Version 5.0.1
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 6.1
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.
Examples:
- The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41)
Type: Property
Belongs to version: version 7.1
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 6.2.2
P76 has contact point
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 5.0.2
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 6.2
P76 has contact point
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point bl.ric@rlg.org (E51)
Type: Property
Belongs to version: Version 4.1
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 6.0
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 6.2.1
P76 has contact point
Quantification: many to many (0,n,0,n)
Scope note:
This property associates an instance of E39 Actor to an instance of E41 Appellation which a communication service uses to direct communications to this actor, such as an e-mail address, fax number, or postal address.
Examples:
- The Research Libraries Group, Inc. (RLG) (E74) has contact point “bl.ric@rlg.org” (E41)
Type: Property
Belongs to version: version 7.1.1
P76 has contact point
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E51 Contact Point of any type that provides access to an E39 Actor by any communication method, such as e-mail or fax.
Examples:
- RLG (E40) has contact point “bl.ric@rlg.org” (E51)
Type: Property
Belongs to version: Version 5.1.2
P78 is identified by
Quantification: many to many (0,n,0,n)
Scope note:
This property identifies an E52 Time-Span using an E49Time Appellation.
Examples:
- the time span 1926 to 1988 (E52) is identified by Showa (Japanese time appellation) (E49)
Type: Property
Belongs to version: Version 5.0.1
P78 is identified by
Quantification: many to many (0,n:0,n)
Scope note:
This property identifies an E52 Time-Span using an E49Time Appellation.
Examples:
- the time span 1926 to 1988 (E52) is identified by “Showa” (Japanese time appellation) (E49)
Type: Property
Belongs to version: Version 6.1