- From: Tim Berners-Lee <timbl@w3.org>
- Date: Thu, 5 Jan 2006 10:31:25 -0500
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: Jan Algermissen <jalgermissen@topicmapping.com>, Frank Manola <fmanola@acm.org>, Timothy Falconer <timothy@immuexa.com>, semantic-web@w3.org
On Jan 4, 2006, at 14:23, Richard Cyganiak wrote: > > On 4 Jan 2006, at 20:03, Tim Berners-Lee wrote: > >> One answer is: don't! The SemWeb is about conecting the data to >> what it means. >> Keep the data in the place where it works and runs fast. >> Find/Write ontologies about what the data is about. >> Run a virtual RDF server (supporting SPARQL if a large DB) on top >> of the data. >> publish the connection between the database columns and the >> ontolgies. >> > > I don't get this last bit. Why would someone know what database > column a bit of data comes from? Isn't this an implementation > detail that should better be hidden from consumers of the RDF? Sorry. I meant define it. Don't publish it widely. But internally, this mapping is what your code then uses to make it virtually part of the semantic web. A 1998 article on it, updated in 2002, proposing a mapping: "Relational Databases on the Semantic Web" http://www.w3.org/DesignIssues/RDB-RDF.html This points to python code (dbview.py) implementing the mapping. Slides on the architecture buried in my BioIT talk from around slide 16 on http://www.w3.org/2005/Talks/0517-boit-tbl There are quite a lot of implementations of this sort of thing out there now. Tim
Received on Thursday, 5 January 2006 15:31:37 UTC