-
Notifications
You must be signed in to change notification settings - Fork 49
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
Spec inconsistencies and like/match. #55
Comments
There isn't any official spec, that's the problem. I've been trying to get a response on this too, but never heard anything. I kinda gave up and follow my own spec based on xpath, which javascript developers may or may not like, but at least it's a decent and concise standard and easy to understand. Considering your question, I'd opt for matches. |
I never saw that aps link, it looks slightly better, but it isn't implemented either afaik. |
Re-reading the aps doc, this is more APS's own interpretation of RQL and not official (hence the line "APS uses a subset of the RQL operators and adds some APS-specific functions"). I'm guessing they ran into similar issues, added the operators they needed and named that one "like". So, unless someone else can clarify the only "official" spec is the one in this repo. But now we're back to the question of why it doesn't match the implementation? Its too bad. For URL encoded queries, RQL looked to be the best in terms of simplicity and clarity, its just lacking some rigorousness. |
Hi, all! |
There's the spec in this repo as well as this page:
https://doc.apsstandard.org/2.1/spec/rql/
which references this repo
The later specifies a "like" operator for string matching with wildcards. I've also seen references to this but named "match" instead of like including in the javascript implementation in this repo. But it doesn't show up at all, either as like or match, in the spec in this repo.
So the most important question I have is:
Where is the official spec for RQL, most importantly around operators and their definitions? Maybe there's another place that I missed?
Depending on the answer to that and what the spec is I may have follow up questions for this javascript implementation.
The text was updated successfully, but these errors were encountered: