W3C home > Mailing lists > Public > semantic-web@w3.org > January 2007


From: Danny Ayers <danny.ayers@gmail.com>
Date: Sat, 13 Jan 2007 20:12:13 +0100
Message-ID: <1f2ed5cd0701131112p40ad2714xd5205083299200a9@mail.gmail.com>
To: "Semantic web list" <semantic-web@w3.org>
Cc: "Brian Suda" <brian.suda@gmail.com>
I've just added a page of this name [1] to the ESW Wiki, would appreciate
any pointers. While ConverterToRdf [2] lists tools that are of immediate
interest to people working with RDF, conversion the other way may prove
equally important to the web.

A usage example - a social networking service might offer data import from
vCard format documents. This could be generated from the data in a FOAF
profile via an online service. (Anyone doing that yet? It's available from
microformat formatted data, e.g. [3]).

Like ConvertersToRdf, there are various different mechanisms/strategies
available. I've listed the following so far:

* Direct serialisation (Raptor?)
* SPARQL (one or TwoPhaseSparql)
* programmatic

The Semantic Web needn't rely on every system understanding RDF (in fact I'd
argue that only a tiny percentage of support is needed to get major gains in
net utility). But RDF/XML (and Turtle) serialisations and SPARQL endpoints
still demand quite a lot of the system at the other end of the wire. Online
extraction/conversion facilities could ease this burden. Without outputs
compatible with existing applications, there's a danger of Semantic Web
applications looking like black holes.


[1] http://esw.w3.org/topic/ConverterFromRdf
[2] http://esw.w3.org/topic/ConverterToRdf
[3] http://suda.co.uk/projects/X2V/


Received on Saturday, 13 January 2007 19:12:24 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:59 UTC