Wack: It's part of a website framework 'Angelite' we're developing, all data that drives the website (both static and dynamic) is RDF in Aquamarine.
Wack: A good place to start browsing the API is from the Server and/or Model interface.
Wack: Please note the ability to make 'volatile' statements; these will disappear after the model has been closed, more or less a pseudo-transactional system to facilitate request-specific output in the website framework it is part of.
dajobe: aquamarine.idl
Wack: We're still considering cleaning up a lot of stuff to make the DB more 'RDF compliant' internally and externally (dajobe noted properties being split in namespace & localname) and other leftovers like statements being resources etc.
Wack: A good place to start browsing the API is from the Server and/or Model interface.
Wack: Please note the ability to make 'volatile' statements; these will disappear after the model has been closed, more or less a pseudo-transactional system to facilitate request-specific output in the website framework it is part of.
dajobe: aquamarine.idl
Wack: We're still considering cleaning up a lot of stuff to make the DB more 'RDF compliant' internally and externally (dajobe noted properties being split in namespace & localname) and other leftovers like statements being resources etc.
dajobe: at least when aquamarine.Node is a Statement