For tech teams

Code that makes skills portable worldwide.

Open schemas, traceable sources and versioned APIs give development teams a shared foundation: locally integrable, globally interoperable and permanently free from lock-in.

Request pilot integration Review the standard

Nonprofit · Global public good

  • Open interfaces
  • No vendor lock-in
  • Built for global diversity

Integration principle

Meaning travels with the data.

An OSC integration transfers more than labels. It records which skill is meant, where the claim came from and which version it belongs to.

The data remains understandable after leaving an HR system, learning platform or analytics tool.

Core fields

Start small, extend later.

A small, well-maintained dataset is enough for a first pilot. These four areas should be right from the start.

Identity

Stable ID, record type, language and preferred label.

Meaning

Short definition, synonyms and clearly typed relationships.

Origin

Publisher, source, licence and evidence reference where available.

Lifecycle

Version, change date, status and a clear change note.

Data contract

Expert data and calculated signals stay separate.

That makes testing, audits and later model changes easier.

  • Ontology fields describe concepts, classes and rules.
  • Graph data connects concrete skills, roles, sources and evidence.
  • Embeddings and scores include model version, purpose and creation time.
  • Evidence includes issuer, method, context, validity and review status.
  • A matching score is never presented as a confirmed competency.

API working draft

Example paths for pilot integrations.

The paths show the intended structure. They do not yet promise a production address, authentication method or availability.

GET /osc/api/v1/skills/?language=de-DE
GET /osc/api/v1/skills/{skill_id}/
GET /osc/api/v1/evidence/{evidence_id}/
GET /osc/api/v1/graphs/relations/?skill_id={skill_id}
GET /osc/api/v1/embeddings/similar-skills/?skill_id={skill_id}
POST /osc/api/v1/pilots/evidence-check/