RdfProcessingToolkit
RdfProcessingToolkit copied to clipboard
Create a more readable function reference
Also, json:entries and geof:parsePolyline is missing in the docs
Probably the best approach would be as follows:
- Extend the function binder to build the FNO model using reflection so that our function extensions are self-describing.
- Create a small main class that iterates Jena's function registry and emits the FNO models of all registered functions.
- Have a static site (markdown?) generator that builds a function reference from a function ontology document (FNO)
- Textual descriptions should for I18N reasons probably be maintained in a separate RDF model. Probably this model should reference functions by the fully qualified class name (java:pkp.MyClass) rather then the public SPARQL IRI.