Which type of VC is intended to be specific to a particular domain?

Which type of VC is intended to be specific to a particular domain?

• A. Convertible VCs
• B. Non-Convertible VCs
• C. Centralized VCs
• D. Decentralized VCs

Answer: (B)

The main idea here is that domain specificity in verifiable credentials is achieved by designating credentials as non-convertible. A non-convertible credential carries a fixed set of claims and a schema tailored to a particular domain, with verification rules that are anchored in that domain’s requirements. This keeps the credential meaningful and trustworthy only within that domain, preventing easy adaptation or reinterpretation for other contexts. In contrast, convertible credentials are meant to be repurposed or reinterpreted across different domains, which can blur the meaning of the claims and undermine domain-specific trust and governance. The choices about centralized versus decentralized refer to where and how trust is managed, not whether a credential is scoped to a specific domain, so they don’t address domain specificity.

The main idea here is that domain specificity in verifiable credentials is achieved by designating credentials as non-convertible. A non-convertible credential carries a fixed set of claims and a schema tailored to a particular domain, with verification rules that are anchored in that domain’s requirements. This keeps the credential meaningful and trustworthy only within that domain, preventing easy adaptation or reinterpretation for other contexts. In contrast, convertible credentials are meant to be repurposed or reinterpreted across different domains, which can blur the meaning of the claims and undermine domain-specific trust and governance. The choices about centralized versus decentralized refer to where and how trust is managed, not whether a credential is scoped to a specific domain, so they don’t address domain specificity.