Re: Reinventing the wheel ( ...again ); this time with RDF In/Out Services

Dear Aldo,
I am not too sure this is what you're looking for but it might be.
We worked about 6 weeks on this [1][2] :-) this summer
me, Christian Morbidoni, Richard Cyganiak and Michele Nucci.

Abstract
Over the years, a number of studies and practical efforts have
proposed technologies to retrieve, publish, cooperatively edit, lookup
and query RDF models. Also, other studies and practices have shown
that standard communication channels, e.g. e-mail, RSS and IM, can be
successfully used in Semantic Web scenarios. In this paper we
collectively refer to such technologies as "Semantic Web data access"
and present the "description of data access" ontology (DODA).
DODA is a lightweight formalization which features a simple structure
and specifically targets Social Semantic Desktop use cases. DODA
supports client software in providing meaningful and assisted user
interfaces; as a result, the software con provide the user with a
seamless view of heterogeneous data sources and facilitate giving
external access to local data.


Giovanni

[1] http://semedia.deit.univpm.it/tiki-index.php?page=DescriptionOfDataAccess

On 12/5/06, Aldo Bucchi <aldo.bucchi@gmail.com> wrote:
>
> 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 14:30:15 UTC