skills.rest
sourcelabbg
sourcelabbgOFFICIAL
Explore all skills by this author →
WebsiteGitHub

mdoc-standards-tech

Explain mDoc standards including ISO/IEC 18013-5, CBOR, COSE, and X.509.

Updated Mar 7, 2026
Search Tags:#standards#cbor#x509#mdoc#digital identity#cose
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill mdoc-standards-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mdoc-standards-tech
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/mdoc-standards-tech
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill mdoc-standards-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users understand the complex standards and underlying technologies that power Mobile Documents (mDocs), enabling them to build compatible and secure digital identity solutions.

Core Features & Use Cases

  • Standards Overview: Explains ISO/IEC 18013-5, 18013-7, and 23220 series.
  • Technology Deep Dive: Covers CBOR encoding, COSE signing, salted hashed claims, and X.509 certificates (IACA, DSC).
  • Use Case: A developer needs to integrate mDoc functionality into their application and requires a clear explanation of the data formats and security mechanisms involved.

Quick Start

Use the mdoc-standards-tech skill to explain the underlying standards behind mDocs.

Frequently Asked Questions about mdoc-standards-tech

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

FAQPage Schema
What are mDoc standards and how do they work for digital identity?▼

mDoc standards are specifications like ISO/IEC 18013-5 that define secure digital identity documents. They use CBOR encoding and COSE signing to structure and protect data, enabling verifiable mobile credentials.

How does CBOR encoding work in ISO/IEC 18013-5 mobile documents?▼

CBOR encoding structures the data payloads in ISO/IEC 18013-5 mobile documents. It provides a concise binary format that allows efficient serialization of identity claims for secure digital identity solutions.

How do COSE signing and X.509 certificates secure mDoc digital identity data?▼

COSE signing applies cryptographic signatures to mDoc payloads, while X.509 certificates manage trust anchors like IACA and DSC. This combination ensures that mobile documents remain tamper-proof and verifiable.

What are salted hashed claims and why are they needed in mDoc standards?▼

Salted hashed claims protect privacy in mDoc standards by applying unique salts to individual data elements before hashing. This selective disclosure mechanism prevents correlating identity data across multiple transactions.

Do I need to understand ISO/IEC 23220 to build mDoc digital identity applications?▼

Understanding ISO/IEC 23220 is necessary for building mDoc digital identity applications because it defines the overall architecture and APIs for the mobile document ecosystem, complementing the 18013-5 data format specifications.

What is the difference between ISO/IEC 18013-5 and 18013-7 for mobile documents?▼

ISO/IEC 18013-5 defines the device engagement and data structure for offline mDoc presentation, while 18013-7 specifies protocols for online digital identity verification. Both are essential for comprehensive mDoc standards compliance.

Related Skills

Explore More Software Engineering Skills→
moonshineTPmoonshineTP

PKI and X.509

Generate CSRs, sign certificates, and manage X.509 revocation.

Community
Advanced
sourcelabbgsourcelabbg

oid4vp-dcql

Parse and generate DCQL queries for verifiable presentations.

Official
Intermediate
sourcelabbgsourcelabbg

oid4vp-format-mdoc

Specify ISO mdoc integration into OpenID4VP presentations with DeviceResponse and SessionTranscript.

Official
Advanced
sourcelabbgsourcelabbg

haip-overview

Explain the EUDI HAIP scope, terminology, and requirements for OpenID4VC.

Official
Basic