Credential Engine Technical Site
Technical Advisory Group
The Technical Advisory Group (TAG) 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.
The Application Work Group (AWG) is a standing subgroup of the TAG and supports members who are using Credential Engine data to design and/or develop applications. Credential Engine will provide technical team support, and online tools (e.g., GitHub repository, Slack Channel, Google Docs) and host meetings to bring members together to foster support. Anyone interested in sharing technical challenges and solutions is welcome to join the Applications Work Group.
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 systems that communicate all virtually all aspects of credentials.
Credential Engine offers the following options for publishing to the Credential Registry:
- Registry Assistant Publishing API
- Manual Entry
- Bulk Upload
For more information on setting up your account and getting started with any of the publishing methods, click here.
Credential Engine offers a robust search API to enable developers to leverage the wealth of data contained in the registry, using the CTDL and CTDL-ASN schemas.
Credential Engine offers a way for non-technical participants to enable a credential search on their own website. The Credential Finder Widget can be customized to match your site's theme and your preferences for automatic filtering, so that the results it shows can be more closely tailored to your site's purposes.
Join Credential Engine
Visit the Credential Engine website to:
- Learn more about Credential Engine
- Subscribe to updates
- Become a participant or partner
We are happy to announce that the April 2019 releases of CTDL and CTDL-ASN are now pending and ready for comments:
This release primarily adds terms from SKOS to CTDL-ASN to improve our use of concept schemes with competency frameworks and other places in the schema.
The CTDL and CTDL-ASN schemas will be officially updated on Friday, April 26, 2019.
Join us at the upcoming App-athon! Registered participants will have an opportunity to apply for a travel scholarship to support travel to and from the event.
Credential Engine, the Indiana Commission for Higher Education, and event partner Learning Tapestry are co-hosting the Indiana App-athon: Credential Data Learn and Build (LaB), a two-day event that will bring together technologists, developers, educators, state agency personnel, and others to demonstrate what innovations are possible with open, transparent credential data in Indiana and beyond. Learn more and register here.
As of today, CTDL and CTDL-ASN have been officially updated to the 20190301 Release.
The primary change for this release is the introduction of Pathways and Pathway-related classes and properties. The CTDL Pathway classes are intended to enable describing a wide variety of pathways, from education to careers to personal achievement.
For more information, view the Release History pages:
We are happy to announce that the February 2019 release of CTDL and CTDL-ASN are now in pending and ready for comments:
The major focus of this release is the addition of Career and Education Pathways to CTDL. Pathways allow describing a sequence of credentials and related information that ultimately lead to a goal, such as a career or credential.
The CTDL and CTDL-ASN schemas will be officially updated on Friday, February 22nd, 2019.
We invite the community to leave feedback in our Github.