Re: EOCred: show other requirements

Concentric Sky has been working on an Open Pathways data model and will be
starting up standardization work at IMS Global soon.

Pathways is essentially a method of describing requirements for
"completion" in terms of BadgeClasses (specific assessments of achievement
based on criteria) and other nested rulesets. This vocabulary will likely
grow beyond just being able to express things that eventually boil down to
BadgeClasses.

We have found based on 4 or so years investigating the idea of "learning
pathways" that is it probably an ineffective idea to model a pathway out of
credentials themselves. It is better to make a map of learning objectives
(like competencies, program completion requirements, etc), and show how
that map relates to credentials versus trying to put credentials in a line,
because that is not how most educational applications of the pathways idea
work.

I recommend taking a light touch on the side of "requirements" for EOCRED,
because of the risk of developing vocabulary that prescribes going down a
direction that is different from what a number of implementers in the
credentials space have expressed interest in doing.

   - Yes, we should use validFor, but only for relative dates from award to
   expiration of a credential award. There should be a separate "expires"
   property for awarded credentials showing a specific expiration date.(there
   are already "expires" terms in use in almost every credentials vocabulary,
   like Open Badges and Verifiable Credentials). I recommend to use the term
   "expires" to
   - It would be useful to sync with appropriate terms validFor and
   issuedBy from http://schema.org/Permit
   - +1 to the idea of modeling the expected time commitment to complete
   the criteria of a credential. This would be important to be machine
   readable and consistently implemented across implementations more than many
   of the other properties we've talked about.

*Nate Otto*
*Director, Open Badges, Concentric Sky*
concentricsky.com
he/him/his

Received on Tuesday, 20 March 2018 18:12:50 UTC