Live data from Hacker News

SWI-Prolog for the semantic web

swi-prolog.org

31–32 of 32 posts

Re: SWI-Prolog for the semantic web

#31
post #30

Earlier quoted context omitted.

SPARQL is PSPACE-complete. Worst case complexity and "fast in practice" aren't really the same thing at all. I suspect average case complexity for SPARQL is much better, which is backed up by several reasonably peformant implementations.

What are these reasonably performant implementations? Have you tried them with a billion edges? Also, if your data store is "fast in practice" but has worst cases that are PSPACE-complete, how do you prevent worst-case queries from DOSing it?

Well, I'm a vendor in the space so I like my implementation: http://stardog.com/ -- and yes we've "tried it" with 10s of billions of edges.

Worst cases are prevented from DOSing by having query management features like auto-killing queries that run too long, etc.

Re: SWI-Prolog for the semantic web

#32
post #27

Earlier quoted context omitted.

True. Most notably I badly miss the ability to encapsulate queries in named "functions". That is one of the things I really like in prolog, since it enables to quickly raise one's level of abstraction, by building up a "language" of facts and rules. If anyone knows a way to do something similar in SPARQL, I'm highly interested to know.

You can do this with user-defined rules in some RDF databases. Stardog(.com) supports it nicely.

Interesting, thanks for the hint!
Post reply on HN