Data Portability

Here’s Talis’ very own Danny Ayers performing his song on Data Portability called “Get Your Data Out”

For those who don’t know what Danny is referring to The DataPortability movement is about ensuring the data you put into sites like Facebook or LinkedIn etc about yourself and your friends or contacts is available for you to move around between sites. This is still early days though and lot more work needs to be done before this becomes a reality but it’s encouraging that Facebook has agreed to work with the group and develop some standards.

Making Tea and the Semantic Web

Abstract. Making Tea is a design elicitation method developed specifically to
deal with situations in which (1) the designers do not share domain or artefact
knowledge with design-domain experts, (2) the processes in the space are semi-
structured and (3) the processes to be modeled can last for periods exceeding
the availability of most ethnographers. We propose a set of criteria in order to
understand why Making Tea worked. Through this criteria we also reflect upon
the relation of Making Tea to other design elicitation methods in order to pro-
pose a kind of method framework from which other designers may be assisted
in choosing elicitation methods and in developing new methods.

Download paper here, by Monica Schraefel and Alan Dix.

I periodically check up on Alan’s homepage at Lancaster University and have a read through any papers he has made available. Earlier today I found an interesting looking paper entitled: Within Bounds and Between Domains: Reflecting on Making Tea within the Context of Design Elicitation Methods – the abstract for which I have transcribed above.

Just reading the title made me smile as I recalled many an evening spent listening to Alan talking to me about an idea, or helping me understand something I was struggling with, all over a cup of tea (actually usually over several cups of tea!). I wasn’t sure what to expect from this paper, but I’m glad I read it, it proved invaluable for a number of reasons but primarily because it actually led me back to the Semantic Web, and some of the work we are doing at Talis. Whilst on the face of it this assertion might sound somewhat tenuous but maybe it isn’t … as I’ll try to illustrate briefly(ish)…

The paper describes some of the history behind an attempt by a group of computer scientists to design a digital version of a synthetic chemists lab book. However because the computer scientists were not experts in the domain or had very little experience in chemistry they struggled to understand the process that the chemists followed. Whilst they could observe the chemists doing their job and glean some information through interviewing them they simply could not understand the critical issue with reference to the lab books – when, how and why certain things were recorded and others were not. If your trying to create a digital replacement it’s absolutely imperative that you can understand what it is the user is doing and why. It’s at this point that Making Tea became so important …

In frustration, among the team of Canadian and British computer scientists and
chemists, the group made tea, a process embraced by both nations for restoring the
soul. It was at this point that the chemist-turned-software-engineer on the team said
“Making tea is much like doing an experiment.” The rest is history. The design team
took up the observation and used making tea to model the process of both carrying
out an experiment and recording it. To wit, the team’s chemist make tea multiple
times: first using well understood kitchen implements, where questions were asked
like “why did you not record that?” “You just did 20 steps to get the tea ready to pour,
yet you’ve only written down “reflux.” Why?” From kitchen implements, the team
moved to chemistry apparatus set up in the team’s design space. From there the team
moved to the chemistry lab. The results of the exchanges in these spaces informed the
design process. Indeed, they also informed the validation process: design reviews with
chemists in various positions, from researchers to managers to supervisors, were car-
ried out by making tea, and demonstrating how the artefact worked in the tea-making
experimental process. This time it was the chemists’ turn to interrupt the presentation
with questions about the artefact and their process.

The paper goes on to describe why ‘Making Tea’ worked so well as a design elicitation/validation method. I won’t provide a summary comparing it to other methodologies (you can read the paper for that) but I will summarise the four criteria that Monica and Alan identified that made it so successful in this example.

  1. Neutral Territory: Making Tea created a neutral space that was not owned by either the system designers or the domain experts – the intended users of the application. In a smiliar vain (although not exactly the same) having a neutral space you can go to to carry out design elicitation activities has proven hugely beneficial in our own experience at Talis. I have seen that removing ourselves from our offices or normal environment to spend time as part of a multi disciplinary team to focus on understanding and designing a solution to a problem both helps to focus us and place everyone on an equal footing in an alien environment. It also forces us to come together … thats important.
  2. Boundary Representation: When the problem domain is understood by both designers and users this forms a point of contact or reference that both groups feel comfortable with, and can relate to each other – it not only offered a way for domain experts to describe their tasks and activities, but also one where software engineers could offer back potential new designs
  3. Disruption: By being similar yet different from the actual process being represented, Making Tea forced the users to reflect on their tacit activities. To my mind this should be simple to appreciate for anyone who has ever pair programmed. When you constantly have someone asking you what your doing, asking you to talk through your thought processes, as disruptive as it might seem it actually forces you to reflect on what your doing. I’ve lost count of the number of times I’ll start to explain a piece of code I’m writing to someone, and then find that the actual processes of having to articulate what I’m doing reveals very quickly that I’m doing something wrong or failing to see the bigger picture.
  4. Time Compression: Making Tea reduced the time taken for a normal ex-
    periment into a period that could be completed in a participatory session
    .The net effect of this is at facilitates rapid iteration of both observation of processes and each design. This sits quite well with the Agile mantra of rapid iteration and constant feedback.

I guess I like Making Tea, this entire metaphor feels very comfortable. It also got me thinking about some of the work I’ve been doing at Talis. I’ve been spending a fair amount of time looking at ontologies to represent different kinds of knowledge. Most recently Rob and I have been looking at how to model Workflow’s in RDF … it doesn’t sound particularly tea-like yet I can’t help but think that our current efforts to try and get closer to our users and also others working in this domain is going to help us understand what we are trying to build far better than trying to be purely academic in our approach to researching this area.

Now back to the tenuous Semantic Web link I mentioned earlier. Monica is working at Southampton University on a number of their semantic web projects. She was/is the Project Lead on MyTea, which tried to re-imagine the original work that the Smart Tea Project team mentioned in the paper did in building a digital lab book. What the MyTea project attempted to do was enhance the original work by integrating the tool with Semantic Technologies and what the folks down in Southampton refer to as The Semantic Grid ( they also run an active project called myGrid which appears to bring all this together ):

The Semantic Web and Semantic Grid, however, are motivating a possible sea change in the way scientists make their work available. With the Semantic Grid, a Web-based technology for sharing data and computation, scientists can share information in richer forms than traditional lab books and publishing has allowed. They will be able to make rafts of data generated in experiments available to other scientists, and to the public for compariosn exploration and study; they can share analyses of information and collaborate in new ways.

Now I’m not sure what the current status of either of the projects is since the paper was originally written in 2005, and the sites don’t look like they have been updated in a while other than myGrid. from my perspective im interested in the work flow modelling they talk about. Yet in additon to that there is something that does touch on what we are trying to do at Talis in building a platform that facilitates this notion of a Web of Linked Data – how to find ways of enriching existing applications by providing the means to link data together in ways that have never really been possible before. We have already seen the amazing things we can do with data and applications when you fundamentally accept that what we are talking about is not a technology change as such, but rather a complete paradigm shift.

This post does feel a bit strange due to the somewhat tenuous links and a bit of tangential reasoning but it’s forcing me to reflect on something I’m struggling to articulate at the moment … but that’s not a bad thing.

Nexuiz – Wonderful FPS

A couple of months ago our Development Team here at Talis decided they wanted to have some sort of game server running internally so we could have a little fun from time to time. Most people had settled on Unreal Tournament but it had two major problems, a) you needed a semi decent graphics card to play it, and b) you had to buy it ( if ur being honest and above board which we are! ).

Anyway I came across Nexuiz, which is a free FPS based on an early Quake Engine. It requires fairly modest hardware to run, so it’s perfect for running on laptops. It also runs natively on both Windows and Mac which is excellent given a number of us have Mac Book Pro’s and I wasn’t sure if I wanted to try and run an FPS inside of VMWare although it would probably have worked. Anyway because of this we set up a Nexuiz Server running in a VM on our internal network. It runs very well, and plays incredibly well. It might not be as visually aesthetic as later versions of Quake or Doom or Enemy Territory, but what it lacks in visual polish it more than makes up for in playability … it is awesome!

Having played a few times there’s a number of things that strike me. I’ve been playing FPS games for a number of years, I even play for a great team. Now because Nexuiz is based on a Quake Engine, anyone who has ever played Quake/Doom/Enemy Territory will be immediately familiar with it. Whilst the game-play is different, as are the weapons, the damage levels and even the hit boxes, it doesn’t take too long to get used to it, or the frantic pace at which the game is played. Check out these gameplay videos…

It supports all the popular game modes, although at the moment we have it running Team Death Match pretty much all the time. it also supports a really nice little single player mode which is great to practise on, and get used to the controls and feel. I have to confess I am really beginning to like it, in a LAN setting. It’s a lot of fun, and just the thing when you need a five minute break from staring at a load of code that you have been refactoring for several hours.

Download it and try it out!

Introducing the Semantic Web Gang

Talis has a launched a new series of podcasts to add to the range currently available. This new Semantic Web Gang is a monthly show hosted by my colleague Paul Miller, and brings together a collection of experts in the field to provide their insights and discuss current news relevant to the Semantic Web.

The gang currently comprises of:

  1. Greg Boutin
  2. Mills Davis of Project 10X
  3. Tom Heath another of my colleagues at Talis
  4. Daniel Lewis of OpenLink
  5. Alex Iskold of AdaptiveBlue
  6. Thomas Tague of Reuters

It’s a great first outing for this series. The first show was very broad reaching and packed quite a lot into a relatively short amount of time but I thought it was really interesting hearing the different perspectives each of these guys brought to the discussion. I enjoyed listening to their views on whether they believe, as Tim Berners-Lee, intimated in a previous Podcast with Paul, that the Semantic Web is ready for mainstream adoption. Their views carry some weight given that these guys are some of the people at the forefront in bringing the Semantic Web vision to reality. Listen to the talk and find out what they think ;-).

You can read more about this on Paul’s Semantic Web Blog over at ZDNet, and I also think its great that ReadWriteTalk have also decided to syndicate the show here.

Well done Paul!

Apple’s Design Process

Came across this really interesting article in Business Week about Apple’s Design Process. It provides a wonderful insight into how Apple consistently create products that delight consumers. What strikes me though is that the process is, on the face of it, very simple in terms of it’s key element – there’s an important lesson there – perhaps their secret is their simplicity?  I just want to touch on three of the stages or activities described in the article:

Pixel Perfect Mockups

From my own experience, I know that producing High Fidelity wire frames or mockups can be extremely time consuming and very costly as an up-front design activity. Which is why many organisation’s don’t do this. Yet it’s hard to argue against the fact that they do remove all ambiguity and do lessen the need to correct mistakes later. We are beginning to realise the value of this at Talis, we have embarked on a couple of projects where we take this approach (although not as far as pixel perfect) up front and so far it has proven invaluable.

10 to 3 to 1

I thought this was really interesting, the notion that the develop ten entirely different mock ups of any new feature – and it really is ten different mockups, not "seven in order to make three look good" if they actually do that then that’s a remarkable. They take ten ideas, whittle those down to three which they then spend time refining until they end up with just one strong design.

Paired Design Meetings

I’m definitely in favour of this – every week the teams have two meetings. In the first meeting they do nothing but brainstorm ideas and disregard any constraints so they can think completely freely – and go crazy! Subsequently they hold a second meeting in which designers and engineers are required to nail everything down in order to figure out how each crazy idea would actually work.

These kinds of activities are incredibly useful. It’s important not to stifle or constrain the creative process which is why we have these kinds of brainstorming sessions – where nothing is considered a bad idea, no matter how ludicrous. Our development group at Talis has used techniques such as these to come up with new an innovative ideas that probably would not have come to fruition unless participants where given the freedom to go crazy (For the record Tom Heath’s ideas are generally the craziest ). The trick though is having the talent and ingenuity to take a crazy idea and turn it into something real .. and believe me it feels great when you do.

 

… if you haven’t experimented with techniques such as these then I suggest you give them a try.

Automated Testing Patterns and Smells

Wonderful tech talk by Gerard Meszaros who is a consultant specialising in agile development processes. In this particular presentation Gerard describes a number of common problems encountered when writing and running automated unit and functional tests. He describes these problems as “test smells”, and talks about their root causes. He also suggests possible solutions which he expresses as design patterns for testing. While many of the practices he talks about are directly actionable by developers or testers, it’s important to realise that many also require action from a supportive manager and/or system architect in order to be really achievable.

We use many flavours of xUnit test frameworks in our development group at Talis, and we generally follow a Test First development approach, I found this talk beneficial because many of the issues that Gerard talks about are problems we have encountered and I don’t doubt every development group out there, including ours, can benefit from the insight’s he provides.

The material he uses in his talk and many of the examples are from his book xUnit Test Patterns: Refactoring Test Code, which I’m certainly going to order.

Sir Tim Berners-Lee Talks with Talis about the Semantic Web


Sir Tim Berners-Lee, often credited as the inventor of the World Wide Web and also Director of the World Wide Web Consortium, recently chatted with my colleague Paul Miller as part of our Talking with Talis Podcast Series.

You can listen to the podcast here, or download the mp3 from here. Alternatively you can read the full transcript here.

It’s a excellent podcast which I’ll recommend to anyone who is interested in understanding the Semantic Web. It’s a far ranging discussion in which Tim talks about a number of issues ranging from the importance of Linked Data to the perceived Readiness of the Semantic Web and it’s mainstream adoption.

I thoroughly enjoyed listening to the podcast and in some ways it felt good to get the sense that as an organisation we are actually building the sorts of technologies that will help bring Tim’s vision to life.

I think… we’ve got all the pieces to be able to go ahead and do pretty much everything… you should be able to implement a huge amount of the dream, we should be able to get huge benefits from interoperability using what we’ve got. So, people are realizing it’s time to just go do it.

I totally agree with Tim, at Talis we have done exactly that, we have invested a lot of time and effort into building our Semantic Web Platform which is currently underpinning many of our next generation products. And allowing us to collaborate with others on some pretty interesting projects. The Semantic Web is fast becoming a reality and it feels pretty awesome riding this particular wave at the moment.

I’m also pretty excited at the moment Rob, Tom, Paul, Me and Chris will all be attending the LinkedData Workshop at WWW2008 next month in Beijing. Rob and I will be presenting our paper – which should be great fun.

So if any of you are out there and want to find out more about us and what we are doing come along and have a chat!

Swarm Creativity – feels like a kind of magic …

Swarm Creativity: Competitive Advantage Through Collaborative Innovation Networks by Peter Gloor is an excellent book. It introduces the concept of Collaborative Innovation Networks (COINs) – a methodology that aims to enhance quality and competitive edge. Anyone who has read The Wisdom of the Crowds or Emergent Intelligence will be familiar with some of the themes in this book, in fact it certainly does continue that tradition. According to Gloor a collaborative innovation network is a "cyberteam of self-motivated people with a collective vision, enabled by technology to collaborate in achieving an innovation by sharing ideas, information and work" – thus by extension Swarm Creativity is what results when such a group works together and exchanges ideas.

The idea of COINs are not new, in fact much of the book is devoted to providing historical examples such as Marco Polo, the Rothschilds and even the Fugger Banking empire of the German  Renaissance period. There are also much more modern examples including SHARE ( Swiss House for Advanced Research and Education ), Diamler Chrysler, , SalesForce, Intel, IBM, Deloitte, even the United Nations.

The book opens with what  I believe to be a seminal quote from Thomas W Malone  "The Future of Work", 2004:

"As managers, we need to shift our thinking from command and control to coordinate and cultivate – the best way to gain power is sometimes to give it away."

I can personally relate to this because the culture we are striving for at Talis seems to be underpinned with this kind of thinking. I don’t doubt that it feels radical to some since it does represent a departure from the bureaucratic hierarchical models of management that seem to permeate through many organisations. This new approach has many advantages though and until you experience them first hand they might seem impenetrable … in fact whilst reading the book I gained my own first hand experience of how beneficial COINs can be …

Just over five weeks ago Talis sent me, Rob, Chris, Alan and Ross away to a separate office to develop a prototype application. We were given a very short brief, in fact we had to actually define the requirements for the system ourselves. What ensued was a a couple of weeks of brainstorming, idea gathering, and then a week of wireframing and the a week of implementation, at the end of which we had a working prototype.

What wasn’t immediately apparent at the time was that this was a small COIN. The company had gathered together a small group of highly motivated individuals, presented them with a problem and asked them to come up with an innovative solution. Now during that four week period the team didn’t always agree with each other in fact we did disagree and at the beginning we probably had somewhat divergent views about what the product should be. We certainly challenged each others ideas and understanding and in doing so we slowly,  over the course of the first two weeks,  converged on a shared understanding and we then were able to very rapidly put the whole thing together. There was no hierarchy in the team, there were no prescribed roles or responsibilities, the team was very much self organising with each member of the team doing whatever needed doing without needing direction or being told to necessarily do something. Everyone, collectively, knew where we wanted to get and did whatever was required to get there. This is echoed in the book where Gloor points out similarities between creative swarms and phenomena found in nature:

"Swarm creativity is like a beehive or ant colony. It may look chaotic from the outside, but everyone has a job, knows what to do, and does it."

For me personally it was an incredible experience, both extremely challenging and also extremely rewarding. It’s amazing how much you can get done when you have a single problem to focus on without any other distractions. But as Alan observed what a collaborative effort like this does is enable even the smallest of organisations to compete with much larger organisations when it comes to innovation.

I thoroughly recommend the book!

Inspiration

Spent some time talking to my friend and colleague Ian this evening. We were talking mostly about work largely around the Talis Platform and some projects I’ve been involved in lately. We talked about problems and solutions, and how things have been recently for me personally with everything thats happened lately. Anyway during our conversation he said something that reminded me heavily of something Chomsky once said:

There are no magic answers, no miraculous methods to
overcome the problems we face,  just the familiar ones: 
honest search for understanding, education, organization,
action that raises the cost of state violence for its perpetrators 
or that lays the basis for institutional change—and the kind 
of commitment that will persist despite the temptations of 
disillusionment, despite many failures and only limited successes,
inspired by the hope of a brighter future.

                                           - Noam Chomsky

Back at the tail end of 2006, I wrote this about Ian, and it still holds true today :

Our programme lead on skywalk, Ian Davis, is probably one of the finest programme mangers I have ever worked with. Probably because he doesnt think of himself as a programme manager. He’s extremely goal driven and yet a humanist who puts the well being of his team before anything else. As a team leader he’s a pragmatist, but it’s his charm and his passion that has helped bring together bunch of talented geeks and focused them into a team in every sense of the word.

I’m grateful for the support that Ian and many of my other colleagues have given me. It occurred to me though this evening that I can be inspired by the hope of a brighter future, and I can draw that inspiration from the people I work with – like Ian, Rob, Chris, Paul, Richard, Amanda, Justin, Sarah, Dan, Sam, Malcolm, Ceri and everyone else I work with. We are all on a journey together, in more ways than one.

Thank you … all.