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

ODATA-1583 #204

Merged
merged 13 commits into from
May 22, 2024
2 changes: 1 addition & 1 deletion docs/odata-json-format/odata-json-format.html
Original file line number Diff line number Diff line change
Expand Up @@ -504,7 +504,7 @@ <h2 id="45-control-information"><a name="ControlInformation" href="#ControlInfor
<p>In some cases, control information is required in request payloads; this is called out in the following subsections.</p>
<p>Receivers that encounter unknown annotations in any namespace or unknown control information MUST NOT stop processing and MUST NOT signal an error.</p>
<h3 id="451-control-information-context-odatacontext"><a name="ControlInformationcontextodatacontext" href="#ControlInformationcontextodatacontext">4.5.1 Control Information: <code>context</code> (<code>odata.context</code>)</a></h3>
<p>The <code>context</code> control information returns the context URL (see <a href="#ODataProtocol">OData-Protocol</a>) for the payload. This URL can be absolute or <a href="#RelativeURLs">relative</a>.</p>
<p>The <code>context</code> control information returns the context URL (see <a href="#ODataProtocol">OData-Protocol</a>) for the payload. This URL can be absolute or <a href="#RelativeURLs">relative</a>. The fragment portion of the context URL MUST NOT be percent-encoded.</p>
<p>The <code>context</code> control information is not returned if <a href="#metadatanoneodatametadatanone"><code>metadata=none</code></a> is requested. Otherwise it MUST be the first property of any JSON response that allows this control information (this excludes for example <a href="#ErrorResponse">error responses</a>).</p>
<p>The <code>context</code> control information MUST also be included in requests and responses for entities whose entity set cannot be determined from the context URL of the collection.</p>
<p>For more information on the format of the context URL, see <a href="#ODataProtocol">OData-Protocol</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions docs/odata-json-format/odata-json-format.md
Original file line number Diff line number Diff line change
Expand Up @@ -748,6 +748,7 @@ stop processing and MUST NOT signal an error.
The `context` control information
returns the context URL (see [OData-Protocol](#ODataProtocol)) for the
payload. This URL can be absolute or [relative](#RelativeURLs).
The fragment portion of the context URL MUST NOT be percent-encoded.

The `context` control information is not returned if
[`metadata=none`](#metadatanoneodatametadatanone) is requested. Otherwise it MUST be the
Expand Down
2 changes: 1 addition & 1 deletion docs/odata-protocol/odata-protocol.html
Original file line number Diff line number Diff line change
Expand Up @@ -1002,7 +1002,7 @@ <h2 id="102-collection-of-entities"><a name="CollectionofEntities" href="#Collec
<pre><code>http://host/service/Customers
http://host/service/$metadata#Customers</code></pre>
</div>
<p>If the entities are contained, then <code>entity-set</code> is the top-level entity set or singleton followed by the path to the containment navigation property of the containing entity.</p>
<p>If the entities are contained, then <code>entity-set</code> is the top-level entity set or singleton followed by the canonical path to the containment navigation property of the containing entity. Key values in that path are represented in canonical form (parentheses-style) without percent-encoding.</p>
<div class="example">
<p>Example 12: resource URL and corresponding context URL for contained entities</p>
<pre><code>http://host/service/Orders(4711)/Items
Expand Down
3 changes: 2 additions & 1 deletion docs/odata-protocol/odata-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -2044,8 +2044,9 @@ http://host/service/$metadata#Customers
:::

If the entities are contained, then `entity-set` is the top-level entity
set or singleton followed by the path to the containment navigation
set or singleton followed by the canonical path to the containment navigation
property of the containing entity.
Key values in that path are represented in canonical form (parentheses-style) without percent-encoding.

::: example
Example 12: resource URL and corresponding context URL for contained
Expand Down
1 change: 1 addition & 0 deletions odata-json-format/4 Common Characteristics.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,7 @@ stop processing and MUST NOT signal an error.
The `context` control information
returns the context URL (see [OData-Protocol](#ODataProtocol)) for the
payload. This URL can be absolute or [relative](#RelativeURLs).
The fragment portion of the context URL MUST NOT be percent-encoded.

The `context` control information is not returned if
[`metadata=none`](#metadatanoneodatametadatanone) is requested. Otherwise it MUST be the
Expand Down
3 changes: 2 additions & 1 deletion odata-protocol/10 Context URL.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,8 +79,9 @@ http://host/service/$metadata#Customers
:::

If the entities are contained, then `entity-set` is the top-level entity
set or singleton followed by the path to the containment navigation
set or singleton followed by the canonical path to the containment navigation
property of the containing entity.
Key values in that path are represented in canonical form (parentheses-style) without percent-encoding.

::: example
Example ##ex: resource URL and corresponding context URL for contained
Expand Down