<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dr. Susanne Guth-Orlowski on Medium]]></title>
        <description><![CDATA[Stories by Dr. Susanne Guth-Orlowski on Medium]]></description>
        <link>https://medium.com/@susi.guth?source=rss-184e9bf49b6f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MogWnow83BQpATTQAYgzGg@2x.jpeg</url>
            <title>Stories by Dr. Susanne Guth-Orlowski on Medium</title>
            <link>https://medium.com/@susi.guth?source=rss-184e9bf49b6f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:24:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@susi.guth/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Access Control to Digital Product Passport Data with Qualified Electronic Attestation of Attributes…]]></title>
            <link>https://medium.com/@susi.guth/access-control-to-digital-product-passport-data-with-qualified-electronic-attestation-of-attributes-60af7b6dd9bc?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/60af7b6dd9bc</guid>
            <category><![CDATA[eidas]]></category>
            <category><![CDATA[digital-product-passport]]></category>
            <category><![CDATA[access-control]]></category>
            <category><![CDATA[eu-business-wallet]]></category>
            <category><![CDATA[legal-entity-identifier]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 14:24:38 GMT</pubDate>
            <atom:updated>2026-10-30T14:10:11.216Z</atom:updated>
            <content:encoded><![CDATA[<h3>Access Control to Digital Product Passport Data with Qualified Electronic Attestation of Attributes and ODRL policy rules</h3><h3>1. Introduction</h3><p>Digital Product Passports (DPPs) become mandatory for products placed on the EU single market under several regulations, starting with Batteries in February 2027. DPPs are decentrally stored and will contain public and restricted (controlled) data. For example, detailed material composition in anode, cathode, and electrolyte can be relevant to recyclers while remaining controlled information for other parties due business confidentiality requirements. For this purpose a standardised, robust access control mechanism for digital product passports is required.</p><p>The DPP ecosystem is a decentralised system, i.e. product data stays with the economic operator. Therefore managing access to the DPP remains in the hands of the economic operator, who placed the product on the market, not necessarily the manufacturer. To follow a standardised access control approach that owners and requesters of DPP data can apply, it needs to be clearly defined, standardised, and implemented by the DPP ecosystem.</p><p>This article shows how such a decentralised access control approach for DPPs can be designed and implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8CXpnfFjF0vrGnPnKZsYw.png" /><figcaption>Figure 1: Access Control to Digital Product Passport Data with Qualified Electronic Attestation of Attributes and ODRL policy rules</figcaption></figure><h3>2. Underlying principles</h3><p>For our concept we are using Digital Company Identities, that have been established by eIDAS 1.0 <a href="https://eur-lex.europa.eu/eli/reg/2014/910/oj/eng"><strong>Regulation (EU) No 910/2014</strong></a>, and eIDAS 2.0 <a href="https://eur-lex.europa.eu/eli/reg/2024/1183/oj/eng"><strong>Regulation (EU) 2024/1183</strong></a> and are operationalised by the EU Business Wallet (EBW) regulation <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:52025PC0838">COM(2025) 838</a> and EU Digital Identity (EUDI) Wallets. Such digital identities shall be used to securely authenticate the actor that aims at accessing the DPP.</p><p>Once digitally authenticated, the economic operator can grant the requester access to the entire DPP, parts of the DPP, or can only provide statements about the product, e.g. in the way zero knowledge proofs operate. The economic operator can use additional attributes of the digital company identity credential, for the decision making, for example the company address or its business nature.</p><p>In our example, the nature of the business of the requester is a “<strong>recycling facility</strong>” that needs to understand the battery’s critical raw material composition for processing it at its end of life. We assume that the “material composition” is non-public information.</p><h3>2.1 Company Identity: EBWOID, LEI, and UN Grid</h3><p>Several approaches towards a trusted digital company identity exist, e.g. the Legal Entity Identifier (LEI), the EU Business Wallet Owner ID data, the national Business Register ID, the upcoming UN grid and others. Those approaches are shortly described in this section.</p><h3>2.1.1 EU Business Wallet Owner ID (EBWOID)</h3><p>The European Business Wallet Owner ID (formally known as Legal Person Identifier (LPID) in eIDAS 2.0) is the company identifier, defined in the <a href="https://digital-strategy.ec.europa.eu/en/policies/business-wallets">EU Business Wallet</a> Regulation. It includes, at a minimum, the <strong>official legal name</strong> of the company and a cross-border <strong>unique identifier</strong>. This unique identifier is the official business register number with a country prefix which makes the number unique in Europe. The EBWOID data looks like this:</p><blockquote><em>Official Legal Name: “</em><a href="https://4therecord.io/"><em>4TheRecord GmbH</em></a><em>”</em></blockquote><blockquote><em>Unique identifier “DER1402.HRB21047”</em></blockquote><p>Where “DE” is the prefix for Germany, “R1402” the identifier of the national register followed by the company identifier of that register “HRB21047”.</p><p>The LPID, now called EBWOID, is an accepted company identifier under <a href="https://standards.cencenelec.eu/ords/f?p=205:110:::::FSP_PROJECT:79954&amp;cs=14DC1F74D7E9F9DD3EA30959F19526334">CEN/CENELEC JTC24 DPP standards EN 18219 — Unique Identifiers</a>, which is a prerequisite to comply to the EU regulation.</p><h3>2.1.2 Legal Entity Identifier (LEI)</h3><p>The Legal Entity Identifier (LEI), as defined and operationalised by <a href="http://gleif.org/">GLEIF</a> and standardised in ISO 17442–1:2020; was originally used to verify company identity in the banking sector after the Lehman Brothers crisis (<a href="https://www.dilitrust.com/legal-entity-identifier-lei/">Dilitrust Article</a>). LEIs have the advantage that they are accepted and standardised globally also outside of the EU. A LEI includes more company details, such as who owns and represents the company, the business register ID, the entity status, etc.</p><p>The LEI is a company identifier that is accepted in <a href="https://standards.cencenelec.eu/ords/f?p=205:110:::::FSP_PROJECT:79954&amp;cs=14DC1F74D7E9F9DD3EA30959F19526334">CEN/CENELEC JTC24 DPP standards EN 18219 — Unique Identifiers</a>, which is a prerequisite to comply to the EU regulation.</p><h3>2.1.3 United Nations Grid</h3><p>The <a href="https://grid.unece.org/">UN Grid</a> is the youngest company identifier concept. It defines the register of registers on UN level. The UN GRID is a United Nations curated and member maintained list of the authoritative registrars of participating UN Member States. The GRID will enable organisations to verify whether a trade relevant credential (e.g., a commercial registration number, a property title, a trademark ownership certificate) has been issued by a valid and recognized authoritative registrar. The UN grid is not yet operational and not part of JTC 24 standards for DPP, but can play an important role in verifying company identities globally in the future.</p><h3>2.2 The National Business Register: The trusted source</h3><p>What all company identifiers have in common is that they are based on the most trusted source of company identifiers — the trusted national business register. The identifiers differs in:</p><ul><li>the <strong>legal status</strong> of the identifiers, e.g. legal compliance for European DPP via the <a href="https://standards.cencenelec.eu/ords/f?p=205:110:::::FSP_PROJECT:79954&amp;cs=14DC1F74D7E9F9DD3EA30959F19526334">CEN/CENELEC standard EN 18219</a> which currently only the EBWOID and the LEI fulfill. EBWOID will be an accepted company identity under Union Law, once the EU Business Wallets go live.</li><li>the <strong>applicable geography</strong>: e.g. EBWOID is only valid in Europe for European Companies, whereas LEIs and UN Grid identifiers are targeting global companies.</li><li><strong>the maturity</strong>, whereas LEIs are well known and established in the industry globally, EBWOIDs are a relatively new concept (but based on the known trusted national company register IDs). The UN grid concept is under development.</li></ul><p>The scenarios of access control use cases in the DPP ecosystem are numerous (See <a href="https://medium.com/@susi.guth/eu-digital-identity-wallets-and-digital-product-passports-dpps-ff96b24eeae6">EU Digital Identity Wallets and Digital Product Passports (DPPs)</a> . Especially relevant is the DPP registry regulation that allows digital identities under eIDAS 1 and under Union Law to authenticate themselves against the DPP registry (see Chapter 3).</p><h3>2.3 Qualified Electronic Attestations of Attributes (QEAA)</h3><p>A Qualified Electronic Attestation of Attributes (QEAA) under eIDAS 2.0 is a tamper-proof digital credential issued by a state-supervised<a href="https://digital-strategy.ec.europa.eu/en/policies/eu-trusted-lists"> Qualified Trust Service Provider (QTSP)</a>. It legally verifies specific personal or organizational attributes, such as address, tax ID and carries the <strong>same legal equivalence</strong> across the EU as a certified paper document with an official seal.</p><p>Technically, QEAAs come as SD-JWT VC (Selective Disclosure for JSON Web Token-based Verifiable Digital Credentials), ISO/IEC 18013–5 (mdoc) or <a href="https://www.w3.org/TR/vc-data-model-2.0/">W3C Verifiable Credentials (VCDM)</a>. W3C Verifiable Credentials for EBWOID and LEI that can be used by EU Business Wallets are currently being defined. Please find first drafts by <a href="https://medium.com/u/9e5c4424bb8b">Spherity</a>, the technical partner of the <a href="https://www.bundesanzeiger-verlag.de/evidenzwesen/eubw/">Bundesanzeiger Verlag</a> who runs the German National Business Register here: <a href="https://oid.spherity.com/oid">Company Identity Vocabulary</a>. Those examples schemes are later used in this article. NOTE: These specifications are not standardised yet.</p><h3>2.3.1 LEI QEAAs</h3><p>In order to be legally binding under eIDAS 2.0 an LEI verifiable credential needs to be issued as a QEAA by a trusted, accredited GLEIF local operating unit (LOU) to the business wallet of the requester. LOUs have the obligation to check the national business register of the requestor’s residence country.</p><h3>2.3.2 EBWOID QEAAs</h3><p>The EBWOID credential is also issued by the national business register, again the Bundesanzeiger Verlag has that role in Germany, in the form of a QEAA. The current <a href="https://www.webuildconsortium.eu/">WE BUILD</a> specification defines SD-JWT VC, a digitally signed, JWT-based verifiable credential delivered into the business wallet. W3C Verifiable Credentials are also allowed, but their encoding is not yet specified. However, internationally W3C Verifiable Credentials are often used in Business-to-Business interactions and Supply Chain Data exchange, <a href="https://untp.unece.org/docs/specification/VerifiableCredentials">see also the United Nations Transparency Protocol</a>. It seems that in this B2B context W3C Verifiable Credentials will prevail.</p><h3>2.3.3 Additional Qualified Attributes</h3><p>The EBWOID credential currently only includes the company name and the EU Business Wallet Owner ID. The LEI credential can provide additional information, such as company address, the legal representative of the company or optionally the nature of the business in form of the <a href="https://ec.europa.eu/eurostat/web/nace">NACE code</a> or the United Nations <a href="https://profiles.ihe.net/PCC/ODH/CodeSystem-ISICRev4.html">International Standard Industrial Classification Codes</a> (ISIC) Rev. 4.</p><blockquote>Note, the European NACE code has been derived from the UN ISIC but is not fully congruent.</blockquote><p>In our example the economic operator additionally checks the nature of the requestor’s business to grant access to the non-public DPP data. That means, the economic operator verifies if the requestor actually is a battery <strong>repair facility</strong>. This information can be encoded in the LEI credential by indicating the NACE code which is available to all national business registers. The NACE code of a battery recycler is “38.32”.</p><p>Potentially, additional qualified attributes can also be added to the EBWOID QEAA.</p><h3>3. Authentication requirements of the DPP Registry Regulation</h3><p>The previously explained identifiers and mechanisms have already been chosen to manage the access against the DPP registry and are thus well suitable for a general access control approach in the DPP ecosystem.</p><p>The respective regulation that defines this requirement for getting access to the DPP registry is the DPP Registry Implementing <a href="https://eur-lex.europa.eu/eli/reg_impl/2026/1778/oj/eng">Regulation EU 2026/1778 </a>(see below). The DPP registry allows two means of authentication:</p><ol><li>A <strong>Qualified Electronic Seal</strong> (QES) supported by a qualified certificate for electronic seal issued by a Qualified Trust Service Provider (QTSP) pursuant to regulation EU 910/2014 (eIDAS 1.0). The QES comes in the form of an x.509 certificate. Note: It is likely that this mechanism will be dominant also for non-EU companies until EU Business Wallets are operational.</li><li>A <strong>Qualified Electronic Attestation of Attributes </strong>(QEAA) issued by a QTSP under Union Law. This can be an attestation under</li></ol><ul><li>EU 2024/1183 (eIDAS 2.0)</li><li>Or under the upcoming EU Business Wallet Regulation with a valid EU <strong>Business Wallet Owner ID</strong> data (EBWOID). EU Business Wallets (EBW) are an accepted means of authentication once the EBW becomes Union Law. Adoption of the EWB is expected in Q4/2026 and in force by Mid 2028 (indicative timeline).</li><li>For non-EU companies, the <strong>Legal Entity Identity (LEI)</strong> can also suffice when issued as an qualified electronic attestation of attributes by a QTSP.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*L5ou6CZ9FWXQXgY3Bq_RGA.png" /><figcaption><em>Figure 2: Extract from the DPP registry Implementing regulation</em></figcaption></figure><p>For signing a DPP, <strong>a qualified electronic attestation of attributes is not required, a low security level such as substantial or low assurance level is sufficient currently</strong>. Binding the electronic signature to a company is currently not defined /required in the CEN/CENELEC JTC24 standards. The Standard EN18246 only defines that an “electronic signature” needs to be used. It is expected that the assurance level for DPPs will be defined in a separate implementing regulation.</p><p>From the DPP regulation we see that Qualified Electronic Seals can be used to authenticate against the DPP registry. However, the process is mainly manual. With the European Business Wallet and Qualified Attestations of Attributes on the horizon the authentication and authorization in the DPP ecosystems will be automated. Therefore, it is important to push forward the definition of the EBWOID credential and an LEI credential to service EU and non-EU companies with an <strong>automated electronic authentication means. </strong>EU business wallets and other non-EU wallets are<strong> </strong>incorporating Wallet-to-Wallet communication protocols, such as <a href="https://openid.net/sg/openid4vc/">OIDC4VC / VP</a> or <a href="https://identity.foundation/didcomm-messaging/spec/v2.1/">DIDComm</a>, to enable such automated electronic data exchange.</p><h3>4. Identity-, role-, attribute based access control for DPPs</h3><p>Access to Digital Product Passports can be based on the company identity, based on the business nature or role, country or based on other attributes that have been issued in the QEAA or on a combination of those.</p><p>The<a href="https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng"> ESPR mentions</a> the following two main groups with extended access right to controlled DPP data:</p><ul><li><strong>Market Surveillance Authorities: </strong>Those are market surveillance authorities, customs and the European Commission or any organisation acting on their behalf that must verify regulatory compliance, for example identifying Substances of Concern in products that may pose risks to European citizens.</li><li><strong>Actors with legitimate interest: </strong>Those are professional repairers, refurbishers, remanufacturers, and recyclers, that need detailed material composition, dismantling, or disposal data to perform appropriate R-strategy processes.</li></ul><p><strong>Access control based on the EBWOID:</strong> The EBWOID enabled economic operators to maintain a white list of actors with legitimate interest or market surveillance authorities that get access to the controlled DPP data.</p><p>While this mechanism is already very effective, it has the prerequisites that the economic operator needs to know the actor that is trying to access the DPP beforehand. In global supply chains and international recycling and reuse of products this mechanism does not scale. Knowing the business nature of a business can additionally help the decision whether to grant or deny access to the DPP data.</p><p><strong>Access control based on the role/ NACE code.</strong> If the NACE code of the company has been part of the Company Identifier QEAA, such as the LEI QEAA, the access can be granted based on the consumer’s business nature or role in the industry. This has the advantage that the economic operator does not need to know the requester before granting access to the DPP.</p><p><strong>Access Control based Market Surveillance Authority ID. </strong>A Market Surveillance Authority (MSA) is a government body responsible for ensuring that products placed on the market comply with safety, health, and environmental standards. At European level, these authorities are registered in the<a href="https://webgate.ec.europa.eu/single-market-compliance-space/market-surveillance"> Information and Communication System for Market Surveillance (ICSMS<strong>)</strong></a>, where each authority is assigned a <strong>unique Authority ID</strong>.</p><p>For example, the German MSA “<a href="https://webgate.ec.europa.eu/single-market-compliance-space/market-surveillance/ma-authorities/1458?filter=countryId:1003,t:1,city:mainz,responsabilities:GAA0704MZ;GAA0609WI;GAA0610F-HE">Bundesnetzagentur</a>” has the EU unique Authority ID №1458. This system provides a solid foundation for identifying and authenticating MSAs. If this unique Authority ID would be issued as QEAA by a trusted issuer, it could also be used as ID/role credential for Market Surveillance Authorities.</p><p>Market surveillance authorities are public sector bodies, which will get a EBWOID credential and MUST use the EU Business Wallet starting from Mid 2028 (indicative timeline).</p><p><strong>Notified bodies </strong>are registered in a similar manner like MSA (see<a href="https://webgate.ec.europa.eu/single-market-compliance-space/home"> Single Market Compliant Space)</a> and would also profit from a QEAA that attests their MSA role.</p><blockquote>The above concepts show that access to DPPs can be implemented by existing identification schemes, the upcoming EU Business Wallet and existing law that legally binds company identifiers and roles to QEAAs.</blockquote><h3>Information Flow: Grant or deny access to the DPP</h3><p>Below please find an information flow diagram that shows the handshake for DPP access control using one or more QEAAs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*DfQ5zrBj8c4M9J89_mzi9w.png" /><figcaption><em>Figure 3: Information Flow Diagram: Grant or deny access to the DPP</em></figcaption></figure><p>High level access control flow for controlled DPP data</p><ol><li>A <strong>third party</strong> requests access to controlled DPP data</li><li>The <strong>economic operator</strong> requests a <strong>company identity attestation that is eligible under EU Law.</strong></li><li>The third party provides e.g. EU <strong>Business Wallet Owner ID data</strong>, <strong>LEI</strong>, or an equivalent company credential eligible under EU Law.</li><li>The economic operator verifies the identity attestation</li><li>Upon successful authentication, the operator potentially requests additional evidence such as the <strong>Market Surveillance Authority ID</strong>, or the <strong>NACE code</strong>, depending on the use case.</li><li>The third party provides the required attestation</li><li>The economic operator verifies this second attestation.</li><li>Based on the validity of the provided attestations access is <strong>granted or denied to the controlled DPP data.</strong></li></ol><p>9. If the initial identity verification fails, access is rejected immediately.</p><h3>5. The Access Control Policy Engine</h3><p>As described, the economic operator can use e.g. the LEI credential for certain attributes (e.g. the NACE code). Such checks should be standardised and clearly defined, so that all economic operators can act in the same way and also actors in battery recycling can rely on a standardised automated process.</p><p>For this purpose we are formalising the access policy using an <a href="https://www.w3.org/TR/odrl-model/"><strong>Open Digital Rights Language</strong> (<strong>ODRL) </strong></a>policy. ODRL is a W3C Recommendation for a rights expression language for rights and duties in an electronic readable and processable language. Addionally, Gaia-X has defined an <a href="https://gitlab.com/gaia-x/lab/policy-reasoning/odrl-vc-profile/">ODRL profile for Verifiable Credentials</a> which we are using in our example. We use ODRL to say: “A battery recycler must show a valid LEI QEAA credential AND the nature of his business must be battery recycling so that he gets access to the material composition data of a DPP.”</p><p>The ODRL right expression for this example has four elements:</p><ul><li><strong>Protected asset:</strong> the criticalRawMaterials field of a DPP</li><li><strong>Assigner:</strong> the economic operator that controls the DPP</li><li><strong>Requesting party:</strong> a legal entity, in our example, the battery recycler</li><li><strong>Condition:</strong> the requesting party must present a valid LEI Credential containing a NACE code that includes battery recyclers. Approved NACE codes are: 1. <strong>E38.12</strong>: Collection of hazardous waste, 2. <strong>E38.22</strong>: Treatment and disposal of hazardous waste, 3. <strong>E38.32</strong>: Recovery of sorted materials</li></ul><p>The logical rule is:</p><pre>IF LegalEntityIdentityCredential is valid<br>AND Legal entity NACE code ∈ approved NACE codes<br>THEN permit access to the criticalRawMaterials data<br>ELSE deny access</pre><p><strong>Note:</strong> For the sake of clarity and brevity, several other steps that need to be performed prior to evaluation are omitted here, such as verifying the LEI credential issuer and its authority to issue the LEI credential.</p><h3>6. Bring it together: ODRL policies, LEI credential, and DPP</h3><p>A <strong>Legal Entity Identity Credential</strong> and an <strong>Open Digital Rights Language</strong> (<strong>ODRL) policy</strong> can be combined to manage the access control to a <strong>Digital Product Passport Credential.</strong></p><p>Combining ODRL policies and LEI credentials framework has the advantage that ODRL expresses the access control policy, while credential verification remains external to ODRL. That separation aligns with how ODRL was designed and allows flexibility to adapt and extend access control rules without the need to change the authentication and authorisation concept as a whole:</p><p><strong>Overall principle: </strong>QEAAs provide trusted evidence about the requesting organization, a resource or a representative, while ODRL expresses the authorization rule(s).</p><p>The ODRL policy engine therefore does not need to perform credential verification itself. A credential-verification component verifies the credential and provides the relevant claims to the ODRL policy engine.</p><p>For an introduction to DPP use cases and access-control requirements, see the Medium article:<a href="https://medium.com/p/285d27e990cf?utm_source=chatgpt.com"> DPP use cases and access control</a></p><h3>6. 1 The DPP Credential</h3><p>The remainder of this document shows a DPP that is issued as W3C Verifiable Credential that includes product data, of which the material composition is worth protecting. Then we define that access control rule that we would like to apply to the DPP verifiable credential. This rule is then translated into ODRL. When accessing the DPP credential the requester has to substantiate the request with a Legal Entity Identity credential issued by a QTSP. The DPP issuer then applies the standard rule defined in ODRL to make a decision on giving the requester access to the DPP or not. In our example, the DPP issuer / economic operator would like to give access to the DPP, if the DPP requestor has a company objective that is “recycling”. In concrete words the company identity credential needs to contain the NACE code 38.32 “recycler”.</p><p>The example Battery Passport is the following W3C Verifiable Credential Specification, which is an accepted format at per EN 18246. It follows the current <a href="https://single-market-economy.ec.europa.eu/document/download/cd1e5e6c-4a4a-4b99-995a-49eb6916187e_en?filename=Digital%20Batteries%20Passport%20-%20data%20point%20by%20category.pdf">Battery Data Guidelines</a> of the European Commission and it is cryptographically valid.</p><pre>{<br>  &quot;@context&quot;: [<br>    &quot;https://www.w3.org/2018/credentials/v1&quot;,<br>    &quot;https://w3id.org/security/suites/ed25519-2020/v1&quot;,<br>    &quot;https://dpp.4therecord.io/contexts/battery-passport-v1.jsonld&quot;<br>  ],<br>  &quot;id&quot;: &quot;https://dpp.4therecord.io/b0001/dpp.json&quot;,<br>  &quot;type&quot;: [<br>    &quot;VerifiableCredential&quot;,<br>    &quot;DigitalProductPassportCredential&quot;<br>  ],<br>  &quot;issuer&quot;: &quot;did:web:4therecord.io&quot;,<br>  &quot;issuanceDate&quot;: &quot;2026-05-01T00:00:00Z&quot;,<br>  &quot;credentialSubject&quot;: {<br>    &quot;id&quot;: &quot;did:web:4therecord.io:b0001&quot;,<br>    &quot;batteryPassportIdentifier&quot;: &quot;did:web:4therecord.io:b0001&quot;,<br>    &quot;batteryIdentifier&quot;: &quot;4TRVFP-INV-2025-0001&quot;,<br>    &quot;responsibleEconomicOperator&quot;: {<br>      &quot;name&quot;: &quot;4TR VoltForce GmbH&quot;,<br>      &quot;identifier&quot;: &quot;urn:iso15459:4TRVoltForceManufacturerID&quot;,<br>      &quot;role&quot;: &quot;Manufacturer and passport registrant&quot;<br>    },<br>    &quot;manufacturer&quot;: {<br>      &quot;name&quot;: &quot;4TR VoltForce GmbH&quot;,<br>      &quot;identifier&quot;: &quot;urn:iso15459:4TRVoltForceManufacturerID&quot;,<br>      &quot;postalAddress&quot;: &quot;Hafenstrasse 24, 45127 Essen, Germany&quot;,<br>      &quot;singleContactPoint&quot;: &quot;Battery Product Compliance Department&quot;<br>    },<br>    &quot;manufacturerIdentifier&quot;: &quot;urn:iso15459:4TRVoltForceManufacturerID&quot;,<br>    &quot;manufacturingLocation&quot;: &quot;Essen, Germany&quot;,<br>    &quot;manufacturingDate&quot;: &quot;2025-02&quot;,<br>    &quot;batteryCategory&quot;: &quot;Electric vehicle battery&quot;,<br>    &quot;modelIdentification&quot;: &quot;VFP City 24 NMC&quot;,<br>    &quot;serialNumber&quot;: &quot;4TRVFP-INV-2025-0001&quot;,<br>    &quot;batteryMassKg&quot;: 150.75,<br>    &quot;ratedCapacityAh&quot;: 120,<br>    &quot;nominalEnergyKWh&quot;: 24,<br>    &quot;batteryChemistry&quot;: &quot;Lithium-ion Nickel-Manganese-Cobalt&quot;,<br>    &quot;hazardousSubstances&quot;: [<br>      {<br>        &quot;name&quot;: &quot;Lithium hexafluorophosphate&quot;,<br>        &quot;location&quot;: &quot;Electrolyte&quot;<br>      },<br>      {<br>        &quot;name&quot;: &quot;Organic carbonate solvents&quot;,<br>        &quot;location&quot;: &quot;Electrolyte&quot;<br>      }<br>    ],<br>    &quot;usableExtinguishingAgent&quot;: &quot;Water for external cooling by trained responders under an applicable emergency response plan&quot;,<br>    &quot;criticalRawMaterials&quot;: [<br>      {<br>        &quot;name&quot;: &quot;Lithium&quot;,<br>        &quot;massPercent&quot;: 2.4<br>      },<br>      {<br>        &quot;name&quot;: &quot;Cobalt&quot;,<br>        &quot;massPercent&quot;: 1.2<br>      },<br>      {<br>        &quot;name&quot;: &quot;Nickel&quot;,<br>        &quot;massPercent&quot;: 7.8<br>      }<br>    ],<br>    &quot;renewableContentSharePercent&quot;: 12,<br>    &quot;voltage&quot;: {<br>      &quot;minimumV&quot;: 160,<br>      &quot;nominalV&quot;: 200,<br>      &quot;maximumV&quot;: 235,<br>      &quot;relevantTemperatureRangeC&quot;: [<br>        -20,<br>        45<br>      ]<br>    },<br>    &quot;originalPowerCapabilityW&quot;: 60000,<br>    &quot;powerLimits&quot;: {<br>      &quot;maximumContinuousDischargeW&quot;: 40000,<br>      &quot;maximumPeakDischargeW&quot;: 60000,<br>      &quot;maximumChargeW&quot;: 24000,<br>      &quot;relevantTemperatureRangeC&quot;: [<br>        10,<br>        35<br>      ]<br>    },<br>    &quot;expectedLifetimeCycles&quot;: 1500,<br>    &quot;expectedLifetimeReferenceTest&quot;: &quot;25 °C; 0.5 C charge/discharge; 80% depth of discharge; 80% remaining capacity endpoint&quot;,<br>    &quot;capacityExhaustionThresholdPercent&quot;: 70,<br>    &quot;nonOperatingTemperatureRangeC&quot;: [<br>      -20,<br>      45<br>    ],<br>    &quot;nonOperatingTemperatureReferenceTest&quot;: &quot;Storage at 50% state of charge for 30 days&quot;,<br>    &quot;warrantyPeriod&quot;: &quot;2030-02&quot;,<br>    &quot;initialRoundTripEnergyEfficiencyPercent&quot;: 94,<br>    &quot;roundTripEnergyEfficiencyAtHalfCycleLifePercent&quot;: 90,<br>    &quot;initialCellInternalResistanceMilliOhm&quot;: 1.8,<br>    &quot;initialPackInternalResistanceMilliOhm&quot;: 65,<br>    &quot;cycleLifeTestCRate&quot;: 0.5,<br>    &quot;markingRequirements&quot;: {<br>      &quot;separateCollectionSymbol&quot;: &quot;Crossed-out wheeled bin&quot;,<br>      &quot;cadmiumOrLeadSymbol&quot;: &quot;Not applicable to the synthetic composition&quot;<br>    },<br>    &quot;wasteBatteryInformation&quot;: {<br>      &quot;wastePrevention&quot;: &quot;Follow the vehicle manufacturer&#39;s charging and storage instructions; assess suitable batteries for reuse or repurposing through qualified channels.&quot;,<br>      &quot;separateCollection&quot;: &quot;Keep waste EV batteries out of unsorted municipal waste and use separate collection.&quot;,<br>      &quot;collectionAndTreatment&quot;: &quot;Return through an authorised vehicle battery take-back or collection channel for assessment and treatment.&quot;,<br>      &quot;safety&quot;: &quot;Do not open or handle a damaged high-voltage pack; isolate it and contact qualified personnel for safe handling.&quot;,<br>      &quot;symbolMeaning&quot;: &quot;The crossed-out wheeled bin means separate collection is required.&quot;,<br>      &quot;substanceImpacts&quot;: &quot;Electrolyte and metal compounds can harm people and the environment if the battery is damaged or improperly discarded.&quot;<br>    },<br>    &quot;renderMethod&quot;: {<br>      &quot;type&quot;: &quot;HtmlRenderMethod2026&quot;,<br>      &quot;url&quot;: &quot;https://dpp.4therecord.io/b0001/index.html&quot;<br>    }<br>  },<br>  &quot;proof&quot;: {<br>    &quot;type&quot;: &quot;Ed25519Signature2020&quot;,<br>    &quot;created&quot;: &quot;2026-10-27T16:21:03Z&quot;,<br>    &quot;verificationMethod&quot;: &quot;did:web:4therecord.io#key-1&quot;,<br>    &quot;proofPurpose&quot;: &quot;assertionMethod&quot;,<br>    &quot;proofValue&quot;: &quot;zsccHCpCQ4k43Juu73mFsD7c35gsSsmVGyBdoNGstcXfbuq44zB5XgkwiDAa6TyhuKtYiiCRb6L3Wqe8eeed51w6&quot;<br>  }<br>}</pre><p>The ODRL policy specifically targets:</p><pre>dpp.json#credentialSubject.criticalRawMaterials</pre><p>If the ODRL policy is met, the economic operator grants access to the controlled criticalRawMaterials data.</p><h3>6.2. The Legal Entity Identity (LEI) Credential</h3><p>The requesting organization presents the following Legal Entity Identity Credential:</p><pre>{<br>  &quot;@context&quot;: [<br>    &quot;https://www.w3.org/ns/credentials/v2&quot;,<br>    &quot;https://oid.spherity.com/contexts/eucc/v1&quot;<br>  ],<br>  &quot;type&quot;: [<br>    &quot;VerifiableCredential&quot;,<br>    &quot;EuCompanyCertificate&quot;<br>  ],<br>  &quot;id&quot;: &quot;urn:uuid:f086cced-1153-4540-993b-b4d52ca499c2&quot;,<br>  &quot;validFrom&quot;: &quot;2019-12-03T12:19:52Z&quot;,<br>  &quot;validUntil&quot;: &quot;2029-12-03T12:19:52Z&quot;,<br>  &quot;issuer&quot;: &quot;did:key:z6MkiY62766b1LJkExWMsM3QG4WtX7QpY823dxoYzr9qZvJ3&quot;,<br>  &quot;credentialSubject&quot;: {<br>    &quot;id&quot;: &quot;did:key:z6Mki562766b1LJkExWMsM3QG4WtX7QpY823dxoYzr9qZvJ2&quot;,<br>    &quot;type&quot;: [<br>      &quot;LegalPerson&quot;<br>    ],<br>    &quot;legalName&quot;: {<br>      &quot;@language&quot;: &quot;de&quot;,<br>      &quot;@value&quot;: &quot;Flower Power AG&quot;<br>    },<br>    &quot;legalIdentifier&quot;: &quot;DEPLPOAG.123456789&quot;,<br>    &quot;legalFormType&quot;: &quot;Aktiengesellschaft&quot;,<br>    &quot;registeredAddress&quot;: {<br>      &quot;addressArea&quot;: &quot;Friedrichswerder&quot;,<br>      &quot;adminUnitL1&quot;: &quot;Germany&quot;,<br>      &quot;adminUnitL2&quot;: &quot;Berlin&quot;,<br>      &quot;locatorDesignator&quot;: &quot;33&quot;,<br>      &quot;postCode&quot;: 10119,<br>      &quot;postName&quot;: &quot;Berlin&quot;,<br>      &quot;thoroughfare&quot;: &quot;Unter den Linden&quot;<br>    },<br>    &quot;registrationDate&quot;: &quot;2024-07-02T09:49:49Z&quot;,<br>    &quot;legalEntityStatus&quot;: &quot;Active&quot;,<br>    &quot;legalRepresentative&quot;: [<br>      {<br>        &quot;legalEntityId&quot;: &quot;did:key:z6Mki562766b1LJkExWMsM3QG4WtX7QpY823dxoYzr9qZvJ2&quot;,<br>        &quot;role&quot;: &quot;CEO&quot;,<br>        &quot;scopeOfRepresentation&quot;: &quot;Alone&quot;<br>      },<br>      {<br>        &quot;legalEntityId&quot;: &quot;did:key:z6Mki562766b1LJkExWMsM3QG4WtX7QpY823dxoYzr9qZvJ1&quot;,<br>        &quot;role&quot;: &quot;Director&quot;,<br>        &quot;scopeOfRepresentation&quot;: &quot;Jointly&quot;<br>      }<br>    ],<br>    &quot;legalEntityActivity&quot;: {<br>      &quot;type&quot;: &quot;E38.32&quot;,<br>      &quot;code&quot;: &quot;Recycling&quot;,<br>      &quot;businessDescription&quot;: &quot;Recovery of sorted materials&quot;<br>    },<br>    &quot;contactPoint&quot;: {<br>      &quot;contactPage&quot;: &quot;https://flower-power.com&quot;<br>    }<br>  }<br>}</pre><blockquote>Note: This LEI credential does not contain the necessary proof of a QTSP that would be required to validate the credential in an operational environment.</blockquote><p>The important claim part required for authorization is:</p><pre>…<br>&quot;legalEntityActivity&quot;: {<br>  &quot;type&quot;: &quot;E38.32&quot;,<br>  &quot;code&quot;: &quot;RECYCLING&quot;,<br>  &quot;businessDescription&quot;: &quot;Recovery of sorted materials&quot;<br>}<br>…</pre><p>The ODRL policy evaluates the type claim:</p><pre>$.credentialSubject.legalEntityActivity.type</pre><p>against the approved NACE codes.</p><h3>6.3. The ODRL Policy</h3><p>The corresponding policy can be expressed as shown below. Its semantic meaning is:</p><blockquote>The economic operator did:web:4therecord.io grants permission to read the material composition data of the DPP to a legal person whose verified Legal Entity Credential contains one of the approved NACE codes E38.32, E38.12, or E38.22.</blockquote><p>If the condition is satisfied, the requester is permitted to read the criticalRawMaterials field of the DPP credential.</p><p>This example illustrates the key architectural separation: Verifiable Credentials provide the trusted evidence and identity layer; ODRL provides the authorization policy layer.</p><pre>{<br>  &quot;@context&quot;: [<br>    &quot;http://www.w3.org/ns/odrl.jsonld&quot;,<br>    {<br>      &quot;ovc&quot;: &quot;https://w3id.org/gaia-x/ovc/1/&quot;<br>    }<br>  ],<br>  &quot;@type&quot;: &quot;Offer&quot;,<br>  &quot;uid&quot;: &quot;https://example.com/policy/dpp-material-composition&quot;,<br>  &quot;permission&quot;: [<br>    {<br>      &quot;@type&quot;: &quot;Permission&quot;,<br>      &quot;target&quot;: &quot;https://did.4therecord.io/b0001/dpp.json#credentialSubject.materials&quot;,<br>      &quot;action&quot;: &quot;http://www.w3.org/ns/odrl/2/read&quot;,<br>      &quot;assigner&quot;: &quot;did:web:4therecord.io&quot;,<br>      &quot;ovc:constraint&quot;: [<br>        {<br>          &quot;ovc:leftOperand&quot;: &quot;$.credentialSubject.legalEntityActivity.type&quot;,<br>          &quot;operator&quot;: &quot;http://www.w3.org/ns/odrl/2/isAnyOf&quot;,<br>          &quot;rightOperand&quot;: [<br>            &quot;E38.32&quot;,<br>            &quot;E38.12&quot;,<br>            &quot;E38.22&quot;<br>          ],<br>          &quot;ovc:credentialSubjectType&quot;: &quot;EuCompanyCertificate&quot;<br>        }<br>      ]<br>    }<br>  ]<br>}</pre><h3>7. Benefits of the modular approach</h3><p>This approach provides several important benefits for DPP ecosystems:</p><ul><li><strong>Attribute-based access control.</strong> Access can be granted based on verified characteristics of an organization rather than maintaining individual whitelists.</li><li><strong>Fine-grained access.</strong> The policy can protect individual DPP attributes, such as criticalRawMaterials, rather than exposing the complete DPP.</li><li><strong>Interoperability.</strong> Legal identity credentials can be used across different DPP services, while ODRL provides a common policy language.</li><li><strong>Scalability.</strong> A DPP provider can define eligibility criteria such as approved NACE codes without knowing every potential recycler or other downstream actor in advance.</li><li><strong>Separation of concerns.</strong> Credential infrastructure handles authentication and verification; ODRL handles authorization.</li><li><strong>Policy flexibility.</strong> The economic operator can change which NACE codes are authorized without changing the underlying identity credential.</li><li><strong>Selective Disclosure.</strong> Only the required attributes (by the ODRL Policy) are requested, the requesting party does not need to disclose their full organizational profile.</li><li><strong>Trusted Issuers.</strong> The assigner of the policy can choose their own trusted credential issuers. Depending on the jurisdiction and domain, a state or EU-wide trusted list can also be leveraged to delegate trust verification.</li></ul><h3>8. Acknowledgements</h3><p>This concept has greatly benefited from discussions with experts in the field of DPPs and digital identity, including:</p><p><strong>Dennis Hannemann and Louise de Laat (Bundesanzeiger Verlag), Steffen Schwalm (msg), Yassir Sellami (Gaia-X).</strong></p><p>I welcome any constructive feedback and discussion from practitioners and stakeholders working on DPPs, digital identity, and regulatory innovation.</p><p>Updates:</p><p><strong>October 19th, 2026</strong>. The article has been updated with the latest<em> </em><a href="https://single-market-economy.ec.europa.eu/document/download/cd1e5e6c-4a4a-4b99-995a-49eb6916187e_en?filename=Digital%20Batteries%20Passport%20-%20data%20point%20by%20category.pdf"><em>“Guidance Document: Digital Batteries Passport — data points by category”</em></a></p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Listen to this podcast on Digital Identity Wallets and Digital Product Passports:</p><p>Please also check out our podcast on Digital Product Passport and EU Business Wallets with<a href="https://medium.com/u/184e9bf49b6f?source=post_page---user_mention--ff96b24eeae6---------------------------------------"> Dr. Susanne Guth-Orlowski</a> and<a href="https://medium.com/u/2d7ca4c61292?source=post_page---user_mention--ff96b24eeae6---------------------------------------"> Carsten Stöcker</a> here:</p><p>For reading <strong>digital product passport news</strong>, please follow<a href="https://www.linkedin.com/in/sguth/"> Susanne’s</a> and the<a href="https://www.linkedin.com/company/"> 4TheRecord</a> LinkedIn page.</p><p>For <strong>trainings </strong>on digital product passports, please check out our<a href="http://4therecord.io/training"> training programm</a> on<a href="http://4therecord.io/"> 4therecord.io</a>.</p><p>For more <strong>podcasts </strong>on Digital Product Passports, please follow us on<a href="https://www.youtube.com/playlist?list=PLT-WX3P9sOtfJi6YEenmYhcZs8RCepAP6"> YouTube</a>,<a href="https://open.spotify.com/show/6opb75RSIT1tgNJGqMjgzH"> Spotify</a> ,<a href="https://podcasts.apple.com/zw/podcast/spherity-podcast/id1621254669"> iTunes</a> or the<a href="https://podcast.app/digital-product-passport-insights-a-4therecord-podcast-p6260998"> podcast app</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60af7b6dd9bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Access Control for Digital Product Passports using EU Business Wallets]]></title>
            <link>https://medium.com/@susi.guth/access-control-for-digital-product-passports-using-eu-business-wallets-285d27e990cf?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/285d27e990cf</guid>
            <category><![CDATA[espr]]></category>
            <category><![CDATA[access-control]]></category>
            <category><![CDATA[verifiable-credentials]]></category>
            <category><![CDATA[digital-product-passport]]></category>
            <category><![CDATA[european-business-wallet]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 17:27:59 GMT</pubDate>
            <atom:updated>2026-06-25T08:54:14.105Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>The<a href="https://digital-strategy.ec.europa.eu/en/policies/business-wallets"> <strong>EU Business Wallet</strong></a><strong> proposal</strong> defines several important<a href="https://medium.com/@susi.guth/eu-digital-identity-wallets-and-digital-product-passports-dpps-ff96b24eeae6"> use cases for <strong>Digital Product Passports (DPPs)</strong></a>, one of which is <strong>access control for controlled (non-public) DPP data</strong>.*</p><blockquote>“The Digital Product Passport (DPP), central to the EU’s circular economy agenda, depends on trusted access to conformity and sustainability data. The <strong>Business Wallets</strong> proposal can prove legal identity and any granted access rights, allow conformity declarations to be signed and sealed, and ensure product data is exchanged securely and verifiably across borders.” (see <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52025PC0838">Proposal for a <strong>REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on the establishment of European Business Wallets</strong></a><strong>)</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jzdzq0PLJmTDWFM-v7HF7g.png" /><figcaption>Figure 1: How does access control to DPPs work with wallets?</figcaption></figure><p>While many DPP attributes are publicly accessible — supporting informed consumer decisions and proper end-of-life handling — certain types of data are subject to access restrictions due to <strong>business confidentiality</strong>. These include:</p><ul><li><strong>Material composition data</strong></li><li><strong>Supply chain due diligence information</strong></li></ul><p>At the same time, specific stakeholders require access to this restricted data to perform their roles effectively. The<a href="https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng"> ESPR mentions</a> the following two main groups with extended access right to controlled DPP data:</p><ul><li><strong>Market Surveillance Authorities: </strong>Those are market surveillance authorities, customs and the European Commission or any organisation acting on their behalf that must verify regulatory compliance, for example identifying <strong>Substances of Concern</strong> that may pose risks to European citizens.</li><li><strong>Actors with legitimate interest: </strong>Those are professional repairers, refurbishers, remanufacturers, and recyclers, that need detailed material composition, dismantling, or disposal data to perform appropriate R-strategy processes.</li></ul><p>To enable secure access to controlled DPP data, these actors must be <strong>reliably identified and authenticated</strong>.</p><h3>Identification of Market Surveillance Authorities</h3><p>A <strong>Market Surveillance Authority (MSA)</strong> is a government body responsible for ensuring that products placed on the market comply with safety, health, and environmental standards.</p><p>At European level, these authorities are registered in the<a href="https://webgate.ec.europa.eu/single-market-compliance-space/market-surveillance"> <strong>Information and Communication System for Market Surveillance (ICSMS)</strong></a>, where each authority is assigned a <strong>unique Authority ID</strong>. For example the German MSA “<a href="https://webgate.ec.europa.eu/single-market-compliance-space/market-surveillance/ma-authorities/1458?filter=countryId:1003,t:1,city:mainz,responsabilities:GAA0704MZ;GAA0609WI;GAA0610F-HE">Bundesnetzagentur</a>” has the EU unique Authority ID no. 1458. This system provides a solid foundation for identifying and authenticating MSAs.</p><p>(Notified bodies are registered in a similar manner (see<a href="https://webgate.ec.europa.eu/single-market-compliance-space/home"> Single Market Compliant Space)</a>)</p><h3>Identification of Actors with Legitimate Interest</h3><p>The eligibility of economic actors can be determined using<a href="https://ec.europa.eu/eurostat/web/nace"> <strong>NACE codes</strong></a> (<em>Nomenclature of Economic Activities</em>), a standardized European classification of business activities. NACE codes can be used to assess whether a company qualifies as an <strong>“actor of legitimate interest”</strong> for accessing controlled DPP data.</p><p>For example:<br> A company with the NACE code <strong>38.32 (recovery of sorted materials / recycling)</strong> should be allowed to access <strong>battery material composition data</strong>.</p><h3>Towards a Standardized Approach for DPP Access Control</h3><p>Currently, there is <strong>no standardized mechanism</strong> to manage access control for DPPs in the decentralized setup. We propose addressing this gap through the use of <strong>electronic attestations of attributes issued and verified by EU Business Wallets.</strong></p><blockquote>Excursus: Electronic Attestations of Attributes</blockquote><blockquote>Within the<a href="https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/694487738/EU+Digital+Identity+Wallet+Home"> <strong>EU Digital Identity (EUDI)</strong></a> framework and the<a href="https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/694487738/EU+Digital+Identity+Wallet+Home"> <strong>EU Business Wallet</strong></a><strong> initiative</strong>, an <strong>electronic attestation of attributes</strong> (e.g. in the form of a W3C verifiable credential) refers to an electronically <strong>signed document </strong>issued by a<strong> trusted authority</strong> to individuals or organizations. Examples of such attestations include:</blockquote><blockquote>- A <strong>driver’s license</strong> issued by the Ministry of Transport to the personal EUDI Wallet</blockquote><blockquote><strong>- Business Wallet Owner ID data</strong> issued by the national business register to the Business Wallet to identify a company in the EU.</blockquote><blockquote><strong>- Legal Entity Identifier (LEI)</strong> attestations issued by Qualified LEI issuer to the Business Wallet to identify companies worldwide.</blockquote><h3>Required Infrastructure</h3><p>To standardize access control for DPPs using <strong>EU Digital Identity and EU Business Wallets</strong>, several infrastructure components are required:</p><h4>1. Issuance of Company Attribute Attestations</h4><p>Trusted authorities (e.g. business registers such as <strong>Bundesanzeiger Verlag</strong> in Germany) must be enabled to standardise and issue <strong>attestations </strong>that include <strong>NACE codes. </strong>The Bundesanzeiger Verlag is <strong>c</strong>urrently it is already preparing to issue Business Wallet Owner ID data or a verifiable Legal Entity Identifier (LEI) attestation that way.</p><h4>2. Attestations for Market Surveillance Authorities</h4><p>The <strong>ICSMS</strong> or another trusted body must be enabled to standardise and issue <strong>attestations </strong>to the Business Wallet of MSAs that include their <strong>unique Authority ID no.</strong></p><h4>3. Scalable Business Wallet Adoption</h4><p><strong>Business Wallets</strong> must be widely available — not only in Europe, but globally. Policy Recommendations, such es<a href="https://unece.org/trade/documents/2025/07/session-documents/revised-recommendation-no-49-transparency-scale-fostering"> UN/ECE Recommendation 49</a> and Initiatives such as the<a href="https://www.globalbattery.org/press-releases/international-trade-centre-%28itc%29-and-gba-announce-partnership/"> GBA operational trials</a> in cooperation with <strong>International Trace Center</strong> can play a key role in enabling this adoption. The ITC is currently developing wallet technology as an open public good to remove technological barriers for smaller companies along the battery value chain.</p><h3>Access Control Process</h3><p>With this infrastructure in place, access to controlled DPP data can follow a standardized process (see figure below) using Wallet to Wallet Communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*0iPP_4uM0b78S2mkrakFaw.png" /><figcaption>Figure 2: High Level Access Control Flow for controlled DPP data</figcaption></figure><p>High level access control flow for controlled DPP data</p><ol><li>A <strong>third party</strong> requests access to controlled DPP data</li><li>The <strong>economic operator</strong> requests a <strong>company identity attestation that is eligible under EU Law.</strong></li><li>The third party provides e.g. <strong>Business Wallet Owner ID data</strong>, <strong>LEI</strong>, or an equivalent company credential eligible under EU Law.</li><li>The economic operator verifies the identity attestation</li><li>Upon successful authentication, the operator requests additional evidence such as the <strong>Market Surveillance Authority ID</strong>, or the <strong>NACE code</strong>, depending on the use case</li><li>The third party provides the required attestation</li><li>The economic operator verifies this second attestation.</li><li>Based on the validity of the provided attestations access is <strong>granted or denied to the controlled DPP data.</strong></li></ol><p>9. If the initial identity verification fails, access is rejected immediately.</p><h3>Variants and Implementation Options</h3><p>The model allows for flexibility, including:</p><ul><li>Embedding <strong>NACE codes directly within Business Wallet Owner ID data instead of in a separate attestation.</strong></li><li>Using <strong>whitelists or blacklists</strong> based on verified company identities to allow or deny access to a DPP.</li></ul><h3>Conclusion</h3><p>The proposed approach demonstrates that <strong>all core building blocks already exist</strong>:</p><ul><li>EU Digital Identity framework</li><li>EU Business Wallets Regulation (to be ratified soon)</li><li>Established identifiers such as <strong>NACE codes</strong> and <strong>ICSMS IDs for Market Surveillance Authorities.</strong></li></ul><p>The next step is to <strong>align regulators and infrastructure providers</strong> — including <strong>ICSMS</strong> and national business registers — to support, standardize, and scale this approach alongside the rollout of <strong>EU Business Wallets</strong>.</p><h3>Acknowledgements</h3><p>This concept has greatly benefited from discussions with experts in the field of DPPs and digital identity, including:</p><p><strong>Dr. Carsten Stöcker (CEO Spherity)</strong> , <strong>Mikael af Hällström (Tax Agency Finland)</strong> , <strong>Dennis Hannemann and Louise de Laat (Bundesanzeiger Verlag)</strong></p><p>I welcome any constructive feedback and discussion from practitioners and stakeholders working on DPPs, digital identity, and regulatory innovation.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>*For DPP use cases for EU Business Wallets, read this<a href="https://medium.com/@susi.guth/eu-digital-identity-wallets-and-digital-product-passports-dpps-ff96b24eeae6"> Medium Article</a>.</p><p>Listen to this <strong>podcast </strong>on Digital Idenitify Wallets and Digital Product Passports:</p><p>Please also check out our podcast on Digital Product Passport and EU Business Wallets with<a href="https://medium.com/u/184e9bf49b6f?source=post_page---user_mention--ff96b24eeae6---------------------------------------"> Dr. Susanne Guth-Orlowski</a> and<a href="https://medium.com/u/2d7ca4c61292?source=post_page---user_mention--ff96b24eeae6---------------------------------------"> Carsten Stöcker</a> here:</p><iframe src="https://www.youtube.com/embed/FBs6b1nZxjE?feature=oembed" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0169b2be72993e7ebc8d87be8dd79eb2/href">https://medium.com/media/0169b2be72993e7ebc8d87be8dd79eb2/href</a></iframe><p>For reading <strong>digital product passport news</strong>, please follow<a href="https://www.linkedin.com/in/sguth/"> Susanne’s</a> and the<a href="https://www.linkedin.com/company/"> 4TheRecord</a> LinkedIn page.</p><p>For <strong>trainings </strong>on digital product passports, please check out our<a href="http://4therecord.io/training"> training programm</a> on<a href="http://4therecord.io/"> 4therecord.io</a>.</p><p>For more <strong>podcasts </strong>on Digital Product Passports, please follow us on<a href="https://www.youtube.com/playlist?list=PLT-WX3P9sOtfJi6YEenmYhcZs8RCepAP6"> YouTube</a>,<a href="https://open.spotify.com/show/6opb75RSIT1tgNJGqMjgzH"> Spotify</a> ,<a href="https://podcasts.apple.com/zw/podcast/spherity-podcast/id1621254669"> iTunes</a> or the<a href="https://podcast.app/digital-product-passport-insights-a-4therecord-podcast-p6260998"> podcast app</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=285d27e990cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EU Digital Identity Wallets and Digital Product Passports (DPPs)]]></title>
            <link>https://medium.com/@susi.guth/eu-digital-identity-wallets-and-digital-product-passports-dpps-ff96b24eeae6?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff96b24eeae6</guid>
            <category><![CDATA[eudi-wallet]]></category>
            <category><![CDATA[ecodesign]]></category>
            <category><![CDATA[european-business-wallet]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[dpp]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Sun, 31 Aug 2025 15:19:15 GMT</pubDate>
            <atom:updated>2026-04-17T12:35:49.537Z</atom:updated>
            <content:encoded><![CDATA[<p>The eIDAS 2.0 regulation (Regulation EU 2024/1183 [1]) entered into force <strong>in May 2024 </strong>upgrades Europe’s digital identity framework by introducing interoperable <strong>European Digital Identity Wallets (EUDI-Wallets). </strong>The EUDI wallet can<strong> </strong>store both natural-person identification data (<strong>PID</strong>) and legal-person identification data (<strong>LPID</strong>), (UPDATE: called EU Business Wallet Owner ID data in the EU Business Wallet Regulation Proposal) which are verifiable credentials, enabling businesses to securely prove their identity, corporate details, certifications, or authorizations across the EU.</p><p>The <strong>EU Business Wallet </strong>is the tailored EUDI Wallet version for companies: it supports issuance of LPIDs (e.g., company registration, VAT number, representative mandates) and facilitates high-assurance processes such as B2B onboarding, supply-chain operations, and cross-border regulatory compliance.</p><p>It integrates qualified digital signatures, selective attribute disclosure, and standardized attestations boosting security, interoperability, and convenience for businesses. EU <strong>Member States must begin issuing these wallets — both personal and business by no later than the end of 2026.</strong></p><p>The new European <strong>Commission Single Market Strategy</strong> [2] includes both Business Wallet and DPP. Whereas the <em>“Digital Product Passport (DPP) will become the main tool for disclosing and sharing product information across all new and revised product legislation.”,</em> the European Business Wallet shall be used for “<em>doing business simply and digitally</em>”, and in general the EUDI Wallet shall be used <em>“as a safe, reliable, and private means of digital identification for everyone in Europe.”</em></p><blockquote>In the context of digital product passports, EUDI Wallets can potentially be used for the following use cases: Issuing, registering, verifying, and amending the DPP and authorizing the actors when accessing non-public DPP data.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uWj1RRCuM3iv5PJhdQXSeg.png" /><figcaption>Figure: Digital Product Passport Use Cases for EUDI Wallets</figcaption></figure><h3>1. Issuing a Digital Product Passport</h3><p>Before a product enters the market, the economic operator must issue its Digital Product Passport (for example in form of a W3C Verifiable Credential). Using the <strong>EU Business Wallet</strong>, the economic operator can sign the DPP with its <strong>company identity credential</strong> — tied to Business Wallet Owner ID (BWOID) or a <strong>Legal Entity Identifier (LEI)</strong>. This ensures that the DPP is not only created by the right entity but also cryptographically bound to a verifiable and recognized corporate identity.</p><h3>2. Registering a Digital Product Passport</h3><p>Once a DPP is issued, it needs to be registered by the economic operator at the official <strong>DPP Registry</strong> managed under the European Commission framework. The Business Wallet enables the economic operator to <strong>authenticate against the registry</strong> using its LEI credential, ensuring that only verified entities can register digital product passports. This provides traceability, prevents fraud, and establishes trust at the very first point of interaction.</p><p>Potentially the DPP Registry can issue a <strong>registration credential</strong> to the Economic Operator that is bound to the DPP, so that market actors can verify that a product was registered and is legibly placed on the European Market.</p><h3>3. Authenticating Against Economic Operators</h3><p>To access the public data of a DPP, no authentication is required. But not all DPP data will be public. Certain datasets, such as supplier details or repair records, might be kept private and accessible only to authorized actors — authors with legitimate interests such as market surveillance, repairers, recyclers, etc. With the EU Business Wallet, such an actor can <strong>authenticate itself with its LEI credential</strong> when requesting access to such non-public data from another economic operator. This creates a secure and standardized way of granting controlled access without compromising sensitive business information.</p><h3>4. Verifying Digital Product Passport Data</h3><p>Trust in the DPP ecosystem relies on being able to confirm that the data is verifiable and trustworthy. The EUDI Wallet allows stakeholders (individuals and companies) to <strong>verify the signature and issuer</strong> of a DPP (and the W3C Verifiable Credentials that are linked in the DPP) before acting on its data. This prevents tampering, ensures that updates come from legitimate sources, and reduces the risk of counterfeit or manipulated product records entering the supply chain.</p><p>For example <strong>consumers</strong> can<strong> v</strong>erify a product’s <strong>eco-label </strong>or <strong>supply chain actors </strong>can check<strong> a companie’s sustainability information</strong>, increasing the trust in ESG data.</p><h3>5. Amending a DPP with Downstream Data</h3><p>Products do not remain static after they leave the factory. Repairs, refurbishments, and state-of-health checks all generate valuable data. Using the Business Wallet, companies and service providers can <strong>amend an existing DPP</strong> by issuing verifiable credentials containing downstream data — for example, a certified repair event or battery state-of-health report. Such records can easily assigned to an existing DPP by using the globally unique product identifier in the DPP as subject id in the verifiable credential. These amendments are digitally signed with the business wallet, ensuring they are trusted contributions to the product’s life cycle history.</p><p>References:</p><p>[1] European Commission — <em>The Digital Identity Regulation Enters into Force</em><br> <a href="https://ec.europa.eu/digital-building-blocks/sites/display/EUDIGITALIDENTITYWALLET/The+Digital+Identity+Regulation+Enters+into+Force">https://ec.europa.eu/digital-building-blocks/sites/display/EUDIGITALIDENTITYWALLET/The+Digital+Identity+Regulation+Enters+into+Force</a></p><p>[2] European Commission Single Market Strategy:<a href="https://single-market-economy.ec.europa.eu/single-market/strategy_en"> https://single-market-economy.ec.europa.eu/single-market/strategy_en</a></p><p>Please also check out our podcast on Digital Product Passport and EU Business Wallets with <a href="https://medium.com/u/184e9bf49b6f">Dr. Susanne Guth-Orlowski</a> and <a href="https://medium.com/u/2d7ca4c61292">Carsten Stöcker</a> here:</p><iframe src="https://www.youtube.com/embed/FBs6b1nZxjE?feature=oembed" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0169b2be72993e7ebc8d87be8dd79eb2/href">https://medium.com/media/0169b2be72993e7ebc8d87be8dd79eb2/href</a></iframe><p>For reading the <strong>digital product passport newpaper</strong>, please follow <a href="https://www.linkedin.com/in/sguth/">Susanne’s</a> and the <a href="https://www.linkedin.com/company/">4TheRecord </a>LinkedIn page.</p><p>For <strong>trainings </strong>on digital product passports, please check out our <a href="http://4therecord.io/training">training programm</a> on <a href="http://4therecord.io/">4therecord.io</a>.</p><p>For more <strong>podcasts </strong>on Digital Product Passports, please follow us on <a href="https://www.youtube.com/playlist?list=PLT-WX3P9sOtfJi6YEenmYhcZs8RCepAP6">YouTube</a>, <a href="https://open.spotify.com/show/6opb75RSIT1tgNJGqMjgzH">Spotify</a> , <a href="https://podcasts.apple.com/zw/podcast/spherity-podcast/id1621254669">iTunes</a> or the <a href="https://podcast.app/digital-product-passport-insights-a-4therecord-podcast-p6260998">podcast app</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff96b24eeae6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The world’s first decentralized, verifiable Battery Passport.]]></title>
            <link>https://medium.com/spherity/the-worlds-first-decentralized-verifiable-battery-passport-a0f42c1bcb5e?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0f42c1bcb5e</guid>
            <category><![CDATA[battery-passport]]></category>
            <category><![CDATA[european-green-deal]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[circular-econonomy]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Mon, 23 Oct 2023 21:18:01 GMT</pubDate>
            <atom:updated>2024-01-30T09:54:48.801Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>How to implement a Battery Passports based on SSI technology</h4><p><em>Last update: Nov. 24th 2023</em></p><p>In this article, we show the first working Battery Passport whose authenticity can be proven and that links to verifiable supply chain data, such as a third party Due Diligence report. Battery Passports must be attached to each battery that is placed on the European Market starting from August 2025 with CO2 data of the battery.</p><p>You can learn about the implementation details of the Battery Passport which is using the Self-Sovereign-Identity (SSI) technology concept that is completely based on open international standards and can be used and implemented free of charge. The <a href="https://medium.com/me/stats/post/efdd09a4ed75">concept</a> is permission-less, that means it allows any supply chain partner to participate in the DPP system.</p><p>Technically, it is interoperable with <a href="https://gaia-x.eu/">Gaia-X</a> and any data space built on top of it and it does not require any central component. It does NOT use the Eclipse data space connector which was invented to connect two large data repositories, which is not required in the DPP use case and conflicts with wallet-2-wallet communication. It uses technologies listed in the “<a href="https://medium.com/p/f1102c452020">StandICT.eu Landscape of Standards for digital product passports</a>” and follows the Battery Pass Content Guidance.</p><p>The Battery Passport needs to be issued by the company that places the battery on the European Market, for example, EV manufacturers but also stationary battery manufacturers. The battery passport needs to be human readable by some supply chain actors, such as recyclers or end customers. However, it also needs to be machine readable and verifiable by the usage of an API for automated compliance checks, e.g. by European Customs. This article shows both versions of the Battery Passport and all implementation details.</p><h3>1. The human readable Battery Passport</h3><p>The human readable Battery Passport provides an interface that allows people in the product’s life cycle to read detailed information about the battery they have in front of them. Please find our Battery Passport showcase here: <a href="https://acme.dpp.spherity.com/">https://acme.dpp.spherity.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nDuFiNG3Xe5W7mKK" /><figcaption>Figure 1: Human readable Battery Passport — <em>Don’t call it a web site!</em></figcaption></figure><p>The attributes you see in this passport are defined in the <a href="https://www.systemiq.earth/battery-pass-content-guidance-eu-battery-passport/">Battery Pass Content Guidance Documents</a>. Battery Pass is a project which is <a href="https://www.bmwk.de/Redaktion/EN/Pressemitteilungen/2022/04/20220425-parliamentary-state-secretary-kellner-batteries-in-the-eu-must-be-as-sustainable-as-possible.html">funded by the German Ministry of Economic Affairs and Climate Action</a>; the battery pass attributes have been developed in cooperation with major battery industry initiatives, such as the Global Battery Alliance, Catena-X, and many individual experts.</p><p>There are public and non-public attributes in the digital product passport. Public attributes can be accessed by anyone, all other attributes require an authentication of the user as the data underlies strict business confidentiality. The access control mechanism for authorised DPP users is not standardised yet. Possibilities are using common login/password mechanisms or using verifiable credentials. The login in our showcase is a mock-up as well as the data values in the passport, everything else is working technology.</p><h3><strong>2. Battery Passport Discovery</strong></h3><p>Battery passport discovery requires a globally unique identifier that is resolved on the internet. In this section, we give an overview about the battery identifier, the data carrier of the identifier (QR code), and the actual resolving of the Battery Identifier to the passport information.</p><h4>2.1 The Battery Product Identifier</h4><p>To discover a digital product passport on the internet it needs a globally unique identifier which is resolvable to a URL. The European Commission is asking for a decentral storage of the DPP which makes using <a href="https://www.w3.org/TR/did-core/">W3C Decentralized Identifiers</a> (DIDs) as battery identifiers a perfect fit.<strong> DIDs are globally unique identifiers by definition</strong> and have some other advantages:</p><ul><li>DIDs are <em>free of charge.</em></li><li>DIDs are issued and controlled by the manufacturer and not by a central organisation.</li><li>The passport data and who has access to it stays with the manufacturer.</li><li>As data is not uploaded to central systems, it is always up to date.</li><li>A DID is a persistent identifier, that means it can stay the same during its entire life cycle.</li><li>At the same time DIDs allow flexibility wrt the information that is attached to a DID, e.g. the owner of a battery, the URL to the battery passport, a service endpoint to verifiable data can change over time.</li><li>DIDs provide a built-in security functionality to attach verifiable data (also known as: <a href="https://www.w3.org/TR/vc-data-model-2.0/">W3C Verifiable Credentials</a>) to the battery passport, for example Due Diligence Reports.</li></ul><p>Depending on the DID method, the DID has a different syntax and different methods to create, revoke, update, and delete (CRUD). The syntax of our Battery DID example is</p><pre>did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3-4d72-a747-feeb2c2ed263</pre><p>It consists of the DID-method (did:web) the domain and path where the did document can be found (acme.dpp.spherity.com/battery) and the unique identifier in that domain (here the UUID 7be3b99c-33a3-4d72-a747-feeb2c2ed263.<strong> </strong>In the next sections, we are explaining how to encode a DID-based product identifier in a URL, and how to resolve it. For more information about using DID as Product Identifier, please read the IEEE award winning paper “<a href="https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3">Accessing Digital Product Passports with Decentralized Identifiers (DIDs)</a>”</p><h4>2.2 Data carrier</h4><p>At the moment the European Commission is asking for<a href="https://www.consilium.europa.eu/en/press/press-releases/2023/07/10/council-adopts-new-regulation-on-batteries-and-waste-batteries/"> QR codes</a> as the Data Carrier that leads to the Battery Passport. Other possible data carriers are RFID or NFC chips. The data carrier must contain the product identifier as a minimum. There are discussions that the data carrier should also contain some additional data attributes for use cases where no internet access is available, or retrieving data from the internet takes too long. However, those data attributes are not yet defined. A QR code type that allows for a web link plus additional attributes has been defined in <a href="https://www.beuth.de/de/technische-regel/din-spec-91406/314564057">DIN SPEC 91406:2019–12</a>.</p><p>The QR code below leads to the human readable battery passport shown in Section 1. Take out your phone and try it out!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/0*S7ogf4RammQXO-0P" /><figcaption>Figure 2: Scan it! This QR code leads you to the Battery Passport.</figcaption></figure><p>The QR code contains the Decentralised Identifier (DID) and a DID resolver link. To resolve the DID to the battery passport, it needs to be combined with a DID resolver link. In our case, we use the <a href="http://godiddy.com/">godiddy.com</a> resolver kindly provided by <a href="http://danubetech.com/">Danube Tech</a>. The DID resolver can be freely chosen by the manufacturer or can be built in-house. The combination of DID and resolver URL leads to the link below which is encoded in the QR code above.</p><pre>https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3-4d72-a747-feeb2c2ed263?service=product</pre><h4><strong>A brief aside on DID resolvers</strong>:</h4><blockquote>As a DID revolver you can use the <a href="http://dev.uniresolver.io/">Universal Resolver</a>, the <a href="https://hub.ebsi.eu/tools/did-resolver">EBSI DID-resolver</a>, or you can build your own DID resolver by following the <a href="https://www.w3.org/TR/did-core/">DID specs</a>. This is an important aspect of the technology approach, because during the lookup of battery passports some data can be collected, such as how often a certain battery passport is queried. If this lookup and usage information is crucial, it is wise to build and host your own DID resolver, otherwise it is the most convenient to use a DID resolver service.</blockquote><p>Scanning a QR code that leads you to a web site, is a common functionality, e.g. of mobile phones and millions of devices around the world already have this capability. What happens in the background when you call the link above is explained in the next section.</p><h4>2.3 DID resolving</h4><p>When calling the link the link above the DID resolver finds the <strong>DID Document</strong> that belongs to the battery DID. Every DID is associated with a DID Document. A DID Document is a small data file in JSON format that provides useful information about the DID, such as the public keys associated with it. For DPP access, the most important part of the DID Document is the service endpoint section. Here, the battery manufacturer can provide URLs to the DPP webpage and other resources like authentication endpoints for and machine-readable data.</p><p>Figure 3 shows the information flow of accessing a digital product passport.</p><ol><li>The DID and resolver link is scanned from the QR code, then</li><li>the DID resolver is called and finds the DID document of the battery.</li><li>The DID document includes the human readable Battery Passport website URL which is given back to the user who scanned the QR code.</li><li>The user can explore the battery passport website.</li></ol><p>The access to the API/ services endpoint works in the same way. The service endpoint gives access to the verifiable Battery Passport and its linked verifiable credentials, e.g. verifiable information about the battery manufacturer or the battery supply chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/0*GVflZlfo5I-qV-ay" /><figcaption>Figure 3: Resolving DIDs to verifiable Battery Passports data</figcaption></figure><p>For more details on resolving QR codes to Product Passports, please watch the video “The Power of DIDs #5: A Deep Dive into Service Endpoints and Digital Product Passports” by Markus Sabadello or read the corresponding article “<a href="https://medium.com/@susi.guth/resolving-digital-product-passports-f08ac8f11b5a">Resolving Digital Product Passports</a>”.</p><h4>2.4 The DID Document</h4><p>In Figure 4 below please find the source code of the Battery’s DID Document which includes two service endpoints:</p><ul><li>one which indicates the public accessible, human readable Battery Passport web site <a href="https://battery.dpp.spherity.com/">https://acme.dpp.spherity.com/</a> and</li><li>one that reveals the service endpoint where the verifiable battery passport can be found as well as additional verifiable information that is related to the passport, such as audit certificates.</li></ul><p>The number of service endpoints is unlimited. The structure of the DID Document is defined in the <a href="https://www.w3.org/TR/did-core/">W3C DID specification</a>. The advantage of the DID Document concept is, if changes need to be made to the battery passport URLs or the service endpoints, or new service endpoints need to be added it can be done without having to change the content of the data carrier or the product identifier. This way product lines can be sold to other companies and information (such as battery loading cycles and repairs) can be added during the <strong>lifetime </strong>of a product.</p><pre>{<br>&quot;@context&quot;: [<br>&quot;https://www.w3.org/ns/did/v1&quot;,<br>&quot;https://w3id.org/security/suites/ed25519-2020/v1&quot;<br>],<br>&quot;id&quot;: &quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3-4d72-a747-feeb2c2ed263&quot;,<br>&quot;verificationMethod&quot;: [<br>{<br>&quot;id&quot;: &quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3–4d72-a747-feeb2c2ed263#a7a125a110e9f6cd8a7cd4825ba840dc7600320e9d5bea19144cb64d785ad00a&quot;,<br>&quot;type&quot;: &quot;Ed25519VerificationKey2020&quot;,<br>&quot;controller&quot;: &quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3–4d72-a747-feeb2c2ed263&quot;,<br>&quot;publicKeyMultibase&quot;: &quot;z6MkqjcefbHmLzkJKk8cHH8P8aiWxq3MsDaRJM3tyr7RKqm3&quot;<br>}<br>],<br>&quot;authentication&quot;: [<br>&quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3–4d72-a747-feeb2c2ed263#a7a125a110e9f6cd8a7cd4825ba840dc7600320e9d5bea19144cb64d785ad00a&quot;<br>],<br>&quot;assertionMethod&quot;: [<br>&quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3–4d72-a747-feeb2c2ed263#a7a125a110e9f6cd8a7cd4825ba840dc7600320e9d5bea19144cb64d785ad00a&quot;<br>],<br>&quot;keyAgreement&quot;: [],<br>&quot;service&quot;: [<br>{<br>&quot;id&quot;: &quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3–4d72-a747-feeb2c2ed263#product&quot;,<br>&quot;type&quot;: &quot;ProductPassport&quot;,<br>&quot;serviceEndpoint&quot;: &quot;https://acme.dpp.spherity.com/battery/7be3b99c-33a3-4d72-a747-feeb2c2ed263&quot;<br>},<br>{<br>&quot;id&quot;: &quot;did:web:acme.dpp.spherity.com:battery:7be3b99c-33a3–4d72-a747-feeb2c2ed263#product-information&quot;,<br>&quot;type&quot;: &quot;ProductPassport&quot;,<br>&quot;serviceEndpoint&quot;: &quot;https://acme.dpp.spherity.com/battery/7be3b99c-33a3-4d72-a747-feeb2c2ed263&quot;<br>}]}</pre><p>Figure 4: DID Document of a battery with service endpoints</p><h4>2.5 The trusted ledger</h4><p>According to the DID spec, the DID Document must sit on a <strong>Trusted Ledger</strong>. The Trusted Ledger of the DID Document depends on the DID method being used. A trusted ledger can be an Ethereum Network, a Hyperledger Indy Network, or a simple web domain. Therefore, the technical DID resolution differs for each DID method.</p><p>The <strong>DID method</strong> is specified by the DIDs prefix. In our example, we’re using the <a href="https://w3c-ccg.github.io/did-method-web/">did:web</a> DID method. Unlike other methods that store DID Documents on distributed ledgers, the did:web method involves hosting the DID Document at the well-known URL of a pre-existing web domain*. This is useful when the web domain and organisation controlling it is already trusted by users, such as reputable institutions like government agencies or large enterprises.</p><p><em>*DID-web is lacking some security features, such as traceable key rotation. Improvements are currently being designed e.g. </em><a href="https://trustoverip.github.io/tswg-did-method-webs-specification/"><em>here</em></a><em>, and </em><a href="https://github.com/LedgerDomain/did-webplus"><em>here</em></a><em> and </em><a href="https://medium.com/danube-tech/moving-beyond-the-limitations-of-did-web-c10f53eafdc3"><em>here</em></a><em>.</em></p><h3>3. The machine readable Battery Passport and its verification</h3><p>The second main feature of this showcase is to verify the Battery Passport, ie. to check if the battery passport was modified, if the vocabulary is compliant, and who issued the Battery Passport.</p><h4>3.1 The machine readable Battery Passport</h4><p>In our showcase, Spherity is the manufacturer of the Battery and issuer of the Battery Passport. Everyone can verify who issued the DPP and if it was modified or revoked. This is achieved by signing the DPP verifiable credential with the Spherity’s private key using our DPP solution VERA. The credential includes Spherity’s company DID in the issuer field <strong>(Issuer DID</strong>) and the <strong>Product DID</strong> in the credentialSubject field. It also contains all the<strong> technical data</strong> about the Battery which is also displayed on the human readable web page shown above. Lastly, the proofValue field contains the digital <strong>signature </strong>which was created using the private key associated with Spherity’s issuer DID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M7snHMG07qphUzID" /><figcaption>Figure 5: The Battery DPP in form of a Verifiable Credential</figcaption></figure><h4>3.2 The semantics</h4><p>The DPP can be checked against a <strong>vocabulary </strong>that is used to describe the Battery. This step checks if the naming of the attributes and the structure correspond to a given schema. As mentioned in Chapter 1, the used vocabulary and its semantics was defined by the Battery Pass Content Guidance Documents. As this vocabulary do not yet exist as JSON-LD schema, we have created a demo schema and are hosting it on our Spherity Website in the interim (See: <a href="https://api-rcs.susi.spherity.dev/products/v1/public-ev-battery-passport-007.jsonld">https://api-rcs.susi.spherity.dev/products/v1/public-ev-battery-passport-007.jsonld</a>). You find the link to this battery pass schema in the context section of the Battery DPP (see Figure 5). In future, this schema and a corresponding SHACL-file should be hosted and maintained by the Battery Pass Project or some other Battery Industry Consortium for Battery DPP validation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BXvHS3A0ZPtwLApu" /><figcaption>Figure 6: Vocabulary of the Battery Passport technical data is defined in the JSON-LinkedData schema</figcaption></figure><h4>3.3 Validation of the Battery Passport</h4><p>The Battery Passport can be verified by any third-party verifier without requiring any additional integration work. In this case, we used the open-source verifier developed and kindly made available by <a href="https://id.eecc.de/">EECC</a>. The verifier mainly checks the signature of the Battery Passport.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GrQDIaj3T1PxsL97" /><figcaption>Figure 7: Third party verifier checks the digital signature of the Battery Passport</figcaption></figure><p>For this process the verifier reaches out to the DID document of the issuer, here Spherity with the DID did:web:dpp.spherity.com. As per the did:web specification, the DID document MUST be located at the path <a href="https://dpp.spherity.com/.well-known/did.json.">https://dpp.spherity.com/.well-known/did.json.</a> Any verifier service that receives the DID did:web:dpp.spherity.com will recognize it as a did:web because of its prefix and will know that the DID document can be retrieved from the domain dpp.spherity.com in the /.well-known/ path if not otherwise specified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VXcnKHclBkw7PXXl" /><figcaption>Figure 8: DID document of the DPP issuer Spherity</figcaption></figure><p>Spherity’s DID document includes the public key and the applied encryption method / key which is an ingredient to the cryptographic function of validating the Battery Passport signature. When the signature validation is successful, the EECC verifier shows a green check mark with the comment “Credential Verified!” (See Figure 7).</p><p>A customer, auditor or regulator can thus be confident that the Battery Passport was actually issued by the real Manufacturer (here: <a href="https://www.spherity.com/digital-product-passport">Spherity GmbH</a>) and be sure that the DPP had not been modified since it was issued (otherwise the signature verification would fail). One other important service of digital signatures is non-repudiation. This means that the issuer can not deny having issued this Product Passport.</p><h4>3.4 Verifiable Due Diligence reports</h4><p>More verifiable credentials can be discovered about the Battery manufacturer or its suppliers such as the sustainability report, the Greenhouse Gas Emissions report or the Child Labor report. Those reports are issued as verifiable credentials by a trusted auditor using the same technical concept. The reports can be retrieved via the service endpoints in the DID Document (also called credential store) or could be referenced in the DPP credential and verified through the same method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PXGpNNfK_nrv8yy8" /><figcaption>Figure 9: UI Example 3rd Party Audits</figcaption></figure><p>In our showcase, we have added a due diligence report that can be downloaded and verified in the same way as the Battery Passport itself. When verifying the “Third party supply chain assurance” report you will notice that the issuer of the report is an auditor (here: <a href="https://www.rcsglobal.com/">RCS Global</a>) and that its signature was successfully verified.</p><p>With this principle all relevant supply chain data can be linked from the digital Battery Passport and technically verified. This allows battery manufacturers to show their legal compliance with legal obligations and compliance audits can thus be performed via a few API calls. The decentralised and standardised manner of the concept makes such a DPP system trusted and scalable. It allows supply chain actors to easily join the ecosystem and share data only with verified actors in predefined roles.</p><p>Special thanks go to the great technical team of Spherity, who implemented my Battery Passport vision: <a href="https://medium.com/u/16518b469d1e">Ricky Thiermann</a>, <a href="https://medium.com/u/20f8afaf51cf">Konstantin Tsabolov</a>, <a href="https://medium.com/u/e57dcf84e530">Johannes Ebert</a>, Amine Alani, Anuja Deshpande, and Durgesh Singh (Abhi).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0f42c1bcb5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spherity/the-worlds-first-decentralized-verifiable-battery-passport-a0f42c1bcb5e">The world’s first decentralized, verifiable Battery Passport.</a> was originally published in <a href="https://medium.com/spherity">Spherity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resolving Digital Product Passports]]></title>
            <link>https://medium.com/@susi.guth/resolving-digital-product-passports-f08ac8f11b5a?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f08ac8f11b5a</guid>
            <category><![CDATA[digital-product-passport]]></category>
            <category><![CDATA[circular-econonomy]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <category><![CDATA[textile]]></category>
            <category><![CDATA[green-new-deal]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Thu, 29 Jun 2023 08:12:15 GMT</pubDate>
            <atom:updated>2023-06-29T08:12:15.625Z</atom:updated>
            <content:encoded><![CDATA[<p>How to build and discover a persistent DPP product web page based on decentralized identifiers</p><p>Authors: <a href="https://www.linkedin.com/in/sguth/">Dr. Susanne Guth-Orlowski</a>, <a href="https://www.linkedin.com/in/markus-sabadello-353a0821/">Markus Sabadello</a></p><h3>Introduction</h3><p>Decentralized Identifiers (DIDs) are a new type of digital identifier or address that can be used to refer to individuals, organizations, facilities, locations, products or any “things”. Compared to other identifiers such as domain names or UUIDs, DIDs have a number of empowering properties. They are designed to be decentralized, cryptographically verifiable, persistent, and resolvable. They are therefore also an ideal fit for identifying products and can be used for discovering verifiable metadata about a product in the form of a Digital Product Passport (DPP).</p><p>We are describing this DPP “deep linking” with the help of a DPP for a T-Shirt produced by Spherity. We show how you can use decentralized identifiers to create a unique identifier for the T-Shirt and then to link to the Product Passport Website (for example<a href="https://20230614.dpp.spherity.com/"> a T-Shirt DPP</a>), using this unique identifier and a DID resolver (here provided by <a href="http://godiddy.com/">godiddy.com</a>). The technology described in this article fulfills similar functionality as e.g. a (s)GTIN and its GS1 digital link but with the mentioned advantages.</p><h3>How to create a DID and DID document for a DPP</h3><p>As a first step a DID needs to be created for the T-Shirt. Potentially using any DID method can be used to create the DID, including did:web, did:ebsi, did:indy, did:ethr, did:ion, etc. This ensures interoperability across different networking infrastructures and ecosystems. The tool that usually offers this functionality is a digital identity wallet, here provided by Spherity. Every DID comes with a DID-document that defines the DID further. The DID-document includes additional metadata about the DID, e.g. its public key for validation and optionally service endpoints that lead to more information about the DID’s subject (e.g. a web page or credential stores).</p><p>In order to create a DID that can be used for discovering a digital product passport, the associated DID document MUST contain a service endpoint with an identifier, (in our example we use the identifier “#product”), a service type “ProductPassport”, and an endpoint URL that points to the digital product passport web page. The example DID, we use for the T-Shirt is shown below:</p><blockquote>did:web:20230614.dpp.spherity.com:products:tshirt</blockquote><p>The T-Shirt DID has the following, corresponding DID document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*fscCWWoKkE6BeO4oPMwiTQ.png" /><figcaption>Figure 1: DID document of T-Shirt DID</figcaption></figure><p>Besides the service endpoint, the DID document could also include other metadata about a product, e.g. using properties such as “alsoKnownAs” that can list additional, equivalent identifiers for the same product. For more detailed information about DID documents, please refer to the W3C Specification <a href="https://www.w3.org/TR/did-core">Decentralized Identifiers (DIDs) v1.0</a>.</p><h3>How to construct a DID URL “deep link” for a DPP</h3><p>Now that we have a DID with a “ProductPassport” service endpoint, we can construct a DID URL that always dereferences to the service endpoint URL of the DPP public product page, using the “service” DID parameter. This dereferencing functionality is specified in the W3C specification <a href="https://w3c-ccg.github.io/did-resolution/">Decentralized Identifier Resolution (DID Resolution) v0.3</a>.</p><p>Example DID URL:</p><blockquote>did:web:20230614.dpp.spherity.com:products:tshirt?service=product</blockquote><h3>How to dereference the DID URL “deep link”</h3><p>This DID URL can be dereferenced to the DPP public product page according to the standard interfaces defined in the <a href="https://www.w3.org/TR/did-core/">W3C DID Core specification</a>, using tools that implement this specification. The most straightforward way is to prepend the DID URL “deep link” with the HTTPS endpoint of a DID resolver service, e.g.:</p><figure><img alt="https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:web:20230614.dpp.spherity.com:products:tshirt?service=product" src="https://cdn-images-1.medium.com/max/966/1*fS7tV-6psasGT8CeA2ldLA.png" /><figcaption>Figure 2: <a href="https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:web:20230614.dpp.spherity.com:products:tshirt?service=product">Deep Link</a> to the digital product passport of the T-Shirt</figcaption></figure><p>This <a href="https://api.godiddy.com/0.1.0/universal-resolver/identifiers/did:web:20230614.dpp.spherity.com:products:tshirt?service=product">deep link</a> can then be added to a data carrier. Very often the data carrier for digital product passports will be QR codes, but other RFID chips will be accepted. The QR code for our T-Shirt show case can be seen in the visual below on the T-Shirt. Scan it with your regular mobile phone to try it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DlD8026akLri731j" /><figcaption>Figure 3: T-Shirt with QR code that leads to the digital product passport.</figcaption></figure><p>When the “deep link” is opened, e.g. by scanning the QR code above, clicking on a link, or invoking an API function, then the DID URL gets derefenced by following these steps:</p><ol><li>The DID resolver resolves the DID to its associated DID document, according to the applicable DID method.</li><li>The DID resolver processes the “service” DID parameter and selects the service endpoint with identifier “#product” from the DID document.</li><li>If the “deep link” is opened in a web browser, the DID resolver responds with a 303 Redirect HTTP code that sends the web browser directly to the DPP public product page. Otherwise, if the “deep link” is opened by some other application or service, the address of the DPP public product page and other information are returned in a machine-readable form.</li></ol><p>The dereferenced result is the service endpoint URL from the DID document, i.e. the digital product passport, here the DPP of the Spherity T-Shirt. DPP public product page:</p><blockquote><a href="https://20230614.dpp.spherity.com/">https://20230614.dpp.spherity.com/</a></blockquote><p>When visiting the T-Shirt DPP you can see public, human readable information, but it also contains verifiable product information that has been issued as verifiable credentials for the T-Shirt.</p><h3>Exkurs: Additional DID URL Examples</h3><p>For illustration of the flexibility of DID technology, we have created several additional DID URLs that can be dereferenced to a DPP public product page. These DIDs are created in various underlying networking infrastructures, such as the European Blockchain Service Infrastructure (EBSI), IDunion, ION, and Ethereum, which come with different characteristics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7WvMgkW7df2S15C2po4bw.png" /><figcaption>Figure 4: DIDs can be anchored on various network infrastructures</figcaption></figure><h3>Summary: Advantages of DID URL “deep links” for digital product passports</h3><p>The fascinating aspect of this mechanism is that these DID URL “deep links” inherit all the unique properties of DIDs themselves. They are:</p><ol><li>Decentralized: Creating and dereferencing the “deep links” works without any dependency on a centralized infrastructure or intermediary, and across different underlying networking infrastructures and ecosystems.</li><li>Cryptographically verifiable: DIDs are designed in a way that allows cryptographic verification during the DID resolution process, to ensure that the DID document is the correct one for a given DID.</li><li>Persistent: DID documents can be updated over time, which means that the location of the “DPP” public product page can change, without having to create a new DID URL “deep link” every time. This allows full portability of services and data about a product, while maintaining a stable, long-lived identifier for the product.</li><li>Resolvable: As shown in the various examples above, DID URL “deep links” can be dereferenced to a DPP public product page as well as additional metadata.</li></ol><p>DIDs are globally unique identifiers due to their underlying cryptographic algorithms. For more requirements of identifiers for digital products passports and the benefits of using DIDs, please refer to the article “Accessing DPPs with DIDs” <a href="https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3">https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3</a>.</p><p>For feedback about this article please get in touch with the authors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f08ac8f11b5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Digital Product Passports using decentralized identity standards]]></title>
            <link>https://medium.com/spherity/implementing-digital-product-passports-using-decentralized-identity-standards-f1102c452020?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1102c452020</guid>
            <category><![CDATA[circulareconomy]]></category>
            <category><![CDATA[supply-chain]]></category>
            <category><![CDATA[digital-product-passport]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[gaia-x]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Thu, 27 Apr 2023 16:46:01 GMT</pubDate>
            <atom:updated>2023-05-26T06:26:26.636Z</atom:updated>
            <content:encoded><![CDATA[<p>Or how to use the “StandICT.eu Landscape of Standards for digital product passports”</p><p>Authors: Dr. <a href="/service/mailto:susanne@spherity.com">Susanne Guth-Orlowski</a>, <a href="/service/mailto:johannes.ebert@spherity.com">Johannes Ebert</a>, <a href="/service/mailto:ricky.thiermann@spherity.com">Ricky Thiermann</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YXa4uGBUpPk9Qbc6qGy35g.png" /></figure><h3>Introduction</h3><p>This article is showing how to implement the digital product passport (DPP) with some standards mentioned in the StandICT.eu ‚A Landscape of Standards for digital product passports‘ [<a href="https://www.standict.eu/digital-product-passport-standards-report">1</a>]. Whereas the architecture diagram from the report is technology agnostic (see Figure 1), in this article we are concentrating on using decentralized technologies, such as W3C decentralized identifiers [<a href="https://www.w3.org/TR/did-core/">2</a>] and W3C verifiable credentials [<a href="https://www.w3.org/TR/vc-data-model/">3</a>] to implement the digital product passport. It shows how those technologies, file formats, and protocols can be used to exchange supply chain data among industry players, authorities and end customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LN80TbWCle-OjeZJuXiZmA.jpeg" /><figcaption>Figure 1: <em>Architectural overview and areas of standardization for the DPP (Source: Dr. S. Guth-Orlowski)</em></figcaption></figure><p>In the following chapters we will describe what standards are needed for the decentralised approach and how they work. We show how W3C decentralized identifiers are created for all involved supply chain parties and products, how product and company information is issued as W3C verifiable credential, and how digital product passports can be found and verified from its users.</p><h3>Setting up Decentralized Identifiers for Companies and Products</h3><p>For a trusted digital environment it is essential to create globally unique identifiers for all involved parties and “things” (here: products). In the world of decentralized identifiers (short DIDs), DIDs are created by a wallet. A wallet is a piece of software that implements a large number of standards around decentralized identifiers, including communication protocols, trusted ledger access, etc. When creating a DID, the wallet follows the rules defined by the W3C decentralized identifiers standard [<a href="https://www.w3.org/TR/did-core/">2</a>].</p><p>Every party, for example a supplier, creates its own company DID, which also includes the creation of a public-private key pair. Whereas the private key always stays with the supplier, the public key is published on a trusted ledger in a DID document. The public key needs to be accessible to the ecosystem to verify signatures from the supplier. Economic operators can also create DIDs as globally unique identifier for their products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sZpEfppuTSGSyRTqT9J_pg.jpeg" /><figcaption><em>Figure 2: Creating Decentralized Identifiers for all actors</em></figcaption></figure><p>DID documents are registered [<a href="https://identity.foundation/did-registration/">4</a>] on a trusted ledger where they cannot be modified or tampered with. The trusted ledger can be chosen depending on the use case, the security requirements, and the required level of trust. Often used trusted ledgers are:</p><ul><li>The well-known [<a href="https://identity.foundation/specs/did-configuration/">5</a>] URL of a secure domain (see DID:web [<a href="https://w3c-ccg.github.io/did-method-web/">6</a>]); a trusted ledger where <strong>no blockchain </strong>technology is involved.</li><li>Hyperledger Indy [<a href="https://wiki.hyperledger.org/display/Indy">7</a>] (see DID:indy [<a href="https://hyperledger.github.io/indy-did-method/">8</a>]), for example IDunion [<a href="https://idunion.org/?lang=en">9</a>]</li><li>Ethereum (see DID:ethr [<a href="https://github.com/decentralized-identity/ethr-did-resolver/blob/master/doc/did-method-spec.md">10</a>]), for example EBSI [<a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/Home">11</a>]</li></ul><p>The DID document optionally also includes service endpoints, which lead to further information / claims about the supplier, e.g. the supplier’s company registration, its company identity verification in form of a vLEI [<a href="https://www.gleif.org/en/vlei/introducing-the-verifiable-lei-vle">12</a>], its ISO certification, or its GHG emissions report. Claims about the supplier can be made by the supplier himself (self attestations) or by third parties (e.g. an auditor). In the world of decentralized identifiers, such claims are implemented as ‘verifiable credentials’, which is described in the next section.</p><h3>Provision of Data and Digital Product Passport creation</h3><p>Before creating a digital product passport, the data it contains must be made available in a verifiable manner. Third parties and suppliers provision this information in the form of W3C Verifiable Credentials [<a href="https://www.w3.org/TR/vc-data-model/">3</a>]. In Figure 3 below the third party issues the ESG credential to the supplier, the GHG emissions report, as well as the battery test report to the economic operator (flow 1.a).</p><p>Technically speaking the third party’s wallet initiates a secure connection with the supplier wallet using the standardised DIDComm [<a href="https://identity.foundation/didcomm-messaging/spec/v2.0/">13</a>] protocol. It then issues the ESG credential which is encoded in JSON-LD [<a href="https://www.w3.org/TR/json-ld11/">15</a>] or VC-JSON [<a href="https://w3c.github.io/vc-json-schema/">16</a>] and signs it with the third party’s private key. In the same way the economic operator receives the GHG emissions report and the battery test report. The supplier issues the product information about his pre-product also as a verifiable credential to his own wallet signed by his private key (also called: self attestation, (see flow 1b)).</p><p>Now the economic operator who places the battery on the market can verify the product information and ESG compliance of his supplier (flow 2) and reference the respective credentials in the battery passport which he creates (flow 3). The battery passport is a self attestation, a verifiable credential issued and signed by the economic operator. In the battery passport he also references his own credentials that concern the battery (Battery Test and GHG emissions) and adds all additional required attributes to be compliant to the regulation. For batteries those attributes are defined in the Battery Passport Content Guidance [<a href="https://thebatterypass.eu/assets/images/content-guidance/pdf/2023_Battery_Passport_Content_Guidance.pdf">17</a>] . For other products and product components vocabularies often already exist, which might need to be enhanced to comply to the Ecodesign for Sustainable Products Regulation [<a href="https://commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/sustainable-products/ecodesign-sustainable-products_en">18</a>]. Examples are the Safety Data Sheet for chemical products [<a href="https://echa.europa.eu/documents/10162/2324906/sds_en.pdf/01c29e23-2cbe-49c0-aca7-72f22e101e20">19</a>], RMS for recycled plastic [<a href="https://www.rmscertified.com/wp-content/uploads/2021/05/Framework-052021_1159.pdf">20</a>], the <a href="https://industrialdigitaltwin.org/en/content-hub/submodels">Asset Administration Shell Submodels</a> for Industry 4.0 information, the Circularity.ID for textiles, or the PCDS [<a href="https://pcds.lu/wp-content/uploads/2020/11/20200214_Light_PCDS_v3.2s_FORM.pdf">21</a>] for general circularity attributes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3MvWkv2J7pprtwXEr4WODA.png" /><figcaption><em>Figure 3: Data provisioning and digital product passport creation</em></figcaption></figure><p>Finally, the product identifier, the product DID, is encoded in a suitable way to fit to the data carrier. In our example it is encoded into a QR code (flow 4). An alternative to creating a DID per product is to use an already established product identifier in the DPP (see [22]).</p><h3>Find and verify the digital product passport data</h3><p>Once the DPP is created, its identifier is put on a QR code and glued on top of a battery. The DPP user now needs to find the DPP data and verify it. How to find digital product passports of products that use a DID as a unique global identifier, has been described in the IEEE award winning paper “Accessing Digital Product Passports with Decentralized Identifiers” [<a href="https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3">23</a>]. No central component is required to register and find digital product passports, as the Universal Resolver [<a href="https://w3c-ccg.github.io/did-resolution/">24</a>] naturally takes over this part.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZEESQKyz21toOtwR3wcQng.jpeg" /><figcaption><em>Figure 4: Find and verify the Digital Product Passport</em></figcaption></figure><p>In short, to find the DPP, one has to decode the QR code and retrieve the product DID (step 1). As a response to resolving the DID with the universal resolver [<a href="https://wiki.hyperledger.org/display/ARIES">25</a>] (step 2), the user application (a wallet) receives the DID document (step 3) which includes the service endpoints for fetching the digital product passport. The DPP is securely kept in the credential store of the economic operator. If no access control is applied, the DPP can be shared and validated immediately by checking its signature with the public key of the economic operator on the trusted ledger. However, the DPP and supply chain data underlie high business confidentiality requirements. Therefore, the credential store and the issuer’s wallet are managing the access control for the DPP which is described in the more technical sections below.</p><p>To fetch the DPP from the economic operator, the user needs to talk to the wallet of the economic operator. Wallets often implement protocols, such as DIDComm [<a href="https://identity.foundation/didcomm-messaging/spec/v2.0/">13</a>] which are designed for a secure message exchange between wallets. Protocols on top of DIDComm, such as Aries [<a href="https://wiki.hyperledger.org/display/ARIES">25</a>] or DIF Presentation exchange [<a href="https://identity.foundation/presentation-exchange/spec/v2.0.0/">26</a>] allow handshakes between wallets, with which they can ask for and receive verifiable credentials. Alternatively, OpenIDConnect [<a href="https://openid.net/connect/">27</a>] with OID4VC [<a href="https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html">14</a>] and OID4VP [<a href="https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0-07.html">24</a>] or other emerging protocols can be used. On this level access control mechanisms can be implemented, as verifiable credentials, here the DPP, are only shared on request. Examples for access control mechanisms are:</p><ul><li>A wallet can be configured to automatically share all credentials with everyone.</li><li>A wallet can implement a role based access control mechanism, where access rights to verifiable credentials can be expressed and enforced based on a rights expression language, such as ODRL [<a href="https://www.w3.org/TR/odrl-model/">29</a>]. For example, access is given if the requester can show an identity credential that proves his auditor role.</li><li>A wallet can be configured to share no concrete data but only proofs of the data (Selective Disclosure, Zero Knowledge Proofs).</li></ul><p>The eclipse data space connector [<a href="https://projects.eclipse.org/projects/technology.edc">30</a>] defines another way to express, negotiate, and document the rules under which data is shared, and also with whom. However, it replaces the basic way wallets communicate with each other, is only used in certain industry consortia (such as <a href="https://catena-x.net/en/offers/edc-the-central-component">Catena-X</a>), and thus is not suitable for a broad, cross-industry data exchange. The best solution for credential exchange and access control is the one closest to the industry requirements, its common practice, and that adheres to general security standards [<a href="https://www.iso.org/committee/45306.html">31</a>, <a href="https://www.enisa.europa.eu/publications/tsp1-framework">32</a>].</p><p>Each industry or product segment needs to determine the above mentioned wallet exchange protocols to allow the highest level of interoperability which usually manifests in a trust framework. A trust framework defines some technical but also non-technical rules to establish trust for a certain use case or industry. A general trust framework approach is shown in Trust over IP [<a href="https://trustoverip.org/toip-model/">33</a>], and specific examples are OCI [<a href="https://www.oc-i.org/resources-portfolio/oci-interop-v3-0-0">34</a>] and Gaia-X [<a href="https://gaia-x.gitlab.io/policy-rules-committee/trust-framework/gaia-x_trust_framework/">35</a>].</p><h3>Benefits</h3><p>Benefits of the decentralized approach are:</p><ul><li>Product information stays with its owner.</li><li>The owner of the data has full control over who can access his data.</li><li>Because product and company data is not uploaded to central platforms and not shared multiple times, the data is always up to date.</li><li>Decentralised technology is inclusive. Everyone with a wallet can technically participate in the ecosystem.</li><li>Entry barriers are low, as open source wallets and reference implementations are available.</li><li>Companies have a high need to insert trusted data into their internal systems. Data in the form of verifiable credentials can meet this need and provide end-to-end verifiability.</li><li>A decentralised approach allows an ad-hoc trusted data exchange without a bilateral integration, also referred to as ‘decentralised integration’. In other words you can exchange data with and trust data of a company you have never dealt with before.</li><li>A decentralised approach makes central components obsolete, which saves development, deployment, management and other ongoing costs which come with central components.</li></ul><p>A DPP solution that follows the approach above is the Spherity Digital Product Passport.</p><p>This article is subject to change and will be further improved.</p><h3>Sources</h3><p>The sources in <strong>bold</strong> are standards mentioned in the StandICT report</p><p>[1] StandICT.eu Technical Working Group Digital Product Passport. (2023, March 21). A Landscape of Standards for the Digital Product Passport (EUOS TWG) (J. Gayko &amp; B. Helfritz, Eds.). StandICT.eu. Retrieved April 26, 2023, from <a href="https://www.standict.eu/digital-product-passport-standards-report">https://www.standict.eu/digital-product-passport-standards-report</a></p><p><strong>[2] Sporny, M., Longley, D., Sabadello, M., Reed, D., Steele, O., &amp; Allen, C. (2022, July 22). Decentralized Identifiers (DIDs) v1.0 (M. Sporny, A. Guy, M. Sabadello, &amp; D. Reed, Eds.). W3C. </strong>Retrieved April 26, 2023, from <a href="https://www.w3.org/TR/did-core/">https://www.w3.org/TR/did-core/</a></p><p><strong>[3] Sporny, M., Longley, D., &amp; Chadwick, D. (2022, March 22). Verifiable Credentials Data Model v1.1 (M. Sporny, G. Noble, D. Longley, D. C. Burnett, B. Zundel, &amp; K. Den Hartog, Eds.). W3C. </strong>Retrieved April 26, 2023, from <a href="https://www.w3.org/TR/vc-data-model/">https://www.w3.org/TR/vc-data-model/</a></p><p><strong>[4] Sabadello, M., &amp; Saglam, C. (n.d.). DID Registration (Pre-Draft). DIF.</strong> Retrieved April 26, 2023, from <a href="https://identity.foundation/did-registration/">https://identity.foundation/did-registration/</a></p><p><strong>[5] Buchner, D., Steele, O., &amp; Looker, T. (n.d.). <em>Well Known DID Configuration</em>. DIF Approved Deliverable. </strong>Retrieved April 26, 2023, from <a href="https://identity.foundation/specs/did-configuration/">https://identity.foundation/specs/did-configuration/</a></p><p>[6] Gribneau, C., Prorock, M., Steele, O., &amp; Terbu, O. (2023, March 18). did:web Method Specification (M. Prorock, O. Steele, &amp; O. Terbu, Eds.). W3C. Retrieved April 26, 2023, from <a href="https://w3c-ccg.github.io/did-method-web/">https://w3c-ccg.github.io/did-method-web/</a></p><p><strong>[7] Hyperledger Foundation. (n.d.). Hyperledger Indy.</strong> Retrieved April 26, 2023, from <a href="https://wiki.hyperledger.org/display/Indy">https://wiki.hyperledger.org/display/Indy</a></p><p>[8] Curran, S., Bastian, P., Hardman, D., Howland, C., &amp; Bormann, C. (2023, February 23). Indy DID Method Specification. Hyperledger Foundation. Retrieved April 26, 2023, from <a href="https://hyperledger.github.io/indy-did-method/">https://hyperledger.github.io/indy-did-method/</a></p><p>[9] IDunion. (n.d.). IDunion — Ermöglicht selbstbestimmte Identitäten. Retrieved April 27, 2023, from <a href="https://idunion.org/?lang=en">https://idunion.org/?lang=en</a></p><p>[10] Veramo Core Team. (2022, November 7). ETHR DID Method Specification. DIF. Retrieved April 26, 2023, from <a href="https://github.com/decentralized-identity/ethr-did-resolver/blob/master/doc/did-method-spec.md">https://github.com/decentralized-identity/ethr-did-resolver/blob/master/doc/did-method-spec.md</a></p><p>[11] EBSI. (2023, April 11). European Blockchain Services Infrastructure. Retrieved April 27, 2023, from <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/Home">https://ec.europa.eu/digital-building-blocks/wikis/display/EBSI/Home</a></p><p>[12] GLEIF. (n.d.). Introducing the verifiable LEI (vLEI). Retrieved April 26, 2023, from <a href="https://www.gleif.org/en/vlei/introducing-the-verifiable-lei-vle">https://www.gleif.org/en/vlei/introducing-the-verifiable-lei-vle</a></p><p><strong>[13] Curren, S., Looker, T., Terbu, O., Den Hartog, K., &amp; Shaaban, B. (n.d.). DIDComm Messaging v2.0</strong> (S. Curren, T. Looker, &amp; O. Terbu, Eds.). DIF. Retrieved April 26, 2023, from <a href="https://identity.foundation/didcomm-messaging/spec/v2.0/">https://identity.foundation/didcomm-messaging/spec/v2.0/</a></p><p><strong>[14] Lodderstedt, T., Yasuda, K., &amp; Looker, T. (2023, February 3). OpenID for Verifiable Credential Issuance. OpenID Foundation. </strong>Retrieved April 26, 2023, from <a href="https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html">https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html</a></p><p><strong>[15] Sporny, M., Longley, D., Kellogg, G., Langthaler, M., Champin, P.-A., &amp; Longley, D. (2020, July 16). JSON-LD 1.1 (G. Kellogg, Ed.; W3C Recommendation). W3C. </strong>Retrieved April 26, 2023, from <a href="https://www.w3.org/TR/json-ld11/">https://www.w3.org/TR/json-ld11/</a></p><p><strong>[16] Cohen, G., &amp; Steele, O. (2023, April 5). Verifiable Credentials JSON Schema 2022 (Final Community Group Report). W3C.</strong> Retrieved April 26, 2023, from <a href="https://w3c.github.io/vc-json-schema/">https://w3c.github.io/vc-json-schema/</a></p><p>[17] Battery Pass. (2023, April). <em>Battery Passport Content Guidance</em>. Retrieved April 26, 2023, from <a href="https://thebatterypass.eu/assets/images/content-guidance/pdf/2023_Battery_Passport_Content_Guidance.pdf">https://thebatterypass.eu/assets/images/content-guidance/pdf/2023_Battery_Passport_Content_Guidance.pdf</a></p><p>[18] European Commission. (n.d.). Ecodesign for sustainable products. Retrieved April 26, 2023, from <a href="https://commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/sustainable-products/ecodesign-sustainable-products_en">https://commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/sustainable-products/ecodesign-sustainable-products_en</a></p><p>[19] European Chemicals Agency. (2020, December). Guidance on the compilation of safety data sheets. Retrieved April 26, 2023, from <a href="https://echa.europa.eu/documents/10162/2324906/sds_en.pdf/01c29e23-2cbe-49c0-aca7-72f22e101e20">https://echa.europa.eu/documents/10162/2324906/sds_en.pdf/01c29e23-2cbe-49c0-aca7-72f22e101e20</a></p><p>[20] GreenBlue. (2021, May 6). The Recycled Material Standard Framework. RMS. Retrieved April 26, 2023, from <a href="https://www.rmscertified.com/wp-content/uploads/2021/05/Framework-052021_1159.pdf">https://www.rmscertified.com/wp-content/uploads/2021/05/Framework-052021_1159.pdf</a></p><p>[21] PCDS. (2020, February 14). Product Circularity Data Sheet (PCDS) v3.2s. Retrieved April 26, 2023, from <a href="https://pcds.lu/wp-content/uploads/2020/11/20200214_Light_PCDS_v3.2s_FORM.pdf">https://pcds.lu/wp-content/uploads/2020/11/20200214_Light_PCDS_v3.2s_FORM.pdf</a></p><p>[22 ] EECC, GS1 Germany GmbH, Robert Bosch GmbH, SBB, Siemens AG, &amp; Spherity GmbH. (2023, March 27). Empowering Sustainable Products and Consumer Confidence through Verifiable Credentials v1.01. IDUnion. Retrieved April 26, 2023, from <a href="https://drive.google.com/file/d/1-JPm-TDpqWoXyghX_8o8_F-FSuZatILF/view?usp=share_link">https://www.google.com/url?q=https://drive.google.com/file/d/1-JPm-TDpqWoXyghX_8o8_F-FSuZatILF/view?usp%3Dshare_link&amp;sa=D&amp;source=docs&amp;ust=1682580329996953&amp;usg=AOvVaw2Nvinal4PXtZEXPXhGxh_a</a></p><p>[23] Guth-Orlowski, S. (2022, February 21). Accessing Digital Product Passports with Decentralized Identifiers (DIDs). Retrieved April 26, 2023, from <a href="https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3">https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3</a></p><p><strong>[24] Sabadello, M., &amp; Zagidulin, D. (2023, January 18). Decentralized Identifier Resolution (DID Resolution) v0.3 (M. Sabadello &amp; D. Zagidulin, Eds.; Draft Community Report). W3C. </strong>Retrieved April 26, 2023, from <a href="https://w3c-ccg.github.io/did-resolution/">https://w3c-ccg.github.io/did-resolution/</a></p><p><strong>[25] Huseby, D., &amp; Bohan, S. W. (2022, July 08). Hyperledger Aries. Hyperledger Foundation.</strong> Retrieved April 26, 2023, from <a href="https://wiki.hyperledger.org/display/ARIES">https://wiki.hyperledger.org/display/ARIES</a></p><p>[26] McGrogan, D., Cohen, G., Steele, O., &amp; Chang, W. (n.d.). Presentation Exchange 2.0.0 (D. Buchner, B. Zundel, M. Riedel, &amp; K. Hamilton Duffy, Eds.; DIF Ratified Specification). DIF. Retrieved April 26, 2023, from <a href="https://identity.foundation/presentation-exchange/spec/v2.0.0/">https://identity.foundation/presentation-exchange/spec/v2.0.0/</a></p><p><strong>[27] Sakimura, N., NRI, Bradley, J., &amp; Ping Identity. (2014, November 8). OpenID Foundation.</strong> Retrieved April 26, 2023, from <a href="https://openid.net/connect/">https://openid.net/connect/</a></p><p><strong>[28] Terbu, O., Lodderstedt, T., Yasuda, K., Lemmon, A., &amp; Looker, T. (2021, December 17). OpenID Connect for Verifiable Presentations. OpenID Foundation. </strong>Retrieved April 26, 2023, from <a href="https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0-07.html">https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0-07.html</a></p><p><strong>[29] Iannella, R., &amp; Villata, S. (2018, February 15). Open Digital Rights Language (ODRL) Version 1.1 (W3C Recommendation). W3C.</strong> Retrieved April 26, 2023, from <a href="https://www.w3.org/TR/odrl-model/">https://www.w3.org/TR/odrl-model/</a></p><p>[30] Eclipse Foundation. (n.d.). Eclipse Dataspace Components. Retrieved April 26, 2023, from <a href="https://projects.eclipse.org/projects/technology.edc">https://projects.eclipse.org/projects/technology.edc</a></p><p>[31] ISO/IEC JTC 1/SC 27. (n.d.). <em>Information security, cybersecurity and privacy protection</em>. ISO. Retrieved April 26, 2023, from <a href="https://www.iso.org/committee/45306.html">https://www.iso.org/committee/45306.html</a></p><p><strong>[32] Barreira, I., Izenpe, Gustavsson, T., Primekey, Wiesmaier, A., AGT International, &amp; Manso, C. G. (2013, December 20). Guidelines for trust service providers — Part 1: Security framework. ENISA.</strong> Retrieved April 26, 2023, from <a href="https://www.enisa.europa.eu/publications/tsp1-framework">https://www.enisa.europa.eu/publications/tsp1-framework</a></p><p>[33] Trust Over IP Foundation. (n.d.). The ToIP Model. Retrieved April 27, 2023, from <a href="https://trustoverip.org/toip-model/">https://trustoverip.org/toip-model/</a></p><p>[34] Wirrig, C., Colgan, A., Payson, B., &amp; Waldorf, E. (n.d.). OCI DSCSA Interoperability Profile v3.0.0. OCI. Retrieved April 26, 2023, from <a href="https://www.oc-i.org/resources-portfolio/oci-interop-v3-0-0">https://www.oc-i.org/resources-portfolio/oci-interop-v3-0-0</a></p><p>[35] Gronlier, P. (n.d.). Gaia-X Trust Framework. Retrieved April 27, 2023, from <a href="https://gaia-x.gitlab.io/policy-rules-committee/trust-framework/gaia-x_trust_framework/">https://gaia-x.gitlab.io/policy-rules-committee/trust-framework/gaia-x_trust_framework/</a></p><p>Stay sphered by joining Spherity’s <a href="https://mailchi.mp/fe1306b69858/spherity-newsletter">Newsletter</a> list and following us on <a href="https://www.linkedin.com/company/spherity">LinkedIn</a> and <a href="https://twitter.com/spherityproject">Twitter</a>. For press relations, contact communication@spherity.com.</p><p>Also tune into our <strong>Product Passport Pioneers Podcast</strong> with DPP policy makers, Governments, car manufacturers, and other industry experts on <a href="https://open.spotify.com/show/5lahNE1aratHDLmielDctZ?si=2587373ec5f14911">Spotify</a>, <a href="https://podcasts.apple.com/de/podcast/spherity-podcast/id1621254350?l=en">Apple Podcast</a>, <a href="https://www.buzzsprout.com/1955933">Buzzsprout</a>, <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5idXp6c3Byb3V0LmNvbS8xOTU1OTMzLnJzcw==">Google Podcast</a>, and <a href="https://www.youtube.com/@spherity2407/featured">YouTube</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1102c452020" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spherity/implementing-digital-product-passports-using-decentralized-identity-standards-f1102c452020">Implementing Digital Product Passports using decentralized identity standards</a> was originally published in <a href="https://medium.com/spherity">Spherity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The digital product passport — Perspective of the European Commission, DG Connect]]></title>
            <link>https://medium.com/spherity/the-digital-product-passport-perspective-of-the-european-commission-dg-connect-4a0bbcd7f159?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a0bbcd7f159</guid>
            <category><![CDATA[digital-product-passport]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[ecodesign-for-products]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <category><![CDATA[espr]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Thu, 13 Oct 2022 09:18:26 GMT</pubDate>
            <atom:updated>2022-10-13T09:18:26.450Z</atom:updated>
            <content:encoded><![CDATA[<h3>The digital product passport — Perspective of the European Commission, DG Connect</h3><h3>Summary of the Spherity Podcast‚ Product Passport Pioneers’ — Episode #2 with Ilias Iakovidis, European Commission DG Connect.</h3><p>The digital product passport (DPP) is regulated for the first time in the ‘new EU Battery regulation’ and proposed in the<a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_22_2013"> Ecodesign for Sustainable Products Regulation of the European Commission</a> published on March 30, 2022. On this occasion, we are keen to interview the makers of the DPP, who have worked behind the scenes to create the DPP concept and influenced the regulation for reaching the Goals of the European Green Deal. We discuss technical implementations and hurdles, and where it adds business values aside from regulatory compliance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5L40Xc-g45gDPhllwyqghw.jpeg" /><figcaption>Listen to the full interview at your favourite podcast app, e.g. <a href="https://www.buzzsprout.com/1955933">Buzzsprout</a></figcaption></figure><p>In our second episode, we invited Ilias Iakovidis, Advisor at the European Commission DG Connect to discuss with our Chief Innovation &amp; Solutions Officer, Dr. Susanne Guth-Orlowski, the upcoming EU circular economy regulations, the European Commission’s support, and the Ecodesign for Sustainable Products Regulations (ESPR) proposals. Ilias Iakovidis has worked for the Commission for 20 years, focusing on digitizing healthcare. With his extensive knowledge, Ilias aims to accelerate the circular economy transition by bringing digitization into the ecosystem.</p><p>Here’s a summary of our 5th episode. To know the details, visit our podcast for the <a href="https://open.spotify.com/episode/7L6y7FdgIKWBWpIX9rIBxa?si=4010cd11c1ef4bf6">full interview</a>.</p><p><strong>Q: What was your journey to the position that you have today?</strong></p><p>A: The first 20 years in the Commission, I’ve been working on digitizing healthcare. My experience in healthcare led me to see what I can do for the environment, i.e. to accelerate the transition to a circular economy while minimizing the conflicts between digital and green transition. The circular economy is maybe the biggest thing we can do for climate change. I’m using a lot of lessons learned from healthcare which I am now bringing into fruition in DG Connect, which was involved in defining the Digital Product Passport (DPP) for the new regulation (<a href="https://environment.ec.europa.eu/publications/proposal-ecodesign-sustainable-products-regulation_en">ESPR</a>) that came out on March 30, 2022.</p><p><strong>Q: What is the DG Connect?</strong></p><p>A: It’s a General Directorate (<em>french: Directorate General</em>). DG in the Commission is something like a ministry in a national government. <a href="https://ec.europa.eu/info/departments/communications-networks-content-and-technology_en">DG CONNECT</a> is the European IT Ministry that regulates telecommunications and is responsible for digital services like the Digital Market Act, the AI Act, and the Data Act. Thus, we work on data, AI, the internet of things (IoT), and digitalization in general. We are responsible for the single market regulations.</p><p><strong>Q: What is your role with regard to the DPP?</strong></p><p>A: I am coordinating the green digital transformation and as part of it I also work on the Digital Product Passport initiative. We work on this with three other DGs:</p><p>1. <a href="https://ec.europa.eu/info/departments/internal-market-industry-entrepreneurship-and-smes_en">DG GROW</a>, responsible for the internal market, industry, entrepreneurship, and SMEs),</p><p>2. <a href="https://ec.europa.eu/info/departments/energy_en">DG ENERGY</a>, which is in charge of Ecodesign legislation</p><p>3. <a href="https://ec.europa.eu/info/departments/environment_en">DG ENVIRONMENT</a>, which is in charge of environmental legislation and environmental issues.</p><p><strong>Q: The European Commission has published two regulations concerning the digital product passport: the “</strong><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52020PC0798#"><strong>New Battery Regulation”</strong></a><strong> and the </strong><a href="https://environment.ec.europa.eu/publications/proposal-ecodesign-sustainable-products-regulation_en"><strong>Ecodesign for Sustainable Products Regulation</strong></a><strong> (ESPR). How do those regulations relate to each other?</strong></p><p>A: There is the “<a href="https://environment.ec.europa.eu/strategy/circular-economy-action-plan_en">Circular Economy Action</a>” plan that was issued in March 2020. It includes the actions for the coming years on the circular economy. In March 2022 we implemented four of those actions.</p><p>1. The first action is the Ecodesign for Sustainable Product Regulation (formerly called “Sustainable Product Initiative”) which regulates that products which are sold on the European market are sustainable. It has three pillars:</p><ul><li>It forbids the destruction of unsold goods.</li><li>It enlarges the ecodesign with regards to material efficiency and minimizes waste.</li><li>It includes an innovative element: the digital product passport (DPP). The DPP is envisaged for a number of product categories. The “new battery regulation” had already introduced that concept 1,5 years ago but in a stricter sense for batteries.</li></ul><p>2. The second one is the strategy on textiles. In one phrase, we want that the <strong>“Fast Fashion” is “Out of Fashion”. </strong>This will minimize the chemicals for textiles and enlarge sustainable materials in the textile industry.</p><p>3. The third is revising the regulation on construction. This is very relevant because construction is causing 50% of resource extraction and 40% of the EU energy consumption goes to buildings. This means that around <strong>35–36% percent of emissions in the EU are from heating and cooling buildings</strong>. Therefore, building materials should be recyclable, repairable, more durable, and reusable. This will decrease the waste in the EU which is <strong>50% related to construction</strong>.</p><p>4. The fourth is supporting consumers in their green transition. It’s a revision of some directives to ensure that when consumers buy something they get — at the point of sale — a guarantee of durability, information relevant to the repair, and a verifiable claim using a standardized method (see also: <a href="https://ec.europa.eu/environment/eussd/smgp/initiative_on_green_claims.htm">Initiative on substantiating green claims</a>).</p><p><strong>Q: In an EU press release of March 30st 2022, it is stated that the Commission is “proposing new rules to make almost all physical products on the European market more environmentally friendly throughout their entire life cycle”. Does that mean that all goods are targeted by the ESPR, not only textiles, buildings, and batteries?</strong></p><p>A: The Ecodesign for Sustainable Products Regulation is a framework regulation. It will address one product category at a time. I suspect that textiles will be among the first product categories for which a delegated act will be defined. A delegated act is secondary legislation, where we will call for studies, impact assessments, and talk to all supply chain and value chain actors. As a result ESPR requirements for textiles specifically will be defined which become relevant for companies that are producing fashion, apparel, and clothes. So, digital product passports and their content will be designed per product category. After textiles, we will look at furniture and then steel or construction products.</p><p><strong>Q: How do you select the sequence of product categories for which delegated acts are defined?</strong></p><p>A: There is a whole team behind the selection of product categories, for example, electronics. — There is a process that determines which product category is the lowest hanging fruit and where we can make the biggest impact with regard to energy and material savings. Until today, the Ecodesign Initiative has saved 120 billion € just by telling the electrical appliances how to improve their design and thus their consumption. Now we are enlarging the ESPR by looking at the material consumption. There is a whole team working with the Joint Research Center (<a href="https://ec.europa.eu/info/departments/joint-research-centre_en">JRC</a>) and other research departments of the European Commission on how to select them.</p><p>The only product category that we exclude at the moment is food and pharmaceutical products. For food there is another initiative, called <a href="https://food.ec.europa.eu/horizontal-topics/farm-fork-strategy_en">Farm to Fork Strategy</a>, that is addressing the traceability of food materials</p><p><strong>Q: Does the ESPR define some general requirements for all digital product passports and each delegated act is making those more concrete for each product category?</strong></p><p>A: Yes, the digital product passport, the data it contains, and who can access it will be done per product category. But in order to make sure that we have one system across all product categories, we need a horizontal agreement on standards, identifiers, access rights management, and data. For example, we have to have codes (identifiers) for materials that are the same across the product categories. So, there is a system level of the product passport, an interoperability level that has to be common to all product categories.</p><p><strong>Q: What is the general concept of the product passport? What is the benefit?</strong></p><p>A: The digital product passport is basically about tracing and tracking information along the supply chain so that businesses know where their material comes from and what is in it. And then — even more importantly — it follows the product in order to make sure that there is support for repair, refurbishment, recycling, and end-of-life handling. It ensures the sharing of information with authorized actors.</p><p><strong>Q: Is it correct that the general DPP technical concept is the same so that raw material manufacturers can serve different value chains with the same solution, i.e. they don’t have to serve ten different systems for ten different value chains?</strong></p><p>A: That is probably the most important point to make. The basic system (for all product categories) has to be the same. Imagine an SME that is serving the textile industry and it’s serving the plastic bottle industry and others. The way they identify themselves and they enter information into those product passports or access them has to be the same. It cannot vary across the product categories because, e.g. you don’t want to have to authenticate yourself in one way to the textile industries supply chain product passport and in another way to batteries, and in another way to furniture.</p><blockquote>This is where Spherity comes to build the DPP solutions based on standardized decentralized identity technology.</blockquote><p><strong>Q: The European Union is supporting the implementation of digital product passports with fundings. Can you give us an overview of the EC-funded activities?</strong></p><p>A: The most visible project we launched is the Digital Product Passport project in the Digital Europe Program. It will be a coordination and support action to provide a DPP concept and prototype across three different value chains. This project will kick off after summer (in 2022). Other projects referring to the DPP started already as part of the Horizon Europe Programme (Twin Transition). More projects with reference to the DPP will come up in 2023 and 2024 to help manufacturers share and exchange data in an efficient way. In addition, reducing the administrative burden is one of the goals of the DPP.</p><p><strong>Q: Is one of the goals also to connect the digital product passports with systems that already exist?</strong></p><p>A: Of course, the biggest problems will be the interoperability with legacy systems and dealing with all the innovations e.g. decentralized identifiers and the decentralized world — championed by the distributed ledger technology. It does not always have to be a blockchain solution but the new idea of decentralization comes in very heavily and the public administration is still struggling with this concept.</p><blockquote>In a nutshell: That is why Spherity conducts this podcast — To create more understanding of where the decentralized technology comes in and what benefits it brings. One of the most important innovations is not the blockchain, but the concept of decentralized identifiers.</blockquote><blockquote>Bringing in the concept of self-sovereign identities for humans, companies, and products has some advantages: it makes the data verifiable and non-repudiatable, systems can check if the data was modified or includes “fake news”, it allows business confidentiality, self-sovereign managment of company data, and does not need a central platform to manage the entire digital product passport.</blockquote><p><strong>Q: Where do you see the need for these new technologies and what are your expectations of how they can help implement the digital product passport?</strong></p><p>A: They are essential, as we already took the decision in the regulation to call for a decentralized system. Unlike in the past, when everybody had to send us the information to a centralized database, we already decided that this (DPP) will be decentralized. So, every actor will keep the data at their site. We need to help small SMEs that do not have their own site.</p><p>There will be Cloud-as-a-Service to help us. We are working on big projects such as Gaia-X in Europe to make sure that everybody has access to some kind of cloud services.</p><p><strong>Q: Spherity is an implementation partner of the </strong><a href="https://www.gxfs.eu/"><strong>Gaia-X Federation Services</strong></a><strong>. We are building the </strong><a href="https://www.pressebox.com/pressrelease/ecsec-gmbh/Consortium-of-ecsec-Spherity-and-msg-won-the-implementation-project-of-the-Gaia-X-Notarization-API/boxid/1100786"><strong>Notarization API</strong></a><strong> as a reference implementation at the moment. Can we use the Gaia-x technology as a basis for the digital product passport?</strong></p><p>A: Yes, we see that as one of the possible solutions. We are technology neutral of course in the legislation but given the environment for a decentralized system where the product identifier brings the product information together virtually.</p><p>Decentralization is not a new concept. The electronic patient health record, for example, carries information from different systems, such as hospitals, labs, and doctors which is linked only by the customer’s identity. The system only allows authenticated medical doctors to access it and creates an audit trail. There is no area with a higher data sensitivity than in this use case. Companies have big considerations about their trade secrets and IPR. They don’t want that to be compromised.</p><p><strong>Q: We hear from every industry that business confidentiality is one of the largest requirements and considerations. Previous centralized engagements to make the supply chain more visible have failed because companies don’t want to give away their business data. This is why we think that a decentralized approach will have a higher acceptance in the industry. What other circumstances will make the DPP a success or what hurdles do you see?</strong></p><p>A: The data quality and the trust of all the players will be success factors. But trust is the result of a process that needs to be driven by the industry, not micromanaged by the Commission. The industry needs to get involved with all its B2B transactions. The DPP system needs to support a number of claims so that companies can prove that they are green and sustainable. <strong>The greenwashing era is over</strong>. Of course, it will take years until the data is verifiable and of good quality. We know that from the automotive sector. They have this big database (<a href="https://www.mdsystem.com/imdsnt/startpage/index.jsp">IMBS</a>) and for the first five years, a lot of companies just ignored it due to lack of quality. It will be an evolution. And B2C will also become relevant. If you have a sustainable product, you will want to communicate that to the customer.</p><p><strong>Q: In our previous episode, we talked to the Global Battery Alliance that is preparing to play the role of standardizing DPP data and its semantics for the battery passport. Do we need such consortia for every product category/vertical that you regulate?</strong></p><p>A: The ESPR framework regulation will lead to delegated acts. For example, we will invite the textiles and the construction industry for public consultations and public discussions. So the industries need to come together. In the European Green Digital Coalition companies even go beyond the regulative requirement. Therefore, for the DPP I recommend: <strong>Letting the industry drive it! </strong>Let them see the value of DPP and hopefully then even drive the standardization process. Because we need more standards for DPP we will need to come in and issue standardization mandates.</p><p><strong>Q: What other benefits do you see for the industry apart from being compliant with the regulation?</strong></p><p>A: Regulatory compliance should be just one goal. Companies want to show that they are sustainable. Only companies with sustainable business models will survive in the future. Also, companies need situational awareness, e.g. about the raw material they are using. And for situational awareness they need data. Think of <strong>products-as-a-service,</strong> where the companies keep owning the product. These companies need to know the state of health of their products, what performance level it still has, and when it has to be called back, refurbished, or repaired. Those new circular economy business models need a lot of information and they should see the digital product passport as the enabling mechanism for this.</p><p>We also want to support consumers in their green journey. Imagine, you buy a product online, and next to a price they also see the CO2 footprint.</p><p><strong>Q: Do you think the digital product passport can serve as a basis for a future CO2 tax?</strong></p><p>A: Well, we have to make the greener and more sustainable products cheaper.</p><p><strong>Q: Where do you think the digital product passport stands in two, five, and ten years?</strong></p><p>A: In two years, we will start to grasp the bigger picture and understanding of the DPP. It’s one of those big innovations that we are putting forward. In five years, few product categories will start having (incomplete) digital product passports.<strong> In 10 years, it will become a standard.</strong> The big issue is the other jurisdictions outside of Europe. We need to make the whole world come on board because (big) parts of the supply chains are outside of the EU.</p><p>If a company wants to sell products to the European Market, it needs to have the product passport onboarded. Products need to be green and sustainable.</p><p><strong>Q: Please share with us your final statement of the DPP.</strong></p><p>A: My most important message to the industry is to <strong>embrace the regulation</strong> and to see how it can help their transition to sustainability, how it helps consumers, and also how to make reports easier for the governments and market authorities.</p><p>If you’re interested in the topic, make sure to listen to the entire podcast! Spherity’s podcast season: Product Passport Pioneers provides an overview of the “New EU Battery Regulation,” which mandates that all batteries be issued a digital product passport in the future and how companies can achieve compliance using Spherity’s Digital Product Passport technology. Interviews with people who have influenced legislation or contributed to the success of the digital product passport are featured in this season. Several aspects of the digital product passport will be discussed, including its environmental and business impact, history, and predicted future.</p><p>Participate in discussions about how companies can achieve compliance with Spherity’s Digital Product Passport technology.</p><p>Don’t miss the next episodes by following us on <a href="https://open.spotify.com/show/5lahNE1aratHDLmielDctZ?si=2587373ec5f14911">Spotify</a>, <a href="https://podcasts.apple.com/de/podcast/spherity-podcast/id1621254350?l=en">Apple Podcast</a>, <a href="https://www.buzzsprout.com/1955933">Buzzsprout</a>, and <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5idXp6c3Byb3V0LmNvbS8xOTU1OTMzLnJzcw==">Google Podcast</a>!</p><p>Stay sphered by joining Spherity’s <a href="https://mailchi.mp/fe1306b69858/spherity-newsletter">Newsletter</a> list and following us on <a href="https://www.linkedin.com/company/spherity">LinkedIn</a> and <a href="https://twitter.com/spherityproject">Twitter</a>. For press relations, contact communication@spherity.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a0bbcd7f159" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spherity/the-digital-product-passport-perspective-of-the-european-commission-dg-connect-4a0bbcd7f159">The digital product passport — Perspective of the European Commission, DG Connect</a> was originally published in <a href="https://medium.com/spherity">Spherity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The battery passport — Perspective of the Global Battery Alliance]]></title>
            <link>https://medium.com/spherity/the-battery-passport-perspective-of-the-global-battery-alliance-c77147321812?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c77147321812</guid>
            <category><![CDATA[battery]]></category>
            <category><![CDATA[circulareconomy]]></category>
            <category><![CDATA[digital-product-passport]]></category>
            <category><![CDATA[digital-identity]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Thu, 19 May 2022 07:43:46 GMT</pubDate>
            <atom:updated>2022-05-19T07:43:46.929Z</atom:updated>
            <content:encoded><![CDATA[<h3>The battery passport — Perspective of the Global Battery Alliance</h3><h3>Summary of the Spherity Podcast‚ Product Passport Pioneers’ — Episode #1 with Torsten Freund, Head of Project Management “Battery Passport”, GBA</h3><p>The digital product passport (DPP) is regulated for the first time in the ‘new EU Battery regulation’ and proposed in the<a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_22_2013"> Ecodesign for Sustainable Products Regulation of the European Commission</a> published on March 30, 2022. On this occasion, we are keen to interview the makers of the DPP, who have worked behind the scenes to create the DPP concept and influenced the regulation for reaching the Goals of the European Green Deal. We discuss technical implementations and hurdles, and where it adds business values aside from the regulatory compliance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWEtvBUidxNq_iTH-t36Jg.jpeg" /></figure><p>In our first Product Passport Pioneers episode, our Chief Innovation &amp; Solution Officer at <a href="http://www.spherity.com/">Spherity</a>, <a href="https://www.linkedin.com/in/sguth/">Dr. Susanne Guth-Orlowski</a>, interviews Dr. <a href="https://www.linkedin.com/in/torsten-freund-3b440a">Torsten Freund</a>, Head of Project Management for the “Battery Passport” at the <a href="https://www.globalbattery.org/">Global Battery Alliance (GBA)</a>. Dr. Torsten Freund has worked for more than 25 years at BASF and since 2020 has been seconded to the GBA, leading the program to develop the GBA Battery Passport for the Electric Vehicle Batteries. The program aims to report all relevant indicators of the new battery regulation.</p><p>Have a read to quickly catch up with the highlighted discussion, or simply go to our podcast to access the <a href="https://open.spotify.com/show/5lahNE1aratHDLmielDctZ?si=ba8b0b3193dc40ee">full interview</a>.</p><p><strong>Q: ​​Why was the Global Battery Alliance (GBA) founded and who are its most important members?</strong></p><p>A: GBA began its journey as a project under the auspices of the World Economic Forum in 2017, set up in Davos, Switzerland. The battery industry and its link to climate protection became visible on our radar, and our utmost concern is that we achieve our goal of building a sustainable and responsible battery supply chain.</p><p>We have four stakeholder groups:</p><ul><li>Production companies of batteries, meaning industries that are directly involved in the value chain, such as car industries, OEMS, component producers, mining and refining companies, but also recycling companies.</li><li>Civil society, representing the interests in the space of environment protection and social aspects in the GBA; for instance institutions that eliminate child labor.</li><li>Government representatives, providing legal support for the legal implementation of the GBA, contributing inputs on how to incentivise companies to use the battery passport and consult on the intended outcomes.</li><li>IT companies that make the necessary data available to bridge the gap between the physical battery and the digital battery representation, i.e. the digital product passport.</li></ul><blockquote>In a nutshell: The GBA covers the entire battery ecosystem</blockquote><p><strong>Q: What will the digital product passport contain?</strong></p><p>A: The digital product passport will begin its journey containing verifiable data about</p><ul><li>greenhouse gas emissions from the entire value chain</li><li>social indicators, e.g. elimination of child labor, for example via third-party certifications.</li></ul><p>As a first step, the GBA will build an electronic exchange system prototype that contains those two metrics in a standardized way. Altogether, the GBA has identified about 30 required metrics that will be complemented in the long run.</p><blockquote>In a nutshell: The DPP will contain all information that supports a sustainable and responsible value chain.</blockquote><p><strong>Q: Do you think decentralized technologies can help to implement the DPP?</strong></p><p>A: I don’t have an opinion yet. The examples (of decentralized approaches) we have seen thus far have many promises and can certainly be one of the potential solutions.</p><p>Generally, the interoperability between systems, the data taxonomy/ontology, and standard data formats are critical for success as well as the auditability of the digital product passport.</p><p>We also need to address data governance, i.e. Who is allowed to see what and how can we manage access rights? Only those who are entitled should get access to the data of the product passport.</p><p><strong>Q: What will be the status of the DPP in 4 and 10 years from now ?</strong></p><p>A: In four years, in 2026, we need a first version of the Battery Passport that is fulfilling the core needs of the new Battery Regulation. After that we can think of additional, beneficial use cases that can build on top of the first version.</p><p>Digital passports are not a one-time event. We must carefully consider what we want to accomplish with a passport and the impact it should have in the end. In a circular economy, we are developing a sustainable and responsible value chain. It is critical to begin discussing not only battery passports but also material passports in general, emphasizing the importance of starting small and concrete. This action must be interpreted by all stakeholders as a call for a life-changing opportunity for the environment. Despite the obstacles, the key message is that change is possible, and we have the technologies to make it happen.</p><p><strong>Q: What are the biggest hurdles in developing a battery passport and how would you solve it?</strong></p><p>A: The first challenge is to manage expectations. Developing battery passport content and a flow of data exchange is tedious. It requires a stretch of thinking process over a period, so that we can deliver a mature solution to the ecosystem.</p><p>The second challenge concerns the interoperability of the data. Various initiatives have started to develop DPP. Yet, many initiatives with many standards will not create a standard. Therefore, designing common interchangeable or interoperable solutions is mission critical.</p><p>Setting a target for the next five years is a challenge, however we continue to take this responsibility and move forward.</p><p><strong>Q: What is your most important message:</strong></p><p>A: The key message is: “The change is possible to move from fossil fuels to electricity. We have the technology in place and batteries will play a major role. But this goal is too large for a single person, company, organization or stakeholder segment to solve alone. We must all work together NOW to make it happen.”</p><p>If you’re interested in the topic, make sure to listen to the entire podcast! Spherity’s podcast season: Product Passport Pioneers provides an overview of the “New EU Battery Regulation,” which mandates that all batteries be issued a digital product passport in the future and how companies can achieve compliance using Spherity’s Digital Product Passport technology. Interviews with people who have influenced legislation or contributed to the success of the digital product passport are featured in this season. Several aspects of the digital product passport will be discussed, including its environmental and business impact, history, and predicted future.</p><p>Participate in discussions about how companies can achieve compliance with Spherity’s Digital Product Passport technology.</p><p>Don’t miss the next episodes by following us on <a href="https://open.spotify.com/show/5lahNE1aratHDLmielDctZ?si=2587373ec5f14911">Spotify</a>, <a href="https://podcasts.apple.com/de/podcast/spherity-podcast/id1621254350?l=en">Apple Podcast</a>, <a href="https://www.buzzsprout.com/1955933">Buzzsprout</a>, and <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5idXp6c3Byb3V0LmNvbS8xOTU1OTMzLnJzcw==">Google Podcast</a>!</p><p>Stay sphered by joining Spherity’s <a href="https://mailchi.mp/fe1306b69858/spherity-newsletter">Newsletter</a> list and following us on <a href="https://www.linkedin.com/company/spherity">LinkedIn</a> and <a href="https://twitter.com/spherityproject">Twitter</a>. For press relations, contact communication@spherity.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c77147321812" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spherity/the-battery-passport-perspective-of-the-global-battery-alliance-c77147321812">The battery passport — Perspective of the Global Battery Alliance</a> was originally published in <a href="https://medium.com/spherity">Spherity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessing Digital Product Passports with Decentralized Identifiers (DIDs)]]></title>
            <link>https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/175ca455cee3</guid>
            <category><![CDATA[battery]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[circulareconomy]]></category>
            <category><![CDATA[product-passport]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Mon, 21 Feb 2022 12:03:01 GMT</pubDate>
            <atom:updated>2023-06-01T14:11:28.798Z</atom:updated>
            <content:encoded><![CDATA[<h3>How DIDs can serve as a single point of truth for the digital twins of products.</h3><p>Product information of tomorrow will be digital, i.e. every product will have a digital twin. The first regulation that is mandating digital product information in the form of a digital product passport is the <a href="https://medium.com/p/efdd09a4ed75">“new battery regulation</a>”. Those digital product passports need to be easily accessible and their information needs to be verifiable, as it may come from untrustworthy sources from all over the world.</p><p><a href="https://www.w3.org/TR/vc-data-model/">Verifiable credentials</a> are digital, verifiable attestations which can be used to capture such product information. They are always related to an identifier, in most cases to a <a href="https://www.w3.org/TR/did-core/">decentralised identifier</a>. This article explains what requirements a product identifier has, how decentralized identifiers can be used as the future unique identifier for products, what benefits this brings, what work needs to be done to get there and what projects already use decentralised identifierts today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvsLLCrsMZvgRlnKvmGOlw.png" /><figcaption>Products, preproducts and services world wide need a unified identifier (Photo by <a href="https://unsplash.com/@bernardhermant?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Bernard Hermant</a>)</figcaption></figure><h3>A. Requirements for digital product identifiers</h3><p>Finding the right identifier for digital products is not an easy task, therefore let’s start with the <strong>requirements</strong>, which have been collected from various relevant sources in the product passport ecosystem; such as from the talk of the <a href="https://www.din.de/de/din-und-seine-partner/termine/termine/cyberfruehstueck-zum-digitalen-produktpass-856324">European Commission </a>about the digital product passport, from internal discussions of <a href="https://idunion.org/?lang=en">IDunion</a>, from the <a href="https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=COM:2020:798:FIN">“new Battery Regulation”</a>, from discussions in the <a href="https://www.globalbattery.org/">Global Battery Alliance</a> Track &amp; Trace Group, from discussions in <a href="https://gaia-x.eu/what-is-gaia-x/federation-services">Gaia-X</a> / (Cartena-X) and internal Spherity discussions.</p><p>1. The identifier must be <strong>globally unique.</strong></p><p>2. The identifier solution must be <strong>scalable </strong>for global use.</p><p>3. The identifier must be suitable for being transported by a data carrier, such as a<strong> QR code</strong></p><p>4. The QR Code shall contain some minimal information that is readable without an internet connection.</p><p>5. When scanning the QR code, the identifier must serve as a <strong>globally unique, uniform resource locator (URL) </strong>on the internet. *</p><p>6.<strong> Customer facing</strong> technology to search for product information should be the same for all industries.</p><p>7. It must be possible by other means than scanning a QR code to <strong>search for the identifie</strong>r on the internet, and find product information.</p><p>8. The identifier must be usable for end consumer products but also for B2B - and <strong>pre-products</strong>.</p><p>9. The identifier format should be the same in all <strong>vertical and horizontal industries</strong>, so that each (pre-) product can be connected to another.</p><p>10. Identifiers should be suitable for <strong>batches </strong>but also for <strong>serialized products</strong>, i.e. with unique identifiers per product.</p><p>11. The identifier should allow to refer to<strong>/reuse existing widely used identifiers</strong>, such as <a href="https://en.wikipedia.org/wiki/Universal_Product_Code">universal product code (UPC)</a>, European Article Number (EAN), Global Trade Item Number (GTIN), the <a href="https://en.wikipedia.org/wiki/International_Standard_Book_Number">International Standard Book Number</a> (ISBN), or the ISO/IEC 15459 Unique Transport Unit ID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*E5B_2APlAPv6mGS3" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/0*xF_RREfhr9S4qqEA" /><figcaption>Figure 1: Widely used identifiers for products</figcaption></figure><p>12. It also must be possible to <strong>relate </strong>the product identifier to company identities, machine identities or human identities. This is necessary to e.g. identify a company that is responsible for and can be held liable for a product (identity).</p><p>13. Data that describes the product should be <strong>originated </strong>by its commercially responsible company.</p><p>14. The commercially responsible company must be able to <strong>manage the identifier.</strong></p><p>15. The identity technology must be <strong>based on open standards</strong> and be applicable for various use cases and industries<strong>.</strong></p><p>16. The <strong>barriers </strong>to use the worldwide unique identifier <strong>should be low.</strong></p><p>17. It should be <strong>compliant to Gaia-X,</strong> which was also mentioned by <a href="https://www.linkedin.com/in/boris-boehme-a75ab75b/">Boris Böhme</a>, Referatsleiter, Department Digitalpolitik of the German Ministry of Economic Affairs and Climate Action, on the first <a href="https://www.din.de/de/din-und-seine-partner/termine/termine/cyberfruehstueck-zum-digitalen-produktpass-856324">Cyberfrühstück about DPP of DIN</a> on February 10th, 2022. Gaia-X was initiated to create a next generation European data infrastructure, i.e. a secure, federated system that meets the highest standards of digital sovereignty.</p><p>18. The information that the identifier leads to should be <strong>trusted </strong>and cryptographically <strong>verifiable</strong></p><p>19. The product identifier must allow to collect <strong>life cycle</strong> information of the product.</p><p>20. No central look up components should be involved that lead to bottlenecks or allow (mass) data analytics.</p><h3><strong>B. Solution approach with decentralized identifiers</strong></h3><p>The identification technology that we propose for products is decentralized identifiers (DIDs) that are closely related with verifiable credentials (VCs), both standardized by the W3C. Using DIDs, product identifiers are not managed centrally by an organization (such as GS1) but in a decentral way by the product owner himself. Information that describes the product (also called subject) is issued by the product owner, audit organizations, or business partners in the form of electronically signed, trustworthy verifiable credentials or simple web links to additional resources.</p><p>For example the manufacturer of a plastic part issues the plastic raw material code of the product as a verifiable credential. The verifiable credential is linked to the decentralized identifier of the plastic product. With this mechanism any product information can be linked to the plastic part.</p><p>Decentralized identifiers are often stored on distributed ledgers (DLT), such as Ethereum. However DIDs can also exist without blockchains, by using other trusted sources (such as a web domain, see <a href="https://w3c-ccg.github.io/did-method-web/">did:web)</a> to manage their DID documents. DID documents link to the storage location of the verifiable credentials (or web-based resources) that describe the DID subject further and most importantly contain the public key for electronic signature validation.</p><p>The string below is an example for a decentralized identifier. <a href="https://www.w3.org/TR/did-core/#did-url-syntax">DIDs have the same syntax</a> as URLs:</p><pre>did:web:testing-did-web.spherity.com</pre><p>DIDs start with did defining the URI scheme, followed by the DID method/namespace (here: <a href="https://w3c-ccg.github.io/did-method-web/#did-document-integrity-verification">did:web</a>) followed by the DID method specific identifier, here the string “did:web:testing-did-web.spherity.com”. This string leads to a spherity subdomain, where the DID document is stored and can be found under the <a href="https://testing-did-web.spherity.com/.well-known/did.json">well-known URL.</a> The DID method specifies how the DID document is managed (e.g., created, found(resolved), updated or deactivated).</p><blockquote>Excurs: Multiple DID methods exist. In other DID methods, such as did:ethr, the DID documents are stored on a distributed ledger (in this case Ethereum) and the identifier string is the public key of the DID.</blockquote><p>The combination of the DID method and the method specific identifier ensure that a DID is <strong>globally unique, </strong>which<strong> </strong>leads us to our analysis of <strong>how decentralized identifiers fulfill the requirements of section A.</strong></p><p>1. DIDs are <strong>globally unique.</strong></p><p>2. The <strong>scalability </strong>of the solution will grow. Today, most DIDs are resolved by the Universal Resolver (which is not production grade) or professionally hosted DID resolvers as offered by Spherity.</p><p>3. DIDs can easily be<strong> encoded as QR code</strong> and when scanned</p><p>4. the QR code can show <strong>human readable</strong> information that does not require an internet connection and/or</p><p>5. lead to a <strong>URL</strong>.</p><p>6. The customer/user of the product passport would for any product have the same <strong>user experience</strong>, which is scanning in the QR code which leads him/her to more product information. This might require a dedicated application (see Section C).</p><p>7. Having a DID at hand, a <strong>search </strong>with a DID resolver will always lead you to the DID document of the product and thus to more information about it. DID resolvers can also be queried by APIs.</p><p>8. <strong>DIDs </strong>can be used <strong>for </strong><a href="https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/A_DID_for_everything.md"><strong>everything</strong></a>, also for products, pre-products, services, etc.</p><p>9. in <strong>all industries</strong> and</p><p>10. for all <strong>commercial sizes</strong>. Sometimes a DID is issued for a single product, sometimes for a product batch.</p><p>11. DIDs can be used as an <strong>abstraction level for already established identification schemes</strong>, such as GTINs, EANs, UPCs, ISBNs, or identifiers that conform to ISO/IEC (e.g ISO 15459). We give an example of how DIDs can be related to GTINs in Section C.</p><p>12. Additionally, DIDs can be used for company identities so that <strong>products can be linked to the company that placed the product on the market</strong>. The Global Legal Entity Identity Foundation (GLEIF) is currently beta testing their DID/VC based <a href="https://www.gleif.org/en/lei-solutions/gleifs-digital-strategy-for-the-lei/introducing-the-verifiable-lei-vlei">verifiable LEI</a>, other approaches foresee the binding of the company DID to a X.509 certificate or a GLN.</p><p>13. By issuing DIDs for their products, the <strong>commercially responsible companies</strong> can manage their products,</p><p>14. k<strong>eep control</strong> about the product information and who accesses it. Also fake products can be detected this way, when a product identifier is not linked to a verified manufacturer.</p><p>15. The technology is completely <strong>based on standards</strong>. Additionally, the <a href="https://www.gxfs.de/">Gaia-X federation services</a> will provide open source reference implementations of all needed components to work with DIDs and verifiable credentials in 2022.</p><p>16. Thus <strong>barriers </strong>to use the technology <strong>will be low</strong> and</p><p>17. the <strong>interoperability to Gaia-X </strong>is ensured.</p><p>18. The signed verifiable credentials make product information verifiable and thus trusted. For more benefits of the decentral approach, please refer to “<a href="https://medium.com/p/efdd09a4ed75">The product passport and its technical implementation”</a> by <a href="https://medium.com/u/184e9bf49b6f">Dr. Susanne Guth-Orlowski</a>.</p><p>19. In principle everyone can issue information about a given identifier. So also consumers can issue product usage information during the <strong>product life cycle</strong> (please also refer to Section D).</p><p>20. Due to the decentral nature of the technology, <strong>no central components are needed</strong>. DID resolvers can easily scale and grow on the job as well as other technologies around them.</p><p>Of course, even though no central technical components are required, this approach needs a <strong>Governance </strong>that decides on standards, e.g. the description standards of the product such as the <a href="https://pcds.lu/">product circularity data sheet</a> or the GS1 standards <a href="https://www.gs1.org/standards/epcis">EPCIS &amp; Core Business Vocabulary</a>, the used encryption algorithms, the accepted company identification schemes and did-methods. One first example of such a governance is the <a href="https://www.oc-i.org/">Open Credentialing Initiative</a> (OCI) that defines the standards for the pharmaceutical supply chain in the US to comply with the Drug Supply Chain Security Act (DSCSA).</p><h3><strong>C. Example implementation with GS1 digital link and DID binding</strong></h3><p>This section shows how decentralized identifiers can be linked to already established industry identifiers, such as (S)GTINs of GS1. The same principles can be applied to other widely used identifiers, such as <a href="https://en.wikipedia.org/wiki/International_Standard_Book_Number">International Standard Book Number</a> (ISBN), ISO/IEC 15459 Unique Transport Unit ID, Universal Product Code (UPC), and many more. The decentralized identifier works here as an abstraction layer for existing identification standards.</p><p>What is special about the GS1 standard, is that to every GS1 identifier, there is already the possibility to register a <a href="https://www.gs1.org/standards/gs1-digital-link">GS1 digital link</a> and define several link types that lead you to a web based product page. We will use the GS1 digital link in our example below.</p><p>To create a globally unique product DID, the manufacturer would use an open source or commercially available wallet. Using our DID example from above the DID document below is stored under the well-known URL of a web domain (not on a DLT / blockchain). It contains the DID, the cryptographic algorithms used and includes service endpoints where more information about the product DID can be found. <strong>It is the gateway and single source of truth to product information.</strong></p><p>One service endpoint is the GS1 digital link which leads to more (public) product information. The second service endpoint leads to a protected storage for verifiable credentials. To receive those credentials, a requestor needs to be authorized to access the storage and send requests that are compliant to the <a href="https://identity.foundation/didcomm-messaging/spec/">DIDcomm</a> protocol. Additional service endpoints can lead to other descriptions and certificates of the product, such as a digitally signed eco label by the ministry of environment or an ISO certification. The DID above described DID document has the following syntax.</p><blockquote>Note: You can checkout the DID document yourself by resolving the DID “did:web:testing-did-web.spherity.com” with the <a href="https://dev.uniresolver.io/">Universal Resolver</a>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-T8iGFzzlzcOkaaEtBLAHA.png" /><figcaption>Figure 2: The product’s DID document: A gateway to the GS1 digital link and verifiable credentials</figcaption></figure><p>Now, how do I get from the DID to the product information as an end customer? For this, the user needs a mobile app that is able to use the camera, scan in the QR code, read out the DID, send it to a DID resolver, receive the DID-document, find the GS1 digital link and open the product page in a browser. Alternatively, DIDs can be resolved by a web server that calls a resolver. This ‘deep link’ looks as follows:</p><pre><a href="https://dev.uniresolver.io/1.0/identifiers/did:web:testing-did-web.spherity.com">https://dev.uniresolver.io/1.0/identifiers/did:web:testing-did-web.spherity.com</a></pre><p>Most mobile devices only support the latter today.</p><p>You could argue that we should use the digital link in the product QR code directly. True, but that only works for consumer goods that have a (S)GTINs and manufacturers that are GS1 customers. In the supply chain, though, we have many pre-products that do not have an (S)GTIN, and use other identification schemes as mentioned above. Also, we believe that issuing identifiers by a central organization will be less needed in the future (see also: <a href="https://w3c-ccg.github.io/did-primer/#how-dids-differ-from-other-globally-unique-identifiers">A primer for decentralized identifiers</a>); with a wallet in your hand, you can create globally unique product codes yourself.</p><p>Finally, for very sensitive information, the second service endpoint can be contacted to receive signed <strong>verifiable credentials</strong>. For this the user app needs to be a full featured wallet that can communicate with a secured service endpoint (e.g. via <a href="https://identity.foundation/didcomm-messaging/spec/">DIDcomm</a>), has the necessary access rights, that can ask for verifiable credentials, and that can verify their signatures / proofs. This is a built-in security layer which is required when it comes to highly confidential supply chain data that should <em>only be accessible to authorized partie</em>s.</p><p>As an <strong>alternative, </strong>organizations that issue identification schemes, such as GS1, ISBN, ISO, etc. can create their own DID method that is optimized to their specific use cases. We could think of a GS1 DID method (did:gs1:[gtin]) an ISBN DID Method (did:isbn:[ISBN]) or an ISO DID method (did:iso-15459:[iso-15459]), that return DID documents with DID-method specific service endpoints.</p><h3><strong>D. Summary &amp; Discussion</strong></h3><p>This section aims to summarize the benefits when using DIDs for product identification the future work that needs to be done and mention some projects that have used DID to identify <a href="https://medium.com/spherity/the-cloud-edge-approach-8052160fc0ff">IOT devices</a> and products. <strong>Benefits </strong>in our view are:</p><ul><li>With DIDs the world would have a <strong>standard entry point to product information </strong>and respects already existing identifiers.</li><li>Using a wallet, every commercial actor can <strong>create and manage their own </strong>globally unique product identifier. As mentioned above, free, open source wallet reference implementations for all roles are currently developed by the Gaia-X project, which means that technical entry barriers will be low.</li><li>Existing public product information is accessible in the same way as critical highly confidential product information which becomes <strong>verifiable </strong>and thus <strong>trusted</strong>.</li><li>DIDs can be applied to all “things” that need to be identified and thus open up the potential application area to e.g. the <strong>Smart Home, all supply chains and the Industry 4.0 sector.</strong></li><li>Product DIDs can be connected to everything else, such as enterprise DIDs (e.g. a verifiable LEI or verifiable GLN) and have the potential to serve as a<strong> basis for VAT or CO2 taxation.</strong></li></ul><p>To walk towards DIDs as product identifiers, some <strong>future work</strong> is required:</p><ul><li><strong>Migration and integration efforts</strong> are necessary to move from existing identifiers to DIDs or to integrate them into the existing landscape. The described concept is thus a long term goal towards unified product identification. However, we assume that all technical components will be available as free, open source components. For integrations into existing identity provider infrastructure, please refer to “<a href="https://medium.com/spherity/on-ssi-enabled-idp-solutions-d382abc4b433">On SSI-enabled IDP Solutions</a>” by <a href="https://medium.com/u/2d7ca4c61292">Carsten Stöcker</a>.</li><li><strong>Different DID methods</strong> lead to different storage locations and management of DID-documents. Interoperability between various DID methods need to be made available by technology suppliers and in the long run by additional standardization efforts.</li><li><strong>Costs </strong>might occur for secure key generation of product keys. E.g. if the DID document of every product would need to be anchored to Ethereum this would cost approx. 1 USD per product / batch. This is not affordable for most serialized pharmacy products. However,<a href="https://ethereum.org/en/developers/docs/scaling/"> Layer 2 and other scaling</a> approaches marginalize those costs. Alternative solutions such as private- , consortial- , para chains can serve as a DID anchor as well and of course not using a blockchain at all (as explained in the example in this article with the did:web method) is an attractive solution.</li><li>High available <strong>resolvers </strong>are needed for this solution approach. Next to the Universal Resolver, which is not production grade today, some companies (such as <a href="https://www.linkedin.com/posts/sguth_sure-spherity-universal-resolver-for-enterprises-ugcPost-6829045515905310720-NT5B">Spherity</a>) already started product grade resolvers that are easily scalable.</li></ul><p>For some aspects further concept work is needed, for example how to add <strong>usage information</strong> to a product. In the case of batteries,<strong> </strong>the state of health (SOH) needs to be added to the product records to later decide on their reusability. However, the user does not control the DID document of the battery, so how can a user issue Verifiable Credentials about the battery DID, for example for each storage procedure? One solution could be that the consumer receives a delegation key with limited rights to sign usage records in the form of verifiable credentials to the battery DID.</p><p>This solution has already been implemented and tested in the <a href="https://www.dena.de/future-energy-lab/">dena research project</a> of the German Ministry of Economic Affairs and Climate Action, when implementing a <a href="https://youtu.be/JhuUxVy7X60">machine identity ledger for smart meter gateways</a> that issued metering records as verifiable credentials. Other projects, where DIDs have been used for “things” and products are:</p><p>The <a href="https://www.merckgroup.com/en/research/innovation-center/highlights/blockchain.html">M-Trust</a> project by Merck KGaA, enabling food product authenticity and product data transparency. It gives actors the possibilty to access, attach and request data associated with a food product. Manufacturers, logistics providers, and suppliers always stay in control of their data and manage the access rights to it.</p><p>The <a href="https://railchain.berlin/">Rail Chain</a> Project funded by the German “Bundesministerium für Verkehr und digitale Infrastruktur (BMVI)”. In this project, Spherity issued a DID for each intelligent train component which made them addressable and enabled communication among them in a secure way.</p><p><em>*Update: In the new Ecodesign for Sustainable Products Regulation the EU decided to propose to use the GTIN (i.e. ISO 15459 compatible IDs) which caused heavy protests from the Identity Community.</em></p><p>** This article received an IEEE paper award in the CRFID/RAIN Alliance Digital Twin Number Resolver Challenge in 2022.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXC6Vno4dlNfi_9pK6bUzA.jpeg" /></figure><p>* * *</p><p>If you like this article, please follow <a href="https://medium.com/u/184e9bf49b6f">Dr. Susanne Guth-Orlowski</a> on Medium.</p><p>For more information about Spherity’s Digital Product Passport, please refer to our DPP landing page: <a href="https://www.spherity.com/digital-product-passport">https://spherity.com/digital-product-passport/</a></p><p>If you are intending to build digital product passport technology, feel free <a href="/service/mailto:communication@spherity.com">to reach out to Spherity</a>. You can also follow Spherity on <a href="https://medium.com/spherity">Medium</a>, <a href="https://twitter.com/spherity">Twitter</a>, <a href="https://www.linkedin.com/company/18314188">LinkedIn</a> or sign up for our <a href="https://mailchi.mp/fe1306b69858/spherity-newsletter">newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=175ca455cee3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spherity/accessing-digital-product-passports-with-decentralized-identifiers-dids-175ca455cee3">Accessing Digital Product Passports with Decentralized Identifiers (DIDs)</a> was originally published in <a href="https://medium.com/spherity">Spherity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cloud-Edge Approach]]></title>
            <link>https://medium.com/spherity/the-cloud-edge-approach-8052160fc0ff?source=rss-184e9bf49b6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8052160fc0ff</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[smart-meter]]></category>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[cloud-wallet]]></category>
            <dc:creator><![CDATA[Dr. Susanne Guth-Orlowski]]></dc:creator>
            <pubDate>Thu, 16 Dec 2021 10:04:23 GMT</pubDate>
            <atom:updated>2022-02-21T11:56:09.090Z</atom:updated>
            <content:encoded><![CDATA[<h4>Secure and efficient solution for establishing trust in global operating IoT networks</h4><p>This article shows how IoT devices can be uniquely identified and decentrally managed at large scale with the cloud-edge approach. It discusses how usual drawbacks of IoT devices such as low bandwidth, low availability, limited computing power, unsatisfactory update capabilities, etc., can be addressed by moving certain functionalities to a cloud component. Also, it explains how metering data of IoT devices becomes verifiable and thus forms the basis of establishing trust in global operating IoT networks. The cloud-edge concept is applicable to all machines, such as trucks,<a href="https://spherity.com/mobility-daimler-mobility-blockchain-platform/"> cars</a> and<a href="https://railchain.berlin/"> trains</a>,<a href="https://medium.com/spherity/walking-towards-climate-neutrality-as-a-service-cnaas-bd01c188e8c2"> direct air capture</a> plants, smart meters, smart city devices, and many more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ymmCqKMYnqDnsR9AxMsjww.jpeg" /><figcaption>The cloud-edge approach can uniquely identify and decentrally manage IoT devices at large scale. (Photo from <a href="https://unsplash.com/photos/AlzwNY1AIrw">Unsplash</a>)</figcaption></figure><h3>Decentralized Identifiers for Machines</h3><p>The global edge computing market is projected to reach $16.6B by<a href="https://www.einnews.com/pr_news/554340408/edge-computing-market-to-reach-16-556-6-million-by-2025-32-8-cagr-record"> 2025</a>. The global installed base of Low-Power WAN-enabled active devices grew 62% to 450 million during 2020 and is expected to grow a further 47% to 660 million in<a href="https://iotbusinessnews.com/2021/10/20/00352-5-things-to-know-about-the-lpwan-market-in-2021/"> 2021</a>. Cyber security attacks are rising constantly with main targets being governments and<a href="https://www.securitymagazine.com/articles/95668-cyberattacks-increased-17-in-q1-of-2020-with-77-being-targeted-attacks"> industrial companies</a>. As IoT devices will play an essential role in the management of crucial world wide business processes, it’s time to review some security and management aspects of those devices.</p><h4>Trusted Devices</h4><p>When an IoT device sends information, e.g., about its status or metering data, it is essential that the device is trustworthy; especially when it is part of the critical infrastructure such as smart meters for energy-producing power plants.</p><p>A trusted device can prove its own identity. One way to authenticate a device is to verify the digital signature it creates for the data it sends. Digital signatures can be based either on a central or a decentralized Public Key Infrastructure.</p><p>The approach we are presenting here is based on a <strong>decentralized </strong>Public Key Infrastructure (PKI), as defined in the W3C standards ‘<a href="https://www.w3.org/">Decentralised Identifiers</a>’ and ‘<a href="https://www.w3.org/TR/vc-data-model/">Verifiable Credentials’</a>. This approach has a few advantages, for example:</p><ul><li><strong>Self-sovereignty. </strong>No central component is creating and managing identities, their key material, and their related data. The identity itself is responsible for this and, thus, can decide what data is shared with third parties when and for what purpose.</li><li><strong>Describing Identities</strong>. With verifiable credentials more information can be made verifiable about a public key holder than only their name, city, company, etc. as is currently available in the traditional X.509 certificate of a central PKI. Working with verifiable credentials allows for describing identities with unlimited data sets that are issued by trusted institutions.</li><li><strong>Decentralized Integration</strong>. Networks of trusted devices can easily be integrated with each other by accepting mutual trust anchors, i.e. trusted institutions that certify the trustworthiness of a device.</li><li><strong>Credential Chaining. </strong>Verifiable Credentials can link to other credentials and, thus, create a credential chain. With this mechanism, not only the identity of the device can be verified but also who has installed it, who has manufactured it and who has audited it.</li></ul><h4>The wallet</h4><p>To create and manage decentralized identifiers, send, receive, and verify verifiable credentials, a piece of software is required, which is called “Wallet”. Just like a physical wallet or purse nowadays, in future your electronic wallet will hold all your passports, certificates, access cards, and membership cards in the form of verifiable credentials issued by (trusted) institutions. This way, not only humans can achieve trustworthiness but also companies, products, processes, machines, and also IoT devices. Each IoT device that aims at participating in the decentralized ecosystem requires a wallet.</p><h3>The Edge-only approach</h3><p>A wallet for an IoT device needs to fulfill certain functionalities. The most security-relevant functionality is to sign the data it issues. Further functionalities are the holding of credentials that others have issued about the IoT device or verifying credentials that are presented by other wallets. More operational requirements for a wallet are, for example:</p><ul><li>Implementing the latest version of the W3C, DIF and other standards used in the ecosystem, such as communication protocols between wallets or integration into a workflow software.</li><li>Serve the latest version of the blockchain protocol or even support multiple blockchain protocols.</li><li>Allowing for fast software updates.</li><li>Providing high availability, e.g. for external requests about the device status.</li><li>Allowing access from multiple devices (mobile, laptop, tablet, etc.)</li><li>Managing secure connections to other devices/wallets.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ai49YAAixKdMSCyT" /><figcaption>Figure1: Edge-only approach of a decentralized (machine) identity ledger</figcaption></figure><p>Implementing such functionality for a wallet that runs on the IoT device is often challenging because resources, such as storage, processing power, bandwidth, and accessibility, are often limited. This challenge can be addressed by the cloud-edge approach explained in the following chapter.</p><h3>Characteristics of the Cloud-Edge Approach</h3><p>The cloud-edge approach splits the responsibility of the wallet into two parts. One part that resides on the IoT device (edge) and a second part that manages the remaining functionalities in the Cloud. Using an example from the energy sector, we are describing the cloud-edge approach for the creation of unique, digital identities for Smart Meter Gateways. These are devices to meter the production from power plant units like wind turbines and solar panels. The solution has been implemented in the<a href="https://future-energy-lab.de/piloten/blockchain-identity-ledger/"> BMIL project</a> funded by the German Ministry of Energy and Economic Affairs. In the BMIL project,<a href="https://www.my-oli.com/projekte"> OLI Boxes</a> were used as IoT devices, representing the Smart Meter Gateway by safely managing its private key.</p><p>This approach describes the concept of dual responsibility of a blockchain wallet, where the security-critical part of the responsibility is taken over by the IoT device, here the Smart Meter Gateway, and the other part by a cloud component. The approach implements a secure and efficient solution for a distributed energy system where energy-producing power plant units are uniquely identified and their identities are stored on a decentralized ledger. This machine identity ledger can then serve as a basis for a large number of energy-related use cases, such as P2P energy trading, energy flexibility markets, proof-of-origin for green energy and so forth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*406hgUUX824A0fqf" /><figcaption>Figure 2: Cloud-edge approach with key management at the edge and process management in the cloud</figcaption></figure><p>In this solution the key material remains at the local edge device in a hardware wallet, the OLI Box in our example. This means the security-relevant keys are stored on a secure, dedicated physical device and not in a program (Software Wallet). The management of the processes and business logic is largely moved to the cloud. In this cloud-edge approach the cloud part is often referred to as a digital twin.</p><p>The cloud-edge approach makes it possible to cover the following scenarios:</p><ul><li><strong>Offline operation</strong>: The cloud-edge approach allows certain functions to remain available even when the IoT device is temporarily offline. In principle, faster response times can be expected from the cloud component than from IoT devices, which are often located in private, closed networks. This makes the processes less susceptible to disruptions on the sometimes long and complex transmission paths via different infrastructures (LTE, cloud, VPN, etc.).</li><li><strong>Continuous operation: </strong>The cloud component can be migrated to new software versions without downtime. This enables continuous operation of critical infrastructure and, at the same time, allows adding new functionalities on the fly.</li><li><strong>Bulk operations</strong>: In order to maintain the same software status in the network, all wallets must be updated as simultaneously as possible. With the cloud-edge approach this can be done at the push of a button through bulk operations of the cloud components. Network configurations can also be carried out efficiently via bulk updates.</li><li><strong>(Blockchain) Protocol-independent:</strong> By splitting the responsibility in two, it is possible to make the edge blockchain-independent or interoperable. The cloud component takes over the abstraction to the various distributed ledger technologies (DLTs). For example, the Spherity wallet makes it possible to switch from the currently used Ethereum to Hyperledger Ledger Indy, other ledgers or DID methods. Since DLTs are still constantly evolving, this is a <em>future-oriented concept.</em> The complexity of other communication protocols, such as wallet-to-wallet communication, can be abstracted away from the edge device software.</li><li><strong>Identity- &amp; Access Management (IAM):</strong> Integrations into existing company IAM technologies, such as Keycloak and OpenID-Connect, can be provided <em>once</em> by the cloud wallet and not by every edge node.</li><li><strong>User experience &amp; monitoring: </strong>IoT devices can be conveniently displayed, monitored and managed in a cloud wallet dashboard. Cloud wallets can also be accessed from different devices (mobile, tablet, laptop), which is what end users demand.</li><li><strong>Tests, simulations and forecasts:</strong> New functionalities and use cases, such as the introduction of green power certificates, can be easily tested via cloud environments. After a software update, grid reliability can be tested with the cloud wallet before going live. In the energy use case, simulations for grid optimization and flexibility can also be performed with clones of the actual devices. According to the<a href="https://www.gaia-x.eu/"> Gaia-X</a> vision, it shall become possible to generate forecasts about the development of energy networks using the explained technology as the basis.</li><li><strong>Key Management: </strong>Through the cloud-edge approach, various key management solutions can be made available in the cloud wallet. Each use case will determine the required security level for the private keys, e.g. if a Hardware Security Module or a Multi-Party Signature is required for the process. The business logic can then choose from the available key management options.</li></ul><p><strong>Implementing the Cloud-Edge Approach</strong></p><p>The cloud-edge approach is implemented by using a key delegation mechanism defined in <a href="https://github.com/ethereum/EIPs/issues/1056">ERC: Lightweight Identity #1056</a>. With this standardized feature it is possible to delegate certain operations to the cloud wallet. This means that the cloud component can act on behalf of the IoT device. It is facilitated by a cryptographic operation that links the public key of the cloud component to that of the edge device (here the OLI box). Key delegation is an essential part of this solution and will be described in a separate, more technical article.</p><h3>Summary</h3><p>The introduced cloud-edge solution approach mitigates the limitations of an “edge-only” concept, such as lower bandwidth and availability, limited computing power, more difficult software updates, especially for security reasons, and in the case of Smart Meter Gateways, a new BSI certification to be performed. The concept is applicable to all machines, such as trucks,<a href="https://spherity.com/mobility-daimler-mobility-blockchain-platform/"> cars</a> and<a href="https://railchain.berlin/"> trains</a>,<a href="https://medium.com/spherity/walking-towards-climate-neutrality-as-a-service-cnaas-bd01c188e8c2"> direct air capture</a> plants, smart city devices, and many more.</p><p>European projects, such as <a href="https://www.gaia-x.eu/">Gaia-X</a>, that have the goal to build a trusted platform for industry data are using decentralised identifiers as a basis. Also the upcoming<a href="https://medium.com/post/efdd09a4ed75"> digital product passport</a> will contain verifiable data by various issuers, such as proving that green energy has been used to manufacture an EV battery. The cloud-edge approach makes such complex endeavors possible and its technical implementation manageable.</p><p><strong>Watch the video introducing Spherity’s role in building Blockchain Machine Identity Layer for the Deutsche Energie-Agentur (dena) project to learn more.</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJhuUxVy7X60%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJhuUxVy7X60&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/66a1621537da02c01bc6b08e07d7c410/href">https://medium.com/media/66a1621537da02c01bc6b08e07d7c410/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMu0HOAezcKI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMu0HOAezcKI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMu0HOAezcKI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4c301e5f99d3d2c2c0bddc7809eb006/href">https://medium.com/media/f4c301e5f99d3d2c2c0bddc7809eb006/href</a></iframe><p>If you like this article, please follow <a href="https://medium.com/u/184e9bf49b6f">Dr. Susanne Guth-Orlowski</a> on Medium.</p><p>If you are intending to implement a cloud-edge approach, feel free <a href="/service/mailto:communication@spherity.com">to reach out to Spherity</a>. You can also follow Spherity on <a href="https://medium.com/spherity">Medium</a>, <a href="https://twitter.com/spherityproject">Twitter</a>, <a href="https://www.linkedin.com/company/18314188">LinkedIn</a> or sign up for our <a href="https://mailchi.mp/fe1306b69858/spherity-newsletter">newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8052160fc0ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spherity/the-cloud-edge-approach-8052160fc0ff">The Cloud-Edge Approach</a> was originally published in <a href="https://medium.com/spherity">Spherity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>