FeatureTyping

FeatureTyping is defined in KerML specification on page 203. Excerpt from the machine readable specification:

FeatureTyping is Specialization in which the specific Type is a Feature. This means the set of instances of the (specific) typedFeature is a subset of the set of instances of the (general) type. In the simplest case, the type is a Classifier, whereupon the typedFeature has values that are instances of the Classifier.

The following diagram shows the inheritance hierarchy of FeatureTyping according to the specification:

// Class: FeatureTyping digraph { FeatureTyping [label="FeatureTyping (KerML)" shape=plaintext] Specialization -> FeatureTyping Specialization [label="Specialization (KerML)" shape=plaintext] Relationship -> Specialization Relationship [label="Relationship (KerML)" shape=plaintext] Element -> Relationship Element [label="Element (KerML)" shape=plaintext] }

The following table shows all attributes defined for FeatureTyping according to the specification together with the documentation from the machine readable specification. Note that in SysIDE API, we use snake case for attribute names instead of Pascal case used in the specification.

Attribute	Documentation from machine readable specification
Attributes defined in `FeatureTyping`:
`typed_feature`	The `Feature` that has a `type` determined by this `FeatureTyping`.
`type`	The `Type` that is being applied by this `FeatureTyping`.
`owning_feature`	A `typedFeature` that is also the `owningRelatedElement` of this `FeatureTyping`.
Attributes defined in `Specialization`:
`general`	A `Type` with a superset of all instances of the `specific` `Type`, which might be the same set.
`specific`	A `Type` with a subset of all instances of the `general` `Type`, which might be the same set.
`owning_type`	The `Type` that is the `specific` `Type` of this `Specialization` and owns it as its `owningRelatedElement`.
Attributes defined in `Relationship`:
`is_implied`	Whether this Relationship was generated by tooling to meet semantic rules, rather than being directly created by a modeler.
`related_elements`	The Elements that are related by this Relationship, derived as the union of the `source` and `target` Elements of the Relationship.
`targets`	The `relatedElements` to which this Relationship is considered to be directed.
`sources`	The `relatedElements from which this Relationship is considered to be directed.`
`owning_related_element`	The relatedElement of this Relationship that owns the Relationship, if any.
`owned_related_elements`	The relatedElements of this Relationship that are owned by the Relationship.
Attributes defined in `Element`:
`element_id`	The globally unique identifier for this Element. This is intended to be set by tooling, and it must not change during the lifetime of the Element.
`declared_short_name`	An optional alternative name for the `Element` that is intended to be shorter or in some way more succinct than its primary `name`. It may act as a modeler-specified identifier for the `Element`, though it is then the responsibility of the modeler to maintain the uniqueness of this identifier within a model or relative to some other context.
`declared_name`	The declared name of this `Element`.
`short_name`	The short name to be used for this `Element` during name resolution within its `owningNamespace`. This is derived using the `effectiveShortName()` operation. By default, it is the same as the `declaredShortName`, but this is overridden for certain kinds of `Elements` to compute a `shortName` even when the `declaredName` is null.
`name`	The name to be used for this `Element` during name resolution within its `owningNamespace`. This is derived using the `effectiveName()` operation. By default, it is the same as the `declaredName`, but this is overridden for certain kinds of `Elements` to compute a `name` even when the `declaredName` is null.
`qualified_name`	The full ownership-qualified name of this `Element`, represented in a form that is valid according to the KerML textual concrete syntax for qualified names (including use of unrestricted name notation and escaped characters, as necessary). The `qualifiedName` is null if this `Element` has no `owningNamespace` or if there is not a complete ownership chain of named `Namespaces` from a root `Namespace` to this `Element`.
`is_implied_included`	Whether all necessary implied Relationships have been included in the `ownedRelationships` of this Element. This property may be true, even if there are not actually any `ownedRelationships` with `isImplied = true`, meaning that no such Relationships are actually implied for this Element. However, if it is false, then `ownedRelationships` may not contain any implied Relationships. That is, either all required implied Relationships must be included, or none of them.
`is_library_element`	Whether this Element is contained in the ownership tree of a library model.
`owning_membership`	The `owningRelationship` of this `Element`, if that `Relationship` is a `Membership`.
`owned_relationships`	The Relationships for which this Element is the owningRelatedElement.
`owning_relationship`	The Relationship for which this Element is an ownedRelatedElement, if any.
`owning_namespace`	The `Namespace` that owns this `Element`, which is the `membershipOwningNamespace` of the `owningMembership` of this `Element`, if any.
`owner`	The owner of this Element, derived as the `owningRelatedElement` of the `owningRelationship` of this Element, if any.
`owned_elements`	The Elements owned by this Element, derived as the ownedRelatedElements of the ownedRelationships of this Element.
`documentation`	The Documentation owned by this Element.
`owned_annotations`	The `ownedRelationships` of this `Element` that are `Annotations`, for which this `Element` is the `annotatedElement`.
`textual_representations`	The `TextualRepresentations` that annotate this `Element`.