...
- JTA (Andre)
- Handle all transactions
- One write at a time - need to move to multiple writers
- Connection API
- Graph URIs (permits arbitrary URIs - does not identify host)
- Rmi://host.com/server1?graph=foo:bar as opposed to # (fragment ID)
- SPARQL Engine
- SPARQL Language
- Focused on join optimizations rather than filtering which is needed for complex SPARQL queries
- Meeting W3C SPARQL spec especially what goes in must come back exactly (cannot be canonicalized)
- Sesame Integration
- James at Sesame giving good feedback
- Sesame is 100% SPARQL but not Mulgara. SPARQL has distinct clause which causes problems with set semantics. Not easily fixed. No support for Regular Expression (different from Java). Order-by arbitrary expression support.
- HTTP APIs
- TQL (iTQL name going away)
- SPARQL
- Using Servlets
- Throw exception if "insert" into Get operation
- Post expects an RDF file
- May be output in JSON
- HTTP UI
- Cleaned up no longer implemented in Barracuda
- Tutorial mentions graph URI: (not needed for real) Select Query: Query: Submit Button
- XA 1.1
- Scalability
- Multiple writers
- No problem with recycling Identifiers on 64bit systems
- 192 to 32 files for storage
- Better block writes
- Get test info from Ronald/Paul for presentations
- Change term from Model to Graph (W3C)
- Can index on all three orders SPO, POS, OSP
- Can index SPOG,POSG,OSPG,GSPO,GPOS,GOSP mostly these
- RLog - RDF Prolog
- hasUncle(X, Z) :- hasFather(X, Y), hasBrother(Y, Z). head :- body
Wiki Markup - Foof:Person(foo:bar).
- Supports transitivity, symmetry, will support consistency
- User transitivity to implement a resolver
- JLine - Library for Java but must use native code to do it. Supports a lot of platforms. Andy wrote
...