Partner navigation property for multi-uplinks #382
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vocabularies/Common.xml
Outdated
| <Annotation Term="Core.LongDescription"> | ||
| <String>Let B be any entity in the collection addressed by evaluating the `PartnerPath` starting at an entity A. | ||
| If the annotated navigation property is single-valued, it MUST lead back from B to A. | ||
| If the annotated navigation property is collection-valued, A MUST be one of the |
There was a problem hiding this comment.
D.h. wenn die annotated navigation property "_Headers" wäre, dann wüsste man, dass Headers(1)/_Items(2)/_Subitems(3)/_Headers(1) wieder A ergibt? Aber was hat man davon? Oder welches Beispiel hattest Du im Sinn?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses oasis-tcs/odata-specs#2067