The kickoff happened yesterday with stellar attendance and participation, very awesome! If you missed it, here’s how to get caught up:
- You can replay the presentation, here.
- If you prefer, the slides are available here.
- The community discussion will take place here on Google+, do join if you want to participate or just to listen.
The next step is to set up bi-weekly meetings, to work towards this group’s purpose. Which is (I can totally hear you asking) to… fill out a form, a Project Authorization Request (PAR, if you will). Aaron, as the chair, will be responsible for writing a statement of scope for xAPI. This will be narrowed over the months of work that this group does, it will describe exactly what it means to standardized xAPI, what scope the API addresses. This scope, will be put in a form. That form will be submitted to the NESCOM committee (yes, this is just as much of a rollicking ride as it sounds like). It’s important though, and sarcasm aside, standards are entirely about replicable process and that’s what we need to follow to move this forward.
***Original Post 2/20/14***
You may have heard that Aaron is heading up the xAPI working group at IEEE (stands for something, but no one calls it by the full name – it’s I-triple-E to everyone). He wrote in detail on what this means to the spec in this post. The reason I’m bringing this up is that the kickoff is next week! Join us for a Hangout on Monday, February 24th at 10am Eastern. Aaron will explain everything, with as many words as he can muster. Here’s the agenda for the kickoff:
- Why xAPI?
- Why IEEE?
- Why is Aaron doing this?
- How this Study Group will work
- Goals for the Study Group
If you can’t make it, get in touch and we will fill you in on the details.