Member comment
The idea of semantic lenses is all about having a flexible way to present recovery.gov data. Suppose recovery.gov collects data on an (imagined) recovery project involving restoration efforts in our National Parks.
With a traditional approach, information about the money spent on this project would be made available via a user interface designed by recovery.gov itself. Maybe there would be a table showing how much money each National Park was getting.
Now suppose a visitor wants to instead plot this information on a map, or see a view that mashes up the National Parks spending with other stimulus funds spent by the Department of the Interior. The idea of semantic lenses is that any visitor to the recovery.gov can choose to create a new map view, and then (simply by clicking!) choose what data to put on the map.
Think of it as "choose your own interface".
Regarding implementation approach, XML is a useful interchange format for representing data, but it does not capture the concepts in the data that are needed to enable this sort of scenario in which users can mash up data & views however they want. A semantic (RDF-based) approach provides the conceptual type information needed to flexibly combine data with user interfaces (into "lenses") in an as-needed basis by end users of the recovery.gov Web site.
Comment from
LeeFeigenbaum
at
Cambridge Semantics
on
Apr 28, 2009