Skip to content

Conversation

HeikoTheissen
Copy link
Contributor

No description provided.

@HeikoTheissen HeikoTheissen linked an issue Apr 25, 2025 that may be closed by this pull request
@HeikoTheissen HeikoTheissen added the Data Aggregation Extension for Data Aggregation label Apr 25, 2025
@@ -370,6 +370,8 @@ The output set of the transformation $\Pi_G(s)$ is in one-to-one correspondence
- Otherwise, the behavior is undefined. (Such cases never occur when $\Pi_G(s)$ is used in this document.)
3. Return $u$.

Instances in the output set of $\Pi_G(s)$ that contain the key of an entity MAY retain that entity's applicable control information [#OData-JSON#ControlInformation].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something like (feel free to edit as appropriate)

Suggested change
Instances in the output set of $\Pi_G(s)$ that contain the key of an entity MAY retain that entity's applicable control information [#OData-JSON#ControlInformation].
Instances in the output set of $\Pi_G(s)$ that contain the key of an entity retain the metadata associated with the entity instance, such as id and etag.

and possibly state that this information may be returned in the final response according to the format-specific conventions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Aggregation Extension for Data Aggregation
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Control information for non-transient entities after $apply
2 participants