ISSUE-109: SHACL requires that SPARQL implementations be able to call functions defined on the fly
function calling
SHACL requires that SPARQL implementations be able to call functions defined on the fly
- State:
- CLOSED
- Product:
- SHACL - SPARQL
- Raised by:
- Peter Patel-Schneider
- Opened on:
- 2015-11-04
- Description:
- The current SHACL spec requires that SPARQL code be able to call functions defined in the shapes graph. This not only requires calling extension functions as in http://www.w3.org/TR/sparql11-query/#extensionFunctions but the ability to create these functions on the fly, i.e., for each validation, and back them with executables derived from the shapes graph.
I don't think that this is something that was envisioned for SPARQL extension functions. Its implementation may turn out to be problematic.
An alternative would be to have a single SPARQL function that gives access to the SHACL functions, e.g., something like callSHACLFunction(name,arg,...).
- Related Actions Items:
- No related actions
- Related emails:
- shapes-ISSUE-109 (function calling): SHACL requires that SPARQL implementations be able to call functions defined on the fly [SHACL Spec] (from sysbot+tracker@w3.org on 2015-11-04)
Related notes:
RESOLUTION: Close ISSUE-109, keeping with the current spec - no wrapper function
See http://www.w3.org/2015/12/15-shapes-minutes.html#resolution04
Display change log
