Value Only

In many scenarios, applications working with Asset Administration Shell (AAS) data already know the structure and meaning of a Submodel. Since attributes, structure, and semantics usually remain unchanged, transferring complete model information with every request is unnecessary. Metadata can still be requested separately using the Content modifier set to Metadata (see IDTA-01002).

The Value Only format is supported for the following types:

• Submodel

• Submodel Element Collection

• Submodel Element List

• Property

• Range

• File

• Blob

• Reference Element

• Relationship Element

• Annotated Relationship Element

Benefits

Reduced Data Transfer: Applications are typically interested only in current values. Sending just the values reduces transferred data and improves efficiency—especially important for devices with limited processing power or network bandwidth.

Separation of Concerns: Semantics and structure can be provided by one system (e.g., a database optimized for querying model information), while actual data values are delivered by another system (e.g., a device providing live runtime data).

Efficient UI Updates: By using separate requests for metadata and values, applications can build user interfaces efficiently and update displayed values quickly without repeatedly transferring static information.

Hint

For a more in-depth explanation see IDTA Part 1: Metamodel v3.1.1

• Submodel Value Only
• Submodel Element Collection Value Only
• Submodel Element List Value Only
• Property Value Only
• Range Value Only
• File Value Only
• Blob Value Only
• Reference Element Value Only
• Relationship Element Value Only
• Annotated Relationship Element Value Only