You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publishing OSMT collections of competencies to the Credential Registry has numerous benefits due to the nature of the data as CTDL Linked Open Data and the opportunities to link to/from RSDs. CTDL has numerous classes and properties for contextualizing inbound and outbound arcs to and from RSDs.
OSMT can offer a direct integration with the Credential Registry by utilizing the existing Credential Registry publishing APIs managed by Credential Engine (1) Registry Publishing Assistant API https://credreg.net/registry/assistant and (2) Trusted Partner Accounts API https://credreg.net/registry/trustedPartnerPublishing. This support use cases including as a curriculum developer, I want to link RSDs as skills embodied to my competencies that are linked to from my courses and credentials.
Or, OSMT can offer a direct integration by outputting Collections of competencies as CTDL/CTDL-ASN JSON LD. This would enable the Credential Registry publishing system to directly ingest the data. For example, U.S. Dept. of Labor outputs Industry Competency Models and ONET competencies as CTDL/CTDL-ASN JSON LD that is ingested and published to the Registry. See what this looks like via the Credential Finder. See the US DOL Industry Models web page including CTDL/CTDL-ASN JSON LD.
Currently OSMT users have to download data from OSMT, format it in a CSV file to upload to the Credential Registry. This would make publishing RSDS to the Credential Registry seamless putting the focus on the valuable CTDL linked data structure.
For more information on using the openly licensed, freely available Credential Transparency Description Language (CTDL) for properties for RSDs, so that they will be interoperable with 55K+ skills and 100K+ other entities already in CTDL, see the resources below.
Or, OSMT can offer a direct integration by outputting Collections of competencies as CTDL/CTDL-ASN JSON LD. This would enable the Credential Registry publishing system to directly ingest the data.
@jeannekitchens the application already does this, consistent with the OSN recommendations for publishing RSDs that you helped write. Does this mean that this is enough that no additional work on the CTDL-side is needed? What is the procedure for configuring the Credential Registry publishing system to ingest the data for a particular collection?
To get the list of skills in a collection in JSON-LD, request JSON like this:
Publishing OSMT collections of competencies to the Credential Registry has numerous benefits due to the nature of the data as CTDL Linked Open Data and the opportunities to link to/from RSDs. CTDL has numerous classes and properties for contextualizing inbound and outbound arcs to and from RSDs.
OSMT can offer a direct integration with the Credential Registry by utilizing the existing Credential Registry publishing APIs managed by Credential Engine (1) Registry Publishing Assistant API https://credreg.net/registry/assistant and (2) Trusted Partner Accounts API https://credreg.net/registry/trustedPartnerPublishing. This support use cases including as a curriculum developer, I want to link RSDs as skills embodied to my competencies that are linked to from my courses and credentials.
Or, OSMT can offer a direct integration by outputting Collections of competencies as CTDL/CTDL-ASN JSON LD. This would enable the Credential Registry publishing system to directly ingest the data. For example, U.S. Dept. of Labor outputs Industry Competency Models and ONET competencies as CTDL/CTDL-ASN JSON LD that is ingested and published to the Registry. See what this looks like via the Credential Finder. See the US DOL Industry Models web page including CTDL/CTDL-ASN JSON LD.
Currently OSMT users have to download data from OSMT, format it in a CSV file to upload to the Credential Registry. This would make publishing RSDS to the Credential Registry seamless putting the focus on the valuable CTDL linked data structure.
For more information on using the openly licensed, freely available Credential Transparency Description Language (CTDL) for properties for RSDs, so that they will be interoperable with 55K+ skills and 100K+ other entities already in CTDL, see the resources below.
CTDL concept schemes for controlled vocabularies: https://credreg.net/ctdl/handbook#controlledvocabularies
CTDL competency metadata: https://credreg.net/ctdlasn/terms/Competency#Competency
CTDL Collection Handbook Section https://credreg.net/ctdl/handbook#collection
CTDL handbook: https://credreg.net/ctdl/handbook#ctdlasnschema
CTDL skills in the Registry: https://credentialfinder.org/search?searchType=competencyframework
Note that CTDL provides linked open data structure for many entities that are related to skills, including credentials, courses, jobs, and pathways.
For support using CTDL, contact info@credentialengine.org
The text was updated successfully, but these errors were encountered: