Skip to content

Commit a36a629

Browse files
committed
Added microsites content
1 parent 75fc2a5 commit a36a629

31 files changed

Lines changed: 8399 additions & 0 deletions
Lines changed: 203 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,203 @@
1+
{
2+
"OB-30": {
3+
"title": "Open Badges Specification v3.0",
4+
"href": "https://www.imsglobal.org/spec/ob/v3p0/",
5+
"status": "Candidate Final Public",
6+
"publisher": "1EdTech"
7+
},
8+
"OB-CERT-30": {
9+
"title": "Open Badges Specification Conformance and Certification Guide v3.0",
10+
"href": "https://www.imsglobal.org/spec/ob/v3p0/cert/",
11+
"status": "Candidate Final Public",
12+
"publisher": "1EdTech"
13+
},
14+
"OB-IMPL-30": {
15+
"title": "Open Badges Implementation Guide v3.0",
16+
"href": "https://www.imsglobal.org/spec/ob/v3p0/impl/",
17+
"status": "Candidate Final Public",
18+
"publisher": "1EdTech"
19+
},
20+
"OB-ERRATA-30": {
21+
"title": "Open Badges Specification v3.0: Errata",
22+
"href": "https://www.imsglobal.org/spec/ob/v3p0/errata/"
23+
},
24+
"OB-INFO-30": {
25+
"title": "Open Badges Specification Information Model v3.0",
26+
"href": "https://www.imsglobal.org/spec/ob/v3p0/InfoModel/ob_InfoModel.html",
27+
"status": "IMS Base Document",
28+
"publisher": "1EdTech"
29+
},
30+
"OB-BAKE-30": {
31+
"title": "Open Badges Specification Baking a Badge v3.0",
32+
"href": "https://www.imsglobal.org/spec/ob/v3p0/ImageBinding/ob_ImageBinding.html",
33+
"status": "IMS Base Document",
34+
"publisher": "1EdTech"
35+
},
36+
"OB-REST-30": {
37+
"title": "Open Badges Specification REST/JSON API v3.0",
38+
"href": "https://www.imsglobal.org/spec/ob/v3p0/RESTBinding/ob_RESTBind.html",
39+
"status": "IMS Base Document",
40+
"publisher": "1EdTech"
41+
},
42+
"OB-OPEN-30": {
43+
"title": "Open Badges Specification OpenAPI Schema v3.0",
44+
"href": "https://www.imsglobal.org/spec/ob/v3p0/schema/openapi/",
45+
"status": "IMS Base Document",
46+
"publisher": "1EdTech"
47+
},
48+
"OB-JSON-30": {
49+
"title": "Open Badges Specification JSON Schema v3.0",
50+
"href": "https://www.imsglobal.org/spec/ob/v3p0/schema/json",
51+
"status": "IMS Base Document",
52+
"publisher": "1EdTech"
53+
},
54+
"OB-JSONLD-30": {
55+
"title": "Open Badges Specification JSON-LD Context v3.0",
56+
"href": "https://www.imsglobal.org/spec/ob/v3p0/",
57+
"status": "IMS Base Document",
58+
"publisher": "1EdTech"
59+
},
60+
"CLR-20": {
61+
"title": "Comprehensive Learner Record Standard v2.0",
62+
"href": "https://www.imsglobal.org/spec/clr/v2p0/",
63+
"status": "IMS Base Document",
64+
"publisher": "1EdTech"
65+
},
66+
"CLR-CERT-20": {
67+
"title": "Comprehensive Learner Record Conformance and Certification Guide v2.0",
68+
"href": "https://www.imsglobal.org/spec/clr/v2p0/cert/",
69+
"status": "IMS Base Document",
70+
"publisher": "1EdTech"
71+
},
72+
"CASE-10": {
73+
"title": "1EdTech Competencies and Academic Standards Exchange (CASE)",
74+
"href": "https://www.imsglobal.org/spec/case/v1p0/",
75+
"status": "1EdTech Final Release",
76+
"publisher": "1EdTech"
77+
},
78+
"OR-11": {
79+
"title": "1EdTech OneRoster® Specification v1.1",
80+
"href": "https://www.imsglobal.org/oneroster-v11-final-specification",
81+
"status": "1EdTech Final Release",
82+
"publisher": "1EdTech"
83+
},
84+
"EDUAPI-10": {
85+
"title": "Edu-API Specification Specification v1.0",
86+
"href": "https://imsglobal.org/spec/eduapi/v1p0/",
87+
"status": "IMS Candidate Final",
88+
"publisher": "1EdTech"
89+
},
90+
"CEDS": {
91+
"title": "Common Education Data Standards (CEDS) Version 7 Data Model Guide",
92+
"href": "https://ceds.ed.gov/pdf/CEDS-7-0-Data-Model-Guide_for_508.pdf"
93+
},
94+
"RSD": {
95+
"title": "Rich Skill Descriptors",
96+
"href": "https://www.openskillsnetwork.org/rsd"
97+
},
98+
"DATA-INTEGRITY": {
99+
"title": "Data Integrity 1.0",
100+
"href": "https://w3c-ccg.github.io/data-integrity-spec/",
101+
"authors": ["Manu Sporny", "Dave Longley"],
102+
"status": "CG-DRAFT",
103+
"publisher": "Credentials Community Group"
104+
},
105+
"VC-API": {
106+
"title": "Verifiable Credentials HTTP API",
107+
"href": "https://w3c-ccg.github.io/vc-api/",
108+
"status": "W3C Community Group Draft Report",
109+
"publisher": "Credentials Community Group"
110+
},
111+
"PRESENTATION-EXCHANGE-10": {
112+
"title": "Presentation Exchange v1.0.0",
113+
"href": "https://identity.foundation/presentation-exchange/spec/v1.0.0/",
114+
"status": "DIF Ratified Specification",
115+
"publisher": "Distributed Identity Foundation"
116+
},
117+
"OIDC-VCI": {
118+
"title": "OpenID Connect for Verifiable Credential Issuance",
119+
"href": "https://openid.net/specs/openid-connect-4-verifiable-credential-issuance-1_0.html",
120+
"status": "Standards Track",
121+
"publisher": "OpenID Foundation"
122+
},
123+
"OIDC-VP": {
124+
"title": "OpenID Connect for Verifiable Presentations",
125+
"href": "https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0.html",
126+
"status": "Standards Track",
127+
"publisher": "OpenID Foundation"
128+
},
129+
"VC-EXTENSION-REGISTRY": {
130+
"title": "Verifiable Credentials Extension Registry",
131+
"href": "https://w3c-ccg.github.io/vc-extension-registry/",
132+
"status": "CG-DRAFT",
133+
"publisher": "Credentials Community Group"
134+
},
135+
"VC-DID-WEB-METHOD": {
136+
"title": "DID Web Method Specification",
137+
"href": "https://w3c-ccg.github.io/did-method-web/",
138+
"status": "CG-DRAFT",
139+
"publisher": "Credentials Community Group"
140+
},
141+
"JSON-SCHEMA-2019-09": {
142+
"title": "JSON Schema: A Media Type for Describing JSON Documents",
143+
"href": "https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-02",
144+
"status": "Internet-Draft",
145+
"publisher": "Internet Engineering Task Force"
146+
},
147+
"JSON-SCHEMA-VALIDATION-2019-09": {
148+
"title": "JSON Schema Validation: A Vocabulary for Structural Validation of JSON",
149+
"href": "https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-validation-02",
150+
"status": "Internet-Draft",
151+
"publisher": "Internet Engineering Task Force"
152+
},
153+
"DATA-INTEGRITY-SPEC": {
154+
"title": "Data Integrity",
155+
"href": "https://w3c-ccg.github.io/data-integrity-spec/",
156+
"status": "CG-DRAFT",
157+
"publisher": "Credentials Community Group"
158+
},
159+
"VCRL-10": {
160+
"title": "1EdTech Revocation List Status Method",
161+
"href": "https://www.imsglobal.org/spec/vcrl/v1p0/",
162+
"status": "Candidate Final Public",
163+
"publisher": "1EdTech"
164+
},
165+
"VCCR-10": {
166+
"title": "1EdTech Credential Refresh Service",
167+
"href": "https://www.imsglobal.org/spec/vccr/v1p0/",
168+
"status": "Candidate Final Public",
169+
"publisher": "1EdTech"
170+
},
171+
"VCCS-10": {
172+
"title": "1EdTech JSON Schema Validator 2019",
173+
"href": "https://www.imsglobal.org/spec/vccs/v1p0/",
174+
"status": "Candidate Final Public",
175+
"publisher": "1EdTech"
176+
},
177+
"VC-STATUS-2021": {
178+
"title": "Credential Status List 2021",
179+
"href": "https://www.w3.org/TR/vc-bitstring-status-list/",
180+
"status": "W3C Working Draft",
181+
"publisher": "W3C Credentials Community Group"
182+
},
183+
"MULTIBASE": {
184+
"title": "The Multibase Data Format",
185+
"href": "https://datatracker.ietf.org/doc/html/draft-multiformats-multibase-01",
186+
"status": "Internet-Draft",
187+
"publisher": "IETF"
188+
},
189+
"MULTICODEC": {
190+
"title": "MULTICODEC",
191+
"href": "https://github.com/multiformats/multicodec/"
192+
},
193+
"CTDL-TERMS": {
194+
"title": "Credential Transparency Description Language Terms",
195+
"href": "https://credreg.net/ctdl/terms",
196+
"publisher": "Credential Engine"
197+
},
198+
"CTDL-ASN-TERMS": {
199+
"title": "Credential Transparency Description Language ASN Terms",
200+
"href": "https://credreg.net/ctdlasn/terms",
201+
"publisher": "Credential Engine"
202+
}
203+
}
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
## Abstract
2+
3+
Open Badges are visual symbols of accomplishments packed with verifiable metadata according to the Open Badges specification. The Open Badges 3.0 specification [[OB-30]] defines the properties necessary to define an achievement and award it to a recipient, as well as procedures for verifying badge authenticity and “baking” badge information into portable image files. It includes term definitions for representations of data in Open Badges and defines an API for exchanging badge information. These term definitions appear in the current Open Badges JSON-LD Context File.
4+
5+
This version of the specification aligns Open Badges with the conventions of the [[VC-DATA-MODEL-2.0]] for the use cases of [=Defined Achievement Claim=] and a [=Skill Claim=]. The credentials that are produced are easily be bundled into [=Comprehensive Learner Records=] and [=Verifiable Presentations=]. Portability and learner data privacy are improved by expanding the usage of cryptographic proofs/signatures, because this format will be compatible with a growing array of proof schemas that are developed for the Verifiable Credentials Data Model.
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
## Conformance and Certification
2+
3+
The goal of 1EdTech certification for Open Badges [[OB-30]] is to ensure interoperable implementations of badging systems that generate and issue digital badges as well as those that host and display badges.
4+
5+
1EdTech certification for Open Badges demands features and capabilities beyond those that are strictly required by the specification. These additional features are defined in this document. The specification is intentionally left very flexible to allow it to be used for many purposes. Gaining this certification is expected to be more difficult than simply meeting the minimum requirements for producing a valid Open Badge.
6+
7+
Certification may be achieved in one or more of the following services:
8+
9+
* Open Badges Issuer
10+
* Open Badges Displayer
11+
* Open Badges Host
12+
13+
The service types and associated certification tests are defined below.
14+
15+
### API categorization
16+
17+
This specification defines a [=RESTful API=] protocol to be implemented by applications serving in the roles of [=Service Consumer=] and [=Service Provider=]. The API uses OAuth 2.0 for authentication and granular resource-based permission scopes.
18+
19+
All the endpoints defined in the [Open Badges 3.0 API](https://imsglobal.org/spec/ob/v3p0#api) are grouped in four services for certification purposes. This grouping
20+
is based on the role of the [=candidate platform=] in the API architecture and the purpose of the operation. Thus, the resulting grouping is as follows:
21+
22+
Consumer<br />(Initiates Requests) | Provider<br />(Responds to Requests)
23+
:--------------------------------: | :----------------------------------:
24+
[Service Consumer (Read)](#service-consumer-read) | [Service Provider (Read)](#service-provider-read)
25+
[Service Consumer (Write)](#service-consumer-write) | [Service Provider (Write)](#service-provider-write)
26+
27+
These services contain a set of required endpoints a [=candidate platform=] must support for its further certification. Some services may contain a set of optional endpoints that, if supported by the [=candidate platform=], it must support as well.
28+
29+
### The Conformance Process
30+
31+
The process for conformance testing role implementations of Open Badges includes the following:
32+
33+
* First, launch the [1EdTech Conformance Test Suite](https://certification.imsglobal.org/certification/verifiable-credentials) for Open Badges 3.0 and follow the onscreen instructions to run the tests.
34+
* Once the tests have been successfully run, submit your test results. A copy of your test results will be sent to your email address.
35+
36+
To pass certification, you must take the following steps:
37+
38+
* You must be an 1EdTech Digital Credentials and Badges Alliance Member, an 1EdTech Affiliate Member, or 1EdTech Contributing Member.
39+
* You must pass all the tests associated with the features you are applying for using the certification suite hosted on the 1EdTech website.
40+
* The tests must be completed by a designated representative of the 1EdTech member organization, and you must agree that there is no misrepresentation or manipulation of results in the submitted information.
41+
42+
After 1EdTech reviews your submitted information and notifies you that your application is approved, you can claim certification to Open Badges 3.0 and display the 1EdTech certified logo on your website and in your software. The 1EdTech Global Certified Products Directory will list your conformance details.
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
## Open Badges 3.0 Displayer Service Conformance {#displayer-conformance}
2+
3+
An Open Badges Displayer is an application that displays and verifies badges for viewers. The candidate platform must support viewer-initiated verification of a badge.
4+
5+
### Verification and status
6+
7+
The tests within this section refer to possible values of the status of a badge. The meaning of these values and how to determine them from a credential is defined in sections 9.1 and 9.2 of [[OB-30]]. As a quick summary:
8+
9+
- A Credential is revoked if the `credentialStatus` property is present, and the `type` of the CredentialStatus object is "1EdTechRevocationList".
10+
- A Credential is expired if the current date and time is after the `validUntil`.
11+
12+
### Tests {#display-tests}
13+
14+
1. The conformance test system will display the URL of three badges. One of them is neither expired nor revoked, other is expired but not revoked and the last one is not expired but revoked. The candidate platform must verify these badges and submit the status in the conformance test system. Demonstrate through separate videos that the platform allows viewers of badges to see the following data in all provided badges:
15+
16+
- image (if the badge provided is a baked badge)
17+
- name
18+
- description
19+
- issuer name
20+
- issuedOn Date
21+
- status (expired and/or revoked)
22+
23+
1. Demonstrate through video that the platform allows viewers of badges to do the following:
24+
- Trigger verification of the badge and retrieve results verifying that the badge credential is not expired, and not revoked
25+
26+
1. The conformance test system will display the URL of three badges created using [[VC-DATA-MODEL-1.1]] with
27+
the same characteristics as in Test 1. The candidate platform must verify these badges and submit the status in the conformance test system. Demonstrate through separate videos that the platform allows viewers of badges to see the following data in all provided badges:
28+
29+
- image (if the badge provided is a baked badge)
30+
- name
31+
- description
32+
- issuer name
33+
- issuedOn Date
34+
- status (expired and/or revoked)
35+
36+
1. Demonstrate through video that the platform allows viewers of badges to do the following:
37+
- Trigger verification of the badge and retrieve results verifying that the badge credential is not expired, and not revoked
38+
39+
#### Supported Proof Mechanisms
40+
41+
Open Badges Verifiers must support the following supported proof mechanisms for
42+
Linked Data Proof format:
43+
44+
- [[VC-DI-EDDSA]] suite with the `eddsa-rdfc-2022` algorithm.
45+
- [[VC-DI-ECDSA]] suite with the `ecdsa-sd-2023` algorithm.

0 commit comments

Comments
 (0)