Cell phones have evolved immensely since 1983, both in design and function.
From the Motorola DynaTAC, that power symbol that Michael Douglas wielded so forcefully in the movie “Wall Street”, to the iPhone 3G, which can take a picture, play a video, or run one of the thousands applications available from the Apple Store.
There are thousands of models of cell phones that have hit the streets between 1983 and now.
We’ve picked a few of the more popular and unusual ones to take you through the history of this device that most of us consider a part of our everyday lives.
The following papers have been accepted for SFSW2009:
- Christoph Lange : Krextor — An Extensible XML->RDF Extraction Framework
- Eugenio Tacchini, Andreas Schultz and Christian Bizer : Experiments with Wikipedia Cross-Language Data Fusion
- Jouni Tuominen, Tomi Kauppinen, Kim Viljanen and Eero Hyvönen : Ontology-Based Query Expansion Widget for Information Retrieval
- Laura Dragan, Knud Möller, Siegfried Handschuh, Oszkar Ambrus and Sebastian Trueg : Converging Web and Desktop Data with Konduit
- Mariano Rico, David Camacho and Oscar Corcho : Macros vs. scripting in VPOET
- Norman Gray, Tony Linde and Kona Andrews : SKUA — Retrofitting Semantics
- Pierre-Antoine Champin : Tal4Rdf: lightweight presentation for the Semantic Web
- Rob Styles, Nadeem Shabir and Jeni Tennison : A Pattern for Domain Speciﬁc Editing Interfaces Using Embedded RDFa and HTML Manipulation Tools
- Stéphane Corlosquet, Richard Cyganiak, Axel Polleres and Stefan Decker : RDFa in Drupal: Bringing Cheese to the Web of Data
Looks like a great line-up. As neither Nad, Jeni nor I are able to attend our paper will be presented (briefly) by Chris Clarke.
Are you writing multi-tenant software? Are you using RDF at all? Do you want to keep track of your tenants?
You might want to comment on the first draft of the new Multi-Tenant Configuration Schema.
This schema attempts to describe a simple set of concepts and relationships about tenants within a multi-tenant software system. It avoids anything that would constitute application configuration, but will happily co-exist with classes and properties to do that. The documentation is sparse currently, awaiting questions and comment so that I can expand on areas that require further explanation. Comment here, or email me.
1987 – Larry Wall falls asleep and hits Larry Wall’s forehead on the keyboard. Upon waking Larry Wall decides that the string of characters on Larry Wall’s monitor isn’t random but an example program in a programming language that God wants His prophet, Larry Wall, to design. Perl is born.
The proceedings jumped the line to farce when Fritz Attaway and a colleague from the MPAA pulled out a cinematic demonstration of just how to camcord a movie from your television screen. (You start with a $900 HD video camera, a tripod, a flat-screen television, and a room that can be completely darkened.) Tim Vollmer captured the whole scene on a video of his own. Mind you, this is the same industry that has lobbied to make a crime of camcording in movie theaters, telling us how to frame shots properly from the television. (As Fred Benenson notes, they’re also demonstrating DRM’s impossibility of closing the “analog hole.”)
Agree with this summary from Richard
On the surface, to those not yet bought in to the potential of Linked Data, and especially Linked Open Data, this may seem like an interesting but not necessarily massive leap forward. I believe that what underpins the fairly simple functional user interface they provide will gradually become core to bibliographic data becoming a first-class citizen in the web of data.
Overnight this uri ‘http://id.loc.gov/authorities/sh85042531’ has now become the globally available, machine and human readable, reliable source for the description for the subject heading of ‘Elephants’ containing links to its related terms (in a way that both machines and humans can navigate). This means that system developers and integrators can rely upon that link to represent a concept, not necessarily the way they want to [locally] describe it. This should facilitate the ability for disparate systems and services to simply share concepts and therefore understanding – one of the basic principles behind the Semantic Web.
Great to see LoC doing this stuff and getting it out there.