Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ SPDX-License-Identifier: CC-BY-4.0

== Composite I4.0 Components

As described in xref:annex/general.adoc#life-cycle-with-type-assets-and-instance-assets[], there is a class of relationships between assets of different hierarchy levels.
As described in xref:annex/general.adoc#life-cycle-with-type-assets-and-instance-assets[Life Cycle with Type Assets and Instance Assets], there is a class of relationships between assets of different hierarchy levels.
In this class of relationships, automation equipment is explained as a complex, interrelated graph of automation devices and products, performing intelligent production and self-learning/optimization tasks.

Details and examples for composite I4.0 Components can be found in xref:bibliography.adoc#bib13[[13\]].
Expand Down
37 changes: 20 additions & 17 deletions documentation/IDTA-01001/modules/ROOT/pages/bibliography.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -125,14 +125,14 @@


[#bib24]
[24] ISO 13584-42 "Standard data element types with associated classification scheme – Part 1: Definitions – Principles and methods" Edition 4.0, 2017-07
[24] ISO 13584-42 "Standard data element types with associated classification scheme – Part 1: Definitions – Principles and methods" Edition 4.0, 2017-07.

[#bib25]
[25] IEC 61360-1 "Standard data element types with associated classification scheme – Part 1: Definitions – Principles and methods", Edition 4.0, 2017-07. DIN EN 61360-1:2018-07.


[#bib26]
[26] ISO/TS 29002-10:2009(E) "Industrial automation systems and integration — Exchange of characteristic data — Part 10: Characteristic data exchange format", First edition 2009-12-01
[26] ISO/TS 29002-10:2009(E) "Industrial automation systems and integration — Exchange of characteristic data — Part 10: Characteristic data exchange format", First edition 2009-12-01.

[#bib27]
[27] A. Bayha, J. Bock, B. Boss, C. Diedrich, S. Malakuti "Describing Capabilities of Industrie 4.0 Components".
Expand All @@ -142,25 +142,20 @@

////
[#bib28]
[28] AutomationML Association: "Application Recommendations: Asset Administration Shell Representation (AR 004E)", Version 1.0.0, 20.11.2019,
Available: https://www.automationml.org/o.red.c/dateien.html
[28] AutomationML consortium: "Application Recommendation: AAS Representation (AR 004E)", Document Identifier: AR AAS, V1.0.0. November 2019.
Accessed: 2025-10-19. [Online].
Available: https://www.automationml.org/wp-content/uploads/2022/04/Asset-Administration-Shell-Representation-V1_0_0.zip
////

[#bib29]
[29] H. Knublauch, D. Knotokostas "Shapes Constraint Language (SHACL)" W3C Recommendation, 2017,
[29] H. Knublauch, D. Knotokostas "Shapes Constraint Language (SHACL)" W3C Recommendation, 2017.
Accessed: 2025-03-24. [Online].
Available:
Available: https://www.w3.org/TR/shacl/

////
[#bib30]
[30] "I4AAS – Industrie 4.09 Asset Administration Shell". June 2021. [Online] Available: https://opcfoundation.org/markets-collaboration/I4AAS/
////
[30] "I4AAS – Industrie 4.09 Asset Administration Shell". June 2021.
[#bib31]
[31] DIN EN IEC 61406-1: "Identification Link - Part 1: General requirements (IEC 61406-1:2022)".
December 2023. Online.
Available: https://www.dinmedia.de/en/standard/din-en-iec-61406-1/372053652
[#bib32]
[32] F. Manola, E. Miller "RDF 1.1 Primer" W3C Recommendation, 2014,
Expand All @@ -177,19 +172,19 @@
Technical Report.
Version 2.3. October 10, 2020. Industrial Internet Consortium.
IIC:IIVOC:V2.3:20201025
Accessed: 2025-03-24. [Online].
Accessed: 2025-10-19. [Online].
Available: https://www.iiconsortium.org/vocab/
[#bib35]
[35] "OMG Unified Modelling Language (OMG UML)".
Formal/2017-12-05. Version 2.5.1. December 2018.
Accessed: 2025-03-24. [Online].
Accessed: 2025-10-19. [Online]
Available: https://www.omg.org/spec/UML/
[#bib36]
[36] T. Preston-Werner "Semantic Versioning".
Version 2.0.0.
Accessed: 2025-03-24. [Online].
Accessed: 2025-10-19. [Online]
Available: https://semver.org/spec/v2.0.0.html
[#bib37]
Expand All @@ -205,11 +200,15 @@
Available: https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2022/12/2022-12-07_IDTA_AAS-Reading-Guide.pdf
[#bib39]
[39] IDTA-02003 "Submodel Template of the Asset Administration Shell - Generic Frame for Technical Data for Industrial Equipment in Manufacturing", Version 1.2, Aug. 2022, Industrial Digital Twin Association
[39] IDTA-02003 "Submodel Template of the Asset Administration Shell - Generic Frame for Technical Data for Industrial Equipment in Manufacturing",
Version 1.2, Aug. 2022,
Industrial Digital Twin Association
See xref:bibliography.adoc#bib45[[45\]].
[#bib40]
[40] IDTA-02006 "Submodel Template of the Asset Administration Shell - Digital Nameplate for Industrial Equipment", Version 2.0, Oct. 2022, Industrial Digital Twin Association
[40] IDTA-02006 "Submodel Template of the Asset Administration Shell - Digital Nameplate for Industrial Equipment",
Version 2.0, Oct. 2022,
Industrial Digital Twin Association
See xref:bibliography.adoc#bib45[[45\]].
////
Expand Down Expand Up @@ -256,7 +255,11 @@
[#bib48]
[48] "How to create a submodel template specification".
V1.1. Junde 2025. Industrial Digital Twin Association.

Check warning on line 258 in documentation/IDTA-01001/modules/ROOT/pages/bibliography.adoc

View workflow job for this annotation

GitHub Actions / qodana

Typo

Typo: In word 'Junde'

Check warning

Code scanning / QDJVMC

Typo Warning documentation

Typo: In word 'Junde'
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

June

Guideline.
Accessed: 2025-10-19. [Online].
Available: https://industrialdigitaltwin.org/wp-content/uploads/2025/06/IDTA_How-to-write-a-SMT-v1.1.pdf
December 2022. Industrial Digital Twin Association.
Accessed: 2025-03-24. [Online].
Available: https://industrialdigitaltwin.org/wp-content/uploads/2022/12/I40-IDTA-WS-Process-How-to-write-a-SMT-FINAL-.pdf
Expand Down
9 changes: 9 additions & 0 deletions documentation/IDTA-01001/modules/ROOT/pages/changelog.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,15 @@ Minor Changes:
* corrected and added links for definitions of qualifiers in IEC CDD (https://github.com/admin-shell-io/aas-specs-metamodel/issues/611[#611])
* Annex UML: add information how to graphically depict attributes of type "Reference" (https://github.com/admin-shell-io/aas-specs-metamodel/issues/601[#601])
* minor changes (including (https://github.com/admin-shell-io/aas-specs-metamodel/issues/600[#600])
* remove Note 2 from Reference/referredSemanticId
* update bibliography
editorial changes

Minor Bugfixes:

* correct ID for AasNonContainerSubmodelElements/Blob
* correct ID for Extension/name
* correct ID for HasSemantics/supplementalSemanticId

=== Metamodel Changes V3.2 vs. V3.1.1

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@

Other attributes of the administrative information like creator refer to ISO 15836-1:2017, the Dublin Core metadata element set.

For more information on the concept of subject, see Attribute Based Access Control (ABAC) xref:bibliography.adoc#bib49[[49\]].

Check failure on line 43 in documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/common.adoc

View workflow job for this annotation

GitHub Actions / qodana

Link Resolve inspection

Anchor doesn't resolve
The assumption is that every subject has a unique identifier.

xref:spec-metamodel/common.adoc#AdministrativeInformation[AdministrativeInformation] allows the usage of templates (xref:spec-metamodel/common.adoc#HasDataSpecification[HasDataSpecification]).
Expand Down Expand Up @@ -219,7 +219,7 @@
.2+h|Attribute 3+h| ID
h|Explanation h|Type h|Card.

.2+e|name 3+| `\https://admin-shell.io/aas/3/1/Extension`
.2+e|name 3+| `\https://admin-shell.io/aas/3/1/Extension/name`
a|Name of the extension |xref:spec-metamodel/datatypes.adoc#NameType[NameType] |1

.2+e|[[Extension_valueType]]valueType 3+| `\https://admin-shell.io/aas/3/1/Extension/valueType`
Expand Down Expand Up @@ -331,7 +331,7 @@

|xref:spec-metamodel/referencing.adoc#Reference[Reference] |0..1

.2+e|supplementalSemanticId 3+| `\https://admin-shell.io/aas/3/1/HasSemantics/supplementalId`
.2+e|supplementalSemanticId 3+| `\https://admin-shell.io/aas/3/1/HasSemantics/supplementalSemanticId`
a|
Identifier of a supplemental semantic definition of the element called supplemental semantic ID of the element

Expand Down Expand Up @@ -550,7 +550,7 @@

Example of a _TemplateQualifier:_ a submodel element with qualifier value "mandatory" or "optional".
This qualification is needed to build a correct submodel instance.
For more information see xref:bibliography.adoc#bib48[[48\]].

Check failure on line 553 in documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/common.adoc

View workflow job for this annotation

GitHub Actions / qodana

Link Resolve inspection

Anchor doesn't resolve

.Example: Qualifier from IEC CDD
[[image-22-qualifier]]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -234,7 +234,7 @@ FTP://unicode.org

.2+e|[[QualifierType]]QualifierType 2+| `\https://admin-shell.io/aas/3/1/QualifierType`
a|_NameType_ a|
"ExpressionSemantic" (as specified in DIN SPEC 92000:2019-09, see xref:bibliography.adoc#bib16[[16\]])
"ExpressionSemantic" (as specified in DIN DKE SPEC 92000:2019-09, see xref:bibliography.adoc#bib16[[16\]])

"life cycle qual" (as specified in IEC 61360-7 - IEC/SC 3D - Common Data Dictionary (link:https://cdd.iec.ch/cdd/common/iec61360-7.nsf/SearchFrameset?OpenFrameSet[CDD - V2.0015.0004])

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -68,15 +68,13 @@ Expected semantic ID of the referenced model element (_Reference/type=ModelRefer


====
Note 1: if Reference/referredSemanticId is defined, the semanticId of the model element referenced should have a matching semantic ID.
Note: if Reference/referredSemanticId is defined, the semanticId of the model element referenced should have a matching semantic ID.
If this is not the case, a validator should raise a warning.
====



====
Note 2: it is recommended to use an external reference for the semantic ID expected from the referenced model element.
====



|xref:Reference[Reference] |0..1
Expand Down Expand Up @@ -530,7 +528,7 @@ h|Explanation
.2+e|BasicEventElement | `\https://admin-shell.io/aas/3/1/AasNonContainerSubmodelElements/BasicEventElement`
a|Basic event element

.2+e|Blob | `\https://admin-shell.io/aas/3/1/AasSubmodelElements/Blob`
.2+e|Blob | `\https://admin-shell.io/aas/3/1/AasNonContainerSubmodelElements/Blob`
a|Blob

.2+e|Capability | `\https://admin-shell.io/aas/3/1/AasNonContainerSubmodelElements/Capability`
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@
a|
Direction of event

Can be \{ input, output }
Can be { input, output }

|xref:Direction[Direction]|1

Expand Down Expand Up @@ -261,7 +261,7 @@
a|Event-specific payload |xref:spec-metamodel/datatypes.adoc#BlobType[BlobType] |0..1
|===

For more information on the concept of subject, see Attribute Based Access Control (ABAC) xref:bibliography.adoc#bib49[[49\]].

Check failure on line 264 in documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/submodel-elements.adoc

View workflow job for this annotation

GitHub Actions / qodana

Link Resolve inspection

Anchor doesn't resolve
The assumption is that every subject has a unique identifier.

== Blob Attributes
Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@startuml
abstract class DataSpecificationContent <<abstract>> {
abstract class DataSpecificationContent <<abstract, Template>> {
}
@enduml
Loading