Skip to content
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

Extension as DataTransferEndpoint for AAS Operation Results #155

Open
carlos-schmidt opened this issue Oct 25, 2024 · 0 comments
Open

Extension as DataTransferEndpoint for AAS Operation Results #155

carlos-schmidt opened this issue Oct 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@carlos-schmidt
Copy link
Collaborator

Currently, AAS operation results can only be transferred to remote data destinations.
This is because an AAS operation invokation request to the client is nested inside the destination DataAddress like this:

{ "type": "HttpData",
  "properties": {
        "https://w3id.org/edc/v0.0.1/ns/baseUrl": "http://localhost:5001/transferEndpoint",
        "method": "POST",
        "operation": {
            "inputArguments": {
                "input1": 4,
            },
            "inoutputArguments": {
                "inout": "helloworld"
}   }   }   }

Maybe create a new request with only the operation variables as payload

@carlos-schmidt carlos-schmidt changed the title Extension as DataTransferEndpoint for AASOperation results Extension as DataTransferEndpoint for AAS Operation Results Oct 26, 2024
@carlos-schmidt carlos-schmidt added the enhancement New feature or request label Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant