Educational and Occupational Credentials in Schema.org

Notes for W3C community group kick-off meeting

http://bit.ly/eocredko

Aims

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.

See also the Connecting Credentials glossary of credentialing terms. Related work includes: the Credential Transparency Description Language (CTDL) developed for the Credential Engine; IMS Global's Badge Alliance; and, the W3C Verifiable Claims Working Group.

Working with schema.org

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond.

A shared vocabulary makes it easier for webmasters and developers to decide on a schema and get the maximum benefit for their efforts.

http://schema.org/

• A very broad, non-specialist vocabulary
• Hierarchy of resource types
• Reuse of generic terms

The practicalities of working with schema.org described by Richard Wallis in Evolving Schema.org, Pt1: The Bits and Pieces, Pt2: Working Within the Vocabulary & Pt3: Choosing Where to Extend.

Relevant things (nearly?) in schema.org

DefinedTerm

Competence �?

( )

Organization

Person

Creative�Work

Working as a W3C Community Group

1. IPR:
1. W3C Community and working group patent and copyright policy summary
2. W3C Community contributor license agreement

Contributions to schema.org will be licensed under Creative Commons Attribution-ShareAlike License (version 3.0) and schema.org’s terms of service.

2. Membership is free and open to anyone/any organization that signs the Contributor Agreement
3. Chair: Participants choose a chair. I have been nominated, and am happy to act as chair. If anyone want to propose themself or another as chair or co-chair, there is a process for candidacy and voting.

My suggested process for our work

• Use case outlines (to define priorities)
• Examples from the wild
• Deduce requirements (check against examples)
• Model in schema.org �or�Define new schema.org terms
• Example markup
• Code to submit to schema.org
• Document (use cases and requirements plus examples)

​

Comms and coordination

• Discussion on maillist public-eocred-schema@w3.org
• Documentation on W3 CG wiki

https://www.w3.org/community/eocred-schema/wiki/

• Outcome / progress summaries on blog

All these are open: group write and world read access

Possible more conference calls if needed.

Next steps

• Use cases (here are some from Credential Engine)
• Examples (here are some from Credential Engine)�( ⇒ scope )