You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I was implementing the /collection and /comparison endpoints we discussed, I thought of a few other possible uses. I would like to know if people think these should be part of the spec.
Overview
Given a POST request the service could notify if this collection is present in the database, and at what level.
Level 1 input
If input is a level 1 representation, INPUT looks like this:
For this to work with level 2 inputs, we have to compute the digests on the server. That means this endpoint could actually be used as a digest computing service for local collections. Thoughts?
This is starting to get into the idea of the search function, but this is actually much simpler than the search function we envisioned.
The text was updated successfully, but these errors were encountered:
@nsheff Seems useful. However, I believe the more common query would be to retrieve the level 0 digests of all the seqcols that contain the submitted arrays, not just information that at least one such seqcol exists. Would this be the search feature you mentioned (I don't remember...)?
As I was implementing the
/collection
and/comparison
endpoints we discussed, I thought of a few other possible uses. I would like to know if people think these should be part of the spec.Overview
Given a
POST
request the service could notify if this collection is present in the database, and at what level.Level 1 input
If input is a level 1 representation, INPUT looks like this:
And response looks like:
Level 2 input
To do this for a level 2 representation, input is:
Response:
For this to work with level 2 inputs, we have to compute the digests on the server. That means this endpoint could actually be used as a digest computing service for local collections. Thoughts?
This is starting to get into the idea of the search function, but this is actually much simpler than the search function we envisioned.
The text was updated successfully, but these errors were encountered: