+ "description": "The mission of the Universal Object & Resource Attestation (UORA) Community Group is to develop a vendor-neutral, decentralized protocol for the identity, state verification, and lifecycle tracking of physical assets. By bridging the gap between physical objects and digital identifiers, UORA enables every resource to function as a first-class citizen of the internet, fostering global trust, transparency, and interoperability across supply chains and industries.\n\n<h4>Scope</h4>\nThe group will focus on the technical specifications required to bind physical objects to the digital world using the W3C's foundational standards for Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).</p>\n<ul>\n<li>Universal Addressing: Develop protocols for assigning and resolving DID-native addresses to discrete physical units (at Batch, SKU, or Serial-level granularity).</li>\n<li>Attestation Schemas: Define data models and vocabularies for \"Event-Based Attestations\" that document a physical asset's lifecycle. Core event types include, but are not limited to:</li>\n<li>Origin: Proof of creation, mining, or manufacture.</li>\n<li>Transfer: Change of custody or ownership.</li>\n<li>Transformation: Processing, assembly, or modification.</li>\n<li>Disposition: Recycling, decommissioning, or end-of-life.</li>\n<li>Secure Physical Binding: Establish best practices and specifications for the tamper-evident linking of a digital DID to a physical anchor (e.g., via NFC, QR, cryptographic hardware, or IoT sensors) to verify possession and state.</li>\n<li>Implementation & Interoperability: Create guidelines for integrating UORA with existing business systems (e.g., ERP, SCM) and networks to ensure practical adoption.</li>\n</ul>\n\n<h4>Deliverables</h4>\n<ul>\n\n<li>UORA Core Specification: A technical document defining the architecture for DID-native object addressing and resolution.</li>\n<li>Universal Resource Attestation Schemas: A library of vocabularies and data models for cross-industry lifecycle attestations.</li>\n<li>Secure Physical Binding Protocol: A specification outlining methods and best practices for securely linking digital DIDs to physical objects.</li>\n<li>Implementation Guidelines and Use Cases: Documentation providing practical integration pathways, reference architectures, and business case examples to accelerate adoption.</li>\n</ul>\n\n<h4>Success Criteria</h4>\n\n<p>The Community Group will be considered successful when its core specifications are used by at least two independent, interoperable implementations to track physical assets across a multi-party supply chain.</p>\n\n<h4>Out of Scope</h4>\n\n<ul>\n<li>Development of new blockchain or distributed ledger protocols.</li>\n<li>Creation of new cryptographic primitives.</li>\n<li>Mandating specific commercial hardware, sensor, or IoT platforms.</li>\n</ul>",
0 commit comments