Schema Object


Schemas are used to list a set of attributes. Issuers of Verifiable Credentials may reference schemas within Credentials they issue in order to provide a layer of semantic interoperability with other issuers utilising the same schema.
In the AnonCreds Specification, schemas are written directly to a Verifiable Data Registry, rather than using a centralized service such as Schemas are also associated with Credential Definitions, which are used to link the schema, issuer and holder together (detailed further here).
This documentation will guide an implementor of AnonCreds on cheqd on how the cheqd AnonCreds Object Method defines and structures Schema IDs and associated content.

AnonCreds Schema ID

Each specific AnonCreds identifier must be defined within an AnonCreds Object Method in the AnonCreds Object Method Registry.
This means that an AnonCreds Schema Object ID does not need to be formatted in any particular syntax, in the latest version of the AnonCreds Specification.

Legacy AnonCreds Schema ID

Prior to the AnonCreds specification being updated, the schema_id was defined as a composite of the following set of elements:
  • publisher DID: is a string. The DID of the Schema Publisher.
  • object type: An integer denoting the type of object. 2 is used for Schemas.
  • name: is a string, the name of the schema
  • version: is a string, the version of the schema in semver format. The three part, period (“.”) separated format MAY be enforced.
The schema_id therefore was formatted in the following way:
For example a Legacy AnonCreds schema_id could be:
Through combining each of the components into one string, it provides client applications all of the information they need to know about the schema in a simple and easily consumable format.
This is important to mention, since many client applications may still expect Schema IDs or Schema Content to contain the information or syntax within this Legacy schema_id.
This legacy format is now attributed to the Hyperledger Indy Legacy AnonCreds Objects Method

AnonCreds Schema Object Content

The actual Schema Object Content which is written to the Verifiable Data Registry, contains the following information:
  • attr_names: is the array of attribute names (claim names) that will constitute the AnonCred credential of this type.
  • name: is a string, the name of the schema, which will be a part of the published schema_id.
  • version: is a string, the version of the schema in semver format. The three part, period (“.”) separated format MAY be enforced. The version will be part of the published schema_id.
For example:
"data": {
"attr_names": [
"name": "degreeSchema",
"version": "1.5.7"
Returning to the Legacy AnonCreds schema_id as a reference point, within the Schema Object Content, the name and the version should be the same as the name and version in the composite schema_id.
Therefore, the schema_id "7BPMqYgYLQni258J8JPS8K:2:degreeSchema:1.5.7" would identify and resolve to the Schema Object content above.
Once published on a Hyperledger Indy ledger, an additional identifier for the published schema, the TXN_ID, is available to those reading from the ledger

cheqd AnonCreds Object method for Schemas

cheqd Schema ID

cheqd on-ledger resources identify individual resources using DID URLs.
cheqd resources module uses the following format:
Rather than using a composite string for the Schema Resource ID. The cheqd AnonCreds object method uses a UUID to identify the Schema Object Content which includes additional Schema Object Content Metadata, providing the required fields for equivalence with Hyperledger Indy implementations.
For example, the following DID URL is cheqd's representation of a schema_id:

cheqd Schema Object Content

Before creating any on-ledger transaction, it is important to assemble to required Schema Object Content and save it as a file locally.
In the example below, the content should be saved as a file, for example: degreeSchema.json with the following content:
"AnonCredsObject": {
"data": {
"attr_names": [
"name": "degreeSchema",
"version": "1.5.7"
"AnonCredsObjectMetadata": {
"objectFamily": "anoncreds",
"objectFamilyVersion": "v1",
"objectType": "2",
"typeName": "SCHEMA",
"publisherId": "did:cheqd:mainnet:7BPMqYgYLQni258J8JPS8K",
"objectUri": "did:cheqd:mainnet:7BPMqYgYLQni258J8JPS8K/resources/6259d357-eeb1-4b98-8bee-12a8390d3497"
This implementation uses AnonCredsObjectMetadata to provide equivalency between cheqd's AnonCreds Object Method and other AnonCreds Object Methods, including the fields, where:
Object Metadata field
Method Specification
did:Indy Objects Method
did:Indy Objects Method
Legacy Hyperledger Indy Objects Method
Legacy Hyperledger Indy Objects Method
Fully qualified DID or URI to easily identify the Schema Publisher
cheqd Objects Method
Fully qualified DID URL to easily access the Schema Object
cheqd Objects Method
Note: The cheqd ledger will not provide any checks on the Schema Object Content or Metadata. Therefore, it is the responsibility of the Schema creator to make sure that the name, version and AnonCredsObjectMetadata are correct.

create Schema transaction

To create a Schema on cheqd, you need to carry out a resource transaction, specifying the following information.
cheqd-noded tx resource create-resource \
--collection-id 7BPMqYgYLQni258J8JPS8K \
--resource-id 6259d357-eeb1-4b98-8bee-12a8390d3497 \
--resource-name degreeSchema \
--resource-type schema \
--resource-version 1.5.7 \
--resource-file degreeSchema.json \
did:cheqd:mainnet:7BPMqYgYLQni258J8JPS8K#key1 \
l6KUjm...jz8Un7QCbrW1KPE6gSyg== \
--from <your-account> \
--node \
--chain-id cheqd-mainnet-1 \
--gas auto \
--gas-adjustment 1.3 \
--gas-prices 25ncheq
Note that this transaction includes the file degreeSchema.json that was formatted prior to creating the transaction.

cheqd resource Metadata

Once you have created your resource on cheqd, the following metadata will be generated in the DID Document Metadata associated with did:cheqd:mainnet:7BPMqYgYLQni258J8JPS8K
"resourceURI": "did:cheqd:mainnet:7BPMqYgYLQni258J8JPS8K/resources/6259d357-eeb1-4b98-8bee-12a8390d3497",
"resourceCollectionId": "7BPMqYgYLQni258J8JPS8K",
"resourceId": "6259d357-eeb1-4b98-8bee-12a8390d3497",
"resourceName": "degreeSchema",
"resourceType": "schema",
"resourceVersion": "1.5.7",
"mediaType": "application/json",
"created": "2022-07-19T08:40:00Z",
"checksum": "7b2022636f6e74656e74223a202274657374206461746122207d0ae3b0c44298",
"previousVersionId": null,
"nextVersionId": null

Fetching a cheqd Schema Object

Rather than requiring a specific GET_SCHEMA function and interface to fetch the Schema Object Content (such as that required on Indy for the schema_id (7BPMqYgYLQni258J8JPS8K:2:degreeSchema:1.5.7), existing DID Resolvers will be able to query for the Schema Object Content using the following parameters:
Common and standardized resource parameters:
did:cheqd:46e2af9a-2ea0-4815-999d-730a6778227c?linkedResource=true // note that this would only be a valid query if there is ONLY ONE resource associated with the DID and DID Document.
did:cheqd:46e2af9a-2ea0-4815-999d-730a6778227c?resourceName=degreeLaw&resourceType=JSONSchema2020&versionTime=2018-07-19T08:40:00Z&resourceMetadata=true or, did:cheqd:46e2af9a-2ea0-4815-999d-730a6778227c?resourceMetadata=true // note that this would only be a valid query if there is ONLY ONE resource associated with the DID and DID Document.

Query by name and version

Like via the Legacy AnonCreds schema_id, it is possible to obtain the Schema Object Content by querying the Schema Publisher DID, Schema name and Schema Version. The following query will dereference to the Schema Object Content itself:
using a DID Resolver:

Query by resource ID

For applications which are cheqd-aware, it would be possible to find the Schema Object Content via the resourceId using a fully qualified DID URL path or query, for example:
using a DID Resolver:
using a DID Resolver: