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

hlr-25-unified-definition-and-controlled-vocabu

Define EUDI attribute schemas with controlled vocabularies per ARF Annex 2 Topic 25.

Updated Mar 7, 2026
Search Tags:#eud#arf#high-level requirements#attribute definition#controlled vocabulary
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-25-unified-definition-and-controlled-vocabu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hlr-25-unified-definition-and-controlled-vocabu
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-25-unified-definition-and-controlled-vocabu
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-25-unified-definition-and-controlled-vocabu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for consistent and controlled vocabularies for attributes within the EUDI ecosystem, ensuring clarity and interoperability.

Core Features & Use Cases

  • Attribute Definition: Provides requirements for unified attribute definitions.
  • Controlled Vocabularies: Ensures controlled vocabularies are used for attributes.
  • Use Case: When developing EUDI Wallet specifications, use this skill to ensure all attribute definitions are standardized and adhere to controlled vocabulary principles.

Quick Start

Use the hlr-25-unified-definition-and-controlled-vocabu skill to understand requirements for attribute definitions.

Frequently Asked Questions about hlr-25-unified-definition-and-controlled-vocabu

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

FAQPage Schema
What are the EUDI high-level requirements for unified attribute definitions?▼

EUDI high-level requirements for unified attribute definitions mandate consistent terminology and controlled vocabularies to ensure clarity and interoperability within the EUDI Wallet ecosystem. They specify normative SHALL, SHOULD, and MAY requirements for attribute schemas.

How do I standardize attribute schemas in the EUDI Wallet framework?▼

To standardize attribute schemas in the EUDI Wallet framework, apply the high-level requirements for unified attribute definitions and controlled vocabularies. This ensures all attributes adhere to controlled vocabulary principles during EUDI Wallet specification development.

When do I need controlled vocabularies for EUDI attribute definitions?▼

Controlled vocabularies for EUDI attribute definitions are needed when developing EUDI Wallet specifications to maintain ecosystem interoperability. They ensure consistent attribute definition terminology across the EUDI framework.

Does this address ARF Annex 2 Topic 25 requirements for attribute schemas?▼

Yes, this satisfies the normative SHALL, SHOULD, and MAY requirements from ARF Annex 2, specifically Topic 25. It provides the necessary high-level requirements for unified attribute definitions and controlled vocabularies within the EUDI framework.

Why use controlled vocabularies for EUDI Wallet attribute definitions?▼

Controlled vocabularies for EUDI Wallet attribute definitions solve the need for consistency across the EUDI ecosystem. Using them ensures clarity and interoperability by standardizing attribute terminology during wallet specification development.

Related Skills

Explore More Legal & Compliance Skills→
sourcelabbgsourcelabbg

hlr-54-accessibility

Provide normative accessibility requirements for EUDI Wallet Units.

Official
Basic
sourcelabbgsourcelabbg

arf-annex3-mdl-rulebook

Define mDL attribute schemas and ISO/IEC 18013-5 encoding for EUDI Wallet.

Official
Basic
sourcelabbgsourcelabbg

arf-topic-o-catalogues-for-attestations

Implement EUDI Wallet attestation catalogues with attribute and scheme registration.

Official
Intermediate
OrcaQubitsOrcaQubits
35

magento-eav-attributes

Create and manage Magento 2 EAV attributes, sets, and groups via PHP.

Official
Intermediate