[redland-dev] Storage options and more

[Morten Frederiksen]

Hi there,

I've been corresponding with Dave regarding the MySQL storage factory for 
Redland that I've been writing, and he suggested we took the conversation in 
here...


...

I wonder if it would be a good idea to have the storage code do table 
creation (with slient failures) when supplied with the "new" parameter - that 
should make it even easier to use?

On my wish list is currently an nt(+)->rdf/xml converter, which I've hacked 
together in a Perl script, but it reads the complete input into a model 
before serializing, I imagine it could be made more effective with more 
direct access to some serializer methods? Perhaps rapper could be extended? 
Otherwise the name "reppar" is up for grabs... ;->

Also, I'd really like the raptor_uri_parse method (and others) to be public, 
especially since I'd like to extend rdfproc to handle a RSI (Redland Storage 
Identifier) instead of a model name/id. Also, I'd want to add my "tree" code 
(that recursively extracts properties and resource from a base URI) to that, 
as a new command.

RSI ideas:
* MySQL:  mysql://user:password@host:port/db/model[/context]
* 3store: tstore://user:password@host:port/db/model[/context]
* bdb:    bdb:///path/model[/context]
Perhaps the context should be in the query string instead (definitely not as 
a fragid)?


Regards,
Morten Frederiksen

PS: I just got my FOAF Explorer ( http://xml.mfd-consult.dk/foaf/explorer/ ) 
to accept (almost) all of RDF/XML by invoking Redland from PHP - it works!