Skip to main content

User account menu

  • Log in
Home
CIDOC CRM

Cidoc Horizontal Menu

  • Home
    • About & Info
    • Use & Learn
    • Issues
    • Mappings
    • Compatible Models
    • Use Cases
    • Best Practices
  • Activities
  • Resources
  • Community
  • News

Issues

  • Short Intro
  • Issue Formulation
  • Issue Processing
  • CRM SIG archive

Choose a shortcut

Compatible models & Collaborations
Link to old CIDOC CRM website
Next meeting
Use cases
CIDOC CRM Tutorial
CIDOC CRM Website designs and logos 
CRM SIG mailing list
Editorial Suggestions
Site Support

 

P69 revision

214
2012-07-25
3 - Changes in the CIDOC CRM model
Done
2014-04-03

Posted by Patrick Le Boeuf, 25/7/2012

Also, I have a question about a property in CIDOC CRM. It is property P69 is associated with. This property is a symmetric property, both domain and range of which is E29 Design or Procedure. It is explicitly said to be symmetric in the CIDOC CRM definition, and its label reads the same in both domain-to-range and range-to-domain directions. It also has a property,P69.1 has type, which is said to "allow the nature of the association to be specified; examples of association between instances of E29 Design or Procedure include: whole-part, sequence, prerequisite, etc." However, the example for P69 does not include an example for P69.1. 

My question is: Since P69 is symmetric, if P69.1 specifies that the nature of the association is "whole-part", how do you recognize which design-or-procedure is the whole and which is the part? If it specifies that the nature of the association is "sequence", how to indicate which is the first and which is the second in the sequence? If it specifies that the nature of the association is "prerequisite", how is it possible to recognize, in a perfectly symmetric association, which of the two instances of E29 is the prerequisite of the other? It occurs to me right now that, if the association between two designs or procedures is of a "whole-part" nature, this might be better expressed through P148 has component (is component of) (inherited from E89). Would it not be better to delete the "whole-part" example in the scope note for P69?

In my paper, I use P69 between an instance of F25 Performance Plan and the content of a set model, which I regard as an instance of E29 Design or Procedure used for building the set, and I specify the nature of the association through P69.1 has type:E55 Type {instance = "scenery"}, which perhaps you'll deem wrong.
I don't think we can say that a performance plan "incorporates" (R14) the content of a model; what may be incorporated in the performance plan is the content of the scenery itself, but the model is, I think, more a design or procedure for building the scenery (or for making a costume).

The name of the property was changed to "P69 has association with (is associated with)". Martin Doerr will elaborate the scope note and Patrick Le Boeuf will write an example 

Amersfoort 20/11/2012

 


Example proposed by Patrick by email on 5/12/2012 


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 set design (E55) 
 


The SIG have decided to take from the shows feature of P130 and write the scope note of associates in design or procedure. Christian Emil Ore will write the scope note having workflows in mind. 

28th CRM-SIG meeting, Stockholm June 2013

 



Posted by Christian Emil in 15/10 




P69 has association with (is associated with) 

Domain: E29 Design or Procedure
Range: E29 Design or Procedure
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 the use ofP69.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 
link (E29) has type has part (E55)
* Preparation of parchment (E29) has association with soaking and unhairing of skin (E29) has type 'has part' T55 Type. 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).
Properties: P69.1 has type: E55 Type

Harmonize scope note of P130 "shows feature of" with P69. The scope note is accepted the examples need to be particular (CEO will look for examples) 
29th CRM-SIG meeting, Heraklion, October 2013

 

The crm-sig accepted the examples given by CEO 
30th CRM SIG meeting, Hague April 2014

THE MODEL

  • About & Info
  • Short Intro
  • Scope
  • Recommendations
  • References
  • Critics
  • Important Theories
  • Use&Learn
  • Short Intro
  • User Guidance
  • Methodology
  • Tutorials
  • Functional Overview
  • Last Official Release
  • Concept Search
  • Issues
  • Short Intro
  • Issue Formulation
  • Issue Processing
  • CRM SIG Archive
  • Mappings
  • Short Intro
  • Mapping Methods
  • Mapping Tools
  • Mapping Memory
  • Reports about Mappings
  • Compatible Models
  • Short Intro
  • Models
  • Use Cases
  • Short Intro
  • Use Cases

RESOURCES

  • Related Activities
  • Versions
  • References
  • Presentations
  • Technical Papers
  • Tutorials
  • Critics
  • Important Theories
  • Publications
  • Mappings
  • Compatible Models
  • Translations
  • Best Practices
  • Meeting Contributions
  • Minutes
  • Issues
  • CRM SIG Archive
  • Meeting Contributions

ACTIVITIES

  • Short Intro
  • SIG Meetings
  • Minutes
  • Workshops
  • Related Activities

PEOPLE

  • Short Intro
  • Related Stakeholders
  • SIG Members
  • Hosts

NEWS

HOME

 

 

Copyright © 2025 Company Name - All rights reserved

Developed & Designed by Alaa Haddad