Data Type
Definition in different languages
Set of levels.
Preferred name
Note: It is advised to keep the length of the name limited to 35 characters.
Constraint AASc-3a-002
:
preferredName shall be provided at least in English.
Short name
Source of definition
Symbol
Unit
Value
Value Format
Note: The value format is based on ISO 13584-42 and IEC 61360-2.
List of allowed values
Dispatch visitor
on this instance.
to visit this instance
Dispatch visitor
with context
on this instance.
type of the context
to visit this instance
to be passed along to the dispatched visitor method
Yield from definition if it is set, or yield nothing.
Yield from shortName if it is set, or yield nothing.
Dispatch the transformer
on this instance.
transformation of this instance
T - type of the transformation result
to transform this instance
Dispatch the transformer
on this instance in context
.
transformation of this instance
T - type of the transformation result
ContextT - type of the transformation context
to transform this instance
to be passed along to the transformer
Generated using TypeDoc
Content of data specification template for concept descriptions for properties, values and value lists conformant to IEC 61360.
Remarks
Note: IEC61360 requires also a globally unique identifier for a concept description. This ID is not part of the data specification template. Instead the id as inherited via IIdentifiable is used. Same holds for administrative information like the version and revision.
Note: idShort and shortName are very similar. However, in this case the decision was to add shortName explicitly to the data specification. Same holds for displayName and preferredName. Same holds for description and definition.
Constraint
AASc-3a-010
: If value is not empty then valueList shall be empty and vice versa.Note: It is also possible that both value and valueList are empty. This is the case for concept descriptions that define the semantics of a property but do not have an enumeration (valueList) as data type.
Note: Although it is possible to define a ConceptDescription for a :attr:´value_list`, it is not possible to reuse this {@link DataSpecificationIec61360.valueList}. It is only possible to directly add a {@link DataSpecificationIec61360.valueList} as data type to a specific semantic definition of a property.
Constraint
AASc-3a-009
: If dataType one of: IntegerMeasure, RealMeasure, RationalMeasure, IntegerCurrency, RealCurrency, then unit or unitId shall be defined.