Doug Belshaw was the first to enlighten me on this self publishing principle, and encourage me to set up my own site, and publish out from there. Every drawing should have it’s own canonical link he’d say. Unambiguous words, and I’m glad I listened. This rang true again when working with Jim Groom and Reclaim Hosting on the articulation of a Domain of One’s Own, in a learning context. But the immediate feedback of social media can make one (me) a touch lazy. Reading Kin Lane’s post on the Personal API, I’m reminded of just how important this principle is to those who would publish…
What gives an open badge value? Well, apart from the fact that value is a conversation between two parties, I reckon there are a few interesting ingredients – not least the parties involved in the issuing of the badge itself.
This thought was created as part of a blog post by Doug Belshaw: Badges, Proof and Pathways
If you’re interested in Open Badges, you’ve probably asked the question well who’s using them? The team at We Are Open, lead by Doug Belshaw have assembled a number of interested parties, and put together an awesome fortnightly newsletter for just this reason.
Sign up here: badge.news
Some days, it’s just not happening. So I remind myself of the process. 1. Go to trello. 2. Organise the things 3. Start at the top – half an hour later I’ve fallen down a twitter shaped rabbit hole…
There’s a bunch of skills needed for future digital workers (and me). How will we ever get stuff done?
Drawn for this blog post on the future of work skills.
How I work has changed massively over the past ten years. Okay, so now I draw pictures, whereas I used to write programs – or lead others to write programs. Probably the biggest change I’ve had is being exposed to Mozilla’s way of working. They corale creative communities using some very clever practices and technologies. And right at the centre of this deeper magic community alignment…
This thinkery was created for this DML blog post.
A beach is a place of wonder – I’m never happier than when on a beach. An endless supply of creative materials, with a landscape that continually changes. Task #1 – let’s find out what the tide is doing, and how fast it’s doing it…
If you haven’t come across the TIDE podcast, it’s well worth a listen. This week it celebrates it’s fiftieth episode, and long may it continue.
Every time I find myself on a beach, I’ll be looking for a pebble that catches my eye. I’ll pick a few contenders, and over the course of a two week holiday will end up with maybe 100 pebbles. At the end of the holiday, I’ll take maybe two or three home. I have attached meaning to them.
I hired our first Rookie at wapisasa because of his ability to solve a Rubik’s Cube in under a minute, amongst other things. To me (as someone who needs somewhat longer than a minute) I saw persistence and a pattern-oriented mind that enjoyed solving problems. The small stuff matters, but is often unnoticed or undervalued.
Open Badges seem so simple, don’t they?
But wait – don’t make assumptions – ask questions! They’ve got stuff inside. Data. Authenticated data.
But the big news? – you can take them with you because they’re built on an open standard. They can be connected together to form a learning pathway. The data structure inside the badge can even be extended for a particular purpose.
Curious? There’s loads more information (and pictures) here: OB101
This week, the team at the University of Southampton organised an excellent Open Badge conference, which I really enjoyed taking part in. Doug Belshaw (his slides are here) and Carla Casilli were keynoting.
“Let’s just badge everything” is probably not the best strategy in getting up and running with micro-credentials.
Here are two questions worth considering:
- What (behaviours, commitment, recognition…) would this badge help us encourage that we struggle to encourage currently? and
- Why would an earner of this badge show it to someone else?