Last Friday I ventured north to Nottingham, along with Ed Parsons, Steven Feldman and Muki Haklay to attend the one day Supporting the Contextual Footprint event run by the Horizon Digital Economy Research institute at the University of Nottingham. Along the way I discovered a manner of tracking my journey that I’d hadn’t previously considered, but that’s covered in a previous blog post.
The focus of the Horizon event was to discuss the infrastructure needed to support location in its role as a key context and to identify any research theme that came out of the discussions; a classic case of the ill defined and fuzzy interface between the commercial world and that of academia.
The day was split into three thematic tracks:
- The Location Challenge
- What are the challenges specific to the capture and management of location data?
- What is the state-of-the-art in the technologies available to store, query and present location data?
- How do we understand location in context, especially in real-time, on the move?
- Whose Data Is It Anyway?
- What data should be considered “personal”?
- Should I “own” data about me, such as where I am, my home electricity usage, my bank transactions?
- How can users be enabled and encouraged to manage this data?
- What technologies are available to do this?
- How, when and by whom should “personal” data be exploited?
- What checks and balances should be in place to protect all stakeholders, including both citizens and service innovators?
- Can Crowds Be Authoritative?
- Crowd sourcing is a powerful technique for data collection enabled by modern handheld devices, but how far can user-contributed data be trusted?
- What are the processes required in order to meld crowd-sourced data with existing, authoritative, datasets?
- What are the legal implications of generating, combining and using such user-generated datasets?
- For example, what environmental details could citizen sensors collect?
- How might this change our understanding of the live state of the world?
The location challenge session was a basic introduction to geo and to location, just to get everyone on the same page. A small wry cheer from myself and Ed was caused by the mention of slippy maps after half an hour of pure GIS but the session was also notable for reminding us that GPS isn’t just the domain of the US NAVSTAR system, though it’s the one we’re most familiar with and which is considered pretty much synonymous with GPS (the Wikipedia entry for GPS redirects to the NAVSTAR entry). But there’s also the Russian GLONASS, the Chinese COMPASS and the European Galileo systems chafing at the heels of NAVSTAR and threatening it’s hegemony. We also touched on the accuracy of satellite navigation systems, ranging from the fictitious, with Dan Brown asserting that “(GPS) is accurate within 2 feet anywhere in the world”, even when in the toilet in the Louvre, to the technically feasible, with accuracy of 1 cm being touted as possible. Though no one in the room was able to articulate precisely what use 1 cm GPS accuracy would be.
The low point of the session was a rambling and tedious sales pitch from Oracle which can be summarised concisely as “there’s an explosion of (geographic) data coming, you need to buy our (highly priced) servers in order to cope with it”. It’s a shame no-one’s told Flickr about the need for Oracle servers as they’ve been making MySQL and commodity Linux servers cope with an explosion of data for a while now.
The high point of the session was a (rather hip looking) Doctor who’s name escaped me who’d managed to do something that eludes many commercial concerns. They’d managed to put together a prototype, intelligent car pooling and routing service, complete with web, mobile and SMS interfaces, together in just a few weeks. Oh and it worked as well; this was not only deeply impressive but illustrated the positive social and community facet of this thing we call location.
An an erstwhile privacy nerd, the session on whose data is it anyway? was fascinating, defining and categorising a whole range of what can be considered personal data:
- access data (name, address, phone number)
- direct data (photos)
- intrinsic data (fingerprint, genome)
- state data (location, activities)
- transactional data (finance, journeys, purchases)
- interaction data (things I say and do)
- indirect observation data (energy usage)
- things I create data (emails, texts, documents, photos)
- things I’m given data (emails, texts, documents, photos)
- things I’ve seen data (documents, tweets, locations)
With all of this data being out there, in a variety of data sinks, both personal, governmental and commercial, the concept of a distributed, durable, scalable and trusted personal data store was floated as a theoretical solution; much emphasis should be placed on the word theoretical by the way. A worthy theoretical concept, the notion of if you need to know about me, ask my PDS, is alas one that the majority of the audience who hail from a commercial background, view as interesting but flawed and not viable in the real world.
The high point of the session was a recommendation to read Paul Ohm’s Broken Promises of Privacy; the low point the need to Lynne Truss to visit the room unannounced to pounce on the person who thought that “Who’s Data is it Anyway?” was acceptable for a title slide.
The final can clouds be authoritative session started aptly withe a quote from Wikipedia and paired Muki Haklay from University College London against Glen Hart from the Ordnance Survey. Whilst the pairing may have been unintentional, following a strong proponent of the crowd sourced OpenStreetMap with a pointed, if tongue in cheek, talk from the OS made comparisons difficult to avoid. Stephen Feldman’s write up of the day has more insight on this final session and is well worth a read.
Acronym of the day goes to BHP, which left the audience looking perplexed until it was revealed as a Bloody Hard Problem. Days like this are essential to draw academia away from a pure research perspective and to get representatives of commercial organisations and academia talking on common ground … that in itself is a BHP which Horizon goes a long way towards solving.