That’s an excellent question. If you’ve been following the hashtag on twitter (#TinCanAPI) or watching the mailing list, you may have noticed a flurry of activity.
Currently the Experience API spec is at version .90, it’s moving to .95 at the end of August. That said, the heat is on. A bunch of very, very smart people from across the xAPI adopters, spectators, and advocates are focusing in on what .95 will be. There are increased meetings, calls, messages and beyond.
If you want to participate, please join in. There are a few ways to play.
If you’re adopting xAPI by building apps or e-learning content, ADL is hosting open Office Hours on Tuesdays starting at 2:30pm Eastern. Members of ADL’s technical team steering xAPI will be on the calls every week, ready to answer questions and walk through your code. It’s open to all and it’s a good chance to get into your weeds, get the help you need and learn from one another.
You can join the Office Hours here: https://www2.gotomeeting.com/join/416857738
If you’re interested in helping shape the specification itself (hey, some people are really into that), the Working Group calls are on Thursdays at 2:30pm Eastern. This has been a weekly call since the launch of xAPI back in April and these discussions go through the finer points of the spec as it continues to evolve.
You can join the Working Group here: https://www2.gotomeeting.com/join/776171578
Once the .95 is complete we will be making updates throughout tincanapi.com to make sure you have the info you need to work with it. In the meantime, Google group discussions have the details of the proposed changes and the working draft is here.
