http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure
Scope note:
This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing.
Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 has association with (is associated with)..
Designs or procedures can be seen as one of the following:
1. A schema for the activities it describes
2. A schema of the products that result from their application.
3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci's famous plans for flying machines.
Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product.
Examples:
- the ISO standardisation procedure
- the musical notation of Beethoven's "Ode to Joy"
- the architectural drawings for the Kölner Dom in Cologne, Germany
- The drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan
In First Order Logic:
E29(x) ⊃ E73(x)
Instances of crm:E29_Design_or_Procedure can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class crm:E29_Design_or_Procedure | |||
| crm:P33i_was_used_by | owl:ObjectProperty | crm:E7_Activity | |
| crm:P68_foresees_use_of | owl:ObjectProperty | Scope note: This property identifies an E57 Material foreseeen to be used by an E29 Design or Procedure. E29 Designs and procedures commonly foresee the use of particular E57 Materials. The fabrication of adobe bricks, for example, requires straw, clay and water. This property enables this to be documented. This property is not intended for the documentation of E57 Materials that were used on a particular occasion when an instance of E29 Design or Procedure was executed. Examples: - procedure for soda glass manufacture (E29) foresees use of soda (E57) In First Order Logic: P68(x,y) ⊃ E29(x) P68(x,y) ⊃ E57(y) P68(x,y) ⊃ P67(x,y) | crm:E57_Material |
| crm:P69_has_association_with | owl:ObjectProperty | 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)'. In First Order Logic: P69 (x,y) ⊃ E29(x) P69 (x,y) ⊃ E29(y) P69(x,y,z) ⊃ [P69(x,y) ∧ E55(z)] P69(x,y) ⊃P69(y,x) Properties: P69.1 has type: E55 Type | crm:E29_Design_or_Procedure |
| crm:P69i_is_associated_with | owl:ObjectProperty | crm:E29_Design_or_Procedure | |
| From class crm:E73_Information_Object | |||
| crm:P165_incorporates | owl:ObjectProperty | Scope note: This property associates an instance of E73 Information Object with an instance of E90 Symbolic Object (or any of its subclasses) that was included in it. This property makes it possible to recognise the autonomous status of the incorporated signs, which were created in a distinct context, and can be incorporated in many distinct self-contained expressions, and to highlight the difference between structural and accidental whole-part relationships between conceptual entities. It accounts for many cultural facts that are quite frequent and significant: the inclusion of a poem in an anthology, the re-use of an operatic aria in a new opera, the use of a reproduction of a painting for a book cover or a CD booklet, the integration of textual quotations, the presence of lyrics in a song that sets those lyrics to music, the presence of the text of a play in a movie based on that play, etc. In particular, this property allows for modelling relationships of different levels of symbolic specificity, such as the natural language words making up a particular text, the characters making up the words and punctuation, the choice of fonts and page layout for the characters. A digital photograph of a manuscript page incorporates the text of the manuscript page Examples: - The content of Charles-Moïse Briquet’s ‘Les Filigranes: dictionnaire historique des marques du papier’ (E32) P165 incorporates the visual aspect of the watermark used around 1358-61 by some Spanish papermaker(s) and identified as ‘Briquet 4019’ (E37) - The visual content of Jacopo Amigoni’s painting known as ‘The Singer Farinelli and friends’ (E38) P165 incorporates the musical notation of Farinelli’s musical work entitled ‘La Partenza’ (E73) - The visual content of Nicolas Poussin’s painting entitled ‘Les Bergers d’Arcadie’ (E38) P165 incorporates the Latin phrase ‘Et in Arcadia ego’ (E33) | crm:E90_Symbolic_Object |
| From class crm:E89_Propositional_Object | |||
| crm:P129_is_about | owl:ObjectProperty | Scope note: This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. This differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of an E89 Propositional Object. Examples: - The text entitled 'Reach for the sky' (E33) is about Douglas Bader (E21) In First Order Logic: P129(x,y) ⊃ E89(x) P129(x,y) ⊃ E1(y) P129(x,y) ⊃ P67(x,y) | crm:E1_CRM_Entity |
| crm:P148_has_component | owl:ObjectProperty | Scope note: This property associates an instance of E89 Propositional Object with a structural part of it that is by itself an instance of E89 Propositional Object. Examples: - Dante's "Divine Comedy" (E89) has component Dante's "Hell" (E89) In First Order Logic: P148(x,y) ⊃ E89(x) P148(x,y) ⊃ E89(y) | crm:E89_Propositional_Object |
| crm:P148i_is_component_of | owl:ObjectProperty | crm:E89_Propositional_Object | |
| crm:P67_refers_to | owl:ObjectProperty | Scope note: This property documents that an E89 Propositional Object makes a statement about an instance of E1 CRM Entity. P67 refers to (is referred to by) has the P67.1 has type link to an instance of E55 Type. This is intended to allow a more detailed description of the type of reference. This differs from P129 is about (is subject of), which describes the primary subject or subjects of the E89 Propositional Object. Examples: - the eBay auction listing for 4 July 2002 (E73) refers to silver cup 232 (E22) has type item for sale (E55) In First Order Logic: P67(x,y) ⊃ E89(x) P67(x,y) ⊃ E1(y) P67(x,y,z) ⊃ [P67(x,y) ∧ E55(z)] Properties: P67.1 has type: E55 Type | crm:E1_CRM_Entity |
| From class crm:E28_Conceptual_Object | |||
| crm:P149_is_identified_by | owl:ObjectProperty | Scope note: This property identifies an instance of E28 Conceptual Object using an instance of E75 Conceptual Object Appellation. Examples: - The German edition of the CIDOC CRM (E73) is identified by ISBN 978-3-00-030907-6 (E75) In First Order Logic: P149(x,y) ⊃ E28(x) P149(x,y) ⊃ E75(y) P149(x,y) ⊃ P1(x,y) | crm:E75_Conceptual_Object_Appellation |
| crm:P94i_was_created_by | owl:ObjectProperty | crm:E65_Creation | |
| From class crm:E71_Man-Made_Thing | |||
| crm:P102_has_title | owl:ObjectProperty | Scope note: This property describes the E35 Title applied to an instance of E71 Man-Made Thing. The E55 Type of Title is assigned in a sub property. The P102.1 has type property of the P102 has title (is title of) property enables the relationship between the Title and the thing to be further clarified, for example, if the Title was a given Title, a supplied Title etc. It allows any man-made material or immaterial thing to be given a Title. It is possible to imagine a Title being created without a specific object in mind. Examples: - the first book of the Old Testament (E33) has title "Genesis" (E35) has type translated (E55) In First Order Logic: P102(x,y) ⊃ E71(x) P102(x,y) ⊃ E35(y) P102(x,y,z) ⊃ [P102(x,y) ∧ E55(z)] P102(x,y) ⊃ P1(x,y) Properties: P102.1 has type: E55 Type | crm:E35_Title |
| crm:P103_was_intended_for | owl:ObjectProperty | Scope note: This property links an instance of E71 Man-Made Thing to an E55 Type of usage. It creates a property between specific man-made things, both physical and immaterial, to Types of intended methods and techniques of use. Note: A link between specific man-made things and a specific use activity should be expressed using P19 was intended use of (was made for). Examples: - this plate (E22) was intended for being destroyed at wedding reception (E55) In First Order Logic: P103(x,y) ⊃ E71(x) P103(x,y) ⊃ E55(y) | crm:E55_Type |
| crm:P19i_was_made_for | owl:ObjectProperty | crm:E7_Activity | |
| From class crm:E70_Thing | |||
| crm:P101_had_as_general_use | owl:ObjectProperty | Scope note: This property links an instance of E70 Thing to an E55 Type of usage. It allows the relationship between particular things, both physical and immaterial, and general methods and techniques of use to be documented. Thus it can be asserted that a baseball bat had a general use for sport and a specific use for threatening people during the Great Train Robbery. Examples: - Tony Gill's Ford Mustang (E22) had as general use transportation (E55) In First Order Logic: P102(x,y) ⊃ E71(x) P102(x,y) ⊃ E35(y) P102(x,y,z) ⊃ [P102(x,y) ∧ E55(z)] P102(x,y) ⊃ P1(x,y) | crm:E55_Type |
| crm:P130_shows_features_of | owl:ObjectProperty | Scope note: This property generalises the notions of "copy of" and "similar to" into a dynamic, asymmetric relationship, where the domain expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. It is a shortcut of P15 was influenced by (influenced) in a creation or production, if such a reason for the similarity can be verified. Moreover it expresses similarity in cases that can be stated between two objects only, without historical knowledge about its reasons. Examples: - the Parthenon Frieze on the Acropolis in Athens (E22) shows features of the Original Parthenon Frieze in the British museum (E22). Kind of similarity: Copy (E55) In First Order Logic: P130 (x,y) ⊃ E70(x) P130 (x,y) ⊃ E70(y) P130(x,y,z) ⊃ [P130(x,y) ∧ E55(z)] P130(x,y) ⊃ P130(y,x) Properties: P130.1 kind of similarity: E55 Type | crm:E70_Thing |
| crm:P130i_features_are_also_found_on | owl:ObjectProperty | crm:E70_Thing | |
| crm:P16i_was_used_for | owl:ObjectProperty | crm:E7_Activity | |
| crm:P43_has_dimension | owl:ObjectProperty | Scope note: This property records a E54 Dimension of some E70 Thing. It is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom. An instance of E54 Dimension is specific to an instance of E70 Thing. Examples: - silver cup 232 (E22) has dimension height of silver cup 232 (E54) has unit (P91) mm (E58), has value (P90) 224 (E60) In First Order Logic: P43(x,y) ⊃ E70(x) P43(x,y) ⊃ E54(y) | crm:E54_Dimension |
| From class crm:E77_Persistent_Item | |||
| crm:P123i_resulted_from | owl:ObjectProperty | crm:E81_Transformation | |
| crm:P124i_was_transformed_by | owl:ObjectProperty | crm:E81_Transformation | |
| crm:P12i_was_present_at | owl:ObjectProperty | crm:E5_Event | |
| crm:P92i_was_brought_into_existence_by | owl:ObjectProperty | crm:E63_Beginning_of_Existence | |
| crm:P93i_was_taken_out_of_existence_by | owl:ObjectProperty | crm:E64_End_of_Existence | |
| From class crm:E1_CRM_Entity | |||
| crm:P3_has_note | owl:DatatypeProperty | Scope note: This property is a container for all informal descriptions about an object that have not been expressed in terms of CRM constructs. In particular it captures the characterisation of the item itself, its internal structures, appearance etc. Like property P2 has type (is type of), this property is a consequence of the restricted focus of the CRM. The aim is not to capture, in a structured form, everything that can be said about an item; indeed, the CRM formalism is not regarded as sufficient to express everything that can be said. Good practice requires use of distinct note fields for different aspects of a characterisation. The P3.1 has type property of P3 has note allows differentiation of specific notes, e.g. "construction", "decoration" etc. An item may have many notes, but a note is attached to a specific item. Examples: - coffee mug - OXCMS:1983.1.1 (E19) has note "chipped at edge of handle" (E62) has type Condition (E55) In First Order Logic: P3(x,y) ⊃ E1(x) P3(x,y) ⊃ E62(y) P3(x,y,z) ⊃ [P3(x,y) ∧ E55(z)] Properties: P3.1 has type: E55 Type | owl:Thing |
| crm:P129i_is_subject_of | owl:ObjectProperty | crm:E89_Propositional_Object | |
| crm:P136i_supported_type_creation | owl:ObjectProperty | crm:E83_Type_Creation | |
| crm:P137_exemplifies | owl:ObjectProperty | Scope note: This property allows an item to be declared as a particular example of an E55 Type or taxon The P137.1 in the taxonomic role property of P137 exemplifies (is exemplified by) allows differentiation of taxonomic roles. The taxonomic role renders the specific relationship of this example to the Type, such as "prototypical", "archetypical", "lectotype", etc. The taxonomic role "lectotype" is not associated with the Type Creation (E83) itself, but selected in a later phase. Examples: - Object BM000098044 of the Clayton Herbarium (E20) exemplifies Spigelia marilandica (L.) L. (E55) in the taxonomic role lectotype In First Order Logic: P137(x,y) ⊃ E1(x) P137(x,y) ⊃ E55(y) P137(x,y,z) ⊃ [P137(x,y) ∧ E55(z)] P137(x,y) ⊃ P2(x,y) Properties: P137.1 in the taxonomic role: E55 Type | crm:E55_Type |
| crm:P138i_has_representation | owl:ObjectProperty | crm:E36_Visual_Item | |
| crm:P140i_was_attributed_by | owl:ObjectProperty | crm:E13_Attribute_Assignment | |
| crm:P141i_was_assigned_by | owl:ObjectProperty | crm:E13_Attribute_Assignment | |
| crm:P15i_influenced | owl:ObjectProperty | crm:E7_Activity | |
| crm:P17i_motivated | owl:ObjectProperty | crm:E7_Activity | |
| crm:P1_is_identified_by | owl:ObjectProperty | Scope note: This property describes the naming or identification of any real world item by a name or any other identifier. This property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment. Examples: - the capital of Italy (E53) is identified by "Rome" (E48) - text 25014-32 (E33) is identified by "The Decline and Fall of the Roman Empire" (E35) In First Order Logic: P1(x,y) ⊃ E1(x) P1(x,y) ⊃ E41(y) | crm:E41_Appellation |
| crm:P2_has_type | owl:ObjectProperty | Scope note: This property allows sub typing of CRM entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus. The CRM is intended to focus on the high-level entities and relationships needed to describe data structures. Consequently, it does not specialise entities any further than is required for this immediate purpose. However, entities in the isA hierarchy of the CRM may by specialised into any number of sub entities, which can be defined in the E55 Type hierarchy. E51 Contact Point, for example, may be specialised into "e-mail address", "telephone number", "post office box", "URL" etc. none of which figures explicitly in the CRM hierarchy. Sub typing obviously requires consistency between the meaning of the terms assigned and the more general intent of the CRM entity in question. Examples: - "enquiries@cidoc-crm.org" (E51) has type e-mail address (E55) In First Order Logic: P2(x,y) ⊃ E1(x) P2(x,y) ⊃ E55(y) | crm:E55_Type |
| crm:P39i_was_measured_by | owl:ObjectProperty | crm:E16_Measurement | |
| crm:P41i_was_classified_by | owl:ObjectProperty | crm:E17_Type_Assignment | |
| crm:P62i_is_depicted_by | owl:ObjectProperty | crm:E24_Physical_Man-Made_Thing | |
| crm:P67i_is_referred_to_by | owl:ObjectProperty | crm:E89_Propositional_Object | |
| crm:P70i_is_documented_in | owl:ObjectProperty | crm:E31_Document | |
| crm:P71i_is_listed_in | owl:ObjectProperty | crm:E32_Authority_Document | |
| From class crm:E90_Symbolic_Object | |||
| crm:P106_is_composed_of | owl:ObjectProperty | Scope note: This property associates an instance of E90 Symbolic Object with a part of it that is by itself an instance of E90 Symbolic Object, such as fragments of texts or clippings from an image. Examples: - This Scope note P106 (E33) is composed of fragments of texts (E33) - 'recognizable' P106 (E90) is composed of 'ecognizabl' (E90) In First Order Logic: P106(x,y) ⊃ E90(x) P106(x,y) ⊃ E90(y) | crm:E90_Symbolic_Object |
| crm:P106i_forms_part_of | owl:ObjectProperty | crm:E90_Symbolic_Object | |
| crm:P128i_is_carried_by | owl:ObjectProperty | crm:E24_Physical_Man-Made_Thing | |
| crm:P142i_was_used_in | owl:ObjectProperty | crm:E15_Identifier_Assignment | |
| From class crm:E72_Legal_Object | |||
| crm:P104_is_subject_to | owl:ObjectProperty | Scope note: This property links a particular E72 Legal Object to the instances of E30 Right to which it is subject. The Right is held by an E39 Actor as described by P75 possesses (is possessed by). Examples: - Beatles back catalogue (E72) is subject to reproduction right on Beatles back catalogue (E30) In First Order Logic: P104(x,y) ⊃ E72(x) P104(x,y) ⊃ E30(y) | crm:E30_Right |
| crm:P105_right_held_by | owl:ObjectProperty | Scope note: This property identifies the E39 Actor who holds the instances of E30 Right to an E72 Legal Object. It is a superproperty of P52 has current owner (is current owner of) because ownership is a right that is held on the owned object. P105 right held by (has right on) is a shortcut of the fully developed path from E72 Legal Object through P104 is subject to (applies to), E30 Right, P75 possesses (is possessed by) to E39 Actor. Examples: - Beatles back catalogue (E73) right held by Michael Jackson (E21) In First Order Logic: P105(x,y) ⊃ E72(x) P105(x,y) ⊃ E39(y) | crm:E39_Actor |
| From class owl:Thing | |||
| crm:P14i_performed | owl:ObjectProperty | crm:E7_Activity | |
| crm:P165i_is_incorporated_in | owl:ObjectProperty | owl:Thing | |
| crm:P22i_acquired_title_through | owl:InverseFunctionalProperty | crm:E8_Acquisition | |
| crm:P23i_surrendered_title_through | owl:ObjectProperty | crm:E8_Acquisition | |
| crm:P28i_surrendered_custody_through | owl:ObjectProperty | crm:E10_Transfer_of_Custody | |
| crm:P29i_received_custody_through | owl:ObjectProperty | crm:E10_Transfer_of_Custody | |
| crm:P48_has_preferred_identifier | owl:ObjectProperty | Scope note: This property records the preferred E42 Identifier that was used to identify an instance of E1 CRM Entity at the time this property was recorded. More than one preferred identifier may have been assigned to an item over time. Use of this property requires an external mechanism for assigning temporal validity to the respective CRM instance. P48 has preferred identifier (is preferred identifier of), is a shortcut for the path from E1 CRM Entity through P140 assigned attribute to (was attributed by), E15 Identifier Assignment, P37 assigned (was assigned by) to E42 Identifier. The fact that an identifier is a preferred one for an organisation can be better expressed in a context independent form by assigning a suitable E55 Type to the respective instance of E15 Identifier Assignment using the P2 has type property. Examples: - the pair of Lederhosen donated by Dr Martin Doerr (E22) has preferred identifier "OXCMS:2001.1.32" (E42) In First Order Logic: P48(x,y) ⊃ E1(x) P48(x,y) ⊃ E42(y) P48(x,y) ⊃ P1(x,y) | crm:E42_Identifier |
| crm:P50i_is_current_keeper_of | owl:ObjectProperty | crm:E18_Physical_Thing | |
| crm:P52i_is_current_owner_of | owl:ObjectProperty | crm:E18_Physical_Thing | |
@prefix crm: <http://www.cidoc-crm.org/cidoc-crm/> .
@prefix ecrm: <http://erlangen-crm.org/current/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
crm:E29_Design_or_Procedure a owl:Class ;
rdfs:label "E29 Design or Procedure"@en ;
rdfs:comment """Scope note:
This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing.
Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 has association with (is associated with)..
Designs or procedures can be seen as one of the following:
1. A schema for the activities it describes
2. A schema of the products that result from their application.
3. An independent intellectual product that may have never been applied, such as Leonardo da Vinci's famous plans for flying machines.
Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product.
Examples:
- the ISO standardisation procedure
- the musical notation of Beethoven's "Ode to Joy"
- the architectural drawings for the Kölner Dom in Cologne, Germany
- The drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan
In First Order Logic:
E29(x) ⊃ E73(x)"""@en ;
rdfs:subClassOf crm:E73_Information_Object ;
owl:equivalentClass ecrm:E29_Design_or_Procedure ;
skos:notation "E29"^^xsd:string .