- From: Alexander Löser <aloeser@cs.tu-berlin.de>
- Date: Thu, 08 Aug 2002 14:28:03 +0200
- To: Seth Ladd <seth@brivo.net>
- CC: www-rdf-interest@w3.org
Seth Ladd wrote: > Alexander Löser wrote: > > At http://nutria.cs.tu-berlin.de/roodolf > > you can query Google Search Engine via a Webinterface and will retrive > > the result in RDF. I used the Jena Toolkit, the Google API and an Tomcat > > Server. > > The RDF Schema is aviable at http://nutria.cs.tu-berlin.de/roodolf/rdfs > > Great idea! > > A couple of suggestions to make it more Web friendly... > > - Instead of relatedInformationPresent, is it possible to construct a > URI that points to the relatedInformation for this resource? That URI > would probably go back to your service and do the relatedInformation API > call, but you can wrap that as a Resource. Very RDF friendly. :) Ok. Now a relatedInformationURI Property is aviable. You can use this Property to initiate an new RooDolF search. > > > - Can we create a URI for the search itself? Instead of the .jsp being > the URI, we can create something like: > > http://your.google.service/search/param+param+param I don't know how to realize such an query string with tomcat. Any Idea? The URI for the search is created already but for the adequat Google Search. So your Property hasGoogleResults can be described by adding the google URL. Do you belive it would be interesting to create a Roodolf search Url Property? > > > That would be a URI that represents that search. We can GET that over > and over. Plus we can include that in our own RDF. Imagine being able > to describe a resource and include a property hasGoogleResults. > > Very cool, > Seth -- ______________________________________ Alexander Löser Technische Universitaet Berlin Fakultaet IV - CIS bmb+f-Projekt: "NewEconomy" "Neue Medien in der Bildung" email: aloeser@cs.tu-berlin.de office: +49- 30-314-25555 fax : +49- 30-314-21601 ______________________________________
Received on Thursday, 8 August 2002 08:30:16 UTC