Member-only story
Making Sense of Competency Specifications Bodies
The phrase “competency as currency” seems to be popping up everywhere lately — and for good reason. With headlines about automation taking jobs, more and more people will be judged not based on a resume or even if they went to college, but what they can demonstrably do.
Indeed, in many ways a competency based economy will improve outcomes for what are currently often called disadvantaged students. As I have personally learned over the past few years coming from the K12 classroom, there are academic standards and then there are specification setting bodies. As more people find out about these bodies I thought it would be useful to document and better understand what each body does in regards to competencies+interactions and where it interacts. Most competency bodies serve different purposes or are at different ‘levels’ of the data exchange trees. EG PESC looks to set how JSON files are formatted and consumed — specifications from IMS Global and others use the JSON format for the output of their specifications.
If you represent one of these bodies, I welcome clarification — I’ve made the Google Doc able to be commented on.
For a great introduction to what makes specification-setting difficult, see Episode 2 of Edtech Interop.
