Slashdot Log In
Super-Fast RDF Search Engine Developed
Posted by
ScuttleMonkey
on Fri May 04, 2007 09:27 AM
from the google-to-buy-ireland dept.
from the google-to-buy-ireland dept.
The Register is reporting that Irish researchers have developed a new high-speed RDF search engine capable of answering search queries with more than seven billion RDF statements in mere fractions of a second. "'The importance of this breakthrough cannot be overestimated,' said Professor Stefan Decker, director of DERI. 'These results enable us to create web search engines that really deliver answers instead of links. The technology also allows us to combine information from the web, for example the engine can list all partnerships of a company even if there is no single web page that lists all of them.'"
Related Stories
[+]
Why the Semantic Web Will Fail 179 comments
Jack Action writes "A researcher at Canada's National Research Council has a provocative post on his personal blog predicting that the Semantic Web will fail. The researcher notes the rising problems with Web 2.0 — MySpace blocking outside widgets, Yahoo ending Flickr identities, rumors Google will turn off its search API — and predicts these will also cripple Web 3.0." From the post: "The Semantic Web will never work because it depends on businesses working together, on them cooperating. There is no way they: (1) would agree on web standards (hah!) (2) would adopt a common vocabulary (you don't say) (3) would reliably expose their APIs so anyone could use them (as if)."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Official DERI Website (Score:3, Informative)
DERI [www.deri.ie]
TMA: Too Many Acronyms (Score:3, Insightful)
Re:TMA: Too Many Acronyms (Score:5, Funny)
OMG: Oh my God!
WTF: What the fuck?
BBQ: Barbecue.
HTH
Parent
Re:Official DERI Website (Score:5, Funny)
Parent
This could be huge (Score:5, Interesting)
Next up: Ontology spam (Score:5, Insightful)
Parent
Re: (Score:2)
Re: (Score:2)
For a while, yes. But as long as there is a cash-per-page-view market, the onslaught of adverspam will reach every corner of the web. It can't be stopped as long as there is money to be made there.
Certainly the big "pure knowledge" sites will defend themselves, as Wikipedia does, but that is an ar
Re: (Score:2)
And I'm sure that next generation search engines will create clever ways of detecting and punishing ontology spam (e.g., noting the dissonance between the text and the tags)
Re: (Score:2)
Re: (Score:2)
transparency ==> translucency ==> opacity
Or, to put it in website design terms: "It's not blue enough.
Re: (Score:2)
Re: (Score:2)
I'd say consistent ontology is a bigger challenge (though also one that doesn't need to be anywhere near completely solved for all kinds of useful applications to exist.) Trust mechanisms built on RDF aren't really all that big of a challenge: trust relationships are fairly basic, straightforward relationships of exactly the type RDF was designed to express from the outset, after all
Re: (Score:3, Insightful)
Re:This could be huge (Score:4, Insightful)
Parent
Re: (Score:2, Interesting)
Re: (Score:2)
Why would I want to search... (Score:2)
Re: (Score:2)
Links! (Score:4, Insightful)
I need both: answers *and* links! Many times when I search the web, I don't know for sure what am I searching for, let alone being able to ask specific question...
Re: (Score:2)
Re: (Score:2)
RDF could do very useful things, like throwing up a disambiguation question at the top os the results page when you've not made it clear what you want, or filtering out the plague of typosquatter/content free price comparison/'be the first to write a review of this item' sites, but so could a bit more intelligence built into Google.
Re: (Score:2)
Re: (Score:3, Funny)
No thanks, I don't need Clippy in my search engine.
Re: (Score:2)
In your example, I'm guessing you might find the option to filter dow
Re: (Score:2)
However, I think contextural disambiguation questions like what you're suggesting are already served by "search within results" queries. Proposing likely criteria for narrowing down the results would be, I think, a disservice. It pigeonholes sites, but worse than that, pigeonholes searches. This leads to easy gaming of the search system -- SEO would cause pretty much every site to make sure it's associated with the typical disambiguation terms, thus removing the utility
Re: (Score:2)
The terms wouldn't be 'typical disambiguation terms', as they would be generated freshly from the content of the pages that appear in the searc
Re: (Score:2)
So, I think what you're suggesting is that the search engine prompt those terms to help people narrow their search? Didn't Ask Jeeves try this and miserably fail -- and if
Search solved. World hunger next. (Score:4, Funny)
Re: (Score:2)
We've already got a cure for cancer.
Hype (Score:5, Insightful)
Yet another
Re: (Score:2, Insightful)
RDF? (Score:4, Funny)
I'll prove him wrong (Score:4, Interesting)
This is without a doubt the greatest invention in the history of time!
There, I just proved the professor wrong. Muahaha.
Cannot be overestimated (Score:5, Insightful)
The importance of any event can be overestimated and quite often is overestimated. It is called hype.
When speaking of XML, XHTML and semantic WEB then the word "overestimated" fits just nice.
If this was not the case then HTML should long have been dead and the whole WEB should have been based on pure XML with meaningful tags.
-- Do not read me, I am a stupid tag
Could be interesting, but missing details (Score:5, Interesting)
What kind of queries are they running? There are several different RDF query languages (think of SeRQL, RDQL, N3, SPARQL, etcetera) and some of them support quite complex queries. Quickly finding the answers to a simple query like is just a matter of an indexed lookup and not very special. But, like in SQL, much more complex expressions can be generated that require complex index operations on the query execution level. Having implemented an RDF database that supports SPARQL queries an order of magnitude faster than the software the W3C uses for their experiments (which, admitedly, doesn't have performance as a prime requirement), I know that it's possible to do simple things fast, but the interesting part is handling RDF queries that don't easily map to efficient database operations.
Which brings me to the most important point: where is their detailed report? Can I get the software somewhere and perform my own tests? The article is too vague to draw any conclusions about what their RDF database does, and how good it is. I'd love to read up on it, but I can't seem to find the information.
Here's the Tech Report (Score:5, Informative)
We have a Technical Report available at http://www.deri.ie/fileadmin/documents/DERI-TR-20
From the abstract:
"We present the architecture of an end-to-end search engine that uses a graph data model to enable interactive query answering over structured and interlinked data collected from many disparate sources on the Web.
In particular, we study distributed indexing methods for graph-structured data and parallel query evaluation methods on a cluster of computers.
We evaluate the system on a dataset with 430 million statements collected from the Web, and provide scale-up experiments on 7 billion synthetically generated statements."
Parent
Re:Here's the Tech Report (Score:4, Insightful)
Parent
SUPER Speed (Score:2, Funny)
Re: (Score:2, Informative)
If you're going to steal a joke, you need to make sure to replace all references to the original. Find / Replace works great for this.
Two things... (Score:2)
Second, the problem with "the semantic web" if you're relying on people providing the metadata themselves, is the reliability (trustworthiness?) of the person creating the metadata. There's a reason the meta name="keywords" tags aren't a significant factor if at all in any of the major search engines' ranking systems.
sounds fishy (Score:3, Interesting)
Of course a search based on meta data is going to be faster and more accurate, but only when the meta data is correct. We've had this since the beginning of the interweb; people would load up their pages with bogus meta data just to generate search traffic. Because of this dishonesty, search engines have had to resort to other methods of evaluating and indexing pages (for example, based on actual content).
I don't see any difference between this new RDF and that old stuff.
Save the hype (Score:2)
Developer on this project (Score:3, Informative)
Re: (Score:2)
I'm using Firefox under Windoz and I could not access the article either. It's a bad URL.
This is great and all (Score:2)
Re:Great!! (Score:5, Informative)
Parent
Re: (Score:3, Informative)
Re: (Score:2)
Re: (Score:2)