6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)vsW3C Verifiable Credentials (VC) Data Model 2.0
See exactly how 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls map to W3C Verifiable Credentials (VC) Data Model 2.0. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) maps to W3C Verifiable Credentials (VC) Data Model 2.0 with 15% coverage across 7 directly mapped controls. Analysis of 41 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls identifies 36 compliance gaps — primarily concentrated in General Provisions.
Source: TheArtOfService Knowledge Graph | 41 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 13 of 13 mapped controls across 4 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
General Provisions(6 mappings)
Criminal Offences(2 mappings)
Liability of Legal Persons(2 mappings)
Implementation(3 mappings)
Related Comparisons
Other 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) comparisons
Other W3C Verifiable Credentials (VC) Data Model 2.0 comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) and W3C Verifiable Credentials (VC) Data Model 2.0?
6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) has 41 controls across its framework, while W3C Verifiable Credentials (VC) Data Model 2.0 covers 18 controls. Direct mapping analysis identifies 7 overlapping controls (15% coverage). The frameworks diverge most significantly in General Provisions, where 15 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls have no direct W3C Verifiable Credentials (VC) Data Model 2.0 equivalent.
How many controls map between 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) and W3C Verifiable Credentials (VC) Data Model 2.0?
Of 41 total 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls, 7 map directly to W3C Verifiable Credentials (VC) Data Model 2.0 controls — representing 15% coverage. The remaining 36 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) to W3C Verifiable Credentials (VC) Data Model 2.0?
36 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls have no direct equivalent in W3C Verifiable Credentials (VC) Data Model 2.0. The highest concentration of gaps is in General Provisions with 15 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) and W3C Verifiable Credentials (VC) Data Model 2.0?
The domain with the highest gap count is General Provisions (15 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.