Tag: Open Badges (page 2 of 10)

What is a ‘credential’ anyway?

Carla Casilli, badge system design expert extraordinaire, former colleague, and one of the authors of the report I shared my notes on yesterday, has recently been writing about the nature of badges and credentials. In her most recent post she asks the community:

Are all badges credentials, regardless of conceptual size, depth of assessment, or amount of criteria?

Last year I wrote for DML Central entitled Taking Another Look At The Digital Credentials Landscape. In it, I created a visual representation of how I, and others I’d consulted through my work with City & Guilds, saw the current digital credentialing landscape. As you can see from the image below, we situated everything within a meta-level circle of ‘credentials’.

Digital credentials landscape

What I (spectacularly) failed to do in that post was to define what I meant by ‘credential’. I assumed that everyone was using the term in the same way as I (and I assume most Europeans do). The Quality Dimensions for Connected Credentials report from the American Council on Education uses the Lumina Foundation’s definition of a credential as:

A documented award by a responsible and authorized body that has determined that an individual has achieved specific learning outcomes relative to a given standard. Credential in this context is
an umbrella term that includes degrees, diplomas, licenses, certificates, badges, and professional/industry certifications.

While this is not a bad definition, it is rather limiting; I think it’s overly-focused on traditional education. The word ‘credential’ comes from the Latin ‘credentia’ via the English word ‘credence’. To give credence to something is to ascribe validity, often via a recommendation; it is a state of belief in something as being true. Credential letters in the Middle Ages were handed from a person unknown to the recipient from someone known to the recipient (if only by reputation). As a result, the recipient would be more likely to see the person in front of them as ‘credible’. It was credibility by association.

The meanings and definitions of words change over time, of course, but I think that the second half of the Lumina Foundation’s definition, the part that talks of ‘credential’ as an ‘umbrella term’ is key. I’d just reject the first half where it talks about ‘responsible and authorised’ bodies and a ‘given standard’.

This ‘umbrella term’ approach to defining ‘credentials’ also meshes with the definitions from sources that I find reasonably convincing:

  • “A qualification, achievement, quality, or aspect of a person’s background, especially when used to indicate their suitability for something” (Oxford English Dictionary)
  • “A credential is an attestation of qualification, competence, or authority issued to an individual by a third party with a relevant or de facto authority or assumed competence to do so.” (Wikipedia)
  • “The ​abilities and ​experience that make someone ​suitable for a ​particular ​job or ​activity, or ​proof of someone’s ​abilities and ​experience.” (Cambridge Dictionaries)
  • “Personal qualities, achievements, or experiences that make someone suitable for something.” (Macmillan Dictionary)
  • “Warranting credit or confidence — used chiefly in the phrase credential letters.” (Merriam-Webster Dictionary)

I think Carla and I are arguing for the same position from two different vantage points. For example, after sharing a diagram showing two circles overlapping (but not completely) she states:

Badges, as they were envisioned originally, were created to capture learning whenever and wherever that learning occurs: formal, informal, public, private, group, individual. The overlap on the Venn diagram is sometimes referred to as microcredentials, and actually gives that term greater meaning and sense.

I definitely agree with that original vision for badges. I just can’t see a situation where a badge wouldn’t also count as a credential — even if that wasn’t the original intention .

As both the image from my DML Central post, and the image in Carla’s subsequent post demonstrates, it’s nearly impossible to do justice to the complexity of the credentials landscape in just two dimensions. Carla says:

An open badge can be designed to represent a small thing, such as a fundamental principle or a single competency (micro level) — and an open badge can also be designed to represent a large thing, like a competency set, or a license, or a degree (macro level). This visual illustrates that badges can be used to represent any credential currently being issued. This may seem like a minor thing to visualize, but given what badges can represent, it’s one that is definitely worth understanding.

I agree: if represented in three dimensions, badges would be orthoganal to the current credentialing system. They’re certainly acting at some kind of different ‘layer’. But, I would argue, if we’re forced to represent them in two dimensions, they appear to be wholly contained with the circle we currently call ‘credentials’.

What badges don’t have to be, even if they’re wholly contained within the ‘credential’ circle, is traditional. They can recognise all kinds of knowledge, skills, and behaviours — as well as all kinds of things we haven’t even thought of yet!

Image CC BY-SA Andrew Moore


I hope this was useful for those experienced in the world of Open Badges, and those who are new to the ecosystem. If you’re one of the latter, you may find the Open Badges 101 course helpful.

Notes on ACE’s ‘Quality Dimensions for Connected Credentials’

I’m not in the habit of doing this, and I’m not one of the authors, but this is an important, useful report related to Open Badges which many people may never get around to reading. The report can be downloaded for free from the Lumina Foundation’s website, and I’ve also included a link to a backup at the Internet Archive in case that site is ever down:


downloading-updates-32  Download: Quality Dimensions for Connected Credentials (backup)


Context

The first thing to say is that this report speaks into a specific context: Higher Education in the USA. Despite this, I think there’s much to glean for international audiences, and those outside of the university system. There are some areas in which I disagree with the authors (e.g. the definition of a ‘credential’, around the role of endorsement, and the need to prop up the existing system) but I’ll save that for another time. Overall, the report is excellent.

What follows is lengthy quotations from the paper, divided into the sections the authors themselves use. I’ve tried to avoid any sections specifically tied to the American education system. I’ve added my own where necessary by means of introduction and connection to help you understand the flow of the paper.

Introduction

The authors identify problems around the granularisation of credentials, as well as the disintermediation of educational institutions:

[T]he diversity of credentials is not always meeting the needs of students, educational institutions, and employers, and unfortunately the proliferation of credentials is causing confusion. There is a lack of shared understanding about what makes credentials valuable, how that value varies across different types of credentials for different stakeholders, what constitutes quality, and how credentials are connected to each other and to opportunities for the people who have earned them.

It’s worth noting that the work leading to the paper was funded by the Bill & Melinda Gates Foundation:

It provides context for higher education decision makers by describing the problems caused by fractured credentialing systems, articulating quality dimensions that help to address these problems, and visualizing how institutions can improve their credentials to increase their value while meeting the
needs of diverse stakeholders.

Competency-based education is all the rage in the US at the moment, although not everyone agrees with the approach:

This paper is closely related to another resource from the ACE Center for Education Attainment and Innovation, Communicating the Value of Competencies (Everhart, Bushway, and Schejbal 2016), which focuses on how to improve communication of the value of competencies among educational institutions, students, and employers. These papers are related because connected credentials are premised on two foundational concepts: that the competencies a credential represents should be clearly defined, and that these competencies can carry independent value, including the possibility of individual competencies
having currency value as very granular credentials. The competencies paper dovetails with this paper in that understanding and improving the value of connected credentials is directly applicable to communicating the value of competencies (and vice versa). Therefore, improving the value of competencies
is a targeted set of approaches in the broader context of improving the value of credentials. Definitions, concepts, and the dimensions of quality are shared across these two papers, with different focuses.

There are frustrations in the current landscape shared by earners, issuers, and consumers of credentials:

Today, stakeholders experience numerous critical problems:

  • Students do not always have reliable ways to compare credentials with regard to what they include, their market value, their transferability, their relationship to other credentials, and other important factors.
  • Educational institutions need well-defined information about the value of their credentials for employment, career advancement, civic engagement, and other desired outcomes in order to attract students
    and guide them to successful credential attainment.
  • Employers have difficulty understanding the competencies potential employees may or may not have mastered through the credentials they have earned.

There are, however, ways to deal with these issues:

Many organizations are already contributing to initiatives to support connected
credentials—for example:

  • Defining common language to profile the types and levels of knowledge and skills credentials represent, enabling explicit description of the relationship between one credential and other credentials
  • Using clearly defined descriptors to characterize credentials with regard to market value, transfer value, assessment rigor, third-party approval status, and more, empowering institutions to publicize the
    characteristics of their credentials
  • Providing students with clear milestones based on modular components of credentials and relationships among credentials, helping them to understand and document their progress over time along career pathways

The best way to connect credentials is not in some top-down ways, but through more grassroots approaches:

A top-down or “authoritative requirements” approach is not desirable, and in fact, probably would not work, given the diversity of credentialing. Approaches to quality connected credentials more
appropriately emerge from within communities of practice. The framing premise of this paper is that higher education leaders and decision makers are well-positioned to contribute to national initiatives already underway and improve their own credentials in ways that are appropriate for their institutions and communities

What Are Credentials?

The authors use the following definition of a ‘credential’:

“A documented award by a responsible and authorized body that has determined that an individual has achieved specific learning outcomes relative to a given standard. Credential in this context is an umbrella term that includes degrees, diplomas, licenses, certificates, badges, and professional/industry certifications” (Lumina Foundation 2015a, 11).

They also supply a (long) definition what they mean by ‘badges’:

Badges use digital technologies to represent learning achievements; however, not all digital badges are open badges, in that not all badges use open standards that support interoperability and connections among systems and contexts. In this paper, “badge” refers to “open badges” and therefore includes technical and conceptual frameworks for openness, transparency, and interoperability (for more context on open badges, see Derryberry, Everhart, and Knight 2016). “Badges signify accomplishments such as completion of a project, mastery of a skill, or marks of experience” (Casilli and Knight 2012, 1) and can be created and awarded by institutions, organizations, groups, or individuals. Badges are flexible with regard to how issuers create them, define their use, and develop their criteria (which are publicly
viewable, embedded in the badge, and verifiable). Therefore badges can be used in numerous ways to meet a community’s needs, to represent granular competencies as well as deeply linked, rich experiences and complex learning. Badges are being used in conjunction with and/or as modular components of traditional credentials such as degrees. In some cases, especially when badges link to evidence, they are being used as representations of credentials. Badges can expire or be revoked, making them useful for credentials that are not continuously valid. Given their flexibility, badges bridge traditional, accredited credentials, professional and industry-recognized credentials, and nontraditional, experimental credentials.

Importantly, the authors explain that their approach is separate from the (controversial) approach of ‘competency based education’:

Note that a focus on the value of competencies is not the same as “competency-based education,” that is, the restructuring of academic programs to focus on mastery of competencies rather than focusing on time. References to competencies in this paper are relevant for knowledge and skills in all types of credentials and academic programs.

The authors also give a definition of ‘connected credentials’ which seems to be a Lumina Foundation shorthand for an emergent taxonomy of badges:

In the context of this paper, “connected credentials” refers broadly to multiple aspects of connectedness, including connections and relationships among credentials, connections to purpose and value in multiple contexts, and connections to opportunities for credential earners.

Collective Impact for Connecting Credentials

There are many different types of credentials, serving different purposes, and issued by different kinds of organisations. This is confusing for people:

In the face of… many variations, stakeholders struggle to make sense of how credentials are related to each other. This is a particularly poignant struggle for those who seek to earn credentials, since they have few guides or coordinated information to help them make decisions and appropriate investments.

The authors outline the particular problems in the US, which I think are more widely applicable:

The Connecting Credentials Initiative’s Making the Case paper provides a clear overview of the situation, outlining the contextual factors that put pressure on our credentialing ecosystem (Lumina Foundation 2015b, 1–4):

  • The diverse range of students pursuing postsecondary education, including approximately 85 percent post-traditional students (Soares 2013, 6)
  • The mismatch between what employers need and job seekers’ capabilities
  • Lack of clear credential pathways to help students understand and reach their goals
  • The proliferation of education and training providers, with most people using multiple providers
  • Lack of transparency and consistency in quality assurance for credentials

The report goes on to reference many different aspects of the Connecting Credentials initiative, including their Beta Credentials Framework, which “uses competencies as common reference points to help users understand and compare the levels of knowledge and skills that underlie all credentials” — although this is, of course, focused on the American system.

Key Stakeholders

The authors introduce some useful nomenclature for describing the differing roles of stakeholders in the ecosystem:

For the purposes of these descriptions, the complexity of participants in credentialing ecosystems has been simplified to focus on four types of stakeholders:

  • Credential earners
  • Credential issuers
  • Credential consumers
  • Credential endorsers

Earners are “the people who attain credentials”. They have a number of problems around comparing credentials, signaling their competencies, credentials expiring, a lack of modularity and ‘stackability’ in credentials, ‘dead ends’, a lack of on-ramps, socio-economic issues, issues around transparency, and a lack of employer/industry understanding of the credentials they have earned.

Issuers are “organizations that award credentials to earners”. Their problems are around the ‘market value’ of their credentials, how credentials stack together, collaboration with other issuers, and the lack of common descriptors for popular credentials.

Consumers are “those who use credentials to make judgments and decisions about the qualifications and competencies of earners for specific purposes”. Their problems include understanding what the credential represents, and the burden of ensuring employees have the skills to go with the knowledge they earned while earning a credential.

Endorsers have “traditionally… been accrediting bodies or other independent third parties that vouch for the institution or organization and the quality and validity of its credentials. [They] are often also the ones who authorize issuers to award specific credentials. In the case of certifications and licenses, these authorizing entities can be licensure boards, state agencies, or industry organizations.” Endorsers’ problems are around determining the value of credentials, a lack of transparency and clear frameworks, and the paucity of information on which to base their endorsements.

Dimensions of Quality for Connected Credentials

This is the ‘meat’ of the report, in which the authors outline six dimensions for quality, ‘connected’ credentials:

  1. Transparency
  2. Modularity
  3. Portability
  4. Relevance
  5. Validity
  6. Equity

[The dimensions] are not all-encompassing, but they provide useful ways of discussing credentials and how they can be improved, both generally and in the analysis of specific credentials.

The dimensions overlap and also mutually reinforce each other. For example, modularity supports portability by making it easier to move credentials from one context to another; transparency supports relevance, by making it easier for consumers to understand what a credential includes and therefore how it is relevant for their purposes.

The authors outline what they mean by each of the six dimensions in bullet point format. To avoid making this long post even longer, I will simply quote the summary at the end of each dimension.

Transparency

Transparency supports connectedness by making credentials easier to understand and compare, facilitating the definition and implementation of relationships among credentials. Transparency also supports connections to opportunities by helping all stakeholders understand how credentials are valuable.

Modularity

Modularity supports connectedness by making credentials more componentized and less monolithic, leading to more connection points and possible relationships among credentials. Modularity also helps students understand the components within credentials and how they connect to each other and to larger goals such as socioeconomic mobility and lifelong learning.

Portability

Portability supports connectedness by making credentials more applicable in multiple contexts, connecting to multiple purposes and opportunities. Portability also facilitates connections among different types of credentials in different environments.

Relevance

Relevance supports connectedness by illuminating the applicability and purposes of credentials for specific stakeholders in their own contexts, thereby connecting to opportunities in those contexts. Relevance also connects and amplifies different types of value by helping stakeholders understand the
network of verification, documentation, evidence, and social interpretation supporting the credential.

Validity

Validity supports connectedness by illuminating the broad frameworks of meaning and value that connect the credential to opportunities. Validity provides a shared understanding and trust of how the credential is defined, including the evidence and quality assurance structures that are necessary to implement well-defined relationships among credentials.

Equity

Equity as a dimension of quality credentials helps people overcome their disadvantages and connect to opportunities. Equity provides a network of flexible access points and supports that connect students to credential attainment and the benefits of lifelong learning.

Describing the Current State of Credential Types

This section applies the six dimensions of quality as defined by the authors to different types of credentials, including badges. They find that badges pass all of the tests, with the only problems being (unsurprisingly, given the nature of the report) around the lack of a common language/framework for connecting them together.

Challenge Questions for Analyzing Credentials and Visualizing Potential Futures

The final section before the report’s conclusion is a series of questions under the six quality headings that issuers can ask of their credentials. For example:

Are the competencies (knowledge and specialized skills, personal skills, and social skills) represented by this credential clearly defined?

and:

What value does this credential carry for specific stakeholders that you identify as important? How do you know what these stakeholders value? Are they involved in your credential improvement
processes?

These are extremely useful questions for any issuer of credentials to consider.

Conclusion: Call to Action

The authors list various ways that those reading the report who are in US Higher Education can get involved. These include forming working groups, writing papers and book chapters, hosting workshops, and reading other papers by Connecting Credentials.

[A] willingness to ask and seek answers to these questions is an essential first step in breaking down the credentialing silos that sometimes impede student progress and cause our systems to be less effective and beneficial than they could be.

We encourage you to complete the arc of your journey: Identify your credentialing ecosystem stakeholders, articulate the problems they encounter when credentials are not connected, use the challenge questions to analyze and discuss the current state of your specific credentials with regard to the quality dimensions, and then establish a realistic plan and timeline for developing more valuable, robust, and connected credentials that reflect your new approach.


I’d recommend reading the report in full here and, more importantly, think about how you can apply the findings no matter what your context.

For more on Open Badges and how to get started with them, check out Open Badges 101, a free, open community course Bryan Mathers and I put together.

Are alternative approaches such as gamification and badging effective in increasing engagement, retention, and achievement?

Today I’ve been in Birmingham presenting at the AoC Learning Technology conference on behalf of City & Guilds. I made an audio recording of the 20-minute presentation to go along with my slides. You’ll have to manually advance, but it should be fairly obvious when to hit ‘next’!

No audio above? Click here

Some thoughts on the evidence behind Open Badges

A couple of weeks ago, prompted by a post I wrote about Open Badges and HR, Alan Levine wrote a post entitled Seeking Evidence of Badge Evidence. He made many good points in it, which led to Nate Otto (Director of the Badge Alliance) to invite Alan, myself, and a couple of others to engage in a panel session during today’s Open Badges community call.

This post is me thinking out loud about Nate’s proposed questions:

  1. What type of evidence are people collecting for badges today?
  2. What are challenges and barriers to effectively using evidence with badges?
  3. What services and capabilities could be solutions to these challenges?
  4. Who should hold and control badge evidence? Issuers? Earners?

I’m going to answer these in two sections rather than point by point.

Problems with badge evidence

The claim I/we often make about Open Badges is that, unlike LinkedIn profiles or CV’s, they’re a bunch of evidence rather than a bunch of claims. I think we mean a couple of things by that.

First, we mean that we’ve got something to show for the experience we claimed to have had. In other words, even if the badge issuer doesn’t use the (optional) ‘evidence’ metadata field, there is still some kind of social proof to back up our claims.

The second thing we mean by badges being a bunch of evidence rather than being a bunch of claims is pointing to those that do in fact use the ‘evidence’ metadata field. At this point these seem few and far between. I think this is because:

  • Organisations are still largely using badges in a ‘command and control’ top-down kind of way. In other words, creating one badge that is issued to many different individuals. This makes adding evidence onerous.
  • Badges are being issued for relatively low-level things such as participation in workshops and conferences, rather than credentialing more high-stakes knowledge/skills/behaviours.
  • People are misusing the criteria field as they are inexperienced (as we are all are, initially) in badge system design.
  • There’s a lack of understanding about the best ways to deal with the evidence that sits behind badges. Whether due to privacy concerns, fears around cost or compliance, or institutional policies, adding evidence is seen as a burden rather than a gamechanger.

Some suggestions

Most of the clients I deal with have some sort of background in education, and many have experience in designing assessment systems. However, because Open Badges are opendistributed, and put the learner in control, they need assistance in how to think differently.

Here are some suggestions that I’ve made several times to organisations large and small:

1. Provide appropriate levels of credibility

As I’ve learned during my long-term consultancy with City & Guilds, credibility comes through the triangulation of validity, reliability, and viability. If you’re issuing a PhD-level badge, for example, the amount of ‘social proof’ required will be an order of magnitude greater than those badges issued for participation in an event.

2. Put learners/users at the centre of your system

One of the greatest barriers in terms of pushback issuers are likely to get from users of their badging system is privacy. Granular permissions around the evidence that sits behind a badge are important, especially if that evidence happens to be visual in nature (e.g. photos/videos).

There are ways around this using existing systems such as YouTube, Google Docs, and Flickr, but perhaps an extension to the Open Badges specification could provide a standard on which badge issuers could build?

3. Ask employers what they want

Open Badges aren’t only for helping people into a job, on the job, and onto the next job, but this is a common use case. Given this, if you’re a badge issuer, it’s probably worth thinking through in detail who is likely to be the viewer/consumer of your badges. Talking to them about what they would consider sufficient evidence is likely to be an interesting and enlightening conversation.

Conclusion

Being able to provide trusted evidence is a gamechanger when it comes to credentialing. One of the main reasons that Alan found it difficult to find ‘evidence of evidence’ is that we’re still using the same old metaphors and structures for issuing credentials.

As I argued in my Open Badges in Higher Education keynote and afterwards in the Q&A part of Serge Ravet‘s session, if we find more useful metaphors for people that ‘certificates’ then we’re likely to see different kinds of credentials — and hopefully with many more pointing to evidence than we have now!

Image CC BY-ND Bryan Mathers

Open Badges in Higher Education: Disruptive, Desirable, and Democratic

(can’t see anything above? click here!)

Embedded above is my slide deck from today’s Open Badges in Higher Education conference. I had a great day in Southampton so thank you very much to organisers Fiona Harvey, Patrina Law, Deb Baff, Anne Hole, Jane Roberts, and Teresa MacKinnon! An extra thanks to Deb who livestreamed and recorded most of my keynote via Periscope, and to Bryan Mathers whose images I used liberally in my slides.

It was great to meet friends old and new – certainly too many to mention individually here. Resources from the day will appear in due course at this section of the conference website. My slides are also available via Slideshare.

Open Badges for HE - Participant

Why do we hire based on ‘experience’? HR, Automattic, and Open Badges

It’s 2016. Nobody can reasonably expect to have a ‘job for life’, or even work within the same organisation for more than a few years. As a result, you’re likely to dip into the jobs marketplace more often than your parents and grandparents did. That means it’s increasingly important to be able to prove:

  • who you are
  • what you know
  • who you know
  • what you can do

Unfortunately, hiring is still largely based on submitting a statement of skills and experience we call a ‘Curriculum Vitae’ (or résumé) along with a covering letter. This may lead to an interview and, if you like each other, the job is yours. We have safeguards in place at every step to ensure people don’t discriminate on age, gender, or postcode. Despite this, almost every part of the current process is woefully out-of-date. I’ve plenty to say about all of this, but will save most of it for another time.

In this post I’m particularly interested in why we include ‘job history’ or ‘experience’ when applying for new positions. Given that we have so little time and space to highlight everything we stand for, why do we bother including it? Academic credentials are bona fides, but job history is a bit more nebulous. Why is it still such a prominent feature of our LinkedIn profiles? Why do we email people CVs listing our ‘experience’?

Whether you think that looking at someone’s job history allows for a good ‘cultural fit’, or allows you to make assumptions about the network they bring with them, the reality is that we use job histories as a filter. They’re a useful shorthand. After all, if someone has been hired by Google or another big-name organisation, that’s a bit like saying they went to an elite university. We tend to believe in the judgments made by these kinds of organisations and institutions. We trust the filters. If the person was good enough for those organisations, we think, then they must be good enough for ours.

We like to tell ourselves that we live in a meritocratic world. If someone is good enough, so the story goes, then they can achieve the qualifications and experience necessary to get the job they want. Unfortunately, because of a combination of unconscious bias, innovation immune systems, and the new nepotism, some groups of people are effectively excluded from consideration. Don’t know the right people? Not good at interviews? Have skills too advanced or too new for qualifications to have been developed yet? Bad luck, buddy.

Another problem is that we tend to use what I call ‘chunky black box qualifications’ as proxies of the thing we’re trying to hire for. As an example, take jobs that require a degree ‘in any discipline’. What does that actually mean in practice? They want somebody who can think at a certain level, someone who is likely to come across as ‘professional’, someone who can submit work on time. However, we’re not directly looking at the assessment of the particular quality in this situation, we’re merely using an imperfect proxy.

There are many ways round the current status quo. For example, Automattic (the company behind WordPress which powers a lot of websites) does hiring very differently to the standard model. As outlined in this post, when hiring developers they test candidates in real-world situations through paid trials. In fact, as Automattic is a globally-distributed company, communication happens mainly through text. Most candidates don’t have voice conversation with anyone at the organisation until they’re hired! Obviously this wouldn’t necessarily work in every sector, but it is a good example of thinking differently: focus on what the candidate can do, not what they claim to be able to do.

Another way to approach things differently in hiring is to seek wherever possible to break down those ‘chunky black box qualifications’ into more transparent, granular, and fluid credentials.

For example, when I say I worked for Mozilla it usually piques people’s interest. I then have to go on and explain what I did during my time there. This isn’t easy given the amount of different things you do and learn in an organisation that you were with for three years. Yes, I had two different job titles, but I learned a whole load of things that would take time to tease out: working across timezones on a daily basis? Check. Learning how to use GitHub for development? Check. Consensus-based decision-making? Check.

Not every organisation is in a position to offer a trial period like Auttomatic. Nor would every individual be able to take up their offer. However, much as some people start off as consultants for organisations and then end up employed by them, there is value in getting to know people in a better way than the traditional CV and interview process allows. If we need better filters then we need smaller sieves.

For the past five years I’ve been working on Open Badges, a web-native way to issue trusted, portable, digital credentials. In the situation under consideration, I think there there are a few ways in which badges can be used to unlock those chunky black box qualifications.

  1. Granularity – instead of looking at qualifications that act as proxies, we can evidence knowledge, skills, and behaviours directly.
  2. Evidence – whereas LinkedIn profiles and CVs are a bunch of claims, Open Badges can include a bunch of evidence. Proof that someone has done something is just a click away.
  3. Portability – instead of credentials being on separate pieces of paper or in various digital silos, Open Badges can be displayed together, in context, on the web. They are controlled and displayed at the earner’s discretion.

I’m excited by the resurgence in apprenticeships and vocational education. I’m delighted to see more and more alternative ways organisations are finding to hire people. What I’m optimistic about most of all, though, is the ability for organisations to find exactly the right fit based on new forms of credentialing. It’s going to take a cultural shift in hiring, but the benefits for those who take the leap will be profound.

Image via Nomad Pictures

Calling out Pearson on Open Badges

Open Badges is a web-native credentialing system. It was incubated by Mozilla and I served on the founding badges team. Since then, stewardship of the project has been given to a spin-out non-profit called the Badge Alliance. I’m currently consulting on areas including Open Badges, meaning that, all told, I’ve been involved in the community for nearly five years.


You can find out more about Open Badges and how they differ from other digital credentials via the OB101 course.


There are some big players in the Open Badges space. One of them is Pearson, which you may find surprising. After all, why would an organisation best known for its rapacious business practices (and who some see as standing for everything currently wrong in education) get into the open credentials game?

The answer, of course, is to commodify it. They’ve taken a leaf from Microsoft’s old playbook: Embrace, Extend, and Extinguish. Pearson even have a page on their site explaining how they’re using different terminology just to spread FUD.

Pearson’s badging platform is called Acclaim. They have some big-name partners such as IBM and Citrix. Today, I noticed via the #openbadges hashtag on Twitter that they were singing the praises of the Open Badges ecosystem while pimping their own platform.

There’s nothing particularly wrong with that. Acclaim is technically compatible with the Open Badges Infrastructure (OBI). However, it’s entirely pointless that the badges they issue are Open Badges as users cannot export them from the system elsewhere. Given that Open Badges are portable digital credentials this kind of misses the point.

It’s true that Pearson have engaged with the community on this issue, but their justification seems spurious:

Real-time verification is essential for the clients we work with who are invested in building trust networks with their badge earners and other issuers. We fully expect the market to mature such that services like Mozilla will address this, but until then, we are not offering export / integration.

This is exactly the kind of response you would have found Microsoft giving 15 years ago when attempting to embrace, extend, and extinguish open document formats.

Growing sick of seeing Pearson’s disingenuous tweeting on the #openbadges hashtag, I challenged them today:

They held the line:

https://twitter.com/YourAcclaim/status/697785850273206273

Note that they don’t care about the spirit of the community or the ethos behind Open Badges, just the cold, hard code. As far as they’re concerned, they’re technically compatible with the OBI, therefore they’re part of the Open Badges community. This logic doesn’t wash with me.

I’m calling for Pearson to get their act together and allow badges issued via their Acclaim platform to be portable. Credly have the exact same business model as Acclaim, yet their ‘credit’ can be exported to the Mozilla backpack and elsewhere.

If Pearson aren’t willing to allow their badges to be portable, then they should have the guts to stop pretending that they’re interested in the success and sustainability of Open Badges. Muddying the waters doesn’t help anyone except Pearson’s profits.

Parody of Acclaim website thanks to the wonderful X-Ray Goggles

The Possibilities of Badges and Blockchain [DML Central]

My latest post for DML Central has just been published. Entitled The Possibilities of Badges and Blockchain it’s a follow-up to a post I wrote for them last year, which stated that this kind of thing was ‘deep in the future’. Perhaps not!

Read the post

This kind of stuff fascinates me, which is why I’m delighted that a few ex-Mozilla colleagues and interested parties have come together to form Badge Chain. You can sign up on the site for (low-traffic) email updates, and/or subscribe to our Medium publication.

What a post-Persona landscape means for Open Badges

Note: I don’t work for Mozilla any more, so (like Adele) these are my thoughts ‘from the outside’…


Introduction

Open Badges is no longer a Mozilla project. In fact, it hasn’t been for a while — the Badge Alliance was set up a couple of years ago to promote the specification on a both a technical and community basis. As I stated in a recent post, this is a good thing and means that the future is bright for Open Badges.

However, Mozilla is still involved with the Open Badges project: Mark Surman, Executive Director of the Mozilla Foundation, sits on the board of the Badge Alliance. Mozilla also pays for contractors to work on the Open Badges backpack and there were badges earned at the Mozilla Festival a few months ago.

Although it may seem strange for those used to corporates interested purely in profit, Mozilla creates what the open web needs at any given time. Like any organisation, sometimes it gets these wrong, either because the concept was flawed, or because the execution was poor. Other times, I’d argue, Mozilla doesn’t give ideas and concepts enough time to gain traction.

The end of Persona at Mozilla

Open Badges, at its very essence, is a technical specification. It allows credentials with metadata hard-coded into them to be issued, exchanged, and displayed. This is done in a secure, standardised manner.

OBI diagram

For users to be able to access their ‘backpack’ (i.e. the place they store badges) they needed a secure login system.Back in 2011 at the start of the Open Badges project it made sense to make use of Mozilla’s nascent Persona project. This aimed to provide a way for users to easily sign into sites around the web without using their Facebook/Google logins. These ‘social’ sign-in methods mean that users are tracked around the web — something that Mozilla was obviously against.

By 2014, Persona wasn’t seen to be having the kind of ‘growth trajectory’ that Mozilla wanted. The project was transferred to community ownership and most of the team left Mozilla in 2015. It was announced that Persona would be shutting down as a Mozilla service in November 2016. While Persona will exist as an open source project, it won’t be hosted by Mozilla.

What this means for Open Badges

Although I’m not aware of an official announcement from the Badge Alliance, I think it’s worth making three points here.

1. You can still use Persona

If you’re a developer, you can still use Persona. It’s open source. It works.

2. Persona is not central to the Open Badges Infrastructure

The Open Badges backpack is one place where users can store their badges. There are others, including the Open Badge Passport and Open Badge Academy. MacArthur, who seed-funded the Open Badges ecosystem, have a new platform launching through LRNG.

It is up to the organisations behind these various solutions as to how they allow users to authenticate. They may choose to allow social logins. They may force users to create logins based on their email address. They may decide to use an open source version of Persona. It’s entirely up to them.

3. A post-Persona badges system has its advantages

The Persona authentication system runs off email addresses. This means that transitioning from Persona to another system is relatively straightforward. It has, however, meant that for the past few years we’ve had a recurrent problem: what do you do with people being issued badges to multiple email addresses?

Tying badges to emails seemed like the easiest and fastest way to get to a critical mass in terms of Open Badge adoption. Now that’s worked, we need to think in a more nuanced way about allowing users to tie multiple identities to a single badge.

Conclusion

Persona was always a slightly awkward fit for Open Badges. Although, for a time, it made sense to use Persona for authentication to the Open Badges backpack, we’re now in a post-Persona landscape. This brings with it certain advantages.

As Nate Otto wrote in his post Open Badges in 2016: A Look Ahead, the project is growing up. It’s time to move beyond what was expedient at the dawn of Open Badges and look to the future. I’m sad to see the decline of Persona, but I’m excited what the future holds!

Header image CC BY-NC-SA Barbara

3 reasons open source needs Open Badges [opensource.com]

opensource.com

A few months ago, my friend and former colleague Laura Hilliger encouraged me to write something for opensource.com. She’d had a few posts published about the benefits of working openly.

Today, Bryan Mathers and I have had published an article that goes into why Open Badges are such a good fit for open communities.

The web is the perfect medium for a new credentialing system. Just like the web, Open Badges are democratic, open, and distributed. The OBI is itself open source, as are many badge issuing solutions found on GitHub and other code repositories. Open Badges help move forward the open web.

Read the post in full: 3 reasons open source needs Open Badges

I’m closing comments here to encourage you to add your thoughts on the original post.

css.php