Represented Entities in Model UI Fragment Properties@0.0.4

Contents

Up to Use Case Properties

FragmentProperty: Represented EntitiesStatus: EXPERIMENTAL

Documentation

This property explicitly denotes the content of the UI fragment by pointing to an instance or type model of the entity. In cases where the UI fragment is not shipped by the entity (e.g. process component) or in conjunction with it, it is mandatory to use this property. Using this property allows to identify the described UI fragment as relevant if the referenced entity shall be represented by the UI solution. The represented entity does not necessarily need to be a real object (e.g. a plant component), it may also be an arbitrary kind of virtual/logical element, a set of data (e.g. a schedule, measurement data, statistics), etc. When referring to entity type definitions such as Type-AAS it is possible to exploit inference mechanisms that match the type referred to by this property statement against the content entity required. Such inference mechanisms enable the definition of UI fragments for types of content entities instead of for individual instances. Despite such algorithms being available also arbitrary content entity identifiers may be used. In cases where UI fragments and the relevant property statements are shipped together in a component that represents the content entity, this property statement is not required to be used.

Typed Element: → 'RepresentedEntitiesType'

Base Type: <NONE>
Abstract: Yes
Cardinality: 1..∞
From Model: UI Fragment Properties
Documentation: This data type allows to create string-based reference lists either by using Identifiers, URLs, or plain strings in order to create lists of UI fragment contents. Those referred information objects are not required to be asset administration shells, even certain information units defined therein can be referred to. In the case of describing represented contents of a template object, the alternative multiple represented entities type may be used to also describe cardinalities of represented elements for each template section.

Instanciatable Types 4

Name: → 'MultipleRepresentedEntitiesType' Status: EXPERIMENTAL
Base Type: STRUCTURED
Abstract: No
Cardinality: 0..1
From Model: UI Fragment Properties
Documentation: This data type is an extension to the represented entities type by providing a structure that adds lower and upper bound cardinalities to the refferred content entity.
Structured Value Members:
This data type is an extension to the represented entities type by providing a structure that adds lower and upper bound cardinalities to the refferred content entity.
Name: → 'URLType' Status: EXPERIMENTAL
Base Type: STRING
Abstract: No
Cardinality: 0..1
From Model: Common Property Types
Documentation: This type can be used to create actual well-formed URL string property statements.
This type can be used to create actual well-formed URL string property statements.
Name: → 'StringType' Status: EXPERIMENTAL
Base Type: STRING
Abstract: No
Cardinality: 0..1
From Model: Common Property Types
Documentation: This type can be used to create actual string property statements.
This type can be used to create actual string property statements.
Name: → 'IdentifierType' Status: EXPERIMENTAL
Base Type: STRING
Abstract: No
Cardinality: 0..1
From Model: Common Property Types
Documentation: This type can be used to actually create property statements the value of which is pointing to a resolvable entity.

Identifier

This type can be used to actually create property statements the value of which is pointing to a resolvable entity.