From 91b8cd6347ba5e2c275b8b35d12f57cf5cae71ad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Heiko=20Thei=C3=9Fen?= Date: Mon, 9 Sep 2024 12:21:56 +0200 Subject: [PATCH] Completed --- docs/odata-protocol/odata-protocol.html | 6 +++--- docs/odata-protocol/odata-protocol.md | 6 +++--- docs/odata-temporal-ext/odata-temporal-ext.html | 2 +- docs/odata-temporal-ext/odata-temporal-ext.md | 2 +- docs/odata-url-conventions/odata-url-conventions.html | 4 ++-- docs/odata-url-conventions/odata-url-conventions.md | 4 ++-- odata-protocol/11 Data Service Requests.md | 6 +++--- odata-temporal-ext/4 Temporal Requests.md | 2 +- odata-url-conventions/4 Resource Path.md | 4 ++-- 9 files changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/odata-protocol/odata-protocol.html b/docs/odata-protocol/odata-protocol.html index dd439c82..2eb1670f 100644 --- a/docs/odata-protocol/odata-protocol.html +++ b/docs/odata-protocol/odata-protocol.html @@ -1734,13 +1734,13 @@

11.2.4.1 Requesting Stream Properties

-

If the property being requested has type Edm.Stream (see OData-URL, section 9), the media type of the response is the media type of the stream, subject to content type negotiation based on the Accept header of the request. The response body is the octet-stream that represents the raw value of the stream property with that media type.

+

If the property being requested has type Edm.Stream (see OData-URL, section “Addressing a Property”), the media type of the response is the media type of the stream, subject to content type negotiation based on the Accept header of the request. The response body is the octet-stream that represents the raw value of the stream property with that media type.

Note this response format disregards any $format system query option.

11.2.4.2 Requesting a Raw Value using $value

 -

To retrieve the raw value of a primitive property or operation result, the client sends a GET request to the raw value URL. See the OData-URL document for details.

+

To retrieve the raw value of a primitive property or operation result, the client sends a GET request to the raw value URL. See the OData-URL document for details.

The Content-Type of the response is determined using the Accept header and the $format system query option.

The default format for Edm.Binary is the format specified by the Core.MediaType annotation (see OData-VocCore) if this annotation is present. If not annotated, the format cannot be predicted by the client.

The default format for Edm.Geo types is text/plain using the WKT (well-known text) format, see rules fullCollectionLiteral, fullLineStringLiteral, fullMultiPointLiteral, fullMultiLineStringLiteral, fullMultiPolygonLiteral, fullPointLiteral, and fullPolygonLiteral in OData-ABNF.

@@ -1796,7 +1796,7 @@

OData-URL, section 5.1.3.

+

For a full description of the syntax used when building requests, see OData-URL, section “System Query Option $expand”.

Example 38: for each customer entity within the Customers entity set the value of all related Orders will be represented inline

GET http://host/service.svc/Customers?$expand=Orders
diff --git a/docs/odata-protocol/odata-protocol.md b/docs/odata-protocol/odata-protocol.md index 1330463d..096a0e9f 100644 --- a/docs/odata-protocol/odata-protocol.md +++ b/docs/odata-protocol/odata-protocol.md @@ -2792,7 +2792,7 @@ GET http://host/service/Products(1)/Name #### 11.2.4.1 Requesting Stream Properties If the property being requested has type `Edm.Stream` (see -[OData-URL, section 9](#ODataURL)), the media type of the response is the +[OData-URL, section "Addressing a Property"](https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part2-url-conventions.html#AddressingaProperty)), the media type of the response is the media type of the stream, subject to content type negotiation based on the [`Accept`](#HeaderAccept) header of the request. The response body is the octet-stream that represents the raw @@ -2804,7 +2804,7 @@ system query option. #### 11.2.4.2 Requesting a Raw Value using `$value` To retrieve the raw value of a primitive property or operation result, the client sends -a `GET` request to the raw value URL. See the [OData-URL](#ODataURL) document for details. +a `GET` request to the raw value URL. See the [OData-URL](https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part2-url-conventions.html) document for details. The `Content-Type` of the response is determined using the `Accept` header and the [`$format`](#SystemQueryOptionformat) system query @@ -2972,7 +2972,7 @@ expand item is evaluated relative to the retrieved resource being expanded. For a full description of the syntax used when building requests, see -[OData-URL](#ODataURL), section 5.1.3. +[OData-URL, section "System Query Option `$expand`"](https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part2-url-conventions.html#SystemQueryOptionexpand). ::: example Example 38: for each customer entity within the Customers entity set the diff --git a/docs/odata-temporal-ext/odata-temporal-ext.html b/docs/odata-temporal-ext/odata-temporal-ext.html index f4c1fd83..a416031b 100644 --- a/docs/odata-temporal-ext/odata-temporal-ext.html +++ b/docs/odata-temporal-ext/odata-temporal-ext.html @@ -1829,7 +1829,7 @@

4.2.4 Interaction with Standard System Query Options

For snapshot entity sets the point in time for representing data is determined following the rules in section “Propagation of Temporal Query Options” and evaluated first, then all other system query options are evaluated on the data valid at that point in time, including the query option $apply defined in OData-Aggregation.

-

For timeline entity sets the interval for filtering data is determined following the rules in section “Propagation of Temporal Query Options” and evaluated as an additional criterion for $filter in the evaluation sequence defined in OData-Protocol, section “System Query Options”, which is evaluated after the query option $apply.

+

For timeline entity sets the interval for filtering data is determined following the rules in section “Propagation of Temporal Query Options” and evaluated as an additional criterion for $filter in the evaluation sequence defined in OData-Protocol, section “System Query Options”, which is evaluated after the query option $apply.

Example 16: retrieve employee history over a period of application time and filter on job title

GET /api-2/Employees?$expand=history(
diff --git a/docs/odata-temporal-ext/odata-temporal-ext.md b/docs/odata-temporal-ext/odata-temporal-ext.md
index fd345a70..b2f3e2b1 100644
--- a/docs/odata-temporal-ext/odata-temporal-ext.md
+++ b/docs/odata-temporal-ext/odata-temporal-ext.md
@@ -1846,7 +1846,7 @@ on the data valid at that point in time, including the query option
 For timeline entity sets the interval for filtering data is determined
 following the rules in section "[Propagation of Temporal Query Options](#PropagationofTemporalQueryOptions)"
 and evaluated as an additional criterion for `$filter` in the evaluation
-sequence defined in [OData-Protocol, section "System Query Options"](#ODataProtocol),
+sequence defined in [OData-Protocol, section "System Query Options"](https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part1-protocol.html#SystemQueryOptions),
 which is evaluated _after_ the query option `$apply`.
 
 ::: example
diff --git a/docs/odata-url-conventions/odata-url-conventions.html b/docs/odata-url-conventions/odata-url-conventions.html
index 50519979..811b798d 100644
--- a/docs/odata-url-conventions/odata-url-conventions.html
+++ b/docs/odata-url-conventions/odata-url-conventions.html
@@ -1081,7 +1081,7 @@ 
  "$select": "FirstName,LastName"
 }
-

Members of the JSON object also include parameters if the resource path is a function invocation or function import. In this case parameters MUST be represented like parameters in an action invocation OData-JSON, section 18, and in the resource path parentheses after the function name MUST be omitted.

+

Members of the JSON object also include parameters if the resource path is a function invocation or function import. In this case parameters MUST be represented like parameters in an action invocation OData-JSON, section “Action Invocation”, and in the resource path parentheses after the function name MUST be omitted.

Example 53: An employee’s top ten leave requests from now to the end of the year pending their manager’s approval.

POST http://host/service/Employees(23)/self.PendingLeaveRequests/$query
@@ -1093,7 +1093,7 @@ 
  "Approver@expression": "Manager",
   "$top": 10
 }
-

The previous request looks analogous to a bound function invocation with expressions (like in example 30) if it is written using implicit parameter aliases (see OData-Protocol, section 11.5.4.1.1).

+

The previous request looks analogous to a bound function invocation with expressions (like in example 30) if it is written using implicit parameter aliases (see OData-Protocol, section “Inline Parameter Syntax”).

GET http://host/service/Employees(23)/self.PendingLeaveRequests
   ?StartDate=now()
   &EndDate=2024-12-31
diff --git a/docs/odata-url-conventions/odata-url-conventions.md b/docs/odata-url-conventions/odata-url-conventions.md
index c39837d1..7d849a34 100644
--- a/docs/odata-url-conventions/odata-url-conventions.md
+++ b/docs/odata-url-conventions/odata-url-conventions.md
@@ -1542,7 +1542,7 @@ Content-Type: application/json
 
 Members of the JSON object also include parameters
 if the resource path is a function invocation or function import. In this case
-parameters MUST be represented like parameters in an action invocation [OData-JSON, section 18](#ODataJSON),
+parameters MUST be represented like parameters in an action invocation [OData-JSON, section "Action Invocation"](https://docs.oasis-open.org/odata/odata-json-format/v4.02/odata-json-format-v4.02.html#ActionInvocation),
 and in the resource path parentheses after the function name MUST be omitted.
 
 ::: example
@@ -1561,7 +1561,7 @@ Content-Type: application/json
 ```
 
 The previous request looks analogous to a bound function invocation with expressions (like in [example 30](#funcexpr))
-if it is written using implicit parameter aliases (see [OData-Protocol, section 11.5.4.1.1](#ODataProtocol)).
+if it is written using implicit parameter aliases (see [OData-Protocol, section "Inline Parameter Syntax"](https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part1-protocol.html#InlineParameterSyntax)).
 ```
 GET http://host/service/Employees(23)/self.PendingLeaveRequests
   ?StartDate=now()
diff --git a/odata-protocol/11 Data Service Requests.md b/odata-protocol/11 Data Service Requests.md
index a447ab8e..bf897a81 100644
--- a/odata-protocol/11 Data Service Requests.md	
+++ b/odata-protocol/11 Data Service Requests.md	
@@ -231,7 +231,7 @@ GET http://host/service/Products(1)/Name
 #### ##subsubsubsec Requesting Stream Properties
 
 If the property being requested has type `Edm.Stream` (see
-[OData-URL, section 9](#ODataURL)), the media type of the response is the
+[OData-URL, section "Addressing a Property"]($$$OData-URL$$$#AddressingaProperty)), the media type of the response is the
 media type of the stream, subject to content type negotiation based on the
 [`Accept`](#HeaderAccept) header of the request.
 The response body is the octet-stream that represents the raw
@@ -243,7 +243,7 @@ system query option.
 #### ##subsubsubsec Requesting a Raw Value using `$value`
 
 To retrieve the raw value of a primitive property or operation result, the client sends
-a `GET` request to the raw value URL. See the [OData-URL](#ODataURL) document for details.
+a `GET` request to the raw value URL. See the [OData-URL]($$$OData-URL$$$) document for details.
 
 The `Content-Type` of the response is determined using the `Accept`
 header and the [`$format`](#SystemQueryOptionformat) system query
@@ -411,7 +411,7 @@ expand item is evaluated relative to the retrieved resource being
 expanded.
 
 For a full description of the syntax used when building requests, see
-[OData-URL](#ODataURL), section 5.1.3.
+[OData-URL, section "System Query Option `$expand`"]($$$OData-URL$$$#SystemQueryOptionexpand).
 
 ::: example
 Example ##ex: for each customer entity within the Customers entity set the
diff --git a/odata-temporal-ext/4 Temporal Requests.md b/odata-temporal-ext/4 Temporal Requests.md
index a72f5428..70ef58bc 100644
--- a/odata-temporal-ext/4 Temporal Requests.md	
+++ b/odata-temporal-ext/4 Temporal Requests.md	
@@ -441,7 +441,7 @@ on the data valid at that point in time, including the query option
 For timeline entity sets the interval for filtering data is determined
 following the rules in section "[Propagation of Temporal Query Options](#PropagationofTemporalQueryOptions)"
 and evaluated as an additional criterion for `$filter` in the evaluation
-sequence defined in [OData-Protocol, section "System Query Options"](#ODataProtocol),
+sequence defined in [OData-Protocol, section "System Query Options"]($$$OData-Protocol$$$#SystemQueryOptions),
 which is evaluated _after_ the query option `$apply`.
 
 ::: example
diff --git a/odata-url-conventions/4 Resource Path.md b/odata-url-conventions/4 Resource Path.md
index 167ecb9f..8e115c21 100644
--- a/odata-url-conventions/4 Resource Path.md	
+++ b/odata-url-conventions/4 Resource Path.md	
@@ -1086,7 +1086,7 @@ Content-Type: application/json
 
 Members of the JSON object also include parameters
 if the resource path is a function invocation or function import. In this case
-parameters MUST be represented like parameters in an action invocation [OData-JSON, section 18](#ODataJSON),
+parameters MUST be represented like parameters in an action invocation [OData-JSON, section "Action Invocation"]($$$OData-JSON$$$#ActionInvocation),
 and in the resource path parentheses after the function name MUST be omitted.
 
 ::: example
@@ -1105,7 +1105,7 @@ Content-Type: application/json
 ```
 
 The previous request looks analogous to a bound function invocation with expressions (like in [example ##funcexpr])
-if it is written using implicit parameter aliases (see [OData-Protocol, section 11.5.4.1.1](#ODataProtocol)).
+if it is written using implicit parameter aliases (see [OData-Protocol, section "Inline Parameter Syntax"]($$$OData-Protocol$$$#InlineParameterSyntax)).
 ```
 GET http://host/service/Employees(23)/self.PendingLeaveRequests
   ?StartDate=now()