Simon Coggins

For 1, yes we would definitely need to keep the current certificate functionality available - if we did go down that route then the activity creator would need to choose between badge and traditional (PDF) certificate when they create the activity.

I've sent a message to Mark Nelson (the certificate module maintainer) to get his views - I agree there are some advantages of a separate module but we thought it was worth at least floating the idea given the similarities. We'll add a section to the wiki page with some pros and cons.

For 2, given that the activity creator would be choosing between creating a badge or a certificate, any metadata that is available for creating the badge is also available for the certificate. However given the different methods of constructing badges vs. certificates I'm not sure there would be much scope for code reuse.

Simon

Yes, here to start with - if discussions get very in depth and the thread gets unwieldy we can create new topic threads as needed.

Simon

It's now available at:

http://docs.moodle.org/dev/openbadges

Thanks,

Simon

I'm pleased to report that we've created a draft spec on the wiki now:

http://docs.moodle.org/dev/openbadges

and we've created a tracker issue:

http://tracker.moodle.org/browse/MDL-35073

At this stage we are really keen for comments on the proposed spec, both in terms of functionality and technical implementation.

We'll flesh out the use cases with more detail once we're happy we're on the right track then start working on some of the implementation details.

Simon

Hi,

Yes that would make sense - each custom field type has a display function called "display_item_data()" so it's pretty easy to output the field contents.

Simon