How It Works
Credential Registry Infrastructure
User Community Support
Web Applications Hosting and Source Code
The comment period for the April 2018 CTDL release has begun. The official release date is Friday, April 27th, 2018.
This release contains several changes and updates. Please review the http://credreg.net/ctdl/release notes for details.
Reminder - The Technical Advisory Group is scheduled to meet this Friday, March 30th at 11:00 am EST / 10:00 am CST / 9:00 am MT / 8:00 am PST. Below you will find some reference links in preparation for Friday's meeting, along with instructions for joining the webinar.
Dear TAC Members,
This is a reminder that the upcoming Credential Engine TAC webinar is scheduled for this Friday, February 23rd at 11:00 am EST / 10:00 am CST / 9:00 am MT / 8:00 am PST. Below you will find the proposed agenda for this webinar and login information.
- Quick Update on Publishing
- Structure and Format of Data in the Credential Registry
- CTDL: Planning Overview for the March TAC
Audio Options: Call 866-572-8856 or connect via microphone
About Credential Registry
Credential Registry allows users to see what various credentials represent in terms of competencies, transfer value, assessment rigor, third-party approval status, and much more.
The open and voluntary registry will include all kinds of credentials, from education degrees and certificates to industry certifications, occupational licenses, and micro-credentials. Each credential will describe its name, type, level, competencies, assessments, accreditation, labor market value, and so on.
The goals are transparency and clarity, and to help align credentials with the needs of students, job seekers, workers, and employers.
Get Started Now
The Credential Engine project’s technical team (TT) provides credentialing pilot site partners with a set of services beneficial to each organization’s short- and long-term technology planning.
Through each phase of the Credential Engine project, the TT provides assistance, including non-technical and technical materials for administrators and technical staff.
Throughout the process, partners provide information and access needed to co-engineer the Credential Registry, Credential Directory, and other potential apps. Pilot site partners are also discovering the benefits of linked data, and providing iterative feedback on the process and outcomes.Learn More
Developers are able to leverage the the Credential Registry API to build applications that can read or publish as much or as little information about credentials as they need to.
The Credential Engine project's developers are using Dublin Core Application Profiles process to create sytems that communicate all virtually all aspects of credentials.Learn More
Technical Advisory Committee
The Technical Advisory Committee (TAC) promotes collaboration across, and harmonization of, standardization initiatives that are developing data models, vocabularies, and schemas for credentials and competency frameworks, and related competency information such as criticality ratings and assessment data typically captured with a wide variety of systems.
The goal is to identify, document and openly share solutions that support comparability of credentials and competencies across industries/sectors, human resource systems, education, and government systems.Learn More
Easy to Use
The code base, data schema, and API endpoints are easy to use, and easy to learn. The code base is extensible, to make new features easier to add over time.
Source code, specs, and docs are all open. The system is designed to ensure metadata stays open, as well.
No server or API is 100% reliable, so the Credential Registry will distribute its metadata. It backs up data to archive.org, an organization dedicated to ensuring data never disappears.
Based on reseearch into metadata distribution by US Departments of Defense and Education, and many other organizations.
The Credential Registry is designed to scale horizontally by allowing communities to form independently and vertically to handle high demand.
Security is very hard to get right. We have deisgned an open metadata distribution system so that tight security is not necessary. We use cryptographic security within the open data itself to ensure organization identities are non-impersonable.