Where 2.0 is going to be epic this year (see my interview with Brady Forrest here), and it is so exciting to be part of it.  Location technologies and augmented reality are annointed rulers now.  Time Magazine recognized augmented reality as one of its 10 Tech Trends for 2010 (for more see ReadWriteWeb).

The photo above is by Jeremy and Lisa Hight.  Jeremy Hight is an information designer, theorist and artist working in Augmented Reality and Locative Media.   His essay “Narrative Archaeology” was named one of the 4 primary texts in Locative Media.

Jeremy Hight will be part of our panel: The Next Wave of AR: Exploring Social Augmented Experiences, with Anselm Hook, Joe Lamantia, Sophia Parafina and myself. We will debut the video of the ARWave project demo that brings together augmented reality, geolocation, and wave federation (more details later in this post).  And, Jeremy will bring to our presentation some augmentations on his recent brilliant work and paper, “Writing Within the Map.”

Greg J. Smith’s points out in his in depth look at Jeremy’s work that it, “dovetails with some of the main points in Bruce Sterling’s recent atemporality keynote at Transmediale” – fortunately there is a transcription of Bruce’s keynote here.  What is so awesome about this dovetailing is that you can get a feel for the fun part of living in an, “atemporal network culture.”  And, if you want to really understand just how much locative media and augmented reality have changed us, you  might want to dig into these texts.

Bruce Sterling and Jeremy Hight, and members of the ARWave team, and a superb cast of augmented reality movers and shakers – including Will Wright and Jesse Schell, will be speaking at Augmented Reality Event in Santa Clara, June 2nd and 3rd.

But, this week, the AR community’s attention will be on the events at Where 2.0.   The keynote speakers will be streamed live, so if you are not fortunate enough to be there, tune in!

The Next Wave of AR: Exploring Social Augmented Experiences

On our panel, Jeremy Hight, Anselm Hook, Sophia Parafina, Joe Lamantia and I will cover some of the key social, cultural, technical and interactional questions for exploring social augmented experiences. There will be five lightning presentations, and an opportunity for questions from the audience, and a world premier of the ARWave demo!

1) “Augmenting the map as interface: AR and Locative Narratives” - Jeremy Hight

*Map augmentation of the historic route 66 can house an essay contest and publication globally but as embedded within that map augmentation instead of books or even web sites.

* A place on a map can be a graphic index and database to save and collect
the writing of that place with a graphic or textual search index.

*One can pop immersive visualizations of abandoned or lost buildings from map location in shared software and collectively augment (imagine channels within the lost core of detroit where one is memories and accounts tagged within parts in the immersive visualization while another is of poems and stories written by people moved by the place and its semiotics and story).

*The news stand is to be the map.

*New forms of literature will be born of mapping, spaces,augmentation and
new tools

The concept drawings below (click to enlarge) are a collaboration between Jeremy Hight and Paul Wehby, Senior Designer at LA County Museum of Art.

2) Anselm Hook will look at, “10 reasons why AR isn’t a flash in the pan,” and how, “AR can help us see the world we would like to have exist.”

Anselm notes, “So much of what we do is so fickle and I’m looking for ways to connect digital media work to deep values.”

3) Sophia Parafina will present on, “Social AR and Crisis Response”

“Augmented reality as a multi-party conversation.  Rather than being passive viewers of AR with a limited ability to  checkin to places and make annotations, current devices can broadcast sensor information that can be fused into an interactive stream. AR users can send and receive information, location, and sensor data from their mobile device.  The streams can be federated into a unique AR view composed by the user.

Entertainment and gaming are obvious applications, but it can also be applied to crisis situations such as the search and rescue operations in Haiti.  Efforts such as Mission 4636, the SMS translation service, could benefit from AR views.  The collaboration among the Mission 4636 volunteers was the key element  in their success for providing location and rapid translation to responders on the ground.

With an AR view, responders can send back their sensor information from their mobiles to provide contextual information to remote volunteers.  This extends the conversation between remote volunteers and on the ground responders and fosters collaboration which was a key element for the success of Mission 4636″

4) Joe Lamantia, an experience design and strategy consultant helping to define the interaction framework and scenarios behind ARWave, will discuss, “Design Principles For Social Augmented Experiences:”

“With the exotic mixed realities envisioned by futurists and science fiction writers seemingly around the corner, it is time to move beyond questions of technical feasibility to consider the value and impact of turning reality inside out for everyday social settings and experiences. Thanks to the inherently social nature of augmented reality, we can be sure the value and impact of many augmented experiences depends in large part on how effectively they integrate with the social dimensions of real-world settings, in real time.”

Joe will share, “eight guiding principles for designing experiences that engage naturally with the social dimension, and increase the value of augmented experiences.”

5) “ARWave – A demo and state of play,” from Tish Shute

I will have the awesome privilege, on our Where 2.0 panel, of showcasing ARWave.   We will  premier the ARWave demo which shows how ARWave has accomplished the basics of geolocating data on Wave Federation Protocol (and real time collaboration on this geolocated data).  If you’re interested in the ARWave project join the Mailing list, FAQ are here, and have a peek at the current state of development at Google Code, and the specification for an AR Blip.  We also have Waves for the project hosted on Google Wave.  You can join the general discussion here, and the technical side here.

The picture below is a screen shot from the demo video produced by core AR Wave developer and concept designer, Thomas Wrobel.

Click on the image to enlarge, and note: “The pink thing is from Dennou Coil. Its an anti-virus program (that literally chase’s down bugs and glitches and removes them).”

ARWave

In ARWave, stories or art are tied to place. And as Jeremy Hight writes:

“The possibility exists to take a part of an area and overlay a dystopia, a utopia, multiples of each of these, or even recreations of previous incarnations in the past. Writing and publication thus cannot only be of place, and form(s), but of selected augmentations of icons, streets, buildings and related texts on top of the map. These spaces can be built in real time and can be turned on and off as channels of augmentation that over time illustrate many faces of place in its present, past, possible futures,etc. with texts within these alternate spaces as commentary, as fused aesthetic analysis, or simply creative writing relevant to these charged and hybrid spaces.”

As Thomas notes, Jeremy Hight’s,  “idea of channels ties into the concept of waves = a layer, and people can have many layers on at once.”

This is different from the Layar concept of a layer or rather “layar.”

“We are not talking about layers in the classical map layer way of thinking, where you have a layer of all restaurants or a layer of all mountain peaks, etc.,” notes ARWave developer Markus Strickler.

Currently all geo location apps like Layar have to use their own servers, so users have to use different clients with different log ins to see data from different sources.  But because ARWave uses federation, we don’t depend on centralized infrastructure where the client of one company can only connect to the server of that company.  This opens up many exciting new possibilities for how people can decide to view and publish geolocated data.

With AR Wave, via one login, people can access the whole distributed network of servers (see diagrams below), and any content will be accessible to them. ARWave will make it easy for individuals, not just developers, to layer their environment – allowing the creation of augmented reality content to be as simple as contributing to a Wave.

“ARWave will enable individuals to publish easily to everyone….or just a few people,” Thomas notes:

“To ‘publish’ is also self publication and distribution in communities or like minded groups without the hard read of publication or rejection.” = publishing on a Wave. No one approves it, anyone can publish to communities, or their friends and family. Or even just personal publishing it for their own reference.”

But ARWave does not compete with existing AR Browsers.   On the contrary, AR browsers like Layar, Wikitude and others, could implement ARWave and use it to enhance their applications.

“Layar has a killer browser already,  ARWave would add social features. They can keep their “walled garden” of data and still join the federation of open data too ” (Thomas Wrobel)

Yup, that is the cool part of federation – you can have your cake and eat it too!

Sophia Parafina and I will be organizing a discussion session on ARWave and Federation at WhereCamp, right after Where 2.0, April 3rd and 4th, and Dan Peterson who is in leading the federation effort for Google Wave will join us.

The diagrams below illustrate how ARWave and federation can revolutionize the way we share our augmented realities.

Real Time Social Augmented Experiences

Another key aspect of ARWave is it’s near to real time update capabilities.  As Jeff Pulver pointed out in, “SXSW 2010: The days twitter became less relevant:”

“At South By Southwest 2010 (SXSW), a strange thing happened on the way to Austin. A community of twitter faithful shifted from sharing everything about everything on only twitter (and maybe Facebook) and changed their habits to rely on learning about what was happening and where things were happening by using foursquare and Gowalla instead. I’m sure there were other products and platforms being used including Loopt and GySPii but foursquare and Gowalla were the dominant platforms.”

Later Jeff wrote:

“There were times where I could feel the ebbs and the flows of the people move as different people checked into various locations. While most of this was felt locally in the place I was in, it also became apparent on the platforms when hundreds of people would rush to check in to a location. There were also times when it felt like I was chasing ghosts; These were the times I would go to a spot because a friend had checked into that spot only to discover they were no longer there.”

ARWave’s realtime collaborative capabilities are going to introduce some fascinating dynamics to “chasing ghosts,” as the ARWave framework gets integrated into services like foursquare – a project we have already begun to look at.

Augmented Reality Search

As I mention in my previous post, ARWave presents some fascinating possibilities for AR Search.  For example, one might do advanced searching within waves using SPARQL, which could then display in the form of a personal blip in your viewpoint (which in turn could be shared with others).  Linked data will be massively important in filtering and delivering useful info for augmented views (see my conversation with Will Wright about the problem of augmented reality overriding our very smart instincts and not being useless or worse as a result).

Anselm Hook, who I interviewed in depth recently about, Visual Search, Augmented Reality and a Social Commons for the Physical World Platform: Interview with Anselm Hook, has some very interesting thoughts on real time stuff, trading brokerages, and  the view within a single city block, which he elaborated on in the second half to this interview which is upcoming on Ugotrade soon!

The ARWave Developers

There are three people who unfortunately can’t join us at Where 2.0 –  the costs of travelling from Europe being an obstacle.  But as they have been developing the code for ARWave that will rock our augmented world, I asked them, in a Wave conversation, to give me a few comments about their interest in working on ARWave, and a pic and a short bio.   Also I should mention the work of the PyGoWave team whose incredibly fast work creating PyGoWave has given ARWave a rocket launch pad.  Also many thanks to the Wave community, see the Wave Federation Protocol documentation, Google’s Wave Server, RubyOnSails (Ruby On Rails based Wave server).

Davide Carnovale @need2revolt

“Imho, the coolest geolocated related thing is that we’re making a world where the info does not necessarily comes from an explicit search from the user, but comes also from the actual locaton you’re in. For instance, you can have special offers in stores like fourquare does, or your friends can leave geolocated notes for you that are triggered when you walk by.  We can have games based on the treasure hunt schema requiring you to actually go to specific location.

Other than this I can think about self-guided tours of the city, maybe user generated too, or for museums.

Naturally these are long term goals with some rl use cases.

As for my bio, there isn’t much to say… I got a first level degree in computer science and I’m taking the second (and last) level. I’ve developed with mobile agents, osgart/artoolkit, brain computer interfaces, linux kernel and that’s pretty much all…”

Thomas Wrobel

“If you are looking for specific advantages of using Wave I’d say;

* Federated – Letting creators tap into bigger userbase. Each new app or data layer will add to the “incentive” for users to join in. Google had some good stats a few months back as to how much a simple login screen can put people off using stuff.  By breaking that barrier it should make AR userbase’s grow.

* It deals with user accounts, permissions, and real-time updating without creators needing to make a new server standard themselves. It lowers barriers to development.

* As the clients, servers, and data can be made separately by different parties, its easier for developers to concentrate on just providing what they want. You want to just make content? No problem! You dont need to worry about doing anything else but that. It would become as easy as making a webpage (or easier!).

* Bots will allow the development of interactive AR games very easily. Just like modern version of IRC bots, the infrastructure does the heavy lifting, and interesting things can be done with just simple scripting.

* The idea is anyone will be able to make a layer onto the world, and people can mix, match and share their layers as they wish. Its not just the data that becomes interesting to see augmenting our world, but the combinations of data! For example, perhaps you could see the profits generated by different companies above their buildings, but also see how environmentally friendly they are at the same time. Or maybe see pollution levels against health-statistics.  Seeing combinations of geolocated data from different sources at the same time has many interesting possibilities both for scientific as well as casual (game/ map/ chat) use.

hmz..I could go on forever listing stuff here really…..

I guess if we are supposed to be forming a roadmap of significant/interesting things for ARWave?

* Example clients letting people make their own layers (waves) and add points to them.

* Letting people log in to different servers

* Servers federated together. (not our responsibility, but essential part of the roadmap).

* Anyone logged into any server can see data from anyone else that’s shared with them, regardless of where they are logged into

* 3D support, demonstrating various sorts of geolocated data.?

* Use of bots for example games?
—-
My Bio’s quite simple.
Studied 3D Animation in Portsmouth, UK.
Moved to the Netherlands, have since been working in creating ARG games, in the last year founded Lostagain (Lostagain.nl).”

Markus Strickler @kusako

“I think the main point behind ARWave is to go beyond simply displaying existing placemarks on top of a live camera view, towards a highly personalized, augmented world where everybody can edit and share localized information collaboratively and in real time. Wave provides the means to do this through its model of persistent real time conversations and adds even more by providing a way for personal agents (robots) to participate in these conversations.

As for my Bio: I’ve been developing Web applications for the last 15 years, hold a degree in Image Sciences and am currently working as a Java developer in Cologne, Germany.”

Images  from Mitsuo Iso’s Denno Coil (Click to enlarge), the game “Metroid Prime,” and Terminator.

Thomas Wrobel, Sophia Parafina, Joe Lamantia, Matthieu Pierce, and I will lead a  session tomorrow for AR DevCampNYC introducing the AR Wave Project.  Thomas, Joe and Matthieu will be participate via skype (10am to 11.30am EST), and Sophia Parafina and I will both be at AR DevCampNYC at the The Open Planning Project office (TOPP).  The PyGoWave crew will be introducing PyGoWave via LiveStream.

At 1.30pm EST to 2.30pm EST there will be a shared PyGoWave/AR Wave session with Mountain View (if bandwidth permits).

The skype conference will be at ardevcampnyc .  To participate in Wave,  please join the public Wave,  AR Wave: AR DevCamp Session.  There is also a AR Wave Wiki up now – see here.

Dimitri Darras (avatar Dimitri Illios) is working on streaming the AR DevCampNYC sessions into Second Life,  SLURL here.

Thomas has done a very nice introduction and FAQ below.  This should help people new to this project to get up to speed quickly.

There are already several Waves that show the history of this project including: AR Wave: Augmented Reality Framework Development,  AR Wave Use Cases, PyGoWave AR Tech Discussion,  AR Wave Augmented Reality Wave Development, AR Wave / Muku Organization and Admin.

Also I have several posts for people interested in more of the background, including: The Next Wave of AR: Mobile Social Interaction Right Here, Right Now!, AR Wave: Layers and Channels of Social Augmented Experiences, Total Immersion and the “Transfigured City:” Shared Augmented Realities, the “Web Squared Era,” and Google Wave.

Thomas uses the term Arn (augmented reality network) which is one of the candidate names for the project, Muku (crest of a Wave) is another suggestion.  Thomas’ intro and FAQ below can also be found here.

What is the AR Wave Project?

In simple terms its a protocol for storing geolocated data on Wave servers that’s currently being developed.

We believe this will help lay the foundations for an open, universally accessible, and decentralised system for shared augmented reality overlays which various clients can connect to and use.

This AR Network should spark a lot more rapid adoption of AR technologies, give existing browsers more functionality, and provide the network infrastructure, allowing many of the fictional depictions of AR to become a reality one day.

The AR Network.

When we speak of a future AR Network, we mean one as universal and as standard as the internet. One where people can connect from any number of devices, and without additional downloads, experience the majority of the content.

Where people can just point their phone, webcam, or pair of AR glasses anywhere where a virtual object should be, and they will see it. The user experience is seamless, AR comes to them without them needing to “prepare” their device for it.

The Arn should be an inclusive and open platform where any number of devices can connect to, and anyone can make and host their own location-specific models or data.

It should allow people to communicate both publicly and privately, and not have their vision constantly cluttered with things they don’t want to see.

This is our vision, and we think a Wave protocol will help it become a reality.

Why Wave?

Wave allows the advantages of both real-time communication, as well as the advantages of persistent hosting of data. It is both like IRC, and like a Wiki. It allows anyone to create a Wave, and share it with anyone else. It allows Waves to be edited at the same time by many people, or used as a private reference for just one person.

These are all incredibly useful properties for any AR-experience, more so Wave is open. Anyone can make a server or client for Wave. Better yet, these servers will exchange data with each other, providing a seamless world for the user: a single login will let you browse the whole world of public waves, regardless of who’s providing or hosting the data. Wave is also quite scalable and secure: data is only exchanged when necessary, and will stay local to just one server if no one else needs to view it.

Wave allows bots to run on it and thus allowing blips in a waves to be automatically updated, created or destroyed based on any criteria the coders choose. Wave even allows the playback of all edits since the wave was created.

For all these reasons and a few more, Wave makes a great platform for AR.

How?

In basic terms, we will diverse a standard way to geolocate a bit of data and store it as a Blip within a wave.

This data could be a 3d mesh, a bit of text, or even a piece of audio.

Then various clients on various devices could logon, locate, interpret and display this data as they see fit.

Click on image above to enlarge.

A typical example of this might be holding up your phone and seeing messages written by your friends and family in the locations which they are relevant.

You could see an arrow hovering over the café your meeting a friend at, notes above their flat saying if they are in or out, or messages by shops telling you to pick up the particular brand of cereal they like.

This data would be personal to just yourself and whoever you invite to share that wave with.

Other forms of data could be public, like city-maps, online games, or historical landmarks being recreated. Custom views of the world with data for entertainment, commercial, environmental or informative purposes.

The possibilities with geolocated data are endless, as are the various ways to display and make use of them.

One of the things I’m most passionate about is people being able to see many different types of data, both public and private at the same time and from many different sources at once.

For instance, if your playing a AR game, why shouldn’t your chat window be viewable at the same time?

If you have skinned your environment with a custom view of the world, why shouldn’t you also see mapping or restaurant recommendations?

The ways to present these layers of data and toggle them on/off in the most intuitive and flexible ways would be a task for the client markers, and I’m sure we will see many innovations in those areas.

But by using Wave it at least provides the framework for having multiple information sources controlled by many different people yet accessible, and user-submittable, via the same protocol.

Who?

This idea first sprouted from a paper I route focusing on the potential for IRC to be used for AR;

http://www.lostagain.nl/testSite/projects/Arn/AR_paper.pdf

I suggested near the end Wave might be a better alternative (using Google Wave was an idea Tish Shute, Ugotrade, brought up in response to the Arn prototype design on IRC), and it quickly became apparent that Wave was a very suitable medium.

Since then, there was a lot of interest, and numerous people have offered to help.

In particular, recently, the PygoWave team is helping us out, as they have an existing server supporting c/s protocol, which is currently being actively developed.

Where?

You can join the general discussion here;
Augmented Reality Wave Development

Technical side here;
Augmented Reality Wave Framework Development

When?

There’s lots still to do, and we are at an early stage.

Our current targets: (last updated 11/12/2009)

• Getting reading/writing of prototype ARBlips to the PygoWave sever. (the PygoWave team have already made a standalone client and have the protocol for this sorted!)
• Establishing a minimal spec for ARBlips to be later expanded.
• Writing a very simple prototype online client showing how to store/retrieve the data.
• Expanding client to work for some use-cases.
• Establish a logo/branding for the project.

Other FAQs.

Where’s the catch?

While we believe Wave is highly suitable for development, it has the drawbacks of being a new system with just a few servers worldwide, which (at the time of writing this), have not yet been federated together yet.

Naturally, as a new technology, its likely to have some growing pains. And building a new technology on other new technology will multiply that somewhat. The first pain is the lack of a standard client / sever protocol. PygoWave have stepped in to the rescue a bit here, by being not just one of the most developed Wave server other then Google, but also leaping ahead with support for Json based c/s interaction. Google has stated they want community to take the lead on on a c/s protocol, so we are hoping they will adopt a Json variant, or a XMPP one and add it to the spec. We hope in much the same way as POP3/IMAP have been a standard for email server interaction, a similar one will develop for Wave.

In the meantime we plan to keep the code for writing ARBlips somewhat abstracted so as to make it easy to adapt in future.

As for the newness of Wave and other potential problems it will bring, we aren’t that worried as its built on XMPP, which has proved reliable already.

The other catch is we are unfunded, which slows development down considerable as we have to fit it around our other jobs.

I’m making my own AR Browser, and am slightly interested in maybe supporting you.

We are naturally very keen for support, and particularly for those with skills and visions to give feedback on the proposed protocol. Specifically: what do you want stored in a blip?

That’s what’s important at this stage.

We don’t see the Arn as a replacement for existing browser systems at the moment. We don’t want to restrict innovation or development in this fast developing market as we are very impressed at what’s been achieved so far. In many ways our task is small in comparison to what’s already accomplished.

However, we do believe the Arn will make a good addition to existing browser systems. It will allow users contribute data and have social features without having to worry about accounts or hosting.

It will still be quite some work to support; new GUIs will need to be developed to make it easy to submit data from the devices, as well as to login to waves.

However, we hope over time to build a set of example libs to make the read/writing of ARBlips as as easy as possible to implement in your software.

Perhaps a good way to think about it is existing AR Browsers are like word-processors, supporting the Arn will be like adding support for *.txt, but doesn’t limit what you can do with your own format.

Eventually we do hope ARBlips hosted on Wave will become the majority of AR data, and its functionality will be analogous to the internet is today. We truly believe in the long run a standard is essential.

But for now we think merely getting a baseline format established for how AR data can be communicated will increase user-ability, usefulness, and help the market grow.

Can I help?

Sure.

We particularly need people with technical skills in relevant fields. (both gwt/javascript web programming and c++(/qt)standalone programming help very welcome!).

But we also welcome people just with vision to help focus use-cases and to conceptualise what we want to be able to do with the system.

Please either join the relevant AR Waves or Wiki

We are especially interested in those with JSON and Comet experience. Specifically those with the abilities to make standalone applications to read/write to a sever using these methods.

What type of data will a AR Blip store?

This is still actively being decided, but essentially its a physical hyperlink.

A connection between a physical location (or object, see below) and a piece of data.

Specifically, we are thinking about the following fields;

Location in X,Y,Z,
Coordinate System used for the above,
Orientation,
MIMEType [the type of data stored]
DataItself [either a http link for 3d meshs and other larger data, or an inline text string if its just a comment]
DataUpdateTimestamp [so clients know if its necessary redownload]
Editors [the user/s that edited/created this blip]
ReferanceLink [data needed to tie the object at a non-fixed location, such as an image to align it to an object in realtime],
Metatags [to describe the data]

Are you purely tying stuff to fixed geolocations?

Certainly not
As part of of the spec we wish to be able for people to be able to link data to dynamically moving objects, trackable by image or other methods.

The idea being that one day someone could link a piece of text or 3d mesh to an image on a t-shirt they are wearing, or perhaps link a dynamically updating twitter feed, or perhaps provide information on a product (based on its logo).

There’s a large number of possibility’s for image-based linking alone, and that’s not even considering possibilities like linking RFIDs, or other forms of less precise but invisible binding data.

We need a lot of feedback from those companies already doing markless tracking. What types of images do you need, idly to link a mesh to an object? is one enough?

Summary of AR Wave Work to Date

Purpose: To provide an open, distributed, and universally accessible platform for augmented reality. To allow the creation of augmented reality content to be as simple as making an html page, or contributing to a wiki.

Specific Goal: To establish a method for geolocating digital data in physical space (or linking it to physical objects) using wave as a platform.

(For justification as to why we are using Wave see: our faq )

Wave as a platform

We are developing on the PyGoWave server at the moment but the goal is to be compatible with all Wave servers

PyGoWave has already achieved an important aspect in enabling the project in being a waveserver with a working and well documented server protocol. This allows both standalone and webbased clients to interface with it already.  See - The PyGoWave Qt-Based Desktop Client

This is one of the reasons why we have chosen to develop for the Pygo server at this stage.

However, the overall goal of AR Wave is to have a framework compatible with all servers using the Wave Federation Protocol. As more wave servers get c/s protocols then ARblips (the data needed to geolocate objects) could be posted and retrieved from various servers using the same client software. For this a standard should emerge. Just as websites don’t have to be hosted on specific servers, neither should AR data need to be hosted on specific wave servers.

In order to reach our goal, there are a few very achievable steps involved – see below.

Feedback

We are still actively seeking feedback, so feel free to join the Wave discussions, and see the history of how the specifications of the protocol evolved. You can also read the justification for some of the choices already made. Note a new discussion for AR DevCamp will be begin at AR Wave: AR DevCamp Session

This will, of course, only be the first draft of the specification, and it is sure to develop much in future.
The important thing now is to make working prototypes while maintaining flexibility.

So what do we need to do?

Steps :

* Establish the overall method – Done.

Each Wave will be a layer on reality which an individual or a group can create.  Each Blip in this Wave refers to either a small piece of inline data (like text) or a remote piece of larger data (like a 3D mesh) as well as the data needed to pin-point it in either relative or absolute real space.
We call these blips: ARblips. They are simply blips that stored the data necessary to augment a single object onto a specific bit reality.

It is up to the clients how they interpret and display the data. They could interpret it as a simple 2d list of nearby objects, or as an advanced 3D overlay, whereby multiple waves from different sources could to be viewed at once. What’s important is that there is a standard way to link the digital data to the real world space.

* Establishing the specification for the ARblip – In progress
We have a good idea of what’s needed to be stored in an ARblip, and we have hammered out a rough format.
The data might be stored as blip-annotations, but this has yet to be finalised.
A rough outline of the type of data stored can be seen in this c++/qt header for ARblip data can be seen at the end of this document.

* Storing and retrieving these pieces of ARblip data on the PyGo server – In progress.
The Pygowave team has made some excellent libraries that should make reading and writing data on the PyGoWave server very trivial for those with c++ skills.
This, however, is a real critical step, so more developers with C++ skills are very welcome!

* Making the above client mobile, and using a devices gps device to place the data. – Not started.
The next step would be to port the code to a mobile phone and use it’s gps-input  to post geolocated data and view what others have posted. This would be a fairly simple and not to useful app in itself. However, it would mark the first time anyone could post AR data and anyone could view it, all using open-source infrastructure.
As a bonus, because we are using wave infrastructure, the updates to any ARblip should appear in near realtime.

* To continue with the proof of concept, we would like to have simultaneous wave input from a PC
and mobile phone at the same time. – Not started.
For example, someone could post a pin on Google maps API and have that data posted to a ARBlip in a wave. Someone logged into that wave on their mobile device would then see the data posted appear.
More so we hope that when the Google map pin is dragged about, the mobile phone viewer, with just a few seconds lag, will see its location updated in real time.

We hope to make a modest yet practical app at this stage.

* After all this, we can go onto the interesting things:
3D data, camera-overlays, data fixed to objects and many more.  There’s plenty of existing software using these features (such as Wikitude, Layer) and some that are even open source software (like Gamaray and Flashkit). The open source code can give us a leg-up. However, we prefer to establish the protocol first. So naturally, these fancy features aren’t a priority for us. Rather we think our energy is better spent establishing the protocols and infrastructure so that other people can build more advanced bit of software easier.

However, once our primary goals are established, we will look to make a open source augmented reality browser ourself which will surely feature many of these features.

Overall, we hope once we have a simple proof of concept, there will be many groups, both existing and new, wanting to use this Wave system for their own apps, games and data.

Conclusion:
Really it’s now all about growing the community. We hope as soon as we show how great Wave can be for augmented reality, that lots of individuals and teams will start making their own clients to read/write geolocated data.
Overall we don’t think anything we make will be that impressive in itself. That’s not our goal.
We instead hope that our project will enable AR-content to be made as easily as web content. That games, information and apps will be able to be created without the creators having to worry
about the infrastructure behind it.

Technical information -

Current ARBlip header file

(below is a c++/qt header file for an ARBlip object that should illustrate the data being stored)

{

public:

arblip();

~arblip();

arblip(QString,QString,double,double,double,int,int,int,QString);

QString getDataAsString();

QString getEditors();

QString getRefID();

QString getXAsString();

QString getYAsString();

QString getZAsString(); bool isFaceingSprite(); 

private:

//ID reference. This would be a unique identifier for the blip. Presumably the same as Wave uses itself.

QString ReferanceID;

//Last editor(s)

QString Editors;

int PermissionFlags = 68356;  // default 664 octal = rw-rw-r–

//Location

double Xpos;   // left/right

double Ypos;   // up/down

double Zpos;  // front/back

//Orientation

// names, ranges and directions are taken from aeronautics.

// If no orientation is specified, it’s assumed to be a facing sprite.

// Roll: rotation around the front to back (z) axis. (Lean left or right.)

// range +/- 180 degrees with + values moving the objects right side down.

int Roll;

// Pitch: rotation around the left to right (x) axis. (tilt up or down)

// Range +/- 90 degrees with + values moving the objects front up. (looking up)

int Pitch;

// Yaw: rotation around the vertical (y) axis. (turn left or right.)

// range +/- 180 degrees with + values moving the objects face to its right.

int Yaw;

bool FacingSprite; //if no rotation specified, this should default to true

//if set to true when a rotation is set, then it keeps that rotation relative to the viewer

//not relative to the earth.

//Data format

QString DataMIME;

QString CordinateSystemUsed; //The co-ordinate system used. This should be a string representing a Open Geospatial Consortium standard. This could be earth-relative for gps co-ordinates, or in some cases relative to the viewer, for data to be displayed in a HUD like style.

//Data itself

QString Data;

QString DataUpdatedTimestamp; //Time the Data was updated changed

//Note; A seperate timestamp should be used for updates that dont effect the data itself.
//(such as if a 3d object moves, but its mesh isnt changed)

//Data metadata QMap<QString, QString> Metadata;

};

Mobile social communication is beginning to take center stage as the internet moves to real time communications. The recent explosion of interest in augmented reality is part of a wider concern to orchestrate a new landscape of contextually relevant information linked to location/place/time and mobile social connectedness.

The picture above, “Having an iphone has completely changed the way I poop,” is a slide from Gentry Underwood’s workshop at Web 2.0 Expo, NYC, “Social Interaction Design a Primer.”

Last month, I attended  three events starting with MoMo #13, Amsterdam, where I presented on, “The Next Wave of AR: Mobile Social Interaction, Right Here, Right Now!.  Then I caught the last two days of the Web 2.0 Expo, NYC, and finally, Real Time Crunchup SF (which I watched online).

New forms of real time mobile, social connectedness were central themes on all three occasions.

But, in terms of doing stuff that matters with mobile real time technologies, at the moment, we are still at the “hello world” demonstration (see my conversation below with Anil Dash and Mark Drapeau at Web 2.0 Expo below).

As Anil Dash noted,  “I think everybody starts with a train schedule…”

“I remember five years ago when Adrian did Chicagocrime.org. It was a revelation but I mean, that was five years ago.  And people still keep making that app over and over.”

Anil Dash announced at the Web 2.0 Expo that he will be the director of Expert Labs, a new nonprofit that will take the dot-com incubator model and apply it to new digital tools for the federal government:

“For me, in starting Expert Labs it’s been great just to tap into the desire people have to help and serve and to take the idea that you can work for your country without having to work for your government. What can you do to participate?”

The Gov 2.0 movement is attracting the best and the brightest, if you need inspiration check out Carl Malamud’s Gov 2.0 Summit presentation, By the People…..   Jennifer Pahlka is leaving her long time post as co-chair of Web 2.0 events for TechWeb to concentrate on Code for America. And Mark Drapeau is co-chair of the Government 2.0 Expo next May, that O’Reilly and TechWeb are also producing.  You can submit ideas about Gov 2.0, ICT, and cities (or other topics) to the upcoming Gov 2.0 Expo.  Mark says he will welcome them! Note there is a Free Gov 2.0 Online conf. Thursday, Dec. 10th

Tim O’Reilly has committed to Gov 2.0 work and “doing stuff that matters” with missionary zeal (see his keynote Web 2.o Expo, War for the Web).   Tim O’Reilly’s talk, also the article,  War for the Web, are a stark reminder of how the centralization and privatization of large parts of our communications infrastructure threatens the open web.  But “doing stuff that matters,” as it turns out,  is one of the best ways to win the war for the open web.

“Level playing Fields, Open access, Open APIs, Controlling our data, being able to move with it” (Anil Dash)

Slide above from Anil Dash’s presentation at the Web 2.0 Expo, NYC, “Listening to the Experts”

The Gov 2.0 movement is still in the idea and initiative phase, but the ideals and scope of the movement are a natural antidote to the fox in the social network chicken coop business model du jour (see the latest antics of Zynga).

Anil Dash notes the intrinsic bond between Gov 2.0 work and the open web:

“Because government has an inclination to creating openness by its nature. Right?  We don’t have an entirely toll system of federal highways in the states. We understand that the broadcast airwaves are a public good. And so government is inclined to think about creating public goods. It would be ridiculous to spend tax payer dollars on funding proprietary platforms.”

The Power of Government as a Platform for citizen involvement is just beginning to emerge from initiatives like Data.gov  “a collection of federal data housed on the www.data.gov Web site that’s open to public access.”

One of the most challenging aspects of creating in context mobile applications that do stuff that matters is the data curation.

Sean White, explained to me at ISMAR 2009, the challenges of data curation behind this beautiful example of augmented reality doing something that matters (pic below) -  a pollution meter, that “shows carbon monoxide levels projected over New York City.  The height of each ball reflects concentrations of the pollutant” (developed at Columbia University Graphics and User Interface Lab where Steven Feiner is Director).  Note Sean White and Steven Feiner will be at AR DevCamp NYC this weekend at The Open Planning Project office (TOPP) – see below for more information.

Open Data combined with Open Architectures of Participation are a Powerful Combination.

Scott Yates commented in his very insightful post on RT Crunchup SF that a “literny of fixes” for a broken web were “presented as  the state of the art”  in a “series of presentations from companies that have solutions that fix some subset of all the long list of annoyances” (annoyances arising from finding data and friends locked into a variety of different walled gardens).

And, Scott Yates writes:

“There have been presentations from companies who hope to be the future of socially connected communications, but not one of them has the economic or intellectual heft to be considered a true vision for the future.”

If you have been following my recent posts, you will already know that I agree with Scott Yates when he concludes: “Wave really has an opportunity to fix so much of what is broken in communications.”

I have been working on a project to create an open distributed augmented reality/mobile social communications framework based on the Wave Federation Protocol.

This Saturday Dec 5th there will be AR DevCamps held in Mountain View, New York City, Wave and Skype. There will be sessions on many aspects of open augmented reality, including Wave enabled AR.

AR DevCamp

I will attend AR DevCampNYC at the NYC location, The Open Planning Project office (TOPP) penthouse in Manhattan.  This will be an awesome opportunity to meet some of the key augmented reality thought leaders and innovators, including Sean White, Steven Feiner,  Steve Henderson, and many others (see the sign up list here).  Ohan Oda will demo the open Goblin XNA platform.   Thomas Wrobel will answer questions on writing AR Blips to PygoWave Servers and Sophia Parafina (@spara), Joe Lamantia (@mojoe) and I will be on hand to discuss the open distributed framework for AR project -  Wave enabled AR.   The PyGoWave crew will participate via skype (they will be introducing some of their latest work ).  Ori Inbar of Ogmento and Games Alfresco will lead a brainstorming session on the “Big AR NY Game”: The first location-based, social, augmented reality game designed for New York by New Yorkers.

We will continue the interesting discussion led by Marco Neumann (@neumarcx ) on the Semantic Web and Augmented Reality at the Semantic Web Meetup.  John C. Havens will introduce the Outernet Guidelines Initiative.  And Matthew Snodgrass @mattsnod, Lippe Taylor will lead a session on the future implications of AR.  Noah Zerkin, will share his brilliant work on AR software and hardware interfaces and exploring the idea of an AROS.  And Kate Chapman, from Washington, DC,  @wonderchook, and a bevy of local NYC geo geniuses, including organizer Sophia Parafina (@spara ), will explore ways to visualize government data through AR.  I am hoping we will have some projects for the upcoming Gov 2.0 Expo at http://gov2expo.com.

And there will be much, much more – keep checking and adding to the wiki. See you there!

“Hacking Human Behavior Within a City”

Picture from inspiring cities.org -shows some Amsterdam bicycle trends

At Web 2.0 Expo, Gentry Underwood, IDEO, gave a great presentation on how software changes community and communities change software from an ethnographic perspective – “Designing Web 2.0: Here Come the Anthropologists.”

And Baratunde Thurston’s,“There’s a #hashtag for That, was an inspired, brilliant romp through the “mini-grass roots movements” of hashtags - which are “quickly assembled/demolished malleable fun!” or “great ways to mess with people,” that reminded us the power of grass roots movements when it comes to “hacking human behavior.”

But my visit to MoMo #13 preceeding the Web 2.0 Expo showed me clearly “hacking human behavior within a city” is on home turf in Amsterdam, where smart phones and bicycles are the vehicles for the MoMoesque lifestyle.

Thanks to the foresight and generosity of the MoMo organizers, who make sure that the experience of  the speakers together goes beyond the few hours of the event, I had a three day, three night intensive on the future of mobile social interaction – living, thinking, and breathing mobile social connectedness, often into the wee hours, with Dennis Crowley, CEO of FourSquare (see his great MoMo 13 presentation here), Ted Morgan, SkyHook (a must see presentation on what SkyHook is doing with data), the MoMo crew, and many of Amsterdam’s enthusiastic Four Square community. 

And yes, Four Square really is an awesome way to enjoy a city and meet new people.  MIA in this particular pic are key MoMo organizers -  @samwarnaars @mdbraber and @vangeest

But what do fun times in Amsterdam and FourSquare have to do with doing stuff that matters?

Marc Fonteijn, MoMo chair and co-founder of 31Volts points out: “foursquare looks and feels like a game but what it’s actually doing is changing behavior in a playful way”

And Yuri van Geest, who co-founded not only Mobile Monday Amsterdam but also TEDx Amsterdam, added:

“in Holland we are working on using the FourSquare API for mHealth purposes also we see that smart venue owners reward all mayors/lead users/visitors with free meals/drinks/privileges/perks etc. and smart advertisers to boost their co-marketing deals based on FourSquare targeting capabilities of key influencers”

Dennis Crowley, seemingly immune to lack of sleep and jet lag, followed up his MoMo #13 talk with a presentation at Web 2.0 Expo.   I was sitting just behind Mark Drapeau, and I managed to catch up with Mark after Dennis’ talk.

Mark listed Foursquare in his big takeaways from the Web 2.0 Expo, pointing out the potential new forms of mobile social interaction have for “hacking human behavior within a city.”

“I had always been a little leery of trying FourSquare because I have a certain level of privacy I try to keep up. But listening to the CEO of Foursquare talk about it… I knew what it was. I have friends that use it.. but thinking about it as hacking human behavior within a city and social engineering of peoples’ behavior and what they can do, and really understanding what citizens are doing within cities, or other areas, and how they interact with each other.   I think could be incredibly valuable for government 2.0 and government understanding people better.”

And Anil Dash concurred:

“I think Foursquare is a good model in terms of having a game dynamic, being mobile from its default, having a great social experience, leveraging existing networks like Twitter and Facebook instead of trying to compete with them by building their own. I think those are all really, really smart leanings.

I think about if I were a government agency trying to meet those same goals, could I earn badges in Foursquare by doing things that help my community. Right? So when I volunteer at a soup kitchen is that one way to earn an exclusive badge? Is that going to earn me a discount at the bar? Those are all dynamics that we can set up very, very easily and I think that model…maybe it is a public-private partnership. That’d be great.”

Talking with Mark Drapeau and Anil Dash

Tish Shute: I was in Amsterdam speaking at MoMo#13 and I had a lot of fun hanging out with the MoMo crew and Dennis, CEO of Four Square.  I got to meet people and hang out  with Amsterdam’s new Four Square community. But unfortunately I missed the first two days of Web 2.0 Expo.

Mark Drapeau: I got here yesterday too. Yeah. So some big takeaways.

I had always been a little leery of trying FourSquare because I have a certain level of privacy I try to keep up. But listening to the CEO of Foursquare talk about it… I knew what it was. I have friends that use it but thinking about it as hacking human behavior within a city and social engineering of peoples’ behavior and what they can do, and really understanding what citizens are doing within cities, or other areas, and how they interact with each other, I think that could be incredibly valuable for government 2.0 and government understanding people better.

Also I really wanted to hear Tim O’Reilly interview Beth Noveck. I thought the most interesting thing about the interview were the questions and not the answers (also see Mark’s Posterous ).  I thought a lot of the answers were disappointing and political and vague.

But I thought Tim really got some important issues about how do people in the web 2.0 community, the audience of Web 2 Expo, interact in reality when you have a system that we nicknamed Gucci Gulch, where you have lobbyists and lawyers and special interest and councils and all these things that…developers and app builders are not really a part of.  So how do you break in?  I didn’t really hear good answers for that.

I really liked the presentation by the IBM researcher, if I can get his name. Forgive me. Ching Yun-Lin. Talking about putting a value on how many friends you have, how many connections you have and the fact that IBM can actually put a monetary value on the number of connections you have to managers. The number of email accounts you have in your inbox. Or your address book.

I thought that was just fascinating and that’s something I’m very passionate about is social networking for the sake of social networking and not merely for collaboration but making connections among diverse communities and using that to help your business or help your government agency.  Those are my big takeaways this morning.

Tish Shute: I was lucky enough to attend Gov 2.0 Summit.  I think a lot very important areas for Gov 2.0 were defined there, transparency, open data, getting developers into the public sector loop, and citizen-government interaction.  In what areas are we seeing progress and where are we stymied and why?  How do you see this Web 2.0 community connecting to the ideals and plans for action of Gov 2.0?

Mark Drapeau: I think there’s a lot of unanswered questions about Government 2.0 because there’s a lot of good talk and a lot of good ideas and initiatives but there’s still a long way to go before people in this audience, in this community who want to help the government or be a part of policy making or technology in the government can really in a meaningful way, interact with the government processes that, for the most part, are not going away.

And the people that are also part of the system, like giant contractors, they’re not going away. There’s a place for everyone. The question is how do the smaller people break in and I don’t think there are really great answers for that.

Tish Shute: What is the plan for the next Government 2.0 event?

Mark Drapeau: So part of the reason I’m here is to learn and be inspired as the co-chair of the Government 2.0 Expo next May that O’Reilly and TechWeb are also producing. And so there’s increasingly at the Web 2.0 events that they host, there are technologies and people relevant to government missions, or the public sector missions.

And so I think some of the speakers here will carry over in different ways to the Gov 2 Expo in May.

Tish Shute: Is the call for proposals for the Gov 2.0 Expo still open?

Mark Drapeau: There’s still an open call for proposals. Or people, if they know me they can talk to me directly.

(Anil Dash arrives and Mark introduces  me (Anil and I met briefly at Gov 2.0 Summit) – see Anil’s post, New York City is the Future of the Web I do agree but, of course, NYC is my hometown!).

Tish Shute: Anil you are moving into Gov 2.0 work full time now after being a key thought leader in Web 2.0.

Anil Dash: My perspective is probably unique in that I am very strongly from the Web 2.0 world, and new to the Gov 2.0 world and I think it’s telling that you can make the leap. I think that the profound thing is that these worlds are converging and it’s not where it was.

Five years ago the government technology was a bike with the training wheels on it. It was very much somebody’s old hacked up version of Drupel and crossed fingers.  And it looked a little homely and you thought, “well this looks like a run down office kind of thing.”

Now we have have institutions that have wonderful physical presences. You can’t stand in front of the Capital Building or the White House or Supreme Court and not say “that’s a majestic building.” We should have online institutions that reflect the scope and the scale of what they do.

For me, in starting Expert Labs it’s been great just to tap into the desire people have to help and serve and to take the idea that you can work for your country without having to work for your government. What can you do to participate?

Tish Shute: You and Mark had very interesting journeys  into Gov 2.0 didn’t you?

Mark Drapeau: Like the Hunter S. Thomson of Government 2.0

Tish Shute: I like that!

Anil Dash: Can you say that about yourself?

Mark Drapeau: I did the other night and people seemed to buy it, so

Anil Dash: People were feeling it..

Mark Drapeau: That’s right!

Tish Shute: And even if it’s controversial it’s good too!  I see Mark (and perhaps I am wrong with these characterizations) as coming to this via an interest in the social narratives of government and, Anil, you have come to Gov 2.0 work, as you point out, from a deep immersion in the cultures of technology and Web 2.0….

Anil Dash: And it’s also a little bit, I’ve had the privilege of seeing blogs and social media develop from the start and what I learned from it is cultural change and [not just] technology change. This is the same thing happening in government.

We’re calling it Government 2.0 and it makes it seem like it’s a version upgrade and it’s a software thing but it’s cultural change. And the interesting thing is many of the key players have a willingness to go through that cultural change, which means that the technology, therefore, has the opportunity to succeed.

Tish Shute: What did you think about Tim O’Reilly’s keynote and the warning he gave re the open web?

Anil Dash: The war for the web! He’s absolutely right. Honestly, before Expert Labs had started and I’d come on board, my initial plan for a talk at this event was exactly the topics Tim covered in the War for the Web.  That the centralization of vast parts of our communications infrastructure around privately owned, venture funded companies is a risk to innovation in some ways.

We have to make sure to set up our incentives for those companies, the Facebooks and Googles and Twitters of the world, to align with what our goals are as a society, as a culture, as entrepreneurs, and all those other goals.

So I think it’s good to have a voice like Tim’s articulating that threat and that danger so that we can respond to it. I agree completely that we are in the next phase of the battle between open and closed platforms that we went through ten years ago with AOL.

There was a time when AOL dominated more of the dial up internet, one-third of all dial-up users in the US were coming through AOL. People now say “oh, the iPhone is dominant.” The iPhone has 2 percent market share of all phones or something like that, and yet people are doing all their innovation on their platform.

Well, people used to do all their innovation on AOL’s platform and then they ended up having to rewrite it all for the open web.

This pattern is going to repeat. The choice is whether people want to encourage it or fight it or hope it goes away and ultimately there’s no great business that was built entirely within the walls of AOL’s garden. I doubt there will be a great business built entirely within the walls of Apple’s or Facebook’s or anyone else’s garden.

That’s not to say those companies couldn’t evolve to be open, I hope they do, but as it stands right now you would be foolish to bet your business either from a promotional standpoint, from a start-up standpoint, from a new technology standpoint, on any closed platform that you don’t control.

Tish Shute: I was mentioning to Mark that I thought it’s sort of ironic that we now understand how important the architecture of participation of the internet can be to government just as we are on the verge of another big battle to keep the web open…, a moment when walled gardens are seeming to dominate..will this be an obstacle for Gov 2.0?

Anil Dash: No I think actually they’ll get to skip the closed era.

You know I look at the rather famous example in India of never having landlines. They went directly to satellite phones, skipped directly to the wireless generation so they never had an old infrastructure to rip out.

I think you are going to see the same thing with government tech adoption is they are going to start in the era of recognizing the threat of closed platforms and move directly to open platforms.

Because government has an inclination to creating openness by its nature. Right? We don’t have an entirely toll system of federal highways in the states. We understand that the broadcast airwaves are a public good. And so government is inclined to think about creating public goods. It would be ridiculous to spend tax payer dollars on funding proprietary platforms.

Mark Drapeau: Universal accessibility for citizens.

Anil Dash: Right. It’s a fundamental tenant of government and we have an incredible history including the Internet itself, of embracing open standards to solve government problems in a way that helps all of society.

Tish Shute: So people who have championed open participatory architecture of the internet and open source approaches now have even is more incentive to team up with government 2.0!

Anil Dash: Yeah it is an advantage. But also, I mean candidly, open source is almost incidental to it. I mean I think we have come to the point where open source is assumed as some element of any new tech venture. It is much more about level playing fields, open access, open APIs, controlling our data, being able to move with it, that I think is key.

And I go back to that AOL example, there was a moment where they opened their email gateways to standard Internet email. And so instead of the AOL users only being able to email each other, they could email anybody on the web and this is the moment in which all the value was created. You start to have email marketing companies, and open exchanges and open mailing lists happen when anybody could email anybody else, that is the sort of thing that government catalyzed just by being the example.

Tish Shute: Mark talked about Four Square and how that could be really interesting as part of a Gov 2.0 project. But mobile has followed a course with many complications re an architectural participation – I am thinking about the control exerted by the carriers and now Apple for example?

Anil Dash: No, I think it has revealed complications that have always been there. Right? There’s always been multiple platforms. There have always been user agents and web browsers that have different capabilities. There has always been a digital divide. Mobile is making clear that those realities existed.

But I keep saying this, like, I think if I am designing an application today, you design for mobile first, for a number of reasons. One, the digital divide is much less pronounced on mobile devices. Two, you are much more likely to have an experience that scales well from a small device to a larger one than vice versa. Three, you are able to target international markets or other developing markets where mobile is the default computer platform. And you become aware of constraints in bandwidth, in accessibility, in user experience, in general experience with computers, that a lot of people in the technology industry just completely ignore.

And you know you go to Silicon Valley and people think it’s normal to have a six hundred dollar phone that has a thousand dollar a year data plan. And without blinking they designed for devices like that. It’s myopic and ridiculous to think that people can live with that level of privilege all the time on all the devices that they have and that they have a brand new computer. And so that will be its own undoing.

Right? It’s the people that are thinking about open platforms and working with any device and I think FourSquare candidly is doing a good job of this because they did start with the assumption of iPhones and this thing but their initial target audience of hipsters in the east village probably did have those. But now they have an open API, anybody can access it, that’s the right evolution. And I think they’re smart enough, that was always on their plan.

Tish Shute: But in terms of mobile social interaction we basically have really a structure all of lots of different wall gardens?

Anil Dash: For now..

Tish Shute: How do you see mobile developing more interoperability and social interaction capabilities?

Anil Dash: By using the web. I think it doesn’t have to be full-fledged Ajax-y, html applications on the phone. But if we simply rely on the capabilities of the web as it stands today instead of developing for proprietary mobile platforms we can make a lot of amazing things happen. It’s a good constraint. We should embrace our constraints.

It’s not conventional wisdom yet that mobile applications should be developed for the web. But that’ll change in the next year.

Tish Shute: There is a lot of exciting new real time technologies coming to the Web, Pubhubsubbub, Google Wave Federation Protocol. How will these change mobile development?

Anil Dash: RSS cloud. I mean there’s a ton of real time technologies that are coming out together.

Tish Shute: What are your favorites in the real time area?

Anil Dash: I wrote a post about this .. called The Push-Button Web where I actually go into this…

Tish Shute: Oh yes great post!

Anil Dash: I don’t pick a favorite. I think all of them together will work. I think it’s similar to how the web itself evolved.

We have a tangle of different related technologies that get abstracted away when you use a browser. You don’t know if it’s a gif image or a jpeg image when you browse a page. You just know it’s showing an image in line.

I think we’re going to see the same thing happen to real time web. We’re going to very, very quickly settle into a stack of technologies that let us do real time. As a developer you might have to be aware of the subtle differences. As a user your experience is going to be, “I have real time and it works on whatever device I’m on.”

Tish Shute: Mobile seems like a vital part of government 2.0 because it can connect people and their government to their context/public infrastructure/environment that is a shared concern. The open data movement has shown that being able to mash up data and get that delivered in context is a very powerful kind of technology for government 2.0. Right?

Anil Dash: I don’t know. I think that’s there’s just been the “hello world” demonstration. I think everybody starts with a train schedule…

Mark Drapeau: I was just going to say that everyone is starting with the very low hanging fruit. The transportation, the crime. It’s not exactly clear where it’s going to go but I think it’ll go –

Anil Dash: I remember five years when Adrian did Chicagocrime.org. It was a revelation but I mean, that was five years ago. And people still keep making that app over and over.

I remember at the time I had just become friends with Craig Newmark and I said, “Craig’s List should show the crime around the neighborhoods where you have an apartment listing.” And he said, “Well, if I do that then neighbourhoods that are getting better, that historically had more crime, will never improve because people won’t rent apartments there.” And he came back with that answer immediately as soon as I suggested the idea and revealed one, why Craig’s List is the success that it is. But two, what the implications are of releasing data and having to think about the social implications of that.

Mark Drapeau: Well, it’s like Gentry from IDEO said that, “Social software changes the community, which changes the software.”

Anil Dash: Right. Exactly. We have to think about the social implications of the tools and technology we create.

That means that the reason…one of the reasons we have only had these, frankly, unambitious obvious applications of open data is because the people that have had access thus far have been people that are not socially oriented. Like geeks are very inwardly focused.

Tish Shute: Oh. Okay. Well Mark’s changing this..

Anil Dash: They’re in a very insular community.

Mark Drapeau: I think there’s a number of people that are trying to change that.

Anil Dash: Yeah. It’s starting to change but I’m saying that’s why we’ve seen that symptom in the past.

Mark Drapeau: I get a lot of mileage out of the fact that I’m neither sort of a career govie type that’s getting into the 2.0 stuff. Nor am I a lifelong techie who’s getting into the government and stuff. I’m sort of…I’m interested in these anthropological, psychological, animal behavioral, ecological questions about human behavior and networking. And that’s where I kind of come into this.

Anil Dash: And I think we’re going to need an ethnographic approach to looking at how people work with this data in their real lives. People are using this data already and don’t realize it. You know, when we grab a map in an unfamiliar city you’re using government data. We just don’t think of those behaviors as doing so, and we need to understand that to build applications that really solve people’s problems.

Tish Shute: So can you speculate on the next generation you’d like to see?

Anil Dash: I think Foursquare is a good model in terms of having a game dynamic, being mobile from its default, having a great social experience, leveraging existing networks like Twitter and Facebook instead of trying to compete with them by building their own.

I think those are all really, really smart leanings. I think about if I were a government agency trying to meet those same goals, could I earn badges in Foursquare by doing things that help my community. Right? So when I volunteer at a soup kitchen is that one way to earn an exclusive badge?  Is that going to earn me a discount at the bar?  Those are all dynamics that we can set up very, very easily and I think that model…maybe it is a public-private partnership. That’d be great.

Mark Drapeau: Or even doing things to help your internal community. Key people at work or within your agency or things like that. From my vantage point it does seem like local Government 2.0 types are thinking much more about mobile than the Federal government types. The reality is government employees all have BlackBerries and they’re running around all the time. But they’re in terms of government 2.0 type stuff they’re thinking about the Dell desktop they have and the Microsoft Windows system and whenever I mention something like mobile or pervasive videos…..people aren’t really there. They’re worried about cyber security on the traditional systems. They’re worried about desktop applications on a Dell.

Anil Dash: They’re still five years ago.

Mark Drapeau: Yeah. They’re still five years ago and so I think these kind of O’Reilly-Tech Web events, Gov 2.0 Expo, Web 2.0 Expo, etc., are really starting to get at these questions that are now and not five years ago.

Click on the image below or here to watch this presentation and others from Momo13