search

1EdTech / openbadges-specification

Specs related to Open Badges
186 stars 68 forks source link

RDF integration: schema.org/Certification and schema.org/BadgeCriteria #9

Open westurner opened 10 years ago

westurner commented 10 years ago

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: https://github.com/rvguha/schemaorg/issues/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 https://github.com/rvguha/schemaorg/issues/195 ) describes schema.org/Course and schema.org/Credential.

Value Proposition:

westurner commented 9 years ago

See: https://github.com/rvguha/schemaorg/issues/195 "Thing > CreativeWork > Course"

threeqube commented 9 years ago

How about the BadgeClass object information? https://github.com/openbadges/openbadges-specification/blob/master/Assertion/latest.md#badgeclass

westurner commented 9 years ago

OpenBadges BadgeClass to schema:OpenBadgesBadgeClass

[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 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 http://schema.org/Organization
alignment Array of AlignmentObjects 0 or more CreativeWork. educationalAlignment -> AlignmentObject; schema:ItemList / rdf:List http://schema.org/educationalAlignment > https://schema.org/AlignmentObject
tags Array of Text keywords https://schema.org/keywords
tags Array of Text about https://schema.org/about > https://schema.org/Thing > https://schema.org/url

Schema.org does not solve for JWS (https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-38)

ottonomy commented 9 years ago

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.

westurner commented 9 years ago

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 notifications@github.com 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 https://github.com/openbadges/openbadges-specification/issues/9#issuecomment-68941505 .

westurner commented 9 years ago

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

westurner commented 9 years ago

CriteriaUrl / BadgeCriteriaUrl / BadgeCriteria .url

westurner commented 8 years ago

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

westurner commented 7 years ago
westurner commented 7 years ago
westurner commented 6 years ago

"Open Badges v2.0 IMS Candidate Final / Public Draft" (OpenBadges 2.0 JSONLD) http://www.imsglobal.org/Badges/OBv2p0

OpenBadges 2.0 JSONLD @context: https://www.imsglobal.org/sites/default/files/Badges/OBv2p0/v2/context.json

ottonomy commented 6 years ago

@westurner apologies if you're already involved, but I just wanted to make sure you knew about this: https://www.w3.org/community/eocred-schema/ -- The folks at Credential Engine jumpstarted a discussion group to discuss terms to go into schema.org to describe credentials. I'm trying to track it to make sure Open Badges concepts are well represented, since we're based on schema.org in large part.

westurner commented 6 years ago

Thanks! I'll try and find some time to parse through the mailing list archives at https://lists.w3.org/Archives/Public/public-eocred-schema/ .

This was 10 months ago: https://github.com/schemaorg/schemaorg/issues/195#issuecomment-289079327