Attestation / Credential
Represent issuer-asserted claims with durable identity, evidence, validity, status, securing and purpose-bound presentation while remaining independent of storage and interface format.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 24 findings · 72 questions
Attestation definition, identity and schema Defines what the issued assertion is and how its class and instance are identified.
Concept, class and instance identity
Separates the asserted meaning from the credential container and each representation.
Attestation, claim, credential, certificate, licence and permit distinction
Governed class, definition, legal or technical effect, inclusion and exclusion criteria and relation among assertion, evidence container and external grant.
- What identity, class, role, scope, version and values define attestation, claim, credential, certificate, licence and permit distinction? identity
- Which issuer authority, source, evidence, method and event or effective time support attestation, claim, credential, certificate, licence and permit distinction? evidence
- How is attestation, claim, credential, certificate, licence and permit distinction validated, disclosed, contested, corrected, superseded and retained without changing issued history? validation
Credential identifier, type, version, lineage and representation identity
Credential and attestation IDs, type hierarchy, profile version, predecessor or successor, representation ID, issuer serial and authoritative registry.
- What identity, class, role, scope, version and values define credential identifier, type, version, lineage and representation identity? definition
- Which issuer authority, source, evidence, method and event or effective time support credential identifier, type, version, lineage and representation identity? authority
- How is credential identifier, type, version, lineage and representation identity validated, disclosed, contested, corrected, superseded and retained without changing issued history? interoperability
Claim model, schema and subject binding
Defines what is asserted, about which subject, under which vocabulary and evidence.
Claim set, predicate, value, language, unit, source and confidence
Typed claim paths, predicates, values or references, language, units, source assertion, confidence, uncertainty and explicit unknowns.
- What identity, class, role, scope, version and values define claim set, predicate, value, language, unit, source and confidence? relationship
- Which issuer authority, source, evidence, method and event or effective time support claim set, predicate, value, language, unit, source and confidence? temporal
- How is claim set, predicate, value, language, unit, source and confidence validated, disclosed, contested, corrected, superseded and retained without changing issued history? access
Credential schema, vocabulary, context, profile and subject binding
Schema and vocabulary IDs and versions, semantic context, required claims, subject reference, subject role and binding method.
- What identity, class, role, scope, version and values define credential schema, vocabulary, context, profile and subject binding? requirement
- Which issuer authority, source, evidence, method and event or effective time support credential schema, vocabulary, context, profile and subject binding? decision
- How is credential schema, vocabulary, context, profile and subject binding validated, disclosed, contested, corrected, superseded and retained without changing issued history? exception
Parties, authority, issuance and custody Makes issuer authority, issuance evidence and holder custody attributable.
Issuer, subject, holder, verifier and authority
References external actors and the scoped authority for their roles.
Issuer identity, role, mandate, scope, delegation and authority validity
External issuer, issuing role, mandate or accreditation, attestation classes, jurisdiction, delegation chain and effective interval.
- What identity, class, role, scope, version and values define issuer identity, role, mandate, scope, delegation and authority validity? ownership
- Which issuer authority, source, evidence, method and event or effective time support issuer identity, role, mandate, scope, delegation and authority validity? provenance
- How is issuer identity, role, mandate, scope, delegation and authority validity validated, disclosed, contested, corrected, superseded and retained without changing issued history? privacy
Subject, holder, presenter, verifier and relying-party reference
External actor IDs, protocol roles, subject-holder relation, representative authority, role validity and privacy marking.
- What identity, class, role, scope, version and values define subject, holder, presenter, verifier and relying-party reference? classification
- Which issuer authority, source, evidence, method and event or effective time support subject, holder, presenter, verifier and relying-party reference? quality
- How is subject, holder, presenter, verifier and relying-party reference validated, disclosed, contested, corrected, superseded and retained without changing issued history? security
Application, decision, issuance, delivery and custody
Records credential-specific acts without importing generic workflow or wallet masters.
Issuance request, eligibility evidence, assessment and decision reference
External request, criteria and policy versions, evidence, assessor, outcome, reasons, appeals and decision provenance.
- What identity, class, role, scope, version and values define issuance request, eligibility evidence, assessment and decision reference? composition
- Which issuer authority, source, evidence, method and event or effective time support issuance request, eligibility evidence, assessment and decision reference? measurement
- How is issuance request, eligibility evidence, assessment and decision reference validated, disclosed, contested, corrected, superseded and retained without changing issued history? validation
Issuance event, issuer copy, holder copy, delivery, acceptance and custody
Issuance act, authoritative issuer record, holder representation, delivery channel, receipt, custody location, integrity and recovery rules.
- What identity, class, role, scope, version and values define issuance event, issuer copy, holder copy, delivery, acceptance and custody? state
- Which issuer authority, source, evidence, method and event or effective time support issuance event, issuer copy, holder copy, delivery, acceptance and custody? lifecycle
- How is issuance event, issuer copy, holder copy, delivery, acceptance and custody validated, disclosed, contested, corrected, superseded and retained without changing issued history? retention
Validity, status and lifecycle Represents time-qualified standing and non-destructive change.
Validity terms and conditions
Separates issuance time, effective validity and usage conditions.
Issued, valid-from, valid-until, effective, observed and knowledge time
Distinct RFC 3339 event times, timezone, accuracy, source clock, uncertainty, interval boundaries and later correction knowledge.
- What identity, class, role, scope, version and values define issued, valid-from, valid-until, effective, observed and knowledge time? identity
- Which issuer authority, source, evidence, method and event or effective time support issued, valid-from, valid-until, effective, observed and knowledge time? evidence
- How is issued, valid-from, valid-until, effective, observed and knowledge time validated, disclosed, contested, corrected, superseded and retained without changing issued history? validation
Terms of use, jurisdiction, purpose, condition, limitation and dependency
Credential-specific use terms, jurisdiction, audience, prerequisite or external grant, restrictions, dependency and interpretation warning.
- What identity, class, role, scope, version and values define terms of use, jurisdiction, purpose, condition, limitation and dependency? definition
- Which issuer authority, source, evidence, method and event or effective time support terms of use, jurisdiction, purpose, condition, limitation and dependency? authority
- How is terms of use, jurisdiction, purpose, condition, limitation and dependency validated, disclosed, contested, corrected, superseded and retained without changing issued history? interoperability
Status method, events and lineage
Preserves status source, freshness, reason and successor chain.
Status source, method, entry, purpose, value, freshness and error
Status service and authority, method profile, entry or index, status purpose, value, retrieved and next-update time, cache age and processing errors.
- What identity, class, role, scope, version and values define status source, method, entry, purpose, value, freshness and error? relationship
- Which issuer authority, source, evidence, method and event or effective time support status source, method, entry, purpose, value, freshness and error? temporal
- How is status source, method, entry, purpose, value, freshness and error validated, disclosed, contested, corrected, superseded and retained without changing issued history? access
Activate, suspend, reinstate, revoke, expire, renew, correct and supersede event
Typed lifecycle event, prior and next state, authority, reason, effective time, evidence, reversibility, successor and notification.
- What identity, class, role, scope, version and values define activate, suspend, reinstate, revoke, expire, renew, correct and supersede event? requirement
- Which issuer authority, source, evidence, method and event or effective time support activate, suspend, reinstate, revoke, expire, renew, correct and supersede event? decision
- How is activate, suspend, reinstate, revoke, expire, renew, correct and supersede event validated, disclosed, contested, corrected, superseded and retained without changing issued history? exception
Securing, integrity and verification Binds a credential representation to named securing and validation methods.
Proof envelope and verification material
Identifies the exact representation, securing mechanism and public material.
Secured representation, canonical form, digest, media type and envelope
Credential bytes or external artifact, semantic representation, canonicalization, digest, media type, encoding, envelope and detached-content binding.
- What identity, class, role, scope, version and values define secured representation, canonical form, digest, media type and envelope? ownership
- Which issuer authority, source, evidence, method and event or effective time support secured representation, canonical form, digest, media type and envelope? provenance
- How is secured representation, canonical form, digest, media type and envelope validated, disclosed, contested, corrected, superseded and retained without changing issued history? privacy
Proof or signature suite, purpose, method, controller, key and parameters
Proof type, cryptosuite or signature algorithm, proof purpose, verification method and controller, public key ref, parameters, created time and proof value.
- What identity, class, role, scope, version and values define proof or signature suite, purpose, method, controller, key and parameters? classification
- Which issuer authority, source, evidence, method and event or effective time support proof or signature suite, purpose, method, controller, key and parameters? quality
- How is proof or signature suite, purpose, method, controller, key and parameters validated, disclosed, contested, corrected, superseded and retained without changing issued history? security
Validation, trust and result
Records exact checks and keeps technical verification separate from external acceptance.
Schema, proof, path, key, status, time and policy validation checks
Validator and version, input digest, schema and semantic checks, signature or proof checks, path or key resolution, status, time and policy inputs.
- What identity, class, role, scope, version and values define schema, proof, path, key, status, time and policy validation checks? composition
- Which issuer authority, source, evidence, method and event or effective time support schema, proof, path, key, status, time and policy validation checks? measurement
- How is schema, proof, path, key, status, time and policy validation checks validated, disclosed, contested, corrected, superseded and retained without changing issued history? validation
Verification outcome, errors, evidence, assurance, trust and decision separation
Valid, invalid or indeterminate outcome, structured errors, evidence, assurance, issuer-trust result, observation time and explicit non-authorization marker.
- What identity, class, role, scope, version and values define verification outcome, errors, evidence, assurance, trust and decision separation? state
- Which issuer authority, source, evidence, method and event or effective time support verification outcome, errors, evidence, assurance, trust and decision separation? lifecycle
- How is verification outcome, errors, evidence, assurance, trust and decision separation validated, disclosed, contested, corrected, superseded and retained without changing issued history? retention
Presentation, disclosure, privacy and correlation Governs use of credentials without assuming every verifier receives the full issuer record.
Request, purpose and disclosure policy
Captures what a verifier asks for and why before disclosure.
Presentation request, verifier, purpose, audience, claims, format, nonce and expiry
Request ID, verifier and client, purpose, audience, requested claims and predicates, accepted formats, nonce, domain, issue and expiry time.
- What identity, class, role, scope, version and values define presentation request, verifier, purpose, audience, claims, format, nonce and expiry? identity
- Which issuer authority, source, evidence, method and event or effective time support presentation request, verifier, purpose, audience, claims, format, nonce and expiry? evidence
- How is presentation request, verifier, purpose, audience, claims, format, nonce and expiry validated, disclosed, contested, corrected, superseded and retained without changing issued history? validation
Disclosure authority, minimization, derived claim and inference risk
Consent or other authority, requested, disclosed, derived and withheld claims, necessity, policy, inference, linkability and residual privacy risk.
- What identity, class, role, scope, version and values define disclosure authority, minimization, derived claim and inference risk? definition
- Which issuer authority, source, evidence, method and event or effective time support disclosure authority, minimization, derived claim and inference risk? authority
- How is disclosure authority, minimization, derived claim and inference risk validated, disclosed, contested, corrected, superseded and retained without changing issued history? interoperability
Presentation, holder binding and receipt
Binds disclosed material to request context and records its attributable verification.
Presentation identifier, holder binding, credential set, disclosures and integrity
Presentation ID, presenter or holder, holder-binding proof, included credentials, disclosure manifest, format, request binding, digest and created time.
- What identity, class, role, scope, version and values define presentation identifier, holder binding, credential set, disclosures and integrity? relationship
- Which issuer authority, source, evidence, method and event or effective time support presentation identifier, holder binding, credential set, disclosures and integrity? temporal
- How is presentation identifier, holder binding, credential set, disclosures and integrity validated, disclosed, contested, corrected, superseded and retained without changing issued history? access
Presentation receipt, verification, use event, retention and correlation control
Receiver, receipt and verification times, purpose, outcome, onward use, retention, replay control, pairwise handles and correlation assessment.
- What identity, class, role, scope, version and values define presentation receipt, verification, use event, retention and correlation control? requirement
- Which issuer authority, source, evidence, method and event or effective time support presentation receipt, verification, use event, retention and correlation control? decision
- How is presentation receipt, verification, use event, retention and correlation control validated, disclosed, contested, corrected, superseded and retained without changing issued history? exception
Interoperability, access, provenance and agent governance Provides loss-aware mappings and safe autonomous lifecycle operations.
Format, profile and legal-effect crosswalk
Maps W3C, X.509, SD-JWT and presentation profiles with explicit loss.
VC, Data Integrity, X.509, SD-JWT and OpenID4VP crosswalk
Source and target versions, identity, issuer, subject, claim, validity, proof, status and presentation mappings, omissions, conflicts and round-trip class.
- What identity, class, role, scope, version and values define vc, data integrity, x.509, sd-jwt and openid4vp crosswalk? ownership
- Which issuer authority, source, evidence, method and event or effective time support vc, data integrity, x.509, sd-jwt and openid4vp crosswalk? provenance
- How is vc, data integrity, x.509, sd-jwt and openid4vp crosswalk validated, disclosed, contested, corrected, superseded and retained without changing issued history? privacy
Jurisdiction, sector, accreditation, legal effect and recognition profile
Credential class, jurisdiction, sector, issuer qualification, legal or business effect, recognition authority, limitations and review date.
- What identity, class, role, scope, version and values define jurisdiction, sector, accreditation, legal effect and recognition profile? classification
- Which issuer authority, source, evidence, method and event or effective time support jurisdiction, sector, accreditation, legal effect and recognition profile? quality
- How is jurisdiction, sector, accreditation, legal effect and recognition profile validated, disclosed, contested, corrected, superseded and retained without changing issued history? security
Access, retention, provenance and safe operations
Protects claims and usage history while preserving issuer accountability.
Issuer, holder, subject, verifier, status-public, auditor and regulator view
Audience, purpose, authority, included fields, redactions, pseudonymization, freshness, expiry, disclosure record and re-identification risk.
- What identity, class, role, scope, version and values define issuer, holder, subject, verifier, status-public, auditor and regulator view? composition
- Which issuer authority, source, evidence, method and event or effective time support issuer, holder, subject, verifier, status-public, auditor and regulator view? measurement
- How is issuer, holder, subject, verifier, status-public, auditor and regulator view validated, disclosed, contested, corrected, superseded and retained without changing issued history? validation
Provenance, retention, legal hold, disposition, agent authority and audit
Generation and revision provenance, retention trigger, hold, disposition authority, expected head, idempotency, pre-write and post-write checks, rollback and audit evidence.
- What identity, class, role, scope, version and values define provenance, retention, legal hold, disposition, agent authority and audit? state
- Which issuer authority, source, evidence, method and event or effective time support provenance, retention, legal hold, disposition, agent authority and audit? lifecycle
- How is provenance, retention, legal hold, disposition, agent authority and audit validated, disclosed, contested, corrected, superseded and retained without changing issued history? retention
Classifiers Filled
- Family
- World Models
- Category
- Cross-cutting context
- Entry kind
- aggregate
- Navigation path
- NAV.XCT.CRED
- Domain
- XCT.CRED
- Industry
- Cross-industry
- Tags
- attestationcredentialxct.cred
- Also called
- R5
What it is Filled
Owns credential class and issued-instance identity, claim and schema references, issuer, subject and holder role bindings, issuance evidence, validity, status and lifecycle, secured representations, credential-specific verification evidence, presentations, disclosure manifests, interoperability mappings and governed retention. Party identity, issuer mandate, subject profile, source evidence, keys, permission-bearing grants, trust policy, authorization decisions and generic audit logs remain external.
In scope
- Credential and attestation definitions, instance and representation identity, typed claims, schema, vocabulary, issuer authority reference, subject binding and issuance evidence
- Validity and terms, status method and freshness, suspension, revocation, expiry, renewal, correction, supersession, secured representations and verification results
- Presentation requests, disclosures, holder binding, privacy and correlation, format mappings, role views, access, retention, provenance and safe agent operations
Out of scope
- Person, organization, issuer, subject, holder, verifier, mandate, source evidence, key, trust policy, permit grant, authorization decision or audit-log master lifecycle
- Implementing proof, signature, wallet, PKI path, status-list or presentation-protocol algorithms and storing private keys or undisclosed secrets
- Universal claim truth, issuer trust, identity proofing, authentication, authorization, eligibility, legal effect or certified cross-format equivalence
Why it exists Filled
Represent issuer-asserted claims with durable identity, evidence, validity, status, securing and purpose-bound presentation while remaining independent of storage and interface format.
Distinguishing features Filled
- Models issued claims with issuer, subject and holder roles, not the authorization they may evidence.
- Distinguishes holder from subject and issuer, so custody gives no rights over content.
- Keeps issued claims immutable and records changes as events and status updates.
- Separates authenticity, current status, issuer authority and claim truth.
What robots and AI may and may not do Filled
Must not
- Issue a credential without the issuer's authority.
- Edit claims in an issued credential instead of issuing a new one.
- Present more claims than a verifier requested and the holder allowed.
- Treat a valid credential as proof that the claim is true or that the holder is the subject.
- Use a licence credential in place of the underlying permit grant.
Only with a human decision
- Revoking or suspending a credential.
- Defining a new credential class or trust framework.
- Holder consent to a presentation request.
May
- Verify a credential signature and status against the issuer's published material.
- Derive a presentation with only the requested claims.
- Refresh status lists when an issuer publishes updates.
- Map a credential between formats and note fields lost.
Moral aspects Filled
- Credentials gate access to work, travel and services, so wrongful revocation can cause real harm.
- Selective disclosure protects privacy; verifiers should not demand full credentials.
- Status checks can reveal where and when a holder uses a credential.
Who is affected
- Holders and subjects
- Credential issuers
- Verifiers and relying parties
Owners Filled
Steward
Dimension identity, owner, credential governance authority, issuer registry and privacy and records stewards
Roles
- Credential class and schema steward
- Own definitions, claim vocabulary, profiles and migration rules.
- Issuer and issuing authority
- Own issued assertions, evidence-based decisions, status and correction history.
- Subject
- Is the referent of claims and exercises applicable rights without automatically controlling the credential.
- Holder or presenter
- Custody representations and authorize purpose-bound presentations under policy.
- Verifier and relying party
- Request minimum evidence, verify pinned profiles and own external acceptance decisions.
- Status and trust steward
- Maintain status methods, issuer qualification, trust inputs and freshness requirements.
- Privacy and records steward
- Control disclosure, correlation, retention, legal hold, disposition and auditability.
Links to other meta-models Filled
references
- Identity Register, Person, Organization and Agent models - Resolve issuer, subject, holder, presenter and verifier without copying identity profiles.
- Mandate, Evidence, Key, Grant, Policy, Decision and Audit models - Resolve authority, source support, verification material and external legal or business effects.
aligned
- W3C Verifiable Credentials, Data Integrity, Status List and Controlled Identifiers - Project claims, roles, validity, status, proof and identifier-control semantics.
- IETF X.509, OCSP and SD-JWT - Project certificate, status-response and selective-disclosure representations with declared loss.
- OpenID4VP, PROV-O and RFC 3339 - Represent request-bound presentations, accountable activities and explicit event times.
neighbor
- Claim / Evidence - The credential owns the issuer's claim expression and references evidence; source observations and evidence artifacts keep their own identity and provenance.
- Identity / Key / Authentication - Issuer, subject, holder and verifier identities and public key references remain external; credential verification is not authentication by itself.
- Permit / Authorization / Decision - A licence or permit credential may evidence an external grant, but its authenticity and status do not themselves make an authorization decision.
- Digital Signature / Proof - Generic proof artifacts and verification methods remain external or reusable mixins; this model binds them to credential claim, validity, status and presentation context.
- Presentation / Wallet / Audit Log - This model records credential-specific presentations and verification evidence, while wallet inventory and generic append-only audit execution remain external.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Authoritative master-system credential or attestation identifier qualified by issuer and class.
- Governed globally resolvable credential IRI or certificate issuer and serial tuple.
- Dimension UUID when no authoritative or governed global identifier exists.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Filled
- A credential has an issuer, a subject, claims, an issuance date, a validity period and a proof.
- It is confused with the underlying permit or right, an identity record or an access token.
Capabilities and actions required Filled
- Define credential class and profile: Establish claim vocabulary, schema, required evidence, issuer authority, validity, status and representation rules.
- Issue attestation or credential: Create an immutable issued assertion and representations after an authorized evidence-backed decision.
- Deliver, accept and custody holder copy: Transfer a representation to a holder or wallet and record receipt without transferring issuer authority.
- Publish or refresh status: Issue a privacy-aware, time-qualified credential status assertion or list update.
- Suspend, reinstate, revoke, expire, renew or supersede: Append a credential lifecycle event and derived state while preserving earlier claims and representations.
- Create presentation request: Record verifier, purpose, audience, requested claims or predicates, formats, nonce and expiry.
- Derive and present credential: Create a request-bound presentation with permitted disclosure and optional holder binding.
- Verify credential or presentation: Record schema, proof, key, path, status, time and request-binding checks and structured outcome.
- Project or transform loss-aware: Map a credential to another representation or sector profile with explicit omissions and semantic conflicts.
- Correct, retain, dispose and audit: Create a successor correction or execute authorized retention and disposition while preserving required lineage.
Hazards and failure modes required Filled
- Forged or replayed credentials accepted as valid.
- Stale status letting revoked credentials pass.
- Holder tracking through correlatable identifiers.
Standards and interfaces required Filled
- W3C Verifiable Credentials Data Model 2.0.
- W3C Bitstring Status List.
- IETF SD-JWT.
- ISO/IEC 18013-5 mobile driving licence.
- OpenID for Verifiable Credential Issuance and Presentations.
Context of use required Filled
- Legal effect, issuer qualification, subject rights, retention, revocation reasons and recognition depend on jurisdiction and sector.
- W3C and OpenID specifications define technical data and protocol models but do not establish universal issuer trust or authorization.
- NIST guidance focuses on digital identity services and does not define every civil, professional, product or organizational credential.
Sources Filled
- Verifiable Credentials Data Model v2.0 - World Wide Web Consortium
- Verifiable Credential Data Integrity 1.0 - World Wide Web Consortium
- Bitstring Status List v1.0 - World Wide Web Consortium
- Controlled Identifiers v1.0 - World Wide Web Consortium
- Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List Profile - Internet Engineering Task Force
- X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP - Internet Engineering Task Force
- Selective Disclosure for JSON Web Tokens - Internet Engineering Task Force
- OpenID for Verifiable Presentations 1.0 - OpenID Foundation
- Digital Identity Guidelines - National Institute of Standards and Technology
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Date and Time on the Internet: Timestamps - Internet Engineering Task Force
Open questions
- Resolve whether ISO/IEC 18013-5 mdoc and the eIDAS 2.0 / EUDI Wallet architecture belong in the crosswalk finding or in an explicit out-of-scope statement, given that OpenID4VP is widely deployed with mdoc and the model already claims loss-aware projections.
- Add or explicitly exclude the W3C Securing Verifiable Credentials using JOSE and COSE specification; the secured-representation finding talks about envelopes and detached content while citing only the Data Integrity path.
- Confirm the SD-JWT publication identity and number, and determine whether SD-JWT VC is a distinct source needed for credential-type binding beyond the base selective-disclosure mechanism.
- Establish a legal and conformity-assessment source set for issuer accreditation, legal effect and mutual recognition so the recognition-profile finding is not carried on identity and PKI sources alone.
- Settle the precedence rule between immutable issuer lineage and subject erasure or disposition rights, including a tombstone specification, before retention guidance is published as normative.
- Design the subject-initiated contest and dispute intake path that the question set assumes but the ten functions do not expose, and decide whether it is an owned function or an external decision model reference.
- Compare status-list herd privacy against OCSP request privacy and offline verification to produce a defensible freshness and correlation policy rather than the current statement of competing requirements.
- Test the holder-copy custody boundary against the declared external wallet inventory, since the model owns delivery, custody, presentation history and disposition of holder representations while disclaiming wallet inventory.
- No independent Claude or Grok result was available; later credential, PKI, privacy and legal review is required before canonical promotion.
- No approved relation rows were supplied; proposed links to identity, mandate, evidence, key, grant, policy, decision and audit models remain holds.
- National identity documents, mobile driving licences, professional licences, academic credentials, health certificates and regulated trust services require separate profiles.
- X.509 and OCSP have later updates and deployment profiles; certified processing and algorithm suites require profile-specific review.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-xct-017-attestation-credential/spec.yaml, ver-cy/world-models/card-supplements/wm-xct-017-attestation-credential.json