Relation HAS-PARAMETER-SLOT

• Defined in theory: Components-with-constraints
• Source code: components-with-constraints.lisp

Slots on this relation:

Documentation:

A component has an parameter if the parameter value is given by a unary function, called an parameter-slot, that is defined for that component. Calling a slot an parameter-slot means that it is a design parameter: it will need to be assigned a value and may be mentioned in constraints. The parameter slot must have a value.

Instance-Of: Relation

Arity: 2

Domain: Component

Range: Parameter-slot

Other Related Axioms:

(=> (Has-Parameter-Slot $X $Y) (Parameter-Slot $Y))

(=> (Has-Parameter-Slot $X $Y) (Component $X))

(=> (Has-Parameter-Slot ?Component ?Parameter-Slot)
    (Value-Cardinality ?Component ?Parameter-Slot 1))

(<=> (Parameter-Slot-Of $Arg1 $Arg2)
     (Has-Parameter-Slot $Arg2 $Arg1))

(Inverse Parameter-Slot-Of Has-Parameter-Slot)

Notes:

• The parameter is not reified as an object with a slot for its value. Instead, it's just a named slot. Since the slot is a function, and function constants can be used as terms in KIF, then one can still describe properties of an parameter as such.
• The value-cardinality spec says that each parameter must have exactly one value per component. What does this mean for parameters that are not constants, i.e., those that are computed from other values via constraints?

  If someone asserts that component C has-parameter-slot A, then this spec says that there exists a value for the function A applied to C. It does not say that any particular agent knows what that value is.

  (formerly-called has-attribute)
  

  (see-also valid-design)