BLUEPRINT RDF Support

In order for Odysseus to read the SKOS resources that'll power it's bookmarks, Prosody must learn to read RDF. In terms of syntax Prosody properties would be mapped to RDF predicates, and iteration would give all RDF objects that match that predicate path. String literals would be restricted to the most relevant predicate available. Just throw in a new template tag to define XML & RDF namespaces, and we should have all we need.

The only problem is with whether the predicates we're matching are explicit or implicit, and supporting implicit would both be easier at the UI level and more correct. For this I'd add a component I'll call Pallas, which'll add stronger bindings to libRaptor whilst implementing OWL 2 EL.

Pallas would have to handle two use-cases: Collecting subject-predicate-object & object-predicate-subject indices and use those to infer additional triplets lazily for each key & value. Then Ideally upon scanning RDF I'd infer additional properties, which'll be used for discovery features. This can still build on the system with pure forward inferences.