A new tour, built on the same engine, will be released in a couple of weeks, with more to come.

Here’s the abstract: Following the launch of the Serious Games Initiative at the Woodrow Wilson International Center for Scholars in 2002, academics have explored the use of gaming strategies and technologies to teach “serious” content.  Eight years later, it is time to take stock: what have we learned?  In this presentation I will draw conclusions from the literature, and from my research, making reference to several Canadian history “serious games” that I have developed (including games in virtual worlds, isometric environments, and mixed-reality and augmented-reality environments (including a heritage tour/game for the iPhone)).  I will explain why I think we should stop using the term “serious game”, and why I think the playful use of mixed- and augmented-reality is rich with potential for historians and other humanists.

APIs defined:
“APIs are useful translators for people who are going about their own business”

We must consider APIs:
i. within clusters
Universities support collaboration between colleagues within a university, but not those colleagues outside the university
ii. cluster to cluster
How do we transfer expertise in one cluster to another cluster?
iii. from clusters to public

Google as a model for API development
Do we feel threatened by Google because it is a quasi university (or pseudo university, depending on one’s perspective)? What can we learn from Google?
• Google never tried to do or be everything (a la Yahoo and its portal); instead they built lots of individual tools; in the same way each of us should try to do one thing well.
• Google built very simple interfaces (one field, one button)
• Users learn how to use Google apps by trying them
• Its apps are transparent (scholars tend to make things opaque)
• Google gives employees 20% of their time to do what they want; we should do this with our grad students
• Google gives credit (humanists are not good at giving credit (scientists are much better))
How should we use APIs to support collaboration?
We need to define what scholars do (this is what Zotero and Omeca have accomplished – these focused on a process of scholarship) that large corporations (e.g. Google) won’t or can’t do. Scholars:
• build databases
• create content
• print books (that last)
• go slowly
• focus on detail
• think long-term
• teach undergraduates and graduate students
• run journals, symposia, etc.

Potential deliverables (given what scholars do):
• Run a conference using GoogleDocs, where participants pay via PayPal, and another API provides simultaneous translation
• Develop a research exchange where scholars swap tasks (a credit/exchange)
Moving forward
We need:
i. knowledge of what is there
ii. the capacity to integrate it
iii. training for our students
We should build:
a. social APIs (not technical APIs)
b. tools and techniques to engage the public (e.g. so that members of the public could help researchers to do translation work)