Re: Question about certifying teachers

LMS / LRS Specs:
- xAPI/TinCan
  https://en.wikipedia.org/wiki/Experience_API
- SCORM
  https://en.wikipedia.org/wiki/Sharable_Content_Object_Reference_Model

Interactive content specs

- H5P
  https://en.wikipedia.org/wiki/H5P
  https://h5p.org
  https://h5p.org/documentation/developers/h5p-specification

- xBlock (edX)
  https://en.wikipedia.org/wiki/XBlock
  https://github.com/edX/XBlock
  https://open.edx.org/marketplace-all/

  - https://github.com/edx/cookiecutter-xblock

    > This is a cookiecutter template for new XBlocks.
    > It enables creation of the XBlock repository as well as a Dockerfile
for building and running your XBlock in the xblock-sdk workbench.

  - https://github.com/ibleducation/jupyter-edx-grader-xblock

    > Auto-grade a student assignment created as a Jupyter notebook, using
the nbgrader Jupyter extension, and write the score in the Open edX
gradebook



- [ ] "H5P as an Open Edx XBlock extension"
  https://h5p.org/node/32382


H5P / XBlock <-> LMS / CMS <-> Credential Store


LMS
  Learning Management System
LRS
  Learning Record Store

Credential Store, Repository
  See https://w3c.github.io/vc-data-model/#use-cases-and-requirements for
normative language
  - Badgr (SQL database maintained by: ___)
    - https://OpenBadges.org
    - https://openbadges.org/about/participating-issuers/
      - Badgr
  - blockchain (replicated immutable datastore)
    - https://blockcerts.org/ (W3C Verifiable Claims)

From https://www.blockcerts.org/guide/roadmap.html :

> Verifiable Claims is a lightweight format for expressing a
cryptographically verifiable claim across many different use cases.
Blockcerts and Open Badges are working towards expressing Open Badges
assertions as a Verifiable Claim.
> This approach will expand (even further) the interoperability that exists
within the Open Badge ecosystem.

On Friday, January 25, 2019, Wes Turner <[email protected]> wrote:

> OpenBadges
>
> https://openbadges.org/get-started/issuing-badges/
>
> > Open Badges provide a flexible way to recognize learning wherever it
> happens, in and out of formal education and the workplace. They can
> represent any achievement from simple participation to evidence-backed
> competency development.
>
> > By adopting the Open Badges Specification you are joining over 3,000
> organizations across the world who believe in supporting a global
> Specification that enables individuals to capture and share the richer
> picture of who they are.
>
> edX supports Badgr (OpenBadges)
>
> - OpenBadges Backpack is now Badgr
> - https://badgr.com
> - https://github.com/concentricsky/badgr-server (Django API)
> - https://github.com/concentricsky/badgr-ui (Angular 2 UI)
> - https://edx.readthedocs.io/projects/edx-installing-
> configuring-and-running/en/latest/configuration/enable_badging.html
> - https://github.com/edx/credentials
>
>
> Blockcerts (W3C Verifiable Claims)
>
> - https://www.blockcerts.org/guide/roadmap.html
>   - [ ] OpenBadges Verifiable Claims compatibility
>
> - https://github.com/w3c/verifiable-claims
>   - https://w3c.github.io/vc-data-model/
>   - https://w3c.github.io/vc-use-cases/#education
>
>
> ... https://gist.github.com/westurner/4345987bb29fca700f52163c339a270f
>
>
> On Thursday, January 24, 2019, kirby urner <[email protected]> wrote:
>
>>
>> Hi Charles (fond memories from Google App Engine days... we met at a
>> Pycon in Chicago years ago)...
>>
>> Issuing some proof of completion, in certificate form (an actual document
>> with their name on it, could be PDF) helps your enrollees put something on
>> their resume.  The other half of that equation is not a big name school or
>> company, though that might help, so much as a detailed course outline
>> and/or the actual course content, or both -- such that those following up
>> on this credential get a sense of what it means.
>>
>> What did these students actually work through?  Were there projects?
>> Quizzes.  Describing the program helps too (including with recruiting new
>> enrollees).
>>
>> When O'Reilly School of Technology closed its doors, I was clear that the
>> best way to support our alumni was to preserve a record of what we offered,
>> so those advertising completing our courses could point to something
>> objective, in terms of content covered.  OST listened and our content is
>> still online to this day.
>>
>> Example pages:
>>
>> http://archive.oreilly.com/oreillyschool/courses/programs.html
>> http://archive.oreilly.com/oreillyschool/courses/courses.html
>> http://archive.oreilly.com/oreillyschool/courses/Python1/index.html
>>
>> We show our quizzes, but not our projects, not sure why at this point.
>>
>> Students had to finish all the projects, which were assessed by their
>> human instructors.  We had no robo-grading whatsoever, not even for
>> quizzes, as we wanted them to know they had a real human on the other end.
>>
>> Of course a lot of the code camp type websites don't provide actual
>> instructors to sign off on work, as you know.  They may have students
>> aseess each other (or not), ala Coursera, which, in combination with
>> deadlines, means not everyone who starts, manages to finish.
>>
>> Attrition stats may or may not be relevant in your case.  If they got a
>> credential for just showing up (attendance), that's of course not as
>> impressive, so you do your students a favor by advertising the rigors of
>> your offerings.
>>
>> Kirby
>>
>>

_______________________________________________
Edu-sig mailing list
[email protected]
https://mail.python.org/mailman/listinfo/edu-sig