fix: include mdoc in documentation

Signed-off-by: Mirko Mollik <mirko.mollik@eudi.sprind.org>

Author: cre8

README.md

@@ -37,7 +37,7 @@ management, scalable database support, and clean API boundaries.
 
 ## 🧩 Features
 
-- ✅ Supports **OID4VCI**, **OID4VP**, **SD-JWT VC**, and **OAuth Token Status
+- ✅ Supports **OID4VCI**, **OID4VP**, **SD-JWT VC**, **mDOC (ISO 18013-5)**, and **OAuth Token Status
   List**
 - ✅ **OIDF conformance tested** for OID4VCI and OID4VP protocols
 - ✅ JSON-based credential configuration

docs/architecture/supported-protocols.md

@@ -16,6 +16,7 @@ technical framework.
 | [OpenID for Verifiable Credential Issuance (OID4VCI)](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html) | Enables issuers to deliver verifiable credentials to EUDI Wallets using OAuth-based flows. |
 | [OpenID for Verifiable Presentations (OID4VP)](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html)              | Allows services to request and verify credentials presented by EUDI Wallet holders.        |
 | [Selective Disclosure JWT VC (SD-JWT VC)](https://www.ietf.org/archive/id/draft-ietf-oauth-selective-disclosure-jwt-08.html)     | Data model for credentials allowing selective disclosure of individual claims by the user. |
+| [Mobile Driving License (mDOC/mDL)](https://www.iso.org/standard/69084.html)                                                     | ISO 18013-5 standard for mobile driving licenses and other mobile documents.               |
 | [OAuth Token Status List](https://drafts.oauth.net/draft-ietf-oauth-status-list/draft-ietf-oauth-status-list.html)               | Mechanism for determining revocation or suspension status of issued credentials.           |
 
 These standards are evolving in coordination with EU-level pilot projects and

docs/getting-started/issuance/credential-configuration.md

@@ -24,10 +24,13 @@ For a complete configuration example, see the [Complete Configuration Example](#
 - `id`: **REQUIRED** - Unique identifier for the credential configuration that will be used to reference this credential in the issuance metadata or in the credential offer.
 - `config`: **REQUIRED** - Entry for
   [credential_configuration_supported](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-credential-issuer-metadata:~:text=the%20logo%20image.-,credential_configurations_supported,-%3A%20REQUIRED.%20Object%20that).
-    - `format`: **REQUIRED** - The format of the credential, only `dc+sd-jwt` is
-      currently supported.
+    - `format`: **REQUIRED** - The format of the credential. Supported formats:
+        - `dc+sd-jwt` - Selective Disclosure JWT Verifiable Credentials
+        - `mso_mdoc` - Mobile Document (ISO 18013-5)
     - `display`: **REQUIRED** - Display configuration for the credential,
       including name, description, locale, colors, and images.
+    - `docType`: **REQUIRED for mso_mdoc** - Document type identifier (e.g., `org.iso.18013.5.1.mDL`).
+    - `namespace`: **OPTIONAL for mso_mdoc** - Default namespace for claims (e.g., `org.iso.18013.5.1`). If not provided, derived from docType.
 
 ### Optional Fields
 
@@ -200,6 +203,78 @@ This configuration allows:
 
 ---
 
+## mDOC Credential Format
+
+For issuing mobile documents following the ISO 18013-5 standard (such as Mobile Driving Licenses), use the `mso_mdoc` format.
+
+### Basic mDOC Configuration
+
+```json
+{
+    "id": "pid-mdoc",
+    "description": "Personal ID as mDL",
+    "config": {
+        "format": "mso_mdoc",
+        "docType": "org.iso.18013.5.1.mDL",
+        "namespace": "org.iso.18013.5.1",
+        "scope": "mdl",
+        "display": [
+            {
+                "name": "Mobile Driving License",
+                "description": "mDL Credential",
+                "locale": "en-US"
+            }
+        ]
+    },
+    "claims": {
+        "given_name": "ERIKA",
+        "family_name": "MUSTERMANN",
+        "birth_date": "1964-08-12",
+        "issuing_country": "DE"
+    },
+    "keyBinding": true
+}
+```
+
+### mDOC-Specific Fields
+
+| Field               | Required | Description                                                                                                           |
+| ------------------- | -------- | --------------------------------------------------------------------------------------------------------------------- |
+| `docType`           | Yes      | Document type identifier following ISO 18013-5 naming convention (e.g., `org.iso.18013.5.1.mDL`)                      |
+| `namespace`         | No       | Default namespace for claims. If not provided, derived from `docType`. For mDL, this is typically `org.iso.18013.5.1` |
+| `claimsByNamespace` | No       | Alternative to `claims` - allows specifying claims across multiple namespaces                                         |
+
+### Multiple Namespaces
+
+For credentials that require claims from multiple namespaces, use `claimsByNamespace`:
+
+```json
+{
+    "config": {
+        "format": "mso_mdoc",
+        "docType": "org.iso.18013.5.1.mDL",
+        "display": [{ "name": "mDL", "locale": "en-US" }]
+    },
+    "claimsByNamespace": {
+        "org.iso.18013.5.1": {
+            "given_name": "ERIKA",
+            "family_name": "MUSTERMANN"
+        },
+        "org.iso.18013.5.1.aamva": {
+            "DHS_compliance": "F"
+        }
+    }
+}
+```
+
+!!! note "Key Binding Required"
+For mDOC credentials, `keyBinding` should typically be set to `true` as the ISO 18013-5 standard requires device authentication.
+
+!!! info "Selective Disclosure"
+Unlike SD-JWT, mDOC credentials have built-in selective disclosure at the namespace and claim level. The `disclosureFrame` field is not used for mDOC format.
+
+---
+
 ## Display Configuration
 
 The display configuration defines how the credential appears in wallets as defined in the [OID4VCI spec](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-credential-issuer-metadata-p) for the credential metadata:

docs/index.md

@@ -24,7 +24,7 @@ yourself.
 
 Connecting to the EUDI Wallet ecosystem is technically demanding:
 
-- You must understand **OID4VCI**, **OID4VP**, **SD-JWT VC**, and **OAuth-based
+- You must understand **OID4VCI**, **OID4VP**, **SD-JWT VC**, **mDOC (ISO 18013-5)**, and **OAuth-based
   status protocols**.
 - Libraries are scattered, often **incomplete or language-specific**.
 - Hosted services can lead to **vendor lock-in** or obscure how your data is