| [dataspace-protocol-base-dev] Question: About extending the control plane to supply data filtering conditions |
| Dear all, This is a question on how to properly design a Data Transfer Profile and to gather experiences you may have had. So I am not proposing any new feature for the protocol at the moment. Do you think it could be a good idea to extend the `TransferRequestMessage` to specify upfront filtering conditions over the dataset you want to pull or push data? Example: I want all the entities in the dataset that match the filter and I request the transfer of only those. See below. Is this a proper usage of the Control Plane? Or should the filtering query only be specified through the data plane once the transfer has been set ? Thank you very much for your thoughts and feedback All the best { "@context": [ "https://w3id.org/dspace/2025/1/context.jsonld", "https://schema.twindev.org/dspace/types.jsonld" ], "@type": "TransferRequestMessage", "agreementId": "urn:uuid:27c4289f-36f1-4eb4-8fc9-8986be3d6e03", "consumerPid": "urn:uuid:48a5e643-8772-4bbb-a5c9-1f1318ced42d", "format": "Http-Pull-Query-Format", "callbackAddress": "https://callback.example.org/consumer1", "filter": { "@type": "EntityFiltering", "q": "destinationCountry == ES OR destinationCountry == PL" } } |