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 new instances of E71 Human-Made Thing or for shaping or guiding the execution of an instance of E7 Activity.

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): E29 Design or Procedure.

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 CIDOC CRM models a loose relationship between the plan and the respective product.

Examples:

the drawing on the folio 860 of the Codex Atlanticus from Leonardo da Vinci, 1486-1490, kept in the Biblioteca Ambrosiana in Milan

the ISO standardisation procedure

the musical notation for Beethoven’s “Ode to Joy” (Kershaw, 1999)

the architectural drawings for the Kölner Dom (Cologne Cathedral) in Cologne, Germany (Wolff, 1999)

In First Order Logic:

  • E29(x) ⇒ E73(x)

Scope notes

Examples

Additional notes

Identifier: E29

Official URI: http://www.cidoc-crm.org/cidoc-crm/E29_Design_or_Procedure
OntoME URI: https://ontome.net/ontology/c28

Labels

* : Standard label for this language

Namespace

Parent classes

Ancestor classes

Child and descendant classes

Related classes

Outgoing properties (this class is domain)

Outgoing properties (inherited from ancestors)

Incoming properties (this class is range)

Incoming properties (inherited from ancestors)

Profiles using this class

Linked classes graph

Use mouse wheel to zoom in/out.

Comments