RDF integration: schema.org/Certification and schema.org/BadgeCriteria #9
How about the BadgeClass object information? https://github.com/openbadges/openbadges-specification/blob/master/Assertion/latest.md#badgeclass
OpenBadges BadgeClass to schema:OpenBadgesBadgeClass
- OpenBadges BadgeClass Specification: https://github.com/openbadges/openbadges-specification/blob/master/Assertion/latest.md#badgeclass
[edit]
| Property | openbadges Expected Type | schema.org property | Note |
|---|---|---|---|
| name | Text | name | 1:1 -- http://schema.org/name |
| description | Text | description | 1:1 -- http://schema.org/description |
| image | Data URL or URL | image | http://schema.org/image |
| criteria | URL | criteria <URL> | "URL of the criteria for earning the achievement. If the badge represents an educational achievement, consider [adding LRMI markup]" ... http://schema.org/URL (a more specific type like badgeUrl or openBadgeUrl could be helpful) |
| issuer | URL | issuer <Organization> | http://schema.org/Organization |
| alignment | Array of AlignmentObjects | 0 or more CreativeWork. educationalAlignment -> AlignmentObject; schema:ItemList / rdf:List
|
http://schema.org/educationalAlignment > http://schema.org/AlignmentObject |
| tags | Array of Text | keywords | http://schema.org/keywords |
Schema.org does not solve for JWS (https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-38)
Hey, @westurner -- Thanks for working on this. I'm not steeped in schema.org's methods, but I'll try to provide a comment or two that might be useful:
Open Badges are made up of three components: Issuer, BadgeClass and Assertion. A BadgeClass describes one type of achievement recognized by one issuer. Many earners can receive Open Badges recognizing them for that achievement.
BadgeClasses themselves (as of OBI v1.0) are hosted independently of the Assertions, and hosted BadgeClasses are plain JSON, not in JWT/JWS form.
It looks like your mappings are pretty good. For image, you may want to use http://schema.org/image instead of http://schema.org/ImageObject , because there isn't any additional metadata in the BadgeClasses specifically about the image.
For criteria if you're going to create anything beyond http://schema.org/url, it should be http://schema.org/CriteriaUrl -- this field as used in an OpenBadge is too specific to use a term only one step narrower than the general URL type, I think.
I'd be fine leaving the issuer mapping -> http://schema.org/Organization unless you had specific terms for credential issuer and recipient (whatever exact words you settled on). If you're creating a Certification type, I believe these would be two essential properties.
The OBI Alignment Object was patterned after http://schema.org/educationalAlignment I believe.
If you have any more questions or want to talk synchronously, let me know -- I could probably find some time late this week or early next.
I've updated schema:ImageObject -> schema:image in the markdown table.
#RDFJS rdfjs/rdfjs.org/wiki/Relevant-Specs: https://github.com/rdfjs/rdfjs.org/wiki/Relevant-Specs
http://schema.org
schema.org defines a number of Classes (types) with Properties (attributes) that can be expressed in HTML with RDFa or Microdata, in JSON-LD (http://json-ld.org), and then in any other RDF format.
Development and discussion regarding schema.org/Course and schema.org/Credential is underway: schemaorg/schemaorg#195
How could/should we reference OpenBadges Badge Class(es) offered by a schema.org/OnlineCourse ?
[edit]
The current proposal google doc https://docs.google.com/document/d/12YWjLzZC8FiTiOwSAETRIEozeqZdn6O8a4fgqK4t5Ss/edit# ( linked in schemaorg/schemaorg#195 ) describes schema.org/Course and schema.org/Credential.
Value Proposition: