arf-annex3-pid-rulebook

Define PID attributes and encoding specifications for EUDI Wallet ecosystems.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on the attributes and encoding methods for Person Identification Data (PID) within the EUDI Wallet ecosystem, ensuring compliance and interoperability.

Core Features & Use Cases

  • PID Attribute Definitions: Details mandatory and optional PID attributes as defined by the PID Rulebook and CIR 2024/2977.
  • Encoding Standards: Explains how PIDs are encoded using ISO/IEC 18013-5 (mdoc) and SD-JWT VC formats.
  • Use Case: A developer building an EUDI Wallet application needs to understand the exact structure and claims required for a PID to ensure correct issuance and presentation.

Quick Start

Explain the mandatory attributes for a PID according to the PID Rulebook.

Frequently Asked Questions about arf-annex3-pid-rulebook

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

FAQPage Schema
What mandatory attributes are required for a PID in the EUDI Wallet ecosystem?

Mandatory PID attributes in the EUDI Wallet ecosystem are defined by the PID Rulebook and CIR 2024/2977, specifying essential identity claims required for compliant issuance and presentation across both mdoc and SD-JWT VC formats.

How does SD-JWT VC encoding work for Person Identification Data?

SD-JWT VC encoding for Person Identification Data structures identity claims using selective disclosure mechanisms, allowing compliant PID presentation within the EUDI Wallet ecosystem while maintaining attribute privacy and interoperability.

How do I encode PID attributes using ISO/IEC 18013-5 mdoc format?

Encoding PID attributes using ISO/IEC 18013-5 mdoc format involves structuring identity claims according to the standard's mobile document specifications, ensuring interoperability and compliance with ARF Annex 3 requirements.

Does the EUDI PID Rulebook support both mdoc and SD-JWT VC formats?

Yes, the EUDI PID Rulebook supports both ISO/IEC 18013-5 mdoc and SD-JWT VC formats, detailing encoding specifications, mandatory and optional attributes, and compliance requirements for each format.

What is the difference between mandatory and optional PID attributes in CIR 2024/2977?

Mandatory PID attributes in CIR 2024/2977 must be present for compliant identity verification, while optional attributes provide supplementary identity information depending on specific EUDI Wallet use cases and presentation requirements.

Why do I need specific encoding standards for EUDI Wallet PID attributes?

Specific encoding standards for EUDI Wallet PID attributes ensure interoperability between issuers and verifiers across the ecosystem, guaranteeing that identity claims are correctly formatted for both mdoc and SD-JWT VC presentation formats.