From 60ecf948cd2b07a26ed8e20bf72306f110e4e674 Mon Sep 17 00:00:00 2001 From: Sebastian Eicke Date: Mon, 25 Aug 2025 08:05:06 +0200 Subject: [PATCH 1/3] Fixes duplicate link id #id42 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 704a73b..fadc8dd 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ Please address discussions and proposals via issues and pull requests in the git - [How to define the relationship between asset instance and asset type wrt. corresponding submodels?](#idgh13) ### Asset Administration Shell -- [What are best practices for creating a system of Asset Administration Shells?](#id42) +- [What are best practices for creating a system of Asset Administration Shells?](#idgh42) - [Where are examples of AAS available?](#id16) - [Can RDF be used as an interchange format?](#idgh59) - [Values for externalSubjectId within SpecificAssetId?](#idgh78) @@ -111,7 +111,7 @@ As of now, references ignore versioning information. In case versioning is essen [This AAS example](https://admin-shell-io.github.io/questions-and-answers/Examples/isCaseOf_Examples.aasx) contains a template of "Technical Data" submodel with two properties indicating how alterantive semantic IDs can be used in AAS modeling. For example, the "ManufacturerName" property, has a semantic ID "https://admin-shell.io/sandbox/SG2/TechnicalData/ManufacturerName/1/1" and two isCaseOf references to a ECLASS and a CDD IRDIs (the references are within the ConceptDescription). -**[What are best practices for creating a system of Asset Administration Shells?](#id42)** +**[What are best practices for creating a system of Asset Administration Shells?](#idgh42)** There are currently two ways to create/reference further AAS: 1) Using a BOM (Bill of Material) submodel, a dedicated submodel with self- or co-managed assets From e9886297e4e3e07c873067a5f9836527af268a30 Mon Sep 17 00:00:00 2001 From: Sebastian Eicke Date: Mon, 25 Aug 2025 08:32:54 +0200 Subject: [PATCH 2/3] Updates answer idgh42 --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index fadc8dd..9f0c49b 100644 --- a/README.md +++ b/README.md @@ -113,21 +113,21 @@ As of now, references ignore versioning information. In case versioning is essen **[What are best practices for creating a system of Asset Administration Shells?](#idgh42)** -There are currently two ways to create/reference further AAS: -1) Using a BOM (Bill of Material) submodel, a dedicated submodel with self- or co-managed assets +There are currently two ways to create/reference AAS: +1) Creating a submodel by using the [submodel template "Hierarchical Structures enabling Bills of Material" (BOM)](https://github.com/admin-shell-io/submodel-templates/tree/main/published/Hierarchical%20Structures%20enabling%20Bills%20of%20Material) - > Note: Scope of the BOM submodel are relations between *assets* and not *AASs*. BOM submodel defined “isPartOf” and “isIdentical” relation types between assets. + > Note: Scope of the BOM submodel are relations between *assets* and not *Asset Administration Shells*. The submodel defines "SameAs", "IsPartOf" and "HasPart" relationships between assets. - * Self-managed assets have own asset ID which can be used in AAS infrastructure (e.g., a registry) to query available AAS. - * Co-managed assets have no asset ID and own AAS. + * Self-managed assets have their own `globalAssetId` which can be used in an AAS infrastructure (AAS Discovery Service, AAS registry & AAS repository) to query available AAS. + * Co-managed assets do not have an `globalAssetId` and do not have an own AAS. -    *Advantages*: BOM-AAS is self-contained and has no “external” dependencies such as references to AAS, probably will be used as blueprint for further submodels. +    *Advantages*: Asset Administration Shells with BOM submodel are self-contained and have no "external" dependencies such as references to AAS. They can be used as blueprint for further AAS resp. submodels. -    *Disadvantages*: AAS infrastructure for resolution of asset ID to AAS is needed. +    *Disadvantages*: AAS infrastructure (AAS Discovery Service, AAS registry & AAS repository) for resolving of `globalAssetIds` to an AAS is needed (cf. [Specification of the Asset Administration Shell Part 2: Application Programming Interfaces](https://industrialdigitaltwin.io/aas-specifications/index/home/index.html)). -2) Direct references to external AAS or Submodels using ReferenceElements or RelationshipElements. We currently do not recommend this method in case of lacking generalizability and creation of tight couplings between AAS (by taking over the “resolution” part). +2) Direct references to (external) AAS or submodels using submodel elements like `ReferenceElement` or `RelationshipElement`. This is not recommend cause of lacking generalizability and creation of tight couplings between AAS. -(Answered: 2021-06-28) +(Answered: 2021-06-28 | Updated: 2025-08-25 | AAS Metamodel v3) **[How shall a link to a website be entered in an AAS, as File or as ReferenceElement object?](#id2)** From 558ffe24006c7b3783bb8cdd57919eef8243ab57 Mon Sep 17 00:00:00 2001 From: Sebastian Eicke Date: Mon, 25 Aug 2025 13:04:56 +0200 Subject: [PATCH 3/3] Fix --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9f0c49b..3ae3e58 100644 --- a/README.md +++ b/README.md @@ -125,7 +125,7 @@ There are currently two ways to create/reference AAS:     *Disadvantages*: AAS infrastructure (AAS Discovery Service, AAS registry & AAS repository) for resolving of `globalAssetIds` to an AAS is needed (cf. [Specification of the Asset Administration Shell Part 2: Application Programming Interfaces](https://industrialdigitaltwin.io/aas-specifications/index/home/index.html)). -2) Direct references to (external) AAS or submodels using submodel elements like `ReferenceElement` or `RelationshipElement`. This is not recommend cause of lacking generalizability and creation of tight couplings between AAS. +2) Direct references to (external) AAS or submodels using submodel elements like `ReferenceElement` or `RelationshipElement`. This is not recommend cause of lacking generalizability and creation of tight couplings between AAS. (Answered: 2021-06-28 | Updated: 2025-08-25 | AAS Metamodel v3)