Incorporate V3.0.2 changes

Incorporate V3.0.2 changes

Author: BirgitBoss

documentation/IDTA-01003-a/modules/ROOT/pages/Annex/IDTA-01003-a_HandlingConstraints.adoc

@@ -14,8 +14,10 @@ Plattform Industrie 4.0; Anna Salari, Publik. Agentur für Kommunikation GmbH, d
 
 = Handling of Constraints
 
-Constraints are prefixed with *AASc-3a-* followed by a three-digit number. The "c" in "AASc-" was motivated by "Concept Description". The numbering of constraints is unique within namespace AASc-3a; a number of a constraint that was removed will not be used again.
+Constraints are prefixed with *AASc-3a-* followed by a three-digit number. The "c" in "AASc-" was motivated by "Concept Description". 
+The numbering of constraints is unique within namespace AASc-3a; a number of a constraint that was removed will not be used again.
 
+If a constraint is mentioning the ID of the Template, then the same constraints shall also be valid for deprecated data specification template IDs.
 
 ====
 Note: in the Annex listing the metamodel changes, constraints with prefix AASd-, AASs- or AASc- are also listed. These are metamodel, security or data specification constraints, and are now part of the split document parts.

documentation/IDTA-01003-a/modules/ROOT/pages/IDTA-01003-a_ChangeLog.adoc

@@ -12,19 +12,19 @@ SPDX-License-Identifier: CC-BY-4.0
 
 ==  Introduction
 
-This document is part of the series "Details of the Asset Administration Shell" that provide the specifications for interoperable usage of the Asset Administration Shell.
+This document is part of the series "Specification of the Asset Administration Shell" that provide the specifications for interoperable usage of the Asset Administration Shell.
 
-This part of the series extends Part 1 and defines a technology-neutral specification of data specification templates, enabling the description of concept descriptions conformant to IEC 61360 in UML. This UML meta model serves as the basis for deriving several different formats for exchanging Asset Administration Shells, e.g. for XML, JSON, RDF, AutomationML, and OPC UA information models.
+This part defines a technology-neutral specification of a data specification template, enabling the description of concept descriptions conformant to IEC 61360 in UML. This UML meta model serves as the basis for deriving several different formats for exchanging Asset Administration Shells, e.g. for XML, JSON, RDF as described in Part 1 of the document series (IDTA-01001). Data Specification Templates are implemented using the embedded data specification approach. This means, that the implementation is part of the overall schemas as defined for IDTA-01001.
 
-_<<#_Toc129706725,Figure 1>>_ shows the different ways of exchanging information via Asset Administration Shells. This part of the "Asset Administration Shell in Detail" series is the basis for all of these types of information exchange.
+_<<#_Toc129706725,Figure 1>>_ shows the different ways of exchanging information via Asset Administration Shells. This part of the "Specification of the Asset Administration Shell" series is the basis for all of these types of information exchange.
 
 [#_Toc129706725]
 .Types of Information Exchange via Asset Administration Shells
 image::image2.jpeg[align=center]
 
-File exchange (1) is described in Part 5 of this document series.
+File exchange (1) is described in Part 5 of this document series (IDTA-01005).
 
-The API (2) is specified in Part 2 of the document series "Details of the Asset Administration Shell" link:#bib14[[14\]]. It also includes access to concept descriptions using the data specifications as specified in this document.
+The API (2) is specified in Part 2 of the document series "Specification of the Asset Administration Shell" (IDTA-01002) link:#bib14[[14\]]. It also includes access to concept descriptions using the data specifications as specified in this document.
 
 The I4.0 language (3) is based on the information metamodel specified in Part 1 and 3 link:#bib23[[23\]].
 
@@ -54,9 +54,9 @@ The data specification template IEC 61360 introduces additional attributes to de
 
 IEC 61360 requests to use IRDIs for the identification of a concept. The Asset Administration Shell allows to use other identifiers besides IRDI. The IRDI, the unique identifier of an IEC 61360 property or value, maps to ConceptDescription/id.
 
-_<<#_Toc129706726,Figure 2>>_ to _<<#_Toc129706729,Figure 5>>_ show examples from ECLASS _<<#_Toc129706727,Figure 3>>_ shows a property with enumeration type. One of the values in this enumeration is shown in _<<#_Toc129706728,Figure 4>>_, each value has its own unique ID. The unique identifier of a value ( _<<#_Toc129706728,Figure 4>>_) is also used for _Property/valueId._
+_<<#_Toc129706726,Figure 2>>_ to _<<#_Toc129706729,Figure 5>>_ show examples from ECLASS. _<<#_Toc129706727,Figure 3>>_ shows a property with enumeration type. One of the values in this enumeration is shown in _<<#_Toc129706728,Figure 4>>_, each value has its own unique ID. The unique identifier of a value (_<<#_Toc129706728,Figure 4>>_) is also used for _Property/valueId._
 
-_<<#_Ref129950722,Figure 6>>_ Example for Property with Level Type from IEC CDD shows an example from IEC CDD for a concept description of a _Property_ with usage of Level Type (in this example level type MIN, MAX and NOM, see data type). This is a short form of defining a collection of three properties with the same data type and semantics except for the level.
+_<<#_Ref129950722,Figure 6>> shows an example from IEC CDD for a concept description of a _Property_ with usage of Level Type (in this example level type MIN, MAX and NOM, see data type). This is a short form of defining a collection of three properties with the same data type and semantics except for the level.
 
 
 [#_Toc129706726]
@@ -89,7 +89,7 @@ There is one data specification template supporting IEC 61360 [IEC61360-1]:
 
 * _DataSpecificationIec61360:_ defining concept descriptions for both properties and coded values.
 
-_<<#_Ref129879629,Figure 7>>_ Overview Relationship Metamodel Part 1 a & Data Specifications IEC 61360 gives an overview of the data specification template and how it is used in combination with the information model as defined in Part 1 of the document series, namely _DataSpecification_, _DataSpecificationContent,_ and _ConceptDescription_.
+_<<#_Ref129879629,Figure 7>>_ Overview Relationship Metamodel Part 1 a & Data Specifications IEC 61360 gives an overview of the data specification template and how it is used in combination with the information model as defined in Part 1 of the document series, namely  _DataSpecification_, _DataSpecificationContent,_ and _ConceptDescription_.
 
 [#_Ref129879629]
 .Overview Relationship Metamodel Part 1 a & Data Specifications IEC 61360
@@ -99,6 +99,3 @@ IEC 61360 is a standard that describes how to define the semantics of properties
 
 The legend for understanding the UML diagrams and the table specification of the classes is explained in xref:sharedAnnex/IDTA-01xxx_UMLTemplates.adoc[] and xref:sharedAnnex/IDTA-01xxx_UML.adoc[].
 
-====
-Note: an xmi representation of the UML model can be found in the repository "aas-specs" in the github project admin-shell-io: https://github.com/admin-shell-io/aas-specs/.
-====

documentation/IDTA-01003-a/modules/ROOT/pages/IDTA-01003-a_Intro.adoc

@@ -12,7 +12,7 @@ SPDX-License-Identifier: CC-BY-4.0
 
 ===  Scope of This Document
 
-The Asset Administration Shell (see Part 1a of the document series) allows to define data specification templates. Data specification templates aim to enable interoperability between the partners that agree on the template. A template defines a set of attributes, with each attribute having a clear semantics. This set of attributes corresponds to a (sub-)schema.
+The Asset Administration Shell (see Part 1 of the document series, IDTA-01001) allows to define data specification templates. Data specification templates aim to enable interoperability between the partners that agree on the template. A template defines a set of attributes, with each attribute having a clear semantics. This set of attributes corresponds to a (sub-)schema.
 
 This document specifies data specification templates conformant to IEC 61360. IEC 61360 specifies how to define the semantics of single properties or values. The value range of a property can be defined as a value list – an enumeration -, while each of the (coded) values of the value list are treated as single concepts. They are thus suited to be used as data specifications for concept descriptions.
 
@@ -24,7 +24,7 @@ Please consult the continuously updated reading guide link:#bib15[[15\]] for an
 
 === Normative References
 
-[AAS-Part1] "The Exchange of information between partners in the value chain of Industrie 4.0", part of document series "Details of the Asset Administration Shell". V3.0. Jan. 2023. Industrial Digital Twin Association.
+[IDTA-01001] "Specification of the Asset Administration Shell. Part 1: Metamodel", IDTA-01001-3-1. Industrial Digital Twin Association.
 
 [IEC61360-1] Standard data element types with associated classification scheme – Part 1: Definitions – Principles and methods. Edition 4.0 2017-07