Design or Procedure – E29

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 for 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)

Scope Notes

Show Scope note Language Namespace
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 describes2. 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. en

Examples

Show Example Language Namespace
the ISO standardisation procedure the musical notation for 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 en WIP

Additional notes

Show Notes Language Namespace

Labels

Label Language Last updated
Entwurf oder Verfahren de 2018-06-22
Σχέδιο el 2018-06-22
Design or Procedure en 2018-06-22
Conception ou procédure fr 2018-06-22
Projeto ou Procedimento pt 2018-06-22
Проект или Процедура ru 2018-06-22
设计或程序 zh 2018-06-22

Namespace

Namespace URI Last updated
http://dataforhistory.org/imported_ontology/cidoc-crm/base/6/2/ 2019-03-22

Parent classes

Class identifier Justification Root namespace View association
Information Object – E73 http://dataforhistory.org/imported_ontology/cidoc-crm/base/

Ancestor classes

Class identifier Depth Root namespace
E1 CRM Entity 6 CIDOC CRM
E1 CRM Entity 7 CIDOC CRM
E1 CRM Entity 8 CIDOC CRM
E28 Conceptual Object 3 CIDOC CRM
E70 Thing 4 CIDOC CRM
E70 Thing 5 CIDOC CRM
E71 Man-Made Thing 4 CIDOC CRM
E72 Legal Object 3 CIDOC CRM
E77 Persistent Item 5 CIDOC CRM
E77 Persistent Item 6 CIDOC CRM
E89 Propositional Object 2 CIDOC CRM
E90 Symbolic Object 2 CIDOC CRM
Thing Thing 7 The OWL 2 SCHEMA vocabulary(OWL 2)
Thing Thing 8 The OWL 2 SCHEMA vocabulary(OWL 2)
Thing Thing 9 The OWL 2 SCHEMA vocabulary(OWL 2)
S15 Observable Entity 6 CRMsci: An Extension of CIDOC-CRM to support scientific observation
S15 Observable Entity 7 CRMsci: An Extension of CIDOC-CRM to support scientific observation

Childs and descendant classes

Class identifier Depth Root namespace
F25 Performance Plan 1 FRBRoo: Functional Requirements for Bibliographic Records
F34 KOS 1 FRBRoo: Functional Requirements for Bibliographic Records
F35 Nomen Use Statement 1 FRBRoo: Functional Requirements for Bibliographic Records
F36 Script Conversion 1 FRBRoo: Functional Requirements for Bibliographic Records
F43 Identifier Rule 1 FRBRoo: Functional Requirements for Bibliographic Records
SP4 Spatial Coordinate Reference System 1 CRMgeo: a Spatiotemporal Model
SP11 Temporal Reference System 1 CRMgeo: a Spatiotemporal Model
socE Activity Plan 1 CRMsoc. An extension of CIDOC CRM for capturing social documentation

Equivalent classes

Class identifier Root namespace

Outgoing properties (this class is domain)

Domain Property identifier Range Namespace
E29 Design or Procedure P68 foresees use of E57 Material CIDOC-CRM version 6.2
E29 Design or Procedure P69 is associated with E29 Design or Procedure CIDOC-CRM version 6.2

Outgoing properties (inherited from ancestors)

Domain Property identifier Range Namespace
E29 Design or Procedure (is a E1 CRM Entity) P1 is identified by E41 Appellation CIDOC-CRM version 6.2
E29 Design or Procedure (is a E1 CRM Entity) P2 has type E55 Type CIDOC-CRM version 6.2
E29 Design or Procedure (is a E1 CRM Entity) P3 has note E62 String CIDOC-CRM version 6.2
E29 Design or Procedure (is a E1 CRM Entity) P48 has preferred identifier E42 Identifier CIDOC-CRM version 6.2
E29 Design or Procedure (is a E1 CRM Entity) P137 exemplifies E55 Type CIDOC-CRM version 6.2
E29 Design or Procedure (is a E1 CRM Entity) geovP2 is mentioned in E28 Conceptual Object Geovistory ongoing
E29 Design or Procedure (is a E1 CRM Entity) L47 has comment E62 String CRMdig version 3.2
E29 Design or Procedure (is a E1 CRM Entity) L4 has preferred label E62 String CRMdig version 3.2
E29 Design or Procedure (is a E1 CRM Entity) L53 is not uniquely identified by E62 String CRMdig version 3.2
E29 Design or Procedure (is a E28 Conceptual Object) P149 is identified by E75 Conceptual Object Appellation CIDOC-CRM version 6.2
E29 Design or Procedure (is a E70 Thing) P43 has dimension E54 Dimension CIDOC-CRM version 6.2
E29 Design or Procedure (is a E70 Thing) P101 had as general use E55 Type CIDOC-CRM version 6.2
E29 Design or Procedure (is a E70 Thing) P130 shows features of E70 Thing CIDOC-CRM version 6.2
E29 Design or Procedure (is a E71 Man-Made Thing) P102 has title E35 Title CIDOC-CRM version 6.2
E29 Design or Procedure (is a E71 Man-Made Thing) P103 was intended for E55 Type CIDOC-CRM version 6.2
E29 Design or Procedure (is a E72 Legal Object) P104 is subject to E30 Right CIDOC-CRM version 6.2
E29 Design or Procedure (is a E72 Legal Object) P105 right held by E39 Actor CIDOC-CRM version 6.2
E29 Design or Procedure (is a E73 Information Object) P165 incorporates E90 Symbolic Object CIDOC-CRM version 6.2
E29 Design or Procedure (is a E89 Propositional Object) P67 refers to E1 CRM Entity CIDOC-CRM version 6.2
E29 Design or Procedure (is a E89 Propositional Object) P129 is about E1 CRM Entity CIDOC-CRM version 6.2
E29 Design or Procedure (is a E89 Propositional Object) P148 has component E89 Propositional Object CIDOC-CRM version 6.2
E29 Design or Procedure (is a E90 Symbolic Object) P106 is composed of E90 Symbolic Object CIDOC-CRM version 6.2
E29 Design or Procedure (is a Thing Thing) topObjectProperty Thing Thing The OWL 2 SCHEMA vocabulary(OWL 2)
E29 Design or Procedure (is a S15 Observable Entity) O12 has dimension (is dimension of) E54 Dimension CRMsci version 1.2.3

Incoming properties (this class is range)

Domain Property identifier Range Namespace
E7 Activity P33 used specific technique E29 Design or Procedure CIDOC-CRM version 6.2
E29 Design or Procedure P69 is associated with E29 Design or Procedure CIDOC-CRM version 6.2
F18 Serial Work R11 has issuing rule E29 Design or Procedure FRBRoo version 2.4

Incoming properties (inherited from ancestors)

Domain Property identifier Range Namespace
E1 CRM Entity geovP2 is mentioned in Design or Procedure – E29 (is a E28 Conceptual Object) Geovistory ongoing
E2 Temporal Entity histP1 involves Design or Procedure – E29 (is a E77 Persistent Item) Data for History ontology, v.0.1 ongoing
E5 Event P12 occurred in the presence of Design or Procedure – E29 (is a E77 Persistent Item) CIDOC-CRM version 6.2
E7 Activity P15 was influenced by Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E7 Activity P16 used specific object Design or Procedure – E29 (is a E70 Thing) CIDOC-CRM version 6.2
E7 Activity P17 was motivated by Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E7 Activity P19 was intended use of Design or Procedure – E29 (is a E71 Man-Made Thing) CIDOC-CRM version 6.2
E13 Attribute Assignment P140 assigned attribute to Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E13 Attribute Assignment P141 assigned Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E15 Identifier Assignment P142 used constituent Design or Procedure – E29 (is a E90 Symbolic Object) CIDOC-CRM version 6.2
E16 Measurement P39 measured Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E17 Type Assignment P41 classified Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E18 Physical Thing P128 carries Design or Procedure – E29 (is a E90 Symbolic Object) CIDOC-CRM version 6.2
E24 Physical Man-Made Thing P62 depicts Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E31 Document P70 documents Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E32 Authority Document P71 lists Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E36 Visual Item P138 represents Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E63 Beginning of Existence P92 brought into existence Design or Procedure – E29 (is a E77 Persistent Item) CIDOC-CRM version 6.2
E64 End of Existence P93 took out of existence Design or Procedure – E29 (is a E77 Persistent Item) CIDOC-CRM version 6.2
E65 Creation P94 has created Design or Procedure – E29 (is a E28 Conceptual Object) CIDOC-CRM version 6.2
E70 Thing P130 shows features of Design or Procedure – E29 (is a E70 Thing) CIDOC-CRM version 6.2
E73 Information Object P165 incorporates Design or Procedure – E29 (is a E90 Symbolic Object) CIDOC-CRM version 6.2
E81 Transformation P123 resulted in Design or Procedure – E29 (is a E77 Persistent Item) CIDOC-CRM version 6.2
E81 Transformation P124 transformed Design or Procedure – E29 (is a E77 Persistent Item) CIDOC-CRM version 6.2
E83 Type Creation P136 was based on Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E89 Propositional Object P129 is about Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E89 Propositional Object P148 has component Design or Procedure – E29 (is a E89 Propositional Object) CIDOC-CRM version 6.2
E89 Propositional Object P67 refers to Design or Procedure – E29 (is a E1 CRM Entity) CIDOC-CRM version 6.2
E90 Symbolic Object P106 is composed of Design or Procedure – E29 (is a E90 Symbolic Object) CIDOC-CRM version 6.2
histC1 Persistent item condition or characteristic histP4 pertainsTo Design or Procedure – E29 (is a E77 Persistent Item) Data for History ontology, v.0.1 ongoing
histC2 Geographical localisation histP12 isLocationOf Design or Procedure – E29 (is a E1 CRM Entity) Data for History ontology, v.0.1 ongoing
Thing Thing topObjectProperty Design or Procedure – E29 (is a Thing Thing) The OWL 2 SCHEMA vocabulary(OWL 2)
F13 Identifier R8 consists of Design or Procedure – E29 (is a E90 Symbolic Object) FRBRoo version 2.4
F31 Performance R66 included performed version of Design or Procedure – E29 (is a E89 Propositional Object) FRBRoo version 2.4
F35 Nomen Use Statement R38 refers to thema Design or Procedure – E29 (is a E1 CRM Entity) FRBRoo version 2.4
F40 Identifier Assignment R45 assigned to Design or Procedure – E29 (is a E1 CRM Entity) FRBRoo version 2.4
F51 Pursuit R59 had typical subject Design or Procedure – E29 (is a E1 CRM Entity) FRBRoo version 2.4
F52 Name Use Activity R63 named Design or Procedure – E29 (is a E1 CRM Entity) FRBRoo version 2.4
histC10 Appellation for language histP9 isAppellationOf Design or Procedure – E29 (is a E1 CRM Entity) Data for History ontology, v.0.1 ongoing
S4 Observation O16 observed value (value was observed by) Design or Procedure – E29 (is a E1 CRM Entity) CRMsci version 1.2.3
S4 Observation O8 observed (was observed by) Design or Procedure – E29 (is a S15 Observable Entity) CRMsci version 1.2.3
S6 Data Evaluation O11 described (was described by) Design or Procedure – E29 (is a S15 Observable Entity) CRMsci version 1.2.3
S21 Measurement O24 measured (was measured by) Design or Procedure – E29 (is a S15 Observable Entity) CRMsci version 1.2.3
socE Bond socP6 to Design or Procedure – E29 (is a E77 Persistent Item) CRMsoc version 0.1 ongoing
socE Activity Plan socP100 planned for Design or Procedure – E29 (is a E1 CRM Entity) CRMsoc version 0.1 ongoing
D2 Digitization Process L60 documents Design or Procedure – E29 (is a E1 CRM Entity) CRMdig version 3.2
D29 Annotation Object L43 annotates Design or Procedure – E29 (is a E1 CRM Entity) CRMdig version 3.2

Profiles using this class

Label Start date End date Last updated

Linked classes graph

Use mouse wheel to zoom in/out.

Comments