Closed markpyzhov closed 6 years ago
I am assuming that the points are an extrapolation of the idea of using graphql for ML models. In here, we can allow users to access data fields with some restrictions without allowing them to see the whole data.
Regarding the usage, there is one problem. Graphql can not hide the structure of a dataset. That is, all fields that are meant to be accessible via graphql will be visible to everyone and they can't be hidden (although they can be restricted via token based access). If there is some dataset in which we dont want certain people to even know that particular fields exist, using REST API would be better than Graphql as REST allows such hiding to be possible.
If it is possible can you describe step-to-step the use case?
This is what Kapil said and what he and I discussed. Either we have to handle this through GraphQL or by requiring the same dataset to be registered in different ways.
We would need a use case where the structure is hidden or the number of records are limited so that a Data Scientist can work on an Algorithm with only 1000 records, for example.
Access would be specified by the Customer. A Customer would say:
The sample structure could be very standard. Always, 10000 records
We would need a use case where the structure is hidden or the number of records are limited so that a Data Scientist can work on an Algorithm with only 1000 records, for example.
I'm little confused by "where the structure is hidden". The structure is hidden or the data itself? If the data itself, then I would like to propose an additional way: MallCloud/Algorithm-Market-Platform#74
The original text of requirements is described in wiki/BlockChain-communication.
@ehillerbrand @daemonslayer can you explain these two points? I'm not sure I understand the process.
For explanation of difference was created #17