The semantics of a property or other elements that may have a semantic description is defined by a concept description.

Remarks

The description of the concept should follow a standardized schema (realized as data specification template).

Constraint AASc-3a-004: For a ConceptDescription with category PROPERTY or VALUE using data specification IEC61360, the dataType is mandatory and shall be one of: DATE, STRING, STRING_TRANSLATABLE, INTEGER_MEASURE, INTEGER_COUNT, INTEGER_CURRENCY, REAL_MEASURE, REAL_COUNT, REAL_CURRENCY, BOOLEAN, RATIONAL, RATIONAL_MEASURE, TIME, TIMESTAMP.

Note: Note: categories are deprecated since V3.0 of Part 1a of the document series "Details of the Asset Administration Shell".

Constraint AASc-3a-005: For a ConceptDescription with category REFERENCE using data specification template IEC61360, the dataType shall be one of: STRING, IRI, IRDI.

Note: Note: categories are deprecated since V3.0 of Part 1a of the document series "Details of the Asset Administration Shell".

Constraint AASc-3a-006: For a ConceptDescription with category DOCUMENT using data specification IEC61360, the dataType shall be one of FILE, BLOB, HTML

Note: Categories are deprecated since V3.0 of Part 1a of the document series "Details of the Asset Administration Shell".

Constraint AASc-3a-007: For a ConceptDescription with category QUALIFIER_TYPE using data specification IEC61360, the dataType is mandatory and shall be defined.

Note: Categories are deprecated since V3.0 of Part 1a of the document series "Details of the Asset Administration Shell".

Constraint AASc-3a-008: For a ConceptDescription using data specification template IEC61360, definition is mandatory and shall be defined at least in English.

Exception: The concept description describes a value, i.e. value is defined.

Constraint AASc-3a-003: For a ConceptDescription using data specification template IEC61360, referenced via valueList valueId the value shall be set.

Hierarchy

  • Class
    • ConceptDescription

Implements

Constructors

Properties

Administrative information of an identifiable element.

Remarks

Note: Some of the administrative information like the version number might need to be part of the identification.

category: string

The category is a value that gives further meta information w.r.t. to the class of the element. It affects the expected existence of attributes and the applicability of constraints.

Remarks

Note: The category is not identical to the semantic definition (IHasSemantics) of an element. The category e.g. could denote that the element is a measurement value whereas the semantic definition of the element would denote that it is the measured temperature.

description: LangStringTextType[]

Description or comments on the element.

Remarks

The description can be provided in several languages.

If no description is defined, then the definition of the concept description that defines the semantics of the element is used.

Additional information can be provided, e.g., if the element is qualified and which qualifier types can be expected in which context or which additional data specification templates are provided.

displayName: LangStringNameType[]

Display name. Can be provided in several languages.

embeddedDataSpecifications: EmbeddedDataSpecification[]

Embedded data specification.

extensions: Extension[]

An extension of the element.

id: string

The globally unique identification of the element.

idShort: string

In case of identifiables this attribute is a short name of the element. In case of referable this ID is an identifying string of the element within its name space.

Remarks

Note: In case the element is a property and the property has a semantic definition (semanticId) conformant to IEC61360 the idShort is typically identical to the short name in English.

isCaseOf: Reference[]

Reference to an external definition the concept is compatible to or was derived from.

Remarks

Note: It is recommended to use a global reference.

Note: Compare to is-case-of relationship in ISO 13584-32 & IEC EN 61360

Methods

Generated using TypeDoc