Tabulator people

Tim Berners-Lee

Tim coded up the original version at odd times in November and December 2005. See Links on the Semantic Web from Dec 2005

Undergraduate Research Opportunity Program (UROP) over June-August 2006:

Yushin Chen

"Joyce" wrote the calendar views, and incorporated the Simle timeline.

Lydia Chilton

Lydia is working on statistical analysis, charts, etc.

Ruth Dhanaraj

Ruth worked on the Tabulator in January 2006, adding the asynchronous fetching of documents during queries, etc.

Adam Lerer

Adam works on the back-end -- the query system, and generic stuff around the query UI. He implemented SPARQL protocol as a internal layer and as an external protocol.

Jim Hollenbach

Jim is responsible for the map view. He also worked on the framework for multiple queries per view.

David Sheets

David wrote the RDF parser, and does a lot of architecture and release engineering. He also installed the bug tracker.

Thanks also to Dan Connolly and Ralph Swick for co-supervising students and for ideas, support, testing and encouragement. In collaboration with Nokia under the SwapMe project. Thanks to MIT UROP funding, CSAIL UROP funding, and DIG funding.

Features

(All addressed in detail later)

• Does GRDDL and link rel=meta on xHTML pages
• RDF/XML parser (not complete), no N3 yet
• Smush on owl:sameAs, [inverse]FunctionalProperty
• Display with subproperties of rdfs:label
• Load all ontologies (recursively)
• Load data on browse in outline view
• Load data as query binds new URIs
• Provenance: click on any fact -> highlight source in list
• Provenance: double-click on source -> look at source meta inc.

When you use these techniques on the server, the tabulator works better.
We will cover most of these in more details.

AJAR Library

• Fully tested RDF/XML parser
• Indexed triple store
• Asynchronous query engine
• SPARQL client and server (limited)
• Smushes identical nodes (owl:sameAs, owl:InverseFunctionalProperty, owl:FunctionalProperty)
• Looks up data
• Tracks history if HTTP results

Lookup Algorithm

Conventions - should the whole set be a standard?

• What to look up?
  • document from URI (up to #)
  • link rel=meta
  • rdfs:seeAlso links
• Follows 303 redirection
• Content-type is definitive
  • Text/plain: Guess with a warning
  • application/rdf+xml Parse as RDF/XML
  • text/rdf+n3 Parse as N3 (*not imp.)
  • text/html
    • link rel=meta in HTML
    • GRDDL profile
    • RDF/a ??
  • *+xml*:
    • GRDDL profile

Internals

Example

More Information

• This presentation : http://dig.csail.mit.edu/2007/Talks/0108-tab-tbl/

This work is licensed under a Creative Commons Attribution - Non-Commercial - No Derivatives 2.5 License.