Changes: Batch, contentTYpe, Qualifiers, Annex UML

documentation/IDTA-01001/modules/ROOT/pages/changelog.adoc

@@ -41,6 +41,13 @@
 Major Changes:
 
 * IN DISCUSSION: ADDED: New attributes for data ranges in AdministrationInformation  (https://github.com/admin-shell-io/aas-specs-metamodel/issues/484[#484])
+* added new value to enumeration AssetKind: Batch to support Digital Product Passports (https://github.com/admin-shell-io/aas-specs-metamodel/issues/483[#483])
+
+Minor Changes:
+
+* description of data type ContentType changed, some explana, das ition with respect to mime types removed (https://github.com/admin-shell-io/aas-specs-metamodel/issues/604[#604])
+* corrected and added links for definitions of qualifiers in IEC CDD (https://github.com/admin-shell-io/aas-specs-metamodel/issues/611[#611])
+* minor changes
 
 
 == Changes V3.1.1 vs. V3.1

documentation/IDTA-01001/modules/ROOT/pages/mappings/encodings/metadata-objects.adoc

@@ -64,7 +64,7 @@ a|
     "description": [...],
     "id": "idTestAAS",
      ...
-    "derivedFrom": {...}
+    "derivedFrom": {...},
     "assetInformation": {...},
     "submodels": [...]
 }

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/common.adoc

@@ -449,7 +449,8 @@ include::partial$diagrams/21-qualifier.puml[]
 
 Qualifiers may be defined for qualifiable elements.
 
-There are standardized qualifiers defined in IEC CDD, IEC61360-4 – IEC/SC 3D.
+There are standardized qualifiers defined in (https://cdd.iec.ch/cdd/iec61360-7/iec61360-7.nsf/TreeFrameset?OpenFrameSet&ongletactif=1)[IEC CDD, IEC61360-7, CAA002].
+and (https://cdd.iec.ch/cdd/iec61987/iec61987.nsf/TreeFrameset?OpenFrameSet&ongletactif=1)[IEC CDD, IEC 61987, ABJ604].
 A level qualifier defining the level type minimal, maximal, typical, and nominal value is specified in IEC 62569-1.
 In DIN SPEC 92000, qualifier types like e.g. expression semantics and expression logic are defined.
 

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/core.adoc

@@ -91,7 +91,7 @@ h|ID: 3+| `\https://admin-shell.io/aas/3/1/AssetInformation`
 h|Explanation h|Type h|Card.
 
 .2+e|[[assetKind]]assetKind  3+| `\https://admin-shell.io/aas/3/1/AssetInformation/assetKind`
-a|Denotes whether the asset is of kind "Type", Instance", "Role" or none of these types is applicable |xref:AssetKind[AssetKind]|1
+a|Denotes whether the asset is of kind "Type", Instance", "Batch", "Role" or none of these types is applicable |xref:AssetKind[AssetKind]|1
 
 .2+e|[[globalAssetId]]globalAssetId 3+| `\https://admin-shell.io/aas/3/1/AssetInformation/globalAssetId`
 a|
@@ -171,7 +171,7 @@ The content type states which file extensions the file can have.
 |===
 |Enumeration: e|[[AssetKind]]AssetKind
 h|Explanation: a|Enumeration for denoting whether an asset is a type asset or
-an instance asset or is a role or whether this kind of classification is not applicable
+an instance asset or a batch asset or is a role or whether this kind of classification is not applicable
 h|Set of: |--
 h|ID: | `\https://admin-shell.io/aas/3/1/AssetKind`
 
@@ -184,6 +184,9 @@ a|Type asset
 .2+e|Instance | `\https://admin-shell.io/aas/3/1/AssetKind/Instance`
 a|Instance asset
 
+.2+e|Batch | `\https://admin-shell.io/aas/3/1/AssetKind/Batch`
+a|batch asset
+
 .2+e|Role | `\https://admin-shell.io/aas/3/1/AssetKind/Role`
 a|Role asset
 

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/datatypes.adoc

@@ -95,15 +95,10 @@ a|
 _string_ with max 128 and min 1 characters
 
 
-====
-Note: string conformant to RFC2046.
-====
+Any content type as specified in [RFC2046](https://datatracker.ietf.org/doc/html/rfc2046). 
 
-====
-A media type (also MIME type and content type) […] is a two-part identifier for file formats and format contents transmitted on the Internet.
-The link:https://www.iana.org/assignments/media-types/media-types.xhtml[Internet Assigned Numbers Authority (IANA)] is the official authority for the standardization and publication of these classifications.
-Media types were originally defined in Request for Comments 2045 in November 1996 as a part of MIME specification, for denoting type of email message content and attachments.footnote:[Wikipedia.org, date: 2018-04-09]
-====
+The content type should be registered by the Internet Assigned Numbers Authority (IANA([link](https://www.iana.org/assignments/media-types/media-types.xhtml)))
+ as specified in [RFC2048](https://datatracker.ietf.org/doc/html/rfc2048). 
 
 a|
 application/pdf

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/submodel-elements.adoc

@@ -490,11 +490,9 @@ include::partial$diagrams/37-file.puml[]
 ....
 
 
-A media type (also MIME type and content type) is a two-part identifier for file formats and format contents transmitted via the Internet.
-The Internet Assigned Numbers Authority (IANA) is the official authority for the standardization and publication of these classifications.
 
 ====
-Note: for information on handling supplementary external files in exchanging Asset Administration Shells in AASX package format see also Part 5 of the series link:https://industrialdigitaltwin.org/en/content-hub/aasspecifications["Specification of the Asset Administration Shell"].
+Note: for information on handling supplementary external files in exchanging Asset Administration Shells in AASX Package File Format see also Part 5 of the series link:https://industrialdigitaltwin.org/en/content-hub/aasspecifications["Specification of the Asset Administration Shell"].
 An absolute path is used in case the file exists independently of the Asset Administration Shell.
 A relative path, relative to the package root, should be used if the file is part of a serialized package of the Asset Administration Shell.
 ====

documentation/IDTA-01001/modules/ROOT/partials/diagrams/classes/enum-asset-kind.puml

@@ -2,6 +2,7 @@
 enum AssetKind <<enumeration>> {
   Type
   Instance
+  Batch
   Role
   NotApplicable
 }