-
Notifications
You must be signed in to change notification settings - Fork 1
07 Revocations
The Certification of Collaboration programme seeks to maintain a trustworthy and transparent record of certified contributions.
In exceptional circumstances, a certificate may be revoked when the information on which it was issued is found to be materially inaccurate or when the certification process was not properly followed.
A certificate may be revoked if:
- The contribution cannot be substantiated by available evidence.
- Material information was misrepresented.
- The certificate was issued in error.
- The certificate was obtained through misconduct.
- Duplicate or conflicting certificates exist for the same contribution.
Before revocation, the available evidence is reviewed by the founder.
Where appropriate, the certificate holder may be invited to provide additional information or clarification.
Revoked certificates remain part of the historical record and are marked as revoked in the registry.
Prior to the formalisation of the Certification of Collaboration programme, some certificates may have been issued without a Certificate ID, registry entry, or standardised review process.
These certificates are not automatically revoked.
Instead, they are considered legacy certificates.
Where sufficient evidence exists, legacy certificates may be reviewed and assigned a Certificate ID and registry record retrospectively.
Where verification is not possible, the certificate may remain recognised as a historical acknowledgement of participation but cannot be verified through the current certification system.
Registry entries may be marked as:
- Active
- Revoked
- Legacy
- Archived