Subclass of:

• crm:E89 Propositional Object

Scope note:

This class comprises specifications of projected creative activities towards the CC2 Realization of a creative work. It details guidelines and constraints that downstream and upstream creative activities should comply with, according to a documented instance of CC5 Formulation. The specified constraints can be instantiated on the level of kinds of processes, items or qualities and quantities involved in the action. The qualities specified here should be considered to stand as valid constraints on downstream and potentially upstream creative activities (CC14 Programme Conception, CC15 Design Conception, CC16 Realization Planning) within the context of an ongoing CC9 Oeuvre, which can be used as a check of conformity between desired and delivered outcomes ranging across instances of CC5 Formulation subtypes (i.e., CC6 Programme, CC1 Model and CC4 Realization Plan) as well as the act of CC2 Realization itself, unless a newer instance of CC5 Formulation is created to supersede.

An instance of an expected kind of outcome in terms of object, e.g. design or building, is typically implied in most instances of CC12 Event Trigger Template and should be documented via an instance of CC11 Object Trigger Template. 

Examples:

• The analytic description of the evental stipulations contained in the programme (CC9) corresponding to the projective requirements (CC17) determined by the commission awarded to Rodin (E21) by the French Directorate of Fine Arts (E74), 6 August 1880, for a portal to be installed in the new Museum of Decorative Arts for the 1900 Paris World Fair (i.e., that it be completed by 1885 (E52), within a budget of 8000 French francs (E54), and so forth). (https://rodinmuseum.org/collection/about-auguste-rodin)
• The analytic description of the evental stipulations contained in the design concept (CC13) proposed by Daniel Libeskind, expressed in the winning proposal (CC1) for the competition to design the One World Trade Center (i.e., that it be completed within a given timeframe (E52) and budget (E54), that it be built in such and such a place (E53), and so forth. (https://untappedcities.com/2014/11/04/the-nyc-that-never-was-1-wtc-and-the-competition-for-the-world-trade-center-site/) 

In First Order Logic:

• CC12(x) ⇒ E89(x)

Outgoing properties:

• cpro:CP5 stipulates type of object outcome (is type of object outcome stipulated by) → crm:E55 Type
• cpro:CP6 stipulates event type (is type of event stipulated by) → crm:E55 Type
• cpro:CP7 stipulates actor type (is actor type stipulated by) → crm:E55 Type
• cpro:CP8 stipulates place (is place stipulated by) → crm:E53 Place
• cpro:CP9 stipulates time-span (is time-span stipulated by) → crm:E52 Time-Span
• cpro:CP10 stipulates actor (is actor stipulated by) → crm:E39 Actor
• cpro:CP11 stipulates equipment (is equipment stipulated by) → crm:E18 Physical Thing
• cpro:CP12 stipulates particular method (is particular method stipulated by) → crm:E29 Design or Procedure
• cpro:CP13 stipulates specific budget (is budget stipulated by) → crm:E54 Dimension
• cpro:CP14 stipulates object outcome (is object outcome stipulated by) → cpro:CC11 Object Trigger Template
• cpro:CP15 stipulates sub-event (is sub-event stipulated by) → cpro:CC12 Event Trigger Template

Incoming properties:

• cpro:CC5 Formulation → cpro:CP4 projects (was projected by)
• cpro:CC12 Event Trigger Template → cpro:CP15 stipulates sub-event (is sub-event stipulated by)