google – Australian Science

Interview: Henry Story, a Social Web architect and Polymath

Danica Radovanovic — Sun, 29 Jun 2014 09:40:21 +0000

Henry Story studied Analytic Philosophy at Kings College London, Computing at Imperial College, worked for AltaVista where he developed the BabelFish machine translation service, worked at Sun Microsystems on Blogging platforms and the development of the Social Web where he developed the decentralised identity and authentication protocol known as WebID, which is under standardisation at the W3C (World Wide Web Consortium). He contributed to the Atom syndication format at the IETF (The Internet Engineering Task Force), to the Linked Data Protocol at the W3C, and is currently writing an Open Source platform for co-operating systems in Scala based on all those standards.

Henry has been giving talks on the philosophy of the Social Web at the Sorbonne University, and various other places. We took a moment to have a conversation with Henry on very interesting topics – from the early years of the World Wide Web, first search engines, Semantic Web, metadata and ontologies, to the current initiatives within the Web Consortium (W3C), WebID Incubator group activities and its impact on the scientific research.

Henry in red at the OuiShare labs workshop in Paris in May 2014.

Welcome! Would you, please, tell our readers a little bit more about yourself? Where do you come from, both geographically and philosophically? What is your scientific background, and your professional scope?

Hi, thanks for inviting me over. My background is one that crosses frontiers: both geographic/national ones as well as disciplinary ones. I somehow found myself at the intersection of philosophy, logic, programming, web architecture, standards and social networks development and recently startup creation. Furthermore my work has been more and more about exactly this: how to help people co-operate across such disciplinary boundaries in a global open manner.

To help make sense of this tangle it helps to go back a little bit in time. My father is English and received his PhD in Washington DC, my mother is Austrian and a sculptor, and both lived in France where my father taught until recently political economy at the INSEAD Business school. That explains the geographical/national tangle.

INSEAD is also where I learnt computing on a DEC 2020 around 1980 as I was 13 or so. I wanted to ask the computer how to solve the Rubix cube. Of course I was told that it would not be that easy. I had to learn to communicate with the machine and learn how to ask the question. This lead me to learn the programming language Basic, and soon after that Pascal which was a revelation – no GOTO loops needing rewriting whenever a new line was added to the program – just procedures. So I wondered what could there be that was better. I discovered Lisp which made it easy to conceive of a program that could write itself, and from there the questions of Artificial Intelligence and so of philosophy started to open up.

I could see around 1984 the beginnings of the internet appear as I went to the Centre Mondial in Paris that had Lisp Machines available and connections to 4 different centres around the world.

But at the time computers were changing too quickly – I was stunned when I saw the 1984 Apple Macintosh in a shop window, and how it had left the terminal behind for just a graphical interface – so I decided to learn something which seemed more stable and took maths, physics and English literature for A levels (in the UK) and then later analytic philosophy at Kings College London, which was the philosophy that emerged out on the work by Frege and later Bertrand Russel of mathematical logic. I returned to computers to do a MSc at Imperial College later, where I learnt about Unix, Prolog, Agent Oriented Programming, Functional Programming, and Category Theory. At the time I was wondering how all this would come in useful. How would they tie up together? It turns out that in my work on building a distributed decentralised secure social web what I learnt in philosophy as well as what I learnt at Imperial College are all immensely relevant. Indeed in the last few years I have been giving talks on the philosophy of the Social Web at the Sorbonne, and various other venues that do just that.

At the time I did not know it. At Imperial College we had participated in the early stages of the Web. We were using Sun workstations, publishing web pages, and I even saw the birth of Java, the language that promised to allow one to write code that could run on every computer – a must for distributing programs on the World Wide Web. Its success was assured as it was released with Netscape Navigator in 1995. I learnt it, wrote a little Fractal Applet for my homework, put it on my web page, and flew to San Francisco to the first JavaOne conference. In the UK most job agencies had either not heard of the web, or had no access to it. But in California it was completely different. When I told a student at Berkeley about my Web page he asked me for the URL, had a look at it on the spot and suggested I go to the WestTech conference in San Jose. There were 400 tech companies there looking to employ young people – the biggest equivalent in the UK I had seen was a job fair with 40 companies. As I was about to leave a few days later I received a call from AltaVista the top search engine at the time which had indexed 50 million web pages (!) which was a lot at the time. The web was growing exponentially as every person who wrote a web page linked up to other web pages they found interesting hoping to receive perhaps a link back in return, and so make their page visible on the web. This turned every publisher into a web advocate. I went to the interview and got the job. Finally I was back in the US 28 years after I had left it as a child of 5.

This one is very interesting for those who remember the early days of World Wide Web and the first translation engines. In the 90’s you worked as a senior software engineer for AltaVista on the BabelFish machine translation service. What happened with BabelFish?

Yes, at AltaVista, Louis Monier one of the founders with Mike Burroughs, presented me with the project to adapt the Systran translation engines as a web service. Those translation machines had an old history. In the 1960s they were written in assembly code – the low level code machines understand – and had slowly been ported to C, a low level but more easily portable language which operating systems are written in. But they were not designed to be run on the biggest web service at the time, with potentially 100s of thousands or even millions of users.

As the translations were not always that good I played on this weakness by naming the machine babelfish.altavista.com, in reference to the character from the BBC Comedy Series «The Hitch Hikers Guide to the Galaxy»: a fish that when placed in a person’s ear could feed on brainwave energy and translate every known language in the universe. I pushed out a quick version, and it was immediately very successful. Then I spent a lot of time trying to write a more advanced version in Java, but the compilers at the time produced code that ran much too slowly. Finally around 1999 big speedups arrived making it competitive with C, and it was possible to launch the final version of the servers, and move up to a million or 2 translations a day.

AltaVista’s big advantage initially was Digital Equipment Corporation’s 64 bit machines, that were 10 years ahead of Intel, allowing massive and efficient indexes to be built. AltaVista started by fetching the initial pages of Yahoo a human built directory of interesting web pages, retrieving links to pages, then fetching those, and so on recursively. It would then index all the words it found allowing users to instantaneously find information on the web. Sadly AltaVista never was able to take full account of the links between the pages to help with the ranking. Google worked out how to use the information that each web page author published when he links a web page to another one, thereby voting for it in a sense. Using the collective intelligence of the World Wide Web, Google came to produce more and more relevant results, overtaking AltaVista in 2001 as the largest search destination in the World.

Furthermore AltaVista was constantly undermined by management changes. First it was bought by Compaq (which was later to be bought by HP), then it was sold to CMGI which popped in the dot com bust of 2001, was then bought by Yahoo, and finally Yahoo closed it recently. I left well before in 2000 to join a translation startup, then came back to Europe.

In the end these hand written translators were overrun by Google’s translators tuned by statistical algorithms working on massive amounts of published text available on the web or scanned from books.

Also, you’ve been working on the Semantic Web since 2004 at Sun Microsystems. Semantic Web explorations and practical implementations were so popular, what happened to Semantic Web?

Tim Berners-Lee the inventor of the Web, first spoke of the Semantic Web in 1994 at the first World Wide Web conference, as a way to enable the web to not just be a web of linked human readable pages, but also a web of linked data. As the web was a hyper-text system, so the semantic web could become a hyper-data publication platform allowing people to connect data across organisational and national boundaries.

Tim Berners Lee’s www 1994 slide on the semantic web

The first RDF standards appeared in the period 1999-2001. Blogging, one of the first applications of RDF, was started at the end of the millennium, and growing at exponential speeds. Around 2004 I had some time for myself and decided to write a blog. I found that James Gosling – the father of Java – had written and Open Source blog editor called BlogEd. I used that, fixed some bugs in it, then adapted it with a local RDF store. As a result he offered me a job at Sun Microsystems which I gladly took.

Sun Microsystems was a great company that had produced in 1981 the first colour graphical work station running Unix, the internet operating system, based on open standards that had emerged from the break up of AT&T. In 2004 Sun was emerging from the dot com bust, and was facing strong competition from Linux, the open source Unix clone developed in a distributed manner by a world wide community of engineers, which powered Google’s servers since the beginning, and was making inroad everywhere. But Sun had produced some of the best technology around, created a huge Unix and Java community. The CEO Jonathan Schwartz in a bold move had decided to move all of Sun’s code Open Source to compete with Linux. He also allowed and even encouraged us to all blog online, so that we could present a human face of what was a research focused engineering company.

What did blogging add to the web? In short it allowed everyone to publish information and let others know through a syndication feed (RSS then Atom a.k.a RFC 4287, which I contributed to) to subscribe to their updates. This allowed increasing distribution of content publication, allowing everyone to get the latest updates from their preferred authors world wide without needing to wait for the search engines to index those pages, a process which could potentially take months to reach updates, as they had to crawl the whole web for content.

Another very interesting application of the semantic web was FOAF – the Friend of a Friend ontology, put together by Dan Brickley and Libby Miller, and that was evolving in a friendly open source manner through open online discussions. FOAF allowed one to publish one’s profile on one’s web server, and link one’s profile to that of one’s friends who also published it on their web server. So just as with blogging and the web, everybody could participate in a distributed social web.

I wrote a distributed Address Book called Beatnik (take a look at this video), which made it easy to see how one could drag a FOAF profile from a web page onto the address book, and it would show you someone’s friends. You could then click on one of the friends to find their name, photo, contact information find out potentially where they currently were on the globe and follow explore their friends. All of this was totally distributed.

But at the time Facebook was starting to grow and people wanted privacy too. So the criticism I received was that this was all and good for publishing open distributed social networks but that one could not publish confidential information. To do that one needed a global identification system, so that one could connect to any web server one had never before gone to, authenticate with a global identifier, and be then given access to the resource if allowed. There was a standard for doing this that was gaining traction called OpenID, but OpenID was very slow requiring 7 http connections and required the user to type a URL in by hand. Having worked on large sites such as AltaVista this seemed to me very inefficient. I wondered if one could reduce those 7 connections down to one, while also removing the need for the user to even type anything. I asked around on the IETF mailing lists and by luck a few people answered, each one with a third of the solution. WebID was born. It allowed us to use TLS the security system used for commercial transactions on the web and built into every browser to enable authentication in one click to any web site securely using public key cryptography.

What we found was a beautiful hack to transform a system that was up to then used in a purely centralised manner, into a purely decentralised one. Usually client side certificates require one to have a certificate authority to sign the users information. This is expensive, cumbersome, not very flexible, and on the whole not even as trustworthy as it should be. WebID bypasses the certificate authority, and moves trust to the Social Web of published relations between people.

Would you explain to our readers a bit about the W3C WebID Incubator, for those in the science and technology who may not be familiar with the Incubator? Would you tell us more about your role within W3C WebID Incubator group?

We initially developed the protocol on an open mailing list called foaf-protocols. There we tested the ideas by listening to feedback from implementors from every walk of life. In a few years we had verified that this indeed could work correctly. We found the weaknesses in certain browsers and sent them bug reports. We slowly improved the description of the protocol. But as it became clear that it was workable and that we had nearly a dozen implementations we thought it would be time to go through a more formal process, and create a more formal looking document that would give people confidence in it. There the unofficial mailing list was no longer the correct venue.

Very early on I had sat down next to Tim Berners Lee to show him what we were calling at the time foaf+ssl protocol, and he immediately understood it even suggesting we use the name WebID. Tim had some of his students use it to work on developing a big picture of what this was leading to, which he called Socially Aware Cloud storage. So later when we asked him if we could have a space on the W3C to put together a standard for WebID. He approved completely. Nevertheless there are a lot of standards for identity competing for each other, and so this was a bit of a political mine field, and we settled for a low profile Incubator group status of which I am the chair.

Can you share with us some personal notes regarding the WebID Incubator, any challenges you faced along the way, and the outcome?

The beauty of WebID is its simplicity. So my role as the WebID Incubator group chair has been to try to keep it that way. I think small standards that do one thing well but that are designed to compose with other standards work best.

There was a lot of pressure by some folks who came in later to make things much more complex. Usually when one looks closer at those protocols, that complexity hides some centralising architectural presupposition, a number of security issues, or wishful thinking as to how things may work.

I did make a mistake initially by allowing myself to be argued into making WebID more general than it needed to be. It felt nice: it felt like we could have a standard that would encompass all identity systems. This is an easy mistake to make. It is one thing to design a protocol to make it easy to generalise, but it is another one to make it so general that it is difficult to implement. And initially what is needed is to keep it simple and clear so that implementors can follow a spec to write an implementation that works. Vendors often have an opposite need in that the more complexity they can manage the more they can distinguish themselves (they can tick more boxes on their software features set). This is where the rough consensus and working code mottos of the IETF and the W3C are key. A standard comes from having interoperable implementations written by different organisations that may not even know of each other’s existence. If nobody can implement the full standard, then it is not well specified enough.

So under the good advice of Tim Berners-Lee a couple of years ago we decided to return back to the roots and create two specs, one that defines what a WebID is independently of authentication, and another that defines the WebID over TLS authentication. This means that we can get WebID to work with potentially other authentication mechanisms such as BrowserID (now called Mozilla Persona) that was a rising star a few years ago, but has run into trouble because it only had the promise of being decentralised sometime in the future, perhaps….

It now ties in very nicely with a number of emerging standards at the W3C such as:

•The Linked Data Protocol: is a standard to turn the web into a read/write web that has been Tim Berners-Lee’s ambition since the beginning. It takes the best of WebDAV and the Atom protocols that came before it, but simplifies them by integrating them in the semantic web. The Linked Data Protocol is being worked on by IBM, Oracle, Fujitsu, and a number of other companies. I represent Apache there, and probably had one of the first implementations of it, which I worked on with Alexandre Bertails of the W3C that was part of a proof of concept that led to the formation of the Working Group.

•Web Access Control: is a simple ontology and a pattern of linking a resource to it so that a client can (if allowed to) work out who has access to a resource and edit (using LDP) the access control rules which are themselves expressed in RDF. Authentication can be done with WebID over TLS, or other methods. This is still just a wiki page but it has a number of implementations.

Finally, what are you currently working on? Where do you see this leading to? How do you see this impacting the scientific research?

We have now the standards to build a platform for distributed creation, edition, and protection of any kind of information resource be it textual, image, video or data on the web, in way to allow the whole world to connect in ways only dreamed of until now. This of course opens up huge spaces of possibilities in every field.

We have built an implementation of this in Scala, a very interesting programming language that compiles to Java byte code or to JavaScript (with Scala-JS), available under an Apache licence on the read-write-web GitHub repository.

Scala is multi-paradigm programming language that mixes Object Oriented and Functional concepts, which in a world where Moore’s law can only continue progressing through parallelization is becoming essential. Consider that Sun’s latest CPU the T5 cpu contains 16 cores for a maximum of 128 threads per processor, for a total of 1024 on an 8 socket system. Old style Object Oriented programming with mutable objects requires complex systems of locks that are prone to dead-locks. Here mathematical programming which is what functional programming is all about is the cure. By working with non mutable data structures (objects) in a functional way that composes – hence the importance of Category Theory which is the study of such composability – one can guarantee that code can be parallelised.

With the advent of LDP+WAC+WEBID we now not only have paralellisation inside one CPU but now across organisations, where our servers potentially have to communicate constantly with 1000s of other servers. Here again the functional nature of Scala makes asynchronous programming vastly more efficient than traditional thread based programming, saving GB of RAM just to process connections on the internet.

With the advent of Scala-JS we can now envisage writing code that works inside the web browser as well as on the server. So we have now come to build a fully distributed agent platform with declarative and inferential semantics (RDF), speech/document acts (LDP) powered by functional programming languages, bringing together all the fields that I had studied twenty years ago at Imperial College in London.

This platform will allow researchers to connect up seamlessly, link up different data sets together, tie articles to the data sets they were based on, link research up with enterprises, banks, governments and individuals in a seamless manner, whilst still always allowing divergence of opinion and subjectivity to remain, and without the very real danger of polical/economic control that centralised networks present.

The big project is now to re-build all the tools that we have to work with this platform, to create easy user interfaces that need to be aware of the subjectivity of information, so as to allow anybody to always ask about any piece of information: where did this come from? Who said it? What was it the logical consequence of? It should be possible to take different points of views on data: skeptical, trusting, etc… to see what kinds of possibilities are entailed by it.

At present we are busy building a platform for co-operating systems using all the above mentioned standards and tools. The platform is open allowing students, researchers or anyone else to join us on the read-write-web project. We are already working with non-profit organisations such as the French Virtual Assembly that are connecting a number of non profit actors in a network based on a concept they call ‘pair to pair’ where pair stands for project actor idea resource.

Thank you Henry for taking your time to talk with me. Thank you for the Interview!

For more information check out a web site of Henry Story, his Academia.edu page, and you can follow his Twitter feed – Bblfish.

Image sources:

discussing how to create a wish list to our #RDF linked profiles #OSLabs14 #OSFest14 pic.twitter.com/JDFU4i6J32

— Joachim Lohkamp (@JockelLohkamp) May 3, 2014

TBL+13: If everybody did it it would be awesome

http://www.w3.org/2005/Incubator/webid/spec/identity/

test

The post Interview: Henry Story, a Social Web architect and Polymath appeared first on Australian Science.

Weekly Science Picks

Kelly Burnes — Sun, 14 Apr 2013 16:29:34 +0000

DNA

This edition of weekly science picks is going to be a little different… it’s a smorgasbord of intriguing facts ranging from corporate ownership of our DNA to recycling building materials. Let’s get started.

This first story represents the line between scientific research and corporate profits that sometimes leaves the ethical, human components as an afterthought. Hopefully on Monday, 15 April, the US Supreme Court rectifies this when they hear oral arguments on a case concerning the patent of human genes.

The Supreme Court should invalidate the patent on human DNA by Jeffrey A. Rosenfeld and Christopher E. Mason

Today, Salk would be shocked to find that your DNA belongs not to you but rather to many companies and institutions that have patents on the DNA from your cells. Forty-one percent of the genes in your genome are not legally yours, according to a long list of gene patents that have been granted since the 1980s. These patents cover thousands of human genes and restrict a doctor’s ability to look at your DNA and plan your medical treatment. These patent claims contradict an intuitive sense that your DNA is no less yours than your lungs or kidneys.

As if Google wasn’t involved in our daily lives enough, they want to be their in death too. Don’t get me wrong, Google is great, I use their products every day. Although this story is a little creepy to think about, where to store or what happens with all that data we create while alive and breathing, is important.

Google Lets You Manage Your Digital Life From Beyond the Grave by Roberto Baldwin

Google announced today that users of its myriad digital services can control how their data is handled while they’re taking a dirt nap.

If you’re fascinated by buildings and building materials, you’ll enjoy this next story I came across on Arup’s website. Arup is a design, planning, and engineering firm with offices around the globe. (They designed and engineered the Sydney Opera House.)

Resources / The hidden assets of building by Mark Bowers

Take glass, for example. Glass from buildings is not widely recycled because it’s not as straightforward as taking empty bottles to the bottle bank. There are issues such as contamination from silicone sealants to consider, for example. But when Arup worked on refurbishing the Lloyd’s of London building, we showed it could be done.

And the last pick for this week is an update on another legal case soon to be heard in The Hague. The UN Court will hear oral arguments from representatives of both Australia and Japan over the Japanese whale research programme in Antarctica. The case is scheduled for 26 June to 16 July.

Australia to face Japan over whaling in UN Court by BBC News

“Australia will now have its day in court to establish, once and for all, that Japan’s whaling hunt is not for scientific purposes and is against international law,” Australia’s attorney-general, Mark Dreyfus, said.

Cite this article:
Burnes K (2013-04-14 16:29:34). Weekly Science Picks. Australian Science. Retrieved: Aug 25, 2026, from https://australianscience.com.au/news/weekly-science-picks-26/

test

The post Weekly Science Picks appeared first on Australian Science.

Weekly Science Picks

Kelly Burnes — Sun, 13 Jan 2013 18:52:46 +0000

I’ve just returned from a fantastic holiday in Australia (sad I had to leave). The great thing about travel is that it opens your mind and exposes your senses – elevates it to a higher level of thinking, thinking that is clear and uninterrupted. The not so great thing about travelling to far away places is the resulting jet lag…that can lead to not so clear and uninterrupted bouts of thinking at 3AM. What follows is a hodgepodge of the collection of science stories I encountered over the past week.

This first article opens up a much-needed debate on the policy of biodiversity and species preservation. Whether it is rhinos, right whales, snow leopards, I think it’s time we had a conversation on how present day society moves forward with species interaction.

Rhino poaching in South Africa reaches record levels by Matt McGrath

“Rhinos are being illegally killed, their horns hacked off and the animals left to bleed to death,” says Traffic’s director of advocacy Sabri Zain, “all for the frivolous use of their horns as a hangover cure.”

While in Brisbane, I had the great pleasure to meet with the director of Australian Science, Dan Petrovic. We had an hour-long conversation about artificial intelligence. I’m not sure how much interaction I want with my search engine in the future, but the beauty of his story is in the intricate details and the possibilities that may soon be reality. This story technically wasn’t from last week, but that is when I read it. So if you haven’t given it a read, sit yourself down with a cup of coffee or tea and do so. We would love to host a Google+ hangout and get some reader feedback on this topic.

Conversations with Google by Dan Petrovic

This article explores the future of human-computer interaction and proposes how search engines will learn and interact with their users in the future.

I love science. How did I not know about io9? No idea. But thank goodness I have added it to my weekly reading list. (Thanks Dan!) This next story is about humour more than anything. And in science, a sense of humour is an important character trait to have. The U.S. may not be building a Death Star, but kudos to them for the response and taking the opportunity to highlight STEM. My nieces in Ohio are hard at work on building the Lego Death Star they received from Santa. So in a way, the U.S. is getting a Death Star and two aspiring scientists. Maybe thousands!

The White House will not build a Death Star, tells us in hilariously geeky fashion by Lauren Davis

If you do pursue a career in a science, technology, engineering or math-related field, the Force will be with us! Remember, the Death Star’s power to destroy a planet, or even a whole star system, is insignificant next to the power of the Force. – Response from Paul Shawcross, Chief of the Science and Space Branch at the White House Office of Management and Budget

Apparently Shell experienced an incident with its Arctic drilling on New Year’s Eve, with no catastrophic consequences. Arctic drilling seems like a horror movie. You’re sitting on the couch watching TV, the music is loudening, suspense is growing, you know something bad is about to happen at any second…

An energy analyst from the Brookings Institution mentions in the article that oil and gas companies don’t have a choice when it comes to Arctic exploration and drilling. In order to remain competitive, they have to go up there.

In Kulluk’s Wake, Deeper Debate Roils on Arctic Drilling by Traci Watson

Fortunately for the energy industry, the Arctic has become more hospitable to drilling just as other locations have become more hostile. The Arctic sea ice melted away to a record low in 2012, according to the U.S. National Oceanic and Atmospheric Administration, spelling easier access for drill ships, though melting ice also brings new problems.

Fortunate. Back to the drawing board. So many plans and policies, so little time.

As always, stay thirsty for knowledge.

Cite this article:
Burnes K (2013-01-13 18:52:46). Weekly Science Picks. Australian Science. Retrieved: Aug 25, 2026, from https://australianscience.com.au/news/weekly-science-picks-16/

test

The post Weekly Science Picks appeared first on Australian Science.

Predicting the next epidemic

Charles Ebikeme — Wed, 02 Jan 2013 00:15:21 +0000

In some parts of this world the rains predict disease, and a hot, dry, dusty wind is the harbinger of a meningitis outbreak that is yet to come. Now, from where you sit, Google will soon predict the next great epidemic.

At this time of year, ever since that 2009 paper was published on flu trends, seasonal influenza and how we predict it, is a recurring topic.

It seems we are always moments away from the next great flu epidemic. This year saw a novel coronavirus make the rounds. A virus that usually causes nothing more serious and common than a cold, was the source of severe respiratory illnesses in the Middle East, with reported cases coming from Qatar, Saudi Arabia and Jordan, and resulting in 5 fatalities.

The curious case of the novel coronavirus is a new strain of virus that has not been previously identified in humans. The hypothesis is that it jumped the species barrier, but, as of yet, a definitive origin has not been identified.

When a disease will decide to jump the species barrier is hard to predict. Some of the most serious afflictions of humans in recent times have had their origin in animal diseases. HIV/AIDS and ebola being the prime example. Seasonal influenza is another — causing tens of millions of respiratory illnesses and up to half a million deaths worldwide each year.

In mankind’s eternal struggle against disease, as the adage goes, prevention is better than a cure. But how do we prevent disease? How do we mitigate for an oncoming plague or pestilence? A part of this prevention is predicting it.

Currently, we can only really predict an epidemic when it is currently in motion. Hospitalizations are the only way we can really track a disease. When it is possibly already too late. When people are already sick.

In the week the world was supposed to end, the European Centre for Disease Control (ECDC) released its weekly report on influenza surveillance, like it had done since week 40 of this year. The report aggregates data on influenza-like illnesses reported in primary health care facilities, as well as virological and clinical data.

Flu surveillance, in Europe and similarly in the US, is based on nationally organised sentinel networks of physicians, mostly general practitioners (the first person you go see when you’re ill), covering at least 1 to 5% of the population in their countries. Each sentinel physician reports the weekly number of patients seen with influenza-like illnesses and acute respiratory illnesses.

The report is essentially there to tell us when a flu epidemic is going to break out. In week 49, ECDC announced that the season of influenza transmission had begun.

Along with the direct methods of detecting and monitoring disease, in recent years new and innovative non-direct methods have been tested. From sales of over-the-counter medication to online activity. The idea is to try and record health-seeking behaviour… ie before the disease has taken hold in a population.

Emergency hospital during influenza epidemic, Camp Funston, Kansas.

Monitoring disease, 140 characters at a time…

Flu is a disease very amenable to being searched and turning up in social media. Health-seeking behaviour — in this day and age, we google every ailment. However, diseases which are more serious probably won’t follow this social pattern.

The concept is essentially trying to “predict the present

test

The post Predicting the next epidemic appeared first on Australian Science.

Networking the Solar System

Markus — Wed, 13 Jun 2012 09:33:22 +0000

When the human race inevitably expands off planet Earth, we’ll naturally want to take our internet with us – over the past 15 years or so, the internet really has become an integral part of our lives! In fact, even as you’re reading this, 300 gigawatts of electricity worldwide will have been used to transfer 640 terabytes of information across the internet to 1.5 billion desktop computers and a further billion mobile devices. In the time you’ve taken to read this paragraph, over 200 million e-mails have been sent, 6 million Facebook pages have been loaded, 1.3 million YouTube videos have been watched, and 100,000 people have posted an update to their twitter accounts.

Astronaut Tracy Caldwell Dyson enjoying a view from the ISS Cupola window.

Inspite of its sprawling extent on our planet though, the internet’s first step off-world was able to fit inside just 1120 bytes. On January 22, back in 2010, astronaut TJ Creamer made a small but important piece of internet history by being the first human being ever to post to a twitter feed from orbit. Astronauts had been updating twitter feeds while in orbit for some time, but they had previously always relayed their messages via NASA back here on Earth. Since 2010, however, the International Space Station (ISS) has been upgraded to have its own internet connection. Intended for personal use by astronauts and still routed through ground based systems at NASA for security, this is how e-mails, blog posts and twitter updates are sent back home. All the same, even though it might seem a long way away, the ISS is relatively nearby in low Earth orbit.

Things start to become more complicated when you consider travelling further afield, because whether we like it or not, we can’t cheat special relativity. The speed of light is the fastest any interplanetary communication (or anything, for that matter) can travel. The Moon is still close enough that interaction is possible in almost real time. Sending a message to someone on the Moon would involve a delay of a little under three seconds. Good enough to hold a conversation, but with gamers here on Earth complaining about latencies higher than 600 milliseconds, you’re obviously not going to be able to play Halo or Warcraft against a friend over that kind of distance. Travel as far as Mars and the problem becomes even more pronounced, with delays of anywhere between 3 and 22 minutes, depending on exactly where Mars is in relation to Earth. Minutes turn to hours as you continue to travel outwards (transmissions from Voyager 2 currently take over 13 hours to reach us). All things considered, using an interplanetary internet sounds like a rather good idea for communication over distances like these. While phonecalls to Mars would be essentially impossible, delays between responses to e-mails and tweets are fairly routine. You could quite easily have a twitter conversation with someone over on a neighbouring planet.

Preparing for the future, NASA and Google teamed up a few years ago to develop a new internet protocol designed to be used in space. Called Disruption-Tolerant Networking (DTN), it’s designed to work a bit differently to the internet we’re all familiar with. While our familiar TCP/IP systems rely on a constant connection to transfer data, this is obviously unfeasible in deep space. While a DTN network would still operate using a series of nodes passing information from machine to machine, the way ground-based networks do, each node needs to hold onto the data being transmitted until it has a confirmation that the message has been safely passed on.

SpaceX believe it should be possible to send people to Mars within 20 years.

With a steadily accumulating collection of spacecraft in various parts of the solar system. Google’s Vint Cerf has expressed plans to use these old pieces of hardware, many of which have long since completed their original missions, as nodes in what will become an interplanetary internet. Indeed, spacecraft have already transmitted data amongst themselves en route back to Earth. ESA’s Mars Express probe, for instance, has served as a relay between Earth and vehicles landing on Mars, and is set to do so again when NASA’s Curiosity rover arrives at the red planet later this year. In an interview with networkworld.com last year, Cerf is quoted as saying “…if they are still functionally operable — they have power, computer, communications — they can become nodes in an interplanetary backbone. So what can happen over time, is that we can literally grow an interplanetary network that can support both man and robotic exploration.” He continued to explain how, while all space missions to date have involved point-to-point communications, future space missions will likely require “a richer communications network.” This also has an added plus that an interplanetary network infrastructure will allow scientists to receive more data from deep space missions than is currently possible.

With many astronauts already maintaining active twitter feeds from orbit, it has to be said that similar social networks may well play an important role in communications in the future. By the time that role is needed, a network infrastructure will likely be in place for it to operate on. A company like Google, processing petabytes of data and serving hundreds of millions of queries for an index containing billions of websites every day, is certainly qualified to help set up a computer network on interplanetary scales. Maybe in the future when people talk about Google Mars, they might mean it literally!

Image credits: NASA/Tracy Caldwell Dyson (top), SpaceX (bottom)

Cite this article:
Hammonds M (2012-06-13 09:33:22). Networking the Solar System. Australian Science. Retrieved: Aug 25, 2026, from https://australianscience.com.au/space/networking-the-solar-system/

test

The post Networking the Solar System appeared first on Australian Science.

Measuring Network Performance with M-Lab

Editorial Board — Wed, 30 May 2012 07:00:35 +0000

Measurement Lab is an open platform for researchers to deploy Internet measurement tools. By enhancing Internet transparency, M-Lab helps sustain a healthy, innovative Internet. What this explanatory video to learn why M-Lab is important to researchers, network engineers and policy makers. M-Lab is a collaborative effort founded in 2009 by Googler Vint Cerf and a number of network researchers and industry partners, including Google.

M-Lab’s goal is to provide researchers, consumers, policymakers, and anyone else who wants good, intelligible information about the Internet, with open data about network performance.

The nuts and bolts of M-Lab start with a widely-distributed server platform maintained and managed by the M-Lab Collaborative. These servers are purpose-built to support broadband measurement, and are consistently deployed to exact specifications. This means that the data they collect is consistent — important when you’re contrasting global network performance. Researchers host open-source, active broadband measurement tools on these servers, and users access these tools, run tests, and get real-time information on their network performance. Each time a user runs a test (about 200,000 times a day), data is collected and put into the public domain. So far, it’s 516 terabytes and growing.

M-Lab is a head-to-tail solution for high quality, open data. And the best part is that it’s all open. From the testing methodology described in the open source code of the tools, to the server documentation, to the data collected, scientists and others can vet exactly what is being measured, how it’s measured, and what precisely this says about networks and performance. M-Lab’s momentum is generated by working together from a shared source of data to progress the state of networks.

Source.

test

The post Measuring Network Performance with M-Lab appeared first on Australian Science.

Google Gets an Upgrade

Dan — Mon, 30 Jan 2012 09:05:24 +0000

According to Google’s Grzegorz Czajkowski, many of the things people are involved in can be represented in the form of graph, including professional activities and personal relationships. The company was the first to use advanced graph analysis methods like PageRank to get more from the Web.

Using graphs in a dynamic environment like the society brings a new angle to computational power and scalability. Google applies the Bulk Synchronous Parallel Model in its scalable graph analysis by using a framework known as Pregel. Pregel simplifies the calculation of PageRank and scales clusters autonomously without requiring programmers to intervene manually. As a result, the software engineers have more time to concentrate on the algorithm itself.

The Basics of PageRank

PageRank uses the random suffer model that assumes that Web surfers use a linear method when following links until their interests stop or they stop browsing. All the clicks away from the source documents reduce the PageRank. Of course, the actual process is more complex, with the typical value of PageRank dampening being 0.15.

The entire Web can be treated like a graph, where all the pages and index-able files are regarded as ‘vertices’ and the links as ‘edges.’
The vertices are usually initialised with starting values that, interestingly, make no major influence on the end-result. Pregel runs
through a series of super-steps after initialisation by updating values and sending messages to other vertices.

Related Frameworks and Methodologies

According to Bill Slawski of SEO by the Sea, there’s more behind Pregel and Google, which uses other techniques like FlumeJava and Dremel. The company uses Pregel because it is ‘expressive’ and easy to program.
Software engineers have designed their own frameworks and toolkits, especially when dealing with multi-step graph operations.

Characteristics and Benefits of Dremel

Nested data

Interactive speed

Trillion-record, multi-terabyte datasets

Columnar processing and storage

Aggregation tree architecture

Spam analysis

Analysing crawled Web documents

In situ data access

Crash reporting for Google Products

OCR results from Google Books

Tracking the install of Android Market apps

Resource monitoring for work run in Google’s data centres

Debugging map tiles on Google Maps

FlumeJava

Google users started using FlumeJava in May 2009. It is simpler than MapReduce and can control executor and optimizer if necessary. Hundreds of people use pipelines with processing capacities ranging from gigabytes to petabytes every month.
Google employs interchangeable tools and systems that multiple groups can use.

References:

http://arxiv.org/abs/1201.2261
http://arxiv.org/ftp/arxiv/papers/1201/1201.2261.pdf
http://arxiv.org/a/petrovic_d_1

test

The post Google Gets an Upgrade appeared first on Australian Science.