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

Batch requests: Referencing values from response bodies more generally #1969

Closed
HeikoTheissen opened this issue Jul 29, 2024 · 2 comments
Closed
Assignees
Labels
Protocol Protocol, URL Conventions V4.02

Comments

@HeikoTheissen
Copy link
Contributor

OData-Protocol, section 11.7.6 states:

Alternatively, a value reference can consist of a $ character followed by the value of an instance annotation with term Core.ContentID (see OData-VocCore) that occurs in the payload of the preceding request as described in section 11.4.2.2 and section 11.4.3.1, then the referenced value is the corresponding value in the response, which the service SHOULD annotate with the same Core.ContentID value.

This is too narrow. Core.ContentID instance annotations may also appear in responses to other types of request, for example, action invocations.

@ralfhandl
Copy link
Contributor

TC 2024-08-28: for the existing cases (insert, update) the relationship between ContentIDs in request and response is "canonical". For actions this is less clear.

@HeikoTheissen to follow up on this relationship and reduce the amount of out-of-band knowledge.

@ralfhandl & @HeikoTheissen to find out which parts of content-id referencing are already implemented by SAP.

@ralfhandl
Copy link
Contributor

TC agrees that the new functionality can be purely provided via vendor-specific extensions and no changes to the Core specifications are needed.

@ralfhandl ralfhandl closed this as not planned Won't fix, can't repro, duplicate, stale Sep 4, 2024
@github-project-automation github-project-automation bot moved this from Open to Closed in OData TC Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Protocol Protocol, URL Conventions V4.02
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

2 participants