Berners-Lee
World Healthcare Innovation and Technology (WHIT 3.0) Congress 2007

Web Past and Future

http://www.w3.org/2007/Talks/1211-whit-tbl/

Tim Berners-Lee

MIT Computer Science & Artificial Intelligence Laboratory (CSAIL)
Southampton University School of Electronics and Computer Science

World Wide Web Consortium

WHIT 3.0 2007

This talk

Pre-Web

now difficult to explain what it was like!

CERN: The European Particle Physics Laboratory

CERN from the air

CERN: Atlas Detector

The ATLAS detector - a big project

Pre-web at CERN

Need to bridge

1980: Enquire

> ENQUIRE
Enquire V 1.1

Hello!
Opening file (PSK-PCP)VAC-V1:ENQR...

PSB Vacuum Control System                    (concept)  <   O>
--- ------ ------- ------

 [ 1] described-by: Enquiry System
      An experimental system for which this is a test.

 [ 2] includes: Vacuum History System
      Records and displays slow changes in pressure.

 [ 3] includes: Vacuum equipment modules
      Perform all the hardware interface

 [ 4] includes: Control and status applications programs
      Provide operator interaction from the consoles.

 [ 5] described-by: Controle du System a Vide du Booster 11-2-80
      Operational specification of the software

 [ 6] includes: PSB Pump Surveillance System         PCP 228
      Allows rapid monitoring of pressure changes

[number      ]

Solution

1989: Web memo

Circles and arrows again...

Circles and arrows diagram

1990: WWW design

1990: Original WWW architecture

The original architecture diagram

Universality of the Web

independence of:

1991-4: Paradigm shift

Increase of 10x every year

1994: World Wide Web Consortium

good + fair + fast

Leading the web to its full potential

Care and use of the WWW

Spirit of Web design

has been the best part

2005: Mobile Web Initiative

2006: Web Science Research Initiative


(branches: Historical Roadmap Web Science)

Web essential: Layering

Net Neutrality

Internet/Web layer separation

Layers: Link

link level

Layers: Link - 2

link level

Layers: Net hides links

net level

Layers: Web sites

web level

Layers: Web hides computers

web level

Layers: Semantic Web

sem web level

Layers: Semantic Web

sem web level

Layers: Semantic Web hides documents

graph level

Layers: Semantic Web

graph2 level

Atomic relation

graph2 level

Under the hood 1: Errors

graph2 level

Under the Hood 2: Trust - Provenance

graph2 level

Otherwise: Semantic Web

graph2 level

Healthcare Applications in fact share concepts

Its like a metro, the way the lines of common concepts connect the stations of different applications

Mixture of international, national, industry and local terms

Life sciences

Venn diagram showing ontologies overlapping by certain common terms

[Diagram: Joanne Luciano, Predictive MedicineDrug discovery demo using RDF, Siderian Seamark and Oracle 10g]

Message mixes vocabulary from many cultures

Data mixing: Term by term

dc:title Data Integration and Transparency
cc:license <http://creativecommons.org/licenses/by-nc/3.0/>
dc:creator
foaf:name Tim Berners-Lee
foaf:homepage <http://ww.w3.org/People/Berners-Lee>
foaf:email <mailto:timbl@w3.org>
tk:event
dt:start 2007-06-12T09:00
dt:end 2007-06-12T10:00
dt:summary W3C-WSRI eGovernment workshop
geo:lat 38.9
geo:long -77
tk:slides <http://www.w3.org/2007/Talks/0618-egov-tbl>
tim:slideCount 12

One item may involve data from many ontologies

The tradeoff

Local Wider
Local reuse only Wider reuse
Local terms Global or shared terms
Fast Takes effort

Sematic Web views

How it works

graph2 level

The element of the Semantic Web

arrow tail, body and head are l are subject, property and value.

How it works: Everything has a URI

Don't say "colour" say <http://example.com/2002/std6#col>

The relational database

A database's row, column and cell are subject, property and value.

Semantic web includes tables,...

Arrows can make a table, an arrow from each row to each value

...trees

Arrows can make a table, an arrow from each row to each value

... everything

Arrows can make a table, an arrow from each row to each value

RDF data...

a set of circles and arrows

...merges just like that.

more circles and arrows superimposed

Subject and object node using same URIs

Software Architectures

New data applications can be built on top of RDF bus, for example:

db to sw

Components: Adapting random files

Keep your existing systems running - adapt them

db to sw

Components: Triple store

Virtual severs actually figure stuff out as well as look up data

db to sw

Adapting SQL Databases

Keep your existing systems running - adapt them

db to sw

Adapting XML

Remember- RDF on an HTTP server can always be virtual

db to sw

Adapting XML: GRDDL

Remember- RDF on an HTTP server can always be virtual

db to sw

Components: Smart servers

Virtual severs actually figure stuff out as well as look up data

db to sw

Data Bus: Standards Roadmap

architectural layers

Linked Data

Linking out is to use in your data URIs for objects as described on sites

Incentive: kudos, reuse

Data owners should - short term

  1. Take inventory
  2. Decide priorities, most likely benefits
  3. Look for existing ontologies
  4. Don't change the way data is currently managed
  5. Set up standard (RDF, SPARQL) portals onto existing data
  6. Where necessary, adapt or write new ontology bits

Data owners should - medium term

  1. Look for more connections
  2. Work towards more sharing of terms
  3. Do research on top of the widely connected data
  4. Migrate some stuff to native RDF
  5. offer and ask for feeds to/from partners

Recap of Benefits

  1. Programming at the graph level is more robust
  2. Ontologies more robust than DB,XML schemas
  3. Sem Web data integration -- standard data bus
  4. In crisis: Asking the question never asked before
  5. CXO total view of the company
  6. Give and demand data feeds in RDF/SPARQL

Thank You

W3C: w3.org

Thank you for your attention

Slides: http://www.w3.org/2007/Talks/1211-whit-tbl/