-
Notifications
You must be signed in to change notification settings - Fork 5
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
Search #1
Comments
Agreed! Let's use this issue to chat about use cases and then design the API before I (or someone else who wants to contribute) implement it. One thing I find myself wanting already that's not even morphological is "which paragraph has this particular verse?" It would be good to collect a bunch of use cases like this and then see what abstract query types we'll need. I think it will be straightforward to have queries of the form "show me the words with these attributes". We might also wanted to support "show me the {verses|chapters|paragraphs|books} that contain words with these attributes". The "which paragraph has this verse" is a little more unusual a pattern. There's also the possibility of converting human readable verse references so I can type "John 3.16" into a form and have it resolved to /v0/verse/64003016.json or whatever. There is a larger question of supporting something like JSONiq but that's getting into a much bigger question that I'm going to suggest is outside the scope of this particularly discussion. |
I should note that I'm planning a site that allows navigation through other morphological dimensions, e.g. "show me the nouns in this inflectional class" or "show me the verbs that form their present the same way as X". Open question whether the API would support that kind of thing but again, we can leave that outside scope for now, although if we come up with abstract queries patterns, we might want to at least briefly consider object types beyond what the API currently has. |
It would be great to have a search api accessible (especially if it can be morphologically nuanced).
The text was updated successfully, but these errors were encountered: