Annex DPP: fix nav.adoc + update text by BirgitBoss · Pull Request #621 · admin-shell-io/aas-specs-api

BirgitBoss · 2026-05-28T08:10:15Z

update nav.adoc otherwise not found
update text

+* EN 18219:2026 – Digital product passport – Unique identifiers
+* EN 18220:2026 – Digital product passport – Data carriers
+* EN 18216:2026 – Digital product passport – Data exchange protocols
+* EN 18222: 2026 – Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability


+
+This annex specifies how the requirements as specified in
+
+* EN 18222:2026 – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability


-the terms "method" and "operation" are synonym in this context. 
-In FFprEN 18222 "method" is used, in IDTA 01002 "operation" is used.
+The terms "method" and "operation" are synonym in this context. 
+In EN 18222 "method" is used, in IDTA-01002 "operation" is used.


 ====
-The mapping of DPP data elements to AAS metamodel elements (FprEN 18223) is specified in *TODO_XREF:[IDTA-01001 Part 1 -- DPP Metamodel Mapping]*. 
-The DPP metadata Submodel Template is specified in link:https://industrialdigitaltwin.org/en/content-hub/submodels[IDTA-02099-1-0 Digital Product Passport – Part 1: Metadata - Submodel Template Specification] with isShort "DppMeta". 
+The mapping of DPP data elements to AAS metamodel elements (EN 18223) is specified in link:https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.2/annex/dpp.html[IDTA-01001]. 


 * An *Asset Administration Shell* representing the product for which the DPP is issued.
-* A *DppMeta Submodel* (semanticId: `urn:samm:io.admin-shell.idta.dpp_meta:1.0.0#DppMeta` (exact identifier not yet finalized), as defined in *TODO_XREF:[IDTA-02099-1-0]*) containing the DPP header fields (`digitalProductPassportId`, `uniqueProductIdentifier`, `granularity`, `dppSchemaVersion`, `dppStatus`, `lastUpdate`, `economicOperatorId`, `facilityId`, `contentSpecificationIds`).
-* One or more *content Submodels*, each contributing a section of the DPP content. The semanticIds of the contributing content Submodels shall be listed in the `contentSpecificationIds` property of the DppMeta Submodel.
+* A *DppMetadata Submodel* (semanticId: `https://admin-shell.io/idta/cds/dppMetadata/1`, as defined in *IDTA-02099 V1.0*) containing the DPP header fields (`digitalProductPassportId`, `uniqueProductIdentifier`, `granularity`, `dppSchemaVersion`, `dppStatus`, `lastUpdate`, `economicOperatorId`, `facilityId`, `contentSpecificationIds`).


-There are known differences in the serialization of MultiLanguageProperty and File between AAS Value-Only and JTC24 compressed format. Implementations shall ensure that the DPP output conforms to FprEN 18223. For details on these differences and the required transformations, see *TODO_XREF:[IDTA-01001 Part 1 -- DPP Metamodel Mapping, Serialization]*.
-In *TODO_XREF:[IDTA-01001 Part 1 -- DPP Metamodel Mapping, Serialization]* also a detailed mapping for "Full / Expanded" format can be found.
+There are known differences in the serialization of MultiLanguageProperty and File between AAS Value-Only and JTC24 compressed format. Implementations shall ensure that the DPP output conforms to EN 18223. 
+For details on these differences and the required transformations, see link:https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.1.2/annex/dpp.html[IDTA-01001 Part 1 -- DPP Metamodel Mapping, Serialization].



-The discovery of Digital Product Passports can be implemented using the AAS discovery steps defined in *TODO_XREF:[IDTA-01002 Part 2 -- Figure 2]*. These steps enable clients to discover and access AAS instances based on asset identifiers, including the product identifiers used in Digital Product Passports.
+The discovery of Digital Product Passports can be implemented using the AAS discovery steps defined in 
+link:https://industrialdigitaltwin.io/aas-specifications/IDTA-01002/v3.1.2/http-rest-api/interactions.html#fig:seq-aas-endpoints[IDTA-01002 Part 2 -- Figure 2]. 


-To enable discovery, the economic operator responsible for the product shall ensure that the AAS instance representing the DPP is linked to the product identifier via the `globalAssetId` or `specificAssetId` fields in the `AssetInformation` of the AAS. The `uniqueProductIdentifier` in the DppMeta Submodel shall correspond to the `globalAssetId` of the AAS. The explicit mapping is defined in *TODO_XREF:[IDTA-02099]*.
+To enable discovery, the economic operator responsible for the product shall ensure that the AAS instance representing the DPP is linked to the product identifier via the `globalAssetId` or `specificAssetId` fields in the `AssetInformation` of the AAS. 
+The `uniqueProductIdentifier` in the DppMetadata Submodel shall correspond to the `globalAssetId` of the AAS. 
+The explicit mapping is defined in IDTA-02099.




-.DPP Discovery and Composition Sequence with a Repository Service involved (see *TODO_XREF:[IDTA-01002 Part 2 -- Chapter Interactions]*)
+.DPP Discovery and Composition Sequence with a Repository Service involved (see link:https://industrialdigitaltwin.io/aas-specifications/IDTA-01002/v3.1.2/http-rest-api/interactions.html[IDTA-01002 Part 2 -- Chapter Interactions])


-*Access control*: Implementations should enforce appropriate access control policies on DPP operations, in accordance with FprEN 18222, Clause 4.2–4.5. Different data elements within a DPP may require different levels of authorization depending on the stakeholder and their role in the product lifecycle. For further details see *TODO_XREF:[IDTA-01004 Part 4]*.
+*Access control*: Implementations should enforce appropriate access control policies on DPP operations, in accordance with EN 18222, Clause 4.2–4.5. 
+Different data elements within a DPP may require different levels of authorization depending on the stakeholder and their role in the product lifecycle. 
+For further details see link:https://industrialdigitaltwin.io/aas-specifications/IDTA-01004/v3.1/index.html[IDTA-01004 Part 4].


BirgitBoss · 2026-05-28T08:45:49Z

+* EN 18219:2026 – Digital product passport – Unique identifiers
+* EN 18220:2026 – Digital product passport – Data carriers
+* EN 18216:2026 – Digital product passport – Data exchange protocols
+* EN 18222: 2026 – Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability


Suggested change

* EN 18222: 2026 – Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability

* EN 18222:2026 – Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability

BirgitBoss · 2026-05-28T08:46:53Z

+The DPP operations defined in EN 18222 are organized into three API surfaces:
+
+* Life Cycle API - main API methods* (EN 18222, Clause 4, Table 16) -- Mandatory read operations and CRUD operations for DPP lifecycle management.
+* DPP Registry API* (EN 18222, Clause 5, Table 17) -- Registration of DPPs at the DPP Registry.


Suggested change

* DPP Registry API* (EN 18222, Clause 5, Table 17) -- Registration of DPPs at the DPP Registry.

* DPP Registry API (EN 18222, Clause 5, Table 17) -- Registration of DPPs at the DPP Registry.

BirgitBoss · 2026-05-28T08:47:12Z

+
+* Life Cycle API - main API methods* (EN 18222, Clause 4, Table 16) -- Mandatory read operations and CRUD operations for DPP lifecycle management.
+* DPP Registry API* (EN 18222, Clause 5, Table 17) -- Registration of DPPs at the DPP Registry.
+* Life Cycle API - fine granular API methods* (EN 18222, Clause 6, Table 18) -- Element-level read and update operations within a DPP.


Suggested change

* Life Cycle API - fine granular API methods* (EN 18222, Clause 6, Table 18) -- Element-level read and update operations within a DPP.

* Life Cycle API - fine granular API methods (EN 18222, Clause 6, Table 18) -- Element-level read and update operations within a DPP.

Annex DPP: fix nav.adoc + update text

c1e6910

BirgitBoss requested review from alexgordtop, aorzelskiGH, danielporta, g1zzm0, mjacoby, sebbader-sap, waltersve and zrgt as code owners May 28, 2026 08:10

github-advanced-security AI found potential problems May 28, 2026

View reviewed changes

BirgitBoss commented May 28, 2026

View reviewed changes

sebbader-sap approved these changes May 28, 2026

View reviewed changes

BirgitBoss merged commit 8542dd7 into IDTA-01002-3-2_working May 28, 2026
3 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Annex DPP: fix nav.adoc + update text#621

Annex DPP: fix nav.adoc + update text#621
BirgitBoss merged 1 commit into
IDTA-01002-3-2_workingfrom
BiBo/fix_dpp

BirgitBoss commented May 28, 2026 •

edited

Loading

Uh oh!

BirgitBoss May 28, 2026

Uh oh!

BirgitBoss May 28, 2026 •

edited

Loading

Uh oh!

BirgitBoss May 28, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants


		This annex specifies how the requirements as specified in

		* EN 18222:2026 – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability



		.DPP Discovery and Composition Sequence with a Repository Service involved (see TODO_XREF:[IDTA-01002 Part 2 -- Chapter Interactions])
		.DPP Discovery and Composition Sequence with a Repository Service involved (see link:https://industrialdigitaltwin.io/aas-specifications/IDTA-01002/v3.1.2/http-rest-api/interactions.html[IDTA-01002 Part 2 -- Chapter Interactions])

	* EN 18222: 2026 – Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability
	* EN 18222:2026 – Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability

	* DPP Registry API* (EN 18222, Clause 5, Table 17) -- Registration of DPPs at the DPP Registry.
	* DPP Registry API (EN 18222, Clause 5, Table 17) -- Registration of DPPs at the DPP Registry.

	* Life Cycle API - fine granular API methods* (EN 18222, Clause 6, Table 18) -- Element-level read and update operations within a DPP.
	* Life Cycle API - fine granular API methods (EN 18222, Clause 6, Table 18) -- Element-level read and update operations within a DPP.

Conversation

BirgitBoss commented May 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

BirgitBoss May 28, 2026

Choose a reason for hiding this comment

Uh oh!

BirgitBoss May 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BirgitBoss May 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

BirgitBoss commented May 28, 2026 •

edited

Loading

BirgitBoss May 28, 2026 •

edited

Loading

BirgitBoss May 28, 2026 •

edited

Loading