What problem does it solve? Building a Person Identification Data (PID) credential definition for the EUDI Wallet requires exact claim path pointers per format, and hand-writing them risks mismatches with the verifiable data registry and wallet rejections. ## Core Features & Use Cases - Registry-Verified Schemas: Ships the exact claim path pointer documents for the PID credential type urn:eu.europa.ec.eudi:pid:1 in dc+sd-jwt, jwt_vc_json, and mso_mdoc formats. - Claim Semantics Guide: Explains mandatory claims such as name, birthdate, age-over flags, contact data, and address, including the naming differences between JSON formats and mdoc. - iGrant.io API Integration: Shows how to embed the claims array into a credential definition via POST /v2/config/digital-wallet/openid/sdjwt/credential-definition, with label, version, and trust list rules. - Use Case: An integrator building an OpenID4VCI issuer copies the dc+sd-jwt claims document into a credential definition so wallets can selectively disclose PID attributes like is_over_18. ## Quick Start Ask your agent to create a PID credential definition on the iGrant.io demo environment using the dc+sd-jwt format from this schema.