Skip to content

Education Rulebook ​

Document FW-RB-0002 · Version 1.0.0 · Status Active · Updated 2026-10-02 · Licence CC BY 4.0 Official English translation of the Turkish source text; in case of conflict the Turkish text prevails.

The rulebook for the two shared credential types in education (student certificate, diploma): type identifiers, data model summary and selective disclosure policy, who may issue, the identity proofingChecking that a person really is who they claim to be before a credential is issued, for example with an ID card and a liveness check. level before issuance, validity and revocationWithdrawing a credential before it expires; the issuer marks it in a status list that verifiers check., presentation and verification policy, semantic basis (ELM v3 / ISCED-F / EQF), trust anchorThe root key or certificate a verifier trusts first; everything else is checked back to it. and versioning. It branches from the Tamga RulebookA set of binding rules. The Tamga Rulebook holds the rules for all participants; each credential type has its own rulebook that branches from it. (FW-RB-0001) and is written on the pattern of the EUDI ARF (Architecture and Reference Framework)The document set that describes roles, architecture, trust model and rules. Tamga ARF follows the structure of the EU ARF. Annex 3 rulebooks; the technical schema is in SPEC-SCHEMA-0002, and this annex gathers the rules an institution needs to read.

0. Scope ​

This rulebook covers two credential types:

TypevctCatalogue
Student certificateurn:tamga:edu:StudentCredential:1schemas.tamga.network/v1/edu/StudentCredential/1.0.0
Diplomaurn:tamga:edu:DiplomaCredential:1schemas.tamga.network/v1/edu/DiplomaCredential/1.0.0

Both extend the root type urn:tamga:core:TamgaBaseCredential:1. The technical definition (JSON Schema, type definition, ELM mapping) is in SPEC-SCHEMA-0002; in a conflict that document prevails. Following the ARF Annex 3 pattern, this rulebook answers: who issues, to whom, with which identity proofing, for how long it is valid, how it is revoked, how it is presented and verified.

Terminology: in EU terms these credentials are non-qualified EAA (Electronic Attestation of Attributes)The eIDAS term for a credential that attests attributes of a person, such as a degree or a membership.; the Tamga class follows the issuerThe institution that signs and issues credentials: a university, a professional body, a public institution or a company.'s registration: EAA, qualified or public.

1. Data model (summary) ​

1.1 Common attributes (root type) ​

AttributeTypeSelective disclosureNote
family_name, given_namestringalwaysPerson
birth_datedatealwaysNot disclosed in the employer scenario (age discrimination risk)
awarding_body_namemultilingual stringallowedThe institution's official name
awarding_body_idstringallowedInstitution identifier (not issuer_id; the ELM identifier)
awarding_body_countryISO 3166-1 alpha-2allowed
cnfJWK—Binding to the wallet key (mandatory)
vct, vct#integrity, iss, iat, (exp), (status), (category)——Transport profile

Forbidden: a national identity number (TCKN etc.) in any attribute; there is no photo attribute (face matching is done with the identity credential or PID (Person Identification Data)The core identity data a state issues at the highest assurance level. Tamga does not take this role; its identity credential is not a PID.).

1.2 Student certificate — additional attributes ​

student_status (ACTIVE | ON_LEAVE; no graduates), enrollment_year, study_level (EQF 5–8), programme_title (multilingual string), isced_f_code (2–4 digits, mandatory), faculty_name, expected_graduation_year, is_enrolled (derived, true). All allowed. exp is mandatory and exp − iat is at most 90 days. There is no status.

1.3 Diploma — additional attributes ​

qualification_title, eqf_level, nqf_level (TYÇ), isced_f_code, awarding_date, mode_of_study, credit_points (ECTS), grade (always), grading_scheme, thesis_title (always), is_graduate (derived, fixed true), graduated_before (derived). There is no exp; status (status listA compressed, signed list in which each credential has one position that tells whether it is valid, suspended or revoked., IETF Token Status List) is mandatory.

1.4 Selective disclosure policy ​

AttributeDefaultRule
grade, thesis_title, birth_date, family_name, given_nameHidden (always)Not disclosed without the user's explicit approval
Other attributesDisclosed on request (allowed)Must be in the verifier's scope
status, cnf, vct, iss, iatAlways visible (never)Not personal data

The employer's "degree confirmation" scenario: is_graduate, qualification_title, eqf_level, isced_f_code, awarding_body_name, awarding_date are disclosed; birth_date, grade and thesis_title are not.

2. Who may issue ​

RequirementStudent certificateDiploma
Issuer categoryEDUCATIONEDUCATION
Minimum accreditationI2 (contracted)I2; I3 SHOULD
Credential type authorityThis vct in schema_authorizations (a time-windowed allow-list)the same
Legal authorityThe authority to award diplomas and student certificates lies outside the network (the Council of Higher Education); the registrar records it, it does not approvethe same
Authentic sourceThe institution's student information system or its contracted connectionthe same
KeyUnder the institution's control; in an HSM or e-seal at I3the same

An institution cannot authorise itself; authority comes with the registrar's entry.

3. To whom it is issued ​

  • Student certificate: a student whose enrolment status is ACTIVE or ON_LEAVE. No student certificate is issued to a graduate; graduation is the diploma type.
  • Diploma: a person who has completed the graduation process. The person applies; issuing on behalf of a third person (parent, proxy) requires proof of representation (RB-AP-12).
  • One active set of copies (10 copies) per student; on re-issuance the old set is revoked.

4. Identity proofing before issuance ​

The level is not written into the credentialA digital document signed by an issuer and held in the person's wallet; the person shows only the fields that are asked for.; it is a precondition of the type.

TypeMinimum levelAccepted paths
Student certificateT1Offer by e-mail and transaction code by SMS; offer on the student information system screen
DiplomaT2Offer in the student information system after multi-factor sign-in; the institution's registration desk (in person); licensed remote identity verification
Further optionT3Qualified electronic or mobile signature — only through the authorisation code flow or in person; forbidden with the pre-authorised flow

A diploma is never issued with e-mail and SMS alone.

5. Validity, renewal, revocation ​

TopicStudent certificateDiploma
ValidityAt most 90 days; before expiry the copies in the wallet refresh themselves with a refresh token and the institution reads its record againUnlimited (no exp)
Revocation listNone — the short life replaces revocation; a credential that has not expired but is no longer accurate is an accepted riskMandatory; status.status_list {uri, idx}
Reasons to revoke— (not re-issued)Annulment of the diploma (forgery, court decision), an incorrect credential (by re-issuing), withdrawal of consent, a reported device breach
Suspension—SUSPENDED (2-bit value) — during a review
Publication interval—Fixed interval (60 minutes in the pilot); no urgent publication; a revocation takes effect within 90 minutes at most
Institution suspendedNo new credentials; existing ones remain valid until they expireNo new credentials; earlier diplomas remain valid according to their issue date
Certificate renewalEarlier credentials are verified against the old issuer_id entrythe same

6. Presentation rules ​

  • Only OpenID4VP (OpenID for Verifiable Presentations)The protocol a verifier uses to request a credential from a wallet and receive the presentation. and DCQL (Digital Credentials Query Language)The query language a verifier uses in OpenID4VP to say which credentials and which fields it needs.; signed request; encrypted response.
  • Always the same copy per verifierThe party that checks a presented credential: signature, issuer in the trust list, status and policy. Also called relying party.; the attributes disclosed to the same verifier for the same type are consistent.
  • A verifier's scope is a subset of this type's attributes; for a verifier asking for grade, thesis_title or birth_date, the wallet shows an over-asking warning; if these attributes are not in the scope, the request is rejected.
  • In person: the access pass is used for campus access; once the ISO/IEC 18013-5 proximity flow arrives, it replaces it.

Example DCQL (degree confirmation):

json
{
  "credentials": [
    {
      "id": "diploma",
      "format": "dc+sd-jwt",
      "meta": { "vct_values": ["urn:tamga:edu:DiplomaCredential:1"] },
      "claims": [
        { "path": ["is_graduate"] },
        { "path": ["qualification_title"] },
        { "path": ["eqf_level"] },
        { "path": ["isced_f_code"] },
        { "path": ["awarding_body_name"] },
        { "path": ["awarding_date"] }
      ]
    }
  ]
}

7. Verification policy (for verifiers) ​

Verification uses the canonical pipeline of the specification (RB-RP-03). Type-specific rules:

PolicyRequired
job-application-degree (degree confirmation)vct = DiplomaCredential:1; the issuer is in the EDUCATION category and authorised for this type; class at least I2 (I3 SHOULD); not revoked; is_graduate = true, eqf_level ≥ 6; there is no holder assurance attribute — the diploma type is bound at T2
student-discountvct = StudentCredential:1; issuer at least I2; not expired; only is_enrolled = true
campus-accessThe same as student-discount, plus an access pass registration; time-limited consent of at most 6 months
High risk (public sector, banks)All of the above, plus face matching with the identity credential or PID (the verifier's responsibility)

The policy names are those of the reference verifier. The result has three values; INDETERMINATE is not acceptance; the user is told "cannot be verified", not "invalid".

8. Semantic basis and export ​

  • The ELM v3 and Europass mapping is normative; ISCED-F 2013 (2–4 digits), EQF 5–8, TYÇ nqf_level.
  • No JSON-LD carrier is used.
  • The programme-to-ISCED-F mapping table is provided by the institution; without a match no credential is issued.

9. Trust anchor ​

The verifier checks the issuer against the tl-tr › issuers[] entry (issuer_id = the fingerprint of the leaf certificate) and the type against the lotl › schemas[] entry and the catalogue content_hash; root fingerprints are on tamga.network/trust-anchor.

10. Versioning and change ​

  • The type's major version is in the URN (…:1); adding or removing an attribute means a new major version and a new section in the rulebook.
  • Minor and patch versions (display, description) are published with a new metadata_url and content_hash under the same URN; the catalogue marks the current version; a published file never changes.
  • A type in DEPRECATED status remains verifiable.
  • This rulebook is updated at the same time as any version change of SPEC-SCHEMA-0002.

11. Open topics ​

  • Making I3 accreditation mandatory for diplomas after the pilot.
  • Export in ELM JSON-LD format for EU education interoperability.
  • Carrying an optional trust anchor pointer (trust_anchor) in the credential.

References ​

The decisions, specifications and standards this document rests on are listed in Annex E.

Status ​

Active — version 1.0.0 (2 October 2026).

Tamga ARF 1.0 · CC BY 4.0 · The Turkish text is the source; this is its official translation