Re: EOCred: show other requirements

Nate that is thought provoking (in a good way)

At the NGO I work at we have had pathways for a long time. I have noticed
that these pathways evolve just as much as courses do in academic
environments. Do you (or anyone else in the group) have experience with
pathways as they relate to training contexts inside corporations? I know
that the military has well defined pathways for things like promotions and
staff positions within rank and grade. I'm just wondering if we lean more
towards this "pathways" idea if that is well situated across the industry -
even outside of academia.

- Hugh

On Tue, Mar 20, 2018 at 11:12 AM, Nate Otto <nate@ottonomy.net> wrote:

> 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
>
>