- From: Chris Bizer <chris@bizer.de>
- Date: Tue, 5 Dec 2006 10:22:38 +0100
- To: "'Aldo Bucchi'" <aldo.bucchi@gmail.com>, <semantic-web@w3.org>
Hi Aldo, > Another neraby issue... does anyone know if there's a "query service > description" taxonomy /vocabulary? There is a Wiki page collecting work around SPARQL endpoint descriptions: http://esw.w3.org/topic/SparqlEndpointDescription?highlight=%28SPARQL%29%7C% 28Endpoin%29%7C%28description%29 > > I'm now leading a big (10-20 devs) project and I'm willing to give RDF > > a try as the framework for integrating part of the data ( mashup )... > > again, I twistedly love the pain found in early adoption. As an example of an RDF linked data mashup, our recently released book mashup might be of interest to you: http://sites.wiwiss.fu-berlin.de/suhl/bizer/bookmashup/index.html Cheers, Chris -- Chris Bizer Freie Universität Berlin Phone: +49 30 838 54057 Mail: chris@bizer.de Web: www.bizer.de > -----Ursprüngliche Nachricht----- > Von: semantic-web-request@w3.org [mailto:semantic-web-request@w3.org] Im > Auftrag von Aldo Bucchi > Gesendet: Dienstag, 5. Dezember 2006 10:11 > An: semantic-web@w3.org > Betreff: Re: Reinventing the wheel ( ...again ); this time with RDF In/Out > Services > > > duh, I forgot to reference the RIRO vocabulary by Sergei Egorov: > > http://vocab.org/riro/sdl > > best, > Aldo > > On 12/5/06, Aldo Bucchi <aldo.bucchi@gmail.com> wrote: > > Hi all, > > > > Don't you hate it ( or love it in a subtly twisted way ) when you run > > across the very same "I bet no one's ever done this" feature you've > > been working heads down for last two nights? > > > > Well, this time its about this RDFIO thingy... a declarative way to > > wrap services. > > I had two names for it... the first was RDF BAGs ( before/after graphs > > ) or RDFio, but liked the former because it emphasizes the "wrapping" > > action and the latter is just too dumb. > > > > Anyway, > > > > Is there any further work around this? > > say... RIROs & REST for example.. > > > > ( noticed how rest has become a little unrestful these days? ) > > > > I've had a lot of fun trying to create some simple algorithms to > > undertsand at a higher level the cost and amount of arc traversals > > that could be made over a set of BAG-wrapped services ( ok... RIRO > > services ). Would make for a nice paper, server yourselves. > > > > Another neraby issue... does anyone know if there's a "query service > > description" taxonomy /vocabulary? > > When using this wrappers there is a recurrent need to specify further > > "capabilities" of the service. > > > > I need a way to state that > > > > paramA, fulltext search filter > > paramB, mask filter ( full match ) > > sort on B > > sort on C > > the service provides a count() service ( taking the same params but on > > another URL, or passing a flag, or using OPTIONS, who knows ) > > > > get the point? > > > > I believe that with this new REST momentum there is pretty nice chance > > to leap this evident gap and push rdf closer to mainstream. To me, > > it's clear that one fundamental mistake in the marketing of the sw has > > been neglecting the need ( and value ) of these simple "recipes". > > > > We are missing the glue... the transport. > > > > I'm now leading a big (10-20 devs) project and I'm willing to give RDF > > a try as the framework for integrating part of the data ( mashup )... > > again, I twistedly love the pain found in early adoption. > > > > Any pointers appreciated! > > > > > > -- > > ::::: Aldo Bucchi ::::: > > mobile (56) 8 429 8300 > > > > > -- > ::::: Aldo Bucchi ::::: > mobile (56) 8 429 8300
Received on Tuesday, 5 December 2006 09:25:20 UTC