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
Code-to-data and other scenarios may require the consumer to send information to the provider, for example, a mechanism for processing data before it is transferred.
This can be done using the extensible properties of TransferRequestDto and its analog inDataRequest. The extensible data will then be accessible from a resource generator and provisioner.
Currently, however, there is no recommended way for providers to advertise the requirements for this extensible data. One way to do this would be to use the extensible properties of Artifact where a schema representation could be embedded.
This issue serves as a marker to explore how this should be done.
This discussion was converted from issue #1420 on September 27, 2022 17:33.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Code-to-data and other scenarios may require the consumer to send information to the provider, for example, a mechanism for processing data before it is transferred.
This can be done using the extensible properties of
TransferRequestDto
and its analog inDataRequest
. The extensible data will then be accessible from a resource generator and provisioner.Currently, however, there is no recommended way for providers to advertise the requirements for this extensible data. One way to do this would be to use the extensible properties of
Artifact
where a schema representation could be embedded.This issue serves as a marker to explore how this should be done.
Beta Was this translation helpful? Give feedback.
All reactions