Part 3a: Data Specification Template Measurement Units (IDTA-01003-b)

Specification of the Asset Administration Shell

This specification is part of the Asset Administration Shell Specification series.

Version

This is the first version 3.0 of the specification IDTA-01003-b.

Metamodel Versions

This document uses the following parts of the “Specification of the Asset Administration Shell” series:

  • IDTA-01001 Part 1: Metamodel in version 3.2 [22]

Notice

Copyright: Industrial Digital Twin Association e.V. (IDTA)

IDTA Document Number: IDTA-01003-b-3-0

DOI: TO BE ADDED

This work is licensed under a Creative Commons Attribution 4.0 International License.

SPDX-License-Identifier: CC-BY-4.0

  • DATE TO BE ADDED **

How to Get in Contact

Contact: IDTA

Sources: GitHub

Feedback:

Editorial Notes

History

This document, version 3.0, was produced from xxx

Versioning

This specification is versioned using Semantic Versioning 2.0.0 (semver) and follows the semver specification [13].

Conformance

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC2119 RFC8174[1]:

  • MUST word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.

  • MUST NOT This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.

  • SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

  • SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

  • MAY This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)