Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a more readable function reference #21

Open
Aklakan opened this issue Apr 28, 2021 · 1 comment
Open

Create a more readable function reference #21

Aklakan opened this issue Apr 28, 2021 · 1 comment

Comments

@Aklakan
Copy link
Member

Aklakan commented Apr 28, 2021

Also, json:entries and geof:parsePolyline is missing in the docs

@Aklakan
Copy link
Member Author

Aklakan commented Feb 18, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant