-
Notifications
You must be signed in to change notification settings - Fork 22
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
support transaction functions #232
Comments
Do we have a complete list of transaction functions we intend to support? |
I think they should be in the spirit, or similar, to the SPARQL function list. Then we extend those for whatever we don't cover, and some won't be applicable likely in a transactional context. But I sort of feel like that's the place to start, and then here adjust what is supported there ideally after we implement them in query. Also, using I'm basically saying there is still a good amount of work here to spec, and it should closely align with query functions. https://www.w3.org/TR/sparql11-query/#SparqlOps |
|
I think most if not all of these are/can be supported with the new update (
|
Removing the "needs specification" label, the task is to make this list of functions work: https://www.w3.org/TR/sparql11-query/#SparqlOps Per @zonotope , several of these should be largely trivial, and based on the existing method of supporting bind/filter functions. |
Here's what's not implemented yet: Functional forms:
Scalar functions:
String functions:
Numeric functions
Date/time functions
Hash functions
I think it may be worthwhile to break this into separate tickets, maybe for each class of functions. |
|
It might make sense to split |
etc.
The text was updated successfully, but these errors were encountered: