this point my brain nearly overloaded with ideas and I have to admit I've played with coding a badging system but scrapped it I anger 2 weeks ago. This was after implementing a Drupal system and then other PHP based interfaces. I some ways I felt I'd set myself up for a fall with a number of people not just expressing interest in #digitalbadges but wanting to see a prototype after I promised some form of a system by may half term. On reflection this was unachievable but in terms of the principles of the #digitalbadges system we are in a more advanced stage items of methodology and objectives than we have ever been, rather fortunately I stumbled over a blog post by Erin knight titled The 3Ts of badge systems . This encapsulated a lot of my thinking and made things a whole lot clearer and focused. Whilst blogging about the development of  the #digitalbadges system I felt better about my own experience when reading that someone else had found it tough. Rather than dive straight into a badging system like I had done I had to reevaluate and reclassify a number of different areas. There are lots of things to consider and I got myself caught up with a lot of questions similar to what Erin describes as what badges? . Between the 3 of us Brian, Nic and I along with others including Dan Stucke looked at areas we wanted to concentrate on in a google doc.