How It Works

Metadata Infrastructure

Credential Registry Infrastructure

User Community Support

Web Applications Hosting and Source Code

Announcements

Posted on 11/2/2017
CTDL W3C Group

With recent Credential Engine updates, we shared information about the goal to have a subset of the Credential Transparency Description Language (CTDL) included with schema.org through the World Wide Web Consortium (W3C) Community Group process.

Thanks to the leadership of Phil Barker, the W3C Educational and Occupational Credentials Community Group (EOCred) is now approved. The aim of this community group is to show how educational and occupational credentials may be described with schema.org, and to propose any additional terms for schema.org that may be necessary. Educational and Occupational Credentials are defined as diplomas, academic degrees, certifications, qualifications, badges, etc., that a person can obtain through learning, education and/or training. They are typically awarded on successful completion of an assessment of relevant capabilities.

We would like to encourage and welcome anyone with interest to contribute to the work of the group (or even just lurk and follow what we do). To participate or lurk, please join this Group!

  • On the right side of the EOCred Community Group page, select the “JOIN OR LEAVE THIS GROUP” button.
    • You will need a W3C account in order to join. Registering for one is free, but you do need to give an assurance that you will not be contributing an IP that cannot be only licensed under W3C's terms. This is appropriate for contributing work to schema.org.
    • If you already have an account select, “LOG IN.”
    • If you don’t have an account, select “REQUEST AN ACCOUNT.”
  • We recommend you also use the “Tools for this group” available from the EOCredCG page. Click on the mailing lists and select to [subscribe to this list].
  • There’s some information on the Credential Engine GitHub site that was developed to prepare for this group, please take a look:
  • Visit the Credential Engine Technical site to learn more about the Credential Transparency Description Language (CTDL)

We hope to work with you as a member of the EOCred. Please pass this message on to anyone who you think might be interested in joining.

Posted on 10/27/2017
October 2017 CTDL Release

As of today, CTDL has been updated to the 20171027 release.

This release includes the text changes brought to us by the interrim release a few weeks ago, and brings a few key changes of its own:

  • All properties that previously had a range of rdfs:Literal now have a range of either xsd:string or rdf:langString (See https://github.com/CredentialEngine/vocabularies/issues/459 for details)
  • The ceterms:Address and ceterms:GeoCoordinates classes have been cleaned up. Their properties have been trimmed and they have been removed from the range of all properties. They have not been deprecated, as we may yet have use for them.
  • A new class, ceterms:Place, replaces the functionality previously provided by Address and GeoCoordinates. All properties that used to have a range of either of those classes now have a range of ceterms:Place. See https://github.com/CredentialEngine/vocabularies/issues/460 for details.

Additonally, the JSON-LD serializations of the schema have been updated:

  • The @context property is now a link to http://credreg.net/ctdl/schema/context/json rather than an embedded object
  • The @context document now indicates all properties with an explicit range of xsd:anyURI using the { "@type": "@id" } implementation. This means that serializations of CTDL can use ordinary strings for properties like ceterms:subjectWebpage instead of awkward { "@id": "http://..." } objects.
  • The @context document does not use { "@type": "@id" } for properties that point to top-level classes in CTDL. This is done to clearly indicate that these properties point to objects, minimize damage to any existing implementations, and to more easily facilitate the use of special classes that are used to point to entities not yet published in the Credential Registry (see https://github.com/CredentialEngine/vocabularies/issues/394 for details).
  • The @context document now indicates all properties that use a JSON-LD language map (these are the same properties that have a range of rdf:langString). Specifically, it uses the { "@container": "@language" } implementation (Example 36 in this section), such that all language maps should look like this:

{ "ceterms:name": { "en": "English (generic) Name", "en-US": "English (US) Name", "en-GB": "English (UK) Name" } }

Note that all encodings of the schema that credreg.net generates currently use "en-US" as the language property for all language string properties. This includes the encodings of the schema itself and the history/change notes.

For more information, see the following:

Posted on 10/24/2017
October Credential Engine TAC Meeting Cancelled

Due to quite a few members of the TAC attending conferences and travelling this week, we are cancelling the October TAC meeting. The CTDL update will still be released on Friday.

View All Announcements

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

Organizations

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

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

Core Principles