Semantic Search - Faceted Search and Web 3.0 for Drupal

There's a few anomalies with the current setup.
First, Sesame's memory store is truly stored in memory, and I access via both a custom app, and the standard REST interface. This produces concurrency issues, since the Sesame application stored for the REST interface doesn't seem to sync as often. Also, the console fails to catch this unless the url at http://localhost:8080/openrdf-sesame has its web container restarted.

These are all stored in memorystore.data. I plan to ask if sync is set to 0, how long does it take?

The (Slowly) Open Sesame article here provides an honest assessment of using Sesame for real world applications.

Here's an excerpt:

The module is being updated to make sure it works well in Java 6 and with the latest Sesame 2.0 release.
There are still a number of bugs with the pilot application. The application is being tested on OSX and will a launch on windows server 2003. The three major hurdles are

• CRUD speed- using a Sesame memory store is very fast, but updates are hard because of the way it reindexed. Hoping this is fixed in 2.0, as I filed a bug about this before.
  

Here are results of running the scripts against the database of 90,000 statements - 34 queries, in about .3 seconds.

It retrieves all distinct properties, then loops through and retrieves all distinct values for those properties.

The punchline : after a number of tests, prepared queries at this point are only slightly faster. I may cache the tuple query in quercus APC - but for now, the regular queries are sufficiently fast.

COUNT of 33 DISTINCT TOTAL PROPERTIES

You are looking at the speed of AHIRC front page loads now, after another 18 hour day. This is 3-12X faster than the last post!!

note: 300ms were a missing file...

Looks like I'll be using a hybrid approach of the HTTP client, and a custom class running on JAVA to do the aggregation emulation.

Here's a recap of the consequences.
The first points of failure are (since the HTTP client for Sesame works great):

* SPARQL/Sesame not having Aggregate functions
* Sesame not having ORDER BY

This produces large amounts of results and/or queries, which then need to be parsed by JSON, leading to the second point of failure

* Zend JSON and native php 5.2 JSON are not fast enough (perhaps they should not be expected to be for 6000 results)

212 queries to load the front page of AHIRC. That'll do it.
This happens because I am trying to emulate the "COUNT" mixed with "GROUP BY" you'd find in SQL. One company has it:
http://docs.openlinksw.com/virtuoso/rdfsparqlaggregate.html
And looks like others are anxious:
http://simile.mit.edu/mail/ReadMsg?listId=14&msgId=16326
But it's not an easy problem in a broader context:
http://www.ldodds.com/wordtin/Wiki.jsp?page=UniqueNamesAssumption

Development is coming along, and there are a number of possibilities that Sesame opens up.

When you can run complex queries on Drupal data, maybe that will convince some skeptics of the value. Take for example:
http://www.openrdf.org/contrib.jsp
like
http://www.ontotext.com/bor/ (rules engine) and http://www.ontotext.com/owlim/ (OWL store and engine)

The client is nearing completion. I'm working on create, update, and Delete. I'll post a version of the file on this site when done
Thanks for the help from Sesame's project leader in the following forum thread.

http://www.openrdf.org/forum/mvnforum/viewthread?thread=1417