mdoc-structure-function

Explain mDoc structure and functions per ISO 18013-5.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill mdoc-structure-function
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mdoc-structure-function
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/mdoc-structure-function
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill mdoc-structure-function

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users understand the intricate structure of mDocs (ISO 18013-5 data structures) and how these structures enable specific functionalities like selective disclosure and device authentication.

Core Features & Use Cases

  • mDoc Structure Breakdown: Explains the components of an mDoc, including MSO, namespaces, and elements.
  • Functional Explanation: Details how salted hashes enable selective disclosure and protect against unwanted disclosures.
  • Device Authentication: Clarifies the methods for device authentication (signature vs. ECDH MAC) and their implications for anti-cloning and replay protection.
  • Offline Verification: Highlights how the mDoc structure facilitates offline verification.
  • Use Case: A developer needs to integrate mDoc support into their application and requires a clear understanding of how to construct and verify mDoc presentations, including the security mechanisms involved.

Quick Start

Explain how salted hashed claims enable selective disclosure in mDocs.

Frequently Asked Questions about mdoc-structure-function

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do salted hashes enable selective disclosure in mDoc verifiable credentials?

mDoc structure facilitates offline verification by embedding the issuer's signature and revocation data directly into the document. This allows verifiers to cryptographically validate the issuer's authenticity and the data integrity without requiring a live network connection to the issuing authority.

What is the difference between device signature and ECDH MAC for mDoc device authentication?

Device authentication in mDocs uses either a device signature or ECDH MAC to prove the holder's possession of the credential. The signature method provides non-repudiation, while the ECDH MAC method establishes a secure channel that specifically prevents replay and anti-cloning attacks during presentation.

How is an MSO structured within an ISO 18013-5 mDoc payload?

An MSO structure within an ISO 18013-5 mDoc payload contains the issuer's digital signature, namespace mappings, and element digests. It organizes the credential's claims and cryptographic proofs, forming the foundational structure required for constructing valid mDoc presentations.

Can I decode and verify a signed mDoc payload using ISO 18013-5 specifications?

You can decode and verify a signed mDoc payload using ISO 18013-5 specifications by parsing the MSO structure and validating the issuer's signature. This process confirms the integrity of namespaces and element digests, ensuring the digital identity data has not been tampered with.

How do I construct an mDoc presentation for digital identity verification?

To construct an mDoc presentation for digital identity verification, you assemble the required namespaces and element digests from the MSO, apply selective disclosure via salted hashes, and generate the device authentication signature or MAC to protect against replay.