http://schema.org

This site provides a collection of schemas that webmasters can use to markup HTML pages in ways recognized by major search providers, and that can also be used for structured data interoperability (e.g. in JSON).

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: rvguha/schemaorg#195

How could/should we reference OpenBadges Badge Class(es) offered by a schema.org/OnlineCourse ?
[edit]

• Thing > Intangible > Credential > schema.org/OpenBadgesBadgeClass
  • SCH: schemaorg/schemaorg/data/ext/course/course.rdfa: RDFa Class and Properties
  • DAT: schemaorg/schemaorg/data/ext/course/course-openbadgesbadgeclass-examples.txt: JSON-LD example
• Thing > Intangible > Credential > Badge > schema.org/OpenBadgesBadge
  • [OpenBadges] JWS and JSON-LD
  • [OpenBadges] JWSand RDFa

The current proposal google doc https://docs.google.com/document/d/12YWjLzZC8FiTiOwSAETRIEozeqZdn6O8a4fgqK4t5Ss/edit# ( linked in rvguha/schemaorg#195 ) describes schema.org/Course and schema.org/Credential.

Value Proposition:

• JSON-LD / RDFa / Microdata #LinkedData could be embedded in course description HTML pages and discovered by search engines (supporting queries like "Where can I find a course which offers schema:OpenBadgesBadgeClass XYZ?")

See: rvguha/schemaorg#195 "Thing > CreativeWork > Course"

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]

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.

Thank you for your feedback!

Unfortunately I am not able to contribute as much time as I'd like to this
issue.

Anyone that would like to keep pushing forward on this is more than welcome
to do so

On Tue, Jan 6, 2015 at 3:57 PM, Nate Otto [email protected] wrote:

Hey, @westurner https://github.com/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.

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

I've updated schema:ImageObject -> schema:image in the markdown table.

CriteriaUrl / BadgeCriteriaUrl / BadgeCriteria .url

#RDFJS rdfjs/rdfjs.org/wiki/Relevant-Specs: https://github.com/rdfjs/rdfjs.org/wiki/Relevant-Specs

• https://web-payments.org/specs/source/ld-signatures/

• "V2: OBIv2 Alignment"

  • blockchain-certificates/cert-schema#28

• "V2: Verification and Signature (draft)"

  • blockchain-certificates/cert-schema#25
    • "ld-signatures"
      blockchain-certificates/cert-schema#25 (comment)
    • schema.org/Course, schema.org/Credential, CTI @CTITechPlanning
      blockchain-certificates/cert-schema#25 (comment)