CARE ID's DPP confirmed technically compatible with CIRPASS-2's reference architecture
𝗪𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝗰𝗼𝗻𝗻𝗲𝗰𝘁 𝗮 𝗿𝗲𝗮𝗹 𝗗𝗣𝗣 𝘁𝗼 𝘁𝗵𝗲 𝗘𝗨 𝘀𝘆𝘀𝘁𝗲𝗺?
We tested CARE ID's DPP with CIRPASS-2 - Digital Product Passport mock EU Registry & Validator.
𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝟱 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗼𝗻 𝗵𝗼𝘄 𝘁𝗵𝗲 𝗘𝗨 𝗗𝗣𝗣 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗿𝗲𝗮𝗹𝗹𝘆 𝘄𝗼𝗿𝗸𝘀:
1. 𝙏𝙝𝙚 𝙀𝙐 𝘿𝙋𝙋 𝙨𝙮𝙨𝙩𝙚𝙢 𝙞𝙨 𝙨𝙩𝙧𝙪𝙘𝙩𝙪𝙧𝙚𝙙 𝙖𝙨 𝙖 𝙛𝙚𝙙𝙚𝙧𝙖𝙩𝙚𝙙 𝙖𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚:
Company DPP servers (data source) → EU Registry (identifier index) → Data Extractor (pulls from source) → Validator/Comparator
The Registry does not store full DPP data. It records identifiers and references (e.g. liveURL), while the actual data remains distributed across company systems.
→ Implication: Brands will need to own and manage structured product data themselves.
*The detailed structure of this data will ultimately depend on the official vocabulary and data models expected under the upcoming ESPR delegated acts for textiles.
2. "𝙡𝙞𝙫𝙚𝙐𝙍𝙇" ≠ 𝙘𝙪𝙨𝙩𝙤𝙢𝙚𝙧 𝙥𝙖𝙜𝙚
The liveURL is not the QR landing page. It must provide machine-readable product data for EU systems.
→ In practice, two separate endpoints are required:
Customer-facing page
Machine-readable DPP endpoint
3. 𝙑𝙖𝙡𝙞𝙙𝙖𝙩𝙞𝙤𝙣 𝙞𝙨 𝙨𝙚𝙢𝙖𝙣𝙩𝙞𝙘, 𝙣𝙤𝙩 𝙟𝙪𝙨𝙩 𝙨𝙩𝙧𝙪𝙘𝙩𝙪𝙧𝙖𝙡
CIRPASS-2 validation includes:
JSON Schema and SHACL
This moves DPP from "data presence" → data meaning.
However, textile-specific vocabularies and rules are not finalised yet, so full regulatory validation is still evolving.
4. 𝙏𝙝𝙚 𝙨𝙮𝙨𝙩𝙚𝙢 𝙖𝙡𝙧𝙚𝙖𝙙𝙮 𝙚𝙭𝙥𝙚𝙘𝙩𝙨 𝙞𝙢𝙥𝙚𝙧𝙛𝙚𝙘𝙩 𝙙𝙖𝙩𝙖
The DPP Data Extractor does not assume perfect compliance. It can retrieve data even from partially aligned structures.
→ Reality: The ecosystem is designed for gradual adoption, not perfection from day one. Brands don't need to wait until everything is perfect to start.
5. 𝙏𝙝𝙚 𝙧𝙚𝙖𝙡 𝙘𝙝𝙖𝙡𝙡𝙚𝙣𝙜𝙚 𝙞𝙨 𝙙𝙖𝙩𝙖 𝙢𝙤𝙙𝙚𝙡𝙡𝙞𝙣𝙜
Connecting to the infrastructure is relatively straightforward.
The real work is:
vocabulary mapping
schema alignment
semantic rule compliance
standard identifiers
The CIRPASS-2 open-source tools provide a valuable way to explore how real DPP systems may interact with the emerging EU infrastructure.
This is not a compliance assessment, but it demonstrates that CARE ID's DPP architecture is technically compatible with the current iteration of the reference architecture being developed within CIRPASS-2.
Our next step is to align CARE ID’s internal data models with the final textile DPP standards once they are defined through the ESPR delegated acts.
*For reference, we have included a sample metadata payload used during our test with the CIRPASS-2 mock EU Registry. The endpoints shown (including the liveURL) were generated for testing to simulate how CARE ID DPP data could be registered and retrieved within the EU DPP architecture.